List the main stakeholders for Fearless Spiders Indoor Rock Climbing System (FSIRCS). For each stakeholder, write a brief description of their interest in the system and what aspects of it are of particular relevance to them.
You do not need to categorise the stakeholders. Don’t include the systems development team.
List and briefly describe the main functional requirements for the FSIRCS.
List and briefly describe the main nonfunctionalrequirements for the FSIRCS.
Use the User Goal technique to develop a list of use cases for the FSIRCS.
Present your list in a table that includes the participating actors, use case name
and a brief use case description. (b) Use the Event Decomposition technique to identify any additional use cases for the FSIRCS. These will probably be temporal and state event types. Present your list in a table that includes the event, type of event, trigger, use case name, and brief use case description. (Note that some use cases are already identified in Q6, 7, 10 below. Include these in
Create a domain model class diagram for the system, including all classes,attributes, associations, and multiplicity. Show association classes and generalisation hierarchies where appropriate.
Create a CRUD matrix to check the consistency between your domain model class diagram and your complete list of use cases. Set this out in the form of a table with classes as the columns and use cases as the rows. If you find discrepancies between the models while you are doing this, you should go back and correct your earlier models as required.
Create a fully-developed use case description for the use case Book a Climbing Session.
Follow the template provided at the end of this handout.
Draw an activity diagram to represent the flow of activities for the use case Inspect Wall shown at the end of this handout.
Draw a system sequence diagram for the use case Inspect Wall shown at the end of this handout that corresponds to your activity diagram in Draw a state machine diagram to show the possible states and transitions for a Wall object. Label each state with the state name. Label each transition with the appropriate transition name, guard condition (if appropriate) and action expression
Based on the activity diagram for the use case Create Usage Report shown at the end of this handout: (a) Develop a first-cut* sequence diagram for the use case (b) Develop a design class diagram for the relevant part of your domain class diagram