See the question file

See the question file
() Use Case Specification Document () Use Case Specification Document Version No. Project Document Revision History VersionNumber Date Revision Author Description of Revision Table of Contents 1. Introduction 4 2. Use Case Information 4 2.1 Actors 4 2.2 Use Case Interaction 4 3. Trigger 4 4. Pre-condition(s) 4 4.1 4 4.2 4 5. Post-condition(s) 4 5.1 5 5.2 5 6. Use Case Swimlane (Activity) Diagram 5 7. Main/Basic Flow(s) of Events (Happy Path) 5 7.1 5 7.2 5 8. Alternate/Exception Flow of Events 5 8.1 5 8.2 5 9. Assumptions/Business Rules including Non-Functional Requirements 5 10. Use Case Specification Review and Signoff 5 6 Introduction This document captures detailed functional and non-functional BUSINESS requirements. Technical or application IT requirements should not be detailed here. A separate Use Case Summary document ties ALL the individual use cases together. First create the Use Case Summary document using application decomposition. Then increase the detail by creating the individual use case specifications – be careful not to create too many or not create enough use cases. Write a single paragraph describing the purpose of the specific use case in the Introduction. Use Case Information Actors An actor is someone or something (e.g. application system) outside the system or business that interacts with the application. For every Use Case, there must be at least one Main Actor and zero or more Secondary Actors. Actors should be a person, system, or time. Actor Name Role Description Main Secondary ….. Use Case Interaction How does this use case relate to other uses cases? List predecessor and successor use cases. Trigger What causes the use case to initiate? Pre-condition(s) What use cases or other pre-conditions must be met before use can initiate? ….. Post-condition(s) What are ALL the possible output states upon completion of the use case flows? …… Use Case Swimlane (Activity) Diagram Draw diagram(s) that cover ALL main and alternate flows. Main/Basic Flow(s) of Events (Happy Path) For each main flow (usually ONE flow) write the list of steps that occur – describe WHAT occurs not HOW to do it! …. Alternate/Exception Flow of Events For each alternative flow (can be zero or more) write the list of steps that occur – describe WHAT occurs not HOW to do it! …. Assumptions/Business Rules including Non-Functional Requirements Be sure to number the assumption/business rules to allow easy reference to them. Business rules will be where non-functional requirements are recorded – have a way to specifically identify non-functional requirements. Use Case Specification Review and Signoff Review and Signoff of the Use Case Specification Name Project Team Role Signature Date Business Analyst Systems Analyst ….. Originator: / Page 6 of 6 Date Created: Date Revised: Version Number: