22C4400 – Database Systems Project – Initial 1/28/2019
Project Scope
Raman Aravamudhan RSA-22C4400-S19-PROJECT-SCOPE
Department of Computer Science Page 1 of 5 Version 1.1
Note: This document is intentionally incomplete and is in non-standard
format; as part of the course details on requirements will be provided when
asked.
Project Scope:
A new airline company“Iowa Air”has come to Iowa with Cedar Rapids as
its Headquarters. Iowa Air seeks to build their Airline Passenger
Reservation System (ARS). This airline is expected to attract Iowa and
surrounding passengers in a big way. The Reservation system must be
simple, easy to use and offer very high performance.

Customer seeks to build a state of the web application for their Airline.
Students can take www.aa.com for example for detailed functionality.
Project will follow an open book approach which means extensive
discussions with TA and myself are permitted.
In Phase1, Iowa Air plans to operate only Nonstop flights to 5 cities in the
United States; passengers should be able to pay using Visa/Master Card,
and thereafter be able to query the system about their reservation. The
airline schedules can be altered at any time and must be easy to change.
Details of Aircraft are also captured. Assume standard features of Aircraft
and schedules. Passengers should be able to print a receipt and also
receive it as email. Iowa Air allows the passenger to change their
reservation free of cost till 2 days before flight departure time. After that
penalties occur but it will be handled through over the counter and
telephone support process.
Phase 2 will involve Direct Flights and the use of Hub system. Phase 3 will
involve Frequent Flier Mileage program, Seat selection and Trans-Atlantic
Flights. Iowa Air seeks that the design must cater to development of these
capabilities without any modifications to the Phase 1 design.
The goal of this phase of project is to create a robust data model and design the
database using the principles taught in the course. A data driven approach is
highly desired.
Customer objectives and scope description
The proposed web portal must be highly extensible and support concurrency.
The goal of this phase of project is to create a robust data model and design the
database using the principles taught in this course.
An urgent requirement is build a state of the art web / mobile application for
above integrated software application. An iterative approach is probably ideal.
The goal is to build an integrated System. A first step is to gather more
detailed requirements and build a good data Model, use Normalization
22C4400 – Database Systems Project – Initial 1/28/2019
Project Scope
Raman Aravamudhan RSA-22C4400-S19-PROJECT-SCOPE
Department of Computer Science Page 2 of 5 Version 1.1
techniques and design the Normalized database catering to excellent
performance in a totally secured environment.
The key is to come up with a good efficient database design which can support
both Mobile and Web browser environments. The user interface is important but
not every screen is required in Phase 1, as the focus is on database. Use of
Stored procedures must be maximized. Focus is on Database aspects of
the project.
The software must be implemented by semester end which means that a well
tested demo system must be launched that time. Customer prefers to see
intermediate versions of the proposed software. ER Model, Normalized
Database, DDL scripts, Database Objects, Screens and some of these functions
must be delivered in that order. Use of ORM like Hibernate (to be taught in this
course) are good capabilities to consider. Customer contacts will provide
additional details of requirements, if requested by the Project team during project
team meetings.
Customer contacts:
Team # Primary Customer contact Alternate Customer contact
All Ingroj RAMAN
General Requirements:

1. Data Model, Normalization, Database Design, Stored Procedures should be
   as detailed as possible. The user interface and programming will be for
   limited functions only (to be identified). Please use AA only for reference.
   Kindly use Iowa Air in all your work products.
2. The tool should be user friendly & require minimal data entry. The Software
   development team and the Business analysts are required to suggest the
   specific user friendly features while drafting the User Requirement
   Specifications. Some examples of user friendly features may be
   a. minimum data entry
   b. data transfer from context sensitive help screens
3. The system must support user Id / Password based authentication and must
   offer the best security features. The software development team is required
   to identify (in URS) the specific security features to be incorporated in
   software. Some examples of such security features may be
   a. Data encryption techniques (128 bit)
   b. Invisible password
   c. Structure of Password
   d. Password change policy
   e. User Id / Password retrieval policy
   22C4400 – Database Systems Project – Initial 1/28/2019
   Project Scope
   Raman Aravamudhan RSA-22C4400-S19-PROJECT-SCOPE
   Department of Computer Science Page 3 of 5 Version 1.1
   Functional requirements:
4. Book Flight – Round Trip
5. Book Flight – 1 Way
6. Book Flight – Multi City
7. Book Flight – Award Travel
8. Flight Status , Notification
9. Aircraft (CRUD)
10. Flight (CRUD), Aircraft Assignment for Flight
11. Advantage Account
12. Advantage Account logging
13. Your trips
14. News about vacations
15. Contact us
16. About us
17. Advanced Search
18. Trip Cancellation and Change
19. More to be identified

Non Functional and Operational requirements from project team:

1. Each Team must pick a Team Leader and may pick a corporation name
2. Team work is very important.
3. Team members must have regular meetings each week.(at least 2)
4. Meetings should be well planned and should preferably be less than 15
   minutes in each meeting.
5. It is highly recommended that teams meet once after class every week.
6. Distributed teams are a matter of fact; technology should be used to meet
   from remote, if it is convenient.
7. Team must submit more detailed schedule and get it approved.
8. The work done in each stage of software development must be acceptable to
   the customer.
9. All members of the team must assume specific responsibilities.
10. The customer must be informed of the Roles and Responsibilities
11. The tools required for the project will NOT be provided by the customer.
12. Due to acute shortage of resources, the customer is able to meet with project
    teams only on a pre-arranged basis during regular office hours.
13. Use of Stored procedures must be maximized.
14. All documents must be delivered using ICON drop box.
15. Teams must develop the Screens and demo the screen flow before
    developing the full software.

16. It should be easy to make changes to database design
    22C4400 – Database Systems Project – Initial 1/28/2019
    Project Scope
    Raman Aravamudhan RSA-22C4400-S19-PROJECT-SCOPE
    Department of Computer Science Page 4 of 5 Version 1.1
    Specific Deliverable schedule: [Due dates to be decided with class, TA]

    Deliverable Description Due date Weight %

17. Project Plan with individual Schedule < 2 pages
18. Data Attribute collection, Initial DB creation 2/5/19 5
19. User Requirement Specs , Usecase development 5
20. Definitions of queries required in English 5
21. Test Plans , Testing 5
22. ER Model (must be very detailed) 15
23. Normalized database 10
24. High Level Design (screens, database, architecture,
    De-Normalizations if any) Design must be derived
    from model
    10
25. Demo of Stored procedures, functions 10
26. Working software deliverable Iteration 1 10
27. Working software deliverable Iteration 2 – Final 10
28. Use of advanced DB features – discuss 5
29. Final Team Presentations 5
30. Team work 5
    [Item1] Project Plan. Briefly describe the availability of each team member,
    when you plan to meet, roles and responsibilities etc.
    [Items 2-3] Project – Functional / User Requirements /Data Attribute
    a. List all functions and describe it briefly
    b. For each Function list all Data Elements (Input, Output, Persisted or not)
    c. For each Data element identify (Data type, Validations, Domain, Constraints,
    Key or Not, Size, usage etc.)
    d. Write queries in words, GUI , Get Coding skills
    Data Attribute collection: Come prepared for project meeting with Data
    Attributes collection on 2/5/19
    [Items 4] Test Pan (Requirement #, Test condition, Expected result)
31. How you plan to test tool and its components (stored proc, queries)
32. Test Strategies (100%, Black box / white box testing)
33. Unit, Module, over all functional
34. Traceable to requirements
    [Items 5] E-R Model, Normalization [TBA]
    [Items 6] DB Design [TBA]
    [Items 7-8] Code and Software
    Don’t submit it in ICON; Demo it to TA / me; we will ask for code selectively
    Iterations – Deliverables
    Iteration #1: Screens, Db, Test plans, some data pull, over all architecture
    Deliver for the functions included in the iteration
    Iteration 2 (Full) – Both should be working software
    Suggestion: In each iteration, carry out steps 2-6. So incremental
    requirements will be given and agile experience can be provided.
    Due Dates flexible within semester constraints. To be discussed in class
    22C4400 – Database Systems Project – Initial 1/28/2019
    Project Scope
    Raman Aravamudhan RSA-22C4400-S19-PROJECT-SCOPE
    Department of Computer Science Page 5 of 5 Version 1.1
    For Project Meeting (Please be on time, don’t skip without prior approval)
    a. What you did this week, where you need help, problems faced etc.
    b. What you plan to complete next week
    Revision Log
    Date Version Description of change
    1/27/19 1.0 Initial
    1/28/19 1.1 Functional requirements listed
    WX：codehelp