chapter 4 Flashcards

1
Q

requirement

A

an expression of desired behavior.
focus on the customer’s needs.
the “what” instead of the “how.”

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

software requirements specification (SRS)

A

performed by analyst or system analyst.

they are responsible for obtaining user’s requirements.

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

stakeholders

A

any person who is impacted by the system.

anyone who has a stake.

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

clients

A

pay for the software to be developed.

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

customers

A

buy the software after it’s developed.

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

users

A

use the system.

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

domain experts

A

familiar with problems that the software must automate.

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

market researchers

A

conduct surveys to determine future trends and potential customers.

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

lawyers or auditors

A

familiar with the government, safety, or legal requirements.

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

software engineer

A

technology experts

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

means of obtaining software requirements

A

interviewing stakeholders.
observing current systems.
brainstorming with current and potential users.

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

types of requirements

A
functional requirements: required activities.
quality requirements (non-functional): quality characteristics the software must posses.
design constraints: platform, interface, etc.
process constraints: restriction on techniques or resources that can be used.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

requirements: essential

A

must be met.

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

requirements: desirable

A

not necessary but nice to have.

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

requirements: optional

A

possible but could be eliminated.

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

entity relationship diagram (ER-Diagram)

A

entity: real world objects (rectangle).
relationship: edge between two entities. (diamond in the middle; specifies type of relationship)
attribute: annotation on entity, describes properties or data of the entity.

17
Q

uml

A

unified modeling language.

18
Q

uml: underline

A
class variable; all instances share the value.
library system, a loan class might share the "loan period" variable; all books have the same lending period.