Architectural patterens

1) Concurrency: Many applications must handle multiple tasks simultaneously. Each task
presented by a different architectural pattern.
Ex: one approach is an operating system process management its provides built in OS
functions.
Another approach is define scheduler its provides different types of operations
2) Persistence: Data is stored in a data base or file and this can be modified by a other
processes at a later time. There are two types of architectural patterns are used to achieve
persistence.

a) Data base management system pattern: That applies the storage and retrieval
capacity.
b) Application level persistence pattern: That builds persistence features in to the
application architecture .ex: word processing.

3) Distribution: In this process systems or components communicate with one another in a
distributed environment.
There are two elements

1) Which entities connect to one another.
2) The nature of communication.
Distribution problem follows the broker pattern. A broker acts as a middleman
between the client component and server component.
The client sends a message to the broker and broker complete the information.

Organization and refinement

Control: how is control managed within the architecture.
How do computers transfer control within the system.
How is control shared components.
What is the control topology?
Data: how the data communicated between components. what is the mode of data
transfer .i.e. one component to another or data is shared by different components.
What there role how functional components interact with data components.










ARCHITECTURAL DESIGN

In this process software to be developed must be put in to the context.
Design defines the external entities (system, devices, and people).
Software interacts the nature of the interaction. Once context is modeled and
all external s/w interfaces have been described.
Designer specifies the structure of the system by defining and refining software
components.

1) REPRESENTING SYSTEM IN CONTEXT.
Architectural context describes the how the software interacts with entities external
to its boundaries,
Generally software architect uses an architectural context diagram (ACD).
Structure of the architectural context diagram. An architectural context to
model the manner in which software interacts with entities external to its
boundaries.
Super ordinate systems



Subordinate systems

Fig: Architectural context diagram



TARGET SYSTEM
The overall safe home product controller and the internet based system are both
super ordinate to the security function and are shown bellow



1) Superordianate systems: Those systems that use the target system as part of some higher
level processing schemes. 2) Subordinate systems: Those systems that are used by the
target system and provide data or processing that are necessary to complete target system
functionality.
3) Peer level-systems: Those systems that are indicate on a peer to peer basis(information
is produced or consumed by the peers and target system.)
4) Actors: Those entities (people, devices)that interact with the target system by
Producing or consuming information that is necessary for requisite processing.
Fig: safe home product controller and the internet based system are both super ordinate to
the security function.
Surveillance function is used by the home security function. home owner and control
panels are actors ,sensors are used by the security software ae shown as subordinate to it.


target system:
Security Function
uses
uses
peers
homeowner
Safehome
Product
Internet-based
system
surveillance
function
sensors
control
panel
sensors
uses