0% found this document useful (0 votes)
31 views4 pages

B.SC (Hons) Computer Science Software Engineering Sem IV 853

jkkjhkh

Uploaded by

xivisan298
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF or read online on Scribd
0% found this document useful (0 votes)
31 views4 pages

B.SC (Hons) Computer Science Software Engineering Sem IV 853

jkkjhkh

Uploaded by

xivisan298
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF or read online on Scribd
You are on page 1/ 4
[This question paper contains 4 printed pages.] Sr.No. of Question Paper : 853 E Your Roll No... Unique Paper Code 2 234405 Name of the Course: B.Se. (H) Computer Science Name of the Paper : Software Engineering Semester iV Duration : 3 Hours Maximum Marks : 75 Instructions for Candidates 1. Write your Roll No. on the top immediately on receipt of this question paper. The paper has two sections. All questions in ‘Section A’ are compulsory. Attempt any four questions from ‘Section B’. SECTIONA (@ Define Software Engineering. Why is it called Layered Technology? (3) (i) What is Prototyping Process Model ? Under what circumstances, it is recommended. @) Gii) “A high quality SRS (oftware Requirement Specification) is a pre-requisite toa high quality software.” — Justify the statement. @) Gv) What is Requirement Process ? What is its work product ? @) (¥) What are the various metrics for Software Quality ? Explain any one. (3) (vi) What is an ‘object point’ in the COCOMO II Model ? Q) (vii) Explain the reactive and the proactive risk strategies. to deal with software development risks. @) PLO, 853 2 (viii) Explain any three levels of Cohesion. @) (ix) What is Defect Removal Efficiency (DRE) ? How it is used to access the team’s ability to find errors, as they are passed to the next framework activity ? Q) (x) Briefly explain any three roles of an SQA (Software Quality Assurance) group. 6) (xi) What is verification and validation ? Explain with reference to Software testing. @) (xii) What is Boundary Value Analysis (BVA) ? What are the guidelines to create BVA test cases ? @) SECTION B 2. (a) What does the Capability Maturity Model Integration (CMMI) determine ? Explain its five capability levels. ©) (b) What are umbrella activities ? List-any four umbrella activities. (5) 3. Assume that you have to build a software system that : (@ allows students to submit their assignments, ii) provides an environment to the teachers to evaluate them and (ii) generates the result with minimum input. Draw a context diagram and level 1 DFD of the above requirements of the system. (10) 4. (@) Create a flow graph to find the cyclomatic complexity of the following code. ‘Also show the no. of independent paths and regions : long int factorial (int n) { long int fact = 1; while (n> 1) { fact = fact * n; a } retum fact; 3 6) (6) Explain white box and black box testing methods. @ 5. (a) Compute the Function Point value for a project with the following information domain characteristics : Number of user inputs Number of user outputs ‘Number of user inquiries Number of files ‘Number of extemal interfaces Assume the measurement parameters equally divided among low, average and high complexity. Further, assume that the complexity adjustment value is 1.25. () (b) Determine the cost and efforts required for the above (QS (a)) software project. Assume the average productivity for the project is 5 FP/pm and the labor rate of Rs. 40,000 per month. @ PTO. 853 4 6. (a) State the significance of a Gantt chart for scheduling and monitoring a software project. (5) (b) How does the consequences of a risk in a software project assessed ? 6) 7. Write differences between the followings (Attempt any four) : () Error vs Defect (i Analysis and Design model (ii) Direct and Indirect measures of Software (iv) Alpha and Beta testing (¥) Top-down and Bottom-up Integration Testing (10) (200)

You might also like