Q.1) Attempt any FIVE of the following.

10Marks
Q1) Describe symbol used in DFD
=>

Symbol Component Function / Meaning Example

Name

○ Process Transforms data Calculate

Salary

→ Data Flow Shows data movement Input →

Process

Data Store Holds data Database

temporarily/permanently

□ External Entity Source or destination of data User

Q2) Define a Risk and List any two types of Risk

=> Risk is the possibility of an undesirable event or problem that may occur in a project and
can negatively affect its success, performance, cost, or schedule.
Types of Risk:
1. Technical Risk
2. Schedule Risk

Q3) Define the terms Verification and Validation

=> 1. Verification: Verification is the process of checking whether the software is being built
correctly according to the design and requirements.
2. Validation: Validation is the process of checking whether the final software product
meets the user’s needs and expectations.

Q4) Define Risk Identification

=> Risk identification is the first step in risk assessment, which identifies all the different risks
for a particular project is known as risk identification.

Q5) Draw Risk Management Process Diagram

Q6) Enlist Sub Model Used in COCOMOII
=> Sub-Models of COCOMO II:

• Application Composition Model

• Early Design Model
• Reuse Model
• Post-Architecture Model

Q7) List and draw symbols used in Use Case Diagram

=>

Symbol Name / Element

(Stick figure) Actor

⭘ (Oval shape) Use Case

(Rectangle / System Boundary Box)** System Boundary

─── (Line) Association

⟶ (Arrow with «include») Include Relationship

⟶ (Arrow with «extend») Extend Relationship

 ⟶ (Arrow between actors)** Generalization

Q8) What is a Software Modelling and Design

=> Software Modelling and Design is the process of representing, analyzing and planning a
software system before actual coding begins.

Q9) What is Data Modelling

=> Data Modelling is the process of organizing and representing data and their relationships
within a system in a structured way.

Q10) What is Information Hiding

=> Information Hiding means keeping the internal workings private and exposing only what
is necessary for other parts of the system to use safely.

Q11) Define Project Cost Estimation

=> Project Cost Estimation is the process of predicting the total cost required to complete a
software project, including resources, time, effort, and other expenses.

Q12) List the Step of Risk Monitoring

=> Steps of Risk Monitoring:
1. Identify Risks
2. Track Existing Risks
3. Assess Risk Impact
4. Implement Risk Responses
5. Update Risk Register
6. Communicate and Report
7. Review and Improve

Q13) Define Project Management

=> Project Management is the process of planning, organizing, executing, and controlling
resources to achieve specific goals within a defined scope, time, and budget.
Q14) Define Project Scheduling and list Scheduling Methods
=> Project Scheduling is the process of planning the sequence of project activities, allocating
resources, and setting timelines to ensure the project is completed on time.
Scheduling Methods:
1. Gantt Chart
2. Critical Path Method (CPM)
3. Program Evaluation and Review Technique (PERT)
4. Resource Scheduling
5. Milestone Scheduling

Q2) Attempt any FIVE of the following. 20 Marks

Q1) Explain Decision Table with example

• A decision table is a graphical method for explaining the logic of making decision in
tabular format.
• It is matrix representation of logic of decisions which specify the possible conditions
for decision and resulting actions.
• It is a table with various conditions and their corresponding actions.
• A typical decision table is divided into four parts:
1. Condition stub
2. Condition entries
3. Action stub
4. Action entries
Structure of a Decision Table:

Condition Rule 1 Rule 2 Rule 3

Condition 1 Y / N Y/N Y/N

Condition 2 Y / N Y/N Y/N

Action Action X Action Y Action Z

Q2) Differentiate between Black Box testing And White box Testing (any four points)
=>

Sr. No Black Box Testing White Box Testing

1 The internal working of an application Tester has full knowledge of internal
need not be known. workings of the application.

2 Focuses on what the system does. Focuses on how the system does it.

3 Test cases are based on requirements Test cases are based on code logic, paths,
and specifications. and conditions.

4 Also called Behavioural Testing. Also called Structural Testing.

5 Not suited for algorithm testing. Suited for algorithm testing.

Q3) Explain data flow diagram and draw data flow diagram Level 0 Level1 for A Book
Publishing House.

• A Data Flow Diagram (DFD) is a graphical representation of the flow of data in a

system.
• It shows how input data is transformed into output through processes, and how data
moves between processes, data stores, and external entities.
• A data flow diagram is also known as bubble chart or work flow diagram.
DFD Level 0:

