Fundamentals of Software Development (4331604) - Winter 2023 Solution

Question 1(a) [3 marks]

#

Define Software and explain its characteristics.

Answer:

Software is a collection of programs, instructions, and documentation that performs tasks on a computer system.

Key Characteristics:

Mnemonic: “In Logic, Manufacturing Creates” (Intangible, Logical, Manufactured, Complex)

Question 1(b) [4 marks]

#

Write a note on Software engineering – A layered technology.

Answer:

Software engineering is structured as a layered technology with each layer supporting the next.

Layered Structure:

graph TD
    A[Tools] --> B[Methods]
    B --> C[Process]
    C --> D[Quality Focus - Foundation]

Mnemonic: “Tools Make Process Quality” (Tools, Methods, Process, Quality)

Question 1(c) [7 marks]

#

Explain Software Process framework and umbrella activities.

Answer:

Software Process Framework provides structure for software development with core activities and umbrella activities.

Framework Activities:

Umbrella Activities:

• Software project tracking: Monitor progress and control quality
• Risk management: Identify and mitigate potential problems
• Quality assurance: Ensure standards are met
• Configuration management: Control changes systematically
• Work product preparation: Create deliverable documents

graph LR
    A[Communication] --> B[Planning]
    B --> C[Modeling]
    C --> D[Construction]
    D --> E[Deployment]
    F[Umbrella Activities] -.-> A
    F -.-> B
    F -.-> C
    F -.-> D
    F -.-> E

Mnemonic: “Can People Model Construction Daily” + “Track Risk Quality Configuration Work”

Question 1(c OR) [7 marks]

#

Define SDLC and explain each phase.

Answer:

SDLC (Software Development Life Cycle) is a systematic process for developing software applications.

SDLC Phases:

graph TD
    A[Planning] --> B[Analysis]
    B --> C[Design]
    C --> D[Implementation]
    D --> E[Testing]
    E --> F[Deployment]
    F --> G[Maintenance]

Mnemonic: “Please Analyze Design Implementation Testing Deployment Maintenance”

Question 2(a) [3 marks]

#

Describe advantage disadvantage of prototype model.

Answer:

Prototype Model Analysis:

Mnemonic: “Early Reduced Better” vs “Time Cost Scope”

Question 2(b) [4 marks]

#

Explain Prototyping Model and justify when to use with example.

Answer:

Prototyping Model creates working model of software early in development process.

When to Use:

graph LR
    A[Requirements] --> B[Quick Design]
    B --> C[Build Prototype]
    C --> D[User Evaluation]
    D --> E{Satisfied?}
    E -->|No| B
    E -->|Yes| F[Final System]

Mnemonic: “Requirements Quick Build User Satisfied Final”

Question 2(c) [7 marks]

#

Sketch and discuss (I) Waterfall model & (II) Incremental Model.

Answer:

(I) Waterfall Model:

Linear sequential approach where each phase must complete before next begins.

graph TD
    A[Requirements Analysis] --> B[System Design]
    B --> C[Implementation]
    C --> D[Testing]
    D --> E[Deployment]
    E --> F[Maintenance]

(II) Incremental Model:

Development in small increments with each increment adding functionality.

graph TD
    A[Analysis] --> B[Design]
    B --> C[Code]
    C --> D[Test]
    D --> E[Increment 1]
    
    F[Analysis] --> G[Design]
    G --> H[Code]
    H --> I[Test]
    I --> J[Increment 2]
    
    E --> K[Final Product]
    J --> K

Mnemonic: “Water Falls Once, Increments Build Multiple”

Question 2(a OR) [3 marks]

#

Describe advantage and disadvantage of Incremental Model.

Answer:

Incremental Model Analysis:

Mnemonic: “Early Easier Reduced” vs “Total System Management”

Question 2(b OR) [4 marks]

#

Write concept of Rapid Application Development (RAD) and explain it.

Answer:

RAD emphasizes rapid prototyping and quick feedback over planning and testing.

RAD Components:

graph LR
    A[Business Modeling] --> B[Data Modeling]
    B --> C[Process Modeling]
    C --> D[Application Generation]
    D --> E[Testing & Turnover]

Mnemonic: “Business Data Process Application Testing”

Question 2(c OR) [7 marks]

#

Design and describe Spiral Model and give advantage and disadvantage.

Answer:

Spiral Model combines iterative development with systematic risk analysis.

graph TD
    A[Planning] --> B[Risk Analysis]
    B --> C[Engineering]
    C --> D[Evaluation]
    D --> A
    
    E[Determine Objectives] --> F[Identify Risks]
    F --> G[Develop & Test]
    G --> H[Plan Next Iteration]
    H --> E

Spiral Quadrants:

Advantages vs Disadvantages:

Mnemonic: “Plan Risk Engineer Evaluate” + “High Good Customer” vs “Complex Expensive Risk”

Question 3(a) [3 marks]

#

Illustrate importance of SRS

Answer:

SRS (Software Requirements Specification) is crucial foundation document for software development.

Importance Table:

Mnemonic: “Communication Contract Testing”

