Seventh Edition - Chương 12

Tham khảo tài liệu seventh edition - chương 12, công nghệ thông tin, kỹ thuật lập trình phục vụ nhu cầu học tập, nghiên cứu và làm việc hiệu quả
Nội dung trích xuất từ tài liệu:
Seventh Edition - Chương 12 Slide 12.1Object-Oriented and Classical Software EngineeringSeventh Edition, WCB/McGraw-Hill, 2007 Stephen R. Schach srs@vuse.vanderbilt.edu © The McGraw-Hill Companies, 2007 CHAPTER 12 Slide 12.2OBJECT-ORIENTED ANALYSIS © The McGraw-Hill Companies, 2007 Overview Slide 12.3 The analysis workflow Extracting the entity classes Object-oriented analysis: The elevator problem case study Functional modeling: The elevator problem case study Entity class modeling: The elevator problem case study Dynamic modeling: The elevator problem case study The test workflow: Object-oriented analysis © The McGraw-Hill Companies, 2007 Overview (contd) Slide 12.4 Extracting the boundary and control classes The initial functional model: The MSG Foundation case study The initial class diagram: The MSG Foundation case study The initial dynamic model: The MSG Foundation case study Extracting the boundary classes: The MSG Foundation case study Extracting the boundary classes: The MSG Foundation case study © The McGraw-Hill Companies, 2007 Overview (contd) Slide 12.5 Refining the use cases: The MSG Foundation case study Use-case realization: The MSG Foundation case study Incrementing the class diagram: The MSG Foundation case study The specification document in the Unified Process More on actors and use cases CASE tools for the object-oriented analysis workflow Challenges of the object-oriented analysis workflow © The McGraw-Hill Companies, 2007 Object-Oriented Analysis Slide 12.6 OOA is a semiformal analysis technique for the object-oriented paradigm  There are over 60 equivalent techniques  Today, the Unified Process is the only viable alternative During this workflow  The classes are extracted Remark  The Unified Process assumes knowledge of class extraction © The McGraw-Hill Companies, 2007 12.1 The Analysis Workflow Slide 12.7 The analysis workflow has two aims  Obtain a deeper understanding of the requirements  Describe them in a way that will result in a maintainable design and implementation © The McGraw-Hill Companies, 2007 The Analysis Workflow (contd) Slide 12.8 There are three types of classes: Entity classes Boundary classes Control classes © The McGraw-Hill Companies, 2007 The Analysis Workflow (contd) Slide 12.9 Entity class  Models long-lived information Examples:  Account Class  Investment Class © The McGraw-Hill Companies, 2007 The Analysis Workflow (contd) Slide 12.10 Boundary class  Models the interaction between the product and the environment  A boundary class is generally associated with input or output Examples:  Investments Report Class  Mortgages Report Class © The McGraw-Hill Companies, 2007 The Analysis Workflow (contd) Slide 12.11 Control class  Models complex computations and algorithms Example:  Estimate Funds for Week Class © The McGraw-Hill Companies, 2007UML Notation for These Three Class Types Slide 12.12 Stereotypes (extensions of UML) Figure 12.1 © The McGraw-Hill Companies, 2007 12.2 Extracting the Entity Classes Slide 12.13 Perform the following three steps incrementally and iteratively  Functional modeling Present scenarios of all the use cases (a scenario is an instance  of a use case)  Class modeling Determine the entity classes and their attributes   Determine the interrelationships and interactions between the entity classes  Present this information in the form of a class diagram  Dynamic modeling Determine the operations performed by or to each entity class   Present this information in the form of a statechart © The McGraw-Hill Companies, 2007 12.3 Object-Oriented Analysis: The Elevator Problem Case Study Slide 12.14A product is to be installed to control n elevators in a buildingwith m floors. The problem concerns the logic required tomove elevators between floors according to the followingconstraints:1. Each elevator has a set of m buttons, one for each floor.These illuminate when pressed and cause the elevator to visitthe corresponding floor. The illumination is canceled whenthe corresponding floor is visited by the elevator2. Each floor, except the first and the top floor, has twobuttons, one to request an up-elevator, one to request adown-elevator. These buttons illuminate when pressed. Theillumination is canceled when an elevator visits the floor, thenmoves in the desired direction3. If an elevator has no requests, it remains at its currentfloor with its doors closed © The McGraw-Hill Companies, 200712.4 Functional Modeling: The Elevator Problem Case Study ...