Process Customer
Customer
order

DFD Level 1:

Q4) What is Structure flow chart and explain with example

 • A Structure Flow Chart (SFC) is a type of flowchart used in software engineering to show the
logical structure of a program or system in a hierarchical and organized way.
• It helps represent modules, functions, and their relationships clearly — showing how the
overall program is divided into smaller, manageable parts.
• It is mainly used in structured programming to make programs easy to understand, debug,
and maintain.

Example: Find the largest of the two numbers.

Steps:

1. Start
2. Input A, B
3. Decision is A>B?
• If yes -> Display A is largest
• If no -> Display B is largest
4. End

Q5) Explain 4P’S Management Spectrum

• The 4P’s Management Spectrum is a concept in Software Project Management that describes
the four key elements required for the successful management and completion of a software
project.
• These four P’s stand for:
People, Product, Process and Project.

1) People

• People are the most important part of any software project.

• The success of the project depends on the skills, motivation, and teamwork of the people
involved.

Includes:

• Project managers
• Software engineers
 • Testers
• Customers and end-users

2) Product

• This refers to the software or system being developed.

• Before development, the requirements and objectives of the product must be clearly
defined.

Includes:

• Problem definition

• Scope of the product

• Objectives and functions

3) Process

• The process defines the framework or model used to develop the software.

• It provides a structured way to plan, design, develop, test, and deliver the product.

Includes:

• Software Development Life Cycle (SDLC) models like:

o Waterfall Model

o Agile Model

o Spiral Model

4) Project

• The project combines all the above three elements (people, product, and process) to achieve
specific goals within time and budget limits.

• It focuses on planning, scheduling, risk management, and monitoring.

Includes:

• Time management

• Cost management

• Quality assurance

Q6) Describe Any two Cost Estimation techniques

=> Cost estimation techniques are used in software engineering to predict the effort, time, and cost
required to develop a software project.

1) Expert Judgment Technique

• In this technique, experienced managers or experts estimate the project cost based on their
past experience with similar projects.
 • It is simple and quick, but depends on the expert’s knowledge.

2) Delphi Technique

• A group of experts gives individual estimates.

• Their estimates are discussed anonymously and revised until a common agreement is
reached.

• It reduces personal bias and gives more accurate results.

8) Describe RMMM Strategy

• The RMMM Strategy is a structured plan prepared by the project manager to minimize the
impact of risks during the software development process.
• It helps in early detection, prevention, and control of project risks.
• The term RMMM stands for Risk Mitigation, Monitoring, and Management.

Benefits of RMMM Strategy:

• Reduces chances of project failure

• Ensures timely delivery

• Helps in better decision-making

• Builds confidence among the team and stakeholders

Q9) Describe Work Breakdown Structure with suitable diagram

• A Work Breakdown Structure is a hierarchical (tree-like) decomposition of a project

into smaller, manageable parts called tasks or work packages.
• It helps to organize and define the total work required to complete a project
successfully.
• To break complex projects into smaller, easier tasks.
• To assign responsibilities clearly.
• To estimate time and cost more accurately.
• To track project progress effectively.
Q10) Explain Four basic Principle of Project Scheduling

Principle #1: Compartmentalization

• The project must be divided into small, manageable tasks or activities.

• Each task should have clear objectives, start and end points.

• This makes planning and tracking easier.

Principle #2: Interdependency

• Tasks are often dependent on each other.

• The schedule must show the sequence in which tasks will be performed.

• Dependencies help identify which tasks must be completed before others can start.

Principle #3: Effort Validation

• The total effort (manpower, time, cost) assigned to all tasks must be validated.

• The schedule should ensure that available resources are enough to complete the project
within time limits.

Principle #4: Defined Responsibility

• Each and every task is scheduled should be assigned to a specific team member.

Q11) Describe COCOMO and COCOMOII model

=> 1. COCOMO Model (Constructive Cost Model)

• COCOMO (Constructive Cost Model) is a software cost estimation model developed by Barry
Boehm in 1981.
• It helps estimate the effort, cost, and development time required for a software project
based on the size of the project
• It provides the following three levels of models:
1. Basic COCOMO
2. Intermediate COCOMO
3. Complete COCOMO
• Formula:
Effort (Person-Months) = 𝑎 × (𝑆𝑖𝑧𝑒)𝑏
Development Time (Months) = 𝑐 × (𝐸𝑓𝑓𝑜𝑟𝑡)𝑑
2. COCOMO II Model
• COCOMO II is the updated version of COCOMO, developed in the 1990s to handle modern
software development practice like:

