#Arch_Overview
- Productivity
When there is a defined structure/plan for coordinating work between developers when implementing individual features or grounding…
- 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
Architecture is the process of creating system level guardrails and guidelines to help engineers produce a stable, maintainable and long…
- Architecture in agile
Architecture in agile is a little different, you are implementing as you figure out the desired architecture in smaller cycles. which…
- 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…
- 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…
- 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…
- Quality
A well designed system provides some benefits: - Easier maintenance - Ability to be reused in the future - Adapting to future changes
- Service based perspective
The system is viewed as a collection of interacting services/parts that achieve what you want the application to do.
- 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:
- 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…
- The need for software architecture & advantages
We need Software architecture because it provides a solid base for developers to follow in: - What needs to be implemented. - How parts of…
