Scribd
Upload
18 views

CS230 Tutorial Week 2 Solution

Exam papers

Uploaded by

jashwinsinghfj11
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
18 views

CS230 Tutorial Week 2 Solution

Exam papers

Uploaded by

jashwinsinghfj11
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 2

Requirements Engineering Tutorial 1

1. User requirements are statements in a language that is understandable to a user of


what services the system should provide and the constraints under which it operates.
System requirements are more detailed descriptions of the system services and
constraint, written for developers of the system.

2. Functional requirements define what the system should do. Non- functional
requirements are not directly concerned with specific system functions but specify
required system properties or place constraints on the system or its development
process.

3. Product requirements, that specify or constrain the software's behaviour.


Organizational requirements are general requirements derived from policies and
procedures in the customer's organization.
External requirements, which cover all requirements derived from factors external to
the system and its development process.

4. A software requirements document (also known as software requirements


specifications) is a document that describes a software application's intended use-case,
features, and challenges. These documents are created before the project begins
development in order to get all stakeholders on the same page regarding the
functionality of the software.

5. “Shall” refers to a mandatory requirement. “Should” indicates a desirable but not


essential requirement.

6. All requirements have the same format so are easier to read.


The definition of form fields mean that writers are less likely to forget to include
information.
Some automated processing is possible.

7. Requirements elicitation and analysis


Requirements specification
Requirements validation

8. 1.Stakeholders don’t know what they want.


2.Stakeholders use their own language that requirements engineers may not
understand.
3.Stakeholder requirements may conflict.
4.Political factors may influence the system requirements.
5.The business environment may change during elicitation.

9. 1. Description of what’s expected when the scenario starts.


2. Description of the normal flow of events.
3. Description of what can go wrong and how to handle it.
4. Information about concurrent activities.
5. Description of the system state when the scenario finishes.

10. A use-case identifies a typical interaction with a system and the actors (human or
computer) involved in that interaction.

11. Ethnography is an observational technique where an analyst spends a period of time


observing work and noting how the participants carry out their tasks. It is particularly
useful in identifying essential cooperation in work processes.

12. 1. Validity checks


2. Consistency checks
3. Completeness checks
4. Realism checks
5. The verifiability of the requirements should be assessed

13. 1. Requirements reviews


2. Prototyping
3. Test-case generation

14. Requirements management is the process of managing changes to requirements


during requirements specification and after the system has gone into use.

15. 1. Problem analysis and change specification


2. Change analysis and costing
3. Change implementation

You might also like