Communicating Architecture
Overview
It is difficult to capture the complete behavior of a system with a single perspective, when looking at whether the software accomplishes its goal, considering just the code might miss the physical components of the system.
And if you're looking at its physical components you might miss the software management perspective, Imagine you are a software engineer working to create a piece of software for a client, Your client already has an idea in mind that the software has a certain purpose.
Other than the purpose, the software may be implemented any way you decide.
Key Points / Concepts
- Kruchten's 4 + 1 Model Views
- UML Component Diagram
- Practical Scenario
- UML Package Diagram
- UML Deployment Diagram
- UML Activity Diagram