o Object-oriented design
o Reuse of code
o Rapid application development (RAD)
o Reengineering projects
 • It is an improved version that supports modern development methods and reuse.
• It has evolved into a more comprehensive estimation model, called COCOMO II.
• It has four sub-models:
1. Application Composition Model
2. Early Design Stage Model
3. Past-architecture Stage Model
4. A Reuse Model

Q12) Explain Line Of Code (LOC) based estimation

• Line of Code (LOC) based estimation is a software cost estimation technique that estimates
the effort, cost, and time required to develop a software project based on the number of
lines of source code to be written.
• It is one of the oldest and simplest methods used in software engineering.

Advantages:

• Simple and easy to use.

• Useful for small and traditional software projects.

• Helps in early project planning.

Disadvantages:

• Difficult to estimate LOC at the beginning of the project.

• Not suitable for object-oriented or component-based systems.

• Focuses on quantity, not quality of code.

• Ignores code reuse and productivity variations.

Q13) Explain Analytical Estimation Techniques

• Analytical Estimation Techniques are mathematical and formula-based methods used to

estimate the effort, cost, and schedule of a software project.
• These techniques use quantitative data (like size, productivity, and complexity) to give more
accurate and objective estimates.

Advantages:

• More accurate and objective.

• Based on historical data and mathematical models.

• Useful for large and complex projects.

Disadvantages:

• Requires accurate and detailed input data.

• Complex to apply manually.

 • Not suitable for very small projects.

Q14) Explain Function Point (FP) Metrics for Size Estimation with example

• Function Point (FP) Metrics is a software size estimation technique that measures the
functionality delivered to the user by a software system.
• It is independent of programming language and focuses on what the system does rather than
how it is implemented.
• Developed by Allan Albrecht at IBM in 1979.

Components of Function Point:

• External Inputs (EI)
• External Outputs (EO)
• External Inquiries (EQ)
• Internal Logical Files (ILF)
• External Interface Files (EIF)
Example: Library Management System

Component Count Complexity Weight Calculation

EI 10 Average 4 10×4=40

EO 5 High 7 5×7=35

EQ 4 Low 3 4×3=12

ILF 3 Average 10 3×10=30

EIF 2 Low 5 2×5=10

UFP = 40 + 35 + 12 + 30 + 10 = 127

Assume VAF = 1.1, then:

FP = 127 × 1.1 = 139.7 ≈ 140

Q7) Calculate Using a COCOMO Model 1) Efforts 2) Development time 3)Average Staff size4)
Productivity Estimated size of the project is 400 KLOC Using embedded mode
a=1.8,b=1.20,c=2.5,d=0.32

=> Given:

• Project Size (KLOC) = 400

• Mode = Embedded

• Constants: a = 1.8, b = 1.20, c = 2.5, d = 0.32

Step 1: Calculate Effort (Person-Months)

COCOMO formula:
 Effort (PM) = 𝑎 × (Size)𝑏

Substitute values:

Effort = 1.8 × (400)1.20

Step-by-step calculation:

1. Calculate 4001.20

log⁡10 400 = 2.60206

log⁡10 4001.2 = 2.60206 × 1.2 = 3.12247
103.12247 ≈ 1329.2
2. Multiply by a = 1.8

Effort = 1.8 × 1329.2 ≈ 2392.6 PM

Effort ≈ 2393 Person-Months

Step 2: Calculate Development Time (TDEV in Months)

COCOMO formula:

TDEV = 𝑐 × (Effort)𝑑

Substitute values:

TDEV = 2.5 × (2392.6)0.32

Step-by-step calculation:

1. Calculate 2392.60.32

log⁡10 2392.6 ≈ 3.378

3.378 × 0.32 = 1.081
101.081 ≈ 12.06
2. Multiply by c = 2.5

TDEV = 2.5 × 12.06 ≈ 30.15 months

Development Time ≈ 30.2 months

Step 3: Calculate Average Staff Size

Effort
Average Staff =
Development Time
2392.6
Average Staff = ≈ 79.4
30.15
 Average Staff ≈ 79 people

Step 4: Calculate Productivity

Size (KLOC)
Productivity =
Effort (PM)
400
Productivity = ≈ 0.167 KLOC/PM
2392.6

Productivity ≈ 0.167 KLOC per person-month