1.

Airline Reservation System

Objective : our project is to design and develop a software which would automate
the major airline operations like providing the facilities for the reservation of online air
tickets or any other operations through an effective and yet simple GUI for a normal
passenger intending to travel through airways.

PROPOSED RESERVATION SYSTEM: This Airline Reservation System Project will

provide the user with the following functions: Flight Booking System: The system
allows the airline passenger to search for flights that are available between the two
travel cities, namely the Departure city and Arrival city for a particular departure
date. The system gives the list of available flights with certain flight details and allows
customer to choose a particular flight suiting his comforts. If the seats are available
in a particular flight, then the system allows the passenger to book a seat of his/her
choice. Otherwise it asks the user to choose another flight. He can also cancel the
current reservations without any problem. Flight Status System: Our system allows
the registered users to check the flight status if there is any delay in their flight
timings due to inclement weather or any other reason. It automatically notifies by
sending a voice message to the authorised passengers who have their tickets
booked.
PROCESS MODEL We have used LINEAR SEQUENTIAL MODEL or WATERFALL
MODEL for our system which is a software development model in which
development is seen as flowing steadily downwards (like a waterfall) through the
phases of requirements analysis, design, implementation, testing .

WATERFALL MODEL:
HARDWARE INTERFACES : Our software is compatible with Microsoft Windows
based machines.
The database connectivity requires a hardware configuration with a fast database
system running on hard-disk permitting back-up systems to support the primary goal
of reliability.
The system must interface with the standard output device, keyboard and mouse to
interact with the software.

FRONT END DESCRIPTION :-

The Front End for ARS is designed using HTML.
The front end contains a very user-friendly interface.
It contains various screens such as
1. Login
2. Registration
3. Online Reservation
4. Reservation Form
5. Online Transaction
6. Flight Status
7. Web Check-In
8. Cancel Reservation

BACK END DESCRIPTION

The Back End for ARS is designed using MS Access. This includes passenger,
reservation, flights, flight status, account info, web check-in, payment and
cancellation relations.
The account info relation contains the information of the users like its valid
username and password, first name, last name, email-id, contact no and gender.
The passenger relation will contain unique e-ticket number, first name, last name,
gender, D.O.B, seat no, flight no, departure date, e-contact no, booking username.
The flights relation contains the information about all the flights available between
different cities such as flight number, the two cities to which the flight connects i.e.
the origin and destination, total seats and the days on which it flies.

2. BANKING SYSTEM
Requirements:
Administrator can check A/Cs with a login & password & can work out with
A/C holders of the bank can withdraw/deposit cash/cheque/DD to/from their
accounts. To enable faster transactions like

New account creation.

Withdrawal of cash
Deposits of cash or cheque
Checking of Account balances by account holders by admin
Transaction records in the form of reports.

The project makes a sincere effort to provide all the above-mentioned features
to meet the requirements of the bank .The Project category is Visual Basic with
RDBMS (Access) &Management information System.

Tool(s) / Language(s) to be used:-

The Graphical interface (Front End) of the application is prepared by the usage
of Visual Basic. Coding for the validation is provided through the use of Visual
Basic 6.0.
The back end of the application is maintained in Microsoft Access .Information
Source is Management Information System

HARDWARE REQUIREMENT
Hardware is referred to as computing potential .In this project, three hardware
categories have been considered during software planning.
DEVELOPMENT SYSTEM , which is a computer and related peripherals that
will be used during the software development phase. The development system
has been used because it can accommodate multiple users, maintain large
volumes of information and support a rich assortment of software tools.
TARGET MACHINE on which the software will eventual is executed.
SYSTEM SPECIFICATION
Software Specification
OPERATING SYSTEM WINDOWS
NT/2000/XP/2003/Vista/7
BACK END MS ACCESS XP
FRONT END VISUAL BASIC

System Development Life cycle

The structured sequence of operation required imaging developing and Making
operational a new information system its a cycle because the System will need
replacement and Development, cycle will begin.
Phases of SDLC
System Analysis
System Design
Coding
System Testing
System Implementation
System Maintenance

Feasibility Consideration
There were three key consideration involved in this feasibility analysis each
consideration has reviewed to depict how it relates to the system effort .They
are as follows:-
Economic feasibility
Technical feasibility
Operational feasibility

