OOSE NAAC COmpletedQB

Download as docx, pdf, or txt
Download as docx, pdf, or txt
You are on page 1of 12

APCE/IQAC/QB/1

Om Sakthi
ADHIPARASAKTHI COLLEGE OF ENGINEERING
(NAAC ACCREDITED)
G.B. NAGAR, KALAVAI – 632 506, RANIPET DISTRICT

DEPARTMENT OF INFORMATION TECHNOLOGY

QUESTION BANK

SUBJECT CODE & CCS356 object Oriented CLASS III YEAR - 6th SEM IT
TITLE Software Engineering
COURSE IN-CHARGE Mrs.T.Gnana Abinaya AY 2023-2024 (EVEN SEM)

Vision:

The vision of Information Technology department is to make the students recognized as an


international leader in engineering education,research and application of knowledge to benefit
society globally.

Mission:

We make every decision to support the career and personal development of our students. Our
curriculm, teaching and services demonstrate that we value the diverse profiles of our learners..

Course Outcomes:

CO1 TounderstandSoftwareEngineeringLifecycleModels
CO2 ToPerformsoftwarerequirementsanalysis
CO3 TogainknowledgeoftheSystemAnalysis andDesignconceptsusingUML.
CO4 Tounderstandsoftware testing andmaintenanceapproaches
CO5 ToworkonprojectmanagementschedulingusingDevOps

Blooms Taxonomy:

REMEMBERING UNDERSTANDING APPLYING ANALYSING EVALUATE CREATE


R U A AN E C
PART – A (2 MARKS)
QN.NO QUESTIONS C CO1
1. Write the IEEE definition of software engineering. R CO1
2. Demonstrate your understanding of umbrella activities of a A CO1
Software process.
3. If you have to develop a word processing software product, what A CO1
process model will you choose? Justify your answer and examine.
4. Differentiate verification and validation. Give an example. U CO1
5. List the characteristics of software contrasting it with R CO1
characteristics of hardware.
6. Explain How do we create a process that can manage E CO1
unpredictability?
7. Identify the human factors considered for an agile software R CO1
development.
8. Is it possible to realize Win-Win spiral model for software. A CO1
analyse
9. Summarize the pros and cons of iterative software development E CO1
model.
10. Define agile process. Give any two agile principles. R CO1
11. List two deficiencies in waterfall model. Which process model do R CO1
you suggest to overcome each deficiency.
12. Compare perspective and specialized process model. A CO1
13. Predict about XP story. U CO1
14. Discuss about the various drawbacks of spiral model. U CO1
15. Generalize on any two characteristics of software as a product. C CO1
16. Show what led to the transition from product oriented A CO1
development to process oriented development.
17. Differentiate SDD and DDD. A CO1
18. Create six new practices that are designed to help ensure that an CO1
XP project works successfully for significant projects within a C
large organization.
19. Summarize on extreme programming. U CO1
20. Why system engineers must understand R CO1
PART - B ( 13 MARKS)
1. Define software life cycle. List all life cycle models and explain R CO1
spiral model with a neat diagram.
2. (i)Explain atleast one scenario where CO1
a) RAD model would be applicable and not the waterfall
model.
b) Waterfall model is preferable compare to all other models. A
( ii) What are the pros and cons of using mathematical approach
for software development?
3. (i)Describe about agile modelling in detail. R CO1
(ii)Explain the component based software development model
with a neat sketch.
4. (i) Write short notes on aspect oriented software development. E CO1
(ii) Explain in detail about personal process models and team
process models.
5. (i) What is process model? Describe the process model that you U CO1
would choose to manufacture a car explain giving suitable
reasons.
(ii)Describe the various Evolutionary Process Models with neat
diagram.
6. (i) Compare the life cycle models based on their distinguishing A CO1
factors, strengths and weaknesses.
(ii) Discuss the prototyping model. What is the effect of designing
prototype on the overall cost of the software project?
7. (i) Explain in detail about iterative and waterfall model. A CO1
(ii) Write short notes on concurrent models.
8. (i) Discuss in detail about Scrum. U CO1
(ii) What is the significance of the spiral model when compared
with othermodel?
9. (i) Discuss the Extreme Programming process. CO1
(ii) What are some of the issues that lead to an XP debate? U
10. (i) Illustrate about agility and cost of change. CO1
(ii) What key traits must exist among the people on an effective A
software team?
11. ( i) What is agility in the context of software engineering work? CO1
(ii) List the principles of agile software development. U
12. (i) Compose your view about agile software development. CO1
(ii) Generalize your view about extreme programming. C
13. (i) Describe about pair programming and how unit tests used in CO1
XP? R
(ii) List the new practices appended to XP to create IXP.
14. (i) Explain software product engineering with its services and CO1
advantages. A
(ii) Write a note on the unique characters of a software.
PART – C (15 MARKS)
1. Generalize about system engineering hierarchy with suitable CO1
diagram and give an overview of the Business Process C
Engineering with a diagram.
2. Compare the following life cycle models based on their CO1
distinguishing factors, strength and weakness-waterfall model, AD
model, spiral model and Formal Methods Model. (Present in the E
form of table only-use diagrams wherever necessary).
3. Explain about the umbrella activities which support software CO1
development process and discuss about their necessity in
maintaining the quality in both software process and product that E
is being developed for railway reservation system.
4. Assume that you are the technical manager of a software CO1
development organization. A client approached you for a software
solution the problem stated by the client have uncertainties which E
lead to loss if it not planned and solved which software
development model you will suggest for this project – justify.
Explain that model with its pros and cons and neat sketch.
UNIT – II REQUIREMENTS ANALYSIS AND SPECIFICATION
PART – A (2 MARKS)
Qn.NO QUESTIONS C CO2
1. Give a use case diagram for an online shopping which should CO2
provide provisions for registering authenticating the customers U
and also online payment through any payment gateway like
PayPal.
2. Define feasibility study. And list the types. R CO2
3. Classify the following as functional/non-functional requirements CO2
for a banking system
A
(a) Verifying bank balance
(b) Withdrawing money from bank
(c) Completion of transactions in less than one second.
(d) Extending the system by providing more tellers for the
customers.

