You are on page 1of 69


2. System Analysis
2.1. Software Requirement Specification (SRS)
What is SRS?
Software Requirement Specification (SRS) is the starting point of the software
developing activity. As system grew more complex, it became evident that the goal
of the entire system cannot

be easily comprehended. Hence the need for the

requirement phase arose. The software project us initiated by the client needs. The

SRS is the means of translating the ideas of the minds of clients (the input) into a
formal document (the output of the requirement phase.)
The SRS phase consists of two basic activities:
1) Problem/Requirement Analysis:
The process is order and more nebuious of the two, deals with
understand the problem, the goal and constraints.
2) Requirement Specification:
Here, the focus is on specifying what has been found giving analysis
such as representation, specification languages and tools, and checking
the specifications are addressed during this activity.
The requirement phase terminates with the production of the validate SRS
document. Producing the SRS document is the basic goal of this phase.

Role of SRS
The purpose of the Software Requirement Specification is to reduce the
communication gap between the clients and the developers. Software Requirement
Specification is the medium through which the client and user needs are accurately
specified. It forms the basis of software development. A good SRS should satisfy
all the parties involved in the system.

The purpose of this document is to describe all external requirements for mobile
task manager. It also describes the interfaces for the system.

Existing System

The existing system for Stores Management System activities uses open source
standard & technologies. It had been developed on WINDOWS 2000
PROFESSIONAL platform with ‘POSTGRESQL’ database. All the stores of the

The ‘Stores Management System package’ is targeted to automate the almost all of the processes mentioned above to reduce the clerical labour of the staff working in Stores both technical and as well as Accounts departments using the software Industry’s latest technologies and cost effective tools there by providing the better control to the management by avoiding manual errors etc. .power distribution company limited are made through the open source standards & technologies.. Other Commercial activities like hiring equipment etc. 1.. Capital works 2. Stores are required for the following purposes. Operation and Maintenances Works 3. The user interaction is in GUI (Graphical User Interface) mode.

The three tests of feasibility have been carried out: 2. and a host of SUN FIRE 6800 servers.1. The Organization already possesses Windows 2000 Professional Operating System. Hence the solution is technically feasible.1. hence there is 0 additional cost incurred for the tools that will be used.2. Operational Feasibility 2. one has to test whether the proposed system can be developed using existing technology or not. Economical Feasibility As part of this. Technical Feasibility 2. It is evident that the necessary hardware and software are available for the development and implementation of the proposed system. Economical Feasibility 2. Operational Feasibility: . It is planned to implement the proposed system using Windows 2000 Professional. The Organization has already its own satellite link. So it need not invest newly for the internet connection and also the organization initiated to use Open Source in project development. Feasibility Study The existing system is clearly understood the next step is to conduct the feasibility study. Technical Feasibility In technical feasibility study. the costs and benefits associated with the proposed system are to be compared and the project is economically feasible only if benefits outweigh costs.4.4.4. which is a high level capsule version of the entire System Analysis and Design process.3.4. JSP and Apache Tomcat Wed Server. The objective is to determine whether the proposed system is feasible.4. 2.4.3.

The technical staff has sufficient knowledge of the tools being used and the users need just to know how to access and run the programs in the Apache Web Sever. .This test of feasibility checks if the system works with least difficulties when it is developed and installed. Hence it is concluded that the system is operationally feasible.

NET Framework programming environment for devices.  Security in the .NET Framework. Technologies and Features  Provides a quick reference to the major technology areas of the .NET Framework class library. The documentation listed below is located in the "Development Tools and Languages" section of the MSDN Library.NET Compact Framework. and threading. . PLATFORM/LANGUAGES USED Understanding .NET Framework applications: .NET Framework.  . and cross-language interoperability.NET Framework.TOOLS. COM interlope.NET Framework programming such as garbage collection. Contains links to information on the .  Provides information about other technology areas in . Provides information on the . the class library.NET Framework applications are built on the services of the common language runtime and take advantage of the .  Provides conceptual overviews of the . including the common language runtime.NET Framework classes and services that enable secure application development.

 Assemblies in the Common Language Runtime. and security permissions. Assemblies are the fundamental units of deployment.. Defines the concept of assemblies. version control. activation scoping. into all modules and assemblies. a run-time environment that manages the execution of code and provides services that simplify the development process.NET Framework Conceptual Overview  Common Language Runtime explains the features and benefits of the common language runtime. which are collections of types and resources that form logical units of functionality. reuse.  Metadata and Self-Describing Components explain how the .NET Framework simplifies component interoperation by allowing compilers to emit additional declarative information. Programming with Components: . or metadata.  Cross-Language Interoperability.  Common Type System identifies the types supported by the common language runtime.

If you want your components and controls to be usable from other programming languages. For more information about the CLS. The default base class implementation of the IComponent interface is System. This section defines what a component is and provides an overview of .NET Framework a component is a class that implements the System.NET Framework programming concepts that are especially relevant to component programming. you must author them in a Common Language Specification (CLS)compliant language and ensure that all public and protected members are CLScompliant. Server-based Components for .ComponentModel. and how to assemble them from the sophisticated components in the .NET Framework includes classes for several server-based components that you can put into your applications. The Windows Software Development Kit (SDK) provides compilers for four CLS-compliant languages: Visual Basic. C#.IComponent interface or one that derives directly or indirectly from a class that implements this interface. While the term component has many meanings. The following sections explain how to create your own components. see Common Language Specification.Component.The designer architecture in Visual Studio lets you assemble non-visual component classes as easily as you assemble Visual Basic forms.ComponentModel. and J#. C++. .NET Framework classes.NET Framework Applications The . in the .

