Вы находитесь на странице: 1из 84


Submitted to partial fulfillment of the MASTER OF COMPUTER APPICATIONS Maharshi Dayanand University, Rohtak On ASSETS AND COMPLAINT MANAGEMENT SYSTEM


Under By Guidance Mr. T.N. Sharma Director LogicPace Technologies Pvt. Ltd. Jaipur

Submitted By Ashutosh Sharma MCA VI Enrolment No.:



I, ASHUTOSH SHARMA hereby declared that the project entitled ASSETS AND COMPLAINT MANAGEMENT SYSTEM which is being submitted in partial fulfillment of the requirement for the awards of degree of Master of Computer Application in the Mahrishi Dayanand University, Rohtak, in own record carried out by me and the matter embodied in this projects has not been submitted so far for the award of any degree or diploma elsewhere.

Candidates Signature ASHUTOSH SHARMA


This is to certify that Mr. ASHUTOSH SHARMA S/o Mr. Ganga Prasad Sharma has successfully completed the project at our organization. Under training period he has worked on the project entitled ASSETS AND COMPLAINT MANAGEMENT SYSTEM under the guidance of our Director T.N. SHARMA. During this project he was an active member of the team working on the project. This work carried by him is satisfactory and wish him all the best for his future assignments.

Authorized signatory


This is to certify that this report embodies the original work done by Ashutosh Sharma during the project training as a partial fulfillment of the requirement for the award of the degree of master of computer applications of the Mahrishi Dayanand University, Rohtak.

Pradosh Nair Director

Galaxy Softech


I find great pleasure in expressing our deep sense of gratitude towards all those who have made it possible for use to complete this project with success. We would first of all like to thank Mr. Pradosh Nair (Director of Galaxy Softech, Jaipur) who recommended our name to make a project in the esteemed organization. I would like to thank the wonderful persons whose contributes in my project are immense. The person to guide and help me in this project Mr. T. N. SHARMA, Director, KnowledgePoint InfoTech. Pvt. Ltd. Jaipur. I would also like to thank Mr. T.N. Sharma who helped me during the project for providing me the specific guidance in project whenever I needed.


Necessity is Mother of All Inventions
Project training is an important part of the MCA curriculum. The MCA course project training helps a student in getting acquainted with the manner in which his/her knowledge is being practically used outside his/her institute and this is normally different from what he/she has learnt from books. Hence, when the student switches from the process of learning to that of implementing his/her knowledge, he/she finds an abrupt change. This is exactly why project training session during the MCA curriculum becomes all the more important. Project training is prescribed for the student of Technical College as a part of the three-year degree course of MCA by MDU. We are required to undergo project training for a period of 180 days after the completion of the Vth Semester. This training report describes in detail the training after the Vth Semester, which I completed at the KnowledgePoint InfoTech. Pvt. Ltd., Jaipur. This report also gives the information about the organization and its working along with the project undertaken in the training period.

The fundamental step used in SDLC process is based on the ISO 9001 guidelines. My aim was to follow the ISO guidelines and develop a perfect system.

The system development was organized into 5 major parts: Requirement Gathering Documentation/Design Development Coding Testing

Sr.No Page No

1). About Organization 2). Introduction 3.1) Purpose 3.2) Scope 3.3) Definitions, Acronyms and Abbreviations 3.4) References 3.5) Overview 3) General description 4.1) Product perspective 4.2) Product function 4.3) User characteristics 4.4) General constraints 4) Functional Requirements 5.1) Forms for adding & viewing/editing 5) Preliminary Design 5.1) Context Diagram 5.2) Database Design 6) About Technology 7) Layouts and Descriptions 8) Hardware Requirement 9) Software Requirement 10) Bibliography

8 9




18 35 83 83 84

1. About Organization Software Training

KnowledgePoint InfoTech. Pvt. Ltd aim is to create a space for a "meeting of the minds" between students and leading thinkers in software engineering, at the same time providing a challenging, invigorating educational experience that allows students to accomplish their dreams and fulfill their aspirations. Ours is a journey for a goal to be accomplished, a wish to be fulfilled, a vision to be materialized.

Students become experts in the latest software development theories and fundamental engineering principles. This allows them to think critically, plan strategically and communicate effectively.

KnowledgePoint InfoTech. Pvt. Ltd mission is to alter the dynamics of the software industry by providing trusted, supportive and quality software development services to clients that view our partnership as a strategic driver for their success. When we take on your project, we take the stewardship of the project with you in the director's seat. As stewards of your project, we consider ourselves successful not when we deliver your final product but when the product meets your business objectives and that is our vision.

