PROJECT LIFE CYCLE - DEVELOPMENT PROCESS

Screen shot:

DEVELOPMENT PROCESS

2.1. PROJECT LIFE CYCLE

The Software Development Life Cycle (SDLC) is the process by which software is created. Some companies don't have anything more than an ad hoc approach to software development, but these environments still have an SDLC-it's just a bad one. Likewise, each company that has a formal SDLC probably has its own, unique flavor of the SDLC. Sometimes the SDLC is a very complicated, detailed approach that requires a whole team of project managers just to keep going. The lifecycle of a project may include the following steps:

By applying this simple set of definite steps and deliverables at the outset and relating this to a transparent time and cost structure, we provide clients with an effective framework against which to measure expectation, quality, progress and cost for their project.

2.2. DEVELOPMENT PROCESS

Waterfall Model

Planning the development process involves several important considerations. The first consideration is to define a product life-cycle model.A software LIFE- CYCLE model encompasses all activities required to define, test, and develop.

Design- v&v Implementation- v&v Requiremen t analysis- Testing- v&v Maintenance- v&v

FEASEBILITY STUDY

The main aim of feasibility study is to determine whether developing the product is financially and technically feasible .The feasibility study involves.

 An abstract definition of the problem.  Formation of different solution strategies.

 Examination of alternative solution strategies and their benefits, indicating resources required, developed, cost and time respect of each of the alternative solution. A cost effective analysis is performed to determine which solution is the best at this stage , it may also determine whether any of this solution is not feasible due to the high cost , resource constraint or extraordinary technically reason .

The module is totally feasible in all respect i.e. technically it reduces the time consuming and in economically it reduces the cost.

The feasibility aspect of the project was considered at the time of the negotiation with the officials and while discussing the same with the team.

FEASIBILITY ANALYSIS:

The advantage of computer based system is more likely to be plagued by a scarcity of resources and difficulty delivery dates. A feasibility study

 Security Feasibility  Operational Feasibility  Economical Feasibility  Technical Feasibility

SEQURITY FEASIBILITY:

The security of the database from being tampered from an unauthorized personnel different password fields were provided to different users. The password are validated and given in the front-end keeping its flexibility and user friendliness in view. As the concept goes usually the backend is not a frequently visited area that’s why we kept the access of passwords in jsp. As our project keeps, evaluates and relatives very important and confidential data about the diseases and it’s eradication program , it is very important that user should maintain their own individuality and identity so as one cannot overlap or interfere or even tamper the restricted fields.

OPERATIONAL FEASIBILITY:

People are inherently resistance to change and computers have been known to facilitate change. An estimate should be made of how strong a reaction the user staff is likely to have towards the development of a computerized system. It is common knowledge that computer installations have something to do with turnover, transfer retraining and change in job status.

The end users are eager enough to use the s/w. This would reieve them from physical labor and also financially to maintain various registers and paying a lot of staffs in the working office and depot.

The top level officials or the outsides can vital information quickly and correctly form our interpretation.

ECONOMICALLY FEASIBILITY:

Economically Feasibility is most frequently used for evaluating the effectiveness of equipment information system. More commonly known as cost benefit analysis, the procedure is to determine the benefits and saving that are expected from equipment information system and compare them with costs. If benefits outweigh costs, then the decision is made to design and implement the system, otherwise design and implement the system, otherwise further justification or alternation in the proposed system will have to be made if it is to have a chance of being approved.

Keeping in view the no. of clients who would be using this software that is the different places and locations, this project was developed keeping in view the lowest hardware capacity computer available during that time. As can be seen in our synopsis that we use p2 7 p3 computers the lowest available with the client having the following configuration.

 486 DX  60 MHz  1 GB HDD

The software was developed in JSP & Oracle8.0 because we opted for a front-end that will be very user friendly, web friendly and easier for the end user. This also helped the end user to a very large extent because usually the end user is just a data entry operator who knows the distinction between letter and number. Keeping this IQ level of the user into view this type of front-end was used for smooth operation.

TECHNICAL FEASIBILITY:

Technical Feasibility involves financial considerations to accommodate technical enhancement. If the budget is a serious constraint then the project is judged ‘not feasible’.

Here the cost incurred by searching an appropriate s/w which may handle by some few people and hidden to others, but it reduces the searching time, so it technically fit.

The module reduce the work load of different end user , and gives a clear picture about the s/w required so the user use this module , hence this system is operationally feasible .

As this page is technically, economically sequritically and operationally feasible, so this system is judged feasible.

Hardware Feasibility

