Functional Requirements Web Application Travel Itinerary Planning System

Sheffield Hallam University
WEB APPLICATION DESIGN AND MODELLING (A-2011/2) WADAM
Functional Requirements
Web Application
Travel Itinerary Planning System
2012
Distribution :
Hallam Internet Systems Ltd
Document Version Control System - Google web docs
Document Management Control - Google web docs

Version Document Authors Student ID Date
v1 Mr Adrian Ashley 12030388 4/11/2011
Mr. Mohamed Hagras 21046615 4/11/2011
Mr. Akilu Rilwan Muhammad 20049705 4/11/2011
Mr. Zhao Jian 21040874 4/11/2011
2|Page
2012

Project Plan
CONTENTS
1.0 INTRODUCTION AND OBJECTIVES
2.0 FUNCTIONAL REQUIREMENTS
3.0 RISK MONITORING
3.1 Risk Verification and quality control
Bibliography
Glossary
APPENDIX A - Project Management
APPENDIX B - QUALITY CONTROL
3|Page
2012
1.0 INTRODUCTION AND OBJECTIVES

To develop the functional requirements of the systems, below is communication from the
client.
Customers contact details

Mr Dharam Shadija, Mr Steve Lofthouse
We at Innovative travel solutions are known for pioneering travel solutions for example
the ability for people to be able to search for flights for any airline on a single website
was first developed by us over 10 years ago.
We have had another brilliant innovation which will help people organise their travel
itineraries online. This will allow users to share information about their travel with their
loved ones and friends.
Users should be able to create their itinerary online using our website. They could add Flight
details, train details and hotels information into their itinerary. This is private information
and should be only accessible to that particular user. The system should allow users to
create any number of itineraries. Our system should allow people visiting our site to become
users on our site.
Hallam Internet Systems - Team members established 19/10/2011
Mr Adrian Ashley B.Sc (Hons) Student ID 12030388
Mr. Mohamed Hagras Student ID 21046615
Mr. Akilu Rilwan Muhammad Student ID 20049705
Mr. Zhao Jian Student ID 21040874
2.0 FUNCTIONAL REQUIREMENTS
The following requirements were developed during our meetings and emailed to the Hallam
Internet Systems members, further a risk analysis was investigated and a clarification on the
deliverables was confirmed with the client.
[Tracking ID 01 4/11/2011Responce ] and documented in the 3.0 RISK
MANAGEMENT
The functional requirements are as follows:
4|Page
2012
Travel Itinerary Planning System-Functional Requirements

1. Register users into the system.
2. Login registered users into the system.
3. Log out registered users from the system.
4. Create travel itinerary.
5. Add contents to the travel itinerary.
6. Edit travel itinerary contents.
7. Delete travel itinerary contents.
Travel Itinerary Planning System-Users of the system

1. Registered user.
2. Un-Registered user.
Travel Itinerary Planning System- Use Case

1. Use Case Name: Register
Actor: Non-registered user
Use Case Description:
i) User selects Register
ii) System prompts for user details
iii) User enters his details, checks approve on terms and
conditions and submits
iv) System store user’s details into the database
v) System displays account created successfully.
2. Use Case Name: Login

Actor: Registered user
i) User select login
ii) System prompt for user account
iii) User supply login account
iv) System validate user account
v) System starts user’s session
vi) System display login success message
vii) User is login successfully
5|Page
2012
3. Use Case Name: Logout
i) User is login
ii) User select logout
iii) System prompt for logout confirmation
iv) User verify logout selection
v) System confirms user logout
vi) System display logout success
vii) User is logout successfully.
4. Use Case Name: Search for itinerary contents (flight, hotel etc...).
Actor: Registered user& Non-registered user

i) User fill in the search form and click on search
ii) System compares it with the database
iii) System displays the matched results
iv) If user was signed in system will store the search result
and user can see it in previous search button in his
account
5. Use Case Name: Create travel itinerary.

i) User is login
ii) User selects create new Create travel itinerary
iii) User search for itinerary contents (flight, hotel etc...).
iv) User selects the contents he likes from the search
results.
v) User submit content
vi) System updates user's travel itinerary.
6. Use Case Name: Add contents to the travel itinerary

i) User is login
ii) User selects Add contents to the travel itinerary
iii) User selects the contents he wants to Add to the travel
itinerary
iv) User submit content
v) System updates user's travel itinerary.
6|Page
2012
7. Use Case Name: Edit travel itinerary contents

vi) User is login
vii) User selects edit travel itinerary
viii) User selects the contents he wants to edit
ix) User submit content
x) System updates user's travel itinerary.
8. Use Case Name: Delete travel itinerary contents.

i) User is login
ii) User selects delete itinerary
iii) User selects the contents he wants to delete
iv) User submit content
v) System updates user's travel itinerary.
7|Page
2012
3.0 RISK MANAGEMENT

According to the project plan v17, the Risk management is in full operation for the project and
adhered to.
TABLE 3, Risk of Organisational Roles

