Karolina Muszyńska Based on: S. Wrycza, B. Marcinkowski, K. Wyrzykowski „Język UML 2.0 w modelowaniu SI”

Slides:



Advertisements
Similar presentations
Profiles Construction Eclipse ECESIS Project Construction of Complex UML Profiles UPM ETSI Telecomunicación Ciudad Universitaria s/n Madrid 28040,
Advertisements

Karolina Muszyńska Based on: S. Wrycza, B. Marcinkowski, K. Wyrzykowski „Język UML 2.0 w modelowaniu SI”
Karolina Muszyńska Based on:
Modelling Class T05 Conceptual Modelling – Domain References: –Conceptual Modeling of Information Systems (Chapters 1.2.1, 2, 3) –A practical Guide to.
Object-oriented modeling Class/Object Diagrams
Stereotypes Stereotypes provide the capability to create a new kind of modeling element. –They can be used to classify or mark modeling elements. –A type.
® IBM Software Group © 2006 IBM Corporation Rational Software France Object-Oriented Analysis and Design with UML2 and Rational Software Modeler 04. Other.
2008/03/25 Unified Modeling Lanauage 1 Introduction to Unified Modeling Language (UML) – Part One Ku-Yaw Chang Assistant Professor.
Programming with Objects: Class Libraries and Reusable Code.
1 © Wolfgang Pelz UML3 UML 3 Notations describe how to use reusable software. Package Component Deployment Node.
1 CS 426 Senior Projects Chapter 19: Interfaces and Components [Arlow & Neustadt 2005] February 28, 2008.
CS 425/625 Software Engineering System Models
Introduction to UML Visual modeling Models and its importance
Package Diagram CS537 Advanced Software Engineering Fall 2010 Prof. J Guo Presented By: Patel Vishrut Patel Harshil Gadhiya Yogesh Dhola Haresh.
Systems Analysis and Design in a Changing World, 6th Edition
1 A Student Guide to Object- Orientated Development Chapter 9 Design.
Common Page Design. Graphics and Tables Uses: Objects Numbers Concepts Words.
Karolina Muszyńska Based on: S. Wrycza, B. Marcinkowski, K. Wyrzykowski „Język UML 2.0 w modelowaniu SI”
Karolina Muszyńska Based on: S. Wrycza, B. Marcinkowski, K. Wyrzykowski „Język UML 2.0 w modelowaniu SI”
Karolina Muszyńska Based on: G. Schneider, J.P. Winters „Stosowanie przypadków użycia” S. Wrycza, B.
Smith’s Aerospace © P. Bailey & K. Vander Linden, 2005 Architecture: Component and Deployment Diagrams Patrick Bailey Keith Vander Linden Calvin College.
Session 24 Modeling the Development Environment Written by Thomas A. Pender Published by Wiley Publishing, Inc. October 27, 2011 Presented by Hyewon Lim.
SOFTWARE ENGINEERING BIT-8 APRIL, 16,2008 Introduction to UML.
CIT UPES | Sept 2013 | Unified Modeling Language - UML.
CHAPTER ONE Problem Solving and the Object- Oriented Paradigm.
SWE © Solomon Seifu ELABORATION. SWE © Solomon Seifu Lesson 11 Subsystem Design.
Organizing Your Information
METACASE. WHAT THIS PRESENTATION IS ABOUT  What’s META MODELING?  What’s METACASE?  METAEDIT+ 5.1 EVALUTION PROGRAM  Diagram and its kinds.
Practical Object-Oriented Design with UML 2e Slide 1/1 ©The McGraw-Hill Companies, 2004 PRACTICAL OBJECT-ORIENTED DESIGN WITH UML 2e Chapter 9: Interaction.
1 Advanced Software Architecture Muhammad Bilal Bashir PhD Scholar (Computer Science) Mohammad Ali Jinnah University.
Fall 2010 CS4310 Requirements Engineering A Brief Review of UML & OO Dr. Guoqiang Hu Department of Computer Science UTEP 1.
An Introduction to the Unified Modeling Language
Logical view –show classes and objects Process view –models the executables Implementation view –Files, configuration and versions Deployment view –Physical.
Part VII: Design Continuous
1 Package Diagram. 2 הדיאגרמות 3 אבני יסוד: דיאגרמות פריסת התוכנה על גבי החומרה PackageDiagram “חבילות עבודה” מקרא: מודל סטטי מודל דינמי מודל ניהולי.
Relationships Relationships between objects and between classes.
1 Class Diagrams. 2 Overview Class diagrams are the most commonly used diagrams in UML. Class diagrams are for visualizing, specifying and documenting.
© 2005 Prentice Hall1-1 Stumpf and Teague Object-Oriented Systems Analysis and Design with UML.
Domain Classes – Part 1.  Analyze Requirements as per Use Case Model  Domain Model (Conceptual Class Diagram)  Interaction (Sequence) Diagrams  System.
Karolina Muszyńska Based on: S. Wrycza, B. Marcinkowski, K. Wyrzykowski „Język UML 2.0 w modelowaniu SI”
1 Software Design Lecture What’s Design It’s a representation of something that is to be built. i.e. design  implementation.
1 Technical & Business Writing (ENG-715) Muhammad Bilal Bashir UIIT, Rawalpindi.
Chapter 19: Interfaces and Components [Arlow and Neustadt, 2005] University of Nevada, Reno Department of Computer Science & Engineering.
Karolina Muszyńska Based on: S. Wrycza, B. Marcinkowski, K. Wyrzykowski „Język UML 2.0 w modelowaniu SI”
1 Introduction to UML Interface and packages 即時與嵌入式系統實驗試 李榮華.
Banaras Hindu University. A Course on Software Reuse by Design Patterns and Frameworks.
Identifying classes, Packages and drawing class Diagrams, Object Diagrams and composite structure diagrams Week 07 1.
1 Kyung Hee University Interaction Diagrams Spring 2001.
RASDS : a DRAFT model library approach (in complement to P. Shames & T. Yamada slides for SPACEOPS 2004)
DOMAIN CLASSES – PART 1 BTS430 Systems Analysis and Design using UML.
1 Design Object Oriented Solutions Object Oriented Analysis & Design Lecturer: Mr. Mohammed Elhajj
Unified Modeling Language (UML)
UML(Unified Modeling Language)
Course Outcomes of Object Oriented Modeling Design (17630,C604)
Chapter 19: Interfaces and Components
Object Oriented Analysis and Design
Packages.
INFS 6225 Object Oriented Systems Analysis & Design
UNIT – V.
SYS466 Domain Classes – Part 1.
UML profiles.
Class Diagrams.
Chapter 19: Interfaces and Components
Chapter 19: Interfaces and Components
Package Diagram.
Stumpf and Teague Object-Oriented Systems Analysis and Design with UML
Identifying & Creating Use Cases - Part 3
Interfaces and Components
CLASSIFYING MATTER.
Stumpf and Teague Object-Oriented Systems Analysis and Design with UML
Presentation transcript:

