The document describes a system architecture that decomposes a system into smaller, more manageable subsystems and layers. Each layer supplies one level of abstraction and only uses services from the layer below it. The layers include a financial subsystem, I/O subsystem, and user interface subsystem with various components like accounts, transactions, input/output devices, and user interactions between them.

1. 1

2. Student
Management
Accounts
Hrm and Payroll Library
Management

3. 1. Account: access and modifybalance
2. Account: commit result to database
3. Display: display information
4. Form: get numeric value from user
5. Input Device: accept user input
6. Menu: get user selection
7. Output Device: output to theuser
8. Transaction: execute financial transaction
9. User Message: display message and wait

4. Account
1 2
Balance Deposit Withdrawal Transfer
Transaction 8
DisplayDevice
BCR
3
Input Device
5
7
Output Device
ATM
Form
Menu
User
Message
UserInteraction
4
6
9

5. Account
1 2
Balance Deposit Withdrawal Transfer
Transaction 8
DisplayDevice
BCR
3
Input Device
5
7
Output Device
ATM
Form
Men
u
User
Message
UserInteraction
4
6
9

6. 9
6
Financial
Subsystem
8
Input Device
BCR
Display Device
3
5
Output Device 7
ATM
Form
Menu
User
Message
User Interaction
4

7. 9
6
Financial
Subsystem
8
Input Device
BCR
Display Device
3
5
Output Device 7
ATM
Form
Menu
User
Message
User Interaction
4

8. 6
Financial
Subsystem
8
3
5
9
7
ATM
4
I/O
Subsystem
User
Interaction
Subsystem

9. Financial
Subsystem
8
ATM
3 4 5 6 7 9
User Interface
Subsystem

10. Financial
Subsystem
8
ATM
3 4 5 6 7 9
User Interface
Subsystem

11. Decomposition of the system into smaller, more
manageable units, that are layeredhierarchically.
Each layer supplies one level of abstraction
 A layer only uses services of the next
underlying layer
 Layers can be tested independently

12. 26

13. 27

14. Layer can request for services from exactlyone
layer below it.
Layer can respond to a request of a layerexactly
one layer above it.
Total Layers = N = 3
Request = N-1
Response = N+1

15. High Level Architectural Diagram
Services Layers
Operations Layers
Student Data Management
Request
Response

16. It’s a combination of subsystem and layers
When you start at the root each node can be
reached in exactly one way
Usually the nodes can be placed in different
layers a node can be considered as the
representative of thissubtree

17. 3

18. An automated ticket issuing system used by passengers at a
railway station. The System should also allow reservation of
seats and give some route information. The passenger
should be able to pay for the ticket at the counteralso.
To Do : We have to design the architecture of the above
specific principle and propersystem after selecting a
assumptions.

19. Seat Reservation
Train data
Transaction
Bank Data
Route Information