Scribd
Upload
44 views2 pages

Answer Key Introduction To Software

The document contains an answer key for a mid-semester examination in Software Engineering, covering various topics such as software processes, requirement engineering, testing types, and software attributes. It also discusses different software development models suitable for specific projects, including Waterfall, Prototype, Incremental Development, Integration & Configuration, and Spiral Model. Additionally, it outlines the major components of the Scrum process and compares two teams' adherence to Scrum principles.

Uploaded by

huzaifaltaf605
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
44 views2 pages

Answer Key Introduction To Software

The document contains an answer key for a mid-semester examination in Software Engineering, covering various topics such as software processes, requirement engineering, testing types, and software attributes. It also discusses different software development models suitable for specific projects, including Waterfall, Prototype, Incremental Development, Integration & Configuration, and Spiral Model. Additionally, it outlines the major components of the Scrum process and compares two teams' adherence to Scrum principles.

Uploaded by

huzaifaltaf605
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd

Answer Key - Mid Semester

Examinations: Spring 2025


Introduction to Software Engineering
Question 2 - CLO 1, PLO 2 (Marks: 12)

a. Software process as “black box” vs “white box”:


- Black box: Focuses on inputs and outputs without considering the internal workings.
- White box: Examines the internal processes and logic used to produce the output.

b. Requirement engineering in “Agile” vs “Plan-driven” process:


- Agile: Requirements evolve through collaboration, are often captured in user stories.
- Plan-driven: Requirements are defined early in the project and remain fixed throughout.

c. “Unit testing” vs “system testing” in Waterfall Model:


- Unit testing: Verifies individual components or functions of the software.
- System testing: Validates the entire system’s functionality against requirements.

d. “Concept reuse” vs “component reuse”:


- Concept reuse: Reusing design ideas or patterns.
- Component reuse: Reusing actual software components or code modules.

e. Maintainability and Acceptability attributes of good software:


- Maintainability: Ease with which software can be updated or modified.
- Acceptability: Degree to which the software meets user expectations and standards.

f. “Functional” vs “non-functional” requirements:


- Functional: Define specific behaviors or functions (e.g., login, data entry).
- Non-functional: Define system qualities (e.g., performance, security, usability).

Question 3 - CLO 2, PLO 2 (Marks: 15)

a. NASA Space Shuttle Control System – Waterfall Model:


- Reasons: Requires detailed documentation and thorough verification for safety-critical
systems.
- Highly structured, suitable for non-iterative, life-critical projects.
b. Voice-Activated Smart Assistant – Prototype Model:
- Reasons: Need for frequent user feedback to refine voice interaction.
- High uncertainty in user requirements; iterative prototyping helps improve user
experience.

c. Web-based Hospital Software – Incremental Development:


- Reasons: Modules like registration, health records can be built and delivered
incrementally.
- Allows user feedback and progressive integration of features.

d. Payroll Processing System – Integration & Configuration:


- Reasons: Often integrates with existing ERP/HR systems.
- Emphasis on accuracy and compliance, best achieved with pre-validated components.

e. Digital Learning System – Spiral Model:


- Reasons: Evolving system, high risk due to continuous feature updates.
- Emphasizes risk analysis and user evaluation at each iteration.

Question 4 - CLO 2, PLO 2 (Marks: 10)

a. Major Components of Scrum Process (from passage):


- Product Backlog: List of tasks and features.
- Sprint Backlog: Tasks committed for a sprint.
- Sprint: Time-boxed development cycle.
- Scrum Master and Product Owner: Key roles.
- Daily Scrum: Regular team meetings.
- Definition of Done, Acceptance Criteria, and Incremental Delivery.

b. Comparison:
- Team A had on-site collaboration, which helped in faster development.
- Team B, though virtual, practiced all core Scrum elements like sprint planning, daily
updates (asynchronously), and proper sprint review.
- Conclusion: Team B adhered more strictly to Scrum principles and was more disciplined,
making them better at delivering most valued features.

You might also like