You are on page 1of 3

1.

Early requirements from Inception


phase are
Solidified and more rigor is added to
1. Discovery phase, the process.
2. Time for solidifying 2. Details the dynamic nature of the
project charter application
3. Clear understanding of 3. Attempts to model the actual uses of
what features project the system anticipated by project
will implement sponsors.

1. Static and dynamic perspectives of


1. Components produced in the the application are realized
Construction phase are packaged 2. In the form of a language E.g VB
into deployable units. 3. And a form of persistent storage
2. Details the support issues that (for example, Oracle)
surround the application
3. How the project will be maintained
in a production environment
Visual Basic

Simple Base Types Complex object Types


String Class:Order Subclass:OrderHeader
Boolean Class:Customer Subclass:OrderLine
Long Class:InVoice Here OrderHeader and
OrderLine are variables of
“Order”
Once “myorder” object is
created, messages can be
In Runtime, Variables are
sent to it and myOrder
used to create actual Object
will respond, provided
Instances and to Serve
that the operation is
recipients’ message
supported by myOrder's
interface.
Application Goals

Major Pathway1 Major Pathway2

Sequence Diagram
E.g, When the Customer object wants each of its Order
objects to perform the operation calcTotalValue, it
Logically Stated Usecase
sends a message.
Each message requires the receiver object (the Order) to
have an operation defined to honor the request.
Dynamic Collaboration b/w Operations all end up in a class somewhere.
Runtime Objects These classes eventually are used to generate code into
the VB environment.

You might also like