UML is essential for modeling because by using it in analysis and design, you can achieve and grasp better understanding with regards to the factors that need to be consider in satisfying the specified requirements in making a high quality system. As it is described and defined in the factsheets.
The Unified Modeling Language (UML) is the de facto standard language for modeling object-oriented software systems.
In particular UML is becoming extremely popular as a modeling language for object-oriented systems. In order to manage the development process it is of crucial importance to be able to derive accurate quantitative knowledge from the software artifacts.
For me, the very basic reason why UML perhaps is organized and imposed is that these are the tools to really visualized the models with a pattern and create models in very convenient way!(Tina)
UML is a powerful tool that can greatly improved the quality of the systems analysis and design.(Harold)
Source:
http://www.jot.fm/issues/issue_2005_05/article2/
Wednesday, October 7, 2009
Summary of Steps in Putting UML into Work
There are steps that should be followed in putting UML into work . First, is defining the use case model. These includes the task of looking the actors behind and their triggered events. Then, develop use case diagrams to provide better understanding on how actors interact that will define the system. After that, consult some knowledgeable personnel such ac business area experts for verification. Second step will now follow, continue use case diagramming to model the system’s analysis phase.In this step, diagrams are numerous such as activity, use case,sequence and collaboration diagrams. Just like in the first step, you aregoing to consult some personnel for verification if your diagrams are acceptable. The third is developing class diagrams. It focuses more on relationships between classes. The fourth step which is drawing of statecharts diagrams that is used to aide in understanding complex processes that cannot be fully derived by sequence diagrams. The fifth step will now starts,which is you are going to start system’s design by refining UML diagrams for you to derive classes and their attributes and methods out of it. And now the last step , which is you are going to document your system design in a detail way. As it is said the more the complete information you provide the development through documentaion the faster the development and the more solid systemas as an output.
Deployment Diagram
A deployment diagram simply illustrates the physical implementation of the system as well as the hardware given its relationship with each other and the system which it is deployed.
Deployment diagrams show "the allocation of Artifacts to Nodes according to the Deployments defined between them."
In UML:
An artifact in the Unified Modeling Language (UML) is the specification of a physical piece of information that is used or produced by a software development process, or by deployment and operation of a system
A node In the Unified Modeling Language (UML) is a computational resource upon which UML artifacts may be deployed for execution.
Elements in Component Diagram:
1. Node: The element that provides the execution environment for the components of a system. Depicted by a cube with the name of the object in it, preceded by a colon, and underlined.
2. Connection: Similar to the relation/association used in class diagrams to define the interconnection between nodes.
Fg.3
A sample deployment diagram.
Source: http://en.wikipedia.org/wiki/Deployment_diagram
http://www.ifi.uio.no/in219/verktoy/doc/html/doc/user/mg/dgmsuml5.html
Difference of a component diagram from a class diagram
A class diagram shows the static features of the system but do not represent any particular processing. It is also present the nature of the relationship between each class.
A component diagram is similar to a class diagram but then it is more detailed one compares other UML Diagrams. Why? It is because of some reasons; first, this diagram shows every component of the system from a class file to a database and further; second, the same characteristic with a class diagram it shows how every component are related to each other.
A component is a distributable unit of software.
Fg.2
The component diagram allows you to combine deployment nodes with components to show which components run on each node (i.e. hardware).
Source: http://www.visualcase.com/kbase/component_diagram.htm
A component diagram is similar to a class diagram but then it is more detailed one compares other UML Diagrams. Why? It is because of some reasons; first, this diagram shows every component of the system from a class file to a database and further; second, the same characteristic with a class diagram it shows how every component are related to each other.
A component is a distributable unit of software.
Fg.2
The component diagram allows you to combine deployment nodes with components to show which components run on each node (i.e. hardware).
Source: http://www.visualcase.com/kbase/component_diagram.htm
Monday, October 5, 2009
Packages in UML
Packages are the containers for other UML things such as use case, classes or etc. It can be a logical packages or a component packages. It is used "to group elements, and to provide a namespace for the grouped elements".
The purpose of Packages in UML is for us to organize model elements into groups, making the UML diagrams simpler and easier to understand.
Fg.1
Figure 1 is an example of a use case package diagram. It composed of two use case; Withdraw Money and Deposit Money are part of Customer package.
source: http://en.wikipedia.org/wiki/Package_(UML)
The purpose of Packages in UML is for us to organize model elements into groups, making the UML diagrams simpler and easier to understand.
Fg.1
Figure 1 is an example of a use case package diagram. It composed of two use case; Withdraw Money and Deposit Money are part of Customer package.
source: http://en.wikipedia.org/wiki/Package_(UML)
Subscribe to:
Posts (Atom)