4. Draw and explain a simple semantic data model for a library A CO2
Management system.
5. List the characteristics of a good system requirements R CO2
specifications(SRS)
6. Define Quality Function Development(QFD) R CO2
7. How requirements are classified? List them with an example for A CO2
each.
8. Develop the spiral view of requirement engineering process. C CO2
9. Differentiate between normal and exciting requirement. U CO2
10. Point out the problems faced when user requirements are written A CO2
in natural language.
11. Distinguish between the terms inception, elicitation and U CO2
elaboration with reference to requirements.
12. List two advantages of using traceability tables in the R CO2
requirements management phase.
13. Classify the metrics for specifying non-functional requirements. A CO2
14. Express the different types of check list that should be carried out U CO2
for requirement validation process.
15. Explain how to manage changing requirements during the E CO2
requirements elicitation process?
16. What is meant by structural analysis and volatile requirement? R CO2
17. Classify the common data Dictionary notations A CO2
18. Define Petri Net and list types of traceability in a software CO2
process. R
19. Explain, how the requirements are validated? E CO2
20. Generalize on the concept of data dictionary. C CO2
PART – B (13 MARKS)

1. (i) Differentiate functional and non-functional requirements. U CO2


(ii) Give the steps involved in initiating requirements engineering.
2. (i) What are called as non-functional requirements? Explain in CO2
detail. U
(ii) Summarize on user requirements and system requirements in
detail.
3. (i) List and explain the Three aspects that SRS should clearly CO2
document. R
(ii) List the characteristics of good SRS document and their
components.
4. (i) Demonstrate the structure of requirement document. A CO2
(ii) Show the possible users of requirement document.
5. (i) Explain the different ways of writing a system requirement R CO2
specification.
(ii) Describe the spiral view of system requirement.
6. Analyze about the requirement engineering process and how the AN CO2
requirements are managed.
7. (i) What is the purpose of feasibility study? R CO2
(ii) State the inputs and results of the feasibility study.
(iii) List any four issues addressed by a feasibility study.
(iv) Elaborate the phases involved when carrying out a feasibility
study.
8. What is requirement elicitation? Briefly describe the various E CO2
activities performed in requirements elicitation with an example of
a watch system that facilitates to set time and alarm and assess.
9. (i) What is feasibility study? How it helps in requirement CO2
engineering process. C
(ii) How will you classify the requirement types of a project, give
example.
(iii) List the stake holders and all types of requirements for an
online train reservation system.
10. Write short notes on the list given below CO2
(i)Requirements discovery and Interviewing. R
(ii) Scenarios and Use cases.
(iii)Ethnography.
11. (i) Classify the different types of checks carried out on the CO2
requirements in the requirements document during the validation A
process.
(ii) Demonstrate on the requirement validation techniques.
12. (i) Discuss about the requirement management planning. CO2
(ii) Describe about the requirement change management. U
13. (i)Analyze briefly about the structural system analysis in detail. CO2
(ii)Explain about classical perti nets model. AN
14. (i) What is the purpose of data flow diagrams? What are the CO2
notations used for the same? AN
(ii) Explain by constructing a context flow diagram Level-0 DFD
and Level-1 DFD for a library management system.
PART – C ( 15 MARKS)
1. Develop an online railway reservation system, which allows the CO2
user to select route, book/cancel tickets using net C
banking/credit/debit cards. The site also maintains the history of
the passengers. For the above system, list and draw the use case
scenario and model the above specification.
2. Assess on software requirement specification for banking system E CO2
3. Draw and Explain the use case diagram for an ATM system in CO2
requirement elicitation. E
4. Develop the process of ordering a pizza over the phone. Draw the CO2
use case diagram and also sketch the activity diagram representing
each step of the process, from the moment you pick up the phone C
to the point where you start eating the pizza. Include activities that
others need to perform. Add exception handling to the activity
diagram you developed. Consider at least two exceptions (e.g.
delivery person wrote down wrong address, deliver person brings
wrong pizza).
UNIT – III SOFTWARE DESIGN
PART – A (2 MARKS)
QN.NO QUESTIONS C CO3
1. What do you interpret from design heuristics? U CO3
2. List two principles of good design. R CO3
3. What do you infer from the design quality attributes ‘FURPS’? AN CO3
4. Draw the context flow graph of an ATM automation system. R CO3
5. 'A system must be loosely coupled and highly cohesive’. Justify. E CO3
6. Define Modularity. R CO3
7. Give the various types of architectural styles with example. U CO3
8. What is coupling and list the various types of coupling? R CO3
9. How do you apply modularization criteria for U CO3
monolithic software? Discuss.
10. Define mapping. R CO3
11. Analyzean UI design pattern are used for the following. AN CO3
i) Page layout
ii) Tables
iii) Navigation through menus and webpages
iv) Shopping cart.
12. Distinguish between transform flow and transaction flow. U CO3
13. List the basic design principles of class based component. R CO3
14. Point out the steps that are applied to develop a decision table in AN CO3
tabular design notation.
15. Classify the four distinct frame work activity in the user interface A CO3
analysis and design process.
16. Design the architectural context diagram. C CO3
17. In case of user interface analysis, assess the steps E CO3
that are taken for understanding the problems.
18. Classify the user interface design steps. CO3
A
19. Show the facilities to be provided in a system to recover users A CO3
from the mistakes.
20. Generalize on the concept of user interface design pattern. C CO3
PART – B (13 MARKS)
1. Explain the following list of design concept R CO3
(i) Abstraction and Modularity
(ii) Patterns
(iii) Functional independence
2. Explain about software architecture design, with emphasize as fan CO3
in, fan-out, coupling, cohesion and factoring

