Scribd
Upload
11 views1 page

Week 3 Introduction Audio-Transcript

This week focuses on creating specific requirements for a system before beginning development. Students will go through an example of typical requirements and then work in groups to define requirements for the BookMeIn2 system, which will be the first assessed work. While requirements may need to change during the project, establishing them early allows for less reworking and a clearer focus for design.

Uploaded by

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

Week 3 Introduction Audio-Transcript

This week focuses on creating specific requirements for a system before beginning development. Students will go through an example of typical requirements and then work in groups to define requirements for the BookMeIn2 system, which will be the first assessed work. While requirements may need to change during the project, establishing them early allows for less reworking and a clearer focus for design.

Uploaded by

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

CSC-40084: Software Engineering with Group Project

Week 3 Introduction
Welcome to week 3! This week we will be looking into how to create a set of specific requirements for
a system you have been asked to create. In many real world cases you won’t be given these sort of
requirements directly but will be working with the client to find out what the system you are developing
actually needs to do in practice.

Working out these requirements in detail before you start any form of work is an essential step in the
development process of any project. The more you can get planned and done early on, the easier
and less complicated the latter stages of the project will be as you will be far less likely to end up
reworking features if they turn out to be not what the client actually needs or is required.

We will go through a short worked example of the sorts of requirements that you might need to
produce. Within your groups you will then be looking into creating a set of requirements for the
BookMeIn2 system as a whole. These requirements will form the first piece of assessed work on the
module, as well as defining what you would need to think about when designing the system itself later
on.

Don’t be too surprised if the requirements do need to change later on though in the project. Projects
evolve naturally over time, and one of the main points of using an agile methodology is to allow for
those sorts of changes to take place during the project itself rather than sticking to a rigid set of
requirements.

You might also like