DI04000011-Software Engineering Question Bank

2 MARKS QUESTION

1.       Define Software Engineering

2.       What is Risk Identification?

3.       Explain cardinality and modality

4.       Discuss software characteristics in brief.

5.       Describe cohesion and coupling.

6.       List different software process framework activities.

7.       Explain data attributes

8.       What is unit testing?

9.       List out the project estimation techniques

10.    Explain data objects.

11.    Define Black Box Testing.

12.    Define Software.

13.    List any Two Tools used in Data Flow Diagram.

14.    List Umbrella activities.

15.    Define Functional Requirements.

16.    Define Risk.

17.    Give full form (1)COCOMO(2)FTR (3)PERT (4)WBS (5)UML (6)AOA (7)DFD (8)CASE(9)CPM (10)PMC (11)SDLC (12)SRS (13)FP (14)TCF (15)UFP(16)ERD (17)BVA(18)CFG (19) LOC

18.    Define (i) Cyclomatic complexity (ii) Linearly Independent Path.

19.    Define organic embedded system.

20.   Justify: Spiral model can be viewed as a meta model.

3 OR 4 MARKS QUESTION

1.     Explain Waterfall Model for Software Development with neat sketch.

2.     Describe Incremental Model for Software Development with diagram.

3.     Explain the need of Software Engineering.

4.     Explain Software Process Framework Activities.

5.     Describe Prototyping Model and list out its disadvantages.

6.     Explain Spiral Model and list out its advantages.

7.     Develop Data Flow Diagram for Institute Management System.

8.     Compare functional and non-functional requirement of software.

9.     Explain classification of design activities.

10.  Explain classification of design methodology.

11.  Describe Empirical Estimation Technique.

12.  Describe Heuristic Technique for Project Estimation.

13.  Explain software documentation.

14.  Explain test documentation.

15.  Describe code walkthrough.

16.  Describe code inspection.

17.  Discuss the responsibilities of software project manager.

18.  What do you mean by project monitoring and control?

19.  Define Software. Explain umbrella activities in brief.

20.  Discuss the Metrics for Size Estimation.

21.  Explain the work break down structure.

22.  Compare Black box and White box testing

23.  List advantages of object oriented design.

24.  Define Software. List qualities of good software.

25.  Explain Symbols used in data flow diagram.

26.  Explain Software Development Life Cycle.

27.  Explain Spiral Model with Diagram.

28.  Explain Client Server Architecture with Diagram.

29.  Explain Requirement gathering activities.

30.  Explain Object oriented Design

31.  List UML diagram. Explain Use Case Diagram.

32.  Explain Delphi Cost Estimation Technique.

33.  Explain E-R Diagram.

34.  Write a short note on white box testing methods.

35.  Explain: Software doesn’t wear out.

7 MARKS QUESTION

1.   List out the characteristics and explain the importance of SRS document.

2.   Define Risk.Explain Risk Management.

✅ 2 MARKS QUESTIONS – ANSWERS

1. Define Software Engineering

Software Engineering is the systematic, disciplined, and measurable approach used for development, operation, and maintenance of software.

---

2. What is Risk Identification?

Risk Identification is the process of finding and documenting possible risks that may affect software project success.

---

3. Explain Cardinality and Modality

• Cardinality: Number of entity instances participating in a relationship (1:1, 1:M, M:N).
• Modality: Minimum participation of entities (optional or mandatory).

---

4. Software Characteristics

• Developed, not manufactured
• Does not wear out
• Highly complex
• Easy to modify
• Invisible product

---

5. Cohesion and Coupling

• Cohesion: Degree of relationship within module (should be high).
• Coupling: Dependency between modules (should be low).

---

6. Software Process Framework Activities

1. Communication
2. Planning
3. Modeling
4. Construction
5. Deployment

---

7. Data Attributes

Properties describing data objects such as:

• Name
• Type
• Size
• Value
• Description

---

8. Unit Testing

Testing individual program modules independently to verify correctness.

---

9. Project Estimation Techniques

• Expert Judgment
• COCOMO
• Function Point
• Delphi Technique
• LOC estimation

---

10. Data Objects

Data objects represent entities containing related attributes used in a system.

---

11. Black Box Testing

Testing technique that checks software functionality without knowing internal code.

---

12. Define Software

Software is a collection of programs, procedures, and related documentation used to perform tasks.

---

13. Two Tools used in DFD

• Data Flow
• Process
  (Also: Data Store, External Entity)

---

14. Umbrella Activities

• Project tracking
• Risk management
• Quality assurance
• Documentation
• Configuration management

---

15. Functional Requirements

Requirements describing what system should do (functions/services).

---

16. Define Risk

Risk is an uncertain event that may negatively affect project cost, schedule, or quality.

---

17. Full Forms

Term	Full Form
COCOMO	Constructive Cost Model
FTR	Formal Technical Review
PERT	Program Evaluation Review Technique
WBS	Work Breakdown Structure
UML	Unified Modeling Language
AOA	Activity on Arrow
DFD	Data Flow Diagram
CASE	Computer Aided Software Engineering
CPM	Critical Path Method
PMC	Project Monitoring and Control
SDLC	Software Development Life Cycle
SRS	Software Requirement Specification
FP	Function Point
TCF	Technical Complexity Factor
UFP	Unadjusted Function Point
ERD	Entity Relationship Diagram
BVA	Boundary Value Analysis
CFG	Control Flow Graph
LOC	Lines Of Code