Question 3(b) [4 marks]

#

Specify characteristics of good & bad SRS

Answer:

SRS Quality Characteristics:

Additional Good Characteristics:

• Modifiable: Easy to change and maintain
• Traceable: Links to source and design

graph LR
    A[Good SRS] --> B[Complete]
    A --> C[Consistent]
    A --> D[Unambiguous]
    A --> E[Verifiable]
    
    F[Bad SRS] --> G[Incomplete]
    F --> H[Inconsistent]
    F --> I[Ambiguous]
    F --> J[Unverifiable]

Mnemonic: “Complete Consistent Unambiguous Verifiable” vs “Incomplete Inconsistent Ambiguous Unverifiable”

Question 3(c) [7 marks]

#

Classify Types of Requirements in SRS

Answer:

Software requirements are classified into two main categories.

(i) Functional Requirements:

Define what the system should do - specific behaviors and functions.

(ii) Non-functional Requirements:

Define how the system should perform - quality attributes and constraints.

graph TD
    A[Requirements] --> B[Functional]
    A --> C[Non-Functional]
    
    B --> D[Business Rules]
    B --> E[User Actions]
    B --> F[Data Processing]
    B --> G[External Interfaces]
    
    C --> H[Performance]
    C --> I[Security]
    C --> J[Reliability]
    C --> K[Usability]
    C --> L[Scalability]

Comparison Table:

Mnemonic: “Functional = What, Non-Functional = How”

Question 3(a OR) [3 marks]

#

Describe skill to manage software projects

Answer:

Project management requires diverse skill set for successful software delivery.

Essential Skills:

Mnemonic: “Technical Leadership Communication”

Question 3(b OR) [4 marks]

#

Briefly give the Responsibility of software project Manager.

Answer:

Software Project Manager oversees entire project lifecycle and ensures successful delivery.

Key Responsibilities:

Additional Duties:

• Risk Management: Identify and mitigate project risks
• Team Development: Mentor team members and resolve conflicts

graph LR
    A[Project Manager] --> B[Planning]
    A --> C[Execution]
    A --> D[Quality]
    A --> E[Communication]
    A --> F[Risk Management]
    A --> G[Team Development]

Mnemonic: “Plan Execute Quality Communicate Risk Team”

Question 3(c OR) [7 marks]

#

Compare PERT chart – Gantt chart side by side.

Answer:

Both charts are project management tools but serve different purposes and have distinct characteristics.

Detailed Comparison:

Visual Representation:

graph LR
    subgraph "PERT Chart"
        A[Task A] --> C[Task C]
        B[Task B] --> C
        C --> D[Task D]
    end

gantt
    title Gantt Chart
    dateFormat  YYYY-MM-DD
    section Development
    Task A     :a1, 2024-01-01, 3d
    Task B     :a2, 2024-01-01, 2d
    Task C     :a3, after a1 a2, 4d
    Task D     :a4, after a3, 2d

When to Use:

Advantages Comparison:

Mnemonic: “PERT = Path, Gantt = Bars”

Question 4(a) [3 marks]

#

Give steps of Project Monitoring and control process

Answer:

Project monitoring ensures project stays on track through systematic observation and corrective actions.

Monitoring Steps:

Mnemonic: “Track Assess Take”

Question 4(b) [4 marks]

#

Discuss i)Risk Assessment ii)Risk Mitigation

Answer:

(i) Risk Assessment:

Process of identifying and evaluating potential project risks.

(ii) Risk Mitigation:

Strategies to reduce risk impact and probability.

Mnemonic: “Avoid Reduce Transfer Accept”

Question 4(c) [7 marks]

#

Define project risk and how Manage Risk Management it.

Answer:

Project Risk is an uncertain event that, if occurs, has positive or negative effect on project objectives.

Risk Characteristics:

Risk Management Process:

graph TD
    A[Risk Identification] --> B[Risk Assessment]
    B --> C[Risk Prioritization]
    C --> D[Risk Response Planning]
    D --> E[Risk Monitoring]
    E --> F[Risk Control]
    F --> A

Risk Management Steps:

Risk Categories:

Risk Response Strategies:

• Negative Risks (Threats): Avoid, Transfer, Mitigate, Accept
• Positive Risks (Opportunities): Exploit, Share, Enhance, Accept

Mnemonic: “Identify Assess Respond Monitor” + “Avoid Transfer Mitigate Accept”

Question 4(a OR) [3 marks]

#

Describe Software design process and explain Design methodologies.

Answer:

Software design transforms requirements into blueprint for implementation through systematic approach.

Design Process:

Mnemonic: “Analysis Architecture Detail”

Question 4(b OR) [4 marks]

#

Compare Cohesion and Coupling side by side.

Answer:

Both concepts measure module design quality but focus on different aspects.

Comprehensive Comparison:

Types Comparison:

Impact on Design:

Mnemonic: “Cohesion = Inside Strong, Coupling = Between Weak”

Question 4(c OR) [7 marks]

#

Sketch Data Flow Diagram with levels and explain.

