Scribd
Upload
0 views

13_summary_of_system_requirements

The document outlines the importance of identifying both functional and non-functional requirements in system design, emphasizing the need to convert use cases into APIs. It details various non-functional requirements such as availability, scalability, performance, durability, consistency, maintainability, security, and cost. Each category includes specific attributes and considerations that contribute to the overall effectiveness and reliability of the system.

Uploaded by

Sara Totah
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
0 views

13_summary_of_system_requirements

The document outlines the importance of identifying both functional and non-functional requirements in system design, emphasizing the need to convert use cases into APIs. It details various non-functional requirements such as availability, scalability, performance, durability, consistency, maintainability, security, and cost. Each category includes specific attributes and considerations that contribute to the overall effectiveness and reliability of the system.

Uploaded by

Sara Totah
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 3

System requirements - Summary

• Identifying both functional and non-functional requirements is an integral part of any system design.

• Write requirements on the board.

• Use non-functional requirements as a tiebreaker.

• To identify functional requirements, we start with the customers and move backwards.

• Be ready to convert identified use cases into API.


System requirements - Summary

Availability Scalability Performance Durability Consistency

System uptime, the The property of a system to The time required to process Once data is successfully Consistency of data across
percentage of time the system handle a growing load. something and/or the rate at submitted to the system, it is distributed copies.
has been working and which something is processed. not lost.
available.

• high availability • vertical and horizontal • latency • backup • strong consistency


• SLO and SLA scaling • percentiles • RAID • weak consistency
• fault tolerance • elasticity • throughput • replication • consistency model
• resilience • autoscaling • bandwidth • data corruption and • linearizability
• chaos engineering checksum • CAP
• reliability • eventual consistency
• monotonic reads
• read-your-writes
• consistent prefix reads
System requirements - Summary

Maintainability Security Cost

The ease with which a product can Degree to which the system protects How to design systems with the most
be maintained. against threats. effective use of resources.

• failure modes and mitigations • CIA triad • engineering cost


• monitoring • identity and permissions • maintenance cost
• testing management • hardware cost
• deployment • infrastructure protection • software cost
• data protection

You might also like