Software Development Task: Essential Elements

Stakeholders and Their Interests

Q1. List the main stakeholders for the Hour4Hour system (H4H). 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.
Q2. (a) List and briefly describe the main functional requirements for the H4H.
(b) List and briefly describe the main nonfunctional requirements for the H4H.
Q3. (a) Use the User Goal technique to develop a list of use cases for the H4H. 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 H4H. These will probably be temporal and state event types. Present your list in a table that includes the event, type of event, use case name, and brief use case description. You do not need to repeat the use cases you identified in (a) here. (Note that some use cases are already identified in Q6,7,8, below. Include these in your lists.)
Q4. Create a domain model class diagram for the H4H, including all classes, attributes, associations, and multiplicity. Show association classes and generalisationhierarchies where appropriate.
Q5. 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 so that your final set of models is consistent.
Q6. Create a fully-developed use case description for the use case Close Activity. Follow the template provided at the end of this handout.
Q7. Draw an activity diagram to represent the flow of activities for the use case Create Monthly Activities report.
Q8. Draw a system sequence diagram for the use case Submit Offer.
Q9. Draw a state machine diagram to show the possible states and transitions for a NEED object. Label each state with the state name. Label each transition with the appropriate transition name, guard condition (if appropriate) and action expression (if appropriate).
Q10. Develop a user acceptance test plan for a member of the H4H system. Base it on the relevant use cases you have identified. You can follow the example in the textbook (below). Present your test plan in a table including the fields: use case name, test
conditions, expected outcomes. You do not need to include test data.