Vel Tech Rangarajan Dr.

Sagunthala R&D Institute of Science and Technology

(Deemed to be University Estd. u/s 3 of UGC Act, 1956)
School of Computing
VTR UGE 2021- (CBCS)
B.Tech. – Computer Science and Engineering
Question Bank – Integrated Courses
Academic Year: 2024 - 25
Course Category : Program Core
Course Code / Title : 10211CS208/ Software Engineering
Semester : Winter 24-25
Achievable Course Outcomes
CO1 : Identify the suitable process model for software development. K3
CO2 : Prepare the SRS document with project estimation and plan. K3
CO3 : Design the UML Diagrams to develop a software application. K3
CO4 : Apply the software design heuristics for quality improvement K3
CO5 : Build Test cases using various testing strategies. K3

Integrated Courses
Question Unit I Unit II Unit III Unit IV Unit V
Type
2 marks 10 Questions 10 Questions 10 Questions 10 Questions 10 Questions
3 marks 10 Questions 10 Questions 10 Questions 10 Questions 10 Questions
5 marks 10 Questions 10 Questions 10 Questions 10 Questions 10 Questions
Total 30 30 30 30 30
Note:
• 5 Marks and 3 Marks need to be only in K2 or K3 level as per the CO and equal distribution of
questions must be given in K2 and K3 levels.
• 5 Mark Question can also contain subdivisions but provide the evaluation scheme.
• 2 marks questions must be in K1 and or K2 level with equal distribution of questions in K1 and K2
level.
• Please provide only standard questions kindly try to avoid direct questions.
• Use Font Times New Roman font with 12 pt.
• Follow the Revised Bloom's Taxonomy action verbs only.
• Sketches, drawings, and figures should be clearly and neatly presented.
• For problem-based courses, need to provide problematic questions with 70% and theory questions
for 30%.
• Answer Key with scheme need to be provided along with the Question Bank but as a separate file.

1
 REFERENCES
Bloom’s Taxonomical Terms and Definitions
Bloom’s
S.No. Taxonomical Definitions Possible Words in Questions
Level

Cite, Define, Describe, Identify, Label, List,

Match, Name, Outline, Quote, Recall, Report,
K1: Recall facts, basic Reproduce, Retrieve, Show, State, Tabulate,
1
Remembering concepts, or answers. Tell, Choose, Find, How, Omit, Relate, Select,
Spell, Tell, What, When, Where, Which, Who,
Why.
Abstract, Arrange, Articulate, Associate,
Categorize, Clarify, Classify, Compare,
Compute, Conclude, Contrast, Defend, Diagram,
Demonstrate
Differentiate, Discuss, Distinguish, Estimate,
K2: comprehension by
2 Exemplify, Explain, Extend, Extrapolate,
Understanding organizing, comparing,
Generalize, Give Examples Of, Illustrate, Infer,
translating, or
Interpolate, Interpret, Match, Outline,
summarizing,
Paraphrase, Predict, Rearrange, Reorder,
Rephrase, Represent, Restate, Summarize,
Transform, Translate, Demonstrate.
Apply, Calculate, Carry Out, Classify, Complete,
Compute, Demonstrate, Dramatize, Employ,
Examine, Execute, Experiment, Generalize,
Use information in new Illustrate, Implement, Infer, Interpret,
3 K3: Applying situations or solve Manipulate, Modify, Operate, Organize, Outline,
problems, Predict, Solve, Transfer, Translate, Use, Build,
Choose, Construct, Develop, Experiment with,
Make use of, Model, Organize, Plan, Select,
Solve, Utilize.

Unit – I
Unit Contents: Software Development Process Models
Introduction to Software Engineering - Software Development process models – Waterfall Model,
Incremental Model, Spiral Model, V Model – Agile Development-Agile Methodologies – Agile Principles-
SCRUM and XP - Project management- Stages of Project management- 4 P’s of project management –
Process & Project metrics. Case Study: The Railways tracking – Arrival Time Prediction System.

Two Marks Questions.

Course
*Q.Nos. 1- 5 first half Portion of unit syllabus and Q.No 6 - 10 Marks Level
Outcome
from the second half portion of syllabus
1. Software Engineering is the process of designing, developing, testing, 2 CO1 K1
and maintaining software. It is a systematic and disciplined approach
to software development that aims to create high-quality, reliable,
and maintainable software.

