Architectural design

“Establishing the overall structure of a software system.”

DESIGN PROCESS

1. System structuring the communication between the different systems.

- Repository Model- storage area where you put all your input.
- Client Server Model- parallelism/ handle multiple user/ simultaneously servicing/ multi
functioning
- Abstract Machine Model- versions/alterations/ versioning/
 Subsystem – system that is independent/ can perform any output. without any
supervising in it
 Module- dependent from one another
2. Control Modeling- management of the signals of communication
- Centralized- one user
 Call Return- ex. telephone, only access control model then respond to an
appropriate action.
 Manager- monitor, always control, constant monitoring.
 Event Based- when a certain event happens.
o Broadcast-broadcasting information/
o Interrupt Driven- handling errors, thin fabricated problems that could have
been planned about.
3. Modular Decomposition- on how you divide all/ dissect the system, how it is being managed/
specification.
- Object- specification of that particular object, qualitative
- Data Flow- actually doing, more quantitative
4. Domain Specific- ‘free-form’
- Generic- more on copying certain functions that is already existed.
- Referenced- combining two systems.

HR Faculty

SLU

Non-
SAO Teaching
Repository Model

USER1 USER2 USER3

Internet

Facebook
YOutube Google

Client Server Model

 oS

Database

Hardware

Application

asd
Abstract Machine Model
Customer

- ID
- Name
- Address
- Age

Sale

- ID
- Quantity
- Price

Product

- ID
- Name
- Price
- Stock

Customer Buys Product

Receipt Sale
 Terms
and
examples