Using Installation Components . Using System Monitoring Components. you can click the View menu and then click Solution Explorer to open it. The files are displayed in a hierarchical view.Introduces installation components.Using File System and Timer Components .Introduces components that respond to changes to files and directories. If Solution Explorer is not visible. much like that of Windows Explorer.Introduces components that interact with Windows performance counters and event logs. Understanding VB-2010IDE: Using Solution Explorer – Solution Explorer is an area of the integrated development environment (IDE) that contains your solution and helps you manage your project files. which allow you to execute custom actions when your application is deployed. Solution Explorer is located on the right side of the IDE. . raise events on a schedule. By default. or monitor and interact with Windows processes. Using Messaging Components .Introduces components that interact with Microsoft Message Queuing system resources.

You can view this file in Design view.vb node is the Windows Form in your solution. You can also view this file in the Code Editor. which enables you to see the form and any controls that you have added to it. settings. For more information. The solution contains two nodes: My Project and Form1. which enables you to see the code associated with the application you're creating.vb. and resources. The Form1. see Introduction to the Project Designer. a Windows Application solution appears in Solution Explorer.When you create a new Windows Forms application by using Visual Basic Express Edition. The My Project node opens the Project Designer when you double-click it. . The Project Designer gives you access to project properties. as the following diagram illustrates.

and then click Toolbox to display it. Common controls in the Toolbox You can set the Toolbox to automatically hide when you're not using it. fields for entering text. These types of Visual Basic programs are known as Windows Forms applications. the Toolbox is located on the left side of the integrated development environment (IDE). you can drag them directly from the Toolbox to the form. and several controls. By default.Toolbox – The Toolbox is a container for all the controls that you can add to a Windows Forms application or a Windows Presentation Foundation (WPF) application. or you can set the Toolbox to always be visible in the IDE. you can click the View menu. If the Toolbox is not visible. The following illustration shows the common controls in the Toolbox. To add controls to your application. This makes it easier for you to see all the controls while you create your application. A user interface usually consists of a main window or form. Introduction to Windows Forms – The user interface is the part of your program that users see when they run the program. The controls are not visible on the Toolbox when you are in the Code Editor. and the user interface is created using Windows Forms controls. such as buttons. Toolbox Component – . and so forth.

many programs have Exit buttons. controls run code in response to those events. and this text is displayed in the font or typeface determined by the Font property. You can write code that should run when the user clicks the button by creating an event handler. Labels and Text Boxes – One of the easiest ways to communicate information to and receive it from users is through text. When the user clicks a button at run time. When an event occurs. and you can receive data as text from the user and use it in your program. the Button raises the Click event. For example. The Button control also has predefined events that can be used to initiate actions such as ending a program. the button's Click event has an event handler. You can display text about a program's functionality. Visual . that can be set to change their appearance. Buttons are. When a user clicks a button. There are many properties. and the ForeColor property determines the text's color. the Button control in Visual Basic looks and behaves like a push button. generally. The most obvious is the Text property. As you saw in the previous lesson. however.Buttons – The easiest way for users to interact with your program is through buttons. which determines the text displayed. The BackColor property determines the button's color. An event handler is a method that executes when an event occurs. rectangular controls with a raised appearance on the form.

They are the Label and Textbox controls. it appears as if it is just text on the form. The color of this area is usually the same as the color of the form. . The ForeColor property determines the color of the text itself. and the BackColor property determines the color of the area surrounding the text.Basic provides two controls that are designed for displaying and receiving text. The Font property determines the display font for the text in the Text property. Therefore. The Label control is the primary control for displaying text. Because a Label is primarily meant to display text. the most important properties for a Label control are the properties that control its appearance. It appears on the form as text enclosed in a rectangular-shaped area. The Text property contains the text that is displayed in the Label control.

but not both. the check mark is removed." You can use groups of RadioButton controls to enable users to choose between exclusive options. If the box is clicked again. "Here is a set of choices from which you can choose one and only one. Like a CheckBoxcontrol. you might allow users to choose either regular sauce or spicy sauce on their pizza. Selecting one radio button immediately clears all the other radio buttons in the group. When the user clicks the box. the property returns False. Defining a group of radio buttons tells the user. the property returns True. Creating Menus – Menus are an easy and familiar way for users to make choices regarding your program. a check mark appears in the box. Common uses for menus include exposing program .Checked property. The status of the check box can be retrieved by using the CheckBox. Unlike check boxes.Check Boxes and Radio Buttons – The CheckBox control consists of a text label and a box that the user can select. radio buttons (also known as option buttons) always work as part of a group. If the box displays a check mark. For example. you can get information about the status of the RadioButton control from the RadioButton. If no check is displayed.Checked property.

as the following illustration shows. When the title for one menu item is set. By default." located in the upper part of the form. the combo box appears as a text box. When a user selects an item. but when users click the drop-down arrow. enabling users to scroll through a longer list. adding shortcuts for common tasks such as cut and paste. A ListBox control lets you display several items at the same time. it becomes highlighted in the list. You can click the box and type inside it to create the menu titles. or loading and saving files. you can display the list of items in a ListBox control or a ComboBox control. Visual Basic makes it easy to implement menus. ListBox and ComboBox Controls – When you want to give users a list of choices. When the look of your menu is complete. additional menu items can be created underneath and to the right of the first. the MenuStrip control appears as a box that contains the words "Type Here. This allows you to extend the menu with as many additional items or sub-items as you want. When a user selects an item. it becomes highlighted and is visible in the default view.options. A ComboBox control is a combination of a text box and a list box. as the following illustration shows. you can create event handlers to handle the Click events for each item. . a list appears. You can use the MenuStrip control to create menus graphically. When dragged onto a form.

