York University
CSE 4312 - Software Engineering Requirements
PROJECT: The Wimbledon Tournament
Requirements Document
Section 1: Problem Analysis
a) Description of the Problem
b) Background of the Customer
c) Constraints and Scheduling
d) Users and Basic Functionality
e) The Wimbledon Tournament Operation Information
f) Major Current Problems
g) System Capabilities and Scope
h) Conceptual Flow Diagram
i) Feasibility Analysis
2
2
2
3
3
4
4-5
5
5-6
Section 2: Elicitation Techniques
a) Structured/Closed Interview
b) Questionnaire
7
8 - 10
Section 3: Elicited Requirements
a) Functional Requirements
b) Non-Functional Requirements
c) Inverse Requirements
11 – 12
13
13 – 14
Appendix:
Interview Questions and Answers
Group:
1)
2)
15 - 21
Section 1:
Description of the Problem
Our design team has been approached by the president of The
Wimbledon Tournament to produce a software package …..
Background of the Customer
In conference with a key stakeholder of The Wimbledon Tournament
Mr. Oliveira, we have been able to obtain a general overview of the
company and identify their current high-level goals of the prospective
system. Mr. Oliveira indicated that ….
Strategic Direction of the tournament
There is currently only one Wimbledon Tournament in operations and …..
Constraints and Scheduling
Due to the customer using a commercial off the shelf product …..
Users and Basic Functionality
The design team will need to take into consideration …..
The Wimbledon Tournament Information
There are five different …
Major Current Problems
The stakeholder also discussed several problems they are
encountering with the current system.
System Capabilities and Scope:
The Wimbledon Tournament application to be designed will meet the
following overall objectives:
a) Handle
2
Conceptual Flow Diagram
The following is a concept diagram disseminating the design team’s
view of The Wimbledon Tournament process from a very high level.
Feasibility Analysis
Introduction
This section of the report provides a detailed assessment of the
project in terms of whether the expected benefits and costs are
realistic and if this project has a reasonable chance of success. To
thoroughly consider this projects feasibility, the following five areas
of risk were assessed.
 Economic Feasibility
 Operational, Organizational and Cultural Feasibility
 Technological Feasibility
 Schedule Feasibility
 Resource Feasibility
.
1
1
Satzinger W. “John. Systems Analysis and Design in a Changing World.” Thompson Learning, 2000, p51
3
Section 2
Elicitation Techniques

After preliminary assessments have been made regarding
the knowledge domain of The Wimbledon Tournament, we
decided to gain more insight regarding the domain. By using
proven elicitation techniques
Design Implications:
Section 3: Elicited Requirements
Functional Requirements:
Subsystem1:
Introduction: Stakeholders of The Wimbledon Tournament have asked
us to create a software system that will control The Tournament.
Goal:
Functional Requirements List: (The system must incorporate the
following)
1) Internet operations must be possible.
2)
Subsystem2:
Introduction:
4
Non - Functional Requirements:
Introduction: The following is a list of Non- functional requirements
elicited with regards to the operations of The Wimbledon Tournament
application to be designed. All information was revealed from
interviewing the key stakeholder, the customer responses via the
questionnaire as well as practical knowledge of the current business
environment.
Non-Functional Requirements List: (The system must)
1) Have high usability as a key requirement
Inverse Requirements List:
5