For develop this project or implement this project we need different types of hardware configuration for server and client. If we will use different type of hardware’s then it may not work properly.

FOR SERVER

Machine: Pentium IV Server Memory: 256 MB DDRAM Hard Drive: 40 GB HDD or Higher CPU Speed: 2.0Ghz Monitor: S.V.G.A Keyboard: Standard Printer: Laser UPS: 5KVA For client

Machine: Pentium IV Client Memory: 128 MB DDRAM Hard Drive: 10 GB HDD or Higher CPU Speed: 1.0Ghz

Monitor: S.V.G.A

Software Feasibility

Using different types of software, which have listed below so these software’s also need for implement this project, developed this project. If we will use different types of software then this project will not work.

Operating System: WINDOWS 98, 2000, Xp,2007 Front-end Tool: SERVLET, JSP, STRUTS Back-end Tool: SQL SERVER

Server: Tomcat 6.0, WBLOGIC

Economical Feasibility

As soon as the specific requirements and solutions have been identified then the cost of and benefits of each alternative would be evaluated.

Cost Of Estimation Of the Project

The cost of the major hardware, software and accessories required for this project are 20 lakhs.

Requirement Analysis and Specification

Before starting to design a software product, it is extremely important to understand the precise requirements of the customer and to document them properly. The requirements analysis and specifications phase starts once the feasibility study phase is complete and the project is found to be financially sound and technically feasible, the goal of the requirements analysis and specifications phase is to clearly understand the customer requirements and to systematically organize these requirements in a specification document, this phase consists of the following two activities:

 Requirements gathering analysis  Requirements specification

Requirements gathering analysis

We can elaborate the two main activities involved in the requirements gathering and analysis phase:

Requirements gathering.

This activity typically involves interviewing the end-users and customers and studying the existing documents to collect all possible information regarding the system. If the project involves automating some existing procedures then the task of the system analyst becomes a little easier as he can obtain the input and the output data formats and the details of the nation and creativity on the part of the system analyst is required.

Analysis of gathered requirements.

The main purpose to this activity is to clearly understand the exact requirements of the customer. The following basic questions pertaining to the project should be clearly understood by the analyst in order to obtain a good grasp of the problem:

 What is the problem?

 Why is it important to solve the problem?  What are the possible solutions to the problem?

 What exactly are the data inputs to the system and what exactly are the data outputs required of the system?

 What are the likely complexities that might arise while solving the problem?

 If there are external software or hardware with which the developed software has to interface, then what exactly would the data interchange formats with the external system.

Software Requirements Specification (SRS).

After the analyst has collected all the required information regarding the software to be developed, and has removed all incompleteness, inconsistencies, and anomalies from the specification, he starts to systematically organize the requirements n the form of an SRS document. The SRS document usually contains all the user requirements in an informal form.

Contents of the SRS Document

An SRS document should clearly document the following aspects of a system:

 Functional requirements  Nonfunctional requirements  Goals of implementation

The functional requirements part should discuss the functionalities required from the system. It is useful to consider a system as performing a set of functions {f1}. This functional view of a system is shown schematically in figure.

y System

Output

aspects also include reliability issues, accuracy of results, human-computer interface issues, and constraints on the system implementation.

The ‘goals of implementation’ part of the SRS document gives some general

suggestions regarding development. These suggestion guide trade-off among design decisions.

DESIGN

Software design deals with transforming the customer requirements, as described in the SRS document, into a form that is implement able using a programming language, for a design to be easily implement able using a programming language, the following items must be designed during the design phase:

 Different modules required implementing the design solution.

 Control relationship among the identified modules. The relationship is also known as the call relationship or invocation relationship among modules.

 Data structures of the individual modules .

 Algorithms required implementing the individual modules. System design

System design consists of the flow of control among different modules and the approach i.e. function-oriented approach of object-oriented approach is used.

In our project we have used function-oriented approach. The commonly used data flow control (DFD).

6.Coding

Web.xml <?xml version="1.0" encoding="UTF-8"?> <web-app xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" version="2.4" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd"> <servlet> <servlet-name>action</servlet-name> <servlet- class>org.apache.struts.action.ActionServlet</servlet- class> <init-param> <param-name>config</param-name> <param-value>/WEB-INF/struts-config.xml</param- value> </init-param> <init-param> <param-name>debug</param-name> <param-value>3</param-value> </init-param> <init-param> <param-name>detail</param-name> <param-value>3</param-value> </init-param> <load-on-startup>0</load-on-startup> </servlet> <servlet-mapping> <servlet-name>action</servlet-name> <url-pattern>*.do</url-pattern>

Struts-config.xml

