Wednesday, October 7, 2009
Q5. importance of UML
UML is important for modeling in the sense that it emerged as the software blueprint methodology for the business and systems analysts, designers, programmers and everyone involved in creating and deploying the software systems in an enterprise. The UML provides for everyone involved in software development process as a common vocabulary to communicate about software design and analysis. Thus, very important in analyzing and designing a system.
Q4. steps
1. Define the use case model. These steps used use diagrams and scenarios to illustrate the main events and actors in connection with the system.
2.Continue UML diagramming to model the system during the systems analysis phase. In this step, you will used activity sequence and collaboration diagrams.
3. Develop the class diagrams. This step, represent the classes and relationships among objects.
4. Draw statechart diagrams. In this step,modify further on class diagrams.
5. Begin systems design by refining UML diagrams and using them to derive classes and their attributes and methods.
6. Document your system design in detail. This step is critical. The more complete the information you provide the development team through documentation in UML diagrams, the faster the development and the more solid the final production system.
2.Continue UML diagramming to model the system during the systems analysis phase. In this step, you will used activity sequence and collaboration diagrams.
3. Develop the class diagrams. This step, represent the classes and relationships among objects.
4. Draw statechart diagrams. In this step,modify further on class diagrams.
5. Begin systems design by refining UML diagrams and using them to derive classes and their attributes and methods.
6. Document your system design in detail. This step is critical. The more complete the information you provide the development team through documentation in UML diagrams, the faster the development and the more solid the final production system.
Q3. what is illustrated
- It is illustrated in the deployment diagram the physical configurations of software and hardware and the depict of a static view of the run-time configuration of processing nodes and the components that run on those nodes.
- In other words, deployment diagrams show the hardware for our system, the software that is installed on the hardware, and the middleware used to connect the separate machines to one another. This diagram is used for applications that are deployed to several machines.
- Also, deployment diagrams illustrate on how to explore the architecture of embedded systems and showing how the hardware and software components work together. In short, we may want to consider creating a deployment diagram for all but the most trivial of systems.
example of deployment diagram:
source: http://vinci.org/uml/deploymentx.html
The above diagram captures the distinct number of computers involved and shows the communication modes employed.Since,deployment diagram focuses on the physical implementation of the system.
- In other words, deployment diagrams show the hardware for our system, the software that is installed on the hardware, and the middleware used to connect the separate machines to one another. This diagram is used for applications that are deployed to several machines.
- Also, deployment diagrams illustrate on how to explore the architecture of embedded systems and showing how the hardware and software components work together. In short, we may want to consider creating a deployment diagram for all but the most trivial of systems.
example of deployment diagram:
source: http://vinci.org/uml/deploymentx.html
The above diagram captures the distinct number of computers involved and shows the communication modes employed.Since,deployment diagram focuses on the physical implementation of the system.
Q2. differences
component diagram - possess the physical analogs of class
- is more of a bird's eye view of the system and the component of the system
class diagram - show the classes of the system, their inter-relationships, and the operations and attributes of the classes
- gives an overview of a system by showing its classes and the relationships among them
- are static and they display what interacts but not what happens when they do interact.
example of component diagram:
source: http://www.sparxsystems.com.au/resources/uml2_tutorial/uml2_componentdiagram.html
The diagram above demonstrates some components and their inter-relationships. Assembly connectors "link" the provided interfaces supplied by "Product" and "Customer" to the required interfaces specified by "Order". A dependency relationship maps a customer's associated account details to the required interface; "Payment", indicated by "Order".
- is more of a bird's eye view of the system and the component of the system
class diagram - show the classes of the system, their inter-relationships, and the operations and attributes of the classes
- gives an overview of a system by showing its classes and the relationships among them
- are static and they display what interacts but not what happens when they do interact.
example of component diagram:
source: http://www.sparxsystems.com.au/resources/uml2_tutorial/uml2_componentdiagram.html
The diagram above demonstrates some components and their inter-relationships. Assembly connectors "link" the provided interfaces supplied by "Product" and "Customer" to the required interfaces specified by "Order". A dependency relationship maps a customer's associated account details to the required interface; "Payment", indicated by "Order".
Q1. purpose
- The purpose of packages is to illustrate the functionality of a software system and represent the different layers of a software system by illustrating the layered architecture of a software system.
- is the container for UML things, such as use cases or classes. It show system partitioning and occur during systems analysis or designed.
- use a folder symbol with the package name either in the folder tab oe centered in the folder.
example of package diagram:
source: http://www.agilemodeling.com/images/models/packageDiagramUseCases.jpg
This diagram shows the use of packages containing use cases to illustrate the functionality of a software system and represent the different layers of a software system to illustrate the layered architecture of a software system.
- is the container for UML things, such as use cases or classes. It show system partitioning and occur during systems analysis or designed.
- use a folder symbol with the package name either in the folder tab oe centered in the folder.
example of package diagram:
source: http://www.agilemodeling.com/images/models/packageDiagramUseCases.jpg
This diagram shows the use of packages containing use cases to illustrate the functionality of a software system and represent the different layers of a software system to illustrate the layered architecture of a software system.
Subscribe to:
Posts (Atom)