#UML_Diagrams
- Productivity
When there is a defined structure/plan for coordinating work between developers when implementing individual features or grounding…
- Activity diagram components
Activity diagrams have a few major parts: - Start/End nodes : denoted by a labeled opaque circle where your software begins/Ends…
- Adding value to the client
Adding value to the client can sometimes be something tangible like a new feature or extra functionality, but it can also be a…
- Aesthetic perspective
The aesthetic here means the behind the scenes of architectures/styles, where architects keep in mind the Testability and Adaptability of…
- Agents of change
The main target of architects is to make a change or a decision about the system, so some architects rarely deal with code or deep…
- Architectural styles
Architecture of systems vary depending on the architectural model/style. each style has a different way to describe it's architecture, in…
- Architecture in agile
Architecture in agile is a little different, you are implementing as you figure out the desired architecture in smaller cycles. which…
- Architecture overview and Process
- What is architecture. - Important factors to consider in software architecture. - Needs and advantages. - Stakeholders benefitting from…
- Artifacts
A physical result of a development process, for example: in a game, artifacts include things like an executable to run the game, an…
- Communicating Architecture
It is difficult to capture the complete behavior of a system with a single perspective, when looking at whether the software…
- Customer's perspective
The Customer's perspective in the mind a software architect is of what the client needs and what they want from the business.
- Data flow architecture
The system takes data in a certain form and process it through multiple stages, though not as described as a service based architecture…
- Deployment Details
When creating a deployment diagram, it is important to use the correct notation for various elements: - Artifacts: these are created as…
- Development View
This view describes The Hierarchical Software Structure and considers elements such as: - Programming Languages - libraries - Toolsets It…
- Draw a Component Diagram
This is my Solution:
- Draw a Deployment Diagram
This is my Solution:
- Engineering team's perspective
When the architect looks from the engineering team's perspective, they are looking at: - Expectations of work - The needs to achieve a…
- Environment
The environment or target for development can be very specific, involving certain hardware devices, or general, involving supported…
- Evolution
After identifying what parts of the system do, it is easier to add new features or fix potential failures
- How to represent software architecture
At a high level Architectures are described by: - Identity Boxes: Things being done. - Lines: Interactions between the way things are…
- Instance-level diagrams
Instance-level diagrams are much more specific, they map specific artifacts to specific deployment targets, in particular, instance level…
- Kruchten's 4 + 1 Model Views
Multiple perspectives are necessary to capture the complete behavior and development of a software system.
- Logical View
t--- # Note This view focuses on the Functional requirements of the system, usually involving the objects of the system, from these object…
- Manifistation
The Player.class file manifists the player component, the encapsulated unit that contains all the functionality of a player.
- Module 1 Assignments
To access this remote database, the mobile app sends an HTTP request to the remote server that matches the remote server’s provided…
- Nodes
Hardware device are displayed in the same way as nodes with a device tag to differentiate it from other types of nodes.
- Overview
- [x] Architecture overview and Process ✅ 2026-03-06 - [x] Communicating Architecture ✅ 2026-07-13 - [x] Module 1 Assignments✅ 2026-07-13…
- Package Diagram Legend
Packages are simply depicted as a tabbed folder with an empty package (with no elements) having it's name in the center.
- Physical View
This view handles how elements in the logical, process, and development views must be mapped to different nodes or hardware for running…
- Practical Scenario (Wishlist feature)
This scenario will show how the Kruchten's 4 + 1 Model Views apply on a real world project, we want to add a wishlist feature to an…
- Process View
This view focuses on achieving the non-functional requirements, these are the requirements that specify the desired qualities of the…
- Provided interface
A provided interface is used to show that a component offers an interface for others (clients and consumers) to interact with it, a…
- Quality
A well designed system provides some benefits: - Easier maintenance - Ability to be reused in the future - Adapting to future changes
- Relations
This is an example of a relationship between two nodes, or communication path, which denotes a particular communication protocol between…
- relevant libraries
Relevant libraries are all the third-party libraries and implementations along with your implementations, they must be identified and…
- Required interface
A required interface shows that a component expects a certain interface provided by another component to achieve it's goals, the required…
- Scenarios
Scenarios are made with a script that describes the sequence of interactions between objects and processes, this involves the: - Key…
- Service based perspective
The system is viewed as a collection of interacting services/parts that achieve what you want the application to do.
- Specification-level diagrams
Specification-level diagrams give an overview of artifacts and deployment targets, without referencing specific details like machine names.
- Stakeholders
People who are interested in the system and either use it or benefit from it.
- Stakeholders benefitting from architecture
Who are the Stakeholders of Software Architecture and how they benefit from it:
- Swim lanes
these are used to visualize concurrent activities happening in parallel, for example; audio playing alongside the game. that is a fork in…
- System Architect life
Architects keep a lot in their minds, so being able to operate at different levels of abstractions is a necessary skill.
- technological risks
Architects ask themselves "If my system is going to run for a long time, do i risk using and/or training my developers on a technology…
- UML Activity Diagram
In a video game you follow a sequence of levels to reach a goal, moving between levels with each level serving a specific purpose.
- UML Component Diagram
UML component diagrams are a static view of a system depicting it's design at a specific time of it's development and/or evolution.
- UML Deployment Diagram
Software releases are more than just lines of code bundled together, it involves separate parts like: - Libraries - Executables…
- UML Package Diagram
In Object Oriented Software you define interacting classes and sometimes they are related, In video games you have several classes for…