|Lesson 5||Course project: Create UML Exercises |
|Objective||Fundamental components of inventory control system project |
UML Course Project
Identify the fundamental components of the inventory control system project that will be used throughout the course.
To provide a hands-on opportunity to explore the diagramming techniques, we will work on modeling an inventory control system.Although you will not be able to build a complete model, there will be ample opportunity to try the UML modeling notation in a
reasonably realistic setting.
Inventory control system
The goal is to build at least one of each type of diagram to model the functionality of an inventory control system.
Beginning at user requirements and progressing through logical modeling of classes and objects and their interactions, you will proceed to process modeling, component definition, and finally installation. In each module, we will identify the use of each diagram and the notation used to express the model fully.
In the next module, the four classifications of the models included in the UML will be discussed.
One prepare UML diagrams to understand a system in better and simple way.A single diagram is not enough to cover all aspects of the system Sand UML defines different kinds of diagrams to cover most aspects of a system.
One can also create a set of diagrams to meet your requirements. Diagrams are generally made in an incremental and iterative way.
There are two broad caetgories of diagrams
- Structural Diagrams
- Behavioral Diagrams
Poor communication leads to delays and extra cost
As systems change, all project participants must keep informed of the nature and impact of those changes on the requirements and solutions already in progress or already implemented.
Without a standard way to communicate, everyone is left to his own creativity. You have probably seen teams where more time is spent in meetings than actually working. The meetings use up valuable time in an effort to communicate. One person uses flowcharts; another person uses screen layouts; others use volumes of written specifications. The project incurs the overhead of becoming familiar with a variety of communication styles and techniques.
Meanwhile, individual developers who need to apply badly needed changes have to instead labor with widely varied types of documentation to try to understand and repair complex systems. In a straw poll that I conduct in each class, students are asked how they handle a request to change an existing system when the documentation is difficult to understand or non-existent. Almost without exception, the students say they simply rewrite the code. For those of you managing the budget, that means that they are throwing away a corporate asset simply because they cannot understand it and did not have the time to try. Then they are spending more time creating an entirely new and untried solution than they would in making a simple correction if they only knew where to make it.
Translation: Poor communication = slower projects and higher cost of maintenance
Course Project - Exercise