RE+Lecture+01
12
Requirements Engineering Lecture 01 National University – FAST August 22, 2015, 18:00 – 21:00
Transcript of RE+Lecture+01
Requirements EngineeringLecture 01
National University – FASTAugust 22, 2015, 18:00 – 21:00
2
Course Outline
Software Requirements Engineering
Overview
Business Value of Better
Requirements
Good Practices for
Requirements Engineering
The Role of Requirements
Analyst
Documenting Software
Requirements
3
Course Outline
Quality Aspect of
Requirements Engineering
Requirements Management Principles and
Practices
Improving Requirements
Processes
Use Cases
Risk Management & Software
Requirements
4
Marks Distribution
50%
20%
10%
15%
5%
FinalMidtermQuizReportClass Participation
5
Numbers to RememberMinimum passing marks
62
Minimum attendanc
e
80%
Maximum members in a group
2
Minimum members in a group
2
6
Books to Read
• Karl E. Wiegers• Microsoft Press
Software Requirements
• Karl E. Wiegers• Microsoft Press
More About Software Requirements
7
Course ObjectivesTo know what software requirements engineering is
To understand the need of requirements engineering
To understand your customers and how to interact with them
To learn about the skills of a business analyst
8
Course ObjectivesTo develop, manage and document software requirements
To improve the process of managing software requirements
To define project scope
To reduce risks while managing the requirements
9
What is Requirements EngineeringRequirements engineering is primarily a
communication activity – not a technical activity
Requirements engineering is one of the most challenging aspects of software development
It is also the most important aspect, as it lays the foundation for all the subsequent project work
10
RequirementsAccording to Ian Sommerville and Pete
SawyerA specification of what should be implementedThey are descriptions of how the system should
behave, or of a system property or attributeThey may be a constraint on the development
process of the system
11
RequirementsAccording to IEEE Standard Glossary of
Software Engineering Terminology1. A condition or capability needed by a user to
solve a problem or achieve an objective2. A condition or capability that must be met or
possessed by a system or system component to satisfy a contract, standard, specification, or other formally imposed document
3. A documented representation of a condition or capability as in 1 or 2
12
Levels of RequirementsBusiness RequirementsUser RequirementsFunctional RequirementsSystem RequirementsBusiness RulesQuality AttributesExternal InterfacesConstraints
