[计算机软件及应用]CH06对象建模.ppt

北京工商大学信息工程学院姜同强 学习目标 学习完本章后，你应该具备以下能力： 理解对象建模中各种模型之间的关系； 构造捕获系统功能需求的用例模型； 理解需求分析中用例的作用； 发现系统中的类、明确类之间的关系，构造类图； 构造顺序图和协作图。 Requirements Artifacts The set of the use cases describes the user requirements for the system. We derive the software requirements from the use cases during the analysis. Requirements Artifacts The use case models represent the use cases. A use case specification describes each use case diagram. The use case specifications are the detailed description of how the user interacts with the system to achieve a specific goal. Storyboards are a series if pictures that tell the story of what occurs, from the perspective of the user, during a use case. Each use case specification has one or more storyboards. The set of use case specifications must meet all the requirements that describe that the user needs the system to do. The User Requirements are not a specific artifact we produce but are included in multiple artifacts. Requirements Artifacts The Analysis Model also contains one or more Class Diagrams. The Class Diagrams show the entities that need to work together to ensure that our system realizes each use case specification. The Class Diagram contains the functional requirements of the software. Requirements Artifacts The Analysis Model also contains one or more Sequence Diagrams. Sequence Diagrams show how objects of the classes in the Class Diagram collaborate to realize a use case. Each use case specification is related to one or more sequence diagrams. Requirements Artifacts The Analysis Model also contains State Diagrams and Activity Diagrams. Both diagrams are an aid to understanding complex issues with classes, use cases, or major aspects of the system as a whole. Requirements Artifacts The Software Requirements Specification (SRS) is the final artifact of the requirements development process. The SRS contains Functional requirements nonfunctional requirements Interface Requirements Specification (IRS) Requirements Process The nature