OOSE - Anaysis - Analysis Model

8/9/2019 OOSE - Anaysis - Analysis Model

1/26

20/09/2006 SE6161 Analisis dan Perancangan Perangkat Lunak 1Slide 1

OOSE Analysis

Analysis Model


2/26


3/26

SE6161 Analisis dan Perancangan Perangkat Lunak20/09/2006 Page 3

The dimensions of The dimensions of the analysis modelthe analysis model

Behaviour

Information

Presentation


4/26


OOSE Analysis ModelOOSE Analysis Model

Control objectA control object illustrates functionality that isnot contained in any other object in the

system.

Interface objectInterface objects interact directly with theenvironment.

Entity objectInformation about an entity object is stored

even after a use case is completed.

Analysis Model


5/26


Interface ObjectInterface ObjectAll functionality specified in the use case description that

is directly dependent on the system environment is placedin interface objectsActors communicate with the system through these objects

The task is to translate the actors input to the system intoevents in the system, and to translate these events intosomething which is presented to the actor Having identified interface objects, it will be easy tomodify an interface in the system

this is a common situation that must be manageable


6/26


Strategies in finding interface objectsStrategies in finding interface objects

Identified from the system interface descriptionaccompanying the requirement models

Start from the actorsRead the use case description and extract thefunctionality that is interface-specific


7/26


ExampleExample Use CaseUse Case DecriptionDecriptionUse Case Returning ItemUse Case Returning Item

When the customer returns a deposit item , it is measured by the system. The

measurements are used to determine what kind of can, bottle or crate has beendeposited. If accepted, the customer total is incremented, as is the daily total for that specific item type. If the item is not accepted, the lights for NOT VALID ishighlighted on the panel .When the customer pressed the receipt button , the printer prints the date . Thecustomer total is calculated and the following information printed on the receiptfor each item type:

Name Number returnedDeposit valueTotal for this type

Finally the sum that the customer should receive is printed on the receipt .


8/26


Recycling Machine SystemRecycling Machine SystemInterface ObjectInterface Object ExampleExample

Receipt Printer Operator Panel

Alarm Device

Customer Panel Customer Customer

Receipt receiver

ihs ihs


9/26


Association between interface objectsAssociation between interface objects

Interface objects must know of each other to be able tosolve certain task Acquaintance association

Solid directed line (uni directional)Having name and cardinality

Cardinality:

Says how many instances can be associated


10/26


11/26


Association between interface objects (2)Association between interface objects (2)

Consist of associationAggregateContainment hirarchy

Central interface


12/26


Interface ObjectInterface Object ExampleExampleCentral InterfaceCentral Interface

Receipt button Can slotBottle slot

Crate slot

Customer Panel

receipt button[1]

cans[1]

bottles[1]

crates[1]


13/26


Interface object typeInterface object typeInterface to other system

Translates to a standardized protocolJust sends out stimuli without any complex conversion

Advantages:

If the protocol changes, these changes will be local to this object

Interface to a human user Often request GUI

In interface-intensive application, interfaces object could be themajor part (up to 80%) of entire application

Use supporting tools


14/26


15/26


16/26


Strategies in finding entity objectsStrategies in finding entity objectsIdentified from the use case description

Most are found early and obviousIts easy to find entity object, but more difficult to identifyits operations and attributes

In nomal case, operations are not identified in the analysis model(but later in the design model)Typical operations that must be offered by an entity object:

creating and deleting the entity object

storing and fetching information behavior that must be changed if the entity object is changed


17/26


18/26


Entity ObjectEntity Object ExampleExampleRecycling Machine SystemRecycling Machine System

Deposit Item

Bottles CratesCans

inheritsinheritsinherits

Receipt Basis

Item[0..N]


19/26


Association between entity objectAssociation between entity object

Communication associationThe entity object contact another entity object and asksfor information about something

Deposit ItemReceipt Basis


20/26


Control ObjectControl ObjectUsed to model behavior that is not naturally placed in either of another two objects (interface and entity)

Usually needed in more complex use casesTypically acts as glue which unites the other objects

Normally found directly from the use casesIn the preliminary draft, assign one control object for each use case

Deviation from the initial approach can be made for several reason:In the case where there is no behavior in the use case left to model, then thecontrol object is not needed.In the case of a very complicated behavior, the functionality may be dividedinto several control objects

Typical type of functionality placed in the control objects aretransaction-related behavior, or control sequences specific to one or a few use cases, or functionality thas separates the entity objects from the interface objects .


21/26


ExampleExample Use CaseUse Case DecriptionDecriptionUse Case Returning ItemUse Case Returning ItemWhen the customer returns a deposit item, it is measured bythe system. The measurements are used to determine whatkind of can, bottle or crate has been deposited. If accepted,the customer total is incremented, as is the daily total for thatspecific item type. If the item is not accepted , the lights for NOT VALID is highlighted on the panel.When the customer pressed the receipt button , the printer prints the date. The customer total is calculated and thefollowing information printed on the receipt for each item type:

Name

Number returnedDeposit valueTotal for this type

Finally the sum that the customer should receive is printed on

the receipt.


22/26


Control ObjectControl Object ExampleExampleRecycling Machine SystemRecycling Machine System

Deposit item receiver

Alarmist

Report Generator

Information Administrator


23/26


Working with the analysis objectsWorking with the analysis objects

Deposit item receiver

Alarmist

Report Generator

Information Administrator

extends


24/26


Analysis ModelAnalysis Model

ExampleExample

Recycling Machine SystemRecycling Machine System Use Case Returning ItemUse Case Returning Item

Deposit Item

Bottles CratesCans

inheritsinheritsinherits

Receipt Basis

Deposit item receiver Customer Panel Receipt Printer Item [0..N]


25/26


26/26


SubsystemSubsystem ExampleExample -- Recycling Machine SystemRecycling Machine System

Deposit Item

Bottles CratesCans

inheritsinherits

inherits

Receipt Basis

Deposit item receiver Customer Panel

Receipt Printer

Report Generator

Operator Panel

Alarmist Alarm Device

extends

Deposit Administration

Alarm

OOSE - Anaysis - Analysis Model

Documents

Transcript of OOSE - Anaysis - Analysis Model