Brainscape's Knowledge GenomeTM


Top Flashcards (Certified)
All Flashcards

CSC 106: Software Engineering > Chapter 4 > Flashcards

Chapter 4 Flashcards

1
Q

The process of establishing the services that acustomer requires from a system and the constraints under which it operates and is developed.

A

Requirements engineering

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

The _______ are the descriptions of the system services and constraints that are generated during the requirements engineering process.

A

System requirements

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

It may range from a high-level abstract statement of a service or of a system constraint to a detailed mathematical functional specification.

A

Requirement

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

Requirements may serve dual-function where…

A

Basis for a bid for contract (open to interpretation)
Basis for contract itself (defined in detail)

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

“If a company wishes to let a contract for a large software development project, it must define its needs in a sufficiently abstract way that a solution is not pre-defined. The requirements must be written so that several contractors can bid for the contract, offering, perhaps, different ways of meeting the client organization’s needs. Once a contract has been awarded, the contractor must write a system definition for the client in more detail so that the client understands and can validate what the software will do. Both of these documents may be called the requirements document for the system.” This is the ____ by ____

A

Requirements abstraction by Davis

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

2 Types of requirement

A

User
System

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

Statements in natural language plus diagrams of the services the system provides and its operational constraints. Written for customers.

A

User requirements

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

A structured document setting out detailed descriptions of the system’s functions, services and operational constraints. Defines what should be implemented so may be part of a contract between client and contractor.

A

System requirements

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

Any person or organization who is affected by the system in some way and so who has a legitimate interest

A

System stakeholders

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

What are the stakeholder types

A

End users
System manager
System owners
External stakeholders

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

In agile methods, the requirements document is always out of date. True or false

A

True

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

For requirements, agile methods are practical for what systems?

A

Business, but problematic for those that require pre-delivery analysis or systems developed by several teams

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

3 Types of Requirements

A

Functional
Non-functional
Domain

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

It described functionality or system services.

Depend on the type of software, expected users and the type of system

may be high-level statements of what the system should do.

should describe the system services in detail.

A

Functional requirements

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

This is what happens when functional requirements are not precisely stated.

A

Requirements imprecision

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

In principle, requirements should be both ______ and _______.

A

Complete and consistent

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

These define system properties and constraints e.g. reliability, response time and storage requirements. Constraints are I/O device capability, system representations, etc.

A

Non-functional requirements

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

What happens when non-functional requirements are not met?

A

System may be useless

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

Non-functional requirements are less critical than functional requirements. True or false?

A

False

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

Non-functional requirements may affect the ______ architecture of a system rather than the individual components.

A

Overall

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

Non-functional requirements may also generate requirements that restrict existing requirements. True or false

A

True

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

What are the Non-functional classifications?

A

Product requirements (product)
Organisational requirements (policies)
External requirements

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

A general intention of the user such as ease of use.

A

Goal

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

A statement using some measure that can be objectively tested.

A

