Chapter 2, Modeling with UML, Part 1
|
|
|
- Allan Wilkins
- 7 years ago
- Views:
Transcription
1 Object-Oriented Software Engineering Using UML, Patterns, and Java Chapter 2, Modeling with UML, Part 1 Odds and Ends Reading for this Lecture: Chapter 1 and 2, Bruegge&Dutoit, Object-Oriented Software Engineering Lectures Slides: Will be posted before each lecture. Bernd Bruegge & Allen H. Dutoit!! Object-Oriented Software Engineering: Using UML, Patterns, and Java 2! M. Cossentino! 1!
2 Overview for the Lecture Three ways to deal with complexity Abstraction and Modeling (Abstraction -> Hiding details) Decomposition A complex problem or system is broken down into parts that are easier to conceive Hierarchy a hierarchy can be modelled as a rooted tree Introduction into the UML notation First pass on: Use case diagrams Class diagrams Sequence diagrams Statechart diagrams Activity diagrams Bernd Bruegge & Allen H. Dutoit!! Object-Oriented Software Engineering: Using UML, Patterns, and Java 3! What is the problem with this Drawing? Bernd Bruegge & Allen H. Dutoit!! Object-Oriented Software Engineering: Using UML, Patterns, and Java 4! M. Cossentino! 2!
3 Abstraction Complex systems are hard to understand The phenomena Our short term memory cannot store more than 7+-2 pieces at the same time -> limitation of the brain My Phone Number: Bernd Bruegge & Allen H. Dutoit!! Object-Oriented Software Engineering: Using UML, Patterns, and Java 5! Abstraction Complex systems are hard to understand The phenomena Our short term memory cannot store more than 7+-2 pieces at the same time -> limitation of the brain My Phone Number: Chunking: Group collection of objects to reduce complexity 4 chunks: State-code, Area-code, Local-Prefix, Internal-Nr Bernd Bruegge & Allen H. Dutoit!! Object-Oriented Software Engineering: Using UML, Patterns, and Java 6! M. Cossentino! 3!
4 Abstraction Complex systems are hard to understand The phenomena Our short term memory cannot store more than 7+-2 pieces at the same time -> limitation of the brain My Phone Number: Chunking: Group collection of objects to reduce complexity State-code, Area-code, Local Prefix, Internal-Nr Phone Number! Country-Code! Area-Code! 091! 0039! Bernd Bruegge & Allen H. Dutoit! Local-Prefix! Internal-Nr! ! 261!! Object-Oriented Software Engineering: Using UML, Patterns, and Java 7! Abstraction Abstraction allows us to ignore unessential details Ideas can be expressed by models Bernd Bruegge & Allen H. Dutoit M. Cossentino!!! Object-Oriented Software Engineering: Using UML, Patterns, and Java 8! 4!
5 Models A model is an abstraction of a system A system that no longer exists An existing system A future system to be built. Bernd Bruegge & Allen H. Dutoit!! Object-Oriented Software Engineering: Using UML, Patterns, and Java 9! Why model software? Why model software? Software is getting increasingly more complex Windows XP > 40 millions of lines of code A single programmer cannot manage this amount of code in its entirety. Code is not easily understandable by developers who did not write it We need simpler representations for complex systems Modeling is a mean for dealing with complexity Bernd Bruegge & Allen H. Dutoit M. Cossentino!!! Object-Oriented Software Engineering: Using UML, Patterns, and Java 10! 5!
6 We use Models to describe Software Systems Object model: What is the structure of the system? Functional model: What are the functions of the system? Dynamic model: How does the system react to external events? System Model: Object model + functional model + dynamic model Bernd Bruegge & Allen H. Dutoit!! Object-Oriented Software Engineering: Using UML, Patterns, and Java 11! 2. Technique to deal with Complexity: Decomposition A technique used to master complexity ( divide and conquer ) Two major types of decomposition Functional decomposition Object-oriented decomposition Functional decomposition The system is decomposed into modules Each module is a major function in the application domain Modules can be decomposed into smaller modules. Bernd Bruegge & Allen H. Dutoit!! Object-Oriented Software Engineering: Using UML, Patterns, and Java 12! M. Cossentino! 6!
7 Decomposition (cont d) Object-oriented decomposition The system is decomposed into classes ( objects ) Each class is a major entity in the application domain Classes can be decomposed into smaller classes Object-oriented vs. functional decomposition Which decomposition is the right one? Bernd Bruegge & Allen H. Dutoit!! Object-Oriented Software Engineering: Using UML, Patterns, and Java 13! Functional Decomposition System! Function! Top Level functions! Read Input! Transform! Produce! Output! Level 1 functions! Read Input! Transform! Produce! Output! Level 2 functions! Load R10! Add R1, R10! Machine instructions! Bernd Bruegge & Allen H. Dutoit!! Object-Oriented Software Engineering: Using UML, Patterns, and Java 14! M. Cossentino! 7!
8 Functional Decomposition The functionality is spread all over the system Maintainer must understand the whole system to make a single change to the system Consequence: Source code is hard to understand Source code is complex and impossible to maintain User interface is often awkward and non-intuitive. Bernd Bruegge & Allen H. Dutoit!! Object-Oriented Software Engineering: Using UML, Patterns, and Java 15! Functional Decomposition The functionality is spread all over the system Maintainer must understand the whole system to make a single change to the system Consequence: Source code is hard to understand Source code is complex and impossible to maintain User interface is often awkward and non-intuitive Bernd Bruegge & Allen H. Dutoit!! Object-Oriented Software Engineering: Using UML, Patterns, and Java 16! M. Cossentino! 8!
9 What is This? An Eskimo!! Cave Ellbow Pocket Coat Neck Glove Bernd Bruegge & Allen H. Dutoit!! Object-Oriented Software Engineering: Using UML, Patterns, and Java 17! A Face! Hair Nose Mouth Chin Eye Ear Bernd Bruegge & Allen H. Dutoit!! Object-Oriented Software Engineering: Using UML, Patterns, and Java 18! M. Cossentino! 9!
10 An Eskimo! A Face! Cave Hair Ellbow! Pocket Coat Neck Glove Nose Mouth Chin Eye Ear Bernd Bruegge & Allen H. Dutoit!! Object-Oriented Software Engineering: Using UML, Patterns, and Java 19! Class Identification Basic assumptions: We can find the classes for a new software system: Greenfield Engineering We can identify the classes in an existing system: Reengineering We can create a class-based interface to an existing system: Interface Engineering. Bernd Bruegge & Allen H. Dutoit!! Object-Oriented Software Engineering: Using UML, Patterns, and Java 20! M. Cossentino! 10!
11 3. Hierarchy So far we got abstractions This leads us to classes and objects Chunks Another way to deal with complexity is to provide relationships between these chunks One of the most important relationships is hierarchy 2 special hierarchies "Part-of" hierarchy "Is-kind-of" hierarchy. Bernd Bruegge & Allen H. Dutoit!! Object-Oriented Software Engineering: Using UML, Patterns, and Java 21! Part-of Hierarchy (Aggregation) Computer! I/O Devices! CPU! Memory! Cache! ALU! Program! Counter! Bernd Bruegge & Allen H. Dutoit!! Object-Oriented Software Engineering: Using UML, Patterns, and Java 22! M. Cossentino! 11!
12 Is-Kind-of Hierarchy (Taxonomy) Cell! Muscle Cell! Blood Cell! Nerve Cell! Striate! Smooth! Red! White! Cortical! Pyramidal! Bernd Bruegge & Allen H. Dutoit!! Object-Oriented Software Engineering: Using UML, Patterns, and Java 23! Where are we? Three ways to deal with complexity: Abstraction, Decomposition, Hierarchy Object-oriented decomposition is good Unfortunately, depending on the purpose of the system, different objects can be found How can we do it right? Start with a description of the functionality of a system Then proceed to a description of its structure Ordering of development activities Software lifecycle Bernd Bruegge & Allen H. Dutoit!! Object-Oriented Software Engineering: Using UML, Patterns, and Java 24! M. Cossentino! 12!
13 Systems, Models and Views A model is an abstraction describing a system or a subsystem A view depicts selected aspects of a model A notation is a set of graphical or textual rules for depicting models and views: formal notations, napkin designs System: Airplane Models: Flight simulator Scale model Views: Blueprint of the airplane components Electrical wiring diagram, Fuel system Sound wave created by airplane Bernd Bruegge & Allen H. Dutoit!! Object-Oriented Software Engineering: Using UML, Patterns, and Java 25! Systems, Models and Views ( Napkin Notation) Aircraft" " Flightsimulator" " Fuel System" System Model 2 View 2 View 1 View 3 Model 1 Blueprints" " Electrical " Scale Model" Wiring" " Views and models of a complex system usually overlap Bernd Bruegge & Allen H. Dutoit!! Object-Oriented Software Engineering: Using UML, Patterns, and Java 26! M. Cossentino! 13!
14 Systems, Models and Views (UML Notation) System" *" Described by" Model" Class Diagram! *" Depicted by" View" Airplane: System" Object Diagram! Scale Model:Model" Flight Simulator:Model" Blueprints: View" Fuel System: View" Electrical Wiring: View" Bernd Bruegge & Allen H. Dutoit!! Object-Oriented Software Engineering: Using UML, Patterns, and Java 27! Model-Driven Development 1. Build a platform-independent model of an applications functionality and behavior a) Describe model in modeling notation (UML) b) Convert model into platform-specific model 2. Generate executable from platform-specific model Advantages: Code is generated from model ( mostly ) Portability and interoperability Model Driven Architecture effort: OMG: Object Management Group Bernd Bruegge & Allen H. Dutoit!! Object-Oriented Software Engineering: Using UML, Patterns, and Java 28! M. Cossentino! 14!
15 Model-driven Software Development Reality: A stock exchange lists many companies. Each company is identified by a ticker symbol Analysis results in analysis object model (UML Class Diagram): StockExchange *! *! Company Lists tickersymbol Implementation results in source code (Java): public class StockExchange { private m_company = new Vector(); }; public class Company { private int m_tickersymbol; private Vector m_stockexchange = new Vector(); }; Bernd Bruegge & Allen H. Dutoit!! Object-Oriented Software Engineering: Using UML, Patterns, and Java 29! Application vs Solution Domain Application Domain (Analysis): The environment in which the system is operating Solution Domain (Design, Implementation): The technologies used to build the system Both domains contain abstractions that we can use for the construction of the system model. Bernd Bruegge & Allen H. Dutoit!! Object-Oriented Software Engineering: Using UML, Patterns, and Java 30! M. Cossentino! 15!
16 Object-oriented Modeling Solution Domain " (Phenomena)" Application Domain " (Phenomena)! System Model (Concepts)!(Analysis)! TrafficControl" System Model (Concepts)"(Design)! UML! Package! MapDisplay"! Aircraft" TrafficController" Airport" Bernd Bruegge & Allen H. Dutoit FlightPlan"! Summary " Display" FlightPlanDatabase" TrafficControl"! Object-Oriented Software Engineering: Using UML, Patterns, and Java 31! What is UML? UML (Unified Modeling Language) Nonproprietary standard for modeling software systems, OMG Convergence of notations used in object-oriented methods OMT (James Rumbaugh and collegues) Booch (Grady Booch) OOSE (Ivar Jacobson) Current Version: UML Information at the OMG portal Commercial tools: Rational (IBM),Together (Borland), Visual Architect (business processes, BCD) Open Source tools: ArgoUML, StarUML, Umbrello Commercial and Opensource: PoseidonUML (Gentleware), Astah, Violet Bernd Bruegge & Allen H. Dutoit M. Cossentino!!! Object-Oriented Software Engineering: Using UML, Patterns, and Java 32! 16!
17 UML First Pass Use case diagrams Describe the functional behavior of the system as seen by the user Class diagrams Describe the static structure of the system: Objects, attributes, associations Sequence diagrams Describe the dynamic behavior between objects of the system Statechart diagrams Describe the dynamic behavior of an individual object Activity diagrams Describe the dynamic behavior of a system, in particular the workflow. Bernd Bruegge & Allen H. Dutoit!! Object-Oriented Software Engineering: Using UML, Patterns, and Java 33! UML Core Conventions All UML Diagrams denote graphs of nodes and edges Nodes are entities and drawn as rectangles or ovals Rectangles denote classes or instances Ovals denote functions Names of Classes are not underlined SimpleWatch Firefighter Names of Instances are underlined mywatch:simplewatch! Joe:Firefighter! An edge between two nodes denotes a relationship between the corresponding entities Bernd Bruegge & Allen H. Dutoit!! Object-Oriented Software Engineering: Using UML, Patterns, and Java 34! M. Cossentino! 17!
Menouer Boubekeur, Gregory Provan
Software Requirements Menouer Boubekeur, Gregory Provan Lectures Introduction to UML Introduction to Requirements Analysis Advanced techniques for Requirement Analysis M. Boubekeur, CSL, University College
MSc programme (induction week) Computer Science Department INTRODUCTION TO UML
MSc programme (induction week) Computer Science Department INTRODUCTION TO UML Some of this material is based on Bernd Bruegge and Allen H. Dutoit (2009) Object-Oriented Software Engineering: Using UML,
Chap 1. Introduction to Software Architecture
Chap 1. Introduction to Software Architecture 1. Introduction 2. IEEE Recommended Practice for Architecture Modeling 3. Architecture Description Language: the UML 4. The Rational Unified Process (RUP)
Applying Use Cases to Microcontroller Code Development. Chris Gilbert Cypress Semiconductor
Applying Use Cases to Microcontroller Code Development Chris Gilbert Cypress Semiconductor Agenda Why Use Cases Microcontroller Project Development Use Cases Defined Use Cases Composition General Example
Chapter 13 Configuration Management
Chapter 13 Configuration Management Using UML, Patterns, and Java Object-Oriented Software Engineering Outline of the Lecture Purpose of Software Configuration Management (SCM)! Motivation: Why software
Chapter 1: Introduction
Object-Oriented Software Engineering Using UML, Patterns, and Java Chapter 1: Introduction Objectifs des cours Apprécier les fondammentales du Génie Logiciel: Methodologies Techniques de description et
A UML Introduction Tutorial
A UML Introduction Tutorial 1/27/08 9:55 PM A UML Introduction Tutorial In this tutorial you will learn about the fundamentals of object oriented modelling, the Unified Modelling Language and the software
In this Lecture you will Learn: Systems Development Methodologies. Why Methodology? Why Methodology?
In this Lecture you will Learn: Systems Development Methodologies What a systems development methodology is Why methodologies are used The need for different methodologies The main features of one methodology
Notations enable us to articulate complex ideas succinctly and precisely. In projects
OOSE.book Page 29 Sunday, February 1, 2009 9:29 PM Modeling with UML 2 Every mechanic is familiar with the problem of the part you can t buy because you can t find it because the manufacturer considers
UML basics: An introduction to the Unified Modeling Language
Copyright Rational Software 2003 http://www.therationaledge.com/content/jun_03/f_umlintro_db.jsp UML basics: An introduction to the Unified Modeling Language by Donald Bell IBM Global Services Way back
Lecture 9: Requirements Modelling
A little refresher: What are we modelling? Lecture 9: Requirements Modelling Requirements; Systems; Systems Thinking Role of Modelling in RE Why modelling is important Limitations of modelling Brief overview
Software Lifecycles Models
Software Lifecycles Models Software Engineering Lecture 17 Bernd Bruegge Applied Software Engineering Technische Universitaet Muenchen 1 Outline of Today s Lecture Modeling the software life cycle Sequential
Chapter 1: Introduction
Object-Oriented Sof tware Engi neering Using UM L, Patterns, and Java Chapter 1: Introduction Objectifs des cours Apprécier les fondammentales du Génie Logiciel: Methodologies Techniques de description
UML other structural. diagrams. (Implementation Diagrams UML 1.5) Università di Padova. Facoltà di Scienze MM.FF.NN. Informatica - anno 2009-10
Università di Padova Facoltà di Scienze MM.FF.NN Informatica - anno 2009-10 Corso di Ingegneria del Software - B UML other structural diagrams (Implementation Diagrams UML 1.5) v 2.3 Renato Conte - UML:
CHAPTER_3 SOFTWARE ENGINEERING (PROCESS MODELS)
CHAPTER_3 SOFTWARE ENGINEERING (PROCESS MODELS) Prescriptive Process Model Defines a distinct set of activities, actions, tasks, milestones, and work products that are required to engineer high quality
How To Design Software
The Software Development Life Cycle: An Overview Presented by Maxwell Drew and Dan Kaiser Southwest State University Computer Science Program Last Time The design process and design methods Design strategies
Chapter 11: Integrationand System Testing
Object-Oriented Software Engineering Using UML, Patterns, and Java Chapter 11: Integrationand System Testing Integration Testing Strategy The entire system is viewed as a collection of subsystems (sets
An Introduction to the UML and the Unified Process
3 An Introduction to the UML and the Unified Process 3.1 Introduction This chapter introduces the Unified Modeling Language (UML) notation, its motivation and history. It then presents the Unified Process
Zen of VISIO 2008. Leona Rubin WebTechNY User Group Date: September, 2008
Zen of VISIO 2008 Leona Rubin WebTechNY User Group Date: September, 2008 About the speaker Leona Rubin from New York began her career as a Senior Technical Communicator, Information Designer and Management
Object-oriented design methodologies
Object-oriented design methodologies An object-oriented methodology is defined as the system of principles and procedures applied to object-oriented software development. Five years ago, there was no standard
Towards an Integration of Business Process Modeling and Object-Oriented Software Development
Towards an Integration of Business Process Modeling and Object-Oriented Software Development Peter Loos, Peter Fettke Chemnitz Univeristy of Technology, Chemnitz, Germany {loos peter.fettke}@isym.tu-chemnitz.de
Chapter 13 Configuration Management
Object-Oriented Software Engineering Using UML, Patterns, and Java Chapter 13 Configuration Management Outline of the Lecture Purpose of Software Configuration Management (SCM)! Motivation: Why software
The Software Process. The Unified Process (Cont.) The Unified Process (Cont.)
The Software Process Xiaojun Qi 1 The Unified Process Until recently, three of the most successful object-oriented methodologies were Booch smethod Jacobson s Objectory Rumbaugh s OMT (Object Modeling
Object Oriented Programming. Risk Management
Section V: Object Oriented Programming Risk Management In theory, there is no difference between theory and practice. But, in practice, there is. - Jan van de Snepscheut 427 Chapter 21: Unified Modeling
Designing Real-Time and Embedded Systems with the COMET/UML method
By Hassan Gomaa, Department of Information and Software Engineering, George Mason University. Designing Real-Time and Embedded Systems with the COMET/UML method Most object-oriented analysis and design
Use-Case Analysis. ! What is it? ! From where did it come? ! Now part of UML
Use-Case Analysis Use-Case Analysis! What is it?! An informal, user-friendly, technique useful for functional requirements analysis and specification! From where did it come?! Ivar Jacobson, a Swedish
UML SUPPORTED SOFTWARE DESIGN
UML SUPPORTED SOFTWARE DESIGN Darko Gvozdanović, Saša Dešić, Darko Huljenić Ericsson Nikola Tesla d.d., Krapinska 45, HR-0000 Zagreb, Croatia, tel.: +385 365 3889, faks: +385 365 3548, e-mail: darko.gvozdanovic@etk.ericsson.se
Unit I Page No. 1 System Development Object Basics Development Life Cycle Methodologies Patterns Frameworks Unified Approach UML
Unit I Page No. 1 System Development Object Basics Development Life Cycle Methodologies Patterns Frameworks Unified Approach UML System Development (SD) : - o SD refers to all activities that go into producing
Software Development Process Models and their Impacts on Requirements Engineering Organizational Requirements Engineering
Software Development Process Models and their Impacts on Requirements Engineering Organizational Requirements Engineering Prof. Dr. Armin B. Cremers Sascha Alda Overview Phases during Software Development
Contents. Introduction and System Engineering 1. Introduction 2. Software Process and Methodology 16. System Engineering 53
Preface xvi Part I Introduction and System Engineering 1 Chapter 1 Introduction 2 1.1 What Is Software Engineering? 2 1.2 Why Software Engineering? 3 1.3 Software Life-Cycle Activities 4 1.3.1 Software
Software Engineering. System Models. Based on Software Engineering, 7 th Edition by Ian Sommerville
Software Engineering System Models Based on Software Engineering, 7 th Edition by Ian Sommerville Objectives To explain why the context of a system should be modeled as part of the RE process To describe
Comparison between Traditional Approach and Object-Oriented Approach in Software Engineering Development
Comparison between Traditional Approach and Object-Oriented Approach in Software Engineering Development Nabil Mohammed Ali Munassar 1 PhD Student 3 rd year of Computer Science & Engineering Jawaharlal
Development Methodologies. Types of Methodologies. Example Methodologies. Dr. James A. Bednar. Dr. David Robertson
Development Methodologies Development Methodologies Dr. James A. Bednar jbednar@inf.ed.ac.uk http://homepages.inf.ed.ac.uk/jbednar Dr. David Robertson dr@inf.ed.ac.uk http://www.inf.ed.ac.uk/ssp/members/dave.htm
Using Use Cases for requirements capture. Pete McBreen. 1998 McBreen.Consulting
Using Use Cases for requirements capture Pete McBreen 1998 McBreen.Consulting petemcbreen@acm.org All rights reserved. You have permission to copy and distribute the document as long as you make no changes
Lecture Overview. Object-Oriented Software Engineering: Using UML, Patterns, Java, and Software Development Processes. Prof. Dr.
COM 401 Software Engineering Lecture Overview Object-Oriented Software Engineering: Using UML, Patterns, Java, and Software Development Processes Prof. Dr. Halûk Gümüşkaya haluk.gumuskaya@gediz.edu.tr
SOFTWARE PROCESS MODELS
SOFTWARE PROCESS MODELS Slide 1 Software Process Models Process model (Life-cycle model) - steps through which the product progresses Requirements phase Specification phase Design phase Implementation
Information Systems Analysis and Design CSC340. 2004 John Mylopoulos. Software Architectures -- 1. Information Systems Analysis and Design CSC340
XIX. Software Architectures Software Architectures UML Packages Client- vs Peer-to-Peer Horizontal Layers and Vertical Partitions 3-Tier and 4-Tier Architectures The Model-View-Controller Architecture
How To Develop Software
Software Engineering Prof. N.L. Sarda Computer Science & Engineering Indian Institute of Technology, Bombay Lecture-4 Overview of Phases (Part - II) We studied the problem definition phase, with which
Design and UML Class Diagrams
Design and UML Class Diagrams 1 Suggested reading: Practical UML: A hands on introduction for developers http://dn.codegear.com/article/31863 UML DistilledCh. 3, by M. Fowler How do people draw / write
Section C. Requirements Elicitation
This work is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike License. Your use of this material constitutes acceptance of that license and the conditions of use of materials on this
Programming Language Constructs as Basis for Software Architectures
Programming Language Constructs as Basis for Software Architectures 1 From individual parts to components In the 50s: Machine/Assembler programs: bound to specific hardware In the 60s-70s: Higher programming
Modeling Web Applications Using Java And XML Related Technologies
Modeling Web Applications Using Java And XML Related Technologies Sam Chung Computing & Stware Systems Institute Technology University Washington Tacoma Tacoma, WA 98402. USA chungsa@u.washington.edu Yun-Sik
Universiti Teknologi MARA. Requirement Analysis Using UML Approach for Research Management System (RMS)
C^tJ O19OO(^'J.Tfi^'i- Universiti Teknologi MARA Requirement Analysis Using UML Approach for Research Management System (RMS) Enamul Hasan Bin Rusly Thesis submitted in fulfillment of the requirements
UML Tutorial: Part 1 -- Class Diagrams.
UML Tutorial: Part 1 -- Class Diagrams. Robert C. Martin My next several columns will be a running tutorial of UML. The 1.0 version of UML was released on the 13th of January, 1997. The 1.1 release should
Designing a Semantic Repository
Designing a Semantic Repository Integrating architectures for reuse and integration Overview Cory Casanave Cory-c (at) modeldriven.org ModelDriven.org May 2007 The Semantic Metadata infrastructure will
Masters of Science in Software & Information Systems
Masters of Science in Software & Information Systems To be developed and delivered in conjunction with Regis University, School for Professional Studies Object Oriented Design Table of Contents January
The value of modeling
The value of modeling Level: Introductory Gary Cernosek, Marketing Manager, IBM Rational Eric Naiburg, Group Market Manager Desktop Products, IBM Rational 15 Nov 2004 from The Rational Edge: This article
Development models. 1 Introduction. 2 Analyzing development models. R. Kuiper and E.J. Luit
Development models R. Kuiper and E.J. Luit 1 Introduction We reconsider the classical development models: the Waterfall Model [Bo76], the V-Model [Ro86], the Spiral Model [Bo88], together with the further
Object Oriented Design
Object Oriented Design Kenneth M. Anderson Lecture 20 CSCI 5828: Foundations of Software Engineering OO Design 1 Object-Oriented Design Traditional procedural systems separate data and procedures, and
Algorithms, Flowcharts & Program Design. ComPro
Algorithms, Flowcharts & Program Design ComPro Definition Algorithm: o sequence of steps to be performed in order to solve a problem by the computer. Flowchart: o graphical or symbolic representation of
The Unified Software Development Process
The Unified Software Development Process Technieche Universal Darmstadt FACHBEREICH IN-FORMAHK BLIOTHEK Ivar Jacobson Grady Booch James Rumbaugh Rational Software Corporation tnventar-nsr.: Sachgebiete:
Chapter 13: Program Development and Programming Languages
Understanding Computers Today and Tomorrow 12 th Edition Chapter 13: Program Development and Programming Languages Learning Objectives Understand the differences between structured programming, object-oriented
Questions? Assignment. Techniques for Gathering Requirements. Gathering and Analysing Requirements
Questions? Assignment Why is proper project management important? What is goal of domain analysis? What is the difference between functional and non- functional requirements? Why is it important for requirements
IRA 423/08. Designing the SRT control software: Notes to the UML schemes. Andrea Orlati 1 Simona Righini 2
Designing the SRT control software: Notes to the UML schemes Andrea Orlati 1 Simona Righini 2 1 - I.N.A.F. Istituto di Radioastronomia. 2 Dip. Astronomia - Università degli Studi di Bologna. Dicembre 2008
ISSUES OF STRUCTURED VS. OBJECT-ORIENTED METHODOLOGY OF SYSTEMS ANALYSIS AND DESIGN
ISSUES OF STRUCTURED VS. OBJECT-ORIENTED METHODOLOGY OF SYSTEMS ANALYSIS AND DESIGN Mohammad A. Rob, University of Houston-Clear Lake, rob@cl.uh.edu ABSTRACT In recent years, there has been a surge of
Software Design Models, Tools & Processes *
Software Design Models, Tools & Processes * Lecture 1: Software Design and Software Development Process Cecilia Mascolo * Thanks to Alan Blackwell and Jim Arlow for le7ng me use some of their slides. About
Information systems modelling UML and service description languages
Internet Engineering Tomasz Babczyński, Zofia Kruczkiewicz Tomasz Kubik Information systems modelling UML and service description languages Student Contact Hours: 25.02.2015- Location: 325 C3 room 25.03.2015:
Business Modeling with UML
Business Modeling with UML Hans-Erik Eriksson and Magnus Penker, Open Training Hans-Erik In order to keep up and be competitive, all companies Ericsson is and enterprises must assess the quality of their
3C05: Unified Software Development Process
3C05: Unified Software Development Process 1 Unit 5: Unified Software Development Process Objectives: Introduce the main concepts of iterative and incremental development Discuss the main USDP phases 2
An Introduction to Software Visualization. Visualization. Types of Software Visualization. Course Overview
An Introduction to Software Dr. Jonathan I. Maletic Software DevelopMent Laboratory Department of Computer Science Kent State University Course Overview Introductory Lectures Software visualization
How To Design An Information System
Information system for production and mounting of plastic windows MARCEL, MELIŠ Slovak University of Technology - Faculty of Material Sciences and Technology in Trnava, Paulínska 16 street, Trnava, 917
Collated Food Requirements. Received orders. Resolved orders. 4 Check for discrepancies * Unmatched orders
Introduction to Data Flow Diagrams What are Data Flow Diagrams? Data Flow Diagrams (DFDs) model that perspective of the system that is most readily understood by users the flow of information around the
Software development life cycle. Software Engineering - II ITNP92 - Object Oriented Software Design. Requirements. Requirements. Dr Andrea Bracciali
Software development life cycle Software life cycle: Software Engineering - II ITNP92 - Object Oriented Software Design Dr Andrea Bracciali Module Co-ordinator 4B86 abb@cs.stir.ac.uk Spring 2014 (elicitation)
Architecture. Reda Bendraou reda.bendraou{{@}}lip6.fr http://pagesperso-systeme.lip6.fr/reda.bendraou/
Architecture Reda Bendraou reda.bendraou{{@}}lip6.fr http://pagesperso-systeme.lip6.fr/reda.bendraou/ Some slides were adapted from L. Osterweil, B. Meyer, and P. Müller material Reda Bendraou LI386-S1
feature model-driven development Test-Driven Modeling for Model-Driven Development
feature model-driven development Test-Driven Modeling for Model-Driven Development Yuefeng Zhang, Motorola Extreme Programming is a code-centric, lightweight software development process. 1 3 One of XP
Rose/Architect: a tool to visualize architecture
Published in the Proceedings of the 32 nd Annual Hawaii International Conference on Systems Sciences (HICSS 99) Rose/Architect: a tool to visualize architecture Alexander Egyed University of Southern California
Decomposition into Parts. Software Engineering, Lecture 4. Data and Function Cohesion. Allocation of Functions and Data. Component Interfaces
Software Engineering, Lecture 4 Decomposition into suitable parts Cross cutting concerns Design patterns I will also give an example scenario that you are supposed to analyse and make synthesis from The
CPS122 Lecture: State and Activity Diagrams in UML
CPS122 Lecture: State and Activity Diagrams in UML Objectives: last revised February 14, 2012 1. To show how to create and read State Diagrams 2. To introduce UML Activity Diagrams Materials: 1. Demonstration
How To Draw A Cell Phone Into A Cellphone In Unminimal Diagram (Uml)
UML Tutorial: Collaboration Diagrams Robert C. Martin Engineering Notebook Column Nov/Dec, 97 In this column we will explore UML collaboration diagrams. We will investigate how they are drawn, how they
The most suitable system methodology for the proposed system is drawn out.
3.0 Methodology 3.1 Introduction In this chapter, five software development life cycle models are compared and discussed briefly. The most suitable system methodology for the proposed system is drawn out.
Applying 4+1 View Architecture with UML 2. White Paper
Applying 4+1 View Architecture with UML 2 White Paper Copyright 2007 FCGSS, all rights reserved. www.fcgss.com Introduction Unified Modeling Language (UML) has been available since 1997, and UML 2 was
2. Analysis, Design and Implementation
2. Subject/Topic/Focus: Software Production Process Summary: Software Crisis Software as a Product: From Individual Programs to Complete Application Systems Software Development: Goals, Tasks, Actors,
3D Animation of Java Program Execution for Teaching Object Oriented Concepts
3D Animation of Java Program Execution for Teaching Object Oriented Concepts Tim Storer September 23, 2006 Abstract The successful teaching of the object oriented programming paradigm has been identified
The BPM to UML activity diagram transformation using XSLT
The BPM to UML activity diagram transformation using XSLT Ondřej Macek 1 and Karel Richta 1,2 1 Department of Computer Science and Engineering, Faculty of Electrical Engineering, Czech Technical University,
Principles and Software Realization of a Multimedia Course on Theoretical Electrical Engineering Based on Enterprise Technology
SERBIAN JOURNAL OF ELECTRICAL ENGINEERING Vol. 1, No. 1, November 2003, 81-87 Principles and Software Realization of a Multimedia Course on Theoretical Electrical Engineering Based on Enterprise Technology
Software Project Management and UML
Software Project Management and UML Ali Bigdelou Computer Aided Medical Procedures (CAMP), Technische Universität München, Germany Outline Intro to Software Project Management Project Requirements Specification
Software Design Document (SDD) Template
(SDD) Template Software design is a process by which the software requirements are translated into a representation of software components, interfaces, and data necessary for the implementation phase.
KWIC Exercise. 6/18/2007 2007, Spencer Rugaber 1
KWIC Exercise On a subsequent slide, you will be given the description of a simple program for which you will be asked to devise two architectures. For the purposes of this exercise, you should imagine
Introduction. UML = Unified Modeling Language It is a standardized visual modeling language.
UML 1 Introduction UML = Unified Modeling Language It is a standardized visual modeling language. Primarily intended for modeling software systems. Also used for business modeling. UML evolved from earlier
Meta-Model specification V2 D602.012
PROPRIETARY RIGHTS STATEMENT THIS DOCUMENT CONTAINS INFORMATION, WHICH IS PROPRIETARY TO THE CRYSTAL CONSORTIUM. NEITHER THIS DOCUMENT NOR THE INFORMATION CONTAINED HEREIN SHALL BE USED, DUPLICATED OR
Software Development Methodologies
Software Development Methodologies Lecturer: Raman Ramsin Lecture 5 Integrated Object-Oriented Methodologies: OPM and Catalysis 1 Object Process Methodology (OPM) Introduced by Dori in 1995 Primarily intended
Types of UML Diagram. UML Diagrams 140703-OOAD. Computer Engineering Sem -IV
140703-OOAD Computer Engineering Sem -IV Introduction to UML - UML Unified Modeling Language diagram is designed to let developers and customers view a software system from a different perspective and
F-16 Modular Mission Computer Application Software
F-16 Modular Mission Computer Application Software Achieving Cross-Platform Compatibility with Increased Productivity and Quality using the OMG s Model Driven Architecture Lauren E. Clark Chief Engineer
Design of Network Educating Information System Based on Use Cases Driven Shenwei Wang 1 & Min Guo 2
International Symposium on Social Science (ISSS 2015) Design of Network Educating Information System Based on Use Cases Driven Shenwei Wang 1 & Min Guo 2 1 College of Electronic and Control Engineering,
Chapter 6. Data-Flow Diagrams
Chapter 6. Data-Flow Diagrams Table of Contents Objectives... 1 Introduction to data-flow diagrams... 2 What are data-flow diagrams?... 2 An example data-flow diagram... 2 The benefits of data-flow diagrams...
INTRODUCTION TO BUSINESS PROCESS MODELING NOTATION BPMN 1.2 AND BPMN 2.0
INTRODUCTION TO BUSINESS PROCESS MODELING NOTATION BPMN 1.2 AND BPMN 2.0 Email: {goliva,gerosa}@ime.usp.br / Twitter: @golivax Agenda 2 Introduction to Business Processes BPMN 1.2 Introduction Elements
Manage Software Development in LabVIEW with Professional Tools
Manage Software Development in LabVIEW with Professional Tools Introduction For many years, National Instruments LabVIEW software has been known as an easy-to-use development tool for building data acquisition
I219 Software Design Methodology
I219 Software Design Methodology JAIST Master s Program Fall 2014 Nguyen Van Vu nvu@fit.hcmus.edu.vn Topics Course Introduction Objectives and Scope Evaluation Policies Content and Schedule Basic Concepts
A SYSTEMATIC APPROACH FOR COMPONENT-BASED SOFTWARE DEVELOPMENT
A SYSTEMATIC APPROACH FOR COMPONENT-BASED SOFTWARE DEVELOPMENT Cléver Ricardo Guareis de Farias, Marten van Sinderen and Luís Ferreira Pires Centre for Telematics and Information Technology (CTIT) PO Box
Classical Software Life Cycle Models
Classical Software Life Cycle Models SWEN 301 Trimester 1, 2015 Lecturer: Dr Hui Ma Engineering and Computer Science Lecture slides make use of material provided on the textbook's companion website Motivation
Eclipse BPMN Modeler Introducing Intalio Designer
Eclipse BPMN Modeler Introducing Intalio Designer Arnaud Blandin Ismael Ghalimi Hugues Malphettes Intalio Inc, EMEA Manager Intalio Inc, CEO Intalio Inc, Lead Developer 6 rue du conseil general 1205 Geneva
6. Software Lifecycle Models. A software lifecycle model is a standardised format for planning organising, and running a new development project.
6. Software Lifecycle Models A software lifecycle model is a standardised format for planning organising, and running a new development project. Hundreds of different kinds of models are known and used.
Page 1. Outline of the Lecture. What is Software Configuration Management? Why Software Configuration Management?
Books: Software Configuration Management 1. B. Bruegge and A. H. Dutoit, Object-Oriented Software Engineering: Using UML, Patterns, and Java (Chapter 13) Outline of the Lecture Purpose of Software Configuration
CS 40 Computing for the Web
CS 40 Computing for the Web Art Lee January 20, 2015 Announcements Course web on Sakai Homework assignments submit them on Sakai Email me the survey: See the Announcements page on the course web for instructions
Day 3: Modeling and ERP Reference Architectures
Day 3: Modeling and ERP Reference Architectures CIS Department Professor Duane Truex III Air Force Mentor-Protégé Enterprise Reference Architectures Ronald E. Giachetti, Ph.D. Associate Professor Industrial
Software Engineering and Scientific Computing
Software Engineering and Scientific Computing Barbara Paech, Hanna Valtokari Institute of Computer Science Im Neuenheimer Feld 326 69120 Heidelberg, Germany http://se.ifi.uni-heidelberg.de paech@informatik.uni-heidelberg.de
Object Oriented Analysis and Design - Advantages of UML
(Refer Slide Time: 00:45) Management Information System Prof. B. Mahanty Department of Industrial Engineering & Management Indian Institute of Technology, Kharagpur Lecture - 27 OOAD - I (Refer Slide Time:
PATTERN-ORIENTED ARCHITECTURE FOR WEB APPLICATIONS
PATTERN-ORIENTED ARCHITECTURE FOR WEB APPLICATIONS M. Taleb, A. Seffah Human-Centred Software Engineering Group Concordia University, Montreal, Quebec, Canada Phone: +1 (514) 848 2424 ext 7165 and/or ext
Computer Organization
Basics Machine, software, and program design JPC and JWD 2002 McGraw-Hill, Inc. Computer Organization CPU - central processing unit Where decisions are made, computations are performed, and input/output
Design and UML Class Diagrams. Suggested reading: Practical UML: A hands on introduction for developers http://dn.codegear.
Design and UML Class Diagrams Suggested reading: Practical UML: A hands on introduction for developers http://dn.codegear.com/article/31863 UML Distilled Ch. 3, by M. Fowler 1 Big questions What is UML?