NET & VC# SQL Server 2005 Minimum Hardware Required: Processor RAM HDD Pentium 4 or above 256 MB 20 GB Monitor SVGA color monitor and keyboard Software Required: Microsoft Visual Studio 2005 Microsoft SQL Server 2005 .The processes for adding items to list boxes and combo boxes are similar. Hardware & Software Requirement Hardware Used: Processor RAM HDD Monitor Software Used: Front-end: Back-end: Intel Celeron 1 GB 60 GB SVGA color monitor and keyboard ADO. You can use the Add method of the ListBox control and the Add method of the ComboBox control to add items.

Class Fee .DATABASE DESIGN Admin Login: FIELDS DATATYPE DESCRIPTION UserName VARCHAR (15) Stores administrator`s login id. Password VARCHAR (15) Stores User password. Password VARCHAR (15) Stores administrator`s password. User Login: FIELDS DATATYPE DESCRIPTION UserName VARCHAR (15) Stores User login id.

FIELDS DATATYPE DESCRIPTION Class Int . Employee_Details: FIELDS DATATYPE DESCRIPTION Id (pk) Int StoresEmployeeid Empid (Computed) Varchar (7) StoresEmployeeid EmpName Varchar (23) StoresEmployeeName FatherName Varchar (25) StoresEmployeeFatherName Qualification Varchar (15) StoresEmployee qualification BirthDate DateTime StoresEmployeeDateofBirth Department Varchar (10) Stores the Department of Employee Subject Varchar (10) Stores the Subject of Employee MartialStatus Varchar (15) StoresEmployee Martial Status (Married. JoiningDate DateTime Stores the joining Date Photo Image. Null Stores the Salary of Employee . BaseFee Money . Null Stores the photo of Employee Basic_Salary Money. Unmarried) Gender Varchar (6) Stores the Gender of Employee ContactNo Varchar (13) Stores the Employee ContactNo. NOT NULL Stores the Base Fee of Class. Address Varchar (26) Stores Employee Address. NOT NULL Stores Class.

Store the Name of Student Store the Father Name Of Student Store the Mother Name of Student Store The Date Of Birth Store the Gender Address Varchar(40) Store the Address ContactNo Varchr(10) Store the ContactNo Qualification Varchar(15) Store the Qualification AdmissionClass Int DateOfAdmission DateTime Photo Image Store the Admission In Class He/she Admitted Store the AdmissionDate Stores the Photo Enquiry:FIELDS DATATYPE DESCRIPTION StudentName Varchar(25) Store the Name of Student .Student_Details: FIELDS DATATYPE DESCRIPTION Id(pk) Int Store the Studentid RegNo Varchar(7) Name Varchar(25) FatherName Varchar(25) MotherName Varchar(25) DOB DateTime Gender Varchar(6) Store the Student Reg NO.

Fee_Plan FIELDS RegNo(pk) Name Class Annual_Charge Month LateFee Fee ExtraCharge Total Date Region DATATYPE VARCHAR(5) VARCHAR(20) VARCHAR(6) Money VARCHAR(12) Money Money Money Money datetime Varchar(40) DESCRIPTION Stores RegNo. Stores the Name of Students Stores the Class. Stores the Annual_Charge Stores Month Stores LateFee Stores MonthlyFee Stores The ExtraCharge Show the Total fee Of student Stores the date of receiving fee Contains the Cause of extra fee .FatherName MotherName Varchar(25) Varchar(25) Gender DOB Address Varchar(6) DateTime Varchar(30) Course Qualification Varchar(20) Varchar(12) Date ContactNo DateTime Varchar(10) Store the Father Name Store the Mother Name of Student Stores the Gender Store the Birth Date Store the Address of Student Store the Course Store the qualification of Student Date of Enquiry Stores the Contact No.


The deliverables act as milestones against which we can judge the progress and continuing viability of the project. . In the past. known as phases. and because those projects that did satisfy user requirements were being developed over-budget or over time. a conscious decision is made to continue development of the project. An important component of the AIRFORCE SCHOOL MANAGEMENT SYSTEM is that at each phase. The AIRFORCE SCHOOL MANAGEMENT SYSTEM is a methodology that has been constructed to ensure that systems are designed and implemented in a methodical. projects developed without the guidance of the AIRFORCE SCHOOL MANAGEMENT SYSTEM were continued well after 'common sense' dictated that it made no sense to proceed further. logical and step-by-step approach. or to drop it. are used in the project entitled “Airforce school management system”:  The Analysis Phase  The Design Phase  The Development Phase  The Implementation Phase  The Test phase  The Installation and checkout phase Each phase of the AIRFORCE SCHOOL MANAGEMENT SYSTEM creates a tangible product or deliverable.Airforce school management system The software ‘Airforce school management system’ was developed because many computer systems were delivered which did not satisfy user requirements. There are six steps.

