|




  

 PHASE 2 ± Requirements
Specification
‡ GREENWICH SMOOTHIES -
INDIVIDUAL REPORT

‡ You have completed a Specification of

Requirements (Coursework 1) for the
company Greenwich Smoothies and have
received feedback on the quality and
thoroughness of your document.
 Standardised Findings
‡ You have also been provided with a set of
à

à à which you will use
to proceed further in your analysis. These
are found on teachmat and labelled

‡ Staff Findings
‡ Customer Findings
‡ Chat with Charlie Mango
 Your task«
‡ You are now required, as an individual, to
produce a Requirements Specification for
the company Greenwich Smoothies,
based on the standardised findings. You
will also make an oral presentation to the
Managing Director of the company, Charlie
Mango.
 Section 1
Project Background so far, including
‡ The purpose of the project
‡ Client, Customer and Stakeholders
‡ The Users
 Section 2
Project Constraints & Assumptions,
including
‡ Budget, Schedule
‡ The current system, hardware and
software
‡ The current physical environment
‡ Assumptions which you are making about
the future (about the environment, the law,
the product etc)
 Section 3
User group name, responsibilities
User knowledge of the business, of
technologies
User abilities/disabilities, education, skills
User age, gender
User motivation, attitude

(NOT ALL WILL BE RELEVANT)

 Section 4
Functional Requirements, including
‡ The scope of the project
‡ The scope of the product(s)
‡ Functional requirements, mapped from
Use Case diagrams, detailed in
Requirements Catalogue
‡ Data requirements, mapped from Class
Diagrams, relevant to the product
 Section 5
Non-Functional Requirements, including
‡ Appearance and style
‡ Accessibility and Interaction Design
‡ Maintenance, Support
‡ Performance, Seasonality
‡ Security
‡ Legal, Cultural, Ethical, Political
Requirements
 Section 6
Project Issues, including
‡ Project Planning & Management, Risk &
Quality Planning
‡ User documentation and training
‡ Implementation
‡ The future
 Section 7

Recommendations, including
‡ Hardware
‡ Software
‡ Communications
 Appendices
‡ Requirements Catalogue (consisting of a
number of templates)
‡ UML models (consisting of an example of
a Use Case diagram and a Class
Diagram)
‡ Example screens from similar existing
interfaces with your comments
‡ Prototype screen designs for your system
‡ Example Report(s) for Charlie Mango
 Extension work«.
‡ You may also include any other sections or
entries which you feel may be of interest to
Charlie Mango and the Management
Team. Examples would be Project
Planning documents and details of
Hardware and Software
recommendations.
 Report Style
‡ The Requirements Specification should be
written as a Technical Report. It should be
smartly word processed and page
numbered. All diagrams should be
produced to a professional standard. The
report should be arranged in numbered
sections (as specified above) and sub-
sections.
 Report Style
It should also include the following:
‡ Title Page
‡ Contents Page
‡ Introduction
‡ Executive Summary
‡ The deadline for this piece of individual
work is Thursday 28th April 2011.
 Presentation
‡ You will be required to make an individual
presentation of your findings to the
Managing Director, Charlie Mango.

‡ Presentations will be booked with your

tutor before Easter and will take place on
28th April and 6th May 2011.