2
2. A process is a set procedure that involves a sequence of steps that 2 CO1 K2
need to be taken in order to produce a result, whereas a project is a
temporary course of action that aims to deliver a distinctive product,
service, or result.
3. The Waterfall model is a linear, sequential process where each stage 2 CO1 K2
must be completed before moving to the next. Agile development is
iterative and incremental, with frequent feedback loops and the
ability to adapt to changing requirements
4. • Curious and open-minded. 2 CO1 K2
• Self-motivated and proactive.
• Ability to work well under pressure.
• Good at prioritizing tasks.
• Empathetic and strong interpersonal skills.
• Humble and willing to learn from others.
• Strong sense of responsibility and ownership.
5. Collecting User Scenario from the Clients, Prioritize the features, 2 CO1 K1
Project Management.
6. Initiating Processes, Planning Processes , Executing Processes , 2 CO1 K1
Controlling Processes , Closure Processes
7. 1. Define the scope and complexity of the project. The first step 2 CO1 K1
in estimating the time needed for software development is to
define the scope of the project.
2. Create a task list.
3. Make your own software estimate.
4. Conduct team meetings.
5. Establish a project timeline.
8. Verification :Are we building the product right? 2 CO1 K2
Validation:Are we building the right product?
9. Trust between customers and developers is established and a positive 2 CO1 K1
culture is created in which everyone expects the project to succeed•
Customers see on-time delivery of increments and gain feedback on
how the product works. • The whole team has visibility of everything
and consequently team communication is improved. • Unstable
requirements do not hold up progress. •The product is broken down
into a set of manageable and understandable chunks.
10. People, Product, Process and Project 2 CO1 K1

Three Marks Questions.

Course
*Q.Nos. 1- 5 first half Portion of unit syllabus and Q.No 6 - 10 Marks Level
Outcome
from the second half portion of syllabus
1. 1. Requirement compromises are inevitable. - Agile 3 CO1 K3
2. Requirements are not very clear - Incremental
Identification - 1 mark Justification 2 marks
2. Identification of a suitable software development model: 3 CO1 K3

3
 Waterfall, Incremental, Spiral, V-Model, or Agile (1 mark).
Justification of the choice:
Explanation of why the chosen model is appropriate for a Railways
Arrival Time Prediction System (e.g., Agile for flexibility, Spiral for
risk management, or Incremental for step-by-step delivery) (1.5
marks).
Relevance to the context (Railways tracking system):
Clear link between the model's features and the system's
requirements, such as real-time updates, adaptability, or iterative
development (0.5 marks).
3. waterfall model can be accommodated in the spiral process model by 3 CO1 K3
having each iteration represent a phase of the waterfall model. For
example, the first iteration could focus on requirements gathering and
analysis, the second on design, the third on implementation, and so
on.

Similarly, the prototyping model can be accommodated by using the

spiral model's iterative nature to create and refine prototypes in each
iteration, incorporating user feedback and refining the prototype until
it • People: Managing individuals and teams involved in the project.
• Product: Defining objectives, scope, and deliverables.
• Process: Selecting and following a suitable development
methodology.
• Project: Planning, scheduling, and monitoring the project's progress.
evolves into the final product. - Explanation 3 Marks
4. 1.Generates working software quickly and early during the software 3 CO1 K3
life cycle. 2.This model is more flexible – less costly to change scope
and requirements.
3.It is easier to test and debug during a smaller iteration.
4.In this model customer can respond to each built.
5.Lowers initial delivery cost.
5. 1. Project Management,2. Configuration Management,3. Quality 3 CO1 K2
Assurance (QA),4. Risk Management,5. Measurement and Metrics,6.
Documentation,7. Change Management,8. Training and Support,9.
Maintenance
6. • People: Managing individuals and teams involved in the project. 3 CO1 K2
• Product: Defining objectives, scope, and deliverables.
• Process: Selecting and following a suitable development
methodology.
• Project: Planning, scheduling, and monitoring the project's progress.
7. 1.Structured Approach 2.Consistency and Quality 3.Improved 3 CO1 K2
Management and Efficiency Listing significance-1, Explanation-2
8. Team capability, Customer involvement, Psychological safety, Team 3 CO1 K3
autonomy, Scrum , XP
9. Customer collaboration over contract negotiation 3 CO1 K2
Responding to change over following a plan
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Emphasizing flexibility, iterative development, and delivering value
4
 to customer
10. Requirement gathering 3 CO1 K2
Design the Requirements
Construction / Iteration
Testing / Quality Assurance
Deployment
Feedback

