We think you have liked this presentation. If you wish to download it, please recommend it to your friends in any social system. Share buttons are a little bit lower. Thank you!
Presentation is loading. Please wait.
Published byElijah Klein
Modified over 2 years ago
© 2005 by Prentice Hall Appendix 3 Object-Oriented Analysis and Design Modern Systems Analysis and Design Fourth Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich
© 2005 by Prentice Hall Appendix 3-2 Learning Objectives Define events, state transitions, and sequence diagrams. Describe concepts and principles of object- orientation. Describe activities of the different phases of object-oriented development. Compare object-oriented modeling with traditional systems development approaches. Develop dynamic models with state, interaction, and activity diagrams. Model real-world applications with UML.
© 2005 by Prentice Hall Appendix 3-3 The Object-Oriented Development Life Cycle Process of progressively developing representation of a system component (or object) through the phases of analysis, design, and implementation The model is abstract in the early stages As the model evolves, it becomes more and more detailed
© 2005 by Prentice Hall Appendix 3-4 Object oriented cycle is like an onion, evolving from abstract to detailed, from external qualities to system architecture and algorithms.
© 2005 by Prentice Hall Appendix 3-5 Object-Oriented Deliverables and Outcomes 1.The ability to tackle more challenging problem domains 2.Improved communication among users, analysts, designers, and programmers 3.Increased consistency among analysis, design, and programming activities 4.Explicit representation of commonality among system components 5.Robust systems 6.Reusability of analysis, design, and programming results 7.Increased consistency among the models developed during object-oriented analysis, design, and programming
© 2005 by Prentice Hall Appendix 3-6 The Unified Modeling Language (UML) A notation that allows the modeler to specify, visualize, and construct the artifacts of software systems, as well as business models Techniques and notations: Use cases Class diagrams State diagrams Sequence diagrams Activity diagrams
© 2005 by Prentice Hall Appendix 3-7 Use Cases Revisited A depiction of a systems behavior or functionality under various conditions as the system responds to requests from users Full functioning for a specific business purpose See Chapter 7
© 2005 by Prentice Hall Appendix 3-8
© 2005 by Prentice Hall Appendix 3-9 Class Diagrams Revisited Features: Objects and classes Encapsulation of attributes and operations Polymorphism Inheritance Aggregation and composition See Chapter 9
© 2005 by Prentice Hall Appendix 3-10
© 2005 by Prentice Hall Appendix 3-11 Dynamic Modeling Representation of activities that occur throughout the lifetime of a system Types of UML dynamic models State diagram: state changes within an object Sequence diagram: time-sequenced interactions between objects Activity diagram: flow of control between activities within an object
© 2005 by Prentice Hall Appendix 3-12 State Diagrams State A condition during the life of an object during which it satisfies some conditions, performs some actions or waits for some events Shown as a rectangle with rounded corners State Transition The changes in the attribute of an object or in the links an object has with other objects Shown as a solid arrow Diagrammed with a guard condition and action Event Something that takes place at a certain point in time, triggering a state transition
© 2005 by Prentice Hall Appendix 3-13 State diagram: a model of the states of a single object and the events that cause the object to change from one state to another Guard condition Action A transition is labeled with a guard condition and/or an action, separated with a forward slash /
© 2005 by Prentice Hall Appendix 3-14 Diagramming Substates and Decomposing States A state can be expanded into substates using nested state diagrams, similar to expansion of processes in different levels of DFDs.
© 2005 by Prentice Hall Appendix 3-15 Diagramming Substates and Decomposing States An event can be expanded into using nested state diagrams, and may involve substates and subtransitions and events.
© 2005 by Prentice Hall Appendix 3-16 Dynamic Modeling: Sequence Diagrams A depiction of the interaction among objects during certain periods of time Elements of a sequence diagram Objects: represented by boxes at top of diagram Lifeline: the time during which an object exists Activation: the time period during which an object performs an operation Messages: means by which objects communicate with each other
© 2005 by Prentice Hall Appendix 3-17 Types of Messages in Sequence Diagrams Synchronous message The caller must wait for the receiving object to finish executing the called operation before it can resume execution itself Asynchronous message The caller can resume execution right after sending the message, without waiting for the receiver to complete Simple message A message that transfers control from the sender to the recipient without describing the details of the communication 20.17
© 2005 by Prentice Hall Appendix 3-18 time lifeline activation message object
© 2005 by Prentice Hall Appendix 3-19 Process Modeling: Activity Diagrams Shows the conditional logic for the sequence of system activities needed to accomplish a business process Clearly shows parallel and alternative behaviors Can be used to show the logic of a use case
© 2005 by Prentice Hall Appendix 3-20 Elements of Activity Diagrams Activity: a behavior that an object carries out while in a particular state Transition: a movement from one activity or state to another Branch: a diamond symbol containing a condition whose results provide transitions to different paths of activities Synchronization bar: horizontal or vertical bars denoting parallel or concurrent paths of activities Fork: the beginning of parallel activities Join: the end of parallel activities Swimlanes: columns representing different organizatonal units of the system
© 2005 by Prentice Hall Appendix 3-21 swimlane activity branch synchronization bar
© 2005 by Prentice Hall Appendix 3-22 Analysis Versus Design Start with existing set of analysis model Progressively add technical details Design model must be more detailed than analysis model Component Diagram A diagram that shows the software components or modules and their dependencies Deployment Diagram A diagram that shows how the software components, process and objects are deployed into the physical architecture of the system
© 2005 by Prentice Hall Appendix 3-23
© 2005 by Prentice Hall Appendix 3-24 Summary In this chapter you learned how to: Define events, state transitions, and sequence diagrams. Describe concepts and principles of object- orientation. Describe activities of the different phases of object- oriented development. Compare object-oriented modeling with traditional systems development approaches. Develop dynamic models with state, interaction, and activity diagrams. Model real-world applications with UML.
Chapter 7 Appendix B Object-Oriented Analysis and Design: Activity Diagrams Modern Systems Analysis and Design Sixth Edition Jeffrey A. Hoffer Joey F.
McGraw-Hill/Irwin Copyright © 2007 by The McGraw-Hill Companies, Inc. All rights reserved. Chapter 10 Object-Oriented Analysis and Modeling Using the UML.
© 2005 by Prentice Hall Chapter 9 Structuring System Data Requirements Modern Systems Analysis and Design Fourth Edition Jeffrey A. Hoffer Joey F. George.
March 2011 P00801: E-Business Information Systems 1 Lecture 6 E-Business Modelling with UML Prof. Hong Zhu Department of Computing and Electronics Module.
Chapter 7 – Design and Implementation Lecture 1 1Chapter 7 Design and implementation.
1 Week 2 The Object-Oriented Approach to Requirements.
© 2005 by Prentice Hall Chapter 13 Finalizing Design Specifications Modern Systems Analysis and Design Fourth Edition Jeffrey A. Hoffer Joey F. George.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 7 Slide 1 Chapter 7 System Models.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 12Slide 1 Chapter 12 Object-Oriented Design.
Ch:8 Design Concepts S.W Design should have following quality attribute: –Functionality –Usability –Reliability –Performance –Supportability (extensibility,
Chapter 7 – Design and Implementation 1Chapter 7 Design and implementation Note: These are a modified version of Ch 7 slides available from the authors.
Software Process Modeling with UML and SPEM Chris Armstrong Armstrong Process Group
Impractical for large problems. Problem is true for flat state diagram. Object with n independent attributes require 2 n states for representation.
Lecture 6: Software Design (Part I) Dr Valentina Plekhanova University of Sunderland, UK
Chapter 5 – System Modeling 1Chapter 5 System modeling Software Engineering Ian Sommerville, Software Engineering, 9 th Edition Pearson Education,
هوالعلیم آزمایشگاه مهندسی نرم افزار مدرس : مریم رنجبر 1.
1 UML and Classes, Objects and Relationships  Defining Domain Models Using Class Diagrams.
1 Note content copyright © 2004 Ian Sommerville. NU-specific content copyright © 2004 M. E. Kabay. All rights reserved. Object- Oriented Design IS301 –
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 10Slide 1 Chapter 10 Architectural Design.
Executional Architecture Lecture Conceptual vs execution Conceptual Architecture Execution Architecture Component Connector Domain-level responsibilities.
1 Aspects of IEEE P1471 Viewpoints in Unified Modeling Language (UML) Manzur Ashraf, BRAC University Humayra Binte Ali, Dhaka University Md.Mahfuz Ashraf,
1 Notes content copyright © 2004 Ian Sommerville. NU-specific content copyright © 2004 M. E. Kabay. All rights reserved. System Models IS301 – Software.
© 2010 Bennett, McRobb and Farmer1 Data Flow Diagrams Supplementary material to support Bennett, McRobb and Farmer: Object Oriented Systems Analysis and.
Implementation Architecture Lecture Implementation View (1) “ how the system is built ” Focuses on “ how the system is built ” technological.
Day 2: Hands-on UML Using UML to put MITA to work to solve the immediate process improvement needs of states.
Dive into WebRatio 6 BPM Milano, 09/11/2013 WebRatio Customer Services.
Architectural Design IS301 – Software Engineering Lecture # 14 – M. E. Kabay, PhD, CISSP Dept of Computer Information Systems Norwich University.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 1 Software Processes.
Chapter 6 Architectural Design Slide 1 Chapter 6 Architectural Design.
© 2016 SlidePlayer.com Inc. All rights reserved.