Software requirement engineering.
IT Project Management Challenges.
Requirements and Project Failure.
What are Requirements?
A capability that the system must deliver or a condition that it must satisfy in order to address a need of a stakeholder.
Requirement Engineering Vs Software Requirement Engineering.
The process of establishing the services that the customer requires from a system and the constraints under which it operates and is developed
Requirements may be functional or non-functional .
Direct Style Effect Systems -The Print[A] Example- A Comprehension Aid
F22 SRE LECTURE 1.pptx
1.
2.
3. 3
Assistant Professor
Department of Software Engineering, FOIT – University of Central Punjab, Pakistan (Sep 2012 –
Present).
Worked in Academia and Industry
Taught Undergraduate courses at like
SE, SRE, ISD .
OS, DSA, OOP, PF, ITC
Research Interests:
Software Engineering and Allied
Data Analytics
Applied Artificial Intelligence
Software Processes & Metrics.
PhD in Progress
M.Sc (Advanced Methods in CS) – QMUL UK
MS (Computer Science) – Lahore University of Management Sciences (LUMS), Pakistan.
BS (CS) UCP Lahore
18. Requirements Engineering (RE) is a set of
activities concerned with identifying and
communicating the purpose of a
software-intensive system, and the
contexts in which it will be used. Hence,
RE acts as the bridge between the real
world needs of users, customers, and
other constituencies affected by a
software system, and the capabilities and
opportunities afforded by software
intensive technologies
Not a phase or stage
Communication is as important as
the analysis
Quality means fitness-for-purpose.
Cannot say anything about quality
unless you understand the purpose
Designers need to know how and
where the system will be used
Requirements are partly about
what is needed…
Need to identify all the stakeholders
- not just the customer and user
…and partly about what is
possible
33. Requirements Engineering (RE) is a set of
activities concerned with identifying and
communicating the purpose of a
software-intensive system, and the
contexts in which it will be used. Hence,
RE acts as the bridge between the real
world needs of users, customers, and
other constituencies affected by a
software system, and the capabilities and
opportunities afforded by software
intensive technologies
Not a phase or stage
Communication is as important as
the analysis
Quality means fitness-for-purpose.
Cannot say anything about quality
unless you understand the purpose
Designers need to know how and
where the system will be used
Requirements are partly about
what is needed…
Need to identify all the stakeholders
- not just the customer and user
…and partly about what is
possible