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

SEN QB

The document is a comprehensive questionnaire covering various aspects of software engineering, including software characteristics, risk management strategies, software requirements specifications, cost estimation approaches, and software quality assurance. It also discusses project scheduling principles, software process models, testing methodologies, and the COCOMO model for project estimation. Additionally, it includes requests for diagrams such as data flow diagrams, use case diagrams, and Gantt charts, along with explanations of key software engineering concepts.

Uploaded by

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

SEN QB

The document is a comprehensive questionnaire covering various aspects of software engineering, including software characteristics, risk management strategies, software requirements specifications, cost estimation approaches, and software quality assurance. It also discusses project scheduling principles, software process models, testing methodologies, and the COCOMO model for project estimation. Additionally, it includes requests for diagrams such as data flow diagrams, use case diagrams, and Gantt charts, along with explanations of key software engineering concepts.

Uploaded by

givaxol129
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 4

SOFTWARE ENGINEERING QB

Q1.

a) Enlist and explain software characteristics / four types of risks

b) Define software on engineering / Reactive Risk strategies / software requirements specifications /


Proactive and Reactive risk strategy / software quality / empirical estimation approach.

c) State need of software requirement specification (SRS) / two characteristics of Software / .

d) Name two cost estimation approaches / four software quality assurance activities .

e) Specify following cost directives of cocomo: (i) Product attributes (any two) (ii) Hardware
attributes (any two).

f) Differentiate between Software Quality Management and Software Quality Assurance / quality
assurance and quality control (any two points).

g) Define Software Quality Assurance / project Cost Estimation/ software engineering / risk and list
any two type of risk.

h) List : any four types of software.

any four planning principles

4P’s of Management spectrum.

any four selection criteria for Software Process Model

any four characteristics of good SRS.

the phases of software quality assurance.

i)Describe following design concepts i) Abstraction ii) Information hiding.

j) Draw layered approach of software engineering.

Q2.

a) Explain : Software Engineering as layered technology approach.


: the notations used for preparing a Data Flow diagram.
: four basic principles of software Project Scheduling
: Waterfall Model with neat labelled diagram
: CMMI in detail with neat diagram.
: characteristics of software.
: the following 4P’s management spectrum.

b) Explain with example Decision table.

c) Explain following elements of management spectrum: (i) People (ii) Process (iii) Product (iv) Project

: i) Test Case ii) Test Data iii) Test Plan


d) List and explain : basic principles of project scheduling.

: describe any four core principles.

e) State and explain with examples four broad categories of software.

f) Describe : 4 ‘P’s of management spectrum giving their significance.

: the notations used for preparing a structured chart.

: work breakdown structure with diagram.

Q3.

a) Distinguish between perspective process model and agile process model.

b) Describe : any four principles of communication for software engineering.

: four principles of good planning.

: any four software coding principles.

c) Draw : proper labeled “LEVEL I Data Flow Diagram” (DFD) for student attendance system.

: explain Level 1 DFD for railway reservation system

: DFD0 and DFD1 diagram for Library Management System

d) State : importance of “Function Point (FP)” and “Lines of codes (LOC)” in concerned with project
estimation.

: describe any four deployment principles

: describe two metrics of project size estimation.

: the requirements to apply RAD.

: project size estimation techniques and explain any one.

e) Explain : process framework with a suitable diagram.

: line of code metrics for size estimation.

f) With an example, explain Line of Code (LOC) based estimation.

g) Prepare : Macro Timeline chart for 20 days of Hotel Management system (6 days a week) consider
broad phase of SDLC.

: decision table for accessing secured network


Q4.

a) Describe : extreme programming with proper diagram


: the Analytical method of project cost estimation with example
: any four core principles of software engineering practices.

b) List and explain any “four core principles” of software engineering.

c) Explain : RMMM plan with example.

: waterfall process model. State its advantages and disadvantages.

: any one project cost estimation approach.

: GANTT chart and its application for project tracking with an example.

: i) Speculation ii) Collaboration

: i) Heuristic ii) Empirical

: Heuristic method of cost estimation approach.

d) Draw and explain Software Engineering Layered technology approach.

e) Prepare : time line chart for Library Managements System (five days a week) Consider phases of
SDLC.

: Gantt chart for hostel management system. (Five days a week). consider phases of SDLC.

f) Enlist core principles of Software engineering practice.

g) State : the need of SRS and also enlist the characteristics.

: describe any four basic project scheduling principles.

h) Distinguish between Black Box and White Box testing.

Q5.

a) Enlist Requirement Gathering and Analysis for web based project for registering candidates for
contest (any six points).

b) Differentiate between : White box and Black box testing (any six points).

: black box testing and white box testing

c) Describe Co-Como II model for evaluating size of software project with any three parameters in
detail.

d) Sketch a use case diagram for library management system with minimum four use cases and two
actors.

e) Explain : the concept of Black box testing and white box testing.

: software process framework with neat labelled diagram and also describe software
process framework activities.
f) Calculate using COCOMO model (i) Effort (ii) Project duration (iii) Average staff size if estimated size
of project is 200 KLOC using organic mode.

g) Draw and explain : translating requirement model into design model.

: use-case diagram for ATM system with minimum four use cases and two actors.

h) Describe following project cost estimation approaches. i) Heuristic ii) Analytical iii) Empirical

i) Describe a cocomo and cocomo-II models

Q6.

a) Draw and explain : Transition diagram from requirement model to design model.
: conceptual data model with E-R diagram for employee management
system.

b) Describe : CMMI. Give significance of each level.

: six Sigma Strategy in details.

c) Identify and enlist requirement for given modules of employee management software: (i)
Employee detail (ii) Employee salary (iii) Employee performance.

d) Define data objects, attributes, relationship, cardinality with example of each.

e) Compare CMMI and ISO for software w.r.to i) Scope ii) Approach iii) Implementation.

f) Explain six functions of requirement engineering process

g) State and describe any six communication principles.

h) Use COCOMO model to calculate. i) Effort ii) Development Time iii) Average staff size iv)
Productivity if estimated size of project is 400 KLOC using embedded mode.

i) State requirements for given modules of online shopping system. i) Order module ii) Accountant
module iii) Categories module

You might also like