TransNamib User Requiremen ts Document

August 29

201 2
[URDocument ]

Polytechnic of Namibia Department of Software Engineering Lecture: Mr. Gereon Koch Kapuire
Student Name 1. Ikany J. 2. Andjamba T.S. 3. Ipinge H.N 4. Shikesho M.K.P. 5. Nghiyalwa J.P.N Student Number 200870580 201059592 200826921 200842889 201043556

Revision Sheet

Revision Sheet Release No. Rev. 1 Date 08/28/12 Revision Description User Requirements Document

User Requirements Document

We fully accept the changes as needed improvements and authorize initiation of work to proceed. Based on our authority and judgment, the continued operation of this system is authorized. This Development Agreement is effective as from 31 August 2012 BETWEEN: TransNamib Holding Ltd, a company organized and existing under the laws of the National Transport Services Holding Company Act, no. 28 of 1998 of Republic of Namibia, with its head office located at: Bahnhof St, Windhoek Private Bag 13204 WINDHOEK NAMIBIA AND: Polytechnic of Namibia Software engineers which located at: 13 Storch Street, Windhoek Private Bag 13388 Windhoek Namibia 31 August 2012 DATE 31 August 2012 DATE 31 August 2012 DATE 31 August 2012 DATE

SHIKESHO M.K.P NAME Project Leader IKANY JORIS NAME Operations Division Director ANDJAMBA T.S NAME Program Area/Sponsor Representative IPINGE H.N NAME Program Area/Sponsor Director

WHEREAS: The Customer is in the business of Transport Services and has prepared and submitted to the Develop the request for Proposal which outline the Customer's requirement for a Database based system which will satisfy the management needs of customer. In reply to the request for proposal, the developer has prepared and submitted, and the customer has accepted, the proposal which was submitted as part of project description. The developer has represented that it has the capacity and professional ability to produce such functional specifications and, on the basis of that representation, the Customer wishes to purchase and the developer wishes to supply its services on the terms and conditions set out.

User Requirements Document

GENERAL CONFIDENTIALITY IN addition to the confidentially provisions, both parties hereby agree that any confidential information relating to the other which shall be gained carrying out the requirements of this agreement, or relating directly to this agreement, shall be protected by the party gaining such information in the same manner as it would protect its own trade secrets and such confidential information shall be held in trust for the benefit of the other part only. This paragraph shall survive the termination of this agreement. DELIVERY The Developer hereby agrees to deliver the complete functional specifications to the customer for approval on or before the delivery date specified in the development schedule. COPYRIGHT COVER The developer shall defend or settle any suit or proceeding brought against the customer based on a claim that the functional specifications provided by the developer hereunder or the copying in Namibia by the customer of any part of the functional specifications constitutes an violation of any existing copyright, trade secret or other property right, provided for the conclusion or defense of same. The developer shall pay all damages and cost awarded therein against the customer, but shall not be responsible for any costs, expense, compromise or decision earned or made by the customer without the developer's prior written assent. This indemnification shall survive the termination of agreement.

User Requirements Document

1.0 General Information

USER REQUIREMENTS DOCUMENT TABLE OF CONTENTS Page #

GENERAL CONFIDENTIALITY..........................................................................................................iii DELIVERY..............................................................................................................................................iii COPYRIGHT COVER.............................................................................................................................iii 1.0 GENERAL INFORMATION..............................................................................................................1 1.1 Purpose.............................................................................................................................................1 1.2 Scope.................................................................................................................................................1 1.3 Project References...........................................................................................................................1 2.0 Overal Description................................................................................................................................1 2.1 Product Viewpoint...........................................................................................................................1 2.2 Product Functions ..........................................................................................................................1 2.2.1 .1 Hardware Requirements.........................................................................................................3 2.2.1.2 Software Requirements.............................................................................................................3 2.2.1.4 Performance Requirements......................................................................................................3 2.2.1.5 Supportability Requirements...................................................................................................3 2.2.1.6 Security Requirements..............................................................................................................4 2.2.1.7 Interface Requirements.............................................................................................................4 2.2.1.8 Availability Requirements........................................................................................................4 2.2.1.9 Assumptions / Constraints........................................................................................................4 3.0 Proposed Methods and Procedures.....................................................................................................1 3.1 Summary of Improvements............................................................................................................1
3.1.1 Functional Improvements..............................................................................................................................1 3.1.2 Timeliness.....................................................................................................................................................1

1.0 General Information

1.0

GENERAL INFORMATION

1.0 General Information

1.0 1.1

GENERAL INFORMATION Purpose

The main purpose of this project is to reduce the manual errors involved in the TransNamib Booking process and makes it suitable for the customer to book the train as when they require.

1.2

Scope

This name of this system is TN Booking System which gives an option for viewing different train available with different timing for specific date and provides the customers with the capability to book a ticket, modify of or cancel a particular ticket.

