Professional Documents
Culture Documents
advantages
- Provides standard for software development.
- Reducing of costs to develop diagrams of UML using supporting tools.
- Development time is reduced.
- The past faced issues by the developers are no longer exists.
- Has large visual elements to construct and easy to follow.
- This model represents the framework for the system and all the components exist
here.
- It represents the elements and the mechanism to assemble them.
- It never describes the dynamic behavior of the system.
2. Behavioral modeling:
3. Architectural modeling:
25.what is SDLC?
- SDLC is Software Development Life Cycle.
- SDLC of a system included processes like Use case driven, Architecture centric,
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. Supporting Workflows are configuration,
change management, and project management.
Class Diagram
This diagram explores detail design of the system. The class diagram is designed
using Use Case diagram. We can identify all Nouns in use cases as classes and
verbs as method of the classes.
Object diagram
This diagram represents the state of classes in the system and their relationships
or associations at a specific point of time.
State Diagram
This diagram represents different states that objects in the system undergo during
their life cycle.
Sequence diagram
This diagram is used to explore logic of complex operations, function or procedure.
In this diagram, sequence of the interactions between the objects is represented
step by step.
Collaboration diagram
This diagram groups together the interaction between different objects.
Activity diagram
Activity diagram gives detail view of the business logic.
Deployment diagram
It shows deployment view of the system. It shows how hardware and software works
together to run system.
20.what are the different views that are considesred when building an object-
oriented software system.
Building block of UML
Things
- Structural Things
- Behavioral things
- Grouping things
- Annotational things
Relationships
- Dependency
- Association
- Generalization
- Realization
Diagram
- Class Diagram
- Object Diagram
- Use case Diagram
- Sequence Diagram
- Collaboration Diagram
- Statechart Diagram
- Activity Diagram
- Component Diagram
- Deployment Diagram
Dependency
Dependency is the relationship between two things in which a change in one thing
may affect the other thing, but not necessarily the reverse. Graphically, it can be
represented as a dashed directed line, directed to the thing being depended on.
Association
An association is a relationship that connects classes. Example of association is
relationship between person and company. An association is rendered as solid line.
Adornments of association
Generalization
In this type of relationship, the child shares the structure and behavior of the
parent. It is represented as a solid line with a hollow arrowhead pointing to the
parent.
Realization
A realization is a relationship where one class specifies a contract which another
class carries out. This kind of interface can be found out between the interface
and the class.
Use case diagram, Class Diagram, Object Diagram, Sequence Diagram, statechart
Diagram, Collaboration Diagram, Activity Diagram, Component diagram, Deployment
Diagram.
The nine diagrams are divided into static diagrams and dynamic diagrams.