Construction

IF2261 Software Engineering
OOSE - Construction
Program Studi Teknik Informatika STEI ITB
IF-ITB/YW/Revisi: April 2006 IF2261 OOSE - Construction
Page 1
Why do we have a construction process ?

The analysis model is not sufficiently formal The actual system must be adapted to the implementation environment We want to validate the analysis result
Page 2
What is done in the construction phase ?

Identify the implementation environment
n
Identifying and investigating the consequences that the implementation environment will have on the design
Incorporate these conclusions and develop a first approach to a design model Describes how the objects interact in each specific use case
IF-ITB/YW/Revisi: April 2006 IF2261 OOSE - Construction Page 3
The Design Model

Refine the analysis model in the light of the actual implementation environment
n n
Define interface of the objects Define semantics of the operation
Decide how different issues such as DBMS, programming language features, and distribution will be handled Compose of blocks which are the design objects
n n
The block will abstract the actual implementation The implementation of the blocks may be:
one specific class in the source code several different classes
Page 4
Building a design model

First attempt can be made mechanically
n n
based on the analysis model obtain a clear traceability to the analysis model The analysis model: developed in logical terms and is only a conceptual picture of the system to be built The design model: an abstraction of how the actual system really is built
The Analysis Model vs The Design Model

n
The final structure should reflect how the implementation environment has affected construction
n
For example, if the programming language does not support inheritance, the model must reflect how the inheritance is really implemented
The Analysis Model Example Recycling Machine System
Alarmist extends Receipt Printer
Alarm Device
Customer Panel
Deposit item receiver
Operator Panel
Report Generator Receipt Basis Deposit Item inherits inherits inherits
Cans
Bottles Crates
Page 6
First attempt of the Design Model Example Recycling Machine System
Alarmist extends Receipt Printer
Alarm Device
Customer Panel
Operator Panel
Cans
Bottles Crates
Page 7
The Design Model - Implementation Environment

Identify the actual technical constraints under which the system should be built Including:
n n n
The target environment Programming language Existing products that should be used (DBMSs, etc) As few objects as possible should be aware of the constraints of the actual implementation environment
Strategies:
n
Page 8

Target environment
n
Create a new blocks that represent occurrences of the changed parts in the target environment
Strategies:
n
Specified an abstract class polymorphism The object can check the platform at run-time CASE statement in the source code Decide this when the system us delivered Provide several different modul which will be choosed later
Investigate whether the target environment will execute in a distributed way

on a different processors or different processes
Page 9
Example Adapting the target environment

Application objects
File Manager
MS-DOS
UNIX
MacOS
Page 10

Programming language
n n
Affect the design in translating the concepts used The basic properties of the language and its environment are fundamental for the design
Inheritance and Multiple inheritance Typing Standard Portability Strategies for handling errors during run-time
n n n
Exception (Ada) Assertions (Eiffel) None (C++ ver 2) Automatic garbage collection
Memory management
n
The use of component

Component library, such as interface objects IF-ITB/YW/Revisi: April 2006 IF2261 OOSE - Construction Page 11

Using existing products
n n n n
DBMS UIMS (User Interface Management System) Network facilities Internally or externally developed applications that should be incorporated Products used during development
Compilers Debuggers Preprocessor
Other considerations
n n
Requirement for performance Limitations of memory

Other considerations
n
Strategies:
To postpone optimizations until they are needed or you are absolutly sure that they will be needed
n
the real bottlenecks are often missed and then new optimizations are necessary
Use simulation or prototyping to investigate potential optimization problem early

n
Extensive experiences may help to jugde at an early stage
If youre not sure of the correctnessof a performance optimizations, you should not make it untill youre sure of how it should be done
The people and organization involved in the development could also afect the design
n
The principal strategy:

such factors should not affect the system structure. The reason: the circumtances (organizations, staffing, competence areas) that are in effect today will probably change during the systems life cycle
Page 14
Working with the design model