Water fall life cycle model:

Definition:
It is systematic, disciplined and sequential approach to software development
that begins at system level and process through, analysis, design, code, and test

Waterfall life cycle mode Design:

It is multistep process it will focus on 4 fields
Data structure
Architecture
Interface
Algorithm
 3. HEALTH CARE-SE
REQUIREMENTS GATHERING AND ANALYSIS :We start designing our project
system by gathering the facts and requirements about a generic patient entity
first. From a software engineering perspective, a patient record differentiated
by a unique patient id (for this, SSN is used), address, contact phone number,
date of birth, gender, blood type, and a special field to add remarks about the
patient. As for the manipulation of a patient health data, three roles are
defined: a physician, a nurse, and a staff member. A physician can add, modify,
or delete his treatment records for a patient. He/she can view the complete
treatment records of the patients assigned to him/her. The patient health data
should also be manipulated by a nurse, though with lesser rights granted this
time. Namely, a nurse should be able to add health related treatment record
for a patient. A nurse should also be able to browse the visit history of a
patient in a restricted way, which means that a nurse cannot view the detailed
treatment records of physician(s) about a patient. The third role owner, i.e. a
staff date and time, and the cost of visit. The staff should also be able to track
patient wait time, and assign an appropriate and available healthcare provider
to the patient. In addition to the three roles defined above, the system also
introduces an admin role, who is responsible for defining roles, assigning users
to these roles and managing role granting and revocation on a dynamic basis
(as physicians/nurses/staff can be hired, or may leave the job, etc.)

DESIGN after initial gathering of facts and requirements, the collected data is
further analyzed to formally define the database tables, fields of each table,
primary and foreign key assignments, relationship and functional dependency
definitions. To exercise the design phase of the formal software engineering
approach, we combine it with the formal database design step.

WATERFALL APPROACH:
Phases of SDLC
System Analysis
System Design
Coding
System Testing
System Implementation
System Maintenance

SOFTWARE REQUIREMENT:
Data bases
Servers and Clouds
Mysql installed WINDOWS PCs.
 4.EDUCATION-SE
Educational Aspects: Users of educational software should focus on their
learning, not on how to operate the computer. For this to happen, the
software needs to be designed from clear educational principles and
considerations. The basic steps in designing educational software are as
follows: Define the educational aims and objectives. What area of the
curriculum and topics will be covered? What is the purpose and level of the
learning (e.g., to introduce a topic, to explore a topic in more depth, to revise
for exams)? Identify the learning needs. What topics are hard to learn? What
misunderstandings need to be addressed? Do the learners need to acquire
knowledge, or learn skills? Decide which needs could be addressed by
computer. Is the topic difficult to visualise (e.g., needing a microscope)? Does it
relate concrete activities to abstract concepts (e.g. understanding a food web)?
Does is involve constructing and linking diverse material (e.g. exploring the
causes of the Civil War)? Does it require access to many sources of information
(e.g. exploring a population census)? Does is require controlled interactions
between dynamic objects (e.g. dynamic physics experiments)? Could it be
helped by communication or collaboration between distant learners (e.g.
learning a foreign language or culture)? All these could be suited to computer-
mediated learning. Determine the general teaching and learning approach. See
below.

Design and test the software: The larger the project, the more important it is
to take a structured approach to design, testing and implementation.
Whatever the scale, it is essential to produce a clear set of requirements, to
consult users (teachers and learners) during the design, and to verify (is it free
of bugs, robust and usable?) and validate (does it meet the requirements?) the
software.
 Evaluate the entire system: An evaluation can be formative (to identify
problems and suggest improvements) or summative (to assess the quality of
the system or to compare it against competing software or teaching methods).
The evaluation should assess the complete learning system, including
documentation and the contribution of a teacher and other learners, for
usability, usefulness, and desirability.

Teaching and Learning Approach :There are some general approaches to

classroom teaching and learning that are reflected in the design of educational
software. At their most basic, they can be described in terms of oppositions.
Dimensions of teaching and learning

Teacher directed: the software is designed to be used in a classroom under the

control of a teacher.

Learner directed: the software is designed to be used without direct teacher

supervision.

Individual: the software is intended for a single learner working alone.

