Brainscape's Knowledge GenomeTM

Browse over 1 million classes created by top students, professors, publishers, and experts.


See full index

COMPX341 > Requirements > Flashcards

Requirements Flashcards

1
Q

what are product requirements?

A

Any kind of requirement that concerns the software or system itself is a product requirement

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

what are functional requirements?

A

what should the software be doing

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

what are nonfunctional requirements?

A

what kind of constraints do we have in order to solve this problem. e.g. technical environment, network bandwidth

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

what are emergent properties?

A

requirements that include all various components of the system and how information flows between them. These depend on the level of abstraction that you’re working on.

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

what are process requirements?

A

any kind of action you are taking while you are building the software. They tell us something about the procedure or process about building the software

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

what are quantifiable requirements?

A

requirements that we can measure a specific value, that way they are testable.

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

what are system requirements?

A

requirements that specify what is the whole system, including humans and other non-software components, aiming to achieve. The goals of the software.

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

what is the difference between software vs system requirements?

A

We essentially build the software requirements from the system requirements. System are more of a high level description of the system overall, whereas software describes the internal functionality on a lower level

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

what are software requirements?

A

software requirements are properties that must be exhibited by something to solve a problem in the real world.

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

what are stakeholders?

A

those who have a part in the project
users: who uses the software
customers: who pay for the software
regulators: who check the software for compliance
software engineers: who design, create, maintains, tests and even uses the software

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

what is requirements elicitation?

A

the process of finding/figuring out requirements and writing them down. We take the system requirements and turn them into software requirements

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

what are requirements sources? examples?

A

where we get requirements from
goals or business concerns: what the client is telling us
domain knowledge: learn the industry
stakeholders: talk to those involved

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

what is the operational environment?

A

what environment you want (or need) to run the software on

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

what is the organizational environment?

A

how is your system going to affect peoples lives e.g. replacing people

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

what are some techniques to get requirements from sources?

A 
interview stakeholders
divise scenarios
prototypes
synchronization and brainstorming meetings
observation
user stories
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

what is requirements analysis?

A

go over the requirements and see how much we are actually going to proceed with this specific requirement and how the software is going to fit (operational and organizational). Its important because we will have contradictions in our requirements

17
Q

what does being precise with the requirements enable?

A

validation: are these the correct specs
testing: can we verify implementation
estimate costs: requires talking to stake holders

18
Q

what is formal analysis?

A

applying standard logic and proof techniques on the requirements. We write the requirements in such a way that we can put them into a computer and a program can tell us everything we’ve missed

19
Q

what are some types of conceptual modelling?

A 
use case diagrams
data flow models
state models
goal based models
user interactions
object models
SysML
UML
Sequence Diagram
20
Q

what is negotiation?

A

Discuss with the stakeholders/client and finding middle ground because sometimes, they can ask for too much (even the impossible)

21
Q

what is a requirements specification?

A

a software requirements specification SRS is a document which describes the requirements of the software, translated from the system requirements gathered from the stakeholders/client

22
Q

what is requirements validation?

A

reviews
prototyping
model validation
acceptance tests

COMPX341 (5 decks)

Brainscape helps you reach your goals faster, through stronger study habits.
© 2025 Bold Learning Solutions. Terms and Conditions