Changes can and should occur, but all changes should be justified and documented (for robustness reason) We may have to change the design model in various way:
n
n n
To introduce new blocks which dont have any representation in the analysis model To delete blocks from the design model To change blocks in the design model (splitting and joining existing blocks) To change the associations between the blocks in the design model
Use the component

Working with the design model (2)

Adding blocks
n n
Adding blocks to handle the environment is a good change Adding blocks for other functionality should not normally be done, since they should introduced through the analysis model More suspicious You have to have good reasons for it (often implementation reasons) Changing the logical structure of the system should be made in the analysis model first Also suspicious changes Will often decrease the robustness of the system Should be done with a great care
Deleting blocks
n n
Splitting and joining blocks

n n n
Working with the design model (3)

Changes associations
n n
The most common change in the design model Often come from the implementation environment
Synchronization and communication between processes Actual implementation of association
n n
Extension association has no direct implementation technique Inheritance associations
Page 17
Example Change Association extends assc. communication assc.
b1
b1
extends
b2
b2
Page 18
Working with the Design Model Example Recycling Machine System
Alarmist
Alarm Device
Receipt Printer
Customer Panel
Operator Panel
Cans
Bottles Crates
Page 19
Use the component

At an early stage, it is essential to decide upon which component libraries
n
When a component library exist, investigations should begin to find out what functionality it will offer It is essential to be familiar with the library
Rule of thumb for finding places where components could be used

n
Look for acquaintance association with cardinalty [0..N]

This will typically yield a list or array to hold several references
Page 20
10
Example the use of component

E[0..M] C itemList[1] C
LinkedList
ihs
Link
Receipt basis
ReturnedItem[1]
Inserted Item
Deposit Item
Page 21
Interaction Diagram
Describe how the blocks are to communicate by designing the use case The main purpose of the use case design is to define the protocols of the blocks The interaction diagram describes how each use case is offered by communicating objects
n n n
The diagram shows how the participating objects realize the use case through their interaction The blocks send stimuli between one another All stimuli are defined including their parameters
For each concrete use case, draw an interaction diagram

11
Building an interaction diagram

Identify blocks Draw skeleton, consist of:
n n
System border Bars for each block that participates Structured text or pseudo-code
Describes the sequences

n
Mark the bar to which operations belongs with a rectangle representing operation Define a stimulus Draw a stimulus as a horizontal arrow
n n
Start: bar of the sending block End: bar of the receiving block Fork diagram Stair diagram
Structure the interaction diagram

n n
The Skeleton for The nteraction Diagram

System Border Customer Panel Deposit Item Receipt Receiver Basis Deposit Item Receipt Pinter
Time Page 24
12
Example Interaction Diagram for Use Case Returning Item

System Customer Deposit Item Receipt Border Panel Receiver Basis
Customer presses the start button The sensors are activated DO new deposit item is inserted measure and check if this kind of item is acceptable noReceived := noReceived + 1 IF not found THEN create new daily amount := daily amount + 1 WHILE items are deposited
Deposit Item
Page 25
Example Interaction Diagram for Use Case Returning Item

System Customer Deposit Item Border Panel Receiver
Customer presses the start button The sensors are activated DO new deposit item is inserted measure and check if this kind of item is acceptable IF not found THEN create new daily amount := daily amount + 1 noReceived := noReceived + 1 WHILE items are deposited start activated create
Receipt Basis
Deposit Item
new item Item() insertItem (item)
exist() incr
Page 26
13
Structure of interaction diagrams

Fork
n n
indicates a centralized structure and is characterized by the fact that it is an object controls the other objects interacted with it. This structure is appropriate when:
The operations can change order New operations could be inserted
Stair
n n
indicates decentralized structure and is characterized by delegated responsibility. Each object only knows a few of the other objects and knows which objects can help with a specific behavior. This structure is appropriate when:
The operation have a strong connection. Strong connection exists if the objects:
n n n n
form a consist-of hierarchy form an information hierarchy form a fixed temporal relationship form a (conceptual) inheritance relationship
The operation will always be performed in the same order IF-ITB/YW/Revisi: April 2006 IF2261 OOSE - Construction
Page 27
Use Case with extension