Karolina Muszyńska Based on: S. Wrycza, B. Marcinkowski, K. Wyrzykowski „Język UML 2.0 w modelowaniu SI”

 Organizing and grouping - package diagrams ◦ role ◦ basic concepts ◦ advanced concepts ◦ examples 2

 Package diagram is a graphical representation of the logical structure of the system as a set of packages combined with dependencies and decomposed. These diagrams are used for grouping and organizing complex project documentation. 3

 Package - a general-purpose mechanism that is used to organize the elements of a group. Package may include a variety of UML classifiers, complete diagrams, class libraries, subsystems, models or templates.  Dependency - the basic way to combine packages into a logical structure, which results in creation of package diagrams  Package nesting/decomposing – a natural way to organize packages, which can be multilevel 4

5 Package Dependency

6 Nesting/Decomposition

 Stereotyping of packages: ◦ model stereotype ◦ subsystem stereotype ◦ template stereotype ◦ class library stereotype  Stereotyping of dependencies: ◦ import ◦ merge ◦ access 7

 Model stereotype - describes the packages that are models; common model stereotype packages represent use cases models, business models and analytical models  Subsystem stereotype - is useful in modeling systems decomposed into hierarchically ordered packages  Template stereotype - describes a package which is model solutions to problems in a given field  Class library stereotype - describes a package which groups system components to be used by other packages 8

 Import stereotype - describes commonly used dependency, meaning inclusion of classifiers, which are inside the target package into the source package during the operation of the system  Merge stereotype - leads to merging of classifiers which are inside the target package with the classifiers included in the source package; such merging dependency means that the classifiers from the source package inherit from the target package, but only within the classifiers of the same type, identical names, with "public" visibility  Access dependency - means that the source package can access the contents of the target package without physical download of data 9

10 Dependency stereotypes

11 Dependency stereotypes Subsystem stereotype

 identification and labeling of packages  classification of identified packages using appropriate stereotypes,  identification of packages nesting/ decomposition,  combining packages using dependencies,  specification of dependencies by giving them appropriate stereotypes 12