1 Introduction to UML Interface and packages 即時與嵌入式系統實驗試 李榮華.

Slides:



Advertisements
Similar presentations
CS4101 嵌入式系統概論 Program Organization Prof. Chung-Ta King Department of Computer Science National Tsing Hua University, Taiwan ( Materials from MSP430 Microcontroller.
Advertisements

Resource Access Protocols
Chapter 2 – Software Processes Lecture 1 1Chapter 2 Software Processes.
Package Diagrams A package diagram is a UML diagram composed only of packages and the dependencies between them. A package is a UML construct that enables.
Modelling Class T05 Conceptual Modelling – Domain References: –Conceptual Modeling of Information Systems (Chapters 1.2.1, 2, 3) –A practical Guide to.
® IBM Software Group © 2006 IBM Corporation Rational Software France Object-Oriented Analysis and Design with UML2 and Rational Software Modeler 04. Other.
© 2007 Pearson Education, Inc. Publishing as Pearson Addison-Wesley 1 Architectural Modeling Notations.
Karolina Muszyńska Based on: S. Wrycza, B. Marcinkowski, K. Wyrzykowski „Język UML 2.0 w modelowaniu SI”
UML: An Introduction.
中華通訊大學部課程規劃流程圖 基礎課程核心課程應用課程 程式設計 I,II 微處理機 I,II 數位邏輯 FPGA 無線通訊 MAC 靭體設計 計算機應用 / 通訊靭體設計專業領域 大ㄧ大二 大三大四 嵌入式 系統專題 專業選修專題設計 II 硬體描述語言 FPGA+HDL 無線通訊 嵌入式系統 專題設計.
張書銘 D 陳佑任 D 系統安全 Sniffer-Wireshark 之實作.
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.
Introduction to UML Visual modeling Models and its importance
1 SWE Introduction to Software Engineering Lecture 15 – System Modeling Using UML.
1/31 CS 426 Senior Projects Chapter 1: What is UML? Chapter 2: What is UP? [Arlow and Neustadt, 2005] January 22, 2009.
1 CS 691z / 791z Topics on Software Engineering Chapter 17: Interfaces and Subsystems [Arlow & Neustadt, 2002] March 6, 2007.
1 CS 501 Spring 2002 CS 501: Software Engineering Lecture 16 Object Oriented Design I.
ECE 355: Software Engineering
Session 24 Modeling the Development Environment Written by Thomas A. Pender Published by Wiley Publishing, Inc. October 27, 2011 Presented by Hyewon Lim.
Design Patterns OOD. Course topics Design Principles UML –Class Diagrams –Sequence Diagrams Design Patterns C#,.NET (all the course examples) Design Principles.
Implementation Yaodong Bi. Introduction to Implementation Purposes of Implementation – Plan the system integrations required in each iteration – Distribute.
1 ARCHITECTURAL MODELING 主講人 : 李榮華. 2 Outline Deployment Deployment Diagrams Collaborations Patterns and Frameworks.
SOFTWARE DESIGN Design Concepts Design is a meaningful engineering representation of something that is to be built It can be traced to a customer’s requirements.
Guidance on expressing the Dublin Core within the Resource Description Framework(RDF) Eric Miller, Paul Miller, Dan Brickley Dublin Core Metadata Initiative.
Uml is made similar by the presence of four common mechanisms that apply consistently throughout the language. After constructing or developing the architecture.
UML 範圍 :CH25 CH27 CH31 莫家仁 日期 :Sep.5. Outline Components Component Diagrams System And Models.
UML diagrams What is UML UML diagrams –Static modeoing –Dynamic modeling 1.
1 Advanced Software Architecture Muhammad Bilal Bashir PhD Scholar (Computer Science) Mohammad Ali Jinnah University.
Logical view –show classes and objects Process view –models the executables Implementation view –Files, configuration and versions Deployment view –Physical.
Part VII: Design Continuous
Unified Modelling Language (UML) Software Engineering Lab. Sharif University of Technology.
Lab 5 CPIT 250 System Analysis and Design.
Software Engineering Lecture 8 Object-Oriented Analysis.
Social Roles and Relationships.
 Building Block Building Block  Things in the UML Things in the UML  Structural Things Structural Things  Behavioral Things Behavioral Things  Grouping.
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.
TK2023 Object-Oriented Software Engineering CHAPTER 8 LOGICAL ARCHITECTURE.
Object Oriented Analysis and Design 1 Chapter 9 From Design to Implementation  Implementation Model  Forward, Reverse, and Round-Trip Engineering  Mapping.
NEWS Lab – Wireless Networking Group 嵌入式系統與無線網路實驗室 – 無線網路研究群 Ai-Chun Pang ( 逄愛君 ) Grad. Inst. of Networking and Multimedia Dept. of Comp. Sci. and Info.
Design and implementation Chapter 7 – Lecture 1. Design and implementation Software design and implementation is the stage in the software engineering.
Introduction to UML Hazleen Aris Software Eng. Dept., College of IT, UNITEN. …Unified Modeling Language.
1 Kyung Hee University Interaction Diagrams Spring 2001.
CS 501: Software Engineering Fall 1999 Lecture 15 Object-Oriented Design I.
Unified Modeling Language. What is UML? Standard language for specifying, visualizing, constructing, and documenting the artifacts of software systems,
UML (Unified Modeling Language)
Introduction to the Unified Model Language (UML) Rob Byrd
UML Diagrams By Daniel Damaris Novarianto S..
Course Outcomes of Object Oriented Modeling Design (17630,C604)
University of Central Florida COP 3330 Object Oriented Programming
UML Diagrams Jung Woo.
Diagram Interchange Proposal
Chapter 19: Interfaces and Components
Object Oriented Analysis and Design
面向对象分析与设计 Use of starUML By Wang Meihong.
Chapter 12 Collections.
Building Graphical User Interface with Swing a short introduction
Packages.
UNIT – V.
Understand and Use Object Oriented Methods
Introduction to Computer Science for Majors II
Chapter 19: Interfaces and Components
Chapter 19: Interfaces and Components
Paper written by Flavio Oquendo Presented by Ernesto Medina
Chapter 12 Collections.
Copyright © 2015, 2012, 2009 Elsevier Inc. All rights reserved.
Interfaces and Components
Instructor: Chen-Hsiung Yang
Chapter 19: Interfaces and Components
Presentation transcript:

1 Introduction to UML Interface and packages 即時與嵌入式系統實驗試 李榮華

2 Outline Interface 1.Define 2.Why Interface 3.Example Packages 1.Define 2.Why package 3.Example

3 Interface An Interface is a collection of operations that are used to specify a service of a class or a component.

4 Why Interface To build systems with a clear separation of concerns so that,as the system evolves,changes in one part of the system don ’ t ripple through,rending other parts of the system.

5 If it ’ s important for your understanding of current model,you can render an interface as a stereotyped class. Another representation for Interface

6 Interface Specifier  As the figure shows,you can explicitly show the type of role using the syntax rolename:iname,where iname is some interface of the other classifier.

7 Package A package is general-purpose mechanism for organizing elements into groups.Graphically,a package is rendered as a tabbed folder. A package may own other elements,including classes,interface,components,nodes,collaborations,u se cases,diagrams,and even other packages.

8 Why Packages Organize the elements. Control the seams in your system ’ Architecture.

9 Generalization Packages involved in generalization relationship follow the same principle of substitutability as do classes.

10 To model architectural views Identify the set of architectural views. Pace the elements. Group these elements into their own packages.