About Me

Software Requirement Engineering 2nd Jun2012 IT9222

Sponsored Ads:

Quick Links
University Papers University Syllabus Entrance Exam
PSU Papers Bank Papers Placement Papers
VTU Anna Univerity Syllabus Anna Univerity Papers
Second semester
Information Technology
(Regulation 2009)

GATE  |  TANCET  |  Govt & PSU Papers  |  Bank Papers  |  Travel Tips

University Papers  |  Programming, Interview Questions  |  Share market


Other Departments Papers: Click Here

Download PDF File - Click Here

PART A— (10 × 2 = 20 marks)

1. What is “Scope creep”? How can this be managed?
2. Identify the inconsistencies, ambiguities and incompleteness of the following requirement:
“The CGPA of each student is computed as the average performance for the semester.Alt students having poor performance are mailed a letter informing about the poor performance and warning that the poor performance should not be repeated”.
3. List any two requirements bill of rights and requirements bill of responsibilities for software customers.
4. Distinguish between functional and non functional requirements.
5. What are the major outcomes of requirements feasibility study?
6. Outline the role of moderator in reviewing requirements.
7. What is a use-case and how is this helpful in requirements documentation?
8. Why do we need to specify the types of users (who will be using the system) in requirements specification?
9. How can requirements be tested? Give an example.
10. Establish the need for requirement traceability with two distinct reasons.

PART B— (5 × 16 = 80 marks)

11. (a) (i) Describe “Business Requirements” and “User Requirements” with suitable examples. (8)
(ii) Enumerate and explain the major advantages of iterative life cycle models in requirements management. (8)
(b) (i) Summarize the impact of requirements management towards the success of a software project. (8)
(ii) Justify that the cost of fixing an error during requirements gathering phase is much less compared to fixing the same error during testing. (8)

12. (a) Compare the traditional collaborative and cognitive techniques of requirement gathering. Give one example project situation for which these methods are most situated. (16)
(b) Briefly state the difficulties involved in requirements elicitation. Suggest guidelines to overcome these difficulties. (16)

13. (a) Consider a “Weekly Activity Report” system, which is to be used by the Employees of a software development firm for recording the time spent on various
activities done during the course of any given week. You are given responsibility of analyzing the system for estimation purpose. Prepare a software requirement
specification document showing the objective purpose, users, functional requirements and possible non- functional requirements of the system. Clearly define boundaries for the system and list your assumption Also, develop an analysis model to represent the system. (16)
(b) You are responsible for development of an electronic mail system to be implemented over a network. The system will enable users to create letters to be
mailed to another user or to a specific list of people. Letters can be read, copied, stored etc. the system will make use of the existing word processor for creating letters. Using this as the initial requirements, derive a set of concrete requirements for building it as a software product to be marketed. Also, draw the context diagram and a set of data flow diagrams to help in analyzing the requirements specified. (16)

14. (a) (i) Describe a set of attributes that are essential for a requirements document.(8)
(ii) Discuss about the role of change control in requirements management.(8)
(b) (i) Explain the different types of software prototyping highlighting their relative merits. (10)
(ii) You have developed a throwaway prototype system for a client who is very happy with it. However the client suggests that there is no need to develop
another system. But that you should deliver the prototype and offer an excellent price. You know that there may be future problems with maintaining the system. Discuss how you might respond to this customer. (6)
15. (a) (i) Briefly explain the methodology of requirements tracing. (8)
(ii) Comment on the applicability of commercial tools in requirements management. (8)
(b) Write short notes on the following:
(i) CASE tools for the requirement engineering (8)
(ii) Guidelines for conducting requirements inspection. (8)

Post a Comment