Name Muhammad Basit Sufian

Roll No. BSE-SP22-M04

Course SDA
Submitted To Mam Moniba
 Manual 1
STAR UML:
 Type:
Star UML is popular open source modeling tool.
 Features:
A) Various modeling notations.
B) Support range of standard diagrams.
 Customization:
Star UML support extensions and customization through plugin.
 User Interface:
While functional user interface may not be as modern or intuitive as same
as newer tools.
MODERN MODELING TOOLS:
1. LucidChart:
 Lucid chart is a cloud-based collaborative diagramming and modelling
tools.
 It offers real-time collaboration,templates & integration's.
 It provides intuitive, web-based interface.
2. Draw.IO:
 Free,open- source, web-based diagram tools.
 It offers various diagram types and integration with cloud storage.
3. Plant UML:
 Plant UML is comprehensive modeling tools.
 It provide support for UML diagrams, sysML.
 It offers custom extensions and integrations with IDE.
4. Creately:
 It is web based diagramming and design tools.
 It offers real time collaboration templates.
 It features clean and user-friendly interface.
5. Visual Paradigm:
 It is comprehensive modeling and diagramming tool.
 It supports for UML diagram, sysML.
 It offers custom extensions and integration with IDEs.
 It can be integrated to various development environment.
 Manual 2:
USECASE DIAGRAM:
A use case diagram is a type of UML (Unified Modeling Language) diagram that
visually represents the interactions between actors (users or external systems) and
a system under consideration. It illustrates the various ways that users or external
entities can interact with the system to achieve specific goals or functionalities.

Manual 3:
DFD Diagrams:
DFD stands for Data Flow Diagram. It is a graphical representation of how data
flows within a system. DFDs are commonly used in software engineering and
systems analysis to model the flow of information through a system or process.
They provide a visual way to show how data moves between processes, data
stores, and external entities.
 Processes
 Data Flow
 Data Stores
 External Entity
Scenario:
The Owner of star computer repair shop would like to keep track of the repair
jobs for computers they repair, the items used for each repairs jobs, the labor cost
for each repair job, repairmen performing each repair job, and the total cost of
each repair job. When customers bring their computers in to be repaired, they
deposit the repair job and are give a due date to return and uplift their computers.
Repairmen then perform repairs on the customers computers based on the repair
job and detail the labor costs and the items used fir each repair job. When
customers return they pay the total cost of the repair job the deposit is less,
collect a receipt for their payment, and uplift the repaired computers using the
payment receipt.Draw a level 2 DFD diagram

Manual 4:
ER-DIAGRAM:
An Entity-Relationship (ER) diagram is a visual representation of data within a database, illustrating the
entities, attributes, and relationships between them. Entities are objects or concepts (like customers or
orders), attributes are properties of these entities, and relationships show how entities interact with each
other. It's a powerful tool for designing and understanding database structures.
When to use ER-DIAGRAM:
It's particularly helpful in the early stages of database development to clarify requirements, ensure data
integrity, and communicate effectively with stakeholders. So, whether you're starting a new project,
updating an existing database, or troubleshooting data issues, an ER diagram can be a valuable asset.
 Manual 5:
ACTIVITY DIAGRAM:
Activity diagram is another important behavioral diagram in UML: diagram to describe dynamic aspects
of the system. Activity diagram is essentially an advanced version of flow chart that modeling the flow
from one activity to another activity.
When to use ACTIVITY DIAGRAM:
Activity Diagrams describe how activities are coordinated to provide a service which can be at different
levels of abstraction. Typically, an event needs to be achieved by some operations, particularly where the
operation is intended to achieve a number of different things that require coordination, or how the events
in a single use case relate to one another, in particular, use cases where activities may overlap and require
coordination. It is also suitable for modeling how a collection of use cases coordinate to represent business
workflows.
 MANUAL 6
STATE-CHART DIAGRAM:
A state machine is any device that stores the status of an object at a given time and can change
status or cause other actions based on the input it receives. States refer to the different combinations
of information that an object can hold, not how the object behaves.
STATE COMPONENTS:
DIAGRAM:
 MANUAL 7:
CLASS DIAGRAM:
Class diagrams are a type of UML (Unified Modeling Language) diagram used in software
engineering to visually represent the structure and relationships of classes in a system. UML is a
standardized modeling language that helps in designing and documenting software systems. They
are an integral part of the software development process, helping in both the design and
documentation phases.
COMPONENTS:
 MANAUL 8:
OBJECT DIAGRAM:
Object Diagrams are a type of UML (Unified Modeling Language) diagram used in software
engineering that can be referred to as a screenshot of the instances in a system and the relationship
that exists between them. Since object diagrams depict behavior when objects have been
instantiated, we can study the behavior of the system at a particular instant.
COMPONENT:

MANAUL 9:
COMPONENT DIAGRAM:
A component diagram in software engineering is a type of structural diagram that illustrates
the components of a system and the dependencies between them. It shows the high-level
organization and interactions of software components, such as modules, classes, and
packages, within a system. Component diagrams are particularly useful for understanding the
architecture of complex systems, facilitating communication among team members, and
guiding the implementation and maintenance of software projects.
WHEN TO USE COMPONENT DIAGRAM:
You would use a component diagram in software engineering when you need to visualize the
high-level organization and interactions of components within a system. It's especially useful
during the design phase to map out the architecture of a software system, identify dependencies
between components, and ensure that the system is modular and scalable. Additionally,
component diagrams can aid in communication among team members, help stakeholders
understand the system's structure, and guide developers during implementation and
maintenance.

MANAUL 10:
COLLABORATION DIAGRAM:
A collaboration diagram, also known as a communication diagram, is a type of interaction diagram in the
Unified Modeling Language (UML) that illustrates the interactions and relationships among objects within a
system. It shows how objects collaborate to achieve a specific task or goal by depicting the messages
exchanged between them.
WHEN TO USE COLLABORATION DIAGRAM:
You'd use a collaboration diagram in software engineering to model object interactions, visualize message
flows between objects, and facilitate communication among stakeholders during the design and development
phases.

MANAUL 11:
DEPLOYMENT DIAGRAM:
A deployment diagram in software engineering illustrates the physical deployment of software
components across hardware nodes in a system. It shows how software artifacts are deployed onto
hardware infrastructure like servers or devices. Deployment diagrams aid in understanding system
architecture, resource allocation, and network configuration. They're especially useful for system
administrators, developers, and stakeholders to visualize the deployment environment and plan for
system deployment and maintenance.
WHEN TO USE DEPLOYMENT DIAGRAM:
You'd use a deployment diagram when planning the physical deployment of software components
onto hardware, configuring network connections, allocating resources, and ensuring scalability for
system deployment and maintenance.

MANAUL 11:
STATE MACHINE DIAGRAM:
A state machine diagram, also known as a state diagram, is a behavioral diagram in the Unified
Modeling Language (UML) that models the behavior of a system or object over time. It represents
the various states that an object or system can be in, as well as the transitions between those states
triggered by events. State machine diagrams are useful for modeling complex systems with multiple
states and transitions, helping to visualize and analyze their behavior and ensure proper system
functionality.
WHEN TO USE STATE DIAGRAM:
You'd use a state machine diagram to represent the behavior of systems or objects with multiple
states and transitions, aiding in understanding complex system logic, specifying system
requirements, and guiding software implementation where clear state transitions are crucial.

MANAUL 12:
SEQUENCE DIAGRAM:
A sequence diagram in software engineering is a type of interaction diagram that illustrates the
interactions and messages exchanged between objects or components within a system over time. It
represents the sequence of events or actions that occur during the execution of a particular scenario
or use case, showing the chronological order of method calls and responses between objects.
WHEN TO USE SEQUENCE DIAGRAM:
You'd use a sequence diagram in software engineering when you need to visualize the interactions
and messages exchanged between objects or components within a system over time. Specifically,
they're beneficial for designing system architecture, analyzing system behavior, communicating
system design to stakeholders, and aiding in testing and debugging software implementations.
 MANAUL 13:
COMMUNICATION DIAGRAM:
A communication diagram in software engineering is a type of interaction diagram that depicts the
interactions between objects or components within a system through messages or method calls. It
emphasizes the relationships and collaborations between objects, showing how they communicate to
achieve specific tasks or goals. Communication diagrams provide a visual representation of the
runtime behavior of a system, aiding in system understanding, design, and communication among
stakeholders.
WHEN TO USE COMMUNICAITON DIAGRAM:
You'd use a communication diagram in software engineering when visualizing object interactions
and collaborations, emphasizing relationships between objects, and communicating system behavior
to stakeholders. Specifically, they're beneficial for understanding runtime behavior, designing
system architecture, and facilitating communication among development teams.
窗体顶端

MANAUL 14:
PACKAGE DIAGRAM:
A package diagram in software engineering is a structural diagram in the Unified Modeling
Language (UML) that illustrates the organization and dependencies between packages within a
system. It represents the high-level modular structure of a software application, showing how
packages encapsulate related classes, components, or subsystems. Package diagrams help in
organizing and managing the complexity of large systems, facilitating communication among
developers, and ensuring proper modularization and encapsulation.
WHEN TO USE PACKAGE DIAGRAM:
You'd use a package diagram in software engineering when organizing the modular structure of a
system, managing dependencies between packages, communicating system architecture to
stakeholders, and ensuring proper encapsulation and modularization of software components.
Specifically, they're valuable during system design, refactoring efforts, documentation, and
collaboration among development teams.