Programmers who do so may find themselves going back to modify pieces of code they've already written as they move through the project. It can easily form the basis of a contract between the customer and the developer. we'll examine each phase in turn. or it could take months. this phase could be as short as the Preliminary Investigation. The Requirements Statement should list all of the major details of the program. Skipping parts of the AIRFORCE SCHOOL MANAGEMENT SYSTEM can be a big mistake. but remember that the value of the process is that it forces you to follow a standardized methodology for developing programs and systems. the Requirements Statement should be in development: this provides details about what the program should do. At the end of phase 1. Phases Implemented to complete the project Phase1: Analysis In the Analysis Phase. The AIRFORCE SCHOOL MANAGEMENT SYSTEM dictates that Phase 1 should be completed before any actual writing of the program begins. It is surprising to find out how much additional information can be gleaned from spending just a little more time with the user. With a . (sometimes called the Data Gathering Phase) we study the problem. To understand the structure and working of the AIRFORCE SCHOOL MANAGEMENT SYSTEM. deficiency or new requirement in detail. Depending upon the size of the project being undertaken.You might be inclined to skip portions of what the AIRFORCE SCHOOL MANAGEMENT SYSTEM calls for. Phase 2: Design The exceptional programmer might begin coding without a good design. whereas adhering to it ensures that you give the project the greatest chance for success.

we would hope to have a formal Requirements Statement for the program. and a sketch made of what the screen will look like. you can then determine what processing needs to be performed to convert the input to output. the likelihood of this happening will be reduced dramatically. and the input to the program. The end result is a program that will behave in the way it was intended. You will also be in a position to consider what information needs to be saved. At this stage of the AIRFORCE SCHOOL MANAGEMENT SYSTEM it isn't necessary to discuss the 'how' of what the program will do. more information will be available to add to the Requirements Statement. Here is a list of the different components that are 'designed' in this phase:  Input  Output  Processing  Files By the end of the design phase. While doing the Output and Input designs. Most programs are designed by first determining the output of the program. and will generally have with a shorter overall program development time. It is also possible that a first screen design will take shape and at the end of these designs. just to get the requirements down on paper. The reasoning here is that if you know what the output of the program should be.good design. Phase 3: Development . Once you know both the output from. you can determine the input needed to produce that output pretty easily. and in what sort of file. and a rough sketch of what the user interface will look like. Design in the AIRFORCE SCHOOL MANAGEMENT SYSTEM encompasses many different elements.

This leads on to the fifth and final stage Phase5: Test. Initially. Phase 4: Implementation In the Implementation Phase. After the Development phase of the AIRFORCE SCHOOL MANAGEMENT SYSTEM is complete. examination and re-examination of the Requirements Statement is needed to ensure that it is being followed to the letter. During the Implementation phase. That means that we actually start coding the program. There are problems associated with testing a module in isolation. . Any deviations would usually have to be approved either by the project leader or by the customer. Software. Although the programmer will find and fix many problems. to be called by it or possibly. to output intermediate values obtained during execution? Such problems are solved in this phase and modules are tested after writing some overhead code Phase 6: Installation and checkout phase All these phases are important for the project entitled “AIRFORCE SCHOOL MANAGEMENT SYSTEM”. both hardware and software is tested. will be installed on any PCs that require it. All the above phase is used one by one for developing the project. the system is implemented. the user will uncover problems that the developer has been unable to simulate.The Development Phase is in many ways the most exciting time of the SMS. How do we run a module without anything to call it. During testing the major activities are centered on the examination and modification of the code. and programmed in phase 4 of the AIRFORCE SCHOOL MANAGEMENT SYSTEM. In the Development phase. the project reaches fruition. almost invariably. which was designed in phase 2. small modules are tested in isolation from the rest of the software product.


The basic goal of planning is to look into the future. no real monitoring or controlling of the project is possible. A good plan is flexible enough to handle the unforeseen events that inevitably occur in a large project. The major issues that the project plan addresses are:  Schedules and milestones  Software quality assurance plans  Configuration management plans PROBLEM STATEMENT The project Airforce school management system is the system. which works on a local connection to give ease to the School administrator and Employee. and plan the scheduling and resource allocation for these activities.PROJECT PLANNING Planning may be the most important management activity. Without a proper plan. Planning may also perhaps the weakest activity in many software projects. It includes the following functions: LOGIN VERIFICATION  EMPLOYEE TABLE MANTAINANCE  LOGIN MANTAINANCE . and many failures caused by mismanagement can be attributed to lack of proper planning. identify the activity that needs to be done to complete the project successfully. Ideally. all future activities should be planned.

General description Product function and overview Data Entry Section Administrator sectionà This section is developed using VC# and Ado. This section can be accessed by providing administrator password and Staff login password. Employee sectionà Employees have only right’s for reading and insertion… Data Updating Section . STUDENT TABLE MANTAINANCE  FEE SYSTEM  INSERTING GROUPBOX & PICTUREBOX IN TABLE The project aims at the creation of a secure Airforce school management system.NET as front-end and SqlServre 2005 as back-end. this will be accessible to the School administrator and the employees working in the School who have valid user id and password. The administrator can add or edit the master table information. In this section the administrator can authorize employee to data entry and create login credentials for new employees. In School there are few School administrators who administer the School can have access the following facility     EMPLOYEE TABLE MANTAINANCE LOGIN MANTAINANCE STUDENT TABLE MANTAINANCE LOGIN VARIFICATION FEE SYSTEM Administrator will be having unique user id and password through which he can access the above mention facilities.

which is the primary component of any software product that is directly relevant to the users.Administrator sectionà This section can be accessed by providing administrator password.  The commands supported by interface are consistent. The administrator can edit the master table information Employee sectionà This section can be accessed by providing employee password. The administrator can delete the master table information. their speed of recall about how to use the software. Data Deletion Section Administrator sectionà This section can be accessed by providing administrator password. They are as follows:  It is easy to use. .  Once users learn how to use interface.  It is attractive to use. User interface of our project has several characteristics. Employee sectionà Employees have no privilege to delete any type of data. USER INTERFACE DESIGN User interface portion of a software product is responsible for all interactions with the user. Almost every software product has a user interface. User interacts with a software product through its user interface. Studentdetails and admin login credentials by data updating. In this section Employees can update his own login credentials. In this section the administrator can update employee details. In this section the administrator can delete records of the employee who are no longer works in the School .  The time and effort required to initiate and execute different commands is minimum. Update Administrator sectionà Employee has no right’s to enter in this field.


