Find papers

ITM 352

Software Engineering and System Analysis

TU BITM · Semester 6 · BITM curriculum and programme regulation

Requirement
required
Credits
3
Study Guide
7 units available

Chapter notes

Authoritative study guide across 7 syllabus units

Open a unit to read its study notes.

Unit 1: Systems Development Environment· 6 LHs· ~8 marks

Suggest correction

Part 1: Core Concepts (2 Marks)

  • Software Engineering: The systematic, disciplined, quantifiable approach to the development, operation, and maintenance of software systems.
  • Waterfall Model: Classical sequential linear lifecycle model where each phase (Requirements →\to Design →\to Implementation →\to Verification →\to Maintenance) must complete before the next commences.
  • Agile Methodology & Scrum: Iterative, incremental development philosophy emphasizing working software, customer collaboration, and rapid response to change over rigid documentation. Sprints last 2-4 weeks.

Part 2: Structural Frameworks (10 Marks)

Comparison of SDLC Process Models

Model Strengths Weaknesses Best Suited For
Waterfall Simple, structured, clear milestones Inflexible; late working software Stable requirements, mission-critical
Spiral Excellent risk analysis loops Expensive; complex management overhead High-risk, large- scale enterprise
Agile (Scrum) Rapid delivery, highly adaptable Scope creep; harder cost estimation Fast-moving market web/mobile apps

Part 3: Distinction Tables

Basis of Comparison Verification Validation
Core Question “Are we building the product right?” “Are we building the right product?”
Focus Evaluates adherence to specifications and design standards. Evaluates whether product fulfills actual customer needs.
Activities Reviews, walkthroughs, inspections, static analysis. Black-box testing, user acceptance testing (UAT).

Part 4: Worked Problems & Exam Traps

Scrum Ceremony Framework

  1. Sprint Planning: Team selects items from Product Backlog into Sprint Backlog.
  2. Daily Scrum: 15-minute standup answering 3 questions: What did I do yesterday? What will I do today? What blockers exist?
  3. Sprint Review: Live demonstration of completed increment to stakeholders.
  4. Sprint Retrospective: Internal team reflection on process improvements.

Agile does NOT mean “no documentation”. Agile prioritizes working software over comprehensive documentation, but essential architectural schemas remain mandatory.