2 2009/10 Object Oriented Technology 1 Topic 2: Introduction to Object-Oriented Approach Reference: u Ch.16 Current Trends in System Development (Satzinger:

Slides:



Advertisements
Similar presentations
Objectives Explain the purpose and various phases of the traditional systems development life cycle (SDLC) Explain when to use an adaptive approach to.
Advertisements

Chapter 4 - Object-Oriented Analysis and Design in a Nutshell1 Chapter 4 Object-Oriented Analysis and Design in a Nutshell.
Object-Oriented Analysis and Design
Object-Oriented Analysis and Design
L4-1-S1 UML Overview © M.E. Fayad SJSU -- CmpE Software Architectures Dr. M.E. Fayad, Professor Computer Engineering Department, Room #283I.
SE 555 Software Requirements & Specification1 Use-Case Modeling: Overview and Context.
Rational Worldwide Software Symposium
1/31 CS 426 Senior Projects Chapter 1: What is UML? Chapter 2: What is UP? [Arlow and Neustadt, 2005] January 22, 2009.
03/12/2001 © Bennett, McRobb and Farmer Development Process Based on Chapter 5 of Bennett, McRobb and Farmer: Object Oriented Systems Analysis and.
Objectives Explain the purpose and various phases of the traditional systems development life cycle (SDLC) Explain when to use an adaptive approach to.
1 CS 426 Senior Projects Chapter 1: What is UML? Chapter 2: What is UP? [Arlow and Neustadt, 2002] January 26, 2006.
Chapter 6 View Alignment Techniques and Method Customization (Part I) Object-Oriented Technology From Diagram to Code with Visual Paradigm for UML Curtis.
Basic Concepts The Unified Modeling Language (UML) SYSC System Analysis and Design.
PowerPoint Presentation for Dennis, Wixom, & Tegarden Systems Analysis and Design with UML, 3rd Edition Copyright © 2009 John Wiley & Sons, Inc. All rights.
What is UML? What is UP? [Arlow and Neustadt, 2005] January 23, 2014
UML - Development Process 1 Software Development Process Using UML (2)
2Object-Oriented Analysis and Design with the Unified Process Objectives  Explain the purpose and various phases of the traditional systems development.
CIT UPES | Sept 2013 | Unified Modeling Language - UML.
Chapter 1: Introduction to Systems Analysis and Design
Topic 1: Approaches to System Development
Introduction to UML By: Prof. Aiman Hanna Department of Computer Science, Concordia University, Montreal, Canada.
Slide 1 UML Review Chapter 2: Introduction to Object-Oriented Systems Analysis and Design with the Unified Modeling Language, Version 2.0 Alan Dennis,
Unified Modeling Language, Version 2.0
Lecture 3: Visual Modeling & UML 1. 2 Copyright © 1997 by Rational Software Corporation Computer System Business Process Order Item Ship via “ Modeling.
Software development process ธนวัฒน์ แซ่ เอียบ. The development process Process –set of rules which define how a development project. Methodology and.
Software Engineering Prof. Ing. Ivo Vondrak, CSc. Dept. of Computer Science Technical University of Ostrava
Unified Modeling Language* Keng Siau University of Nebraska-Lincoln *Adapted from “Software Architecture and the UML” by Grady Booch.
1 UML Distilled 3e by Martin Fowler Chapter 1 Introduction to UML.
ניתוח מערכות מידע 1 Unified Modeling Language (UML) § § The Unified Modeling Language (UML) is the industry-standard language for: Specifying, Visualizing,
1 COMP 350: Object Oriented Analysis and Design Lecture 1Introduction References: Craig Larman Chapter 1.
L6-S1 UML Overview 2003 SJSU -- CmpE Advanced Object-Oriented Analysis & Design Dr. M.E. Fayad, Professor Computer Engineering Department, Room #283I College.
© 2010 Bennett, McRobb and Farmer1 Development Process Based on Chapter 5 Bennett, McRobb and Farmer Object Oriented Systems Analysis and Design Using.
1 Introduction to UML. 2 What is UML? UML is an acronym for Unified Modeling Language. Unified –Combines the best from existing object- oriented software.
TAL7011 – Lecture 4 UML for Architecture Modeling.
Object-Oriented Analysis and Design. Lesson 1: Introduction to Software Engineering.
UML as a Specification Language for Embedded Systems. By, Mir Ahmed Ali, Asst. Professor, ECM department, SNIST. By, Prof. Narsiah sir, Director of School.
Slide 1 Systems Analysis and Design With UML 2.0 An Object-Oriented Approach, Second Edition Chapter 2: Introduction to Object-Oriented Systems Analysis.
Introduction to OOAD and the UML
Introduction to OOAD & Rational Rose cyt. 2 Outline RUP OOAD Rational Rose.
Lecture 9-1 : Intro. to UML (Unified Modeling Language)
Slide 1 Systems Analysis and Design With UML 2.0 An Object-Oriented Approach, Second Edition Chapter 2: Introduction to Object-Oriented Systems Analysis.
The principles of an object oriented software development process Week 04 1.
1 Technical & Business Writing (ENG-715) Muhammad Bilal Bashir UIIT, Rawalpindi.
Week 04 Object Oriented Analysis and Designing. What is a model? A model is quicker and easier to build A model can be used in simulations, to learn more.
1 Unified Modeling Language, Version 2.0 Chapter 2.
Rational Unified Process Fundamentals Best Practices of Software Engineering Rational Unified Process Fundamentals Best Practices of Software Engineering.
Unified Process Software Development Darren Roback/Ravali Kallem CMIS Fall 2009.
Basic Characteristics of Object-Oriented Systems
UML. Model An abstract representation of a system. Types of model 1.Use case model 2.Domain model 3.Analysis object model 4.Implementation model 5.Test.
Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 14 Slide 1 Object-Oriented Design.
Review of Definitions Software life cycle: –Set of activities and their relationships to each other to support the development of a software system Software.
Slide 1 Unified Modeling Language, Version 2.0 Object-Oriented SAD.
Development Process Based on Chapter 5 Bennett, McRobb and Farmer
Introduction to UML.
Chapter 1: Introduction to Systems Analysis and Design
UNIT 1.
What is UML? What is UP? [Arlow and Neustadt, 2005] October 5, 2017
Systems Analysis and Design With UML 2
University of Central Florida COP 3330 Object Oriented Programming
UML: Unified modeling language
Introduction to Object Oriented Analysis, Design and Unified Modeling Language (UML) Shanika Karunasekera.
Introduction to Software Engineering
Object Oriented Analysis and Design
Rational Worldwide Software Symposium
Unified Modeling Language
Rational Worldwide Software Symposium
Chapter 1: Introduction to Systems Analysis and Design
Rational Worldwide Software Symposium
Uml diagrams In ooad.
Chapter 1: Introduction to Systems Analysis and Design
Presentation transcript:

2 2009/10 Object Oriented Technology 1 Topic 2: Introduction to Object-Oriented Approach Reference: u Ch.16 Current Trends in System Development (Satzinger: Systems Analysis & Design in a Changing World, 4 th Edition) u Appendix B (C. Tsang: Object-Oriented Technology from Diagram to Code with Visual Paradigm for UML)

2 2009/10 Object Oriented Technology 2 Learning Objectives 1. Describe the features and characteristics of the Unified Process (UP) 2. Recognize features of the Unified Modeling Language (UML)

2 2009/10 Object Oriented Technology 3 1. The Unified Process (UP) u Object-oriented system development methodology (system development process) u Offered by Rational / IBM, UP developed by Booch, Rumbaugh, and Jacobson u UP is an iterative, evolutionary and adaptive method u Project will be use-case driven and modeled using UML

2 2009/10 Object Oriented Technology The Unified Process Life Cycle u UP life cycle l Includes 4 phases which consist of iterations l Iterations are “mini-projects” u Inception – develop and refine system vision u Elaboration – define requirements and design and implement core architecture u Construction – continue design and implementation of routine, less risky parts u Transition – move the system into operational mode

2 2009/10 Object Oriented Technology 5 The Unified Process Life Cycle (Figure 16-1)

2 2009/10 Object Oriented Technology UP Phases and Objectives (Figure 16-2)

2 2009/10 Object Oriented Technology The UP Disciplines u UP defines disciplines used within each phase u Discipline – set of functionally related development activities u Each iteration includes activities from all disciplines u Activities in each discipline produce artifacts – models, documents, source code, and executables u Learning CIS/MIS means learning techniques from these disciplines

2 2009/10 Object Oriented Technology The UP Disciplines (continued) u Six main UP development disciplines l Business modeling, requirements, design, implementation, testing, and deployment u Three additional support disciplines l Project management, configuration and change management, and environment

2 2009/10 Object Oriented Technology 9 UP Disciplines Used in Varying Amounts in Each Iteration (Figure 16-3)

2 2009/10 Object Oriented Technology 10 UP Life Cycle Model Showing Phases, Iterations, and Disciplines (Figure 16-4)

2 2009/10 Object Oriented Technology 11 Iterative and Evolutionary One iteration Requirements Design Implementation& Test&Integration &More Design Final Integration &System Test Requirements Design 3weeks(for example) The system grows incrementally. Feedback from iteration N leads to refinement and adaptation of the requirements and design in iteration N+1. Iterations are fixed in length,ortimeboxed. Time Implementation& Test&Integration &More Design Final Integration &System Test

2 2009/10 Object Oriented Technology The Unified Modeling Language (UML) u is a set of diagrammatic techniques, specifically tailored for object-oriented development, u has become an industry standard for modeling object-oriented systems u has been approved as a development standard by the Object Management Group

2 2009/10 Object Oriented Technology The UML diagrams u Use case diagram l Captures the requirements of the system being developed l How the system interacts with the users u Class diagram l Used to describe the types of objects and their relationships by providing a static and structural view of a system in terms of classes and relationships u Interaction diagram l Two types of interaction diagrams: the sequence diagram and the collaboration diagram l How the objects interact to achieve the functionality of a use case

2 2009/10 Object Oriented Technology The UML diagrams (continued) u Activity diagram l Used to model workflow and computational flow l Used to elaborate the execution flow of a use case u State diagram, or state machine diagram l Represents state machines from the perspective of states and transitions, describing all the possible states that a particular object can get into and how the object’s state changes as a result of events that affect the object u Component diagram l Show the different software components of the system and the dependencies between them

2 2009/10 Object Oriented Technology The UML diagrams (continued) u Package diagram l A package contains UML diagrams and may contain other packages, Related diagrams are usually grouped in a single package u Deployment diagram l Used to describe the runtime mapping of software components to the hardware resources (nodes)

2 2009/10 Object Oriented Technology 16 Relationships between the UML models Activity Diagram Use Case Interaction Diagram Class Diagram State Diagram elaborated by realized by Textual Analysis realized by described by use summarize

2 2009/10 Object Oriented Technology 17 Summary u UP is an Object-oriented system development methodology u UP projects are modeled using UML u UML specifies a variety of diagrams to capture the static, dynamic and behavioral aspects of a system