Answer:

Data Flow Diagram (DFD) shows how data moves through system using graphical notation with multiple levels of detail.

DFD Symbols:

DFD Levels:

graph TD
    A[Context Diagram Level 0] --> B[Level 1 DFD]
    B --> C[Level 2 DFD]
    C --> D[Level 3 DFD]
    
    E[Single Process] --> F[Major Processes]
    F --> G[Sub-processes]
    G --> H[Detailed Processes]

Level Descriptions:

Example - Student Information System:

Level 0 (Context Diagram):

[Student] → Student Info → [Student System] → Reports → [Admin]

Level 1 DFD:

graph LR
    A[Student] --> B[1.0 Register Student]
    B --> C[Student Database]
    C --> D[2.0 Generate Reports]
    D --> E[Admin]
    F[Teacher] --> G[3.0 Update Grades]
    G --> C

Balancing Rules:

• Data Conservation: Input = Output at each level
• Process Numbering: Hierarchical numbering system
• External Entities: Same at all levels

Benefits of Leveled DFDs:

Mnemonic: “Context Major Sub Fine” + “Process Entity Store Flow”

Question 5(a) [3 marks]

#

Give Characteristics of good UI.

Answer:

Good User Interface design ensures effective user interaction with software system.

UI Characteristics:

Mnemonic: “Simple Consistent Responsive”

Question 5(b) [4 marks]

#

Briefly explain Unit testing

Answer:

Unit Testing verifies individual software components in isolation to ensure correct functionality.

Unit Testing Overview:

Testing Process:

graph LR
    A[Write Test Cases] --> B[Execute Tests]
    B --> C[Analyze Results]
    C --> D[Fix Defects]
    D --> B

Benefits:

• Early bug detection reduces fixing costs
• Code quality improvement through testing discipline
• Regression testing prevents future breaks

Mnemonic: “Scope Isolation Automation Early”

Question 5(c) [7 marks]

#

Draw activity diagrams of the train reservation system, explain each step.

Answer:

Activity Diagram shows workflow of train reservation system from user request to ticket confirmation.

graph TD
    A[Start] --> B[User Login]
    B --> C{Valid Credentials?}
    C -->|No| B
    C -->|Yes| D[Search Trains]
    D --> E[Select Train]
    E --> F[Choose Seats]
    F --> G{Seats Available?}
    G -->|No| F
    G -->|Yes| H[Enter Passenger Details]
    H --> I[Review Booking]
    I --> J{Confirm Booking?}
    J -->|No| D
    J -->|Yes| K[Process Payment]
    K --> L{Payment Success?}
    L -->|No| K
    L -->|Yes| M[Generate Ticket]
    M --> N[Send Confirmation]
    N --> O[End]

Step-by-Step Explanation:

Activity Types:

Parallel Activities:

• Payment processing and seat reservation can occur simultaneously
• Confirmation email and SMS can be sent in parallel

Exception Handling:

• Login Failure: Return to login screen
• No Seats: Allow different seat selection
• Payment Failure: Retry payment options
• System Error: Show error message and restart

Mnemonic: “Login Search Select Choose Enter Review Pay Generate Send”

Question 5(a OR) [3 marks]

#

Compare Verification, Validation side by side.

Answer:

Both are quality assurance activities but focus on different aspects of correctness.

Verification vs Validation:

Mnemonic: “Verification = Right Process, Validation = Right Product”

Question 5(b OR) [4 marks]

#

Define Testing describe any two testing type.

Answer:

Testing is process of evaluating software to detect errors and ensure it meets requirements.

Testing Definition: Systematic examination of software to find defects and verify functionality.

Two Testing Types:

(1) Black Box Testing:

(2) White Box Testing:

Comparison:

Mnemonic: “Black = External, White = Internal”

Question 5(c OR) [7 marks]

#

Describe each Coding standards and guidelines.

Answer:

Coding Standards are set of rules and conventions for writing consistent, maintainable, and readable code.

Purpose of Coding Standards:

Major Coding Standards Categories:

(1) Naming Conventions:

(2) Code Structure:

(3) Code Organization:

graph TD
    A[Code Organization] --> B[File Structure]
    A --> C[Function Size]
    A --> D[Class Design]
    
    B --> E[Single Responsibility]
    C --> F[Small Functions]
    D --> G[Clear Interfaces]

(4) Documentation Standards:

(5) Error Handling:

(6) Performance Guidelines:

Code Review Standards:

graph LR
    A[Code Written] --> B[Self Review]
    B --> C[Peer Review]
    C --> D[Team Lead Review]
    D --> E[Code Approved]
    E --> F[Merge to Main]

Review Checklist:

Benefits of Following Standards:

Implementation Strategy:

1. Establish Guidelines: Create team-specific coding standards document
2. Tool Integration: Use automated formatting and linting tools
3. Training: Conduct workshops on coding best practices
4. Enforcement: Include standards in code review process
5. Continuous Improvement: Regular updates based on team feedback

Popular Coding Standards:

Mnemonic: “Name Structure Organize Document Handle Perform Review”