Que 1: What is UML?
Ans: UML is Unified Modeling Language. It is a graphical language for visualizing specifying constructing and documenting the artifacts of the system. It allows you to create a blue print of all the aspects of the system, before actually physically implementing the system.
Que 2: What is modeling? What are the advantages of creating a model?
Ans: Modeling is a proven and well-accepted engineering technique which helps build a model. Model is a simplification of reality; it is a blueprint of the actual system that needs to be built. Model helps to visualize the system. Model helps to specify the structural and behavior of the system. Model helps make templates for constructing the system. Model helps document the system.
Que3: What are the different views that are considered when building an object-oriented software system?
Ans: Normally there are 5 views.
1. Use Case view - This view exposes the requirements of a system.
2. Design View - Capturing the vocabulary.
3. Process View - modeling the distribution of the systems processes and threads.
4. Implementation view - addressing the physical implementation of the system.
5. Deployment view - focus on the modeling the components required for deploying the system.
Que 4: What are diagrams?
Ans: Diagrams are graphical representation of a set of elements most often shown made of things and associations.
Que 5: What are the major three types of modeling used?
Ans: Major three types of modeling are structural, behavioral, and architectural.
Ques 6: Mention the different kinds of modeling diagrams used?
Ans: Modeling diagrams that are commonly used are, there are 9 of them. Use case diagram, Class Diagram, Object Diagram, Sequence Diagram, statechart Diagram, Collaboration Diagram, Activity Diagram, Component diagram, Deployment Diagram.
Que 7: What is Architecture?
Ans: Architecture is not only taking care of the structural and behavioral aspect of a software system but also taking into account the software usage, functionality, performance, reuse, economic and technology constraints.
Que 8: What is SDLC?
Ans: SDLC is Software Development Life Cycle. SDLC of a system included processes that are Use case driven, Architecture centric and Iterative and Incremental. This Life cycle is divided into phases. Phase is a time span between two milestones. The milestones are Inception, Elaboration, Construction, and Transition. Process Workflows that evolve through these phase are Business Modeling, Requirement gathering, Analysis and Design, Implementation, Testing, Deployment. Supporting Workflows are Configuration and change management, Project management.
Que 9: What are Relationships?
Ans: There are different kinds of relationships: Dependencies, Generalization, and Association. Dependencies are relations ships between two entities that that a change in specification of one thing may affect another thing. Most commonly it is used to show that one class uses another class as an argument in the signature of the operation. Generalization is relationships specified in the class subclass scenario, it is shown when one entity inherits from other. Associations are structural relationships that are: a room has walls, Person works for a company. Aggregation is a type of association where there is a has a relation ship, That is a room has walls, if there are two classes room and walls then the relation ship is called a association and further defined as an aggregation.
Que 10: How are the diagrams divided?
Ans: The nine diagrams are divided into static diagrams and dynamic diagrams.
Que 11: What is Static Diagrams?
Ans: Static Diagrams (Also called Structural Diagram): Class diagram, Object diagram, Component Diagram, Deployment diagram.
Que 12: What is Dynamic Diagrams?
Ans: Dynamic Diagrams (Also called Behavioral Diagrams): Use Case Diagram, Sequence Diagram, Collaboration Diagram, Activity diagram, Statechart diagram.
Que 13: What are Messages?
Ans: A message is the specification of a communication, when a message is passed that results in action that is in turn an executable statement.
Que 14: What is an Use Case?
Ans: A use case specifies the behavior of a system or a part of a system, Use cases are used to capture the behavior that need to be developed. It involves the interaction of actors and the system.
Get More Questions and Answers with Explanation related to Unified Modeling Language at Netweaver Forums.