SOFTWARE ENGINEERING UML FUNDAMENTALS. Saulius Ragaišis.
|
|
- Marjorie Lynch
- 5 years ago
- Views:
Transcription
1 SOFTWARE ENGINEERING UML FUNDAMENTALS Saulius Ragaišis
2 Information source Slides are prepared on the basis of Bernd Oestereich, Developing Software with UML: Object- Oriented Analysis and Design in Practice (2 nd edition). Addison-Wesley Professional, ISBN X
3 UML The Unified Modeling Language (UML) is a language and notation for specification, construction, visualization, and documentation of models of software systems. The Object Management Group (OMG) has declared UML as its standard. UML is a language and notation for modeling, but it is intentionally not a method.
4 What is UML? A language for capturing and expressing knowledge A tool for system discovery and development A tool for visual development modeling A set of well-founded guidelines A milestone generator A popular (therefore supported) tool
5 What UML is not! A visual programming language or environment A database specification tool A development process A panacea A quality guarantee
6 Types of diagrams Use case diagram: shows actors, use cases, and their relationships. Class diagram: shows classes and their relationships with each other. Implementation diagrams: Component diagram: shows components and their relationships. Deployment diagram: shows components, nodes, and their relationships.
7 Types of diagrams (2) Behavior diagrams: Activity diagram, object flow diagram: shows activities, object states, states, state transitions, and events. Collaboration diagram: shows objects and their relationships, including their spatially structured message exchange. Sequence diagram: shows objects and their relationships, including their chronologically structured message exchange. State diagram: shows states, state transitions, and events.
8 UML diagram philosophy Any UML diagram: Depicts concepts as symbols Depicts relationships between concepts as directed or undirected arcs (lines) Depicts names as labels within or next to symbols and lines
9 UML relationships
10 USE CASE DIAGRAMS
11 Use case diagram Definition: A use case diagram shows the relationships between actors and use cases. Example:
12 Notation A use case diagram includes: diagram name; a set of use cases which are represented as individual ellipses; a set of actors and events that are involved (actors). The use cases are joined by straight lines with the classes involved. A frame around the use cases symbolizes the system boundaries. The names of the use cases can either be placed within the ellipse or underneath it.
13 Use case. Definition A use case describes a set of activities of a system from the point of view of its actors which lead to a perceptible outcome for the actors. A use case is always initiated by an actor. In all other respects, a use case is a complete, indivisible description. Related terms: scenario, script.
14 Use case. Rules At least one actor is involved in each use case. Each use case has a domain-specific trigger. Each use case produces a relevant domain specific result for the actors, i.e. a result of commercial value.
15 Use case. Types Essential use case: is described in an abstract, generalized, simplified, implementation-independent, and technology-neutral manner. It concentrates on the actual domain-specific intention and therefore represents the shortest and most abstract form of use case description. Normal (pragmatic) use case: is a standard use case that, in contrast to an essential use case, may also contain non-domain-specific basic conditions and assumptions. Secondary use cases: are use cases that do not possess the aforementioned required properties of a domain trigger and a domain result but which have been produced by a functional subdivision of existing use cases, i.e. for example by the application of include and extend relationships.
16 Actor. Definition An actor is an entity located outside the system that is involved in the interaction with the system described in a use case. An actor may be a person (e.g. a user) but may also be another technical system (e.g. SAP), the operating system, etc. Related terms: stakeholder, event, external system, dialog, boundary, control, entity.
17 Actor. Description An actor is not the person involved but his role in the context of the use case. Actors possess associations to use cases if they are involved in the processes described in the use cases. Actors can also have relationships to each other. Relationships could be generalization/specialization, in order to represent a hierarchical structure and abstraction between them. Actors do not have to be people, e.g.: other (technical) systems involved in the use case; external system involved in the use case that triggers a time event.
18 Actor. Notation textual stereotype visual stereotype mixed representation
19 Use case description A use case is graphically represented by an ellipsis that bears the name of the use case. Each use case has a unique name. Use cases may additionally be numbered for quick identification. For each ellipse, there is a text that describes the use case in more detail. Such texts may be informal, but some content-related structuring is recommended.
20 Use case description. Example
21 Use case relationships «include» The «include» relationship is used to denote that another use case occurs inside a use case. «extend» The «extend» relationship, on the other hand, is used to show that in certain circumstances or at a specific point (the so-called extension point) a use case is extended with another use case. Specialization/generalization Generalization allows sub use cases to inherit behavior and semantics from super use cases, in analogy with the generalization relationship between classes.
22 Use case relationships. Notation
23 CLASS DIAGRAMS
24 Classes. Definition A class is the definition of the attributes, the operations, and the semantics of a set of objects. All objects in a class correspond to that definition. Related terms: type, object factory.
25 Classes. Notation
26 Template classes
27 Abstract classes
28 Example of class hierarchy with abstract superclass
29 Responsibilities
30 Interface classes
31 Constraints-Object Constraint Language (OCL)
32 Subsystems
33 Packages
34 Generalization, Specialization
35 Example of inheritance
36 Multiple inheritance
37 Association
38 Aggregation A diamond symbolizes an aggregation
39 Composition
40 Dependency relations
41 Refinement/Realization relations
42 BEHAVIORAL DIAGRAMS
43 Activity diagram. Definition Activity diagrams describe the procedural possibilities of a system with the aid of activities. An activity diagram is a special form of a state diagram, which mostly or exclusively contains activities. An activity is a state with an internal action and one (or more) outgoing transition which automatically follows the termination of the internal activity. An activity is a single step in a procedure. Activity diagrams can be subdivided into responsibility domains, the so called swim lanes, which allow activities to be assigned to elements or structures.
44 Activity diagram. Notation
45 Activity diagram. Notation (2)
46 Activity diagram. Notation (3)
47 Activity diagram. Example
48 Collaboration diagram. Definition A collaboration diagram shows a set of interactions between selected objects in a specific, limited situation (context), focusing on the relations between the objects and their topography. Basically, a collaboration diagram shows the same facts as a sequence diagram but from another perspective. The collaboration diagram emphasizes the objects and their cooperation with each other; between them, selected messages are shown.
49 Collaboration diagram. Notation Between the objects, association lines are drawn on which the messages are noted. A small arrow indicates the direction of the message from sender to receiver. If arguments are passed together with the message, they are listed too. Possible responses can be shown as well; they are put in front of the actual message in the form response:= message().
50 Collaboration diagram. Notation (2)
51 Collaboration diagram. Notation (3) The chronological sequence of the messages is indicated by sequence number. The individual elements have the following meaning: Predecessor condition: This is an enumeration of the sequence numbers of other messages that need to have been sent before this message may be sent. This allows synchronization to be achieved. The sequence numbers are listed separated by commas and terminated with a slash /.
52 Collaboration diagram. Notation (4) Sequence expression: To show the sequence of messages, they are numbered in ascending order. If new messages are sent within an operation which interprets a received message, they are given a new subsequence number separated by a dot. Example: message follows message Both were sent during interpretation of message 2.1. Iterations, i.e. repeated sending of a message: are marked with an asterisk *. To describe the iteration in more detail an appropriate indication in pseudo-code can be added in square brackets. Example: 1.2.*[i := 1..n]:
53 Collaboration diagram. Notation (5) Response: The response supplied by a message can be given a name. This name can then be used as an argument in other messages. Its scope is the same as that of local variables inside the message to be sent and may indeed be such a variable. It may also be the name of an object attribute. Message name (parameter list): Name of the message, usually homonymous with a corresponding operation that interprets the message. The signature of the operation is specified.
54 Collaboration diagram. Notation (6) The following stereotypes can be indicated: «association» The object relation is based on an association, aggregation, or composition. This is the default; the specification can therefore be omitted. «global» The receiving object is global. «local» The receiving object is local in the sending operation (and thus «new» or «transient»). «parameter» The receiving object is a parameter in the sending operation. «self» The receiving object is the sending object.
55 Collaboration diagram. Notation (7) Various arrow shapes have been defined for specifying particular synchronization conditions: With a synchronous message, the sender waits until the receiver has accepted the message. Asynchronous messages end up in the waiting queue of the receiver. The sender is not interested in when the receiver accepts the message.
56 Collaboration diagram. Example
57 Sequence diagram. Definition A sequence shows a series of messages exchanged by a selected set of objects in a temporally limited situation, with an emphasis on the chronological course of events. Objects are merely shown by vertical lifelines. This highlights the chronological sequence of the messages. Time runs from top to bottom.
58 Sequence diagram. Notation
59 Sequence diagram. Notation (2)
60 Sequence diagram. Example
61 State diagram. Definition A state diagram shows a sequence of states an object can assume during its lifetime, together with the stimuli that cause changes of state. A state diagram describes a hypothetical machine (finite automaton) which at any given time is found in a set of finite states. It consists of: a finite, non-empty set of states; a finite, non-empty set of events; state transitions; an initial state; a set of final states.
62 State diagram. States
63 State diagram. Substates
64 State diagram. Events and transitions
65 State diagram. Example
66 IMPLEMENTATION DIAGRAMS
67 Component diagram. Definition A component is an executable piece of software with its own identity and well defined interfaces. A distinction should be made between component definitions (e.g. person ) and component instances (e.g. Gabby Goldsmith ). Component diagrams show the interrelations between components.
68 Component diagram. Definition (2) In practice, UML components are very similar to packages: they define boundaries, and group and structure a set of individual elements. Components may have interfaces. Packages and components can be used for very similar purposes. While packages represent a more logical view, components emphasize the physical perspective.
69 Deployment diagram. Definition A node is an object which is physically present at runtime and has computing power or memory, such as computers (processors), devices, and the like. Deployment diagrams show which components and objects run on which node (processes, computers) how they are configured and which communication relations exist between them.
70 Deployment diagram. Notation Components are represented by bricks. Nodes that communicate with each other, i.e. have the appropriate relations, are connected by association lines. Optionally, components or runtime objects (processes) may be placed inside the bricks. Interfaces and dependency relations between these elements are also allowed. Nodes are identified either by their name alone or by a name followed by a specification of the node type. Instead of ordinary bricks, more colorful clip-art could be used.
71 Deployment diagram. Example
72 QUESTIONS?
Software Service Engineering
Software Service Engineering Lecture 4: Unified Modeling Language Doctor Guangyu Gao Some contents and notes selected from Fowler, M. UML Distilled, 3rd edition. Addison-Wesley Unified Modeling Language
More informationSOFTWARE DESIGN COSC 4353 / Dr. Raj Singh
SOFTWARE DESIGN COSC 4353 / 6353 Dr. Raj Singh UML - History 2 The Unified Modeling Language (UML) is a general purpose modeling language designed to provide a standard way to visualize the design of a
More informationUnified Modeling Language (UML) and Modeling
LECTURE-11 Unified Modeling Language (UML) and Modeling UML is a graphical notation useful for OO analysis and design Allows representing various aspects of the system Various notations are used to build
More informationUML Fundamental. OutLine. NetFusion Tech. Co., Ltd. Jack Lee. Use-case diagram Class diagram Sequence diagram
UML Fundamental NetFusion Tech. Co., Ltd. Jack Lee 2008/4/7 1 Use-case diagram Class diagram Sequence diagram OutLine Communication diagram State machine Activity diagram 2 1 What is UML? Unified Modeling
More informationUML 2.0 UML 2.0. Scott Uk-Jin Lee. Division of Computer Science, College of Computing Hanyang University ERICA Campus
UML 2.0 Division of Computer Science, College of Computing Hanyang University ERICA Campus Introduction to UML 2.0 UML Unified Modeling Language Visual language for specifying, constructing and documenting
More informationCS 370 REVIEW: UML Diagrams D R. M I C H A E L J. R E A L E F A L L
CS 370 REVIEW: UML Diagrams D R. M I C H A E L J. R E A L E F A L L 2 0 1 5 Introduction UML Unified Modeling Language Very well recognized specification for modeling architectures, use cases, etc. UML
More informationWhat is a Class Diagram? A diagram that shows a set of classes, interfaces, and collaborations and their relationships
Class Diagram What is a Class Diagram? A diagram that shows a set of classes, interfaces, and collaborations and their relationships Why do we need Class Diagram? Focus on the conceptual and specification
More informationWhat is a Class Diagram? Class Diagram. Why do we need Class Diagram? Class - Notation. Class - Semantic 04/11/51
What is a Class Diagram? Class Diagram A diagram that shows a set of classes, interfaces, and collaborations and their relationships Why do we need Class Diagram? Focus on the conceptual and specification
More informationOMG Modeling Glossary B
OMG Modeling Glossary B This glossary defines the terms that are used to describe the Unified Modeling Language (UML) and the Meta Object Facility (MOF). In addition to UML and MOF specific terminology,
More informationChapter 10. Object-Oriented Analysis and Modeling Using the UML. McGraw-Hill/Irwin
Chapter 10 Object-Oriented Analysis and Modeling Using the UML McGraw-Hill/Irwin Copyright 2007 by The McGraw-Hill Companies, Inc. All rights reserved. Objectives 10-2 Define object modeling and explain
More informationPractical UML - A Hands-On Introduction for Developers
Practical UML - A Hands-On Introduction for Developers By: Randy Miller (http://gp.codegear.com/authors/edit/661.aspx) Abstract: This tutorial provides a quick introduction to the Unified Modeling Language
More informationObject-Oriented Systems Analysis and Design Using UML
10 Object-Oriented Systems Analysis and Design Using UML Systems Analysis and Design, 8e Kendall & Kendall Copyright 2011 Pearson Education, Inc. Publishing as Prentice Hall Learning Objectives Understand
More informationOral Questions. Unit-1 Concepts. Oral Question/Assignment/Gate Question with Answer
Unit-1 Concepts Oral Question/Assignment/Gate Question with Answer The Meta-Object Facility (MOF) is an Object Management Group (OMG) standard for model-driven engineering Object Management Group (OMG)
More informationObject-Oriented and Classical Software Engineering
Slide 16.1 Object-Oriented and Classical Software Engineering Seventh Edition, WCB/McGraw-Hill, 2007 Stephen R. Schach srs@vuse.vanderbilt.edu CHAPTER 16 Slide 16.2 MORE ON UML 1 Chapter Overview Slide
More informationUML REFERENCE SHEETS. 2013, 2014 Michael Marking; all rights reserved, including moral rights. Web site:
UML Reference Sheets 2013, 2014 Michael Marking; all rights reserved, including moral rights. Web site: http://www.tatanka.com/ Revision Information This document was last revised 2014.03.02. The current
More informationCourse "Softwaretechnik" Book Chapter 2 Modeling with UML
Course "Softwaretechnik" Book Chapter 2 Modeling with UML Lutz Prechelt, Bernd Bruegge, Allen H. Dutoit Freie Universität Berlin, Institut für Informatik http://www.inf.fu-berlin.de/inst/ag-se/ Modeling,
More informationBasic Structural Modeling. Copyright Joey Paquet,
Basic Structural Modeling Copyright Joey Paquet, 2000 1 Part I Classes Copyright Joey Paquet, 2000 2 Classes Description of a set of objects sharing the same attributes, operations and semantics Abstraction
More informationCOSC 3351 Software Design. An Introduction to UML (I)
COSC 3351 Software Design An Introduction to UML (I) This lecture contains material from: http://wps.prenhall.com/esm_pfleeger_softengtp_2 http://sunset.usc.edu/classes/cs577a_2000/lectures/05/ec-05.ppt
More informationEnterprise Architect. User Guide Series. UML Models. Author: Sparx Systems. Date: 30/06/2017. Version: 1.0 CREATED WITH
Enterprise Architect User Guide Series UML Models Author: Sparx Systems Date: 30/06/2017 Version: 1.0 CREATED WITH Table of Contents UML Models UML Diagrams UML Structural Models Class Diagram Composite
More informationPractical UML : A Hands-On Introduction for Developers
Borland.com Borland Developer Network Borland Support Center Borland University Worldwide Sites Login My Account Help Search Practical UML : A Hands-On Introduction for Developers - by Randy Miller Rating:
More informationUnified Modeling Language (UML)
Unified Modeling Language (UML) Troy Mockenhaupt Chi-Hang ( Alex) Lin Pejman ( PJ ) Yedidsion Overview Definition History Behavior Diagrams Interaction Diagrams Structural Diagrams Tools Effect on Software
More informationUML Diagrams MagicDraw UML Diagrams
In software development, the diagram is the equivalent of a blueprint. To meet the various needs of many parties, we often need several different blueprints of the same system. Furthermore, every system
More informationAli Khan < Project Name > Design Document. Version 1.0. Group Id: S1. Supervisor Name: Sir.
< Project Name > Design Document Version 1.0 Group Id: S1. Supervisor Name: Sir. Revision History Date Version Description Author Table of Contents 1. Introduction of Design Document 2. Entity Relationship
More informationObjectives Pre-Test Questions Introduction Collaboration Diagrams Flow of Events and Special Requirements...
10 Analysis Modeling M MAJOR A J O R T TOPICSO P I C S Objectives... 144 Pre-Test Questions...144 Introduction... 145 Collaboration Diagrams... 145 Flow of Events and Special Requirements... 151 Class-Responsibility-Collaboration
More informationSOFTWARE MODELING AND DESIGN. UML, Use Cases, Patterns, and. Software Architectures. Ki Cambridge UNIVERSITY PRESS. Hassan Gomaa
SOFTWARE MODELING AND DESIGN UML, Use Cases, Patterns, and Software Architectures Hassan Gomaa George Mason University, Fairfax, Virginia Ki Cambridge UNIVERSITY PRESS Contents Preface P"U
More informationSoftware Engineering Lab Manual
Kingdom of Saudi Arabia Ministry Education Prince Sattam Bin Abdulaziz University College of Computer Engineering and Sciences Department of Computer Science Software Engineering Lab Manual 1 Background:-
More informationUML Component Diagrams A.Y 2018/2019
UML Component Diagrams A.Y 2018/2019 Component diagrams Component diagrams are integral to building your software system. Drawn out with UML diagramming software, they help your team understand the structure
More informationUnit Wise Questions. Unit-1 Concepts
Unit Wise Questions Unit-1 Concepts Q1. What is UML? Ans. Unified Modelling Language. It is a Industry standard graphical language for modelling and hence visualizing a blue print of all the aspects of
More informationIntroduction to Software Engineering. 6. Modeling Behaviour
Introduction to Software Engineering 6. Modeling Behaviour Roadmap > Use Case Diagrams > Sequence Diagrams > Collaboration (Communication) Diagrams > Activity Diagrams > Statechart Diagrams Nested statecharts
More informationLABORATORY 1 REVISION
UTCN Computer Science Department Software Design 2012/2013 LABORATORY 1 REVISION ================================================================== I. UML Revision This section focuses on reviewing the
More informationEnterprise Architect - UML Dictionary
Enterprise Architect is an intuitive, flexible and powerful UML analysis and design tool for building robust and maintainable software. This dictionary explains the way in which Enterprise Architect represents
More informationInteractions A link message
Interactions An interaction is a behavior that is composed of a set of messages exchanged among a set of objects within a context to accomplish a purpose. A message specifies the communication between
More informationExercise Unit 2: Modeling Paradigms - RT-UML. UML: The Unified Modeling Language. Statecharts. RT-UML in AnyLogic
Exercise Unit 2: Modeling Paradigms - RT-UML UML: The Unified Modeling Language Statecharts RT-UML in AnyLogic Simulation and Modeling I Modeling with RT-UML 1 RT-UML: UML Unified Modeling Language a mix
More informationIntroduction to Software Engineering. 5. Modeling Objects and Classes
Introduction to Software Engineering 5. Modeling Objects and Classes Roadmap > UML Overview > Classes, attributes and operations > UML Lines and Arrows > Parameterized Classes, Interfaces and Utilities
More informationObject Oriented Modeling
Overview UML Unified Modeling Language What is Modeling? What is UML? A brief history of UML Understanding the basics of UML UML diagrams UML Modeling tools 2 Modeling Object Oriented Modeling Describing
More informationUNIT I. 3. Write a short notes on process view of 4+1 architecture. 4. Why is object-oriented approach superior to procedural approach?
Department: Information Technology Questions Bank Class: B.E. (I.T) Prof. Bhujbal Dnyaneshwar K. Subject: Object Oriented Modeling & Design dnyanesh.bhujbal11@gmail.com ------------------------------------------------------------------------------------------------------------
More informationWhat s Next. INF 117 Project in Software Engineering. Lecture Notes -Spring Quarter, Michele Rousseau Set 6 System Architecture, UML
What s Next INF 117 Project in Software Engineering Lecture Notes -Spring Quarter, 2008 Michele Rousseau Set 6 System Architecture, UML Set 6 2 Announcements kreqs should be complete Except minor changes
More information7 The proposed domain specific language: operational level
7 The proposed domain specific language: operational level In our methodology, a scenario corresponds to the specification of concrete activities in the pervasive mobile game, including interactions among
More informationObject Oriented Design. Program Design. Analysis Phase. Part 2. Analysis Design Implementation. Functional Specification
Object Oriented Design Part 2 Analysis Design Implementation Program Design Analysis Phase Functional Specification Completely defines tasks to be solved Free from internal contradictions Readable both
More informationObjectives. Explain the purpose and objectives of objectoriented. Develop design class diagrams
Objectives Explain the purpose and objectives of objectoriented design Develop design class diagrams Develop interaction diagrams based on the principles of object responsibility and use case controllers
More informationLecture 17: (Architecture V)
Lecture 17: (Architecture V) Software System Design and Implementation ITCS/ITIS 6112/8112 091 Fall 2008 Dr. Jamie Payton Department of Computer Science University of North Carolina at Charlotte Oct. 30,
More informationUML- a Brief Look UML and the Process
UML- a Brief Look UML grew out of great variety of ways Design and develop object-oriented models and designs By mid 1990s Number of credible approaches reduced to three Work further developed and refined
More informationChapter 5 System modeling
Chapter 5 System Modeling Lecture 1 1 Topics covered Context models Interaction models Structural models Behavioral models Model-driven driven engineering 2 System modeling System modeling is the process
More informationMeltem Özturan
Meltem Özturan www.mis.boun.edu.tr/ozturan/samd 1 2 Modeling System Requirements Object Oriented Approach to Requirements OOA considers an IS as a set of objects that work together to carry out the function.
More informationEnterprise Architect Training Courses
On-site training from as little as 135 per delegate per day! Enterprise Architect Training Courses Tassc trainers are expert practitioners in Enterprise Architect with over 10 years experience in object
More informationCHAPTER 1. Topic: UML Overview. CHAPTER 1: Topic 1. Topic: UML Overview
CHAPTER 1 Topic: UML Overview After studying this Chapter, students should be able to: Describe the goals of UML. Analyze the History of UML. Evaluate the use of UML in an area of interest. CHAPTER 1:
More informationUnified Modeling Language (UML)
Appendix H Unified Modeling Language (UML) Preview The Unified Modeling Language (UML) is an object-oriented modeling language sponsored by the Object Management Group (OMG) and published as a standard
More informationIntroducing the UML Eng. Mohammed T. Abo Alroos
Introducing the UML Eng. Mohammed T. Abo Alroos Islamic University of Gaza Introduction to the UML: The UML stands for Unified Modeling Language. It was released in 1997 as a method to diagram software
More informationClass diagrams. Modeling with UML Chapter 2, part 2. Class Diagrams: details. Class diagram for a simple watch
Class diagrams Modeling with UML Chapter 2, part 2 CS 4354 Summer II 2015 Jill Seaman Used to describe the internal structure of the system. Also used to describe the application domain. They describe
More informationUML Tutorial. Unified Modeling Language UML Tutorial
UML Tutorial Unified Modeling Language UML Tutorial A Unified Modeling Language is a language for specifying, constructing, visualizing and documenting the software system and its components. UML is a
More informationObject-Oriented Design
Object-Oriented Design Lecture 14: Design Workflow Department of Computer Engineering Sharif University of Technology 1 UP iterations and workflow Workflows Requirements Analysis Phases Inception Elaboration
More informationOBJECT ORIENTED DESIGN with the Unified Process. Use Case Realization
OBJECT ORIENTED DESIGN with the Unified Process Use Case Realization Objectives Explain the purpose and objectives of objectoriented design Develop design class diagrams Develop detailed sequence diagrams
More informationPieter van den Hombergh. Fontys Hogeschool voor Techniek en Logistiek. September 9, 2016
Pieter van den Hombergh Fontys Hogeschool voor Techniek en Logistiek September 9, 2016 Contents /FHTenL September 9, 2016 2/35 UML State Uses and application In behaviour is modeled with state charts (diagrams)
More informationEngineering Design w/embedded Systems
1 / 40 Engineering Design w/embedded Systems Lecture 33 UML Patrick Lam University of Waterloo April 4, 2013 2 / 40 What is UML? Unified Modelling Language (UML): specify and document architecture of large
More informationArchitecture and the UML
Architecture and the UML Models, Views, and A model is a complete description of a system from a particular perspective Use Case Use Case Sequence Use Case Use Case Use Case State State Class State State
More informationUML Diagrams & And Some Of Their Elements
UML Diagrams 2013, J.P.N., page 1 UML Diagrams & And Some Of Their Elements UML Diagrams 2013, J.P.N., page 2 Building blocks of the UML As part of a model you have: modelling elements relationships between
More informationTopics. Kinds of UML models. Use case modeling. Actors. Actor. Assignment of reqs to actors and use cases
MACIASZEK, L.A. (2005): Requirements Analysis and System Design, 2 nd ed. Addison Wesley, Harlow England, 504p. ISBN 0 32 20464 6 Chapter 3.2 Objects and Object Modeling Fundamentals of object modeling
More informationModellistica Medica. Maria Grazia Pia, INFN Genova. Scuola di Specializzazione in Fisica Sanitaria Genova Anno Accademico
Modellistica Medica Maria Grazia Pia INFN Genova Scuola di Specializzazione in Fisica Sanitaria Genova Anno Accademico 2002-2003 Lezione 6 UML Introduction Structural diagrams Basics What is? Please explain
More informationA - 1. CS 494 Object-Oriented Analysis & Design. UML Class Models. Overview. Class Model Perspectives (cont d) Developing Class Models
CS 494 Object-Oriented Analysis & Design UML Class Models Overview How class models are used? Perspectives Classes: attributes and operations Associations Multiplicity Generalization and Inheritance Aggregation
More informationUnified Modeling Language I.
Unified Modeling Language I. Software engineering Szoftvertechnológia Dr. Balázs Simon BME, IIT Outline Software engineering Modeling Unified Modeling Language (UML) UML Diagrams: Use Case Diagram Activity
More informationUNIT-4 Behavioral Diagrams
UNIT-4 Behavioral Diagrams P. P. Mahale Behavioral Diagrams Use Case Diagram high-level behaviors of the system, user goals, external entities: actors Sequence Diagram focus on time ordering of messages
More informationMAHARASHTRA STATE BOARD OF TECHNICAL EDUCATION (Autonomous) (ISO/IEC Certified)
Important Instructions to examiners: 1) The answers should be examined by key words and not as word-to-word as given in the model answer scheme. 2) The model answer and the answer written by candidate
More informationUnified Modeling Language (UML) Class Diagram
1 / 10 Unified Modeling Language (UML) Class Diagram Miaoqing Huang University of Arkansas Spring 2010 2 / 10 Outline 1 2 3 / 10 Class Diagram Class diagrams show the static structure of the classes that
More informationMSc programme (induction week) Department of Informatics INTRODUCTION TO UML
MSc programme (induction week) Department of Informatics INTRODUCTION TO UML Some of this material is based on Bernd Bruegge and Allen H. Dutoit (2009) Object-Oriented Software Engineering: Using UML,
More information06. Analysis Modeling
06. Analysis Modeling Division of Computer Science, College of Computing Hanyang University ERICA Campus 1 st Semester 2017 Overview of Analysis Modeling 1 Requirement Analysis 2 Analysis Modeling Approaches
More informationCHAPTER 9 DESIGN ENGINEERING. Overview
CHAPTER 9 DESIGN ENGINEERING Overview A software design is a meaningful engineering representation of some software product that is to be built. Designers must strive to acquire a repertoire of alternative
More informationAdvanced Software Engineering
Dev Bhoomi Institute Of Technology LABORATORY MANUAL PRACTICAL INSTRUCTION SHEET EXPERIMENT NO. ISSUE NO. : ISSUE DATE: REV. NO. : REV. DATE : PAGE: 1 LABORATORY Name & Code: Advanced Software Engineering
More informationAPPENDIX M INTRODUCTION TO THE UML
M INTRODUCTION TO THE UML This appendix, written only for those readers not familiar with the topic, provides a brief introduction, which cannot be considered as exhaustive, to the UML. The UML is a general-purpose
More informationUnified Modeling Language
Unified Modeling Language Modeling Applications using Language Mappings Programmer s Reference Manual How to use this Reference Card: The consists of a set of fundamental modeling elements which appear
More informationChapter 3 System Models
March 16, 2009 Introduction Graphical models aid in requirements and development Introduction Graphical models aid in requirements and development Different perspectives are possible: external: context
More informationObject-Oriented Analysis and Design. Pre-UML Situation. The Unified Modeling Language. Unification Efforts
Object-Oriented Analysis and Design Analysis vs. Design Analysis Activities Finding the Objects/ Classes An Analysis Example The Unified Modeling Language Pre-UML Situation Early 90s Explosion of OO methods/notations
More informationMAHARASHTRA STATE BOARD OF TECHNICAL EDUCATION (Autonomous) (ISO/IEC Certified) MODEL ANSWER
Important Instructions to examiners: 1) The answers should be examined by key words and not as word-to-word as given in the model answer scheme. 2) The model answer and the answer written by candidate
More informationChapter 12. UML and Patterns. Copyright 2008 Pearson Addison-Wesley. All rights reserved
Chapter 12 UML and Patterns Copyright 2008 Pearson Addison-Wesley. All rights reserved Introduction to UML and Patterns UML and patterns are two software design tools that can be used within the context
More informationStructured and Object Oriented Analysis and Design
RAMRAO ADIK INSTITUTE OF TECHNOLOGY, NERUL Department of Computer Engineering Lab Manual Structured and Object Oriented Analysis and Design 2015-2016 List of Experiments Subject: Structured and object
More informationNotation Part 1. Object Orientated Analysis and Design. Benjamin Kenwright
Notation Part 1 Object Orientated Analysis and Design Benjamin Kenwright Version Control Example Team Princess 3 Members 3 Github Users e.g., Elva1997, michelle0924hhx, KimJaeHwang Each user can join and
More informationINTRODUCTION TO UNIFIED MODELING MODEL (UML) & DFD. Slides by: Shree Jaswal
INTRODUCTION TO UNIFIED MODELING MODEL (UML) & DFD Slides by: Shree Jaswal What is UML? 2 It is a standard graphical language for modeling object oriented software. It was developed in mid 90 s by collaborative
More informationCredit where Credit is Due. Lecture 4: Fundamentals of Object Technology. Goals for this Lecture. Real-World Objects
Lecture 4: Fundamentals of Object Technology Kenneth M. Anderson Object-Oriented Analysis and Design CSCI 6448 - Spring Semester, 2003 Credit where Credit is Due Some material presented in this lecture
More informationSoftware Architectures. Lecture 6 (part 1)
Software Architectures Lecture 6 (part 1) 2 Roadmap of the course What is software architecture? Designing Software Architecture Requirements: quality attributes or qualities How to achieve requirements
More informationSoftware Architecture. Lecture 5
Software Architecture Lecture 5 Roadmap of the course What is software architecture? Designing Software Architecture Requirements: quality attributes or qualities How to achieve requirements : tactics
More informationSequence Diagrams. Massimo Felici. Massimo Felici Sequence Diagrams c
Sequence Diagrams Massimo Felici What are Sequence Diagrams? Sequence Diagrams are interaction diagrams that detail how operations are carried out Interaction diagrams model important runtime interactions
More informationHippo Software BPMN and UML Training
Hippo Software BPMN and UML Training Icon Key: www.hippo-software.co.uk Teaches theory concepts and notation Teaches practical use of Enterprise Architect Covers BPMN, UML, SysML, ArchiMate Includes paper
More informationOBJECT ORIENTED DESIGN with the Unified Process. Use Case Realization
OBJECT ORIENTED DESIGN with the Unified Process Use Case Realization 2016 Software Engineering 2 (Zoom-Into Design) Requirement Requirement Specification (Functional & Non- Functional) analysis Requirement
More informationMAHARASHTRA STATE BOARD OF TECHNICAL EDUCATION (Autonomous) (ISO/IEC Certified)
Subject Code: 17630 Model Answer Page No: 1 /32 Important Instructions to examiners: 1) The answers should be examined by keywords and not as word-to-word as given in the model answer scheme. 2) The model
More informationPrinciples of Software Construction: Objects, Design and Concurrency. Just enough UML. toad
Principles of Software Construction: Objects, Design and Concurrency Just enough UML 15-214 toad Christian Kästner Charlie Garrod School of Computer Science With slides from Klaus Ostermann Learning Goals
More informationObject-Oriented Systems Development: Using the Unified Modeling Language
Object-Oriented Systems Development: Using the Unified Modeling Language Chapter 5: Unified Modeling Language Goals Modeling. Unified modeling language. Class diagram. Use case diagram. Interaction diagrams.
More informationLesson 11. W.C.Udwela Department of Mathematics & Computer Science
Lesson 11 INTRODUCING UML W.C.Udwela Department of Mathematics & Computer Science Why we model? Central part of all the activities We build model to Communicate Visualize and control Better understand
More informationUnit-1 INTRODUCTION 1.1 CATEGORIES OF INFORMATION SYSTEMS SYLLABUS:
Unit-1 INTRODUCTION SYLLABUS: Categories of Information systems-traditional paradigm vs. Object oriented paradigm-objects and Classes-Inheritance-Object relationship-examples of UML class modeling-unified
More informationFrom Analysis to Design. LTOOD/OOAD Verified Software Systems
From Analysis to Design 1 Use Cases: Notation Overview Actor Use case System X System boundary UCBase «extend» UCExt Actor A UCVar1 UCVar2 Extending case Generalization «include» Actor B UCIncl Included
More informationDesigning Procedural 4GL Applications through UML Modeling
Designing Procedural 4GL Applications through UML Modeling Shiri Davidson Mila Keren Sara Porat Gabi Zodik IBM Haifa Research Lab Matam - Advanced Technology Center Haifa 31905, Israel (shiri, keren, porat,
More information12 Tutorial on UML. TIMe TIMe Electronic Textbook
TIMe TIMe Electronic Textbook 12 Tutorial on UML Introduction......................................................2.................................................3 Diagrams in UML..................................................3
More informationUML Start-Up Training UB1
UML Start-Up Training UB1 Index History Overview Diagrams Use Case Diagram Sequence Diagram Activity Diagram Class Diagram UML This training course is designed with the intention to teach UML in not longer
More informationMetamodeling. Janos Sztipanovits ISIS, Vanderbilt University
Metamodeling Janos ISIS, Vanderbilt University janos.sztipanovits@vanderbilt.edusztipanovits@vanderbilt edu Content Overview of Metamodeling Abstract Syntax Metamodeling Concepts Metamodeling languages
More informationChapter 4. Capturing the Requirements. 4th Edition. Shari L. Pfleeger Joanne M. Atlee
Chapter 4 Capturing the Requirements Shari L. Pfleeger Joanne M. Atlee 4th Edition It is important to have standard notations for modeling, documenting, and communicating decisions Modeling helps us to
More informationiserver Free Archimate ArchiMate 1.0 Template Stencil: Getting from Started Orbus Guide Software Thanks for Downloading the Free ArchiMate Template! Orbus Software have created a set of Visio ArchiMate
More informationMCQS for Midterm cs504 Combined by Anees Ahmad
MCQS for Midterm cs504 Combined by Anees Ahmad The best way to conduct a requirements validation review is to examine the system model for errors have the customer look over the requirements send them
More informationUnified Modeling Language for Real-Time Systems Design
Unified Modeling Language for Real-Time Systems Design Introduction The Unified Modeling Language, or UML, is a third-generation object-oriented modeling language. It adapts and extends the published works
More informationCourse "Softwaretechnik Modeling with UML Stephan Salinger
Course "Softwaretechnik Modeling with UML Stephan Salinger (Foliensatz/Inhalt: Lutz Prechelt, Bernd Bruegge, Allen H. Dutoit) Freie Universität Berlin, Institut für Informatik http://www.inf.fu-berlin.de/inst/ag-se/
More informationUML Views of a System
UML Views of a System The architecture of a system is the fundamental organization of the system as a whole. The five UML Views: Use Case View: focuses on scenarios Design View: focuses on the vocabulary
More informationChapter No. 2 Class modeling CO:-Sketch Class,object models using fundamental relationships Contents 2.1 Object and Class Concepts (12M) Objects,
Chapter No. 2 Class modeling CO:-Sketch Class,object models using fundamental relationships Contents 2.1 Object and Class Concepts (12M) Objects, Classes, Class Diagrams Values and Attributes Operations
More informationSoftware Design And Modeling BE 2015 (w. e. f Academic Year )
Software Design And Modeling BE 2015 (w. e. f Academic Year 2018-2019) 1 The Team Prof. Ravi Patki, I 2 IT Hinjawadi Pune Prof. Sangita Jaibhaiye SCOE Prof. D.D.Londhe PICT Prof. P. A. Joshi, ZCOER 2 The
More information