Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
Subject: Object Oriented Analysis and Design
B.Tech III Year II-Semester
Computer Science &Engineering
By
Syamala Bathula
...
Table of Contents
Unit-VIII: The Implementation Workflow
• Implementation artifacts-meta model
• Implementation workflow d...
Learning Objectives
At the end of this unit the student will be in a position to:
• Understand the Implementation workflow...
The Implementation Workflow
• Begins in the Elaboration phase and is the main focus of the Construction
phase
• Implementa...
Implementation Artifacts-Meta model
• The implementation model is really just the implementation view of a design
model
• ...
Implementation artifacts
• The implementation model specifies how the design elements are manifest by
artifacts and how th...
<<component>>
c1
<<component>>
c2
Design model
artifact
a1
artifact
a2
artifact
a2
<<device>>
n1
<<device>>
n2
Implementat...
Implementation workflow detail
Architect
Architectural implementation
System integrator
Integrate system
Component enginee...
Implementation workflow detail (cont..)
The workers involved in the implementation workflow are
 Architect
 System integ...
Architectural implementation
Is about identifying architecturally significant Components and mapping them to
physical hard...
Deployment diagram
• The key activity in Architectural implementation is creating one or more
deployment diagrams.
• Deplo...
Deployment diagram for ATM system
Example:
ATM Server
ATM system
Users Dba
Atm server is a processor
which can have some
p...
Nodes
A node is a physical element that exists at run time and represents
a computational resource, generally having at le...
Example:
<<execution environment>>
Firefox
<<execution environment>>
Apache
<<device>>
WindowsPC
<<device>>
LinuxPC
node
0...
Nodes and Components
• Nodes are a lot like Components.
• There are some significant differences between nodes and compone...
Organizing Nodes
• You can organize nodes by specifying relationships among them.
• The most common kind of relationship y...
Artifacts:
• An artifact represents the specification of a concrete, real-world thing such as
the source file
• A artifact...
Artifacts and Classes
• Classes and Artifacts are both classifiers. there are some significant
differences between artifac...
Standard stereotypes in Artifacts
The UML predefines standard stereotypes that apply to artifacts:
1. Executable Specifies...
Introduction to Object Constraint Language(OCL)
• OCL is a language that allows you to add extra information to a UML mode...
Summary/Glossary:
The implementation workflow Begins in the Elaboration phase and is the main
focus of the Construction ph...
Quiz:
1) Implementation model is the main focus of the Construction phase
a) Elaboration phase b) Construction phase c) In...
Key:
1) b
2) c
3) b
4) d
5) c
6) a
THANK YOU
Upcoming SlideShare
Loading in …5
×

Ooad content of ooad unit viii

54 views

Published on

Ooad content of ooad unit viii

Published in: Engineering
  • Be the first to comment

  • Be the first to like this