using System. using System.Web.aspx using System.HtmlControls. using System.Web. CODING Register.WebControls.Web. using System.SqlClient.Security.Data.WebParts.Visible = true.Web. EventArgs e) { } protected void TextBox1_TextChanged(object sender. EventArgs e) { } protected void Button2_Click(object sender.Web.UI. } } protected void TextBox4_TextChanged(object sender.Text) { Label11.Data.Configuration. k = k + 1. EventArgs e) { } protected void RadioButton1_CheckedChanged(object sender.UI.UI.UI.Page { int k= 0. EventArgs e) { if (TextBox5. EventArgs e) { } protected void TextBox3_TextChanged(object sender. using System. Label11. using System.Collections.Text != TextBox3.UI. using System. using System.Web. protected void Page_Load(object sender.WebControls. public partial class Default2 : System.l=0. using System.Text = "password mismatched".5.Web. EventArgs e) { . using System.

} } if (k == 0 && l>0) { l = 0. Label9.Text) { c = c + 1. cmd.Tables["emp"]. i < ds. } String constring = ConfigurationManager.ConnectionString.Rows. for (int i = 0.Rows[i]["Loginname"].Connection = con. EventArgs e) { SqlConnection con = new SqlConnection(constring). i++) { if (ds. cmd.CommandText = "select Loginname from Login". int c = 0. EventArgs e) { l = l + 1.Text. protected void Button1_Click(object sender. SqlDataAdapter da = new SqlDataAdapter().Text != "") { .Text!="" && TextBox3.ToString() == TextBox2.Text != "" && TextBox4.} protected void RadioButtonList1_SelectedIndexChanged(object sender.CommandType = CommandType. cmd. SqlCommand cmd = new SqlCommand().ConnectionStrings["con"].ToString().SelectCommand = cmd.Fill(ds. DataSet ds = new DataSet(). "emp"). da. con. EventArgs e) { } protected void CheckBox1_CheckedChanged(object sender.Text = "user". if (c == 0) { if (TextBox1.Count. da.Text != "" && TextBox2.Tables["emp"].Open().

Text = "Login name already exists".Text + "'. Label8.your login name is: " + TextBox2.'" + DropDownList1.'" + RadioButtonList1.Password. } .Text = "some thing went wrong try again".Text = "you need to accept our terms and conditions".Text + "'. if (i == 1) { Label8. Label8.Visible = true.Gender. } else { Label8.Type) values('" + TextBox2.Text = "successfully registered. } } else { Label8.Text.Visible = true.'" + TextBox1. int i = cmd.Visible = true.Visible = false. Label8.'" + TextBox4.Text + "'. } } else { Label8.Text + "')". Label12.'" + TextBox3. } } else { Label8.Text + "'.Text = "some fields are left empty".Visible = true.Visible = true.ExecuteNonQuery(). Label12.CommandText = "insert into Login(Loginname.'" + Label9.Phno.Text + "'.. on login.Text + "'.Name.

Page { protected void Page_Load(object sender.WebParts. using System.WebControls.Collections.Web.Web.Web.Configuration.UI. using System.UI.Web.WebControls.HtmlControls.UI. using System. EventArgs e) { } protected void Button2_Click(object sender.} protected void TextBox2_TextChanged1(object sender.Security. EventArgs e) { } } Login.Web.UI.SqlClient.Data. public partial class login : System.aspx using System. using System. using System. using System.Web. using System.UI. using System. using System. EventArgs e) { } .Data. using System.Web. EventArgs e) { } protected void TextBox5_TextChanged(object sender. EventArgs e) { } protected void Button1_Click(object sender.

aspx using System.Tables["emp"].Data. Response.CommandType = CommandType. using System.protected void TextBox2_TextChanged(object sender.Visible = true. protected void Button2_Click1(object sender.ToString().Rows[0]["Loginname"]. cmd.Configuration.Close(). } con.Text + "'and Password='" + TextBox2.SelectCommand = cmd. using System. SqlCommand cmd = new SqlCommand().Connection = con. using System. . EventArgs e) { SqlConnection con = new SqlConnection(constring).ConnectionString. da. Label4.Tables["emp"].ConnectionStrings["con"]. DataSet ds = new DataSet().Text+"'". cmd.Count > 0) { Session["Type"] = ds. } else { Label4. Session["Loginname"] = ds. EventArgs e) { } String constring = ConfigurationManager.CommandText = "select Loginname.Rows[0]["Type"].ToString(). con.Text.Rows. SqlDataAdapter da = new SqlDataAdapter(). using System. if (ds.Tables["emp"]. EventArgs e) { } protected void TextBox1_TextChanged(object sender.Text + "'and Type='"+DropDownList1. } Masterpage. cmd.Text = "invalid username or password".Type from Login where Loginname='" + TextBox1.aspx").Fill(ds.Web. "emp"). da.Open().ToString().Collections.Redirect("Home.

using System.Redirect("login.Web. using System.HtmlControls. Response.UI.Visible = false.Data.UI.Visible = true. } } else { pnlcust. pnladmin. EventArgs e) { Session["Type"] = null.UI.Visible = true.Web.UI. pnlog.Visible = false. } else { pnlcust.UI.Visible = false.Visible = false.Web.Visible = true.Web. public partial class MasterPage : System.Visible = true. pnlog.ToString() == "admin") { pnlcust.WebControls.Security. using System. pnladmin.SqlClient.Visible = true. EventArgs e) { if (Session["Type"] != null) { if (Session["Type"]. using System. } } protected void Menu2_MenuItemClick(object sender. pnladmin. MenuEventArgs e) { } protected void LinkButton2_Click(object sender.Web. pnlog.MasterPage { protected void Page_Load(object sender. using System.WebControls. .Web.using System.WebParts.aspx").

Connection = con.aspx using System.UI.ToString().Web. public partial class Default2 : System.CommandType = CommandType.Web.Web.SqlClient. .Web.Collections. using System. EventArgs e) { SqlConnection con = new SqlConnection(constring). using System.Open(). } } Ticketbooking. Response.Web.Web.RemoveAll().ConnectionString.ConnectionStrings["con"].UI.Data. protected void Button1_Click1(object sender.UI.Configuration.WebControls.Data.Web. using System.Text. using System. using System.WebControls.Security. cmd. MenuEventArgs e) { } protected void Menu3_MenuItemClick(object sender. MenuEventArgs e) { } protected void Linkbutton1_Click(object sender.} protected void Menu1_MenuItemClick(object sender. using System. using System. EventArgs e) { } String constring = ConfigurationManager. using System. cmd.UI. EventArgs e) { Session. using System.Page { protected void Page_Load(object sender.UI. con.HtmlControls.aspx"). SqlCommand cmd = new SqlCommand().Redirect("Home.WebParts. using System.

cmd.'" + DropDownList3.Numberofpassenger s) values('" + Session["Loginname"] + "'. Label5.'" + DropDownList1. Label5. cmd.Text + "'. cmd.Text+"')".click on generate to know ticket number".'"+DropDownList4. da. if (i == 1 && j == 1) { Label5.Text + "'. da. "emp").Destinationstation.Text = "Server buzy try again".InsertCommand = cmd.Visible = true.CommandText = "insert into Ticketbooking(Passengername.Rows.SelectCommand = cmd.Count!=0 ) { int k = ds. con.'" + DropDownList2.Text + "'". if (ds. EventArgs e) { SqlConnection con = new SqlConnection(constring).cmd.Rows.Connection = con.Open().Text + "'.Visible = true.ExecuteNonQuery(). } con. } else { Label5. SqlDataAdapter da = new SqlDataAdapter().Visible = true.Sourcestation. int i = cmd. .Tables["emp"].CommandType = CommandType.Text. SqlCommand cmd = new SqlCommand().Count. SqlDataAdapter da = new SqlDataAdapter(). int j = cmd. cmd. da.Text = "successfully booked your ticket.Text+"' where FlightName='" + DropDownList1.ExecuteNonQuery().CommandText = "select Ticketno from Ticketbooking where PassengerName='" + Session["Loginname"] + "'".Fill(ds.Close(). } protected void Button2_Click(object sender.CommandText = "update Scheduling set Seats=Seats-'"+DropDownList4.Tables["emp"].Flightname. Label5. DataSet ds = new DataSet().

using System.ConnectionStrings["con"].UI.ToString(). using System. EventArgs e) { SqlConnection con = new SqlConnection(constring).Fill(ds.Web. cmd.Text + "'".UI. con. protected void Button1_Click(object sender. cmd. using System. using System. da. Label5.Rows[k-1] ["Ticketno"].Text = "Try again to book for ticket".Data. } else { Label5.Web.SqlClient. cmd. } con. } } Cancelticket.Data.SelectCommand = cmd. public partial class Default2 : System.UI.ToString().WebParts.CommandText = "select Numberofpassengers from Ticketbooking where Ticketno='" + TextBox2.Close(). using System.CommandType = CommandType.Visible = true. da.Open(). DataSet ds = new DataSet().UI.Web. using System. SqlCommand cmd = new SqlCommand().Security. SqlDataAdapter da = new SqlDataAdapter().ConnectionString. .Web.Connection = con. using System.aspx using System. using System.Tables["emp"].Web.UI. "emp"). using System.Collections. using System.Text = "YOUR TICKET NUMBER IS : "+ds.Web.Page { String constring = ConfigurationManager.WebControls.Label5.HtmlControls.Text.Web.Configuration.WebControls.

} con. } } else { Label4.Close(). Label4. int i = cmd. int j = cmd.Text = "successfully canceled ".Text + "' and Ticketno='" + TextBox2.Visible = true.Visible = true.Text + "'". Label4. da. if (j == 1) { Label4. cmd.Configuration. } else { Label4.Rows[0]["Numberofpassengers"]).Tables["emp"]. if (i == 1) { cmd. Label4.CommandText = "update scheduling set Seats=Seats+'"+a+"' where Flightname='" + DropDownList1. using System.Collections. } } Addnewflight.CommandText = "delete from Ticketbooking where Passengername='" + Session["Loginname"] + "'and Flightname='" + DropDownList1.Text + "'".aspx using System.Data. using System.ToInt16(ds.DeleteCommand = cmd. .ExecuteNonQuery().int a = Convert.ExecuteNonQuery().Text = "database not updated".Visible = true. using System.Text = "Server buzy try again".

Text = "successfully added".Text + "'.CommandText = "insert into Scheduling(Flightname.ExecuteNonQuery().Web.Text = "". int i = cmd. using System.Data.Destinationstation.Text = "".Web.UI. TextBox1. TextBox6. SqlCommand cmd = new SqlCommand().Connection = con. protected void Button1_Click(object sender.ConnectionStrings["con"].Text = "not added". TextBox3. con. cmd.'" + TextBox3.Text + "')". public partial class Default3 : System.using System. cmd. SqlDataAdapter da = new SqlDataAdapter().'" + TextBox5.Seats. using System.Open().Text = "".Text.UI.ToString(). using System.Sourcestation.'" + TextBox4.UI. EventArgs e) { SqlConnection con = new SqlConnection(constring).Text = "".WebParts. } else { Label7. Label7.Web.Visible = true.Page { string constring = ConfigurationManager.InsertCommand = cmd. if (i == 1) { TextBox2. da.WebControls.Time.Price) values('" + TextBox1.Security.Web. using System.Close(). using System. using System. } con.WebControls.SqlClient.ConnectionString.Visible = true.Text + "'.Web. Label7.UI.Text + "'.Web.CommandType = CommandType.Text = "".'" + TextBox2.'" + TextBox6.Text + "'.Web. .Text = "". cmd.Text + "'.UI. Label7. TextBox5.HtmlControls. TextBox4.

} } .