Described by a probe position in the interaction diagram The probe position indicates a position in the use case to be extended
n
Often accompanied by a condition which indicates under what circumstances the extension should take placed
Page 28
14
Example Probe position

System Customer Border Panel
PROBE: In use case Returning Item when measuring the Deposit Item, the Item stuck Start the alarm
Alarmist
Alarm device
stuck
Alarm Alarm activate
Activate Alarm device
Wait for error to be fixed Error removed Error fixed Turn off the alarm Back to normal insertion reset Alarm fixed
Page 29
Homogenization
In parallel design process, several stimuli with the same purpose or meaning are defined by several designers. These stimuli should be consolidated to obtain as few stimuli as possible.
n
Called homogenization.
Page 30
15
Example - Homogenization
What_is_your_phone_number? Where_do_you_live? Get_address Get_address_and_phone_number
Homogenized into:
Get_address Get_phone_number
Page 31
16

Construction

Загружено:

Сведения о документе

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Construction

Загружено:

Авторское право:

Доступные форматы

IF2261 Software Engineering

Program Studi Teknik Informatika STEI ITB

IF-ITB/YW/Revisi: April 2006 IF2261 OOSE - Construction

Why do we have a construction process ?

IF-ITB/YW/Revisi: April 2006 IF2261 OOSE - Construction

What is done in the construction phase ?

The Design Model

Define interface of the objects Define semantics of the operation

IF-ITB/YW/Revisi: April 2006 IF2261 OOSE - Construction

Building a design model

The Analysis Model vs The Design Model

The Analysis Model Example Recycling Machine System

Alarmist extends Receipt Printer

Deposit item receiver

Report Generator Receipt Basis Deposit Item inherits inherits inherits

IF-ITB/YW/Revisi: April 2006 IF2261 OOSE - Construction

First attempt of the Design Model Example Recycling Machine System

Alarmist extends Receipt Printer

Deposit item receiver

Report Generator Receipt Basis Deposit Item inherits inherits inherits

IF-ITB/YW/Revisi: April 2006 IF2261 OOSE - Construction

The Design Model - Implementation Environment

IF-ITB/YW/Revisi: April 2006 IF2261 OOSE - Construction

The Design Model - Implementation Environment

Investigate whether the target environment will execute in a distributed way

IF-ITB/YW/Revisi: April 2006 IF2261 OOSE - Construction

Example Adapting the target environment

IF-ITB/YW/Revisi: April 2006 IF2261 OOSE - Construction

The Design Model - Implementation Environment

The use of component

The Design Model - Implementation Environment

Requirement for performance Limitations of memory

The Design Model - Implementation Environment

Use simulation or prototyping to investigate potential optimization problem early

Extensive experiences may help to jugde at an early stage

The Design Model - Implementation Environment

The principal strategy:

IF-ITB/YW/Revisi: April 2006 IF2261 OOSE - Construction

Working with the design model

Use the component

Working with the design model (2)

Splitting and joining blocks

Working with the design model (3)

Extension association has no direct implementation technique Inheritance associations

IF-ITB/YW/Revisi: April 2006 IF2261 OOSE - Construction

Example Change Association extends assc. communication assc.

IF-ITB/YW/Revisi: April 2006 IF2261 OOSE - Construction

Working with the Design Model Example Recycling Machine System

Deposit item receiver

Report Generator Receipt Basis Deposit Item inherits inherits inherits

IF-ITB/YW/Revisi: April 2006 IF2261 OOSE - Construction

Use the component

Rule of thumb for finding places where components could be used

Look for acquaintance association with cardinalty [0..N]

IF-ITB/YW/Revisi: April 2006 IF2261 OOSE - Construction

Example the use of component

IF-ITB/YW/Revisi: April 2006 IF2261 OOSE - Construction

For each concrete use case, draw an interaction diagram

Building an interaction diagram

Describes the sequences

Structure the interaction diagram

The Skeleton for The nteraction Diagram

IF-ITB/YW/Revisi: April 2006 IF2261 OOSE - Construction

Example Interaction Diagram for Use Case Returning Item