Đang tải... (xem toàn văn)
Topics covered • Context models • Interaction models • Structural models • Behavioral models Modeldriven engineering System modeling • the process of developing abstract models of a system, with each model presenting a different view or perspective of that system. • representing a system using some kind of graphical notation, which is now almost always based on notations Jul 2013 Chapter 5. System modeling 3 notation, which is now almost always based on notations in the Unified Modeling Language (UML). • helps the analyst to understand the functionality of the system and models are used to communicate with customers
SOFTWARE ENGINEERING Chapter – System Modelling Jul 2013 Topics covered • Context models • Interaction models • Structural models • Behavioral models • Model-driven engineering Chapter System modeling Jul 2013 Chapter System modeling System modeling • the process of developing abstract models of a system, with each model presenting a different view or perspective of that system • representing a system using some kind of graphical notation, which is now almost always based on notations in the Unified Modeling Language (UML) • helps the analyst to understand the functionality of the system and models are used to communicate with customers Jul 2013 Chapter System modeling Existing and planned system models • Models of the existing system • are used during requirements engineering • to help clarify what the existing system does and can be used as a basis for discussing its strengths and weaknesses • then lead to requirements for the new system • Models of the new system • are used during requirements engineering • to help explain the proposed requirements to other system stakeholders • Engineers use these models to discuss design proposals and to document the system for implementation Jul 2013 Chapter System modeling System perspectives • An external perspective • model the context or environment of the system • An interaction perspective • model the interactions between a system and its environment, or between the components of a system • A structural perspective • model the organization of a system or the structure of the data that is processed by the system • A behavioral perspective • model the dynamic behavior of the system and how it responds to events Jul 2013 Chapter System modeling UML diagram types • Activity diagrams • show the activities involved in a process or in data processing • Use case diagrams • show the interactions between a system and its environment • Sequence diagrams • show interactions between actors and the system and between system components • Class diagrams • show the object classes in the system and the associations between these classes • State diagrams • show how the system reacts to internal and external events Jul 2013 Chapter System modeling Use of graphical models • As a means of facilitating discussion about an existing or proposed system • Incomplete and incorrect models are OK as their role is to support discussion • As a way of documenting an existing system • Models should be an accurate representation of the system but need not be complete • As a detailed system description that can be used to generate a system implementation • Models have to be both correct and complete Jul 2013 Chapter System modeling Context models • Illustrate the operational context of a system • show what lies outside the system boundaries • Social and organisational concerns may affect the decision on where to position system boundaries • Architectural models show the system and its relationship with other systems Jul 2013 Chapter System modeling System boundaries • System boundaries are established to define what is inside and what is outside the system • They show other systems that are used or depend on the system being developed • The position of the system boundary has a profound effect on the system requirements • Defining a system boundary is a political judgment • There may be pressures to develop system boundaries that increase / decrease the influence or workload of different parts of an organization Jul 2013 Chapter System modeling The context of the MHC-PMS 10 Jul 2013 Chapter System modeling 55 Types of model • A computation independent model (CIM) • These model the important domain abstractions used in a system CIMs are sometimes called domain models • A platform independent model (PIM) • These model the operation of the system without reference to its implementation The PIM is usually described using UML models that show the static system structure and how it responds to external and internal events • Platform specific models (PSM) • These are transformations of the platform-independent model with a separate PSM for each application platform In principle, there may be layers of PSM, with each layer adding some platformspecific detail Jul 2013 Chapter System modeling MDA transformations 56 Jul 2013 Chapter System modeling Multiple platform-specific models 57 Jul 2013 Chapter System modeling 58 Summary • A model is an abstract view of a system that ignores system details Complementary system models can be developed to show the system’s context, interactions, structure and behavior • Context models show how a system that is being modeled is positioned in an environment with other systems and processes • Use case diagrams and sequence diagrams are used to describe the interactions between users and systems in the system being designed Use cases describe interactions between a system and external actors; sequence diagrams add more information to these by showing interactions between system objects • Structural models show the organization and architecture of a system Class diagrams are used to define the static structure of classes in a system and their associations Jul 2013 Chapter System modeling 59 Summary (cont.) • Behavioral models are used to describe the dynamic behavior of an executing system This behavior can be modeled from the perspective of the data processed by the system, or by the events that stimulate responses from a system • Activity diagrams may be used to model the processing of data, where each activity represents one process step • State diagrams are used to model a system’s behavior in response to internal or external events • Model-driven engineering is an approach to software development in which a system is represented as a set of models that can be automatically transformed to executable code Jul 2013 60 Chapter System modeling Collaboration diagrams – Example • Collaboration diagram for use-case Login 1: login(uname,pswd) : People 1.2 [succ = true]: welcome : Database : LoginForm 1.1: succ := Verify(uname,pswd) Jul 2013 61 Chapter System modeling Collaboration diagrams – Example • Collaboration diagram for use-case Registers course 2: register 1: submit(uname, psswd) : LoginForm 1.2 [succ = true]: welcome 3: submit(crsOffering) : Student 2.1: create 3.4: beSuccessful 1.1: succ := verify(uname, psswd) regForm : RegisterForm 3.1: reg := FetchReg(crsOffering) 3.3: SetReg(reg) 3.2: AddStudent(code) : Registration : Database Jul 2013 62 Chapter System modeling Collaboration diagrams vs Sequence diagrams -• Sequence Example diagram for use-case Login : LoginForm : People 1: submit(uname, psswd) 1.2: welcome : Database 1.1: verify(uname, psswd) Jul 2013 Chapter System modeling Collaboration diagrams vs Sequence diagrams - Example • Sequence diagram for use-case Register courses : Student regForm : RegisterForm : LoginForm 1: submit(uname, psswd) 1.2: welcome : Registration : Database 1.1: verify(uname, psswd) 2: register 2.1: create submit(crsOffering) 3.1: reg := fetchReg(srcOffering) 3.2: addStudent(code) 3.3: setReg(reg) 3.4: beSuccessful( ) 63 Jul 2013 Chapter System modeling 64 Activity diagrams • An activity diagram is a special kind of a statechart diagram that shows the flow from activity to activity within a system • Activity diagrams address the dynamic view of a system They are especially important in modeling the function of a system and emphasize the flow of control among objects • Focuses on activities Activity diagrams Jul 2013 Chapter System modeling 65 Jul 2013 Activity diagrams • Decisions: A decision involves selecting one control-flow transition out of many control-flow transitions based upon a condition Chapter System modeling 66 Jul 2013 Activity diagrams • Concurrency: Concurrency involves selecting multiple transitions simultaneously For example, while the printer is printing a report, the printer must also monitor for other incoming print requests Chapter System modeling 67 Jul 2013 Chapter System modeling 68 Activity diagrams – Example • Activity diagram for submitting action in LoginForm LoginForm Database Show input for username and password Verify [ psswd invalid ] Reject [ psswd valid ] Welcome swimlane Jul 2013 Chapter System modeling 69 Activity diagrams – Example • Activity diagram for submitting in RegisterForm RegForm Database Registration submit Read course offerings Look for registration [ reg found ] [ reg not found ] Create registration Show success Fetch registration Update registration Add student [...]... books borrowed, returned, ordered in a month/quarter Jul 2013 Chapter 5 System modeling 12 Library Mgmt System: System boundary Jul 2013 Chapter 5 System modeling 13 Process perspective • Context models simply show the other systems in the environment, not how the system being developed is used in that environment • Process models reveal how the system being developed is used in broader business processes... use case My operation Jul 2013 Chapter 5 System modeling Library Mgmt System: A sequence diagram 30 Jul 2013 Chapter 5 System modeling 31 Structural models • Structural models of software display the organization of a system in terms of the components that make up that system and their relationships • Structural models may be static models, which show the structure of the system design, or dynamic models,... hits “Confirm” button 5 System change the user name to the new name Jul 2013 Chapter 5 System modeling 24 Library Mgmt System : a few use-cases • Actors: Librarian, Admin, anymore? • Use-cases: Login, Searching-Browsing, Borrow, Return, Create a New Member, Edit Member’s Info??? • Any relations between use-cases? , ??? Jul 2013 Chapter 5 System modeling 25 Sequence diagrams • Sequence... models Jul 2013 Chapter 5 System modeling 14 Process model of involuntary detention Jul 2013 Chapter 5 System modeling 15 Interaction models • Modeling user interaction is important as it helps to identify user requirements • Modeling system- to -system interaction highlights the communication problems that may arise • Modeling component interaction helps us understand if a proposed system structure... system object • An association is a link between classes that indicates that there is some relationship between these classes • When you are developing models during the early stages of the software engineering process, objects represent something in the real world, such as a patient, a prescription, doctor, etc Jul 2013 Chapter 5 System modeling UML classes and association 33 Jul 2013 Chapter 5 System. .. Jul 2013 Chapter 5 System modeling 19 Use cases in the MHC-PMS involving the role ‘Medical Receptionist’ Jul 2013 Chapter 5 System modeling 20 Alternative Use-Case Scenarios • Scenario • A single sequence of steps • No branching!!! • Ex: Login use-case • Main scenario 1 User enters username and password 2 User click “Login” button 3 System validates the username and password are correct 4 System change... design, or dynamic models, which show the organization of the system when it is executing • You create structural models of a system when you are discussing and designing the system architecture Jul 2013 Chapter 5 System modeling 32 Class diagrams • Class diagrams are used when developing an object- oriented system model to show the classes in a system and the associations between these classes • An object... may be people or other systems • Represented diagramatically to provide an overview of the use case and in a more detailed textual form Jul 2013 Chapter 5 System modeling Transfer-data use case • A use case in the MHC-PMS 17 Jul 2013 Chapter 5 System modeling 18 Tabular description of the ‘Transfer data’ use-case MHC-PMS: Transfer data Actors Medical receptionist, patient records system (PRS) Description... doctor, etc Jul 2013 Chapter 5 System modeling UML classes and association 33 Jul 2013 Chapter 5 System modeling 34 Classes and associations in the MHCPMS Jul 2013 Chapter 5 System modeling The Consultation class 35 Jul 2013 Chapter 5 System modeling 36 Generalization • Generalization is an everyday technique that we use to manage complexity • Rather than learn the detailed characteristics of every... • Interactions between objects are indicated by annotated arrows Jul 2013 Chapter 5 System modeling Sequence diagram for View patient information 26 Jul 2013 Chapter 5 System modeling 27 Sequence diagram for Transfer Data Jul 2013 Chapter 5 System modeling 28 Build a Sequence Diagram • 1 Identify the use case whose sequence diagram you will build • 2 Identify which entity initiates the use case •