Requirements Flashcards

1
Q

Is it acceptable for the development team or requirements analyst to suggest modifying the requirements to reuse existing components.

A

Yes, small differences in functionality may be worth the reduced cost of reusing existing components.

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

What, if anything, is wrong with using a statement like the following in a requirements document in order to document a usability requirement: “The user interface should be easy to use”?

A

“easy to use” should be defined. An alternative is “95% of users that fit the profile of the average user defined in section x.y can complete all possible transactions without prior training and without consulting the product documentation.”

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

Requirements may have forward and backward traceability. Backward traceability (from the perspective of the requirement) means that it is possible to trace a specific requirement back to its source (where it originated from). Forward traceability means it’s possible to trace a requirement to a design element, code and/or test case
True or False?

A

True

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

A use case can have multiple scenarios and multiple actors. True or False?

A

True

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

The actor of a use case may be a user or external software system.
True/False

A

True

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

User and customer are synonyms. They refer to the same person or role.
T/F?

A

False

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

Consider the following statement in a requirements document:

(1) The system shall be secure. (2) Users should be authenticated with a user ID and password. After three consecutive invalid password attempts, the user account should be locked for 5 minutes.

What is (1)? What is (2)?

A

non-functional requirement, functional requirement

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

Which type of requirement is more likely to be discrete, that is, completely present or completely absent? (Functional Req., Non-Functional Req., Constraint)

A

Functional Req.

Constraint

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

Assume the following statement comes from a software requirements specification:

“The system shall be easy to learn. 90% of the users as defined in section x.y shall be able to complete use cases 1-3 within 10 minutes without consulting the written documentation.”

This statement is best characterized as what?

A

A non-functional req.

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

Which of the following is not normally found in a requirements document? Chose all that apply (Communication Plan / Mandated Constraints / Schedule / Written use cases and or a use case model / Budget / Non-functional Requirements)

A

Communication Plan & Schedule & Budget

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

The Software Requirements Specification (SRS) shouldn’t specify design but it is OK for the SRS to restrict or limit certain design options. T/F?

A

True

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

Which of the following statements is a constraint of the type you would expect to find in a software requirements specification?

The database must be open source
The project must be completed by 2/12/20xx
The user interface must be intuitive and easy to use. It must pass the usability test outlined in the next
section.
The system must keep a record of every transaction that changes the database

A

The database must be open source

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

Which type of prototype are you more likely to create if your goal is to test the technology stack used for your product?

A

Vertical prototype

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

A throw away prototype can be used to:

A

Better understand requirements & Explore design alternatives & Resolve technical risks

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

The system being modeled in one UML use case diagram may play the role of actor in another use case diagram? In other words, it’s perfectly reasonable for the software system at the center of one use case diagram to be an actor in another use case diagram. T/F?

A

True

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