Types of things that could be included:-

• Where is your organisation? i.e. location,?

• Opening hours of the store or store(s)

• Are there multiple branches?

• Describe the business/club in detail, what exactly does it do?  How does it work?  Who is involved?

• What it does/sells, etc. or do?

• If you know the organisation or person in it, mention the connection

• Justification needed as to why you have chosen this project - important!

Describe what happens from different perspectives. i.e. for each different stakeholder (customers, staff, manager, general users). Stakeholders are people who have a reason to use/interact with the system in some way.

EXAMPLE - LIBRARY System

A library has customers who borrow a book and a librarian who loans them a book. The customer and librarian are both stakeholders.

• Customers who borrow books - How do they register to book a borrow?  What do they need to do to borrow it?  What data is stored?

•  A library also have a librarian - What would their role be?  What data would they see?  What would their job involve?

List the problems you could solve within the problem but are too big for solution in the time available or that the software is unable to do.  Some things will be outside the scope of your project. You must list them here. E.g. for theatre ticketing system, staff wages would clearly be outside the scope of the system. 

Example

• I will not be able to store the advert designs directly into the database as Visual Basic doesn’t support importing and saving images from outside sources

 - This means that I will have to store the location address in the database and then the user will have to take that address and search for it in File Explorer.  This will take up the user’s time and does not improve on the current system when looking at this aspect.

• The system won’t be able to see the progress of the delivery as it is being done

- As the system will only work on a computer there is no way for the delivery worker to tell the system how much they have done and how much they still have to do. This can affect the amount of money needed for the delivery and the management members won’t be able to see how efficient the job is being done

- The deliverers can report to staff who have access to a computer by using a mobile phone. They can say when they have completed a street which will give the team a good idea of the progress being made. However, this can slow up the progress of the deliverers.

Make a presentation to explain to the class what your project is about. 

Include the following in your presentation:

• a title slide (make your presentation look professional)

•  a brief background (1 slide) giving an overview of what the organisation does

• project purpose (1 slide) - what you are trying to achieve by doing this for the organisation

• user requirements for each stakeholder (1 slide per stakeholder) - who are the stakeholders, what do they do ?

• possible limitations (1 slide) - restrictions and things outside the project scope
  
  

• You should also create a feedback form (either a google form, or a paper copy), so that each class member can give you immediate feedback.

Write questions which will allow your peers and teacher to give you ideas for the improvement of your project scope.

Include the following, but this is not an exhaustive list. Add some questions which are specific to your project:

• peer/teacher name

• what they liked about your project

• what they disliked about your project and how they think it could be changed/improved

• any additional stakeholders?

• any additional requirements?

• any other project-specific questions
  
  

Make this feedback form (either a google form, or a paper copy), and distribute it before you present, so that each class member can give you immediate feedback.

For each question on your Feedback Form you need to use the responses to refine your understanding of the problem and your proposed solution:

• List each question with the corresponding responses (from class and teacher). You may or may not take on board the feedback.

• Summarise the responses for each question, by discussing what it means to your project, whether you are going to include it in the scope of  your project and why. You don't have to include the feedback in your scope, but you have to explain why not.