Architectural Design
Architectural
design is of crucial importance in software engineering during which the
essential requirements like reliability, cost, and performance are dealt with. It
involves identifying major system components and their communications.
Logical View
Logical view is
concerned with the functionality that system will provide to the end user. It
also will shows the key abstraction in the system as object or object classes.
Process View
Architecture design.
Process view is the
process that view deals with dynamic aspect of system. It also explain the
system process and how it interact on the runtime behaviour of system. The
process view will address the concurrency, distribution, integration, and more.
This process uses multiple levels of abstractions, a logical network of
processes at the highest level
The development view illustrates a system from a programmer's
perspective and is concerned with software management. This view is also known
as the implementation view. It uses the UML Component diagram to describe
system components. UML Diagrams used to represent the development view include
the Package diagram.
In
Unified Modeling Language (UML), a component diagram depicts how components are
wired together to form larger components or software systems. They are used to
illustrate the structure of arbitrarily complex systems.
A
package diagram in the Unified Modeling Language depicts the dependencies
between the packages that make up a model.
Physical View
The physical view depicts the system from a system
engineer's point of view. It is concerned with the topology of software
components on the physical layer as well as the physical connections between
these components. This view is also known as the deployment view. UML diagrams
used to represent the physical view include the deployment diagram.
Scenario
The description of an
architecture is illustrated using a small set of use cases, or scenarios, which
become a fifth view. The scenarios describe sequences of interactions between
objects and between processes. They are used to identify architectural elements
and to illustrate and validate the architecture design. They also serve as a
starting point for tests of an architecture prototype. This view is also known
as the use case view.
Scenarios serve as abstractions
of the most important requirements on the system. Scenarios play two critical
roles, i.e. design driver, and validation/illustration. Scenarios are used to
find key abstractions and conceptual entities for the different views, or to
validate the architecture against the predicted usage. The scenario view should
be made up of a small subset of important scenarios. The scenarios should be
selected based on criticality and risk. Each scenario has an associated script,
i.e. sequence of interactions between objects and between processes. Scripts
are used for the validation of the other views and failure to define a script
for a scenario discloses an insufficient architecture.
The 4+1 View Model presented in
was developed to rid the problem of software architecture representation. Five concurrent
views are used; each view addresses concerns of interest to different
stakeholders. On each view, the Perry/Wolf definition is applied independently.
Each view is described using its own representation, a so called blueprint. The
fifth view (+1) is a list of scenarios that drives the design method.
Design By:-
IQBAL, AIMAN, ASHRAF, NIK, IRSHAD, AZIIM, ARIF, FAIQ, SYAZWAN
Good Information
ReplyDelete