SoftwareEngineering2

1. What is the purpose of packages? Show an example of package diagrams.

Answer: Package serves its purpose as a container that can be used by UML things commonly known as use case or Classes. These containers used a folder symbol which shows the partition of a system. These partition indicate that classes or use case are group into logical packages (subsystems).

2. How is a component diagram different from a class diagram? Show an example of component diagram.

Answer: Components diagram is different from a class diagram in away that this diagram shows the internal structure component of a system. It also shows the relationship between its component.

3. What is illustrated in a deployment diagram? Show an example of deployment diagram.

Answer: Physical implementation of the system including the systems physical components or commonly known as hardware components, the relationship between the system and the hardware and the system on which it is deployment.

4. Summarize the steps in putting UML to work.

Answer:

· Define the use case model. (Includes the actors in the use case diagram and the process to satisfy the system requirements and generate use case scenario).

· Continue IML diagramming to model the system during the systems analysis phase. (Derive activity diagrams from the use case diagrams and develop sequence and collaboration diagrams for use case scenarios. Review the sequence diagrams with the business area experts to verify process and interaction. Make modifications as necessary until the business area experts agree that the sequence diagrams are complete and accurate).

· Develop the class diagrams. (Look for nouns in use cases and list them and look for similarities and differences in the objects due to the objects states or behavior and then create classes. Define the major relationships between the classes. Examine use case and sequence diagrams in order to determine classes).

· Draw state chart diagrams. (Develop state chart diagrams for certain class diagrams to provide further analysis of the system at this point. Use state chart diagrams to aid in understanding complex processes that cannot be fully derived by the sequence diagrams.).

· Begin systems design by refining UML diagrams and using them to derive classes and their attributes and methods. (Review all existing UML diagrams for the system. Develop methods specifications that detail the input output requirements for the method. Create another set of sequence diagrams to reflect the actual class methods and interactions with each other. Create class diagram using the specialized class symbols for boundary or interface class, entity class and control class).

· Document your system design in detail. (This step is critical. The more complete the information you provide the development team through documentation and UML diagrams, the faster the development and the more solid the final production system).

5. How important is UML for modeling?

Answer: UML is really important for modeling because through this we can achieve a greater understanding in the relationship between the business and system developer with regards to system requirement and the process that must occur in the system to meet these requirements.

http://www.agilemodeling.com/style/packageDiagram.htm

Gelyn S. Cirilo BSIT III

Jayermine Anne S. Beloria BSIT III