Architecture in Technical Perspective View
Perspective is basically view from specific fixed viewpoint. Technical perspective generally explains system’s technical level of view. Software architecture simply contains and includes software systems structure, their behavior, and patterns that guide and advise these elements, their collaborations, and their composition. Different models define how people interact or connect with processes at different actions within system, and things they control and use.
Architecture framework :
Architecture framework is basically an encapsulation of minimum set of practices and requirements for artifacts that are used to describe architecture of system. It also explains term of views known as complementary projections that are generally abstractions of Unified Modeling Language (UML) in set of designs. It just provides principles and practices for developing, interpreting, analyzing, and making use of architecture description of system within specific domain of application or stakeholder community.
Architecture View :
It is generally used to represent entire architecture that is useful and meaningful to one or more stakeholders in system. Architecture view or viewpoint is set of representations of an architecture that covers stakeholder issues. It also represents functional and non-functional requirements of software application. View is basically partial expression of system from specific perspective. A viewpoint is generally collection of patterns, templates, and even conventions for developing one type of view.
In the diagram shown above, you can see following points :
- Use case view –
A use case view is generally used in requirements discipline to provide and give basis for planning technical contents of iterations. Using use case diagrams, it is modeled statically, and using UML behavioral diagrams, it is modeled dynamically.
- Design View –
A design view generally means to organize design information and addresses basic structure and also functionality of solution. It simply explains architecturally important and significant features. It is used to organize design information. It also describes overall design entities and attributes.
- Process View –
It generally deals with dynamic aspects of system, describes processes of system, and even how they communicate and emphasizes behavior of system during run time. It simply describes different activities of system. It also describes control thread relationships between components of design and deployment views. It also describes synchronization aspects of the design.
- Component View –
It addresses source code realization of system software from perspective of integrators and developers of project. It simply explains structure and design of implementation set. It has basically three different views i.e. conventional view, process-related view, and also object-oriented view.
- Deployment View –
It generally explains distribution of processing across set of nodes in system, along with physical distribution of processes and fields. It simply explains structure and design of deployment set. It also shows physical distribution of processing within system. It basically describes and explains environment within which system is runner and executed.