The Organization provides various equipments like laptops, printer, scanner etc. to its employees. The management wants to keep the record of all the equipments provided to various employees and also wants the employees to file any complaint about any equipment easily, if a fault occurs to achieve this objective through the current manual system is difficult, so it proposed to develop a computer based ASSETS MANAGEMENT. Employee can send any complaint to the engineer and the engineer will check the problem and provide valid response. If the engineer does not attend the complaint within three days then employee can send complaint to the administrator to know the reason why the complaint is not attended. Administrator can send a common message to all the employees or a particular employee. 2.1 Purpose 1. 2. 3. 4. Maintaining details of the equipment. Filing complaint about the fault of the equipment. Maintaining details of the warranty/AMC of the equipment. Details of the equipment allotted.

2.2 Scope User Information Module: This module will maintain user information. This will allow us to add new user, enable/disable, updating user related information, view all the users etc. Equipment Module: This module will maintain equipment information. This will allow us to add new equipments, edit equipment details, updating equipment status, view all the equipment details, generating various reports etc. AMC/Warranty Module: This module will maintain AMC/Warranty information. This will allow us to add AMC/Warranty information, edit AMC/Warranty information, updating AMC/Warranty information, view AMC/Warranty Information, generating various reports etc. Complaint Module: This module will maintain the complaints filed by the employees and the responses send by the engineer to the respective employees, generating various reports etc. Allotment Module: This module will maintain information about the various equipments allotted to various users. This will allow us to add new allotments, updating allotments, view allotments etc. Administrator Complaint Module: This module will help the administrator to provide valid reasons to the employees, if the engineer does not attend their problems in three days.