Five Marks Questions.

Course
*Q.Nos. 1- 5 first half Portion of unit syllabus and Q.No 6 - 10 Marks Level
Outcome
from the second half portion of syllabus
1. Waterfall model diagram and concepts (3 mark), 5 CO1 K3
pros and cons (2 mark)
2. Sdlc Cyle - Definition - 1 Mark, Diagram -1 Mark, Explanation 1 5 CO1 K3
Mark, Framework Activities And Umberlla Activities - 2 Marks
3. software project management-Definition-1 Mark , Diagram-1 Mark , 5 CO1 K2
steps-1 Mark ,Explanation-2 Marks
4. Example-2 Marks, Explanation-3 Marks 5 CO1 K2
5. Manifesto for Agile Software Development-2marks, 12 principles 5 CO1 K2
Explanation-3marks
6. feature-2, phase-1,pro and cons-2 5 CO1 K3
7. Definition-2, Explanation with diagram-3 5 CO1 K3
8. Introduction to the Models -2 Marks,Comparison Explanantion -3 5 CO1 K2
Marks
9. XP Defnition 2 Marks, Explanation with pair programming and 5 CO1 K2
continous integration 3 Marks
10. List of all metrics-2 Marks,Explanantion-3 Marks 5 CO1 K2

Unit – II
Unit Contents: System Requirements Specification, Planning & Scheduling
Software Requirements Specification - Software project planning - Software Estimation – Empirical
Estimation Models–Software Project Scheduling – Risk Management – Software risks – Risk identification
– Risk projection – Risk refinement - Defect Prevention. Case Study: Preparation of SRS for the camera
motion sensor system for home automation.

Two Marks Questions.

*Q.Nos. 1- 5 first half Portion of unit syllabus and Q.No 6 - 10 Course
from the second half portion of syllabus Marks Level
Outcome

5
1. An SRS document serves as a formal contract between the software 2 CO2 K1
development team and the client. It outlines the functional and non-
functional requirements of the software system, ensuring that both
parties have a clear understanding of the system's expected behavior
and qualities.
2. Lack of planning is a primary cause of schedule slippage, cost 2 CO2 K1
overruns, poor quality, and high maintenance costs for software.
3. COCOMO stands for COnstructive COst MOdel.COCOMO predicts 2 CO2 K1
the efforts and schedule of a software product based on the size of the
software. Proposed by Boehm
4. Risk projection estimates the possibility and impact of identified 2 CO2 K2
risks, while risk refinement provides detailed strategies to address
and minimize these risks.
5. 1. Communication between Stakeholders 2 CO2 K1
Clear understanding: The SRS acts as a formal document that
provides a clear, detailed description of the system's functionality and
requirements
2. Foundation for Design and Development
Guiding development: The SRS serves as a blueprint for the design
and development teams, guiding them in building the software
according to specified requirements.
6. Expected requirements: These requirements are implicit to the 2 CO2 K2
product or system and may be so fundamental that the customer does
not explicitly state them. Exciting requirements: These requirements
reflect features that go beyond the customer's expectations and prove
to be very satisfying when present.
7. Risk projection is a proactive approach to identifying and addressing 2 CO2 K1
potential challenges before they escalate. It's also called risk
estimation.
8. SRS is a document that is created by the development team in 2 CO2 K1
collaboration with Business Analysts and environment/data teams.
9. Functional Requirements: 2 CO2 K2
A functional requirement defines a system or its component.
Functional requirement is specified by User.
It specifies “What should the software system do?”
Non Functional Requirements
A non-functional requirement defines the quality attribute of a
software system.
Non-functional requirement is specified by technical peoples e.g.
Architect, Technical leaders and software developers.
It places constraints on “How should the software system fulfill the
functional requirements?”
10. Process of restating the risks as a set of more detailed risks that will 2 CO2 K1
be easier to mitigate, monitor, and manage

Three Marks Questions Marks Course Level

6
 *Q.Nos. 1- 5 first half Portion of unit syllabus and Q.No 6 - 10 Outcome
from the second half portion of syllabus
1. 12 principles to be listed - 3 marks 3 CO2 K2

2. Identification of Risks (1 Mark) 3 CO2 K3

