Analysis - Requirements

Question 1

What is a requirement?

Answer 1

A requirement is a statement of what the system must do or what characteristics it needs to have

Question 2

What are the two types of requirements?

Answer 2

• Functional: What the software should do
• Non-functional: What characteristics the system should have

Question 3

How are the requirements used?

Answer 3

Developers use the list of requirements to build the system

Question 4

What is the 4 Process of determining requirements?

Answer 4

1) Requirements discovery
- Elicitation techniques

2) Requirements classification and organization
- Grouping (non-functional, functional)

3) Requirements prioritization
- Order the requirements by most important
MoSCoW (Must have, Should have, Could have, Won’t have)

4) Requirements documentation
- Fully document the requirements
- Check requirements against the quality criteria

Question 5

How do we discover the requirements needed?

Answer 5

• Interviews
• Document Analysis.
• Observation
• Questionnaires
• Joint Application Development (JAD)

Question 6

What does JAD stand for?

Answer 6

Join application development.

• The project team, users and management work together to identify requirements for the system.
• Set in a specially prepared JAD meeting room so all participants can see each other.

Question 7

What does the abbreviation MoSCoW mean?

Answer 7

Must have, should have, could have, won’t have. Used when prioritising requirements into a list.

Question 8

Pros of using questionnaires for gathering requirements?

Answer 8

• Good when there is many people whom information and opinions are needed

Question 9

Cons of using questionnaires for gathering requirements?

Answer 9

• Can take time to get responses
• Response rates for questionnaires can be very low
• Hard to recall after being sent out (Review the questionnaire first questions can be misunderstood)

Question 10

When gathering requirements, which method has a high depth of information?

Answer 10

• Interviews
• Joint Application Development (JAD)

(Questionnaires have a medium)

Question 11

When gathering requirements, which method has a high width of information?

Answer 11

• Questionnaires
• Document Analysis

(Joint Application Development (JAD) has a medium)

Question 12

When gathering requirements, which method has a high integration of information?

Answer 12

• Joint Application Development (JAD)

Question 13

When gathering requirements, which method has a high user involvement?

Answer 13

• Joint Application Development (JAD)

(Interviews has a medium)

Question 14

When gathering requirements, which method has a medium cost?

Answer 14

• Interviews
• Observation

(the rest are low.)

Question 15

Is the following example a functional or non-functional requirement?

“The system must allow registered customers to review their own order history for the past 3 years.”

Answer 15

Functional

Question 16

Is the following example a functional or non-functional requirement?

“The system must retain customer order history for 3 years.”

Answer 16

Functional

Question 17

Is the following example a functional or non-functional requirement?

“The product capabilities or things that a product must do for its users”

Answer 17

Functional

Question 18

Is the following example a functional or non-functional requirement?

“As a Customer, I need to place a food order so that I can have food delivered to my house”

Answer 18

Functional

Question 19

Is the following example a functional or non-functional requirement?

“The system should allow a user to place a food order”

Answer 19

Functional

Question 20

Is the following example a functional or non-functional requirement?

The quality attributes, design and implementation constraints and external interfaces which a product must have.

Answer 20

Non-functional

Question 21

Is the following example a functional or non-functional requirement?

“The user must be able to access the system through a mobile device”

Answer 21

Non-functional

Question 22

Is the following example a functional or non-functional requirement?

“The query response time of the system must be faster than..”

Answer 22

Non-functional

Question 23

How are requirements documented for Agile Methodology?

Answer 23

By using user stories:

• As a WHO, I want to (WHAT they want to accomplish, so that (WHY they want to accomplish that)
• Defining a acceptance criteria, so everyone agrees that the requirement is satisfied

Question 24

What are some functional acceptance criteria for Agile user stories? Give 2

Answer 24

• Can I save my order and come back to it later?
• Can I change my order before I pay for it?
• Can I see a running total cost of what I have chosen?

Question 25

What are some non-functional acceptance criteria for Agile user stories? Give 2

Answer 25

• Can I place an order at any time (24 hours per day or 24/7/365)?
• Can I view the order at any time (24 hours per day or 24/7/365) up to and including delivery?
• Are unauthorised persons and other customers prevented from viewing my order?

Question 26

What should an analyst make sure?

Answer 26

• A good analyst must make sure the that the current business processes and needs of the new system are well understood before moving on to design
• All the key stakeholders should be included in requirements elicitation, if possible, Respect the time commitment you are asking those involved to make! Prepare questions in advance etc. 10 October 2023 46.

Question 26

What are some good criteria for good requirement documentation?

Answer 26

• Correct. Are requirements present that directly address user needs?
• Unambiguous. Is the requirement open to only on interpretation?

-Complete. Has all functionality required by the user been defined?

• Consistent. Do the requirements have no contradictory definitions?
• Ranked for importance
• Not specify a particular design