system requirements (week 3) Flashcards

1
Q

what are system requirements

A

list of features, functional, non-functional requirements and requisite use cases for the software

delves into how of a software

will be documented under the software requirement specification / functional requirement specification that will help developers understand the business and user requirements

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

what are the types of system requiremetns

A

functional requirements
non functional requirements
domain requirements

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

what are functional requirements

A

–> behaviours that the developed product should do or support

–> usually expressed as inputs into the product, outputs of the product, or a description of the behaviour itself

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

give an example of functional requirements

A

authentication when the user tries to log into the system

system shutdown in case of a cyber attack

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

what are non functional requirements

A

describe how a system must behave and establish constraints of its functionality (quality attributes)

define how the system must operate

system can meet its functional requirements and fail to meet its non functional requirements

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

what are the software’s characteristics and expected ux

A

SPURS

security 
performance 
usability
reliability
scalability
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

what is usability

A

defines how difficult it will be for the user to operate the system

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

what are the 3 ways usability can be assessed

A

efficiency of use = avg time it takes the user to complete their goals, how many tasks can be completed, etc

intuitiveness = how simple it is to understand the interface and buttons

low perceived workload = how many attempts are needed by users to accomplish a particular task

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

what is security

A

security requirements ensure that the system is protected from unauthorised access to the system and its data

considers different roles of authorization and authentication across different user roles

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

example of security

A

access permissions from the particular system information may only be changed by the system’s data admin

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

what is reliability

A

reliability decreases because of bugs in the code, hardware failures, or problems with other system components

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

how to measure system reliability

A

count the percentage of operations that are completed correctly or track the avg period of time the system runs before failing

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

example of reliability

A

database update process must roll back all related updates when any update fails.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

what is performance

A

performance is the quality attribute that describes the responsiveness of the system to various user interactions with it

poor performance will lead to a negative user experience

jeopardises the system safety when it is overloaded

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

example of performance

A

front page load time must not be more than 2 seconds for users that access the website using an LTE mobile connection

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

what is availability

A

it is the period of time that the systems operations are available for use with all operations

schedules maintenance periods directly influence this parameter

define the most critical components of the system that must be available at all time and prepare user notifications in case the system or one of its parts becomes unavailable

17
Q

example of availability

A

new module deployment must not impact the front page, product pages. The rest of the pages which experience problems must display a notification with a timer showing when the system is going to be up again

18
Q

what is scalability

A

describe how the system must grow

both hardware and software implications

19
Q

how to increase scalability

A

adding memory, servers, disk space, etc

compress data using optimising algorithms

20
Q

example of scalability

A

website concurent access limit must be scalable enough to support 500,000 users at a time

21
Q

name the 4 differences between functional and non functional requirements

A

–> functional requirements have detailed product features whereas non functional requirements have detailed product properties

–> functional requirements describe the work that is done whereas non functional requirements describe the character of the work

–> functional requirements describe the user actions whereas non functional requirements describe the user experience

–> functional requirements are characterised by verbs whereas non functional requirements are characterised by adjectives