Docsity
Docsity

Prepare for your exams
Prepare for your exams

Study with the several resources on Docsity


Earn points to download
Earn points to download

Earn points by helping other students or get them with a premium plan


Guidelines and tips
Guidelines and tips

Bugs and Errors Bugs and Errors, Lecture notes of Engineering

Bugs and Errors Bugs and Errors

Typology: Lecture notes

2022/2023

Uploaded on 11/19/2023

ceren-kuru
ceren-kuru 🇹🇷

3 documents

1 / 4

Toggle sidebar

This page cannot be seen from the preview

Don't miss anything!

bg1
Chapter 4: Requirements Engineering
Your name:
Answer all questions. 1 mark per question
1. What are user requirements and system requirements?
2. What is the distinction between functional and non-functional requirements?
3. List 3 types of non-functional requirement?
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.
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.
Product requirements, that specify or constrain the softwareʼs behaviour.
Organisational 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.
pf3
pf4

Partial preview of the text

Download Bugs and Errors Bugs and Errors and more Lecture notes Engineering in PDF only on Docsity!

Chapter 4: Requirements Engineering Your name: Answer all questions. 1 mark per question

  1. What are user requirements and system requirements?
  2. What is the distinction between functional and non-functional requirements?
  3. List 3 types of non-functional requirement? 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. 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. Product requirements, that specify or constrain the software ʼ s behaviour. Organisational 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.
  1. What is the software requirements document?

  2. What is the distinction between the termsʼ shallʼ and ʻshouldʼ in a user requirements document, which is written in natural language?

  3. What are the main advantages of using a standard format to specify requirements?

  4. What are the principal stages of the requirements engineering process? The official document that defines the requirements that should be implemented by the system developers. 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.

  5. Requirements elicitation and analysis

  6. Requirements specification

  7. Requirements validation ʻ Shall ʼ normally indicates a mandatory requirement ʻ Should ʼ indicates a desirable but not essential requirement.

  1. What checks should be applied during requirements validation?

  2. List three requirements validation techniques?

  3. What is requirements management?

  4. What are the stages in the requirements change management process?

  5. Validity checks

  6. Consistency checks

  7. Completeness checks

  8. Realism checks

  9. The verifiability of the requirements should be assessed.

  10. Requirements reviews

  11. Prototyping

  12. Test-case generation The process of managing changes to requirements during requirements specification and after the system has gone into use. a. Problem analysis and change specification b. Change analysis and costing c. Change implementation