inf 113: exam 2

when are full-fledged requirements needed?

• when customers want contractually-fixed requirements

• when systems are built by external contractor/using outsourcing

• in regulated environment

what is the purpose of a glossary?

it provides agreed upon common terminology

what’s the definition of a glossary?

collection of definitions of terms that are relevant

what does a glossary define?

• context-specific terms
• everyday terms that have a special meaning in the context
• abbreviations and acronyms

when do we use formal language specifications?

• specify the most critical sections of the requirements document

• specify stable requirements

what is documented informally or semi-formally?

plain natural language, structured natural language, graphic models

what are some aspects to consider in the level of detail usage in RE?

• degree of implicit shared understanding of the problem
• degree of freedom left to designers and programmers
• cost vs. value of detailed specification
• risk you are willing to take

when should we use more detail in RE?

• the work is being done for external client
• development or testing will be outsourced
• project team members are geographically dispersed
• system testing is based on requirements
• accurate estimates are needed

when should we use less detail in RE?

• the work is being done internally
• customers are extensively involved
• developers have considerable domain experience
• precedents are available (ie. prev application is being replaced)

which qualities should we strive for in requirements and RE work products?

• correct

• understandable

• verifiable

• unambiguous

• complete

• necessary

• feasible

• consistent

• conformant

• modifiable (non-redundant & structured)

• traceable

which qualities are the most important?

correctness and understandability

which qualities are important (after the most)?

verifiability and consistency

which qualities are not possible or economically feasible in most cases?

completeness and unambiguity

which three words should be used carefully in RE?

shall, will, should

what does shall signify the statement is?

requirement

what does the will signify the statement is?

assumption

what does the should signify the statement is?

suggestion

what are some natural language tips?

• create glossaries & data dictionaries

• attach a unique identifier

• avoid redundancy

• use templates

• order requirements in sections and sub-sections

what is example of ISO/IEC/IEEE 29148 standard?

unit 1 → section 1,1

what are the names of the EARS patterns?

• ubiquitous

• event-driven

• state-driven

• unwanted behavior

• optional feature

• compound

what is the definition of a user story?

a software system requirement as 1-2 sentences in everyday language of the user

what artifacts can you derive from user stories?

• formal requirements

• use cases

• and more!

what does INVEST stand for (in relation to user stories)?

• independent

• negotiable

• valuable

• estimatable

• sized appropriately (5-15)

• testable

what are some common user story pitfalls?

• the activity cannot be done within the system

• the role is not an actually user

• acceptance criteria not detailed enough

• needs a “so that” portion

• trying to make non-functional req user stories