Higher Revision

Higher Computing
Revision

By Andrew Webster

Dev Methodologies

Introduction

• Software development involves structured approaches to create, test, and maintain applications.

• Different methodologies exist to suit different project needs.

• We will explore key methodologies used in computing.

Waterfall Model

• A linear, sequential approach.

• Phases: Analysis > Design > Implementation > Testing > Evaluation

• Suitable for well-defined projects with clear requirements.

• Pros: Simple, easy to manage, clear structure.

• Cons: Inflexible, late testing stage, difficult to accommodate changes, little client interaction after initial requirements gathering.

Uses top-down design methodology. It is based on the principle of design and then build.
There are seven stages in the process.
Each stage is treated as an individual project. Only when a step is completed does the development move onto the next stage.

No stage is ever truly completed at the first attempt. As the development process goes on, it may be necessary to revisit earlier phases. This is known as iteration.

Waterfall Model

Disadvantages

Stages of development happen in order, so when errors occur and previous stages have to be revisited this wastes valuable time as the project doesn’t continue until these are sorted out. Furthermore, deadlines and budget boundaries may not be met.

Waterfall Model

AGILE Development

• Iterative and incremental development.

• Emphasizes collaboration, flexibility, and customer feedback.

• Popular frameworks: Scrum, Kanban.

• Pros: Adaptable, continuous feedback, customer involvement, quick release schedule, get product out quickly (POC), consistent release cycles

• Cons: Requires strong teamwork, less predictable timeline.

​Replace this with your body text.

​Duplicate this text as many times as you would like.

​All provided templates can be reused multiple times.

​

Replace this with a header

Typical Question

Describe how Agile methodologies could be used in the effective production

of the software.

Regular opportunity to assess development and success
​

Shorter iteration of work and quicker response to change
​

Gather requirements at the same time as development software
​

Greater customer collaboration with client and software development team

Analysis: Scope

Scope defines what the software will include—its functions, features, and goals. It outlines the problems the software aims to solve and the main tasks it must perform.

Think of Scope as to what the System can do

Example of Scope

A school attendance system might include:

• Logging student attendance.

• Generating attendance reports for teachers.

• Allowing parents to view absences.

Analysis: Boundaries

Boundaries define what the software will NOT do. These restrictions help keep the project focused and manageable.

Think of Boundaries as to what the System can't do

Example of Boundaries

For the school attendance system:

• It will not handle student grades (that would be a separate system).

• It will not allow parents to edit attendance records (only teachers/admins can do this).

• It will not work offline (requires an internet connection).

Multiple Choice

What does the 'scope' of a software project define?

• The limitations and constraints of the software

• The specific coding language to be used

• The estimated completion time for the software

• The features and functionality the software will include

Multiple Choice

Which of the following best describes 'boundaries' in software development?

• The estimated cost of developing the software

• The features the software will include

• The aspects that the software will NOT cover

• The time required to complete the project

Multiple Choice

A company is developing a library management system. Which of the following is an example of a boundary?

• The system will allow users to borrow and return books

• The system will generate overdue book reports

• The system will allow students to reserve books

• The system will NOT track employee salaries

Multiple Choice

Why is it important to define scope and boundaries during the analysis stage?

• To ensure the software is completed as quickly as possible

• To prevent unnecessary features and unrealistic expectations

• To determine which programming language will be used

• To ensure the software is expensive to develop

Multiple Choice

A school is developing an online homework submission system. Which of the following is OUTSIDE the scope of the project?

• Allowing students to submit homework online

• Allowing teachers to mark and return homework digitally

• Allowing students to check their grades

• Managing the school's payroll system

Multiple Choice

Which of these statements about scope and boundaries is FALSE?

• The scope defines what the software must do

• The boundaries define what the software must NOT do

• Boundaries help prevent the project from expanding beyond its intended purpose

• Scope and boundaries are not necessary if the project has a large budget