Verifiable/Testable non-functional requirement

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
25
What are the metrics for specifying non-functional requirements?
Speed Size Ease of use Reliability Robustness Portability
26
The processes used for RE vary widely depending on the _________, the people involved and the organisation developing the requirements.
Application domain
27
What are the generic activities common to all processes?
Requirements elicitation; Requirements analysis; Requirements validation; Requirements management.
28
In practice, RE is an iterative activity in which generic activities are ______.
Interleaved
29
Requirements elicitation and analysis also called?
Requirements discovery
30
Involves technical staff working with customers to find out about the application domain, the services that the system should provide and the system’s operational constraints.
Requirements elicitation and analysis
31
What are the requirements elicitation stages?
Requirements discovery, Requirements classification and organization, Requirements prioritization and negotiation, Requirements specification.
32
In requirements elicitation, stakeholders always know what they really want. True or false
False
33
In one of the requirements elicitation stages, Interacting with stakeholders to discover their requirements. Domain requirements are also discovered at this stage
Requirements discovery
34
In one of the requirements elicitation stages, Groups related requirements and organises them into coherent clusters.
Requirements classification and organisation
35
In one of the requirements elicitation stages, Prioritising requirements and resolving requirements conflicts.
Prioritisation and negotiation
36
In one of the requirements elicitation stages, Requirements are documented and input into the next round of the spiral.
Requirements specification
37
Types of interviews with stakeholders
Closed Open
38
Normally a mix of closed and open-ended interviewing.
Interviews in practice
39
Interviewers need to be ______ without ______ ideas of what the system should do
Open-minded, pre-conceived
40
It is where social scientist spends a considerable time observing and analysing how people actually work
Ethnography
41
Ethnography is effective for understanding existing processes but cannot identify new features that should be added to a system. True or false?
True
42
Combines ethnography with prototyping
Focused ethnography
43
What is the problem with ethnography?
It studies existing practices, has historical bias, means no longer relevant
44
These are real-life examples of how a system can be used.
Scenarios and user stories
45
They are a description of how a system may be used for a particular task.
Stories and scenarios
46
Because stories and scenarios are based on a practical situation, stakeholders can relate to them and can comment on their situation with respect to the story. True or false?
True
47
A structured form of user story
Scenarios
48
Scenarios should include
A description of the starting situation; A description of the normal flow of events; A description of what can go wrong; Information about other concurrent activities; A description of the state when the scenario finishes.
49
The process of writing donw the user and system requirements in a requirements document.
Requirements specification
50
User requirements do not have to be understandable by end-users and customers who do not have a technical background. True or False?
False
51
System requirements are more ______ requirements and may include more technical information.
Detailed
52
Ways of writing a system requirements specification
Natural language Structured natural language Design description lang Graphical notations Mathematical specifications
53
The requirements are written using numbered sentences in natural language. Each sentence should express one requirement.
Natural language
54
The requirements are written in natural language on a standard form or template. Each field provides information about an aspect of the requirement
Structured natural language
55
This approach uses a language like a programming language, but with more abstract features to specify the requirements by defining an operational model of the system. This approach is now rarely used although it can be useful for interface specifications.
Design description languages
56
Graphical models, supplemented by text annotations, are used to define the functional requirements for the system; UML use case and sequence diagrams are commonly used.
Graphical notations
57
These notations are based on mathematical concepts such as finite-state machines or sets. Although these unambiguous specifications can reduce the ambiguity in a requirements document, most customers don’t understand a formal specification. They cannot check that it represents what they want and are reluctant to accept it as a system contract
Mathematical specifications
58
In principle, requirements should state what the system ______ and the design should describe ____
Should do, how it does
59
In practice, requirements and design are inseparable. T or F?
True
60
Requirements are written as natural language sentences supplemented by diagrams and tables. Used for writing requirements because it is expressive, intuitive and universal. This means that the requirements can be understood by users and customers.
Natural language specification
61
What are the guidelines for writing requirements?
Standard format Consistent language Text highlighting No computer jargon Explanation of why requirement is needed
62
What are the problems with natural language
Lack of clarity Requirements confusion (of functional and non-functional_ Requirements amalgamation
63
An approach to writing requirements where the freedom of the requirements writer is limited and requirements are written in a standard way.
Structured specifications
64
What has this? Definition of the function or entity. Description of inputs and where they come from. Description of outputs and where they go to. Information about the information needed for the computation and other entities used. Description of the action to be taken. Pre and post conditions (if appropriate). The side effects (if any) of the function.
Form-based specifications
65
Used to supplement natural language. Particularly useful when you have to define a number of possible alternative courses of action.
Tabular specification
66
are a kind of scenario that are included in the UML. It identifies the the actors in an interaction and which describe the interaction itself. Set of use cases should describe all possible interactions with the system E.g Medical receptionists register patients and view personal info
Use cases
67
is the official statement of what is required of the system developers.
Software requirements document
68
The software requirements document should include both a definition of _____ requirements and a specification of the ____ requirements.
User and system
69
The software requirements document is not a design document. T or F?
True. it should set of WHAT the system should do rather than HOW it should do it.
70
Information in requirements document depends on type of system and the approach to development used.
Requirements document variability
71
What includes this? Preface Introduction Glossary User requirements definition System architecture System requirements specification System models System evolution Appendices Index
structure of a requirements document
72
Concerned with demonstrating that the requirements define the system that the customer really wants.
Requirements validation
73
Requirements checking includes
Validity Consistency Completeness Realism Verifiability
74
What are the Requirements validation techniques
Requirements reviews Prototyping Test-case generation
75
Regular ______ should be held while the requirements definition is being formulated. Both client and contractor staff should be involved in reviews. Reviews may be formal (with completed documents) or informal.
Requirement reviews
76
What are needed when reviewing requirements?
Verifiability Comprehensibility Traceability Adaptability
77
The business and technical environment of the system always changes after _____
Installation
78
The people who pay for a system and the users of that system are rarely the same people. T or f
T
79
What describes this? Understanding of Problem -> Initial requirements -> Changed understanding -> changed requirements
Requirements evolution
80
is the process of managing changing requirements during the requirements engineering process and system development.
Requirements management
81
Establishes the level of requirements management detail that is required.
Requirements management planning
82
What are the requirements management decisions?
Reqs identification A change management process Traceability policies Tool support
83
Deciding if a requirements change should be accepted
Requirements change management
84
Requirements change management include
Problem analysis and change specification Change analysis and costing Change implementation

CSC 106: Software Engineering (4 decks)

Brainscape helps you reach your goals faster, through stronger study habits.
© 2025 Bold Learning Solutions. Terms and Conditions