Diagrams in System Analysis and Design
In system analysis and design, diagrams are used to represent the different aspects of a system, its components, and their interactions. The main types of diagrams used in system analysis and design include:
 |
| business boundary, include and extend relationships. |
- Use case diagrams: This type of diagram is used to describe the functionality of a system from the user's perspective. It shows the different use cases (or scenarios) in which a user interacts with the system, as well as the actors (or users) who are involved in those interactions.
- Activity diagrams: This type of diagram is used to represent the flow of activities within a system. It shows the sequence of activities and decisions involved in a particular process or use case.
- Sequence diagrams: This type of diagram is used to represent the interaction between objects in a system. It shows the sequence of messages exchanged between objects in a particular scenario or use case.
- Class diagrams: This type of diagram is used to represent the structure of a system. It shows the different classes that make up the system, their attributes, and their relationships with each other.
- Deployment diagrams: Deployment diagrams are a type of diagram used in system analysis and design to illustrate the physical architecture of a system. They show how the different components of a system are deployed on hardware or software environments, such as servers, workstations, or cloud services.
- Component diagrams: This type of diagram is used to represent the components of a system and their dependencies. It shows the different parts of the system, their interfaces, and how they interact with each other.
These diagrams are used to help system analysts and designers to understand the requirements of the system, design its components, and communicate their designs to stakeholders. Each diagram represents a different aspect of the system, and together they provide a comprehensive view of the system and its behavior.
UML 2.5 Diagrams Overview.
Note, items in blue are not part of official taxonomy of UML 2.5 diagrams.
[Australia] 261111 - ICT Business Analysts
Identifies and communicates with users to formulate and produce a requirements specification to create system and software solutions.
Description of Employment Duties:
- Working with users to formulate and document business requirements
- Identifying, investigating, and analyzing business processes, procedures and work practices
- Identifying and evaluating inefficiencies and recommending optimal business practices, and systemfunctionality and behavior
- Using project management methodologies, principles and techniques to develop project plans and to cost, resource and manage projects
- Taking responsibility for deploying functional solutions, such as creating, adopting and implementing system test plans, which ensure acceptable quality and integrity of the system
- Creating user and training documentation, and conducting formal training classes
- Developing functional specifications for use by system developers
- Using data and process modeling techniques to create clear system specifications for the design and development of system software
- Acting as a central reference and information source, providing guidance and assistance in the system project decision making process