Web. using System. using System. using System.UI.Web.Page { protected void Page_Load(object sender. . using System.UI.WebParts.aspx using System. using System.Security.UI.WebParts.Timings.WebControls. using System. public partial class Default3 : System. using System.UI.aspx using System.WebControls. using System.Collections. EventArgs e) { } } Scheduling. using System.UI.Configuration.UI.Data.Visible = true.Web. using System. using System.Web.Web.Web. using System. } protected void Button1_Click1(object sender.Security. EventArgs e) { } protected void Button1_Click(object sender. using System. using System.Configuration.Collections.UI.Web. EventArgs e) { GridView1.Web.Data.Web.WebControls.Web.Web. using System.WebControls.HtmlControls.Web. using System.UI.Web. using System.HtmlControls. using System.UI.

Web.UI. using System.UI. EventArgs e) { Response.WebParts. using System.aspx using System.Security.Web.UI.Data. } } Passengerlist.Configuration.Web.Web.WebControls. using System. using System.UI. EventArgs e) { } protected void GridView1_SelectedIndexChanged(object sender.UI.HtmlControls. EventArgs e) { .Page { protected void Page_Load(object sender.Redirect("AddnewFlight. using System. using System.Web. using System. using System.aspx").public partial class Default2 : System.Web. using System.Web.UI.WebControls.Web.Page { protected void Page_Load(object sender.Collections. public partial class Default3 : System. EventArgs e) { } protected void Button1_Click(object sender.

using System. int i = cmd.SqlClient.Text = "".Web. EventArgs e) { } String constring = ConfigurationManager.Text = "".Text = "".UI.HtmlControls.Security. using System.Web. SqlCommand cmd = new SqlCommand().UI. using System.Web.Text. using System. TextBox4.WebControls.Visible = true. using System.'" + TextBox2.WebParts. cmd. TextBox2.UI.Text = "".Open(). cmd. SqlDataAdapter da = new SqlDataAdapter().Message) values('" + TextBox1.'" + TextBox3.Collections.ConnectionStrings["con"].CommandText = "insert into Feedback(Name. EventArgs e) { } } Feedback. .aspx using System.ToString().Text + "')". protected void Button1_Click1(object sender. using System.} protected void GridView1_SelectedIndexChanged(object sender. using System. da. using System.Data.Text + "'.'" + TextBox4. public partial class Default3 : System. cmd.InsertCommand = cmd. TextBox3.Web. EventArgs e) { SqlConnection con = new SqlConnection(constring).Web.Web.Email.ConnectionString. Label5. con.WebControls.Text + "'.ExecuteNonQuery(). using System.Subject. using System.UI.Data.Configuration.Page { protected void Page_Load(object sender. if (i == 1) { TextBox1.Text + "'.CommandType = CommandType.Web.Connection = con.UI.

} } TESTING .Label5. } con.Close().plz try after some time".Text = "Thankyou For your valuable feedback".Text = "Some problem arrived. Label5.Visible = true. } else { Label5.

Module testing is done to check the module functionality and interaction between units within a module. The proposed system is tested in parallel with the software that consists of its own phases of analysis. UNIT TESTING: During the implementation of the system each module of the system was tested separately to uncover errors with in its boundaries. Following are the tests conducted on the system. It then tests the overall functionality of each module. implementation. The objective is to take unit-tested module and build a program structures that has been dictated by design. testing and maintenance. INTEGRATION TESTING Integration testing is a systematic technique for constructing the program structure while conducting tests to uncover errors associated with interfacing. It checks the functionality of each program with relation to other programs within the same module. . User interface was used as a guide in the process.SYSTEM TESTING Testing is a set of activities that can be planned in advance and conducted systematically. MODULE TESTING A module is composed of various programs related to that module.

A demonstration has been given to the client and the end-user giving all the operational features. The testing phase involves the testing of the developed system using various kinds of data.ACCEPTANCE TESTING The software has been tested with the realistic data given by the client and produced fruitful results. after a user logins into the portal. It involves user training. Implementation is the stage where theoretical design turned into a working system. Many preparations involved before and during the implementation of proposed system. system testing and successful running of the developed system. An elaborate testing of data is prepared and system is tested using the tests data. IMPLEMENTATION PHASE The implementation is the final and important phase. Implementation is planed carefully to propose system to avoid unanticipated problems. The system needed to be plugged in to the organization’s network then it could be accessed from anywhere. The client satisfying all the requirements specified by them has also developed the software within the time limitation specified. The users test the developed system when changes are made according to the needs. The tasks that had to be done to implement the system were to .

Then the administrator was granted his role so that the system could be accessed.create the database tables in the organization database domain. The next phase in the implementation was to educate the system. A demonstration of all the functions that can be carried out by the system was given to examination department person. . who will make extensive use of the system.

.SNAPSHOTS Main fields required in login verification:  Administrator user id  Administrator password This module identifies Administrator by verifying valid login id and password. If the user enters the user name and password having the administrator’s privilege then the administrator window will be opened else the billing window will be opened.


Controls Used: 9 textboxes  1 date time picker for reference of payment  1 Combo box for month  3 Buttons .In this module user by the help of this form user can take the fee of the Students.

By which user has the right’s to update and Delete the Records from tables. .This is the Home page of user.

In this module any visitor who ever come to know anything from school gives its information. By using the back button user can get access to home page Controls used: 4 Buttons  2 Date time picker  1 Combo Box  1 Group Box  10 labels .

Now admin can Enter the new details of Employee.Main fields required for user updation:  Employee ID In this module admin has to select either the employee id from the text Box. .

By using the accept button Student admission to school get confirmed. .In this Form user takes the relevant Information from the New Student and fill the form and also takes the photo of student. By using the back button user can get access to home page.

In this form facilities provided to the students are shown.

Main fields required for checking the Salary Details
 Empid from textbox
In this module user can see its Salary Details. He has to give only its Empid..

In this module a Grid view is taken in which data binding is made. Controls taken: A Data Grid View  A Combo box  A Button .the particular Empid get highlighted in grid view. A combo Box is also taken for searching the details of employee fast you have to give only the Empid of the particular Employee ..

In this module a Grid view is A Data Grid View  A Button  A Combo box .

In this module the user who is logged on to the system can change password.  Matches the old password for security reasons.Main fields required for changing own password:  Old password  New password Functionality implemented:  User name of the logged on user will be displayed in user name text box. The password will be changed after pressing the change button. . He just has to enter his old password and the desired new password.

so I strongly believe that the enhancement to be done with the project to be done with the design changes. . Although it has been tried to develop a robust and fault free system. coding changes. Main fields required for login deletion:  Employee ID or First Name  New User Name  Desired Password Functionality implemented:  Auto retrieval of existing employee id and first name whose login had been created on tab load.  Design of the system can be changed in the sense of the flow of the control so that the coding can be decreased to a considerable level. But at the same time I would like to mention that since one can not claim himself as a master of the technology there is always some scope of technical modifications in the project that may lead to find code redundancy & storage space minimization. still enough flexibility has been provided for further enhancements and modifications.  The developed sub modules have all the related features but still improvement can be done. As I mentioned earlier then the designed forms are typically reflections of the developer.  Since the data is retrieved from the tables where everything is based on the coding system if the coding system is changed then the system needs to be redesigned. The project “AIRFORCE SCHOOL MANAGEMENT SYSTEM” also falls in the same domain. full concentration is maintained on the design of the system so that it can be easily modified.Further Enhancement Everything that is made has some or the other things to be added to make it better than revolutions.  The number of queries can always be increased when needed by the user just by modifying the code little bit. The developed package is flexible enough to incorporate the modifications or enhancements with less alteration.

 Auto retrieval of detail of employee on selection of either employee Id or first name. . Now admin can delete the whole record of that employee from the database. Now the employee ID and the first name will be available in the create login module. In this module also admin has to select either the employee id or the first name from the drop down combo box. The other fields are automatically retrieved from the database.

Therefore the quality of training received by the person involved with the system in various capacities helps in successful implementation of Proposed System. The new system may be completely new. replacing an existing manual or automated system. Implementation includes all those activities that take place to convert from the old system to the new one. A crucial phase in the system life cycle is the successful implementation of the new system design. Conversion Procedure: . The proposed system is completely new system i.IMPLEMENTATION Implementation means to take into practice.e. the existing system is manual. The Main Aspects of Implementation are as follows:  Training Personnel  Conversion Procedure  Demonstration Training Personnel: Even well designed system can succeed or fail because of the way they are operated and used.

Conversion is the process of changing from the old system to the new one. MAINTENANCE It has been estimated that maintenance of any software product usually requires much more effort than the effort necessary to develop the product. demonstration of the system is given to persons directly or indirectly related with the system. they are  Parallel System  Direct Conversion  Pilot System  Systems Phase-in For the proposed system Parallel System will be beneficial. users continue to operate the old system in usual manner but they will also start using the new system this method is safest one because it ensures that in case of any problems in using the new system. It must be properly planned and executed. Many studies indicate that the relative effort of development of a typical system to its . Demonstration: After the system is implemented and conversion is complete. Four methods are common in use. the organization can still fall back to the old system without loss of time and money. Under this approach.

maintenance effort is roughly in the 40:60 ratios. to a new computer or to a new operating system. This is called Perfective maintenance. In the proposed Loan Processing system we had done Corrective maintenance and adaptive maintenance. Maintenance involves performing any one or more of the following three kinds of activities:  Correcting errors that were not discovered during the product development phase.g. This is called Adaptive maintenance.  Improving the implementation of the system and enhancing the Functionality of the system according to the customer’s requirements. e.  Porting the software to a new environment. This is called Corrective maintenance. .

Bibliography Referenced Books: NIIT courseware Foundation Semester Vol 3 Part I NIIT courseware Foundation Semester Vol 3 Part II NIIT courseware Software Engineering Semester B Vol 3 Referenced Sites: .Google.