There is no such thing as a perfect system.

There are number of tools that allow us to get the best system design.
Tools: UML and Unified Process

UML is modeling language, standardizing the way people communicate with each other
irrespective of their background.
Unified Process: is accompanying methadology to UML (a way to guide along software
projects).

Unified Process Steps:

1) Inception: Evaluate Dos and Don'ts. (Budget considered as well)
2) Elaboration: Use of UML
3) Construction: Coding and testing.
4) Transition: Deployment.

UP makes sure that UML turns out to be the one we need and no extra time is wasted
on diagramming for no reason.

In Unified Process workflow is based on iterations. Iterations: Period of time

fixed/always the same everytime it happens that allow a planning phase at the
beginning of each iteration.
In Unified Process we never build a project that is 100% upfront, every iteration
allows time for general reflection and integration of feedback from users and team
members.
This allows program to responds to needs as they arise.

-> Inception: Whether the project is worth doing? 1. Budget 2. Duration

(unreasonable) 3. Feasibility
Shouldn't take more than week or two.

----> Lifecycle Object Milestone

-> Elaboration: 1) Write use cases, diagram use cases. 2) Map out domain model.

What we have after Elaboration:

- Core Architecture
- Relatively Accurate Schedule
- Risky Elements on your radar
- A ton of user and stakeholder feedback
- Uses Cases
- Started Domain Model

----> Lifecycle Architecture Milestone

-> Construction: Code and testing.

----> Initial Operational Capability Milestone

-> Transition: Projet is released to end users (deployed)

----> Product Release Milestone

At this point quality assurance is paramount (more important)

===
UML
===

Unified means the languge is standardized. (can be used for any scenario).
Modeling because we represent it as diagrams.
Language means standardized communication system.

14 UML Diagrams (We don't need all of them)

2 Categories

Behavorial:
1) Use Case
2) Activity
3) State
4) Communication
5) Interaction Overview
6) Timing
7) Sequence

Techincal:
1) Class
2) Component
3) Object
4) Package
5) Composite
6) Component
7) Profile

========
USE CASE (somewhere inception and elaboration)
========
A story: system possibilities, types of interactions

4 Elements: Actors, Use Cases, Subjects, Include and Extend Relationships