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 .

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

4. 
 haroon.waheed@ucp.edu.pk

4
Days
10:00-
10:55
11:00-
11:55
14:00-
14:55
15:00-
15:55
16:00-
16:55
17:00-
17:55
MONDAY [SESD3242] Scd-Se
(R1) A-304
TUESDAY [SENS3513] Os-Se-T (Q2) C-308
THURSDAY [SESD2213] Sre-Se (O5) C-310
MONDAY
WEDNESDAY
FRIDAY
10:00 AM---6:30 PM
TUESDAY 10:00 AM---5:00 PM
THURSDAY 11:30 PM---7:30 PM

5. 













6. 




7. 



8. 






9. 





10. 



11. 








12. 





13. 








14. 


15. 







16. 





17. 




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

19. 





20. 






21. 








22. 



23. 




24. 



25. 




26. 



27. 



28. 








29. 







30. 

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

35. 



 http://calleam.com/WTPF/?p=4079

36. 




 FBI Virtual case file

37. 


 US Census Bureau Field Data Collection
Automation project

38. 





 Denver baggage system
 Transit Ticketing Authority – Australia

39. 




 New South Wales – Australia
 Lufthansa Systems – Germany

40. 




 Fox-Meyer Drug
 Census Bureau – USA

41. 



 The Vasa
 British Airways Terminal 5 transition – UK

42. 




 Qantas Jetsmart
 Department of homeland security – USA
 Census Bureau – USA

43. 






44. 







45. 



46. 










47. 







48. 




49. 








50. 




51. 



52. 






53. 





54. 


