Standard UML Usage
In most cases, UML will be used for the purpose of analyzing and designing software programs. There are a number of variations within the object oriented analysis world, but many of them have goals which are more or less identical.
Object oriented analysis typically wish to define the primary usage scenarios which exist for the system, but from the view point of distinct users.
Object oriented analysis variations also wish to define the interactions which exist among both the system as well as the user, particularly when it comes to the execution for the usage scenario, which means the actions that are carried out by the user, and the manner in which the system responds to these actions.
Most variations will also give responsibility for any outcomes which are related to the appropriate objects inside the system.
Once you understand the manner in which the objects are involved, and the ways in which the objects handle the execution for the scenario, then you have the key information which can allow you to begin implementing the code which is necessary for the satisfaction of the scenario.
A lot of project teams make the error of trying to deal with both the analysis along with the design for the system scenarios prior to the start of the coding. This action is referenced by the acronym BDUF, or big design up front. The problem with this action is that with all the product design processes, there is a possibility that you may get things wrong.
If you do not make use of the proper amount of testing as well as feedback, then your final design may be heavily flawed.
One misconception which is typically made in regards to UML and OOAD is that you must use a finished design to properly write the code. The truth of the matter is that you do not. All that is necessary is for you to have enough data to get started on the design.
When it comes to the implementation as well as the design for the software scenarios, the users must provide the proper feedback for the end product, since this is the right way of creating a superior design. This naturally leads us to the question of how we can properly use UML within the basic analysis and process for design. To begin with, you will need to model the user types and purposes that they will use the software for.
How UML can be Utilized
When it comes to software projects, there is always the possibility that there will not be enough resources or time to completely finish each feature prior to the deadline. It is critical that customers for the project prioritize the scenarios for usage, and these are referred to as being the use case scenarios.
You must keep in mind that the most critical functionality must be handled sooner within the schedule. This way, if you only have enough time to finish 80 percent for the functionality, you will have finished the 80 percent which is the most crucial.
The analysis and the design functions through the usage of the use case scenarios each time, beginning with the most important. To function, you must know how to describe the way the user and the system will interact with each other.
It is important not to make the error of only committing yourself to a specific user type, and the reason for this is because it will have you chained down to a single solution, and it can become very challenging to comprehend the business logic which is associated with the interactions.
The essential use case scenario must be responsible for showcasing the interactions which occur within abstract terms, and it must make things clear with who is handling what, as well as the flow for this scenario.
It is also important to keep in mind that the way in which you describe the use case scenario will be responsible for the description of the interaction design which is connected to the software. Many people error by attempting to handle the description in the form of requirements, and do not see the need to change them when needed.