SOFTWARE DESIGN AND ARCHITECTURE LECTURE 21. Review ANALYSIS PHASE (OBJECT ORIENTED DESIGN) Functional Modeling – Use case Diagram Description.

Slides:



Advertisements
Similar presentations
Activity Diagrams in UML. Definition Activity diagrams represent the dynamics of the system. They are flow charts that are used to show the workflow of.
Advertisements

Activity Diagrams. Recap Activity Diagrams – When to use? – Where? – Nodes – Edges – More to come …. 2.
© 2006 ITT Educational Services Inc. SE350 System Analysis for Software Engineers: Unit 9 Slide 1 Appendix 3 Object-Oriented Analysis and Design.
Information System Design IT60105
Extending the Requirements Model - techniques for detailing use cases
7M701 1 Activity Diagram. 7M701 2 Example 7M701 3 Activity Diagram: what is it? Describes activities and flows of data or decisions between activities.
University of Toronto Department of Computer Science © Steve Easterbrook. This presentation is available free for non-commercial use with attribution.
Requirements Analysis Activity Diagrams b511.ppt © Copyright De Montfort University 2000 All Rights Reserved INFO2005 Requirements Analysis.
Activity Diagrams Derived from several techniques: Event diagrams of Jim Odell SDL state modeling techniques Workflow modeling Petri nets Especially useful.
COMP1007 Intro to Requirements Analysis © Copyright De Montfort University 2002 All Rights Reserved COMP1007 Introduction to Requirements Analysis Lecture.
1 Business Models Modeling. 2 Why Model the Business Business modeling is a technique to help answer critical questions, such as: What do the workers.
Chapter 10: Architectural Design
TK2023 Object-Oriented Software Engineering CHAPTER 6 SYSTEM SEQUENCE DIAGRAMS.
Basic Concepts The Unified Modeling Language (UML) SYSC System Analysis and Design.
Karolina Muszyńska Based on: S. Wrycza, B. Marcinkowski, K. Wyrzykowski „Język UML 2.0 w modelowaniu SI”
Software Engineering EKT 420. What is Activity Diagram Activity diagrams are graphical representations of workflows of stepwise activities and actions.
Chapter 10 Architectural Design
Activity Diagram.
Chapter 5 – System Modeling
CS 325: Software Engineering March 3, 2015 Activity Modeling for Transformational Systems Trtansformational Systems UML Activity Diagrams.
CIT UPES | Sept 2013 | Unified Modeling Language - UML.
UML A CTIVITY D IAGRAMS 1 Dr. Hoang Huu Hanh, OST – Hue University hanh-at-hueuni.edu.vn.
Chapter 14. Activity Modeling for Transformational Systems
Requirement Engineering. Review of Last Lecture Problems with requirement Requirement Engineering –Inception (Set of Questions) –Elicitation (Collaborative.
Chapter 5 – System Modeling
UML The Unified Modeling Language A Practical Introduction Al-Ayham Saleh Aleppo University
Chapter 4 – Requirements Engineering Lecture 3 1Chapter 4 Requirements engineering.
SOFTWARE DESIGN AND ARCHITECTURE LECTURE 20. Review Software Requirements Requirements Engineering Process.
Copyright 2002 Prentice-Hall, Inc. Chapter 2 Object-Oriented Analysis and Design Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey.
Interaction Models (2): Sequence Diagrams Extracted from textbook: Object Oriented Modeling and Design with UML M. Blaha, J. Rumbaugh 1.
Systems Analysis and Design in a Changing World, 3rd Edition
1 Devon M. Simmonds University of North Carolina, Wilmington CSC450 Software Engineering WorkFlow Modeling with Activity Diagrams.
Software Engineering Prof. Ing. Ivo Vondrak, CSc. Dept. of Computer Science Technical University of Ostrava
Copyright © 2013 Curt Hill UML Unified Modeling Language.
© 2007 Pearson Education, Inc. Publishing as Pearson Addison-Wesley 1 UML Activity Diagrams.
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.
1 Technical & Business Writing (ENG-715) Muhammad Bilal Bashir UIIT, Rawalpindi.
Lecture 14 22/10/15. The Object-Oriented Analysis and Design  Process of progressively developing representation of a system component (or object) through.
Chapter 5 System Modeling (1/2) Yonsei University 2 nd Semester, 2015 Sanghyun Park.
21/1/ Analysis - Model of real-world situation - What ? System Design - Overall architecture (sub-systems) Object Design - Refinement of Design.
 Activity diagram is basically a flow chart to represent the flow from one activity to another activity.
Activity Diagramming by Andrzej Rosolski Stanisław Gliniewicz.
UML ACTIVITY DIAGRAM 1. Recap Formal Use Case diagram UML notation for use cases Examples 2.
Activity & Class Modeling Labs Discussion p3 T120B pavasario sem.
Interaction Models (2): Activity Diagrams Extracted from textbook: Object Oriented Modeling and Design with UML M. Blaha, J. Rumbaugh.
PowerPoint Presentation for Dennis, Wixom, & Tegarden Systems Analysis and Design with UML, 5th Edition Copyright © 2015 John Wiley & Sons, Inc. All rights.
Chapter 4 – System Modeling Lecture 1 1Chapter 5 System modeling.
Chapter 5 – System Modeling Lecture 1 1Chapter 5 System modeling.
Chapter 5 – System Modeling
CompSci 280 S Introduction to Software Development
Systems Analysis and Design in a Changing World, Fourth Edition
Business Process and Functional Modeling
Activity Diagrams.
Chapter 5 System modeling
Chapter 5 – System Modeling
Unified Modeling Language
Activity Diagram.
Activity and State Transition Diagram
Activity Diagram.
System Modeling Chapter 4
Business System Development
Software Engineering Chapter 5 (Part 3) System Modeling Dr.Doaa Sami.
Use Case Modeling - techniques for detailing use cases
CS310 Software Engineering Dr.Doaa Sami
Activity diagram It supports visual representation of sequences of actions that target a certain result. May be built for one or many use cases or for.
Software Engineering System Modeling Chapter 5 (Part 1) Dr.Doaa Sami
Chapter 4 System Modeling.
Object-Oriented Analysis & Design
Chapter 14. Activity Modeling for Transformational Systems
Presentation transcript:

SOFTWARE DESIGN AND ARCHITECTURE LECTURE 21

Review ANALYSIS PHASE (OBJECT ORIENTED DESIGN) Functional Modeling – Use case Diagram Description

Outline ANALYSIS PHASE (OBJECT ORIENTED DESIGN) Functional Modeling – Activity Diagrams

System Modeling System modeling is the process of developing abstract models of a system, with each model presenting a different view or perspective of that system. System modeling has generally come to mean representing the system using some kind of graphical notation, which is now almost always based on notations in the Unified Modeling Language (UML).

System Modeling Models are used – during the requirements engineering process to help derive the requirements for a system, – during the design process to describe the system to engineers implementing the system and – after implementation to document the system’s structure and operation.

Analysis Models At an early stage in the specification of a system, we need to decide on the system boundaries. – This involves working with system stakeholders to decide what functionality should be included in the system and what is provided by the system’s environment. We need to decide that automated support for some business processes should be implemented but – others should be manual processes or supported by different systems.

Modeling System Interactions All systems involve interaction of some kind. – user interaction, which involves user inputs and outputs, interaction between the system being developed Modeling user interaction is important as it helps to identify user requirements.

Modeling System interactions For modeling system interactions we can use – Use case modeling, – which is mostly used to model interactions between a system and external actors (users or other systems).

ACTIVITY DIAGRAM

Activity Diagram Activity diagrams are for modeling business processes, workflows, data flows, and complex algorithms. Based on data flow models – a graphical representation (with a Directed Graph) of how data move around an information system. An activity diagram shows sequential and parallel activities in a process.

Activity Diagram Activity diagrams are the object-oriented equivalent of flow charts and data-flow diagrams from structured development Activity diagrams describe the workflow behavior of a system Activity diagram illustrates the dynamic nature of a system by modeling the flow of control from activity to activity

When to Use Activity Diagrams ? To explore the logic of – a complex operation – a complex business rule – a single use case – several use cases – a business process – software processes Useful for showing workflow and parallel processing

Example

Scenario Customer places an order The sales assistant receives the order and processes it. After successful order processing the order is filled. The customer makes payment and the order is delivered/shipped to him by sales rep.

Example 1:

Actions The fundamental unit of executable functionality in an activity The execution of an action represents some transformations or processes in the modeled system (creating objects, setting attribute values, linking objects together, invoking user-defined behaviours, etc.) 16 Description of the action behaviour

Control nodes – initial nodes 17 In an activity the flow starts in initial nodes, that return the control immediately along their outgoing edges

Control nodes – decision nodes 18 Route the flow to one of the outgoing edges

Control nodes – merge nodes 19 Bring together multiple alternate flows All controls and data arriving at a merge node are immediately passed to the outgoing edge

Control nodes – fork nodes 20 Fork nodes split flows into multiple concurrent flows

Control nodes – join nodes 21 Join nodes synchronize multiple flows

Control nodes – final nodes 22 Final node: – the activity is terminated when the first token arrives

Appointment management Usecase: Get patient information If new patient, then create a record and proceed to payment arrangements Else proceed to payment arrangements Create a new appointment OR change an existing appointment OR remove an old appointment.

Appointment management Get patient information If new patient, then create a record and proceed to payment arrangements Else proceed to payment arrangements Create a new appointment OR change an existing appointment OR remove an old appointment.

Patient Information System

Swim lanes, which represent responsibilities of one or more objects for actions within an overall activity; that is, they divide the activity states into groups and assign these groups to objects that must perform the activities. Swim Lane 28

Activity Diagrams: Swim lanes 29 Open Incident Allocate Resources Coordinate Resources Document Incident Archive Incident Dispatcher FieldOfficer Actions may be grouped into swim lanes to denote the object or subsystem that implements the actions.

Example-2

Receive Order Check Order Item Dispatch Order Authorize Payment Cancel Order Add Remainder to Stock [succeeded] [failed] Assign to Order Receive Supply Choose Outstanding Order Items Assign to Order * for each chosen order item [in stock] *for each order item [need to reorder] Reorder item [all outstanding order items filled] [stock assigned to all order items and payment authorized] Order Processing accounts Stock Manager vertical lines are used to separate “swimlanes” to show which activities are handled by which part of the system 32

Summary Analysis Level Design – Activity Diagrams