UML Class Reviewing (1/4 31st Aug 2010)

Why is modeling important for developing software?

I understood the following reason why we should model.

1. Good to communication with stake holders
2. We can create high level design decision
3. To reduce risks
4. what/if analysis
5. To reuse the design component

First, Stake holders mean those influenced to the project like a developer, investor, customer and so on...
The developer should explain the project to develop the software as a business or an investigation.
When the stake holders and developer discuss, they should understand that software and share their idea collectly.

Second, if we skip the modeling, the project has to get less scale.
The huge project like OS, compiler, Office, etc, needs so many design decision.

Risks mean, bugs happening or misunderstanding among developers, for example.

what/if analysis means "if the object works in some condition, what happens?"
To analysis like this is necessary to understand how prduct performances and whether it satisfies the requirement.

We had better reuse the design of product or its components.
When then, the design should be visualized clearly to reuse it easily.

The better way to realize these is modeling.



What are the system structure?

• module
• Classes and their relations
• Real time interactions
• Data flow
• Deployment
• User interface
• etc..

Module means one functional part of software.
Class can symbolize one set which collects some objects and so on...
Classes or modules should interact earch other.
Classes and modules should be arranged at the each correct location.
User interface is the component which influence the user directly, for example, display(output design) and button(input form).



To design and model with drawing, the notation which simbolizes something should be unified.



That is what I learned in tha class.