Đang chuẩn bị liên kết để tải về tài liệu:
Lecture Software requirements engineering - Lecture­ 14: Elaboration process

After this chapter the student should have acquired the following knowledge and skills: Object oriented analysis, class modeling, object oriented analysis, object oriented modeling, behavioral modeling, structure analysis, flow oriented modeling. | Elaboration Process Lecture-14 Recap Object Oriented Analysis Class Modeling Class Diagram Class diagram for the system class 3 Today’s lecture Object Oriented analysis Object oriented modeling Behavioral modeling Structure analysis Flow oriented modeling CRC Modeling 5 CRC Modeling A CRC model index card for FloorPlan class 6 Behavioral Modeling Creating a Behavioral Model Identify events found within the use cases and implied by the attributes in the class diagrams Build a state diagram for each class, and if useful, for the whole software system Identifying Events in Use Cases An event occurs whenever an actor and the system exchange information An event is NOT the information that is exchanged, but rather the fact that information has been exchanged Some events have an explicit impact on the flow of control, while others do not An example is the reading of a data item from the user versus comparing the data item to some possible value Building a State Diagram A state is represented by a rounded rectangle A transition (i.e., event) is represented by a labeled arrow leading from one state to another Syntax: trigger-signature [guard]/activity The active state of an object indicates the current overall status of the object as is goes through transformation or processing A state name represents one of the possible active states of an object The passive state of an object is the current value of all of an object's attributes A guard in a transition may contain the checking of the passive state of an object Identifying Events A use-case is examined for points of information exchange. The homeowner uses the keypad to key in a four-digit password. The password is compared with the valid password stored in the system. If the password in incorrect, the control panel will beep once and reset itself for additional input. If the password is correct, the control panel awaits further action. State Diagram State diagram for the ControlPanel class 12 Sequence Diagram Sequence diagram (partial) for the SafeHome security function 13 Summary Class Modeling CRC Behavioral modeling State diagrams Sequence diagrams | Elaboration Process Lecture-14 Recap Object Oriented Analysis Class Modeling Class Diagram Class diagram for the system class 3 Today’s lecture Object Oriented analysis Object oriented modeling Behavioral modeling Structure analysis Flow oriented modeling CRC Modeling 5 CRC Modeling A CRC model index card for FloorPlan class 6 Behavioral Modeling Creating a Behavioral Model Identify events found within the use cases and implied by the attributes in the class diagrams Build a state diagram for each class, and if useful, for the whole software system Identifying Events in Use Cases An event occurs whenever an actor and the system exchange information An event is NOT the information that is exchanged, but rather the fact that information has been exchanged Some events have an explicit impact on the flow of control, while others do not An example is the reading of a data item from the user versus comparing the data item to some possible value Building a State Diagram A state is .