Responsibility Risk Monitoring Journal
Update
Mohamed Hagras Project Manager Responsibilities overall project tasks 4/11/11
Mr Akilu Rilwan sequence and activity
Muhammad
Providing staff needs
Mr. Zhao Jian
Team Meeting attendance recording
Adrian Ashley
Mohamed Hagras Communications Update Project requirements 4/11/11

Mr Akilu Rilwan Administrator Change management
Muhammad
Adrian Ashley Documentations & Document standards 4/11/11

Mr. Zhao Jian Backup Administrator UML Maintenance
Mohamed Hagras Staff Training Maintaining staff training for the project 4/11/11
Adrian Ashley Administrator Risk monitoring,
Document control
3.1 Risk Verification and quality control
The clarification has reduced the risk to the project, the request and response is
listed below
[Tracking ID QC RM 01 4/11/2011 Request ]
Dear Mr Shadija , Mr Lofthouse
CC Team Hallam
SUBJECT - Do you have a Check list or Marking Scheme for Submission 2 today
are the deliverables as follows
-------------------------------------<>
1) A UML Usecase diagram
2) Class and Object diagram
3) Functional description of the action in the system
--------------------------------------<>
8|Page
2012
So that Team Hallam Internet System Ltd , can deliver a complete functional requirement as
requested and adhere to the quality control standards and document control which is part of our
companies project plan
You feedback is much appreciated.
Thanks
HALLAM INTERNET SYSTEMS Ltd
[Tracking ID QC RM 01 4/11/2011 Response ]
Dear Developers at HALLAM INTERNET SYSTEMS Ltd,

Thanks for your query.
We have discussed this at our company and we only expect you to deliver functional requirements
document this week. Once we are happy with your understanding of our system you can deliver Use
case document a week today.
We won't be able to issue you a criteria for the functional requirements.
Cheers
Dharam
Bibliography
Mr Dharam Shadija, M. S. L., 2011. Lectures Sheffield Hallam Univerity. [Online]
Available at: https://shuspace.shu.ac.uk
[Accessed 3 11 2011].
Glossary
QC Quality Control
RM Risk Management
UML Unified Modelling Language
Further Reading
Quality Assurance Plan
Configuration Management Plan
Risk Management Plan
Project Schedule
9|Page
2012
APPENDIX A, Project Management
Ref 3.The Spiral Model diagram from (Boehm 1987)
http://www.ics.uci.edu/~wscacchi/Papers/SE-Encyc/Process-Models-SE-Encyc.pdf
10 | P a g e
2012
APPENDIX B QUALITY CONTROL
Hand in Investigate
assignment Assignment
Refine Develop a
plan of
Assignment action
Draft the
Meeting main
discussion
11 | P a g e

Functional Requirements Web Application Travel Itinerary Planning System

Enviado por

Dados do documento

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

Functional Requirements Web Application Travel Itinerary Planning System

Enviado por

Direitos autorais:

Formatos disponíveis

Sheffield Hallam University

WEB APPLICATION DESIGN AND MODELLING (A-2011/2) WADAM

Hallam Internet Systems Ltd

Document Version Control System - Google web docs

Document Management Control - Google web docs

Travel Itinerary Planning System

2.0 FUNCTIONAL REQUIREMENTS

3.0 RISK MONITORING

3.1 Risk Verification and quality control

APPENDIX B - QUALITY CONTROL

1.0 INTRODUCTION AND OBJECTIVES

Customers contact details

Hallam Internet Systems - Team members established 19/10/2011

Mr Adrian Ashley B.Sc (Hons) Student ID 12030388

Mr. Mohamed Hagras Student ID 21046615

Mr. Akilu Rilwan Muhammad Student ID 20049705

Mr. Zhao Jian Student ID 21040874

2.0 FUNCTIONAL REQUIREMENTS

The functional requirements are as follows:

Travel Itinerary Planning System-Functional Requirements

Travel Itinerary Planning System-Users of the system

Travel Itinerary Planning System- Use Case

2. Use Case Name: Login

Actor: Registered user& Non-registered user

5. Use Case Name: Create travel itinerary.

6. Use Case Name: Add contents to the travel itinerary

7. Use Case Name: Edit travel itinerary contents

Actor: Registered user

8. Use Case Name: Delete travel itinerary contents.

Actor: Registered user

3.0 RISK MANAGEMENT

TABLE 3, Risk of Organisational Roles

Mohamed Hagras Communications Update Project requirements 4/11/11

Adrian Ashley Documentations & Document standards 4/11/11

3.1 Risk Verification and quality control

[Tracking ID QC RM 01 4/11/2011 Response ]

Dear Developers at HALLAM INTERNET SYSTEMS Ltd,

Configuration Management Plan

Risk Management Plan

APPENDIX A, Project Management

Ref 3.The Spiral Model diagram from (Boehm 1987)

APPENDIX B QUALITY CONTROL

Você também pode gostar