Professional Documents
Culture Documents
Software Requirement Engineering Airline Reservations System Wathik Almayali Phase1 IP5
Software Requirement Engineering Airline Reservations System Wathik Almayali Phase1 IP5
net/publication/332299336
CITATIONS READS
0 13,358
1 author:
Wathik Almayali
Alnisour College University
12 PUBLICATIONS 0 CITATIONS
SEE PROFILE
Some of the authors of this publication are also working on these related projects:
All content following this page was uploaded by Wathik Almayali on 09 April 2019.
1. User-level facilities
Operating System, SQL Platform, Java Platform, NetBeans IDE and Microsoft
Office
School Laptops
Printers
Memory stick.
Software Resources
MS Office
Internet Explorer
Net Beans IDE 6.5
2. Requirements elicitation
2.1 Project Overview
We have to discover the requirements and control encompass all activities involved.
The engineering and system developers are working in close relationship customer
and end users to the problem to be solved. That can find out more around the project. We
have to describe the functionality of the system. We have to performance of the system
such as hardware constraints extra.
2.2 Requirements Elicitation process
We have to check more dut to relevance and importance for some requirments
could change. Could end user for example changing their job. There are process
for many different elicitation that can be found.
2.2.0 Elicitation overview
THE PUROPOSE PROCESS OF THE MODELS CONCENTRATION ON GENERAL THAT
CAN CHANGE REQUIRMENTS AND COSTS. THE COST OF THE CHANGE IN THE
Problem
Statement
Requirement
s Elicitation
Requirements
Functiona
specification:
non-functional
lRequirements
and
Requireme
nts Analysis Analysis
Dynamic
model
Object
We have to identify in this process as a key points of summary project.
model
1. We shall highly dependent on the context and the process of requirements
elicitation.
2
.
2.4.1 Brainstorming
Shall drawing our thought for the process where participants from different a
stakeholder groups engage in information discussion.
2.2.6.0 Zooming
The requirements elicitation technique for the time been. That effort should
only a used selectively to examine in greater detail. That needs deemed especially
important as referring to this approach as zooming. We have to take the
individual weakness of otherwise effective tetechnique. At the same time we
have to take advantage of their combine strength without increasing significant
unnecessary increase in both effort and time.
3. We have to make sure what does the system do for this requirements.
7. We can define the solution as collection of data for this software application.
3.0.3 Documented
We have to complete collection data and documented that will be manual
files for airline system reservation. We have to upgrade the existing PC based on
the system. If we want to computerize the existing manual system. In this
document. There are reports such as forms, memos, business plans, and policies
and organismal chart. That provide all information about the system we want to
build.
Description & This section shall allow the user – whether enrolled
Priority: or not – to view flight information that matches
input criteria. The user will provide:
a. A flight number and Date
OR
b. Departing/Arriving Cities and Date.
Pre- None.
Conditions:
Side-Effects: None
Source: Inputs are from the user except flight information, which is
retrieved from the system.
Output: The purchased seats are tied to the user’s account, so he/she
can reserve seats later.
Post- Completion of this function guarantees that the user has seats
Conditions: on a specific flight. However, if the user wants particular
seats, he/she must also complete the reserve seats function.
Any successfully-booked flight from this function is assumed
to have completed payment already.
Stimulus/Response:
4. The user confirms the seat 5. Once confirmed, the seats are removed
selections on the screen. from available seats and are applied to
the user account. The user is shown a
final confirmation screen which displays
selected seats and account information.
3.0.7 Account
Description This section gives the user the power to view, save, edit or
& Priority: delete the information stored in his/her account. The user
can check his/her accumulated points, look at the status of
a flight that was booked, cancel a flight that was already
booked (optional) and change his/her address, phone
number, email or password. This feature is not available for
non-registered user.
Inputs: Account changes, if any, made by the user. Account
changes include updates on first name, last name, and
email address, mailing address, password or phone
numbers.
Source: All data are inputs from user.
Output: None.
Destination: The changes are committed on completion of the My
Account function to account information.
Pre- The user must have an account with the website and must
Conditions: be logged in prior to access his/her account.
Post- All changes submitted by the user are applied to the user
Conditions: account on completion of the function.
Description The Logout section provides a way for the user to securely
& Priority: log out of the system. This process will save all user
operations when he/she exits the system. If a user wishes to
continue accessing the website, he/she must log-in again to
access user features.
Inputs: None.
Source: N/A
Side- The system clears the session state for the user once logout
Effects: is
Add/Delete/Modify
Customer InformaJon
Add/Delete/Modify
flight informaJon
Administrator
Add/Delete/Modify
Package InformaJon
CancellaJon of
ReservaJons
Modify details of
webpage
E-
mail
ConfirmaJons
The Administrative management system
DATA DESSCRIPTION
List of Airport name, location, abbreviation such as City, State, time zone
airports
Specific Flight id, Airline Departure/arrival and Date/time
flight
Verify Airport, Seats and total, vacant seat number.
departure
and
destination
such as
Type of the First class, Business class, second class and regulars
seats
Information Flight idea, email, passenger name, credit card type/number,
of address and total price
reservations
made
User Email, password
information
4.3.3 Summery
To start with, I have performed manual testing on the Airline Reservation System
Website. Manual Testing is one of the oldest and rigorous methods of software testing.
This testing strategy gives the best opportunity to check every page thoroughly and
make sure it works in the expected manner. Due to the complexity of the various
automation tools and the time available for testing the entire web application, I preferred
to use manual testing based on the fact that it is one of the best methods of testing
suggested for a beginner. All the test cases mentioned in the Test Plan document of Phase
II were tested here. The results of the manual testing are represented in the following
tables.
Verification Requirements
Objectives: Verify all Project Plan elements and validate if elements match with
the Statement of Work.
Rationale: In order to accomplish project objectives in the expected quality, time
and cost, it is important to verify and validate all project elements.
Roles: Project Manager
Technical Leader
Customer
Products: Verification Results
Acceptance Record
Artefacts: Project Plan
Statement of Work
Steps: 1. Verify the Project Plan
2. Validate the Project Plan
3. Document the results
4. Make corrections
Step Step 1. Verify that all Project Plan
Description Verify that all Project Plan elements are viable and consistent
:
Step 2. Validate the Project Plan
Validate that the Project Plan elements definition match with the
Statement of Work.
Note: Very that the Project Plan including V&V tasks in order to
assure the quality of work products.
ü There are general checklists and checklists for particular modeling and
specification languages
–
Consistency - do the descriptions of different requirements include
contradictions? Are there contradictions between individual
requirements and overall system requirements?
Requirements Review Checklists
5.2 Validation & Verification
• Effective (even after considering cost)
• Authors are more attentive when they know their work will be
closely reviewed
5.3 Verification of design
Factory Acceptance
Project Validation
Project Validation
Plan Final Report
Site Acceptance
Continuity Plan
Specifications
Requirements
Protocol Final
Security Plan
Specification
Performance
Qualification
Qualification
Qualification
Operational
Document
Installation
Functional
Business
Reports
Testing
Testing
Plan
Project
Manager
System
Owner
Operations
Engineering
Technical
Support
Validation
Quality
Assurance
Technical
Writer
Add and
subtract as
required
Traceability Matrix
References:
2013, Cornell Project Management Mythology, retrieved by Wathik from URL
http://www2.cit.cornell.edu/computer/robohelp/cpmm/CPMM_Guidebook.htm#Phase2_
Process_Descriptions.htm
January 2007, Michele Fisher, University of Colorado Student information system
replacement project, retrieved from URL
CR.010 Project Management Plan - Welcome | University of Colorado
http://www.capterra.com/reservations-software?utm_source=bing&utm_medium=cpc
November 28, 2012, hardeep kumar , Java project | Flight reservation system project
retrieved from URL http://presentstudy.com/java-project-flight-reservation-system-project-in-java-
free-download#HRmMKbpUeAAH6rKR.99