Business System Development

Slides:



Advertisements
Similar presentations
© 2005 by Prentice Hall Appendix 3 Object-Oriented Analysis and Design Modern Systems Analysis and Design Fourth Edition Jeffrey A. Hoffer Joey F. George.
Advertisements

Object-Oriented Software Engineering Visual OO Analysis and Design
UML (Sequence Diagrams, Collaboration and State Chart Diagrams) Presentation By - SANDEEP REDDY CHEEDEPUDI (Student No: ) - VISHNU CHANDRADAS (Student.
© 2006 ITT Educational Services Inc. SE350 System Analysis for Software Engineers: Unit 9 Slide 1 Appendix 3 Object-Oriented Analysis and Design.
Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall A.1.
Systems Analysis and Design 8th Edition
Object-Oriented Analysis and Design
CS 425/625 Software Engineering System Models
Sequence Diagram. What is Sequence Diagram?  Sequence Diagram is a dynamic model of a use case, showing the interaction among classes during a specified.
Copyright 2004 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Second Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Appendix.
Modern Systems Analysis and Design Fifth Edition Jeffrey A
SE-565 Software System Requirements More UML Diagrams.
BPMN By Hosein Bitaraf Software Engineering. Business Process Model and Notation (BPMN) is a graphical representation for specifying business processes.
Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 8: Modelling Interactions and Behaviour.
CIT UPES | Sept 2013 | Unified Modeling Language - UML.
State diagrams Interaction diagrams –Sequence diagrams –Collaboration diagrams Object orientation Part 4: Dynamic Modeling.
Copyright 2001 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Appendix A Object-Oriented.
Copyright 2002 Prentice-Hall, Inc. Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 20 Object-Oriented.
Copyright 2002 Prentice-Hall, Inc. Chapter 2 Object-Oriented Analysis and Design Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey.
Systems Analysis & Design 7 th Edition Chapter 5.
Systems Analysis and Design 8 th Edition Chapter 6 Object Modeling.
UML diagrams What is UML UML diagrams –Static modeoing –Dynamic modeling 1.
9-1 © Prentice Hall, 2004 Chapter 9: Analysis Classes Object-Oriented Systems Analysis and Design Joey F. George, Dinesh Batra, Joseph S. Valacich, Jeffrey.
9-1 © Prentice Hall, 2007 Chapter 9: Analysis Classes Object-Oriented Systems Analysis and Design Joey F. George, Dinesh Batra, Joseph S. Valacich, Jeffrey.
Lecture 8 Object-Oriented Analysis and Design 20.1 COSC4406: Software Engineering.
Sequence diagram in UML Martin Palkovik. Sequence diagram  It is a graphic representation of system operations based on chronology - a time sequence.
Course Instructor: Kashif Ihsan 1. Chapter # 3 2.
© 2008 Prentice Hall, Ovidiu Noran Lecture 7b 1 Modelling OO Logic Requirements: Sequence Diagrams and Activity Diagrams (Textbook Chapter 8, Appendix)
Introduction to UML CS A470. What is UML? Unified Modeling Language –OMG Standard, Object Management Group –Based on work from Booch, Rumbaugh, Jacobson.
Chapter 11 Activity Diagrams. 2 “Activity diagrams are a technique to describe procedural logic, business processes, and work flows” - M. Fowler An activity.
CS212: Object Oriented Analysis and Design Lecture 34: UML Activity and Collaboration diagram.
Systems Analysis and Design in a Changing World, Fourth Edition
1 Technical & Business Writing (ENG-715) Muhammad Bilal Bashir UIIT, Rawalpindi.
SOFTWARE DESIGN AND ARCHITECTURE LECTURE 26. Review UML behavioral Diagrams – Sequence diagram.
Lecture 14 22/10/15. The Object-Oriented Analysis and Design  Process of progressively developing representation of a system component (or object) through.
7-1 © Prentice Hall, 2007 Topic 7: Analysis Classes Object-Oriented Systems Analysis and Design Joey F. George, Dinesh Batra, Joseph S. Valacich, Jeffrey.
Chapter 3: Introducing the UML
Analysis Classes. What Is an Analysis Class?  A class that represents initial data and behavior requirements, and whose software and hardware-oriented.
Copyright © 2009 Pearson Education, Inc. Publishing as Prentice Hall Appendix A Object-Oriented Analysis and Design A.1.
Appendix Object-Oriented Analysis and Design: Use Cases and Sequence Diagrams Modern Systems Analysis and Design Fifth Edition Jeffrey A. Hoffer Joey F.
1 7 Systems Analysis and Design in a Changing World, 2 nd Edition, Satzinger, Jackson, & Burd Chapter 7 The Object-Oriented Approach to Requirements.
Unified Modeling Language. What is UML? Standard language for specifying, visualizing, constructing, and documenting the artifacts of software systems,
Systems Analysis and Design in a Changing World, Fourth Edition
Appendix 3 Object-Oriented Analysis and Design
Analysis Classes Unit 5.
Object-oriented and Structured System Models
UML Diagrams By Daniel Damaris Novarianto S..
Chapter 1: Introduction to Systems Analysis and Design
Business System Development
Course Outcomes of Object Oriented Modeling Design (17630,C604)
Object-Oriented Analysis and Design
Unified Modeling Language
Activity and State Transition Diagram
Visit for more Learning Resources
UML Diagrams Jung Woo.
Activity Diagrams Activity diagrams describe the workflow behavior of a system.  The diagrams describe the state of activities by showing the sequence.
UML dynamic Modeling (Behavior Diagram)
System models October 5, 2005.
Process Modeling: Activity/Swimlane Diagrams
Chapter 20 Object-Oriented Analysis and Design
CIS 375 Bruce R. Maxim UM-Dearborn
Appendix A Object-Oriented Analysis and Design
BPMN - Business Process Modeling Notations
Chapter 1: Introduction to Systems Analysis and Design
Chapter 5.
CIS 375 Bruce R. Maxim UM-Dearborn
Appendix A Object-Oriented Analysis and Design
Appendix A Object-Oriented Analysis and Design
Appendix 3 Object-Oriented Analysis and Design
Chapter 1: Introduction to Systems Analysis and Design
Presentation transcript:

Business System Development CSC581

Lecture 28 Object-Oriented Analysis and Design

Summary of the previous lecture In previous lecture, we : Discussed management skills required for success as a systems analyst. Discussed interpersonal skills required for success as a systems analyst. Described the systems analysis profession

Outlines We today’s lecture we will: 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

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

Object oriented cycle is like an onion, evolving from abstract to detailed, from external qualities to system architecture and algorithms.

Object-Oriented Deliverables and Outcomes The ability to tackle more challenging problem domains Improved communication among users, analysts, designers, and programmers Increased consistency among analysis, design, and programming activities Explicit representation of commonality among system components Robust systems Reusability of analysis, design, and programming results Increased consistency among the models developed during object-oriented analysis, design, and programming

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

Use Cases Revisited A depiction of a system’s behavior or functionality under various conditions as the system responds to requests from users Full functioning for a specific business purpose

Class Diagrams Revisited Features: Objects and classes Encapsulation of attributes and operations Polymorphism Inheritance Aggregation and composition

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

State Diagrams State State Transition Event 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

Guard condition Action Guard condition A transition is labeled with a guard condition and/or an action, separated with a forward slash / 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

Diagramming Sub-states and Decomposing States A state can be expanded into substates using nested state diagrams, similar to expansion of processes in different levels of DFDs.

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

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

object time lifeline message activation

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

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

branch activity synchronization bar swimlane

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

Summary of today’s lecture In this lecture we talked about : Defined events, state transitions, and sequence diagrams. Described concepts and principles of object-orientation. Described activities of the different phases of object-oriented development. Compared object-oriented modeling with traditional systems development approaches. Developed dynamic models with state, interaction, and activity diagrams. Modelled real-world applications with UML.

Overview of the next lecture In next lecture, we will: We will consider few more case studies and further explore/practice the concepts of system development which we have learnt in the previous lectures.

The End