Identifies three relevant risks (e.g., hardware failure, software
integration issues, data privacy concerns). Each risk correctly
identified: 0.33 marks (total 1 mark)
Explanation of Risks (1 Mark)
Clear and accurate explanation of how each risk impacts the project.
3. 1.Providing feedback to the customer -SRS should be written in a 3 CO2 K2
natural language, in an unambiguous manner
2.Decomposing the problem into component parts -The information
is organized, borders are placed, ideas solidified
3.Serving as an input to the design specification -As a parent
document, it comes prior to the design specification.
They Must contain sufficient details about the functional system’s
requirements for the design solution to be devised
4.Serving as a product validation check-Is also the parent document
for testing and validation strategies is a basis for estimating costs and
schedules
4. The purpose of empirical estimation models in software project 3 CO2 K2
management is to provide data-driven techniques for estimating
critical aspects of a project, such as effort, cost, and time. These
models rely on:

Historical Data: Using past project data to predict future project

outcomes.
Accuracy: Enhancing estimation precision by analyzing measurable
attributes like lines of code (LOC) or function points (FP).
Decision-Making: Supporting project managers in planning, resource
allocation, and risk management.
Standardization: Providing a consistent approach for estimating
across different projects.
Examples include models like COCOMO and Function Point
Analysis, which help in setting realistic expectations and ensuring
project success.
5. Risk Identification: Involves identifying potential risks that could 3 CO2 K2
affect the project, such as resource unavailability or technical issues.
Risk Projection: Evaluates the likelihood and impact of each risk,
quantifying their potential consequences.
6. Feasibility study-1, Requirement Engineering Process - 2 3 CO2 K2

7. Function Point. 3 CO2 K3

FP = UFP * CAF
FP = Count-total * [0.65 + 0.01 *∑(fi)]
= 378 * [0.65 + 0.01 * 43]
= 378 * [0.65 + 0.43]
= 378 * 1.08 = 408

7
8. 1.Planning is necessary 3 CO2 K2
Planning should be done before a project begins.
For effective planning, objectives and schedules should be clear and
understandable.
2.Risk analysis
Before starting the project, senior management and the project
management team should consider the risks that may affect the
project.
3.Tracking of project plan
Once the project plan is prepared, it should be tracked and modified
accordingly.
4.Meet quality standards and produce quality deliverables
The project plan should identify processes by which the project
management team can ensure quality in software. Based on the
process selected for ensuring quality, the time and cost for the project
is estimated.
5.Description of flexibility to accommodate changes
The result of project planning is recorded in the form of a project
plan, which should allow new changes to be accommodated when the
project is in progress.

9. Hence E=3.0(200)1.12=1133.12PM 3 CO2 K3

D=2.5(1133.12)0.35=29.3PM

Average staff size =38 67Persons

Productivity=176 LOC/ PM
10. Expert Judgment: Relying on the experience of professionals in the 3 CO2 K2
field.
Analogous Estimation: Using historical data from similar past
projects.
Parametric Estimation: Using mathematical models based on project
size and complexity.
Cocomo Model: A well-known model that uses size-related
parameters to estimate project effort and cost.

Five Marks Questions.

Course
*Q.Nos. 1- 5 first half Portion of unit syllabus and Q.No 6 - 10 Marks Level
Outcome
from the second half portion of syllabus
1. Instruction and purpose -1 mark, Functional requirements and non- 5 CO2 K3
functional requirements. 2 Mark
Risk management plan (including risk identification, projection, and
refinement). 1Mark
A brief project scheduling timeline 1 Mark
2. Risk types (3 mark), Examples (2 mark) 5 CO2 K2
3. SRS definition 1 mark, Explanation 2-marks, Table of contents 2 5 CO2 K3
mark

8
4. Empirical Estimation -Definition- 1 mark , steps-1 mark, Diagram- 5 CO2 K2
1mark , Explanation - 2 marks
5. discuss all seven different risk associated -5 5 CO2 K3
6. Diagram-2 Marks,Explanation-3 Marks 5 CO2 K2
7. definition-2 Marks, Types of Models Explanation with example-3 5 CO2 K2
Marks
8. Explanation- 3 marks; importance - 2 marks 5 CO2 K2
9. Explanation-3 Marks,Examples-2 Marks 5 CO2 K2
10. definition 2 marks, list and explanation of steps 3 marks 5 CO2 K2

Unit – III
Unit Contents: Analysis Using UML
Analysis Modeling - Data Modeling – Functional Modeling & Information Flow – Behavioral Modeling -
Structured Analysis - Object Oriented Analysis - Domain Analysis- Object Relationship Model - Object
Behavior Model, Design modeling with UML- Design modeling with UML. Case Study : UML diagrams
for Stock Trading Application using the online Creatly platform.

