2. Project Organization
• The Statewide Traffic Analysis and Reporting
System (STARS) is a full life cycle development
project
• Consistent with the original Request for Offer, the
STARS Project has been divided into two phases
• Phase I of the project has been focused on the
planning, requirements definition, and system
design of STARS
IntroductionIntroduction
3. Project Organization
• To accomplish its overall planning objective, the
initiation and elaboration phase of the project was
organized into the following three stages:
Project Initiation Stage
Requirements Definition Stage
System Design Stage
IntroductionIntroduction
4. Project Organization
• Phase II of the project, the construction and
transition phase, will be focused on the
implementation, testing, and deployment of an
innovative solution based upon the results of the
first phase
• These results include major stage deliverables,
many of which are directly or indirectly traceable to
the detailed business objectives documented in the
STARS Project Management Plan
IntroductionIntroduction
5. Project Organization
• The anticipated conclusion of the System Design
Stage in early Fall 2002 signals the completion of
Phase I of the STARS Project
• The success of this phase is in large part
attributable to the software engineering process
utilized by the STARS Project Development Team
IntroductionIntroduction
6. STARS Software Engineering Process
• STARS software engineering process is a variation
of the Rational Unified Process (RUP)
• RUP is a generic business process for object-
oriented software engineering
• Its goal is to ensure the production of high-quality
software that meets the needs of its end users,
within a predictable schedule and budget
Process OverviewProcess Overview
7. The Rational Unified Process
• Describing RUP as a generic business process
directly implies that the process is adaptable for a
wide range of projects and organizations
• Furthermore, the process can be adopted in whole
or in part at either a project or enterprise level
• Adopting RUP in part directly implies that the
process can be adapted to incorporate important
components of an existing legacy software
engineering process
Process OverviewProcess Overview
8. The Rational Unified Process
• At a project level, it can be implemented at any time
within the software life cycle with appropriate
planning
• Its adaptability is derived from a process
architecture that provides a disciplined approach
for assigning tasks and responsibilities
• Its success is based upon its incorporation of
modern software development best practices into its
process architecture
Process OverviewProcess Overview
9. Software Engineering Best Practices
• Modern software development best practices that
have been incorporated into RUP include:
Develop Iteratively
Manage Requirements
Use Component Architectures
Model Visually (UML)
Continuously Verify Quality
Manage Change
Process OverviewProcess Overview
10. A Use Case Driven Process
• Consistent with RUP, STARS software engineering
process is a use case driven process
• This characterization is based on the understanding
that the behaviors, as well as the business and
functional requirements that the application must
support, are captured in the Software Requirement
Specification’s (SRS) Use Case Model
• Traceability ensures that business requirements will
be satisfied and helps to define project success
STARS Use CasesSTARS Use Cases
11. Use Case Model
• A Use Case Model describes a system’s functional
requirements in terms of use cases
• It is comprised of use case diagrams and use cases
• Use case diagrams shows the relationship among the
actors and the use cases within a system
• These diagrams are created using the unified
modeling language (UML) supported by a tool like
Rational Rose
STARS Use CasesSTARS Use Cases
16. Use Case Model
• A use case provides a description of system
behavior, in terms of sequences of actions
• Actors, which are external to the system and define
its boundaries, interact with the system through the
use cases
• A use case should yield an observable result of value
to an actor, which is captured in the use case’s Post-
Condition
STARS Use CasesSTARS Use Cases
17. Use Case Model
• A use case contains the primary flow and all
alternate, warning, and exception flows
• Each statement that comprises the various ‘flow of
events’ should describe a complete ‘round trip’
“The actor does this and the system does
that in response” or
“The system does this and the actor does
that in response”
STARS Use CasesSTARS Use Cases
18. Use Case Model
• This ‘black box’ approach ensures that the focus is
on the system’s functional requirements, or What
the system is supposed to do, and not the HOW
• The HOW is addressed through analysis and design
utilizing the use case realization process
STARS Use CasesSTARS Use Cases