E
3. Analyzeyour understanding on the following design models A CO3
(i) Data design elements and Architectural design elements.
(ii) Interface design elements and Component-level design
elements. (iii) Deployment-level design elements.
4. (i) Demonstrate in detail about architectural design. A CO3
(ii) Illustrate in detail about any four architectural styles.
5. (i) Give the steps involved in transform mapping. U CO3
(ii) Discuss transform mapping with example.
6. (i) List the steps involved in transaction mapping. R CO3
(ii)Describe transaction mapping with example.
7. (i) Discuss the basic design principles of class based R CO3
components. (ii) Discuss the component-level design
guidelines.
8. Describe the various coupling and cohesion methods used in U CO3
software design.
9. Examine Architectural Styles. CO3
(i) Data centered Architecture and Data Flow Architecture. A
(ii) Call and Return Architecture and Object Oriented
Architecture. (iii) Layered Architecture.
10. (i) Analyze on the concept of graphical design notation. (ii) AN CO3
Explain Tabular Design Notation.
11. i)Describe about user interface analysis in detail. CO3
ii)Explain the general model of a real time system. R
12. (i) Generalize on the concept of user interface design and CO3
list the characteristics of a good user interface design C
(ii) Develop the design issues in interface design.
13. (i) Analyzeabout program design language in designing CO3
conventional components. AN
(ii) Classify and explain the various architectural styles in detail.

