chapter 4 Flashcards
what is req specification?
the collection of all reqs that are to be imposed on the design & verification of the product
____________ describes what the software will do and how it will do it?
SR
list types of reqs.
GF Is Pregnant U
- general
- functional
- implementational
- performance
- usability
what describes the minimum acceptable performance by a system?
performance req
what describes the maximum amount of time needed to demonstrate system to a user?
usability req
list common req problems.
- inaccurate user needs
- inconsistent & incomplete
- expensive to change
- misunderstanding b/u user, analyst & developer
list wrong reqs?
- unsatisfied end-user
- late delivery & higher cost
- frequent system failures & errors
- expensive maintenance
what is req management?
the process of managing changes to reqs
reqs change to reflect what?
- change in business needs
- change in stakeholder needs
- change in env’t
- change in laws & regulations
what is SRS?
official doc that explains the system to users, developers and customers
SRS is developed based on what?
agreement b/n customers & contractors
what does SRS describe?
- overall properties
- functions
- constraints
- app domain info
- system info
what should an SRS doc contain?
introduction & glossary
who uses SRS doc to plan bids and for dev’t process?
proj manager
who uses SRS doc to understand proj being developed?
system engineer
who uses SRS doc to understand r/n ship b/t system & its parts?
system maintenance engineer
what is the structure of an SRS doc?
1.intro
- scope
- purpose
- audience
- use
- definition
- description
- assumption
- dependencies
- user needs - features & reqs
- system features
what are use cases?
describe how a user performs tasks on a system
what forces developers to think through end-users POV?
use cases
what are steps of Use case?
- 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
how are reqs written?
written as paragraphs with graphs & equations
what are problems encountered when writing reqs?
- complex conditionals
- leaving out essential details
- inconsistent use of terminologies
what things should you avoid when writing reqs?
loopholes, ambiguities, subjectivity, comparatives, superlatives
what are characteristics of a req doc?
- complete
- consistent
- verifiable
- viable
- measurable
- explicit
- flexible
- accurate
- no implementational constraints