1.3

Project References
Oracle Database Express Edition, Installation Guide

10g Release 2 (10.2) for Microsoft Windows B25143-01 February 2006 Oracle Database Study Guide

User Requirements Document

Page 1

2.0 System Overall Description

2.0

SYSTEM OVERALL DESCRIPTION

User Requirements Document

2.0 System Overall Description

2.0 2.1

OVERAL DESCRIPTION Product Viewpoint

2.1.1 The TN System interface The client systems should be able to share the data available in the database via the network connection. 2.1.2 User Interfaces The screen formats should be in such a way that even user will find it easy to use. The system must be user-friendly and very inter-active. The functionality provided by the system like displaying error messages should familiarize itself to different users of the software. 2.1.3 Software Oracle database 10g/11g 2.1.4 Memory Constraints Put the requirement for database server (oracle 10g or 11g) 2.1.5 Operation The users can first make a booking for a specific train for a specific time and date. Then after that the system will give any option to make change in the booking or cancel a booking.

2.2

Product Functions

2.2.1 Functional Requirements The project performs the following functions: Search for train: The system allows the train passenger to search for trains that are available between the two travel location, namely the Departure location and Arrival location. In the System the will be a function/procedure that accept 2 values for the system user for the two passenger for two locations and displays a list of train that are scheduled for these locations.

Functional Requirements Document

Page 1

2.0 System Overall Description

2.2.2 User-Defined Functional Requirements User System Administrator User Required Functionalities Passengers/Customers Login into the system Make bookings Cancel Bookings Sign-up as members View the number of spaces available for the train trip View the times the train make trips Make payments for the trips tickets Train Booking Staffs Login into the system View the number of people who make bookings Accept the bookings Cancel Bookings Accept Payment View the number of trains making trips View the number of ticket available Provide more or few tickets for booking View Reports on: What time does is the most booking done What days do most trains make trips What is the maximum number of trips does a train makes in a month What is the maximum number of people a train takes per day What is the maximum number of tickets printed per day Login into the system Administer the System Create end users Perform All system Audits Maintain the System

Functional Requirements Document

Page 2

2.0 System Overall Description

2.2.1 Non Functional Requirements 2.2.1 .1 Hardware Requirements RAM 512 megabytes minimum, 1024 megabytes recommended System architecture Intel (x86) 2.2.1.2 Software Requirements Operating system one of the following 32-bit Windows operating systems: Windows 2000 Service Pack 4 or later Windows Server 2003 Windows XP Professional Service Pack 1 or later Windows 7 Enterprise or Professional Edition 2.2.1.3 Web Browser Requirements For both the server and client components of Oracle Database XE, ensure that the web browsers you plan to use support JavaScript and the HTML 4.0 and CSS 1.0 standards. Ensure also that cookies are enabled. The following browsers meet this requirement: Microsoft Internet Explorer 6.0 or later Netscape Navigator 7.2 or later Mozilla 1.7 or later Firefox 1.0 or later

Oracle Application Express does not support the Corel SVG Viewer. 2.2.1.4 Performance Requirements The database should have adequate and fast performance to retrieve the information for the bookings. The speed per transaction for booking should be at least 10.0 megabytes per seconds The minimum bug counts should at least be 2 times in a month The system should pass the test requirements with at least 95% efficiently 2.2.1.5 Supportability Requirements
The system should have well written and clear pl/sql procedures and functions.

The system should have well defined and declared local and global variables. The system should be well maintained at all the times by the system administrator at least twice in a week.
All the required utilities such as the oracle XE Server and the Oracle client server should

be well maintained and monitored for faulty errors.

Functional Requirements Document Page 3

2.0 System Overall Description

2.2.1.6 Security Requirements There should be authentication for every user who will use the system There should be security audit for every user who will log into the system The user data should be well encrypted and safely supported for every user The resources for the system should be well utilized which includes the data, users and components Every requirement should be assigned with a unique ID 2.2.1.7 Interface Requirements The interface requirements require a network protocol of TCP/IP. 2.2.1.8 Availability Requirements The system should always be available 24/hours and it should be operational for every function to be used for the customers. 2.2.1.9 Assumptions / Constraints Hardware Faults System Failure Technical System failure System Shut down No back-up done

Functional Requirements Document

Page 4

2.0 System Overall Description

3.0 PROPOSED METHODS AND PROCEDURES 3.1 Summary of Improvements

Efficient data sharing and security Efficient data saving for the booking tickets and the passengers who do the booking Fast trips details searching and management 3.1.1 Functional Improvements Discuss functional improvements, including new capabilities. Passengers can make bookings online No more long queues needed to be done to make a booking Few staff will be needed for the booking processing 3.1.2 Timeliness Improved working time for the passengers

END OF THE REQUIREMENT SPECIFICATION DOCUMENT

User Requirements Document

Page 2-5