bsa coursework 2

8/7/2019 BSA Coursework 2

1/16

BSA Coursework 2

The Requirements Specification

Jan Malcolm


2/16

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.


3/16

Standardised Findings

You have also been provided with a set of

standardised findings which you will use

to proceed further in your analysis. Theseare found on teachmat and labelled

Staff Findings

Customer Findings

Chat with Charlie Mango


4/16

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.


5/16

Section 1

Project Background so far, including

The purpose of the project

Client, Customer and Stakeholders The Users


6/16

Section 2

Project Constraints & Assumptions,including

Budget, Schedule

The current system, hardware andsoftware

The current physical environment

Assumptions which you are making aboutthe future (about the environment, the law,the product etc)


7/16

Section 3

User group name, responsibilities

User knowledge of the business, oftechnologies

User abilities/disabilities, education, skills

User age, gender

User motivation, attitude

(NOT ALL WILL BE RELEVANT)


8/16

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


9/16

Section 5

Non-Functional Requirements, including

Appearance and style

Accessibility and Interaction Design Maintenance, Support

Performance, Seasonality

Security

Legal, Cultural, Ethical, PoliticalRequirements


10/16

Section 6

Project Issues, including

Project Planning & Management, Risk &

Quality Planning User documentation and training

Implementation

The future


11/16

Section 7

Recommendations, including

Hardware Software

Communications


12/16

Appendices

Requirements Catalogue (consisting of anumber of templates)

UML models (consisting of an example ofa Use Case diagram and a ClassDiagram)

Example screens from similar existing

interfaces with your comments Prototype screen designs for your system

Example Report(s) for Charlie Mango


13/16

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.


14/16

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.


15/16

Report Style

It should also include the following:

Title Page

Contents Page Introduction

Executive Summary

The deadline for this piece of individualwork is Thursday 28th April 2011.


16/16

bsa coursework 2

Documents