14. i)What are? Describe how UID may be developed for a data R CO3
acquition system.
ii)Discuss the design heuristics for effective modularity design.
PART -C ( 15 MARKS)
1. Model a Dataflow diagram for a "Library Management System". E CO3
State andexplain the functional requirements you are considering.
2. What is the purpose of DFD ?what are the components of DFD? C CO3
Design DFD for the following system:
An on-line shopping system for XYZ provides many services and
benefits to its members and staffs. Currently ,XYZ staffs manually
handle the purchasing information with the use of basic office
software, such ass Microsoft office word and excel.it may results
in having mistakes easily and the process is very
inconvenient .XYZ needs an online shopping system at their
intranet based on the requirement of users. XYZ online shopping
system has 5 key features:
i) to provide the user friendly online shopping cart function to
members to replace hardcopy ordering form.
ii)o store inventory and sales information in data base to reduce
the human mistakes, increase accuracy and enhance the
flexibility of information processing.
iii) to provide an efficient inventory system which can help the
XYZ staffs to gain enough information to update the inventory.
iv) to able to print invoice to members and print a set of
summary reports for XYZ internal usage.
v) to design the system that is easy to maintain the upgrade.

3. Summarize on the Hierarchical concept of user interface design E CO3


and Draw the swim lane diagram for prescription refill function.
4. Rewrite the concept of OCP in your own words. Why is it C CO3
important to create abstraction that serve as an interface between
components?
UNIT - IV TESTING AND MAINTENANCE
PART – A (2 MARKS)
Qn.NO QUESTIONS C CO4
1. Describe the objectives of testing. What is “cyclomatic R CO4
complexity”? Point out its primary use.
2. Analyze on what is a “good” test and List two principles of good AN CO4
design.
3. Differentiate verification and validation. Which type of testing CO4
address verification? Which type of address validation? U
4. Identify What methods are used for breaking very long expression R CO4
and statement.
5. What is flow graph notation and Show how it is important in R CO4
white box testing?
6. Measure the performance of equivalence partitioning. E CO4
7. What is controllability in testing? R CO4
8. Point out the purpose of stud and driver used for testing? AN CO4
9. What are the generic characteristics of software testing? R CO4
10. Summarize various testing strategies for conventional software? U CO4
11. Examine how the software Testing results related to the reliability R CO4
of the software.
12. Between “statement coverage and Branch coverage “, Examine A CO4
which is a stronger criteria? Why?
13. Identify and analyze the type of maintenance for each of the A CO4
following:
(a)Correcting the software faults.
(b)Adapting the change in environment.
14. Give the testing principles the software engineer must apply while U CO4
performing the software testing.
15. Generalize your opinion about Smoke Testing. C CO4
16. Classify the Reverse Engineering process. A CO4
17. Show your understanding on maintainability. A CO4
18. Generalize on What options exist when we are faced with a poorly C CO4
designed and implemented program?
19. Give the software reengineering activities. U CO4
20. Assess on BPR model with neat diagram. E CO4
PART – B (13 MARKS)
1. Describe the type’s basic path testing given. CO4
(i)Flow graph notation. R
(ii)Independent program paths.
2. What is black box testing? Explain the different types of black AN
box testing strategies. Explain by considering suitable examples.
3. (i) Write elaborately on unit testing. How do you develop test CO4
suites. R
(ii)Explain how to broaden testing coverage and improve the
quality of white box-testing.
4. (i)What is cyclomatic complexity and what are the ways to CO4
compute it? U
(ii)Give the steps to select the path in data flow testing.
(iii)Explain how the various types of loops are tested.
5. (i) Describe in detail about software testing strategies. R CO4
(ii)Explain in detail about any one control structure testing.
6. (i)Summarize on Top-down Integration testing and Bottom-up CO4
integration testing. U
(ii)Describe business process reengineering.
7. (i)How would you apply your understanding about Software A CO4
implementation techniques.
(ii) What is refactoring? When is it needed? Explain with an
example.
8. (i) Analyze on equivalence partitioning. List rules used to define CO4
valid and invalid equivalence classes. Explain the technique using
examples. AN
(ii) What is boundary value analysis? Explain the technique
specifying rules and its usage with the help of an example.
9. (i) What conclusions can you draw from regression testing? CO4
Support your answer with a neat sketch.
(ii) Explain the list given below E