Two Marks Questions.

Course
*Q.Nos. 1- 5 first half Portion of unit syllabus and Q.No 6 - 10 Marks Level
Outcome
from the second half portion of syllabus
1. A use case diagram focuses on the functional requirements of a 2 CO3 K1
system, modeling the interactions between users (actors) and the
system. It shows the actions that a user can perform on the system
and the system's responses. A class diagram focuses on the static
structure of a system, modeling the classes, their attributes, and their
relationships. It shows the classes that make up the system and how
they are related to each other.
2. The collaborations are used when it is essential to depict the 2 CO3 K1
relationship between the object. Both the sequence and collaboration
diagrams represent the same information, but the way of portraying it
quite different. The collaboration diagrams are best suited for
analyzing use cases.
3. A use case diagram is a representation of a user's interaction with the 2 CO3 K1
system that shows the relationship between the user and the different
use cases in which the user is involved.
4. Visualizes complex data structures, providing a clear roadmap for 2 CO3 K1
understanding relationships.
Acts as a universal language, fostering effective communication
between business and technical stakeholders.
Creates organized databases by defining entities, properties, and

9
 relationships.
Enhances data quality and integrity by reducing anomalies and
redundancy through normalization.
Minimizes errors in database and application development.
5. Empirical Evaluation (testing with users): This involves usability 2 CO3 K1
testing with real users. Heuristic Evaluation: This method is based on
a set of rules or heuristics. Think Aloud Evaluation: Users verbalize
their thoughts while interacting with the interface. Pluralistic
Walkthrough Evaluation: A team of evaluators examines the
interface together.
6. The Entity-Relation model represents real-world entities and the 2 CO3 K1
relationship between them. Components of a ER Diagram
Entities
Attributes
Relationship
7. An Object Behavior Model represents dynamic behavior using state 2 CO3 K1
transition diagrams that depict the states of an object and the
transitions triggered by events, showing how the object responds to
inputs or changes over time.
8. UML(Unified Modeling Language).It is a graphical language for 2 CO3 K1
OOAD that gives a standard way to write a software system’s
blueprint.
Types: Use case diagram, Class diagram, Activity diagram, State
chart diagram, Interaction diagram, Component diagram, Package
diagram, Deployment diagram
9. These two terms relate to inheritance and polymorphism in UML. 2 CO3 K1
10. Data Flow Diagram (DFD) is a graphical representation of data flow 2 CO3 K1
in any system. It is capable of illustrating incoming data flow,
outgoing data flow and store data. Data flow diagram describes
anything about how data flows through the system.

Three Marks Questions.

Course
*Q.Nos. 1- 5 first half Portion of unit syllabus and Q.No 6 - 10 Marks Level
Outcome
from the second half portion of syllabus
1. Notations - 1 mark ; DIagram - 2 marks 3 CO3 K3

2. Identification of key actors and use cases (1 mark): 3 CO3 K3

Relationships between actors and use cases (1 mark):
Explanation of rationale (1 mark):
3. Definition-1 Mark;Explanation of Sequence Diagram-1 mark 3 CO3 K3
;Figure-1 Mark
4. - Class diagrams model the system's static structure, including 3 CO3 K2
classes, attributes, operations, and relationships.
- They provide a clear blueprint for the data architecture and
organization.

10
 - They depict interactions between data entities, aiding in system
design and understanding.
5. It visually representing functionality, behavior, and structure, 3 CO3 K2
clarifying requirements, and identifying key components. It ensures
clear communication among stakeholders, reduces ambiguity, and
supports traceability throughout development, providing a foundation
for design and testing.
6. Class diagram -3 marks 3 CO3 K3
7. Activity Diagram-3 marks 3 CO3 K3
8. Exaplanation 1 marks ,Notations-2 marks 3 CO3 K2
9. Entity relational (ER) model is a high-level conceptual data model 3 CO3 K2
diagram.
ER modeling helps you to analyze data requirements systematically
to produce a well-designed database.
The Entity-Relation model represents real-world entities and the
relationship between them.Components of a ER Diagram
Entities
Attributes
Relationship
10. Cardinality: 3 CO3 K2
Cardinality describes the maximum number of data objects that can
participate in a relationship. In databases, cardinality is defined as the
uniqueness of data values that are contained in a column.
High cardinality means the column contains a large percentage of
totally unique values. On the other hand, low cardinality means the
column has a lot of "repeats" in its data range. Cardinality between
the tables can be classified into different types such as one−to−one,
many−to−one or many−to−many.
Modality:
Modality is absolutely different from cardinality becausev
The value of modality is computed asv "0", if the relationship is
optional or if there is no need for the relationship to occur.
If there is a necessity of the occurrence of a relationship, then the
value of the modality is computed asv "1".
Therefore, modality describes whether a relationship between two or
more entities is needed or not. Thus, in the case of modality, the
modality can be classified into two types namely nullable modality
and non−nullable modality.

