10 ooad uml-13

Object-Oriented Analysis and Design Using UML
Objectives

In this session, you will learn to:
Create package diagrams
Create component diagrams
Create deployment diagrams

Ver. 1.0 Slide 1 of 21

Introducing Architectural Modeling

Architectural modeling:
Enables visualizing the physical distribution of components
over the network of the organization.
Determines if the design of components meets the
requirements of the software system.
Diagrams to model the architecture of software system are:
Package diagram
Component diagram
Deployment diagram


Creating Package Diagrams

Package diagrams depict the various packages of a
software system and the relationships among them.
Advantages of using packages to model the constituents of
a software system are:
Enables visualizing the functional groups and the relationships
among them.
Facilitates easy management of large software systems.
You can group use cases of a software system into
packages based on the following rules:
Group related use cases
Group use cases based on the actors that use them


Creating Package Diagrams (Contd.)

You can package classes of a software system into
packages based on the following criteria:
Package classes that belong to the same inheritance
hierarchy.
Package classes that are related through composition
relationship.
Package classes that collaborate and interact with each other
to realize use cases.



Symbols used to set the visibility of constituents in
packages are:
– +: Indicates that the constituent is public and, therefore, is
accessible to the constituents of other packages.
– #: Indicates that the constituent is protected and, therefore, is
accessible to the constituents that inherit it.
– -: Indicates that the constituent is private and, therefore, is not
accessible to the constituents outside the package.



Types of relationships between packages are:
Access dependency relation
Generalization relation


Depicting the Package Diagram for the IMS

Package diagram for inventory management system.
Tender Order

Tender Class Order Class

Tender Database Table Order Database Table
TenderPolicy

+ TenderRules Class

+ SupplierSelectionRules

Parts
Supplier

Parts Class <<Composition>>

Supplier Class PartSpecification

Supplier Database
Table
ElectronicParts AutomobileParts
Class Class


Creating Component Diagrams

Components provide realization of a set of interfaces and
form the executable parts of a software system.
Components that you can model to form a complete
software system are:
– Deployment components: Includes components that form the
executable system.
– Work product components: Includes components that are
the outcome of implementation phase of SDLC.
– Execution components: Includes components that are
created when a system is executing.
A component realizes a set of interfaces each of which
specifies the functionality offered by a class.
A class can also realize a set of interfaces.


Creating Component Diagrams (Contd.)

Techniques for modeling components are:
Source code file modeling
Executable file modeling
Database modeling
The various ways to visualize the source code components
of the software system are:
Group the source code files into packages and depict them in a
package diagram.
Draw component diagrams to visualize the relationship
between the source code files of the system.


Creating Component Diagrams (Contd.)

Modeling executable files includes modeling the .exe,
library, and database that comprise the system.
Database modeling involves:
Depicting the database table components using component
diagrams.
Depicting columns and stored procedures associated with each
database table component.


Creating Deployment Diagrams

You draw deployment diagrams to visualize the hardware
on which the software components need to be deployed.
The various computer systems or processing devices on
which components are deployed are called nodes.
A node is represented as a 3-Dimensional rectangular box
containing the components that execute within the node.


Creating Deployment Diagrams (Contd.)

Nodes are associated with each other by a connection,
which represents a communication channel.
You depict a communication channel among nodes by a
straight line drawn between the communicating nodes.
Dependency relationship between a node and a component
is represented by using a dashed line.


Just a minute

Which of the following diagrams is used to visualize the
hardware on which the software components need to be
deployed?
1. Package diagram
2. Component diagram
3. Deployment diagram
4. Interaction Overview diagram

Answer:
Deployment diagram


Identifying Software Architecture Viewtypes

A software architecture viewtype specifies the constituents
that you may model in the architecture of a software
system.
Predefined viewtypes listed by UML are:
– Module viewtype: Specifies the modules that implement a
specific functionality.
– Component and Connector (C&C) viewtype: Specifies a
collection of the components each of which is an execution
unit.
– Allocation viewtype: Specifies as a set of relationships
between the components or modules of a software system with
the development environment.


Demo: Architectural Modeling for the Bank ATM System

Problem Statement:
Janes Technology needs to create the architectural model for
the prototype of the InfoSuper bank ATM system. The
prototype will include only the cash withdrawal feature of the
InfoSuper bank ATM system. The project manager of Janes
Technology has identified the following classes, attributes, and
operations for the prototype of the InfoSuper bank ATM
system:
Class Operations Desciption
ATM Show() Displays the location and branch name of the ATM.

ATMCard GetPin() Accepts the PIN entered by the customer and
verifies it.
GetAccount() Fetches the account information based on the
card_ID and PIN.

SetPin(int)
Updates the PIN.


Demo: Architectural Modeling for the Bank ATM System (Contd.)

BankCustomer InsertCard() Prompts the customer to insert ATM card.

Select a transaction from a list of
SelectTransaction() transactions.

EnterPin() Prompts the customer to enter the PIN.

Invokes the PIN change request. The
ChangePin() bank customer enters the new PIN.

WithdrawCash() Invokes the cash withdrawal operation.

RequestTransactionSummary() Requests for the summary of the
transaction performed by the customer.
Account CalculateInterest() Calculates the interest for the account.
This is an abstract operation.

UpdateAccount() Updates the account information.

VerifiyWithdrawalAmount() Verifies if the amount to be withdrawn is
less than the account balance amount.



CurrentAccount CalculateInterest() Calculates the interest for the current
account.

SavingsAccount CalculateInterest() Calculates the interest for the savings
account.

Transaction getAccountBalance() Obtains the balance of the account.

StartTransaction() Initiates the transaction.

CancelTransaction Cancels the current transaction.
CardScanner AcceptCard() Accept/rejects the ATM card based on the
validation provided.

ReadCard() Reads the Card_Id associated with the
ATM card.

EjectCard() Ejects the ATM card.



DisplayScreen Prompt() Prompts the respective screen as per request.

AcceptInput() Accepts the required input on the displayed
screen.

CashDispenser SupplyCash() Supplies the verified amount as cash.

GenerateRecipt() Generates a receipt for the cash dispensed.

The project manager has also created the following class
diagram after identifying the classes and operations for the
prototype of the InfoSuper bank ATM system.



Solution:
To create the architectural view for the prototype of the ATM
system, you need to perform the following tasks:
Identify components and relationships among them.
Identify the nodes and their executable components.
Create a component diagram.
Create a deployment diagram.


Summary

In this session, you learned that:
Architectural modeling is used to depict the physical
constituents of a software system. The physical constituents
consist of the components and nodes on which the
components execute.
The components of a software system can be modeled on the
basis of different architectural viewtypes. The various
viewtypes are the module viewtype, component and connector
viewtype, and allocation viewtype.
The artifacts that UML provides to enable architectural
modeling are: package diagrams, component diagrams, and
deployment diagrams.
Packages are used to group the related constituents of a
software system.


Summary (Contd.)

Component diagrams are used to model the various
components required for a system to execute.
Deployment diagrams are used to depict the various nodes on
which the components of a software system execute.


10 ooad uml-13

Empfohlen

Empfohlen

Weitere ähnliche Inhalte

Was ist angesagt?

Was ist angesagt? (20)

Andere mochten auch

Andere mochten auch (15)

Ähnlich wie 10 ooad uml-13

Ähnlich wie 10 ooad uml-13 (20)

Mehr von Niit Care

Mehr von Niit Care (20)

Kürzlich hochgeladen

Kürzlich hochgeladen (20)

10 ooad uml-13

Hinweis der Redaktion