CHAPTER 4

ELABORATION PHASE
ELABORATION PHASE
• Objectives
• Stable requirements, architecture, and
plans.
• Executable architecture prototype(s).
• Baseline architecture, vision and plans.
• Completion of engineering for the
project.
2
• Activities
• Elaborating the vision.
• Establishing the critical use cases.
• Elaborating the process and
infrastructure.
• The construction process, the tools and
automation support, and the intermediate
milestones and evaluation criteria.
• Elaborating on the architecture and
selecting components.
• Complete component make/buy, and
component integration.
• Assessment against primary scenarios.
ELABORATION PHASE 3
OBJECTIVES OF ELABORATION PHASE 4

Get a more detailed understanding of the

requirements

Design, implement, validate, and baseline the

architecture.

OBJECTIVES
Mitigate essential risks, and produce more accurate
schedule and cost estimates.

Refine the development case and put the

development environment in place.
OBJECT ORIENTED MODELS - BUSINESS PROCESS 5
MODELING

• ACTIVITY DIAGRAM
• USE-CASE DIAGRAMS & USE-CASE DESCRIPTION
• CLASS DIAGRAMS
• SYSTEM SEQUENCE DIAGRAM
ACTIVITY DIAGRAM 6

• Activity diagrams describe the workflow behavior of a system.

• Activity diagrams are used in process modeling and analysis during
requirements engineering.
• A typical business process that synchronizes several external
incoming events can be represented by activity diagrams.

• They are most useful for understanding workflow analysis of

synchronous behaviors across a process.
ACTIVITY DIAGRAM 7

• Activity diagrams are the object-oriented equivalent of flow charts

and data-flow diagrams from structured development.
• The process flows in the system are captured in the activity diagram.
• Activity diagram illustrates the dynamic nature of a system by
modeling the flow of control from activity to activity.
ACTIVITY DIAGRAM 8

• Activity diagrams are used for

• documenting existing process
• analyzing new Process Concepts
• finding reengineering opportunities.

• The diagrams describe the state of activities by showing the sequence

of activities performed.
• they can show activities that are conditional or parallel.
ACTIVITY DIAGRAM CONCEPTS 9
• An activity is trigged by one or more events and activity may result in
one or more events that may trigger other activity or processes.

• Events start from the start symbol and end with a finish marker having
activities in between connected by events.

• The activity diagram represents the decisions, iterations, and

parallel/random behavior of the processing.
• They capture actions performed.
• They stress on work performed in operations (methods). The
WHEN TO USE ACTIVITY DIAGRAMS ? 10

• The main reason to use activity diagrams is to model the workflow behind the
system being designed.

• Activity Diagrams are also useful for:

• analyzing a use case by describing what actions need to take place and when
they should occur
• describing a complicated sequential algorithm
• modeling applications with parallel processes

• Activity diagrams do not give detail about how objects behave or how objects
collaborate.
COMPONENTS 11

• An activity is an ongoing, though interruptible, execution of a step in a

workflow (such as an operation or transaction)
• Represented with a rounded rectangle.
• Text in the activity box should represent an activity (verb phrase in
present tense).
 12
COMPONENTS
• An event is triggered by an activity. It specifies a significant occurrence that has a
location in time and space.
• An instance of an event (trigger) results in the flow from one activity to another.
• These are represented by directed straight lines emerging from triggering activity
and ending at activity to be triggered. Label text for events should represent
event but not the data involved.

• A decision may be shown by labeling multiple output transitions of an activity with

different guard conditions.
• For convenience a stereotype is provided for a decision: the traditional diamond
shape, with one or more incoming arrows and with two or more outgoing
arrows, each labeled by a distinct guard condition with no event trigger.
HOW TO DRAW AN ACTIVITY DIAGRAM 13
• Diagrams are read from top to bottom and have branches and forks to describe
conditions and parallel activities.
• A fork is used when multiple activities are occurring at the same time.

• A branch describes what activities will take place based on a set of conditions.

• All branches at some point are followed by a merge to indicate the end of the
conditional behavior started by that branch.

• After the merge all of the parallel activities must be combined by a join before
transitioning into the final activity state.
 14
ACTIVITY DIAGRAM : NOTATIONS
ACTIVITY DIAGRAM : NOTATIONS 15
 16
SWIMLANE
ACTIVITY DIAGRAM : 17
SYMBOLS Start State
Fork Activity

Branch
Style 1 : If you have
only ONE actor

Merge Join

End State
 18
EXAMPLE
ACTIVITY DIAGRAM : 19
EXAMPLE

Style 2 : If you have

More than ONE actor
 20
HOW TO DRAW AN ACTIVITY DIAGRAM?

• Step 1: Figure out the action steps from the use case
• Step 2: Identify the actors who are involved
• Step 3: Find a flow among the activities
• Step 4: Add swimlanes
ACTIVITY DIAGRAM : EXAMPLE 1 – CREATING
DOCUMENT
• 1. Open the word processing
package.
• 2. Create a file.
• 3. Save the file under a unique
name within its directory.
• 4. Type the document.
• 5. If graphics are necessary, open
the graphics package, create
the graphics, and paste the
graphics into the document
21
 6. If a spreadsheet is necessary,
open the spreadsheet package,
create the spreadsheet, and
paste the spreadsheet into the
document.
 7. Save the file.
 8. Print a hard copy of the
document.
 9. Exit the word processing
package.
ACTIVITY DIAGRAM 22
– EXAMPLE 1
ACTIVITY DIAGRAM : EXAMPLE 2 – PROCESSING AN 23
ORDER
ACTIVITY DIAGRAM : EXAMPLE 2 – PROCESSING 24
AN ORDER – EXPLANATION OF THE DIAGRAM

• Once the order is received the activities split into two parallel sets of activities.
• One side fills and sends the order while the other handles the billing.
• On the Fill Order side, the method of delivery is the Fill Order side, the method of
delivery is decided conditionally.
• Depending on the condition either the Overnight Delivery activity or the Regular
Delivery activity is performed.
• Finally the parallel activities combine to close the order.
ACTIVITY DIAGRAM : EXAMPLE 3 – A BUSINESS 25
PROCESS OF MEETING A NEW CLIENT

• A salesperson calls the client and sets up an appointment.

• If the appointment is onsite (in the consulting firm's office), corporate technicians prepare a conference room for
a presentation.
• If the appointment is offsite (at the client's office), a consultant prepares a presentation on a laptop.
• The consultant and the salesperson meet with the client at the agreed-upon location and time.
• The salesperson follows up with a letter.
• If the meeting has resulted in a statement of a problem, the consultant creates a proposal and sends it to the
client.
ACTIVITY DIAGRAM : 26
EXAMPLE 3 – SAMPLE
ANSWER – LET’S
CHECK!
ACTIVITY DIAGRAM : EXERCISE – ENROLLMENT IN A 27
UNIVERSITY

• An applicant wants to enroll in the university.

• The applicant hands a filled-out copy of form U113 University Application Form to the
registrar.
• The registrar inspects the forms.
• The registrar determines that the forms have been filled out properly.
• The registrar informs students to attend in university overview presentation.
• The registrar helps the student to enroll in seminars.
• The registrar asks the student to pay the initial.