Five Marks Questions.

Course
*Q.Nos. 1- 5 first half Portion of unit syllabus and Q.No 6 - 10 Marks Level
Outcome
from the second half portion of syllabus
1. List the significance and explanation - 5 marks 5 CO3 K2

2. Behavioral Modeling- Definition-1 mark , types of diagrams -1 mark 5 CO3 K2

, Diagram- 1 mark Explanation- 2 marks

11
3. UML diagrams (3 marks), Details about railway reservation-3 Marks 5 CO3 K2
4. Interface List -2 Mark Design Prespective - 2 Mark Real time 5 CO3 K2
Exaample -1 mark
5. Structured Analysis-2.5 OOA-2.5 5 CO3 K2
6. Diagram -4 Marks,Explanation -1Mark 5 CO3 K2
7. Use Case - 3 marks .. ER - 2 marks 5 CO3 K3
8. Use case diagram- 2Marks, Sequence Diagram-2 Marks and activity 5 CO3 K3
diagram-1 Marks
9. UML diagrams (3 marks), Details about Stock Trading System (1 5 CO3 K3
mark), Tools (1 mark)
10. Use case diagram- 2Marks, Activity diagram-2 Marks, Class 5 CO3 K3
Diagram-1Marks

Unit – IV
Unit Contents: Design Principles and Heuristics
Design Principles – Design Process – Design Elements – Design Concepts – Modular Design – top – down and
bottom-up, Abstraction, step-wise refinement, coupling and cohesion, Refactoring, Architecture – Introduction to
Software Architecture – Data Design – Transform Mapping – Transaction Mapping – Design Patterns. Case
Study: Architecture diagram and design for the Safe Home security system.

Two Marks Questions.

Course
*Q.Nos. 1- 5 first half Portion of unit syllabus and Q.No 6 - 10 Marks Level
Outcome
from the second half portion of syllabus
1 Modularity is a design principle that involves breaking down a 2 CO4 K1
complex system into smaller, more manageable modules or
components. This promotes code reusability, maintainability, and
testability
2 Cohesion implies Relative functional strength of a module 2 CO4 K1
Coupling implies Relative interdependence among modules
3 1. Defining Data Structures and Storage 2 CO4 K1
Efficient data handling: Data design specifies how data will be
structured, stored, and organized in the system.
2. Ensuring Data Integrity and Security
Maintaining accuracy and consistency: Data design incorporates
rules, constraints, and validation mechanisms to ensure data integrity.
4 An abstraction is a tool that enables a designer to consider a 2 CO4 K1
component at an abstract level without bothering about the internal
details of the implementation.
5 Software Architecture defines fundamental organization of a 2 CO4 K2
system and more simply defines a structured solution.

12
6 2 CO4 K2
Aspect: Data Flow-Oriented Design focuses on the flow of data
through the system where as Data Structure-Oriented Design focuses
on organizing and representing the data structure

Approach: Flow-Oriented Design uses uses processes and

transformations as the primary design element where as Data
Structure-Oriented Design emphasizes data and its relationship to
operations
7 What is the need for refactoring? 2 CO4 K1
8 Transform flow - overall data flow is sequential and flows along a 2 CO4 K1
small number of straight line paths
Transaction flow - a single data item triggers information flow along
one of many paths
9 A design pattern in programming is a reusable solution to a common 2 CO4 K1
problem that occurs during software design and development. It
provides a structured approach to solving specific design or
implementation issues, allowing developers to create more
maintainable, flexible, and scalable code.
10 the software engineer designs the system or software. The work 2 CO4 K1
products for this task include a software design document or
specification.

Three Marks Questions.

Course
*Q.Nos. 1- 5 first half Portion of unit syllabus and Q.No 6 - 10 Marks Level
Outcome
from the second half portion of syllabus
1. Justification with reasons and examples - 3 marks 3 CO4 K3

2. Identification of modular design principles (1 Mark) 3 CO4 K3

