系统分析与设计Chap07.pptVIP

* No additional notes * No additional notes * No additional notes * Teaching Notes Note that the use cases have been grouped into business sub-systems. This is key to defining your development strategy – which use cases will be developed first and by whom. * No additional notes. * Teaching Notes Author – the persons who wrote the use case and provide a point of contact for anyone requiring additional information. Date – the date the use case was last modified. Version – the current version of the use case. Use-case name – the use-case name should represent the goal that the use case is trying to accomplish. Should begin with a verb. Use-case type – Business requirements use cases provide a general understanding of the problem domain and scope but don’t include detail to communicate to developers what the system should do. Use-case ID – A unique identifier for the use case. Priority – The priority communicates the importance of the use case (high, medium, or low). Source – The source defines the entity that triggered the creation of the use case. Primary business actor – The stakeholder that primarily benefits from the execution of the use case. Other participating actors – Other actors that participate in the use case. Interested stakeholders – A person (other than the actor) who has a vested interest in the goal of the use case. Description – A short summary description of the purpose of the use case and its activities. * Teaching Notes Precondition – A constraint on the state of the system before the use case can be executed. Trigger – The event that initiates the use case. * Teaching Notes Typical course of events – The normal sequence of activities performed by the actor(s) and the system to satisfy the goal of the use case. * Teaching Notes Alternate courses – The behaviors of the use case if an exception or variation to the typical course occurs. Conclusion – When the use case successfully ends. Postcondition – A constraint on the state of the system after the