FSE Module 3 - Requirements Engineering Part 1

CSEB233 Fundamental of SE , Module 3 Requirements Engineering Part 1

What are requirements?
A condition needed by a user to achieve an objective.

Types of requiremnents
-functional requirements
1.not include quality statement such as fast ,efficient, usable, reliable
2. tell users how the system should react to certain inputs.
-non-functional requirements
1. quality attributes such as security, safety, performance
2. quality characteristic of the software to develop the software

Why Requirement important?
-Cause the development cost, time, effort and quality of the porduct.
-Important step to determine the overall of the software product.

Requirement process
1.RE elicitation (discover requirements from the stakeholders)
-understanding application domain
-understanding problem to be solved
-understanding business processes
-by using joint application design(JAD),interviews and questionaires

2.RE analysis and negotiation
-interaction matrix to identify conflicts and overlaps
-Discussion session in meeting to effectively to negotiate and solve conflicts

3.RE specification(to build the requirement documents)
Attributes –correct,consistent, complete(3 S)

4.RE verification and validation(check the product meets its specification)
-deskcheck
-walkthrough
-inspection
-checklist

5.RE management(managing changes to requirements)
-prevents unauthorised destructive changes to the requirements
-preserves the revision to requirements document
-prevent simultaneous updates of requirements documents

I think NFRs: qualities is not important because it does not really related to requirement.The groundwork and tracking requirements status are just further explanation about RE, therefore no major importances in it.

I would like to suggest to do a simple and creative mind map and pass up on that particular day as well and prepare prizes to the best creative mind map.

Pavithran
IS086067