Explanation of coupling and cohesion (1 Mark)
Application of principles to the Safe Home security system (1 Mark)
3. Defintion-1 Mark; Types -1 Mark; Explanation- 1Mark 1,Business 3 CO4 K2
architecture - Defines the strategy of business, governance,
organization, and key business processes within an enterprise and
focuses on the analysis and design of business processes
2,Application (software) architecture − Serves as the blueprint for
individual application systems, their interactions, and their
relationships to the business processes of the organization.
3,Information architecture − Defines the logical and physical data
assets and data management resources.
4,Information technology (IT) architecture − Defines the hardware
and software building blocks that make up the overall information
system of the organization.
4. - Cohesion refers to how closely related the functions within a 3 CO4 K2
module are; higher cohesion leads to better module focus and clarity.
- Coupling measures the degree of interdependence between
modules; lower coupling improves modularity and flexibility.

13
 - High cohesion and low coupling together result in a well-structured,
maintainable, and scalable software system.
5. Top Down starts with the overall system and breaks it into smaller 3 CO4 K2
components.
Bottom Up begins with designing components and integrating them
into the system.
6. Structural design patterns are essential for building scalable, 3 CO4 K2
maintainable, and flexible software systems. They help simplify
complex systems by organizing components effectively, promoting
reusability, and allowing easy modifications
7. Mapping Software Components, Dataflow And Processing Logic, 3 CO4 K2
Ensuring Accuracy and efficiency.
8. Step-wise refinement is a design strategy that breaks down a complex 3 CO4 K2
problem into simpler, smaller sub-problems. The design begins at a
high level of abstraction and then progressively refines the design by
adding more details. This approach helps manage complexity and
ensures that the system is designed incrementally and effectively.
9. Justification with reasons and examples - 3 marks 3 CO4 K2
10. Refactor (2 mark), Example (3 mark) 3 CO4 K2

Five Marks Questions

Course
*Q.Nos. 1- 5 first half Portion of unit syllabus and Q.No 6 - 10 Marks Level
Outcome
from the second half portion of syllabus
1. Coupling 3 marks cohesion 2 marks 5 CO4 K2

2. Transform mapping -Definition-1 mark, DFD diarams-2 marks, Steps 5 CO4 K3

Explanation- 2 marks
3. Definition-1 mark, Diagrams-2 marks, Explanation- 2 marks 5 CO4 K2
4. Definition-1 mark, Diagrams-2 marks, Explanation- 2 marks 5 CO4 K3
5. Boundary Values -2 Marks Application -2Marks, Example -1 Mark 5 CO4 K2
6. Definition-1 mark, Diagrams-1 mark, Explanation- 3 marks 5 CO4 K3
7. Level0-1 Marks 5 CO4 K3
Level1-2 Marks
Level2- 2 Marks
8. Definition and Steps-3 Marks, Example- 2marks 5 CO4
9. Facade Pattern details (3 marks), example (2 mark) 5 CO4 K3
10. Any 5 concepts - 5 marks 5 CO4 K2

Unit – V
Unit Contents: Testing, Maintenance and Reengineering

14
 Testing approaches - Top-Down, Bottom-Up, Big Bang and Sandwich, object oriented product Implementation
& Integration – Software Testing methods – White Box – Black Box – Unit Testing – Integration testing –
Validation & System testing – Software Maintenance & Reengineering. Case study: Login module of
Ecommerce application - Test cases and Best Practices.

Two Marks Questions

Course
*Q.Nos. 1- 5 first half Portion of unit syllabus and Q.No 6 - 10 Marks Level
Outcome
from the second half portion of syllabus
1. Advantages: 2 CO5 K1
Simulates real-world scenarios.
Can identify system-level defects early.
Disadvantages:
Difficult to isolate and debug defects.
Requires significant testing effort and resources

