0% found this document useful (0 votes)
14 views17 pages

SA - Assignment 1

Uploaded by

Khushi Tandle
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
14 views17 pages

SA - Assignment 1

Uploaded by

Khushi Tandle
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 17

SS ZG653 : Software Architecture

Assignment :1
BITS Pilani Name: Satish Kumar Sharma
ID Number: 2022MT93327
Email: [email protected]

Pilani|Dubai|Goa|Hyderabad
Table of Contents
Page Details Page Number
Purpose of the system 3 and 4
Key Requirements : Functional & 5
Non-Functional
Utility tree of Architecturally Significant Requirements (ASR) 6 and 7
Tactics used to achieve the top 5 ASRs 8
Software Architecture diagram – Context diagram 9
Module decomposition 10 and 11
Component & Connection diagram 12
Deployment diagram 13
Description of how the system works 14 and 15
Key learnings 16

9/11/2022 SS ZG653 2
Purpose of the system
• Offer customers interest on deposits, helping to protect against
money losing value against inflation.
• Lending money to firms, customers and homebuyers.
• Offering financial advice and related financial services, such as
insurance
• Instant access to cash (hole in the wall cash machines)
• Bank lending is profitable for banks and can incur significant
costs for the firm.
• Offer customers to Open account (Saving and Current Account)
• Offer customers to Deposits and Fund Transfer
• Offer customers to Withdrawal Money
• Keep money safe for customers
9/11/2022 SS ZG653 3
Purpose of the system Visual

9/11/2022 SS ZG653 4
Key Requirements : Functional &
Non-Functional
Functional requirements Non Functional requirements

• Login
• Validation • Performance
• Get balance information • Operation and Maintenance
• Withdrawal of money • Backup
• Transfer Money • Security
• Customer info • Automatic & Elastic Scaling
• Beneficiary • Reliability
• Administrative Control
• Account Information
• View statements transaction
• Open Saving or Current Account

9/11/2022SS ZG653 SS ZG653 5


Architecturally Significant Requirements (ASR)

1. The system must respond within 30 seconds.


2. The system must encrypt all network traffic.
3. The system should available 24/7 to Business.
4. New feature required to apply on existing system.
5. The System must be tested like Usability, Security, Scalability
testing... etc.
6. The system must record every modification to customer
records for audit purposes.
7. The Banking system must fund transfer and validated account
holders with sufficient cleared funds.

9/11/2022 SS ZG653 6
Utility tree of Architecturally Significant Requirements
(ASR)
Quality Requirement Question Response Impact Measure
Attribute
Performance The system must Is system Response<1 Medium Yes
respond within 30 response with 00ms
seconds. in time?
Security The system must Is system Yes, all data High Yes
encrypt all network encrypt data? encrypted.
traffic.
Availability The system should Is down time Yes. High Yes
available 24/7. less than
Business. 99.999%?
Modifiability New feature required Is new Yes, Easy to Low No
to apply on existing changes apply new
system. apply? changes
Testability The System must be Is system Yes, it’s High Yes
tested like Usability, follow all tested with
Security, Scalability standard? all standard.
9/11/2022
testing..etc. SS ZG653 7
Tactics used to achieve the top 5
ASRs
Quality
Tactics
Attribute
Control resource demand Limit event Increase resource
Performance response Efficiency
Manages Resource Increase resource Schedule Resources
Detect Attacks Detect Intrusion Verify Message
Integrity
Security
Resist and React to Attacks Identify Actors, Encrypt Data,
Revoke Access Lock computer
Detect Faults Monitor system Self testing
Availability Recover from faults Preparation and Exception Handling
Repair
Modifiability Reduce size of a Modules Split Modules Reduce coupling
Control and Observe System Sandbox, record Playback and
Testability
State
9/11/2022 SS ZG653 8
Software Architecture diagram – Context diagram

9/11/2022 SS ZG653 9
Software Architecture diagram –Module
decomposition – Part 1

9/11/2022 SS ZG653 10
Part 2

9/11/2022 SS ZG653 11
Software Architecture diagram – Component &
Connection diagram

9/11/2022 SS ZG653 12
Software Architecture diagram-Deployment
diagram

9/11/2022 SS ZG653 13
Description of how the system works
• A bank is a financial institution which is involved in borrowing and lending
money. Banks take customer deposits in return for paying customers an
annual interest payment. The bank then uses the majority of these deposits
to lend to other customers for a variety of loans. The difference between
the two interest rates is effectively the profit margin for banks. Banks play
an important role in the economy for offering a service for people wishing
to save. Banks also play an important role in offering finance to businesses
who wish to invest and expand. These loans and business investment are
important for enabling economic growth.

9/11/2022 SS ZG653 14
Description of how the system works Diagram

9/11/2022 SS ZG653 15
Key learnings
Personal Learnings
• Gather and find the goal of System.
• Find Architecturally Significant Requirements (ASR)?
• Prepare Utility Tree.
• Create UML Component Diagram.
• Create context and deployment diagram.
Learning to organization
Challenges in building and managing high scalable web and mobile applications
system.

9/11/2022 SS ZG653 16
Thank You
Name: Satish Kumar Sharma
ID Number: 2022MT93327

9/11/2022 SS ZG653 17

You might also like