Unit 6: Software Process Model (10 Hours)

Unit 6: Software Process Model (10 Hours)

6.1 Software Project Concept

A software project involves planning, designing, developing, testing, and maintaining software applications. It requires systematic management to ensure that the final product meets the desired requirements and is delivered on time and within budget. Key aspects of a software project include:

• Project Scope: Defining what the project will deliver.
• Project Plan: Outlining the tasks, timelines, resources, and milestones.
• Team Collaboration: Ensuring effective communication and collaboration among team members.

6.2 Concept of Software Development Process

The software development process is a structured approach to developing software that ensures quality and efficiency. It involves several phases, each with specific tasks and deliverables. Common models include:

• Waterfall Model: A linear sequential model where each phase must be completed before the next begins.
• Iterative Model: Repeats phases as needed based on feedback and improvements.
• Agile Model: Focuses on iterative development with continuous feedback, allowing for quick adaptations.

6.3 Concept of SDLC Life Cycle

The Software Development Life Cycle (SDLC) is a framework that describes the stages of software development from inception to retirement. Key phases include:

1. Requirement Gathering and Analysis: Identifying and documenting the needs of the users.
2. Design: Creating architecture and design specifications for the software.
3. Implementation: Writing the code based on the design.
4. Testing: Verifying that the software functions correctly and meets requirements.
5. Deployment: Releasing the software to users.
6. Maintenance: Ongoing support and updates to the software.

6.4 System Analyst vs. Software Engineer

• System Analyst:
  • Focuses on analyzing and designing information systems.
  • Works closely with stakeholders to understand their needs.
  • Responsible for requirement gathering and system design.
• Software Engineer:
  • Focuses on applying engineering principles to software development.
  • Involved in the actual coding, testing, and maintenance of software.
  • Works on implementation details and technical specifications.

6.5 Requirement Collection Methods

Effective requirement collection is crucial for project success. Common methods include:

• Interviews: Direct conversations with stakeholders to gather requirements.
• Surveys and Questionnaires: Collecting information from a larger audience.
• Workshops: Group discussions to explore requirements collaboratively.
• Observation: Analyzing users in their natural environment to understand needs.

6.6 Concept of System Design

System design translates requirements into a blueprint for building the system. It involves:

• High-Level Design (HLD): Outlining the system architecture, modules, and data flow.
• Low-Level Design (LLD): Detailing the implementation of each module, including algorithms and data structures.

6.7 Software Quality

Software quality refers to the degree to which a software product meets the specified requirements and customer expectations. Key factors influencing software quality include:

• Functionality: The software's ability to perform its intended functions.
• Usability: How easy and intuitive the software is for users.
• Reliability: The software's ability to operate under specified conditions without failure.
• Performance: How well the software performs in terms of speed and resource usage.

6.8 Software Development Models: Waterfall, Prototype, Agile

Different software development models cater to varying project needs:

• Waterfall Model:

  • Characteristics: Linear, sequential phases.
  • Advantages: Easy to understand and manage; well-defined stages.
  • Disadvantages: Inflexible to changes; not ideal for complex projects.

• Prototype Model:

  • Characteristics: Building a prototype before final development.
  • Advantages: Allows for user feedback early in the process; reduces misunderstandings.
  • Disadvantages: Can lead to scope creep; potential for incomplete documentation.

• Agile Model:

  • Characteristics: Iterative and incremental development.
  • Advantages: Flexibility to changes; continuous user involvement.
  • Disadvantages: Requires constant communication; can be challenging to scale for larger projects.