(a) Reverse Engineering to understand Data.


(b) Reverse Engineering to understand Processing.
(c) Reverse Engineering User Interfaces.

10. Write a generalize concept on the following system testing CO4


(i)Recovery testing and Security testing. C
(ii)Orthogonal array testing and Graph-based testing.
11. (i) Describe in detail about BPR model with a neat diagram. R CO4
(ii)Explain Forward Engineering in detail.
12. Apprise and analyze the purpose of system testing with a high AN CO4
level explanation an all its types.
13. (i)What is the purpose of software reengineering? Explain with a CO4
neat diagram. U
(ii)Summarize the activities involved in software reengineering.
14. (i)Illustrate in detail about Reverse engineering process. CO4
(ii)Explain Forward Engineering for client-server Architectures. A
PART – C ( 15 MARKS)
1. Consider the following program segment. CO4
/*num is the number of function searches in a presorted integer
array arr*/
int bin_ search(int_ num)
{
Int min, max; min=0; max=100;
While(min!=max){
If(arr [(min+ max)/2]>num
Max=(min+ max)/2; E
Else if(arr [(min+ max)/2]
Min= (min+ max)/2;
Else return ((min+ max )/2);
}
Return(-1);
}
(i)Draw the control flow graph for this program segment.
(ii)Define cyclomatic complexity.
(iii)Determine the cyclomatic complexity for this program. (Show
the intermediate steps in your computation. Writing only the final
result is not sufficient)
2. Consider the pseudocode for simple subtraction given below: E CO4
Program ‘Simple Subtraction’
Input(x ,y)
Output(y)
If x> y then DO
x-y =z
else y-x=z
output ‘End Program’
perform the basic path test in and generate test cases. Explain
black box and white box testing.
3. Given a set of numbers ‘n’, the function find prime (a[],n) prints a CO4
number if it is a prime number. Draw a control flow graph,
calculate the cyclomatic complexity and enumerate all paths. State C
how many test cases are needed to adequately cover the code in
terms of branches, decisions and statement? Develop the
necessary test cases using sample values for ‘a’ and ‘n’.
4. Generalize on forward and reverse engineering process in detail. C CO4
UNIT – V PROJECT MANAGEMENT
PART – A (2 MARKS)
Qn.NO QUESTIONS
1. Define risk. What are its type? Give an example. R CO5
2. What is version control? AN
3. Organic software occupies 15,000 LOC. Assess how many E CO5
programmers are needed to complete.

4. Analyze on how are the software risk assessed. AN CO5


5. List out the principles of project scheduling. R CO5
6. Discuss is there a systematic way to sort through the options U CO5
associated with the make/ buy decision?
7. Give the purpose of LOC based estimation. U CO5
8. Compare size oriented and function oriented metrics. E CO5
9. Predict on what is RFP risk Management. U CO5
10. Examine ZIPF’s law. R CO5
11. Describe Earned Value Analysis. R CO5
12. Give some steps in project planning. U CO5
13. Relate task set and network. A CO5
14. Generalize on how productivity and cost related to function C CO5
points.
15. List the two characteristics of software risk. R CO5
16. What are predictable risk? Classify some categories of predictable AN CO5
risk.
17. What do you infer from RMMM? AN CO5
18. Write a note on Risk Information Sheet (RIS). A CO5
19. Show the basic principles that guide software project scheduling. A CO5
PART – B ( 13 MARKS)
20. Generalize on the concept of project metrics. C CO5
1. (i)Examine the activities associated with project process planning. R CO5
(ii)Write short notes on earned value analysis for project tracking.
2. (i)What elements used in COCOMO II model? AN CO5
(ii)Explain in detail about the COCOMO II model for software
estimation.
3. How do you compute Earned Value Analysis and use it to assess CO5
progress. C
4. Develop a program for sorting of n numbers. Draw the Flow chart, E CO5
Flow graph, find out the cyclomatic complexity. (MAKE AND
BUY)
5. (i)Summarize on purpose of Delphi method. State advantages and CO5
disadvantages of the method. U
(ii)Discuss the steps involved in project planning.
(iii)state ZIPF’s law.
6. Demonstrate on the following list given below CO5
(i)Function Point estimation. A
(ii)LOC based estimation.
7. Describe in detail about the following scheduling CO5
(i)Timeline charts. R
(ii)Tracking the schedule.
(iii)Tracking progress for an OO project.
8. (i)Explain in detail about risk identification. AN CO5
(ii)Analyze on the concept of risk projection.
9. (i)Discuss about risk management in a software development life U CO5
cycle.
(ii)Discuss on the concept of RMMM.
10. Discuss the process of functional point analysis. Explain the CO5
function point analysis with sample cases for components of R
different complexity.
(i)Describe a task set for the software project.
11. (i) Explain in detail COCOMO model for software cost CO5
estimation. AN
(ii)If a team A found 342 errors prior to release of software and
team B found 182 errors. What additional measures and metrics
are needed to find out if the teams have removed the errors
effectively? Analyze.
12. (i) Apply COCOMO -II model to estimate total time and effort CO5
required to develop a software of KLOC 230. A
(ii) Outline the importance of “project scheduling and use of Gantt
charts”.
13. Consider the following Function point components and their CO5
complexity. If the total degree of influences is 52, Predict the U
estimated function points.
Function type Estimated count complexity
ELF 2 7
ILF 42 10
EQ 22 4
EO 16 5
EI 24 4
14. (i) Describe in detail about Process Metrics. CO5
(ii) How should we use metrics during the project itself? R
PART – C (15 -MARKS)
1. Compute and prepare function point value for a project with the CO5
following information domain characteristics.
No. of external inputs- 30 C
No. of external outputs- 52
No. of external inquiries- 22
No. of logical files- 12
No. of external interface files- 2
Assume complexity adjustment values for the above are average
(4, 5, 4, 10, 7 respectively).
2. Prepare RIS Sheets for any two risk associated with “Automated C CO5
Airline controller” software.
3. Explain in detail about COCOMO model for software cost CO5
estimation. Use it to estimate the effort required to build software E
for a simple ATM that produces 12 screens, 10 reports and has 80
software components. Assume average complexity and average
developer maturity. Use application composition model with
object points.
4. Suppose you have a budget cost of a project as Rs.9,00,000. The CO5
project is to be completed in 9 months. After a month, you have
completed 10 percent of the project at a total expense of E
Rs.1,00,000. The planned completion should have been 15
percent. You need to evaluate whether project is on- time and on-
budget? Use Earned Value analysis approach and interpret.

CLASS INCHARGE HOD PRINCIPAL

You might also like