Basic RE concepts

Question 1

List the stages of the SW development method

Answer 1

Requirements,
Analysis,
Design,
Implementation,
Testing,
Maintenance

Question 2

What are the skills that analysts need to consult effectively with stakeholders?

Answer 2

Interviewing,
Interpersonal,
Observation,
Organisational,
Critical Evaluation,
Analysis and Abstraction,
Communication

Question 3

List ways of eliciting requirements

Answer 3

Contextual Design - observing plus questioning,
Ethnography - long-term observation,
Prototyping - eliciting feedback,
Interviews,
Questionnaires

Question 4

List the parts of a requirements document

Answer 4

Project Outline,
Functional Requirements,
Non-Functional Requirements,
Acceptance tests,
Project Management

Question 5

What is the requirements document?

Answer 5

The document output from requirements analysis that contains the specification of the system negotiated between client, analyst, and stakeholders.

Question 6

What is the requirements analysis?

Answer 6

The process of analyzing and organizing the information from requirements elicitation into a clear description of the system. It establishes a set of requirements that are agreed to be complete, consistent and unambiguous.

Question 7

What are the stages of the object-oriented style SW development?

Answer 7

Requirements Specification,
Developing a conceptual model (domain class model),
Developing a user interface,
Detailed Design (Class model, Sequence diagram),
Implementation (Java, C++),
Testing,
Maintenance

Question 8

What are the requirements engineering stages?

Answer 8

Requirements elicitation
Requirements analysis
Requirement spec construction
Validation

Question 9

What is a requirement spec?

Answer 9

A detailed description of a software system to be developed with its functional and non functional requirements

Question 10

What is validation?

Answer 10

Check requirements specification against stakeholders goals and requirements and ensures that are inline

Question 11

What is requirements elicitation?

Answer 11

Discovery of what requirements a computer based system should be based upon

Question 12

Different parts of elicitation? Idk how to word this soz but it’s to answer the one where it says talk about one in depth.

Answer 12

Application domain knowledge
Eg knowledge about overall systems in the sector

Problem context knowledge
Eg knowledge of the specific company you’re developing for

Problem knowledge
Eg knowledge of the problem you are trying to solve with the creation of the system

Stakeholders needs wants and work processes to be supported

Question 13

More elicitation in-depth (sorry but this seems easiest one to know in depth)

Answer 13

Establish objectives

• business goals
• Problems to be solved.
• Constraints

Understand background

• organisational structure
• application domain
• existing systems

Organise knowledge

• stakeholder identification
• goal prioritisation
• domain knowledge

Collect requirements

• stakeholder requirements
• domain requirements
• organisational requirements

Question 14

Stages of analysis ( hah anal(

Answer 14

1 organise all of the elicited requirements into coherent groups
2 seperate the functional requirements from the non functional
3 group together all the different kinds of functional requirements.
- eg group database functions tgt
Eg group user interface tgt

4 group all nfr together

• performance requirements
• group security requirements

5 critically review all of the requirements by checking the following problems

• conflicting requirements
• unclear requirements
• ambiguous requirements
• redundant requirements
• incomplete requirements
• inaccurate requirements