<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE struts-config PUBLIC "-//Apache Software Foundation//DTD Struts Configuration 1.2//EN"

"http://struts.apache.org/dtds/struts-config_1_2.dtd"> <struts-config>

<data-sources /> <form-beans >

<form-bean name="loginForm" type="pp.form.LoginForm" /> </form-beans> <global-exceptions /> <global-forwards /> <action-mappings > <action attribute="loginForm" name="loginForm" parameter="submit" path="/login" scope="request" type="pp.action.LoginAction">

<forward name="admin" path="/AdminHome.jsp"/> <forward name="customer" path="/UserHome.jsp"/> <forward name="view" path="/FlightManagment.jsp"/> <forward name="flight"

path="/FlightManagment.jsp"/>

<forward name="cpwd" path="/ChangePassword.jsp"/> <forward name="fview" path="/View Flight.jsp"/> <forward name="mbook" path="/MyBooking.jsp"/> <forward name="cancel" path="/Cancellation.jsp"/> <forward name="feed1" path="/GiveFeedback.jsp"/> <forward name="vannoun"

path="/ViewAnnouncement.jsp"/>

<forward name="dnotice" path="/DeleteNotice.jsp"/> <forward name="subError"

path="/Registration.jsp" />

<forward name="logon" path="/Login.jsp" /> <forward name="logout" path="/UserHome.jsp" /> </action> </action-mappings> <message-resources parameter="pp.ApplicationResources" /> </struts-config> Home.jsp

<%@ page language="java" pageEncoding="ISO-8859-1"%> <%@ taglib uri="http://struts.apache.org/tags-bean" prefix="bean" %> <%@ taglib uri="http://struts.apache.org/tags-html" prefix="html" %> <%@ taglib uri="http://struts.apache.org/tags-logic" prefix="logic" %> <%@ taglib uri="http://struts.apache.org/tags-tiles" prefix="tiles" %>

<!--

Design by Free CSS Templates http://www.freecsstemplates.org

Released for free under a Creative Commons Attribution 2.5 License

Name : Professional

Description: A two-column, fixed-width design with dark color scheme background.

Version : 1.0

Released : 20081230 -->

<title>Professional by FreeCSSTemplates.org</title>

<h1>Air Ticket Reservation</h1> <p>Fly In Cooooooooollllllllllllll...</p> </div>  <div id="menu"> <ul> <li class="active"><a href="Home.jsp">Home</a></li>

<li><a href="AboutUs.jsp">About Us</a></li> <li><a href="ContactUs.jsp">Contact Us</a></li> </ul> </div>  </div>

<div id="page"> <div id="header-pic"></div> <div id="content"> <div class="post"> <h1 class="title"><h2>Welcome To Home Page...</h2> </h1> <p class="byline"> <div class="entry"> </div> <div class="meta"> <p class="links">

Welcome aboard RK Airlines, where you are made to feel like an honoured guest and not just a

passenger. At RK, a flight is not a journey between two airports but an experience of a lifetime.RK is built for people with things to do, places to be, people to see - who don't want to waste time, money or energy in the process. By minimizing the cost/time/tension of air travel, RK opens up a country full of opportunities. With RK, you've got a billion reasons to fly</div>    </div> <div class="post"> <p class="byline"> <div class="entry"> </div> <div class="meta"> </div> </div> </div>  <div id="sidebar">

<li><a

href="Login.jsp">Login<br /></a></li> <li><a

href="Registration.jsp">New User<br /></a></li> </ul> </li> <li> <ul> </li> </ul> </div> </div> </div>

Login.jsp

Design by Free CSS Templates http://www.freecsstemplates.org

Released for free under a Creative Commons Attribution 2.5 License

Name : Professional

Description: A two-column, fixed-width design with dark color scheme background.

Version : 1.0

Released : 20081230 -->

var pwd=frm.pwd.value; if(uname.length==0) { alert("Enter ur UserName"); frm.uname.focus(); return false; } if(pwd.length==0) { alert("Enter ur Password"); frm.pwd.focus(); return false; } return true; } </script> </head> <body> <div id="wrapper"> <div id="header"> <div id="logo">

<h1>Air Ticket Reservation</h1> <p>Fly In Cooooooooollllllllllllll...</p> </div>  <div id="menu"> <ul> <li class="active"><a href="Home.jsp">Home</a></li>

<li><a href="AboutUs.jsp">About Us</a></li> <li><a href="ContactUs.jsp">Contact Us</a></li> </ul> </div>  </div>  <div id="page">

In document AIRLINE RESERVATION SYSYTEM (Page 76-124)