Can someone help me Create a set of detailed use-case DESCRIPTIONS not a use cas
ID: 665511 • Letter: C
Question
Can someone help me Create a set of detailed use-case DESCRIPTIONS not a use case DIAGRAM for a gym membership system?
I am looking for a more detailed one that I have.
This is the use case Description format:
Use Case Description
Use Case Name:
ID:
Importance Level:
Primary Actor:
Stakeholders and Interests:
Brief Description:
Trigger:
Relationships:
Include:
Extend:
Normal Flow of Events:
SubFlows:
S-1:
S-2:
Alternate/Exceptional Flows:
Use Case Name:
ID:
Importance Level:
Primary Actor:
Stakeholders and Interests:
Brief Description:
Trigger:
Relationships:
Include:
Extend:
Normal Flow of Events:
SubFlows:
S-1:
S-2:
Alternate/Exceptional Flows:
Explanation / Answer
A use case diagram is a graphic depiction of the interactions among the elements of a system.
A use case is a methodology used in system analysis to identify, clarify, and organize system requirements. In this context, the term "system" refers to something being developed or operated, such as a mail-order product sales and service Web site. Use case diagrams are employed in UML (Unified Modeling Language), a standard notation for the modeling of real-world objects and systems.
System objectives can include planning overall requirements, validating a hardware design, testing and debugging a software product under development, creating an online help reference, or performing a consumer-service-oriented task. For example, use cases in a product sales environment would include item ordering, catalog updating, payment processing, and customer relations. A use case diagram contains four components.
The boundary, which defines the system of interest in relation to the world around it.
The actors, usually individuals involved with the system defined according to their roles.
The use cases, which are the specific roles played by the actors within and around the system.
The relationships between and among the actors and the use cases.
Reation In Usecase:
Extend is a directed relationship that specifies how and when the behavior defined in usually supplementary (optional) extending use case can be inserted into the behavior defined in the extended use case.
Extended use case is meaningful on its own, it is independent of the extending use case. Extending use case typically defines optional behavior that is not necessarily meaningful by itself. The extend relationship is owned by the extending use case. The same extending use case can extend more than one use case, and extending use case may itself be extended.
Registration.........extend...........>Get on Registration
Triggers
A trigger is the initiator of a use case. It is what causes the use case to start. There isn’t a promise that this event happens – only an indication that this event triggers the start of a use case.
The simple use case above is initiated by one of two events:
The first event is the obvious one – an external event initiates a response from BugBGone.
The second event is driven by BugBGone’s business rules. Perhaps they have a quarterly treatment program, and every week they review the previous quarter’s appointments to contact existing customers and schedule new appointments for them.
Either trigger could initiate the use case, but neither is required to have happened. This lets the team know that they have to account for either trigger, but can not rely on either of them (having happened prior to the start of the use case).
Related Questions
drjack9650@gmail.com
Navigate
Integrity-first tutoring: explanations and feedback only — we do not complete graded work. Learn more.