Collaborative: the software is designed to support pairs or groups of learners.

Instructional: the software provides direct teaching of a piece of knowledge of
skill.

Discovery: the software is designed for learners to explore concepts, discover

knowledge or practise skills.

The dimensions are separate (a software package or website could, for

example support teacher directed, collaborative, discovery-type learning). Each
component of the software package will lie somewhere between the two ends
of the scale, and the design should make clear how the learning should be
carried out. For example, a learner-directed, collaborative, discovery system
should provide clear instructions on what other resources and equipment the
learners might need, what they should prepare before using the program, how
they should collaborate (e.g. taking turns at the keyboard), and what general
kinds of discoveries they might make. The more teacher-directed, individual,
and instructional the system, the more these instructions can be embedded in
the teaching. Teacher-directed Learner-directed Individual Instructional
Discovery Collaborative

Teacher-directed <--------------------->Learner-directed

Individual <--------------------->Collaborative

Instructional <--------------------->Discovery

WATERFALL MODEL USED FOR DESIGNING:

SOFTWARE REQUIREMENTS:

Android development platform

Windows/Linux PC

Servers & Cloud Technology

 5.RETAIL STORES & MANAGEMENT SE

Identify concrete project goals:

Your project goals shouldnt be vague. We want to increase revenue is
effectively meaningless in terms of actionable plans. Think about
specific, clear goals that can drive concrete strategy. We want to open a
new location in an area with higher foot traffic is better. But even more
specific is best: In the next five years, we want to open three new
locations in the tri-city area to better serve our urban customers who
dont own cars. We hope to improve conversions from window shoppers
by 10 percent.

Project managers in the digital space know their key performance

indicators (KPIs) before they begin, and you should too. The statistics
arent that different when you boil them down: Click-through rates are
people who decide to enter your store; time spent on page is time spent
browsing merchandise; a conversion rate is a conversion rate whether
youre talking online or brick-and-mortar.

Know your goals and KPIs before you begin the project. This will give your
work a more laser-tight focus and help you evaluate the project after its
done. Where did you match your expectations, over perform, or fall short?
You need to have solid goals in mind before you begin to really understand
how you performed.

Break projects down into phases:

Henry Ford once said, Nothing is particularly hard when you divide it into
small jobs. Experienced managers break projects down into the
five key phases of project management:-
1. Initiation
2. Planning
3. Execution
4. Performance/Monitoring
5. Closure
Consider how these five phases might apply to a store remodel. In the
initiation stage, you explore the feasibility. How much might it cost,
including lost opportunity while the store is renovating? How long will it
take you to recoup your investment? Once given the green light, you
begin the planning stage. The new store layout is designed. Bids
solicited and contractors hired. Proper paperwork is filed.

In the execution stage, the store closes for renovations, employees are
reassigned elsewhere, and the hands-on work gets done. Performance
and monitoring begins after the store reopens. This is when you assess
how successful the project was in hitting your KPIs and evaluate your
accomplishments. The closure stage is where everything is wrapped up
and contractors are paid. You can then apply what you learned in the
fourth stage to future projects.

Set clear timelines for any project, from renovation to hiring. Use Gantt
charts to get an accurate picture of when things need to be
accomplished. Break your big projects down into small parts, and youll
increase your likelihood of success.

Take advantage of modern technology and the cloud:

Just because youre working in the world of brick and mortar doesnt mean
planning has to be. The world of retail is becoming increasingly reliant on
the proper use of big data and the power of the cloud. There are powerful
tools out there, and you should use them.

For instance, when managing the high-paced frenzy of the holiday

shopping season, maintain your employees schedules on an easily
shareable Google document rather than a printed calendar. This
provides greater flexibility and can be updated with last minute changes.
Your employees will appreciate the ease of checking their hours without
having to come in. Similarly management charts,use resources to have
a better idea of what youre allocating and where.
Retailers are storing more and more data about their customers
shopping habits. Take advantage of this data to predict what your
customers purchase together and arrange your items accordingly. This
data comes full circle in helping you set future goals and KPIs.

MODELS THAT CAN BE USED:

As we might know we can use WATERFALL MODEL for small range

projects.

SOFTWARE REQUIREMENTS:

Android development platform

Window/Linux PCs

Cloud & Server connections