functional requirements

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

Functional Requirements

Web Application

Travel Itinerary Planning System

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


Distribution : Hallam Internet Systems Ltd

Document Version Control System - Google web docs

Document Management Control - Google web docs

Version Document Authors Student ID Datev1 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 | P a g e



Travel Itinerary Planning System 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 | P a g e



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

4 | P a g e



The functional requirements are as follows:

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 system1. Registered user.2. Un-Registered user.

Travel Itinerary Planning System- Use Case

1. Use Case Name: RegisterActor: Non-registered userUse Case Description:

i) User selects Registerii) System prompts for user detailsiii) User enters his details, checks approve on terms and

conditions and submitsiv) System store user’s details into the databasev) System displays account created successfully.

2. Use Case Name: LoginActor: Registered userUse Case Description:

i) User select loginii) System prompt for user accountiii) User supply login accountiv) System validate user accountv) System starts user’s sessionvi) System display login success messagevii) User is login successfully

5 | P a g e



3. Use Case Name: LogoutActor: Registered userUse Case Description:

i) User is loginii) User select logoutiii) System prompt for logout confirmationiv) User verify logout selectionv) System confirms user logoutvi) System display logout successvii) User is logout successfully.

4. Use Case Name: Search for itinerary contents (flight, hotel etc...).

Actor: Registered user& Non-registered userUse Case Description:

i) User fill in the search form and click on search ii) System compares it with the databaseiii) System displays the matched resultsiv) 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.

Actor: Registered userUse Case Description:

i) User is loginii) User selects create new Create travel itineraryiii) User search for itinerary contents (flight, hotel etc...).iv) User selects the contents he likes from the search

results.v) User submit contentvi) System updates user's travel itinerary.

6. Use Case Name: Add contents to the travel itineraryActor: Registered userUse Case Description:

i) User is loginii) User selects Add contents to the travel itinerary

6 | P a g e



iii) User selects the contents he wants to Add to the travel itinerary

iv) User submit contentv) System updates user's travel itinerary.

7. Use Case Name: Edit travel itinerary contents


vi) User is loginvii) User selects edit travel itineraryviii) User selects the contents he wants to editix) User submit contentx) System updates user's travel itinerary.

8. Use Case Name: Delete travel itinerary contents.


i) User is loginii) User selects delete itineraryiii) User selects the contents he wants to deleteiv) User submit contentv) System updates user's travel itinerary.

7 | P a g e



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 HagrasMr Akilu Rilwan MuhammadMr. Zhao Jian

Adrian Ashley

Project Manager Responsibilities overall project tasks sequence and activityProviding staff needsTeam Meeting attendance recording

4/11/11

Mohamed HagrasMr Akilu Rilwan Muhammad

Communications Administrator

Update Project requirementsChange management

4/11/11

Adrian AshleyMr. Zhao Jian

Documentations & Backup Administrator

Document standardsUML Maintenance

4/11/11

Mohamed HagrasAdrian Ashley

Staff Training Administrator

Maintaining staff training for the projectRisk monitoring,Document control

4/11/11

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 LofthouseCC Team Hallam

SUBJECT - Do you have a Check list or Marking Scheme for Submission 2 todayare the deliverables as follows-------------------------------------<>

8 | P a g e



1) A UML Usecase diagram2) Class and Object diagram3) Functional description of the action in the system--------------------------------------<>

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.

CheersDharam

BibliographyMr 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

9 | P a g e



Quality Assurance Plan

Configuration Management Plan

Risk Management Plan

Project Schedule

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



APPENDIX B QUALITY CONTROL

11 | P a g e

Investigate Assignment

Develop a plan of action

Draft the main

discussion Meeting

RefineAssignment

Hand in assignment

functional requirements

Documents