Ooad content of ooad unit viii

  1. 1. Subject: Object Oriented Analysis and Design B.Tech III Year II-Semester Computer Science &Engineering By Syamala Bathula Assistant Professor CSE dept.,VCE
  2. 2. Table of Contents Unit-VIII: The Implementation Workflow • Implementation artifacts-meta model • Implementation workflow detail • Architectural implementation • The Deployment diagram • Nodes • Artifacts • Deployment • Introduction to OCL
  3. 3. Learning Objectives At the end of this unit the student will be in a position to: • Understand the Implementation workflow • Showing how implementation and deployment details of a system can be modeled using the Implementation and Deployment diagrams respectively. • Understand how Component Diagrams and Nodes can be used to describe the deployment environment of a system. • Know the importance of Object Constraint Language(OCL)
  4. 4. The Implementation Workflow • Begins in the Elaboration phase and is the main focus of the Construction phase • Implementation model is transforming a design model into executable code.
  5. 5. Implementation Artifacts-Meta model • The implementation model is really just the implementation view of a design model • The Implementation model is part of the design model. Example: Design Model Implementation Model
  6. 6. Implementation artifacts • The implementation model specifies how the design elements are manifest by artifacts and how these artifacts are deployed onto nodes • Artifacts represent the specification of real-world things such as source files, and nodes. • Nodes represent the specifications of hardware or execution environment onto which those things are deployed
  7. 7. <<component>> c1 <<component>> c2 Design model artifact a1 artifact a2 artifact a2 <<device>> n1 <<device>> n2 Implementation model note artifact <<manifest>> <<manifest>> <<manifest>>
  8. 8. Implementation workflow detail Architect Architectural implementation System integrator Integrate system Component engineer Implement a class Implement a component Perform unit test
  9. 9. Implementation workflow detail (cont..) The workers involved in the implementation workflow are  Architect  System integrator  Component engineer • The Architect is responsible for Architectural implementation • System Integrator is responsible for Integrate System. • Component Engineer is responsible for i. Implement a Class ii. Implement a Component iii. Perform unit test
  10. 10. Architectural implementation Is about identifying architecturally significant Components and mapping them to physical hardware. Deployment model Design model Architectural description Node Component Artifact Architectural description Architect Architectural implementation
  11. 11. Deployment diagram • The key activity in Architectural implementation is creating one or more deployment diagrams. • Deployment diagrams show the configuration of run-time processing elements and the software components, processes, and objects that live on them • The deployment diagram models the physical computational nodes on which the software artifacts will be deployed, and the relationships between those nodes. • The deployment diagram maps the software architecture to the hardware architecture. • A deployment diagram is a graph of nodes connected by communication associations • Software component instances represent run-time manifestations of code units
  12. 12. Deployment diagram for ATM system Example: ATM Server ATM system Users Dba Atm server is a processor which can have some processing capacity. Atm system is a device. and users and dba will come under work product components
  13. 13. Nodes A node is a physical element that exists at run time and represents a computational resource, generally having at least some memory and, often, processing capability. A node represents a type of computational resource upon which artifacts can be deployed for execution. Example: There are two standard stereotypes for nodes. <<device>> the node represents a type of physical device such as a pc or a server <<execution environment>> the node represents a type of execution environment for software Example: Apache web server EJB (Enterprise JavaBeans) Egb_server
  14. 14. Example: <<execution environment>> Firefox <<execution environment>> Apache <<device>> WindowsPC <<device>> LinuxPC node 0..* <<http>> 0..* association
  15. 15. Nodes and Components • Nodes are a lot like Components. • There are some significant differences between nodes and components  Components are things that participate in the execution of a system; nodes are things that execute components  Components represent the physical packaging of logical elements; nodes represent the physical deployment of components. Example: sales Pos.exe Contacts.exe node components
  16. 16. Organizing Nodes • You can organize nodes by specifying relationships among them. • The most common kind of relationship you will use among nodes is an association. • an association represents a physical connection among nodes, such as an Ethernet connection , a serial Line, or a shared bus Examples: kiosk console server RAID farm “ 10-T Ethernet” “RS-232”
  17. 17. Artifacts: • An artifact represents the specification of a concrete, real-world thing such as the source file • A artifact is a physical part of a system that exists at the level of the implementation platform. • Artifacts are deployed on nodes Notation: • Many operating systems and programming languages directly support the concept of an artifact. • Object libraries , executables ,.NET components ,and Enterprise Java Beans are all examples of artifacts. Some other examples of artifacts are  Source files  Executable files  Scripts  Database tables  Documents  Outputs of the development process <<artifact>> Kernel32.dll <<artifact>> Agent.java
  18. 18. Artifacts and Classes • Classes and Artifacts are both classifiers. there are some significant differences between artifacts and classes • Classes represent logical abstraction; artifacts represent physical things • Artifacts may live on nodes, Classes may not • Artifacts represent the physical packaging of bits on the implementation platform • Classes may have attributes and operations. Artifacts may implement classes and methods, but they do not have attributes or operations themselves. Example: <<artifact>> fraudagent.dll FraudAgent FraudPolicy PatternSearch <<manifest>> <<manifest>> <<manifest>> artifact classes
  19. 19. Standard stereotypes in Artifacts The UML predefines standard stereotypes that apply to artifacts: 1. Executable Specifies an artifact that may be executed on a node 2. Library Specifies a Static or dynamic object library 3. File Specifies an artifact that represents a document containing source code or data 4. Document Specifies an artifact that represents a document
  20. 20. Introduction to Object Constraint Language(OCL) • OCL is a language that allows you to add extra information to a UML model. • It is a standard extension to UML. • OCL can specify, queries, constraints, and query operations. • OCL allows you to do the following  Write queries to access model elements and their values-it is a query language a bit like sql  State constraints on model elements –you can define business rules as constraints on model elements  Define query operations. • OCL is not an action language for UML because OCL expression have no side effects • OCL can’t change the value of a model element - you can only query values and state conditions on values. • OCL can’t define an operation other than a query operation • OCL can only execute query operations that don’t change values • OCL can’t be used to specify business rules dynamically at runtime.
  21. 21. Summary/Glossary: The implementation workflow Begins in the Elaboration phase and is the main focus of the Construction phase Implementation model is transforming a design model into executable code. Artifacts represent the specification of real-world things such as source files, and nodes. Nodes represent the specifications of hardware or execution environment onto which those things are deployed The deployment diagram models the physical computational nodes on which the software artifacts will be deployed, and the relationships between those nodes. OCL : Object Constraint Language is a language that allows you to add extra information to a UML model. It is a standard extension to UML. OCL can specify, queries, constraints, and query operations.
  22. 22. Quiz: 1) Implementation model is the main focus of the Construction phase a) Elaboration phase b) Construction phase c) Inception phase d) Transition 2) ____________ is a part of design model a) Analysis model b) Requirements model c) implementation model d) Test model 3) _____________represent the specifications of hardware or execution environment onto which those things are deployed a) Artifacts b) Node c) both d) none 4) Component Engineer is responsible for a) Implement a Class b) Implement a Component c) Perform unit test d) all 5) The ____________________ maps the software architecture to the hardware architecture. a) Component diagram b) Class diagram c) deployment diagram d) none 6) The most common kind of relationship you will use among nodes is an a) association. b) dependency c) generalization d) realization
  23. 23. Key: 1) b 2) c 3) b 4) d 5) c 6) a
  24. 24. THANK YOU

×