Administrator Common Message Module: Administrator can send common messages to various users or individual users. 2.3 Definitions, Acronyms and Abbreviations Not Applicable 2.4References Stock registers and a complaint registers of HCM RIPA. 2.5 Overview (Developer's Responsibility) The developer is responsible for: Developing the System. Testing and Debugging Installing the software at client site and beta testing. Conducting end-user training. Maintaining the system for a period of one year after installation.


3. General Description
3.1 Project perspective The initially this module is proposed to be developed as an independent module. Later in this we can add electricity problems, official problems, mess problems and hostel problems etc. 3.2 Product Functions Some of the important functions proposed to be developed are: Maintaining details of the equipment. Filing complaint about the fault of the equipment. List Of Complaints pending resolved, under process, etc. Maintaining AMC/Warranty Details Maintaining Equipment Allotment Details Maintaining Employee Personal complaints.

3.3 General Constraints: 1. Should run on Windows XP/2000 platform. 2. An employee can complain only once for a particular equipment in a day. 3. An employee can file any complaint for equipment if there is any warranty/AMC.

3.4 User Characteristics There are three main users of the system are: 1. System Administrator: - Managing the Database, User Management. Administrator has rights of every module. 2. Employee: - Employees have the rights to file any complaint about the equipment they are using. 3. Engineer: - Engineer will check the equipment and send the response to the respective complaints.


4. Functional requirements
The important functional requirements have been identified. The detail work is still going on. The present version of the SRS just mentions important functionality and brief description. 4.1 Forms for adding & viewing/editing Login Form: User has to login before accessing the Assets Management. Equipment Details Form: For adding Equipment Details. View/Edit/Delete Equipment Details Form: For viewing/editing/Deleting Equipment Details. Equipment Type Form: For adding various Equipments. View/Edit/Delete Equipment Form: For viewing/editing various Equipments type details. New User Form: For creating new user Change Password Form: User can change the password Enabling User Form: For enabling users Disabling User Form: For disabling existing users. Delete User Form: For deleting users. Add/Delete/View Designation Form: For adding new Designations. Add/Delete/View Room Form: For adding/viewing/deleting new room form. Add AMC/Warranty Info Form: For adding AMC/Warranty Information. Delete/Edit/View Add AMC/Warranty Info Form: For deleting/editing/viewing AMC/Warranty Info. Add Allotments Form: For adding allotments. Edit/Delete/View Allotments Form: For editing/deleting allotments. Employee Complaints Info Form: For sending complaint to the Engineer. Equipment Repair Info Form: For sending response to the employees by the Engineer after Checking the complaint. Equipment Search Form: For searching euipments according to various criteria.


Complaint Search form: For searching complaints according to various criteria. Employee Complaint To Admin Form: For complaining to admin if problem not solved within three days. Employee Personal Problem Form: List of employee complaints to administrator. Admin Common Message form: For viewing/adding. Admin Home Page: Home Page Of Administrator Employee Home Page: Home Page of employee. Engineer Home Page: Home Page Of Engineer.


5. Preliminary Design
5.1 Context Diagram


Request to add, edit, delete and view

Check Complaints and view reports Response of the request

Assets Management

Response of the request


Request to file a complaint And view reports

Response Employee


5.2 Database Design: 1. Equipment Details: Field Name Field Type Varchar(30)PK Varchar(30) Varchar(30) Description Office Serial No. Company Serial No. Like Printer, LCD, Keyboard, Laptops, Switch, Hub, Scanner, UPS etc. Equipment Company Name Equipment Manufacturing Date Price of Equipment Register entry serial no Register Entry Date Equipement detail Description Reference to AMC Information Reference to Room Information

Equip_Serial_no Equipment type

Company Name Model Of Equipment Manufacturing Date Purchase Price Stock Register Serial No Stock Date Equip_Details AMC/Warranty Type AMC ID Warranty expire date Locatoin/Room No. Equip Status UserId Alloted Date 2. AMC Information:

Varchar(50) Varchar(50) Date Number(10,2) Varchar(30) Date Varchar(2000) Number(10) FK Date

Varchar(20) FK
Varchar(20) Varchar(30)FK Date Working/Disposed Reference To User Information Reference To Allotements

Field Type Field Name AMC ID AMC With AMC Start Date AMC End Date 3. Room Information: Field Name Room No. Location Number(10)PK Varchar(50) Date Date


Full Company Name AMC Starting Date AMC Ending Date

Field Type Varchar2(20) Varchar2(50)

Description Room Location like ground floor etc.

4. User Information: Field Name

Field Type

Description 15

UserName Designation Telephone No. UserId Password User Type

Varchar2(50) Varchar2(50) Varchar2(50) Varchar2(30)PK Varchar2(30) Varchar2(50)

User full name User Designation Name User Telephone No.

Type Of User like Administrator, Employee,

5. Complaint Detail: Field Name Complaint No. Room No. Complaint Date Time Equip No Problem Description Repair Date Repair Time Action Taken Status User Id 6. Allotments: Field Name UserId Room No. Allot Date Equip No. 7. Equipment Type: Field Name Equip Type

Field Type Varchar2(50) PK Varchar2(20) FK Date Date Varchar2(30)FK Varchar2(2000) Date Date Varcahr2(500) Varchar2(20) Varchar2(30)

Description Primary Key Reference to Room information Date Of Complaint Time Of Complaint Reference to Equipment Detail Problem Detail Problem repair Date Problem Repair time Action Comments Pending,Resolved, Atteneded But Pending, Taken to Company Reference to User Information

Field Type Varchar2(50) FK Varchar2(50) Date Varchar2(30)FK

Description Reference to user Information Reference to Room No. Allotement Date References to Equipment Details

FieldType Varchar2(30)

Description Like Printer, LCD, Scanner, Keyboard, Laptops etc

8. Designation : Field Name Designation FieldType Varchar2(30)PK Description Designation of the user


9. Admin Complaint Information: Field Name FieldType Complaint No. Number(10)PK UserID Varchar2(30)FK UserName Varchar2(50) Problem Date Date ProblemTime Date Problem Varchar2(2000) Solution Varchar2(2000) Room No. Varchar2(20) Status Varchar2(20)

Description Reference Of user information Name Of Employee Date when Problem received Time when problem received Detail of problem Detail of Solution provided Reference To room Information Status Of Complaint like Resolved, Pending

10. AdminCommonMessage : Field Name FieldType UserId Varchar2(30)FK MessageSentDate Date Message Time Date Message Varchar2(2000)

Description Reference to User Information Date When Message Sent Time When Message was sent Details of message


6. About Technology

The .NET Programming Framework

1. Introduction
The .NET framework is a cluster of different technologies. It includes: The .NET languages, which include C# and Visual Basic .NET, the object-oriented and modernized successor to Visual Basic 6.0. The Common Language Runtime (CLR), the .NET runtime engine that executes all .NET programs, and provides modern services such as automatic memory management, security, optimization, and garbage collection etc. The .NET class library, which collects thousands of pieces of pre-built functionality that you can snap in to your applications. These are sometimes organized into technology sets, such as ADO.NET (the technology for creating database applications) and Windows Forms (the technology for creating desktop user interfaces). ASP.NET, the platform services that allow you to program web applications and Web Services in any .NET language, with almost any feature from the .NET class library. Visual Studio .NET, an optional development tool that contains a rich set of productivity and debugging features. The division between these components is not sharp.


2. VB .NET, C#, and the .NET Languages

In fact, all the .NET languages are compiled to the same intermediate language, which is known as MSIL, or just IL. The CLR only runs IL code, which is the reason why the C# and VB .NET

Code in VB .NET

Code in C#

Code in another .NET language

VB .NET compiler

C# compiler

Appropriate compiler

IL (Intermediate Language) code

CLR just-in-time execution Figure 1 Language compilation in .NET languages are so similar (and perform essentially the same).


ADO.NET data access XML

Web forms

Windows forms

File I/O

(and so on)

Core system classes (threading, serialization, reflection, collections, and so on)

The .NET Class Library

Compiler and loader Code verification and optimization Memory management and garbage collection Code access security (Other managed code services)

The Common Language Runtime

Figure 2 The .NET framework

3. The Common Language Runtime

The Common Language Runtime (CLR) is the engine that supports all the .NET languages. Most modern languages use runtimes, these runtimes may provide libraries used by the language, or they may have the additional responsibility of executing the code (as with Java). Runtimes are nothing new, but the CLR represents a radical departure from Microsofts previous strategy. To start, the CLR and .NET framework are much larger and more ambitious. The CLR 20

also provides a whole set of related services such as code verification, optimization, and garbage collection, and can run the code from any .NET language. Central to the .NET Framework is its runtime execution environment, known as the Common Language Runtime (CLR) or the .NET runtime. Code running under the control of the CLR is often termed managed code.

However, before it can be executed by the CLR, any source code that you develop (in C# or some other language) needs to be compiled. Compilation occurs in two steps in .NET:

1. 2.

Compilation of source code to IL Compilation of IL to platform-specific code by the CLR

This two-stage compilation process is very important, because the existence of the IL (managed code) is the key to providing many of the benefits of .NET.

4. Features of DotNet

Dot Net framework supports a very user friendly IDE Visual Studio which makes dotnet very simple. Visual Studio supports a rich set of design tools, including a well known set of

debugging tools and IntelliSense, which catches errors and offers suggestions as you type. It also supports the robust code-behind model, which separates the .NET code you write from the web-page markup tags.

Platform independence
First, it means that the same file containing IL code instructions can be placed on any platform; at run-time the final stage of compilation can then be easily accomplished so that the code will run on that particular platform. In other words, by compiling to IL you obtain platform

independence for .NET, in much the same way as compiling to Java byte code gives Java platform independence.


Performance improvement
Although we previously made comparisons with Java, IL is actually a bit more ambitious than Java byte code. IL is always Just-In-Time compiled (known as JIT compilation), whereas Java byte code was often interpreted.

Instead of compiling the entire application in one go (which could lead to a slow start-up time), the JIT compiler simply compiles each portion of code as it is called (just-in-time). When code has been compiled once, the resultant native executable is stored until the application exits, so that it does not need to be recompiled the next time that portion of code is run.

Language interoperability
The use of IL not only enables platform independence; it also facilitates language interoperability. Simply put, you can compile to IL from one language, and this compiled code should then be interoperable with code that has been compiled to IL from another language. Common Type System This data type problem is solved in .NET through the use of the Common Type System (CTS). The CTS defines the predefined data types that are available in IL, so that all languages that target the .NET Framework will produce compiled code that is ultimately based on these types. The CTS doesnt merely specify primitive data types but a rich hierarchy of types, which includes well-defined points in the hierarchy at which code is permitted to define its own types. The hierarchical structure of the Common Type System reflects the single-inheritance objectoriented methodology of IL.

Common Language Specification

The Common Language Specification (CLS) works with the CTS to ensure language interoperability. The CLS is a set of minimum standards that all compilers targeting .NET must support. Because IL is a very rich language, writers of most compilers will prefer to restrict the 22

capabilities of a given compiler to only support a subset of the facilities offered by IL and the CTS. That is fine, as long as the compiler supports everything that is defined in the CLS. CLS works in two ways. First, it means that individual compilers do not have to be powerful enough to support the full features of .NET this should encourage the development of compilers for other programming languages that target .NET. Second, it provides a guarantee that, if you restrict your classes to exposing only CLS-compliant features, code written in any other compliant language can use your classes.

Garbage collection
The .NET runtime relies on the garbage collector instead. This is a program whose purpose is to clean up memory. The idea is that all dynamically requested memory is allocated on the heap (that is true for all languages, although in the case of .NET, the CLR maintains its own managed heap for .NET applications to use). Every so often, when .NET detects that the managed heap for a given process is becoming full and therefore needs tidying up, it calls the garbage collector. The garbage collector runs through variables currently in scope in your code, examining references to objects stored on the heap to identify which ones are accessible from your code that is to say which objects have references that refer to them. Any objects that are not referred to are deemed to be no longer accessible from your code and can therefore be removed. Java uses a system of garbage collection similar to this. One important aspect of garbage collection is that it is not deterministic. In other words, you cannot guarantee when the garbage collector will be called; it will be called when the CLR decides that it is needed (unless you explicitly call the collector), through it is also possible to override this process and call up the garbage collector in your code.

.NET can really excel in terms of complementing the security mechanisms provided by Windows because it can offer code-based security, whereas Windows only really offers role-based security.


Role-based security is based on the identity of the account under which the process is running (that is, who owns and is running the process). Code-based security on the other hand is based on what the code actually does and on how much the code is trusted. Thanks to the strong type safety of IL, the CLR is able to inspect code before running it in order to determine required security permissions. .NET also offers a mechanism by which code can indicate in advance what security permissions it will require to run.

The importance of code-based security is that it reduces the risks associated with running code of dubious origin. For example, even if code is running under the administrator account, it is possible to use code-based security to indicate that that code should still not be permitted to perform certain types of operation that the administrator account would normally be allowed to do, such as read or write to environment variables, read or write to the registry, or access the .NET reflection features.


.Net was designed to meet the real-world requirement of creating interactive, networked programs. .Net provides support for writing multi-threaded programs to achieve this. This allows the programmer to write programs that can do many things concurrently. For example a GUI (Graphical User Interface) based application might be listening to user events and taking appropriate action, a separate thread might be doing printing and a separate thread might be downloading a file from some machine across the network, all of this being done concurrently. This results in better performance and better CPU utilization.

It is possible to write multi-threaded programs in other languages also but it is achieved only by making use of System calls while in case of .Net languages like C#, it can be achieved by using features of the language itself.

Rich API (Application Programmers Interface) / Namespaces


.Net API is very rich as compared to other languages. Robust Most programs fail for one of the two reasons: (i) (ii) Memory Management Exceptional conditions at run time

While designing the language one of the aim was to ensure that .Net programs are as robust as possible i.e. they should rarely fail. So due importance was given to the above two factors in the .Net. In .Net memory allocation and de-allocation is handled in the language itself, which eliminates many problems caused due to dynamic memory management features in C/C++. C# like languages also supports object-oriented exceptional handling features to handle exceptional conditions, which occur at run-time. This allows a C# program to recover and continue execution even after an exceptional condition occurs. Better support for Dynamic Web Pages .Net offers an integrated support for web pages, using a new technology ASP.NET. With ASP.Net, code in your page is compiled, and may be written in a any of the .Net languages like C#, J# or VB.Net

Efficient Data Access

A set of .Net components, collectively known as ADO.NET provides efficient access to relational databases and variety of data sources. Components are also available to allow access to the file system and to directories.

Object-Oriented C# is based on object-oriented paradigm. Object-oriented programs are organized around data (i.e. objects) and a set of well-defined interfaces (public methods) to that data.


Introduction to Web Applications in DotNet 1. Introduction

Web applications run on the Web Server. Web applications are accessed through web clients i.e. web browsers like Internet Explorer or Netscape. Whenever you access some web site by specifying the URL (Universal Resource Locator), you are accessing some web application. The main components of a web application written in .net are:

ASP.Net (aspx files) HTML

ASP.Net (aspx file) are also .net programs, which run on the Server and then send the result/response to the client. aspx pages can be thought of as a combination of HTML and C# or VB.net or any .net compatible language code.

You access the web application by specifying the URL. If the URL corresponds to an HTML page the web server simply returns the HTML page to the client, which then displays it. If the URL corresponds to the aspx, then it is executed on the Server and the result/response is returned to the client, which is then displayed by the client.

A web application is nothing but a web-site. A web application can be thought of as a collection of two types of resources:

Static Resourcs Dynamic Resources

Web applications are deployed on the web servers (web-containers) and are normally accessed through the Web Clients, which is normally a web browser. The communication between web client and web server takes place through HTTP protocol. 26

2. Static Resources

These are normally non-executable resources. In some cases static resources may also be the executable resources but they do not execute on the server. A typical web application might have following types of static resources: HTML Images, Audio and Video files Documents Spreadsheets Text files

A web client can ask for any static resource by just specifying the URL. Web server simply returns the specified resource to the client without doing any processing. The client decides what to do with the static resource. The most common static resource is the HTML page. The web browser parses the HTML page and displays in the browser window. For other type of static resources the action taken may differ from browser to browser. The browser either displays the contents of the resource on its own or with the help of software corresponding to the static resource. For example, Internet Explorer may open a .doc file using MS-Word software. The browser prompts for saving the contents in case it is not able to display/process the contents.

3. Dynamic Resources
These are executable resources. A web application can have aspx files of dynamic resources. The dynamic resources are also accessed by directly or indirectly specifying the URL. But the action taken by web server is different in case of dynamic resources. The dynamic resources are .net programs. The server executes the appropriate component and then returns the result to the client normally as HTML using HTTP protocol.

4. Web Client (Thin Client)


In web client based architectures, the user interaction layer is separated from the traditional client layer. Web browser manages the user interaction but leaves the rest to applications on the server side, including the logic for driving the user interface, interacting with components in the middle-tier, and accessing databases.

Features of Web Clients

A browser or a similar application to manage user interaction. For an end-user this is the client layer. HTML is normally used as the means of user interface definition. HTTP(s) is used as the information exchange protocol between the Web-Clients and Web Applications. The Web Application programs on the web server side execute the application logic on behalf of browser Clients.

5. The HTTP Protocol

The HTTP is an application level protocol (generally implemented over TCP/IP Connection). The HTTP is a stateless protocol based on requests & responses. In this paradigm, client application (such as your web browser) sends request to the server (such as the web server of an online store) to receive info (such as downloading a catalog) or to initiate specific processing on the server (such as placing an order).

HTTP Request Methods

As an application-level protocol, HTTP defines the types of request that clients can send to servers and the types of response that servers can send to clients.

The Get Request Method The Post Request Method


The Get Request Method

The Get Request is the simplest & most frequently used request method for accessing static resources such as HTML documents, image etc. The GET method is used when the resource is accessed by specifying the URL in the web browser or by clicking on a hyperlink. Get request can also be used to retrieve dynamic information by using additional query parameters in the request URL of a dynamic resource.


The data is transmitted as the part of URL if GET method is used.

Sometimes we employ GET method even when accepting data from the client using the form. In this case any data provided in the form is appended to the URL as query parameters before sending to the server.

The Post Request Method

Post requests are used when we need to send large amount of complex information to the server. The Post request allows the encapsulation of multi-part message into the request body. For example, you can use post request to upload text & binary files.

Normally we send data using Post method through form by specifying POST as the method.

The data is transmitted as part of the body. So it is possible to send the large amount of data when using Post request.

The Differences between Get & Post Requests


With get request, the request parameters are transmitted as a query string appended to the request URL. In the case of post request, the request parameters are transmitted within the body of the request.

This has two ramifications: Firstly since a Get request contains the complete request info appended to the URL itself, it allows browser to bookmark the page & revisit later. Depending on the type & how sensitive the request parameters are this may or may not be desirable. Secondly some servers might pose restrictions on the length of request URL. This limits the amount of info that can be appended to the request URL.


Key Feature of HTTP

HTTP is a very simple and lightweight protocol. In this protocol, the clients always initiate requests. The Server can never make a Callback Connection to the Client. The HTTP requires the clients to establish connections prior to each request and the servers to close the connection after sending the response. This guarantees that the client cannot hold on to a connection after receiving the response. Either the client or the server can prematurely terminate the connection.

6. The Requirements for Developing & Hosting Web Applications

The following are the most essential requirements for developing and hosting web applications:


A Programming Model and an API - for development of applications.

(ii) Server-side Runtime Support - This includes support for network services and a runtime for executing the applications. (iii) Deployment Support Deployment is the process of installing the application on the server. Deployment could also include customizing the application.

For building and running web applications, the .NET provides the following to meet each of the above requirements:

(i) ASPX Pages These are the building blocks for developing web Applications in .NET. ASPX pages can be developed using any dot net compatible language.

(ii) Web development Server for Hosting Web Applications


IIS is providing .NET runtime for providing all the facilities for writing web applications in .NET. The IIS is responsible for initializing, invoking and managing the life cycle of ASPX files (iii) Packaging Structure & Deployment Descriptor The .NET specification defines a packaging structure for web applications. The specification also defines a deployment descriptor for each web application. The deployment descriptor is an XML file that lets you customize the web application at deployment time.

7. ASP.NET Applications
ASP.NET applications are divided into multiple web pages. This division means that a user can often enter an ASP.NET application at several different points, and follow a link out of your application to another part of your web site or another web server.

The standard definition of an ASP.NET application describes it as a combination of files, pages, handlers, modules, and executable code that can be invoked from a virtual directory on a web server. In other words, the virtual directory is the basic grouping structure that delimits an application.


IIS Web Server

Application Domain Application Domain

Web pages

Configuration files Application and session data

Web pages

Configuration files Application and session data

Web Services

Web Services

Application Domain Web pages

Application Domain Web pages

Configuration files Application and session data

Configuration files Application and session data

Web Services

Web Services

Figure ASP.NET applications

Web Servers and You Web servers run special software (namely, the built-in Internet Information Services, or IIS) to support mail exchange, FTP and HTTP access, and everything else clients expect in order to access web content.

IIS receives a request for a file. It then looks at the file extension, and uses that to determine if the file should be allowed, and what program (if any) is required to handle it. Ordinary HTML files will be sent directly to your browser. ASP files, however, will be processed by the ASP service (which IIS starts and invokes automatically). The ASP service creates an HTML stream with the final result of its processing, and IIS sends this file to the client.


Web request Remote client browser

ASP engine

Page processing Page processing

ASP page (.asp file)

HTML output page

ASP.NET engine

ASP.NET page (.aspx file)

Figure How IIS handles an ASP file request

So in order to test that IIS is working correctly, you need to request the localstart.asp file through IIS. To do this, open an Internet browser, and type a request for the file using the name of your computer. For example, if your computer name is tnsharma, you would type http://tnsharma/localstart.asp or http://localhost/localstart.asp. IIS will receive your request, ASP will process the file, and youll receive a generic introductory page in your Browser.


7. Form Layouts and Descriptions

The important functional requirements have been identified. The detailing work is still going on. The present version of the SRS just mentions important functionality and brief description.

1. User Information Module

Role of user information module: In many web applications there is a need for keeping track of the individual users of the application. This might be necessary with applications where the users created by administrator. User Information involves checking who a valid user is and provide security during his session accordingly, during which he can update his information like changing his password. A logout mechanism is also provided to destroy the user session as a security measure. The User Information Module generally divides into submodules as follows: 1.1 1.2 1.3 1.4 User Authentication Module. User Creation Module User Status and Password editing module. User Drop Module.

1.1 User Authentication Module

Current Web Technology has the inherent problem that there is no notion of a User Session when someone is accessing a Intranet or Internet software: By default, the Web Server Software does not systematically register which users are accessing what pages, or in what sequence. It simply handles a sequence of seemingly unrelated requests. In some web applications, the lack of User Sessions is not a problem, simply because there is no need to restrict access to certain areas, to personalize the viewed pages, or to log specific user actions. The User entity describes the User data implemented by the User Management module. The User entity defines the following fields during his login session on the ACMS[RIPA]. UserId Describes the identification of a user in the system. This field is entered when a user logs onto the application. Password Describes the password for the user. The password is saved in the database. User Status describes the status of the web user. If the user logs out off his session, he


becomes inactive and would never be able to see his account unless he enters his userid and password again. Only administrator created users are allowed to use the application.


1.2 USER CREATION MODULE ACMS users are created by administrator only. On ACMS there are three types of users (i) Administrator (ii) Employee (iii) Engineer. The administrator is responsible for managing database, user management, addition of new users and deletion (which is not allowed to other type of users). Administrator will create users by following steps. Step. 1 : Click on User Information link on the Admin Home page


Step 2 : Click on Add User link


Step 3 : Enter User Information and click on save button and Administrator will get two types of response messages (i) Successfully saved(in case of unique user information), (ii) Already exist (in case of duplicate user information added).


1.3 User Status and Password Editing module Administrator has rights to give new password to user and change user status. Faculty and Guest user(s) can change own password only. Administrator can see user(s) status list and editing the status of the user. Statuses have two types on RipaACMS first one is enabled (by default) second one is disabled. Administrator will change user status and password by following steps.

(i) Change User Status Step 1 : Enable User by Clicking on User Information > Enable User Link

Step 2 : Disable User by Clicking on User Information > Disable User Link 40


Step 3 : (i) Reset User Password by Clicking on User Information > Edit User Link


(ii) Then select the user you want to modify


(iii) Now click on the reset password link if you want to modify the password and enter the password and other information you want to modify.


2. Designation Module
In this module we can do the following tasks: 2.1 Create New Qualification 2.2 Delete Qualification


2.1 Create New Designation In this module administrator will add new Designation into the database. Step : UserInformation > DesignationInfo > Add Designation


2.1 Delete Designation In this module administrator will delete the designation in database . Step : UserInformation > DesignationInfo > Add Designation On clicking the delete button the selected designation will be deleted from the database.


2. Room Module
In this module we can do the following tasks: 2.1 Create New Room 2.2 Delete Room


2.1 Create New Room In this module administrator will add new room into the database. Step : UserInformation > Room Info > Add Room


2.1 Delete Room In this module administrator will delete the room in database . Step : UserInformation > RoomInfo > Add Room On clicking the delete button the selected room will be deleted from the database.


3. Equipment Module
In this module we can do the following tasks: 3.1 Create new Equipment Details 3.2 Modify any Equipment Details 3.3 Delete any Equipment Details 3.4 Show any Equipment Details


3.1 Create New Equipment Details In this module administrator will add new equipment details into the database. Step : Equipment Info > AddEquipmentDetails


3.2 Modify any Equipment Details In this module administrator will modify any equipment details into the database. Step 1. Equipment Info -> Edit/Delete/ViewEquipmentDetails Now you will get Search Equipments form. Here you can search a particular equipment to modify by clicking on search button or you can get all the list of equipments by clicking on the SearchAll button.


Step 2: Now select the equipment you want to modify by clicking on the edit link.


Step 3 Now modify the required details.


3.3 Delete any Equipment Details In this module administrator will modify any equipment details into the database. Step . Select the equipment you want to delete by clicking the delete link.


3.4 View any Equipment Details In this module administrator will modify any equipment details into the database. Step . Select the equipment you want to view by clicking the equipment no you want to view.


4. Equipment Type Module

In this module we can do the following tasks: 4.1 Create new Equipment Type 4.2 Delete any Equipment Details


4.1 Add new Equipment Type In this module administrator will add new equipment type into the database. Step. Equipment Info->EquipmentTypes->AddEquipments


4.2 Delete Equipment Type In this module administrator will delete equipment type from the database. Step. Equipment Info->EquipmentTypes->AddEquipments Clicking on the delete button the selected equipment will be deleted.


5. Add Allotments Module

In this module we can do the following tasks: 5.1 Create new Allotment Details 5.2 View any Allotment Details


5.1 Add new Allotment Details In this module administrator will add new allotments details into the database. Step. Allotment->AddAllotmentInfo


5.1 View any Allotment Details In this module administrator will add new allotments details into the database. Step 1. Allotment->SearchListOfAllotments Here you will get Search Allotments form and from here a specific allotment detail(s) can be searched.


Step 2. Now to search a specific allotment details enter details and click search. To get list of all the allotments click SearchAll


6. Complaint Info Module

In this module we can do the following tasks: 6.1 View any Allotment Details


6.1 View any Allotment Details Step 1. ComplaintInfo->SearchEmployeeComplaintsList By this specific complaint can be searched.


Step 2. Now you can search according to various criteria or get all the list of employee complaints.


Step 3. Now click on the specific complaint no. you want to view.


7. Personal Complaints Module

In this module we can do the following tasks:

7.1 Give response to the user complaints Step. Click on the link Personal Complaints where you will get the list of user complaints And send response to the respective users.


8. Send Common Message

In this module we can do the following tasks:

8.1 Send Common Message to all the users Step. Click on the link Common Message link where you will get the list of users And send message to respective users.


9. Employee Module
Employee can perform following task: 9.1 Hardware Complaints 9.2 Send Personal Complaints 9.3 Change Password

Role of Employee Module: In This Web Application a Employee can do two types of task: .Hardware Complaint: An Employee will send a Hardware complaint to the Engineer if Some Equipments of Desktop Computers are not working properly. Personal Complaint: An Employee will send a Personal Complaint to the Administrator (not to Engineer) if he doesnt get any response from Engineer for a fired complaint in specific time period. When an Employee will logon with his correct userId & Password, he will get Homepage of Employee as shown below:


Home Page shows The total no. of Hardware Complaints and Personal Complaints Sent by the Employee.

9.1 Hardware Complaints Module

In this module employee can do the following tasks: 9.1.1 Send Hardware Complaints 9.1.2 View Hardware Complaints 9.1.1 Send Hardware Complaints Step .1 Check status An Employee can check the status of his Hardware Complaints clicking on Hardware Complaints Link at the left most of the Employee Home Page. After Clicking on Hardware Complaints Link a form will display as below: -


Step 2. To send new complaint click on the New Complaint Link

Now send the message and you will get response as Message sent.


9.1.2 View Hardware Complaints Step . Click on the Complaint No you want to see the response from the engineer.


9.2 Send Personal Complaints Step 1. Click on the Personal Complaints Link Here you can view the solutions of the earlier complaints if provided any.


Step 2. To send new personal complaint click on the New Complaints link.


9.3 Change Password Step . Click on the change password link if you want to change your password.


9. Engineer Module
Employee can perform following task: 9.1 Employee Complaints 9.2 Change Password Role of Engineer Module: In This Web Application a Engineer can do two types of task: .Employee Complaints: An engineer will send a valid response to the employee complaints through this module. Change Password: If he wants to change the password the he do that form this module. When an Engineer will logon with his correct userId & Password, he will get Homepage of Engineer as shown below:


9.1 Employee Complaints Step 1. Click on the Employee Complaints link and you will get a search form. From here you can search the complaints with specific criteria by clicking search button or can get list of complaints by clicking the SearchAll button.


Step 2. From here a respone can be sent using particular complaints of the employee.


Step 3. From here a valid response can be sent.


9.2 Change Password Step . Engineer can change the password by clicking the Change Password Link.


8. Hardware Requirement: Intel Pentium-IV processor 256 MB RAM or higher 40 GB HDD or higher UPS

9. Software Requirement: Microsoft Windows XP / 2000. Dot net framework 2.0 or above IIS 5.1 or higher RDBMS (Back end): SQL SERVER2005 Front end: Asp.net, C#. Web Browser: Internet Explorer6 or higher, Mozilla, Opera.


10. Bibliography

1. Beginning Asp.Net 3.5 in C# 2008 (By: Matthew MacDonald) 2. Professional .Net Framework 2.0 (By: Joe Duffy (Wrox)) 3. Professional Ado.Net 2 programming with sql server. (By: Wallace B.McClure)

Sites: http://msdn.microsoft.com http://codeguru.com www.w3schools.com www.eggheadcafe.com