chapter 4

Question 1

what is req specification?

Answer 1

the collection of all reqs that are to be imposed on the design & verification of the product

Question 2

____________ describes what the software will do and how it will do it?

Answer 2

SR

Question 3

list types of reqs.

Answer 3

GF Is Pregnant U
- general
- functional
- implementational
- performance
- usability

Question 4

what describes the minimum acceptable performance by a system?

Answer 4

performance req

Question 5

what describes the maximum amount of time needed to demonstrate system to a user?

Answer 5

usability req

Question 6

list common req problems.

Answer 6

• inaccurate user needs
• inconsistent & incomplete
• expensive to change
• misunderstanding b/u user, analyst & developer

Question 7

list wrong reqs?

Answer 7

• unsatisfied end-user
• late delivery & higher cost
• frequent system failures & errors
• expensive maintenance

Question 8

what is req management?

Answer 8

the process of managing changes to reqs

Question 9

reqs change to reflect what?

Answer 9

• change in business needs
• change in stakeholder needs
• change in env’t
• change in laws & regulations

Question 10

what is SRS?

Answer 10

official doc that explains the system to users, developers and customers

Question 11

SRS is developed based on what?

Answer 11

agreement b/n customers & contractors

Question 12

what does SRS describe?

Answer 12

• overall properties
• functions
• constraints
• app domain info
• system info

Question 13

what should an SRS doc contain?

Answer 13

introduction & glossary

Question 14

who uses SRS doc to plan bids and for dev’t process?

Answer 14

proj manager

Question 15

who uses SRS doc to understand proj being developed?

Answer 15

system engineer

Question 16

who uses SRS doc to understand r/n ship b/t system & its parts?

Answer 16

system maintenance engineer

Question 17

what is the structure of an SRS doc?

Answer 17

1.intro
- scope
- purpose
- audience
- use
- definition

2. description
   - assumption
   - dependencies
   - user needs
3. features & reqs
   - system features

Question 18

what are use cases?

Answer 18

describe how a user performs tasks on a system

Question 19

what forces developers to think through end-users POV?

Answer 19

use cases

Question 20

what are steps of Use case?

Answer 20

• describe end user
• focus on that end user
• write use case for every user interaction
• write sequence of events
• write user action & system resp
• write alt. user action & system resp
• repeat for d/t users

Question 21

how are reqs written?

Answer 21

written as paragraphs with graphs & equations

Question 22

what are problems encountered when writing reqs?

Answer 22

• complex conditionals
• leaving out essential details
• inconsistent use of terminologies

Question 23

what things should you avoid when writing reqs?

Answer 23

loopholes, ambiguities, subjectivity, comparatives, superlatives

Question 24

what are characteristics of a req doc?

Answer 24

• complete
• consistent
• verifiable
• viable
• measurable
• explicit
• flexible
• accurate
• no implementational constraints

Question 25

what characteristics of a req doc ensures that product is inline with reality of the env’t, technology, budget …

Answer 25

viability