Software Requirements Engineering UOS — University of Sargodha 2015
Discussion
Ask a question about this paper, or help someone else with theirs. Answers are emailed to whoever asked.
No questions yet — be the first to ask.
More Software Requirements Engineering papers
See all
Paper text
Department of CS & IT, University of the Sargodha
Software Requirement Engineering
Mid Term Paper Spring 2015
Time: 1 hrs
Total Marks: 20
Roll No:
Class:
Answer the following question briefly & give example when required: 10*2
1. How Software requirements Serves as a basis for project planning?
2. If all the stakeholders of a software, have different needs, then what methodology
should be adopted by the requirement management team?
3. Define some of the Software Requirement challenges?
4. Why NFRs are often more critical than individual functional requirements?
5. Why Goals are open to misinterpretation & conflicts and how these issues can be
fixed?
6. What are the pros and cons by including too much information in user
requirements?
7. Why it's important to associate rationale with requirements?
8. What are the ISV softwares, name some of them?
9. How requirement Management team purely apply their skills in Land of solution?
10. If a unit cost of 20 is assigned to the effort required to detect and repair an error
during the coding stage, calculate the effort values for remaining stages?
(Hint: use the ratio value as discussed in lecture)
Stage
Requirements time
Design
Coding
Unit test
Acceptance test
Maintenance
Relative Cost to Repair