2. The attributes of software are (Reliability, Scalability, Portability, Re- 2 CO5 K1

usability, Usability)
3. White box Testing requires Knowledge of the internal program design and 2 CO5 K1
code required. Tests are based on coverage of code statements, branches,
paths, conditions
4. Black Box Testing is a type of software testing where the tester has no 2 CO5 K1
knowledge of the internal structure, code, or workings of the software. The
focus is entirely on testing the functionality of the software based on its
inputs and outputs. White Box Testing is a way of testing the software in
which the tester has knowledge about the internal structure or the code or
the program of the software.
5. Requirement Analysis Tool. Structure Analysis Tool. Software Design 2 CO5 K1
Tool.Code Generation Tool.
6. Software maintenance is the process of changing, modifying, and updating 2 CO5 K1
software to keep up with customer needs. Software maintenance is done
after the product has launched for several reasons including improving the
software overall, correcting issues or bugs, to boost performance, and more.
7. Integration testing is the process of testing the interactions between 2 CO5 K1
different modules or components of a system to ensure that they work
together as expected when integrated.
8. V(G) = P +1 V (G) = 2 + 1 = 3 Where P is predicate nodes 2 CO5 K1
9. Planning, Analysis, Design, Implementation, Testing and Deployment 2 CO5 K2
10. Verification: It involves static analysis technique (review) done without 2 CO5 K1
executing code. It is the process of evaluation of the product development
phase to find whether specified requirements meet.
Validation: It involves dynamic analysis technique (functional, non-
functional), testing done by executing code.

Three Marks Questions.

Course
*Q.Nos. 1- 5 first half Portion of unit syllabus and Q.No 6 - 10 Marks Level
Outcome
from the second half portion of syllabus

15
1. 1 mark for each test case 3 CO5 K3

2. Identification of Test Cases (2 Marks) 3 CO5 K3

Application of Black Box Testing (1 Mark)

3. Advantages :1,Test cases can be defined in terms of the functionality 3 CO5 K2
of the system (functional requirements) 2,No drivers needed
Disadvantages :1,Writing stubs is difficult: Stubs must allow all
possible conditions to be tested. 2,Large number of stubs may be
required, especially if the lowest level of the system contains many
methods.3,Some interfaces are not tested separately.
4. - Ensures system reliability and performance by fixing defects, 3 CO5 K2
improving existing features, and enhancing the software’s usability.
- Addresses evolving requirements by adapting to changing user
needs and technology advancements.
- Extends the software’s lifespan by maintaining its functionality and
preventing degradation over time.
5. Input valid credentials Expected Result: Login successful. 1 mark for 3 CO5 K3
each point
Input invalid credentials Expected Result: Error message.
Leave fields blank Expected Result: "Fields are required" message.
6. 1.Reverse Engineering 2. Restructuring 3. Forward Engineering 4. 3 CO5 K2
Re-documentation 5. Migration 6. Testing and Validation
7. Definition, Testing Objective, Testing Methods, Knowledge Level, 3 CO5 K2
Scope, Implementation
8. Software reengineering involves modifying and improving an 3 CO5 K2
existing software system’s structure or design without changing its
core functionality. It may involve tasks like code refactoring,
documentation updating, or migrating the system to newer
technologies.
9. BVA is used to check the behavior of application using test data that 3 CO5 K2
exist at boundary values or in more easy words, for a range of input
data values, boundary values (extreme end values) are used as input
for testing. It is mostly used design technique as it is believed that
software is most likely to fail at upper and lower limits of input data
values.
Example: A software allows people of age 20 to 50 years (both 20
and 50 are inclusive) to fill a form, for which the user has to enter his
age in the age field option of the software.
The boundary values are 20 (min value) and 50 (max value).
10. Pros and Cons (2 mark), concept (1 mark) 3 CO5 K2

Five Marks Questions,

Course
*Q.Nos. 1- 5 first half Portion of unit syllabus and Q.No 6 - 10 Marks Level
Outcome
from the second half portion of syllabus

16
1. Advantages - 2 marks Limitations 3 marks 5 CO5 K3

2. Software Testing -Definition -1 mark , Types -1 mark , Diagram - 1 5 CO5 K2

mark Explanation - 2 marks
3. Alpha testing-2 Marks, Beta testing-2 Marks, Advantages-1 5 CO5 K2
4. Definition and Explanation- 3 marks; example - 2 marks 5 CO5 K2
5. Definition and types-2 Marks, Explanation - 3marks 5 CO5 K2
6. Definition of cyclomatic complexity-1, Control flow Diagram-2 5 CO5 K3
Marks, Calculation - 2marks
7. Definition of cyclomatic complexity-1, Control flow Diagram-2 5 CO5 K3
Marks, Calculation - 2marks
8. Explanation- 3 marks; example - 2 marks 5 CO5 K2
9. Details of Software Reengineering ( 2 mark), Details of Maintenance 5 CO5 K2
(2 mark), examples (1 mark)
10. Definition and Explanation- 3 marks; example - 2 marks 5 CO5 K3

Course Coordinator Dean -SoC

[Name and Signature] [Dr,S,P,Chokkalingam]

17