---

18. (i) Cyclomatic Complexity

Measure of number of independent paths in a program.

(ii) Linearly Independent Path
A unique execution path introducing at least one new edge.

---

19. Organic Embedded System

Small software system developed in a familiar environment with flexible requirements.

---

20. Spiral Model as Meta Model

Spiral model combines features of waterfall, prototyping, and iterative models; hence it acts as a meta model.

---

✅ 3–4 MARK QUESTIONS – ANSWERS

---

1. Waterfall Model

Sequential development model where each phase completes before next begins.

Phases:
Requirement → Design → Coding → Testing → Maintenance

Diagram (write in exam):

Requirements
     ↓
Design
     ↓
Implementation
     ↓
Testing
     ↓
Maintenance

---

2. Incremental Model

Software developed in small functional increments.

Advantages

• Early delivery
• Easy testing
• Flexible changes

---

3. Need of Software Engineering

• Manage complexity
• Improve quality
• Reduce cost
• Meet deadlines
• Maintain software easily

---

4. Software Process Framework Activities

1. Communication – Requirement gathering
2. Planning – Scheduling & estimation
3. Modeling – Design
4. Construction – Coding & testing
5. Deployment – Delivery & feedback

---

5. Prototyping Model

Prototype is developed to understand requirements.

Disadvantages

• Poor documentation
• User confusion
• Extra cost

---

6. Spiral Model Advantages

• Risk handling
• Early error detection
• Flexible changes
• Suitable for large projects

---

7. DFD for Institute Management System

(Write levels)

Entities: Student, Faculty
Processes: Admission, Fees, Result
Data Stores: Student DB

---

8. Functional vs Non-Functional Requirements

Functional	Non-Functional
What system does	How system performs
Features	Performance, security

---

9. Classification of Design Activities

• Data Design
• Architectural Design
• Interface Design
• Component Design

---

10. Design Methodology

• Structured Design
• Object-Oriented Design

---

11. Empirical Estimation Technique

Uses past project data for estimation (e.g., COCOMO).

---

12. Heuristic Technique

Experience-based estimation using rules and expert judgment.

---

13. Software Documentation

Written information describing software development and usage.

Types:

• User manual
• Technical document

---

14. Test Documentation

Documents describing testing activities:

• Test plan
• Test cases
• Test reports

---

15. Code Walkthrough

Informal review where developers explain code step-by-step.

---

16. Code Inspection

Formal review process to detect defects systematically.

---

17. Responsibilities of Project Manager

• Planning
• Scheduling
• Risk management
• Team coordination
• Quality control

---

18. Project Monitoring and Control

Tracking project progress and taking corrective actions.

---

19. Define Software & Umbrella Activities

Software = Programs + documentation.
Umbrella activities support all phases (QA, risk, review).

---

20. Metrics for Size Estimation

• LOC
• Function Points
• Object Points

---

21. Work Breakdown Structure (WBS)

Divides project into smaller manageable tasks.

---

22. Black Box vs White Box Testing

Black Box	White Box
Tests function	Tests code
No code knowledge	Code knowledge required

---

23. Advantages of Object-Oriented Design

• Reusability
• Modularity
• Easy maintenance
• Scalability

---

24. Qualities of Good Software

• Reliability
• Efficiency
• Maintainability
• Usability
• Portability

---

25. DFD Symbols

• Circle → Process
• Arrow → Data Flow
• Rectangle → External Entity
• Parallel lines → Data Store

---

26. SDLC

Structured process for software development phases.

---

27. Spiral Model

Iterative model focusing on risk analysis each cycle.

---

28. Client Server Architecture

Client requests service; server processes request.

---

29. Requirement Gathering Activities

• Interviews
• Questionnaires
• Observation
• Analysis

---

30. Object Oriented Design

Design based on objects containing data and methods.

---

31. UML Diagrams

Use Case, Class, Sequence, Activity, State, etc.

Use Case Diagram: Shows interaction between users and system.

---

32. Delphi Cost Estimation

Experts give estimates anonymously; results averaged.

---

33. ER Diagram

Represents entities, attributes, and relationships graphically.

---

34. White Box Testing Methods

• Path testing
• Loop testing
• Condition testing

---

35. Software Doesn’t Wear Out

Software failures occur due to changes/errors, not physical aging.

---

✅ 7 MARK QUESTIONS

---

1. Characteristics & Importance of SRS

Characteristics

• Correct
• Complete
• Consistent
• Verifiable
• Modifiable
• Traceable

Importance

• Acts as agreement between client & developer
• Reduces development cost
• Helps testing
• Improves project planning
• Avoids misunderstanding

---

2. Risk and Risk Management

Definition of Risk

Risk is a potential problem that may cause loss or delay in a project.

---

Risk Management

Process of identifying, analyzing, and controlling risks.

Steps:

1. Risk Identification
2. Risk Analysis
3. Risk Planning
4. Risk Monitoring
5. Risk Control

Types of Risks

• Project Risk
• Technical Risk
• Business Risk

Importance

• Reduces failure chances
• Improves planning
• Ensures project success