1

CONTENTS
1. 2. 3. COMPANY PROFILE INTRODUCTION TO .NET INTRODUCTION TO ASP.NET

4.

INTRODUCTION TO SQL

5. 6. 7.

ABOUT THE PROJECT EXISTING SYSTEM PROPOSED SYSTEM

SOFTWARE DEVELOPMENT LIFE CYCLE MODULES IN THE PROJECT DATA BASE TABLES SNAPSHOTS DATABASE DIAGRAMS CONCLUSION BIBLIOGRAPHY

9 10 11 12 13 14

1. ABSTRACT OF THE PROJECT

This Project includes all my learning work done during my six months Industrial Training at SPIC Microsoft. This web application is very useful for managing hostels detail. This is a very simple and easy to use web application which store information about hostels, wardens, students, seats in hostels, issued items, purchase details. We can filter the data according to hostelID, studentID, wardenID etc. We can maintain the data stored on the server. This web application is aimed at making data entry, management, updating, storage and retrieval easier and faster. The following objectives have been kept in mind:

Efficiency:-We

tried

to

involve

accuracy,

timeliness

and

comprehensiveness of the system output. Cost: - It is desirable to aim for the system with a minimum cost subject to the condition that it must satisfy the entire requirements. Flexibility: -We have tried that the system should be modifiable depending on the changing needs of the user. Such modifications should entail extensive reconstructing or recreation of application.

INTRODUCTION
SPIC stands for Society for Promotion of Information Technology which is under the Aegis of Department of IT, Chandigarh Administration. In an effort to automate the internal processes of the Departments of the Administration, SPIC has been playing a key role being the Nodal Agency under the National eGovernance Plan. This year ,the Municipal Corporation ,Department of Urban planning and higher Education will be undertaken in this ambitious national level project .SPIC is also working closely with other Departments like Chandigarh Police , Excise and Taxation , Government Medical College & Hospitals ,Govt Fine Arts, Zila Sainik Welfare for automating their internal processes. In an initiative automate the HRD department of Chandigarh Police Department SPIC has Developed and implemented personal Information system for Chandigarh Police. This scope of the project has been defined to manage all the information about all the personals of the police department.

VISION

SPIC is a focused and committed provider of product design and development services.

The Department has mission to "continue to be a strong Outsourced Software Product R&D services companies and provide compelling benefits of the global distributed development model. SPIC provides the best-in-class services to its clients in the development of bestof-breed software products, technology expertise, and commitment to continual improvement. SPIC' values and vision are more than just words. The company vision is to "provide the best Outsourced Software Product Development experience, grow as a trusted technology partner to our clients." These are the foundation building blocks upon which spic is built the successful SPIC value proposition.

Efficiency
SPICs mission is to partner with the world's emerging and established software leaders to help them bring great products to market in efficient way and at less cost.

Integrity
We believe in treating people with respect. We believe in always doing what we say we will and when we say we will do it. We always hold ourselves to the highest ethical standards and take personal responsibility for our words and actions.

Accessibility
We greatly value our people and seek to empower them. We believe in the free flow of information, regardless of rank or power, so that everyone has access to the most complete data in order to make the best decisions. We maximize transparency to create an environment where every individual is accessible and encouraged to contribute, and where each thought is valued and factored into making decisions.

Credibility
We understand the business logics and the partners products and work as a partner extension to achieve the goals. We take all the credibility for successful product execution. Partners rely on us as being a part of their organization.

1. 2 Objective

SPIC has been applying agile methodology for product development using best practices from the bottom-up, and has considerable from key stakeholders and sponsors. Some basic principles being followed are:The launch of software product is the ultimate goal of a software development project. Project teams perform well to achieve short-term, realizable, and recognizably valuable goals. Short and regular feedback loops are necessary to both gauge and direct the progress of a software project. Clients are happy when they feel they have control on system being developed and see regular, tangible results.

3. INTRODUCTION TO DOT NET

The.NET is a web application framework developed and marketed by Microsoft to allow programmers to build dynamic web sites, web applications and web services. It was first released in January 2002 with version 1.0 of the .NET Framework, and is the successor to Microsoft's Active Server Pages (ASP) technology. ASP.NET is built on the Common Language Runtime (CLR), allowing programmers to write ASP.NET code using any supported .NET language. The ASP.NET SOAP extension framework allows ASP.NET components to process SOAP messages. The .NET Framework, introduced by Microsoft in 2002, is a programming platform and set of tools for building and running distributed applications in the Internet era. It also contains an object-oriented class library and a collection of reusable types (a type is a representation of data such as classes) that enable you to accomplish many common programming tasks such as file access, string manipulation, and database management. The class library is categorized into modules (referred to as namespaces) and includes types that support a variety of applications such as: Console applications Windows forms ASP.NET applications XML web services Windows services SQL Server applications Small device applications ASP.NET, the next version of ASP, is a programming framework used to create enterprise-class Web Applications. These applications are accessible on a global basis leading to efficient information management. The advantage that the ASP.NET offers is more than just the next version of ASP. In fact, C# is one of the .NET languages that Microsoft developed. The other languages that use .NET are Visual Basic .NET, J#, and Managed C++, in addition to languages developed by other companies. All these languages work under the .NET umbrella and use its libraries. Actually, you can write an application with modules written in different languages that support .NET.

HISTORY
After the release of Internet Information Services 4.0 in 1997, Microsoft began researching possibilities for a new web application model that would solve common complaints about ASP, especially with regard to separation of presentation and content and being able to write "clean" code. Mark Anders, a manager on the IIS team, and Scott Guthrie, who had joined Microsoft in 1997 after graduating from Duke University, were tasked with determining what that model would look like. The initial prototype was called "XSP"; Guthrie explained in a 2007 interview that, "People would always ask what the X stood for. At the time it really didn't stand for anything. XML started with that; XSLT started with that. Everything cool seemed to start with an X, so that's what we originally named it."The initial prototype of XSP was done using Java, but it was soon decided to build the new platform on top of the Common Language Runtime (CLR), as it offered an objectoriented programming environment, garbage collection and other features that were seen as desirable features that Microsoft's Component Object Model platform didn't support. Once the ".NET" branding was decided on in the second half of 2000, it was decided to rename ASP+ to ASP.NET. Mark Anders explained on an appearance on The MSDN Show that year that, ".After four years of development, and a series of beta releases in 2000 and 2001, ASP.NET 1.0 was released on January 5, 2002 as part of version 1.0 of the .NET Framework. Even prior to the release, dozens of books had been written about ASP.NET and Microsoft promoted it heavily as part of their platform for web services.

The .NET Framework is:

Common Language Runtime provides an abstraction layer over the operating system Base Class Libraries pre-built code for common low-level programming tasks Development frameworks and technologies reusable, customizable solutions for larger programming tasks The dot Net framework consists of two main components one of them is Dot Net framework class library and another is CLR. The dot Net framework class library common for all dot Net language .We can use this to develop different application such as console applications, windows and Web Forms and Web Services. The CLR do some of the important task such as load the IL code of program at runtime. Compile the IL code in native code execute and manage code enforce security and type safety helps in thread support .The code that run in CLR is called unmanaged code. There is a layer which allows both manage code and unmanaged code to interoperate with each other. The CLR is combination of various components which provides the runtime environment and runtime services for our application. These components load the IL code into runtime environment and runtime service for our applications.

10

ASP .NET:
ASP.NET is more than the next version of Active Server Pages (ASP). It provides a unified Web development model that includes the services necessary for developers to build enterprise-class Web applications. While ASP.NET is largely syntax compatible with ASP, it also provides a new programming model and infrastructure for more scalable and stable applications that help provide greater protection. You can feel free to augment your existing ASP applications by incrementally adding ASP.NET functionality to them. ASP.NET is a compiled, .NET-based environment; you can author applications in any .NET compatible language, including Visual Basic .NET, C#, and JScript .NET. Additionally, the entire .NET Framework is available to any ASP.NET application. Developers can easily access the benefits of these technologies, which include the managed common language runtime environment, type safety, inheritance, and so on. ASP.NET has been designed to work seamlessly with WYSIWYG HTML editors and other programming tools, including Microsoft Visual Studio .NET. Not only does this make Web development easier, but it also provides all the benefits that these tools have to offer, including a GUI that developers can use to drop server controls onto a Web page and fully integrated debugging support. Developers can use Web Forms or XML Web services when creating an ASP.NET application, or combine these in any way they see fit. Each is supported by the same infrastructure that allows you to use authentication schemes, cache frequently used data, or customize your application's configuration, to name only a few possibilities. Web Forms allow you to build powerful forms-based Web pages. When building these pages, you can use ASP.NET server controls to create common UI elements, and program them for common tasks. These controls allow you to rapidly build a Web Form out of reusable built-in or custom components, simplifying the code of a page. For more information, see Web Forms Pages. For information on how to develop ASP.NET server controls, see Developing ASP.NET Server Controls.

11

INTRODUCTION TO CRYSTAL REPORT

Crystal Reports for Visual Studio .NET is the standard reporting tool for Visual Studio .NET; it brings the ability to create interactive, presentation-quality content which has been the strength of Crystal Reports for years to the .NET platform. With Crystal Reports for Visual Studio .NET, you can host reports on Web and Windows platforms and publish Crystal reports as Report Web Services on a Web server.

Advantages of Crystal Reports:

Some of the major advantages of using Crystal Reports are: 1. Rapid report development since the designer interface would ease the coding work for the programmer. 2. Can extend it to complicated reports with interactive charts and enhance the understanding of the business model 3. Exposes a report object model, can interact with other controls on the ASP.NET forms 4. Can programmatically export the reports into widely used formats like .pdf, .doc, .xls, .html and .rtf.

12

4. INTRODUCTION TO SQL
SQL is a standard language for accessing and manipulating databases.

What is SQL?
SQL stands for Structured Query Language SQL lets you access and manipulate databases SQL is an ANSI (American National Standards Institute) standard

What Can SQL do?

SQL can execute queries against a database SQL can retrieve data from a database SQL can insert records in a database SQL can update records in a database SQL can delete records from a database SQL can create new databases SQL can create new tables in a database SQL can create stored procedures in a database SQL can create views in a database SQL can set permissions on tables, procedures, and views

13

5. ABOUT THE PROJECT

This project serves as a web application to handle the hostel system accurately and more efficiently. It is platform independent as it is a web based application.

The main idea behind developing this application was to reduce the manual efforts, moreover making the system more easily accessible. This application reduces the problem of data redundancy with the help of normalization. It helps to maintain the records easily and is even less time consuming.

As referred above the technology being used is Dot Net and we worked in web applications with ASP.NET as front end and SQL Server2005 as back end.

SALIENT FEATURES OF PROJECT

Integrated approach to the package helps in minimizing manual approach.

User friendly package Timing and retrieval efficiency In-built validation checks to ensure accuracy

14

Elimination of paper work Suitable help/error message for better user interface Updated information

7. EXISTING SYSTEM

Nowadays for handling these kinds of systems, a lay man does all the work manually. He needs to keep various registers or files so as to keep the details but it creates a mess for him whenever he needs to check a record, save another record, delete any record or update it. This also makes the data not so easy to understand. This increases the hardware cost and the maintenance headache. Moreover there also occurs certain kind of problems: Data redundancy. Loss of data. Difficult to access data. Time Consuming.

Data Redundancy
Data redundancy refers to duplication of data. In case of manually handling this system and maintaining the records, many a times same data is written at many places, so this repetition of data at various places can increase hardware cost, moreover maintaining such data becomes most difficult.

15

Loss of data
In case of any kind of misplacing or if sometimes we lose the registers or files, it may lead to a great loss of data as no duplicate copy or a database is being maintained.

Difficult to access data

When the data is being placed at many places in small segments, it becomes very difficult to gather data from various places, moreover updating or deleting the data at each and every place.

Time Consuming
This process is very time consuming as to search for any data or for taking any kind of action, the person has to go through every data and check for each and every detail of the data.

Record Management:
Is very tangible job in manual database system.

Inaccuracy:
Some time there may be chance of inaccuracy. Existing system is not according to current demand.

16

No Report Generation:
In Existing, system there is any automatic report generation facility.

Inconsistency:
In the existing system, there are no checks or constraints so; the duplication may make the data inconsistent.

Unauthorized Access:
There is no way to restrict unauthorized access to the data except putting the files under lock and key.

Paper Wastage:
Currently some tasks are done manually, its uses paper, hence not a cost efficient system and eco-friendly.

Problem in Updating:
As data are written on papers, the updating or any type of correction requires rewritten of information. There is no procedure for keeping duplicate record system. Due to above reasons the change in the existing system is required for the change we have to perform the feasibility study. The success of a system largely depends upon how accurately the problem is defined and investigation. Until, the problems are clearly defined and evaluated, should we think about solutions.

17

7. PROPOSED SYSTEM

Proposed system is expected to remove the problems of the existing system and provide value-added solution to the problem. Due to limitation in the existing system it is felt to switch over to a new system that covers all the possible aspects:

Proposed system with objectives:

Proposed System is automated and web based system so that's why it has very fast processing speed. Records management is very easy job in database. There may be not any chance of inaccuracy. Proposed system is according to current demand. In Proposed system there is automatic report generation facility. Security and privacy is possible by using user name and password. Data integrity is maintained and redundancy is reduced.

Software System Attributes:

Usability:
The links are provided for each form. The user is facilitated to view and make entries in the forms. Validations are provided in each field to avoid inconsistent or invalid entry in the databases. Some forms consists Hyper Links, which provides

18

further details. Reports screen contains text boxes and drop down lists, so that reports can be produced.

Security:
Application will allow only valid users to access the system. Access to any application resource will depend upon users designation. There are three types of users namely Administrator and Warden. Security is based upon the individual user ID and Password.

Availability:
System will be available around the clock except for the time required for the backup of data.

Portability:
The application is developed in ASP.NET. It would be portable to other operating system provided .NET Framework is available for the OS. As the database is made in SQL Server, porting the database to another database server would require some development effort.

Acceptance Criteria:
The software should meet the functional requirement and perform the functionality effectively and efficiently.

19

A user-friendly interface with proper menus. Data transfer should be accurate and within a reasonable amount of time keeping in mind the network traffic. The system should not allow entry of duplicate key values. System should have the ability to generate transactional Logs to avoid any accidental loss of data. Log file should also be generated.

8. Software Development Life Cycle

This involves the activities in the production of the software system. Generally it can be divided into the following phases:1) Feasibility study 2) Requirement analysis 3) System specification 4) System and component design 5) Implementation component design 6) System testing 7) Maintenance

20

21

8.1.Feasibility Analysis

A feasibility study is initiated to determine the performance and cost effectiveness of the proposed system and if it meets all the constraints, it is recommended in feasibility report. It measure how beneficial or practical the development of the system will be to the organization. It is a preliminary survey for the system investigation. Its aim is to provide information to facilitate a later in-depth investigation. A feasibility study is a test of a system proposal according to this work ability, impact on the organization, ability to meet user needs, and effective use of resources. It focuses on three major questions: What are the users demonstrable needs and how does a candidate system meet them? What resources are available for given candidate system? What is the likely impact of the candidate system on the organization?

Three key considerations are involved in the feasibility analysis. Economic Feasibility Technical Feasibility Behavioral Feasibility

The feasibility study of the software is as follow:

22

Economic Feasibility
Economic feasibility determines the benefits and saving that are expected from the system and compare them with costs. Cost/Benefit analysis has been done on the basis of total cost of the system and direct and indirect benefits derived from the system. The total cost for the proposed system comprises of hardware costs and software costs. The main aim of economic feasibility is to check whether the system is financially affordable or not. The cost for the proposed system can be divided into two parts given below:

Hardware Costs
The hardware cost for the proposed system can be calculated from cost of hardware needed for the development of the proposed system. The hardware specifications for the system are given below:

Personal Computer: The cost of the PC depends upon the configuration of the
PC. The minimum specification assumed for the Pc is given below: P4 processor 256 MB RAM 40 GB free disk space MS Windows

23

Server: As the software is a client-server based application, thus an efficient

server would act as the backbone of a good communication system. The minimum specifications are: Core2Dual processor 512 MB RAM 120 GB free disk space

Software Costs: The Software costs for the proposed system can be calculated
from the cost of software tools needed from the development of the proposed system. The software tools needed for the development of the system are given below:

Microsoft Visual Studio 2008 SQL server 2005

24

Technical feasibility:
Technical Feasibility centers on the existing system and to what extent it can support the proposed system. In this part of feasibility analysis we determined the technical possibilities for the implementation of the system. Two major benefits are: Improving the performance Minimizing the cost of processing

This software is web based application. To develop the software the following technology will be used as per requirement: Language: ASP.NET Editor : Microsoft Visual Studio 2008 Database : SQL server 2005

Behavioral Feasibility
Behavioral feasibility estimates the reaction of the User staff towards the development of the computerized system. For the successful implementation of any system, the users must be impressed that the new system is for his benefit. So, the behavioral feasibility plays a very important role in the development of new system It reveals that whether the system is acceptable by user or not. If the user does not ready to use it, then it doesnt matter how best the system is or how much effort you are putting in its development.

25

8.2 H/W AND S/W REQUIREMENTS .NET Framework System Requirements

To ensure adequate performance, .NET Framework has the following minimum and recommended system requirements for client and server applications:

Operating System Requirements:

The .NET Framework is supported on the following platforms: ---------------------------------------------------------------------------------------------------Scenario Operating System --------------------------------------------------------------------------------------------------Client MS Windows 98 MS Windows 98 Second Edition MS Windows Millennium Edition MS Windows NT 4.0 Workstation with service pack 6.0a or later MS Windows NT 4.0 Server with service pack 6.0a or later. MS Windows 2000 Professional MS Windows 2000 Server MS Windows 2000 Advanced Server MS Windows 2000 Datacenter Server MS Windows XP Home Edition Professional MS Windows Server 2003 Family Note: On all these systems, MS Internet Explorer 5.01 or later and MS Windows Installer 2.0 or later are also required. Server MS Windows 2000 Professional MS Windows 2000 Server with service pack 2.0 MS Windows 2000 Advanced Server with service pack 2.0 MS Windows 2000 Datacenter Server with service pack 2.0 MS Windows XP Professional MS Windows Server 2003 Family

26

Additional Software Requirements:

To use additional features such as ASP.Net, COM+ services and SQL Server .NET Data Provider, you will need the following additional softwares: ---------------------------------------------------------------------------------------------------Scenario Feature Required Software --------------------------------------------------------------------------------------------------Client SQL Server .Net Data MS Data Access Components Provider (MDAC) 2.6 or later Access to system management Windows Management Instrumentation (WMI) (installed with OS on Windows 2000, Windows Millennium Edition and Windows XP) COM+ Services Windows 2000 with service Pack 2.0 Server SQL Server .Net Data Provider ASP.Net MS Data Access Components (MDAC) 2.7 MS Internet Information Services (IIS) 5.0

Hardware Requirements
---------------------------------------------------------------------------------------------------Scenario Processor RAM Required Recommended Required Recommended --------------------------------------------------------------------------------------------------Client Pentium 500 MHz* Pentium 1 GHz 64 MB* 128 MB or higher Server Pentium 667 MHz* Pentium 1 GHz 128 MB* 256 MB or higher

27

* Or the minimum required by the operating system, whichever is higher.

8.3 System Design

The main objective of the system design is to make the application user friendly. After discussing with some of the technical persons, friends, guide; it was concluded that the design of the application should be 3 tier which means that the system will be developed in orientation to three things:

Data:It includes Database and Stored Procedures etc.

Business:It includes the logic that will actually process the data but it should be in the form of objects and classes that will help in providing the application components reusability, abstraction and other Object Oriented features.

Presentation:
It includes the front end that links the user to the whole system. Generally, it is said that if the design is made well, the whole system will work well. So, I have tried my best to put my effort on this phase properly.

28

THREE LAYERS OF PROJECT

29

DATA FLOW DIAGRAM

A data flow diagram is a graphical representation that depicts information flow and the transforms that are applied as data move from input to output. The data flow diagram may be used to represent a system or software at any level of abstraction. It has the purpose of clarifying system requirements and identifying major transformations that will become program in system design. So it is the starting point of the design phase that functionally decomposes the requirement specifications down to the lowest level of details. A DFD consist of a series of bubbles joined by lines. The bubbles represent data transformation and the lines represent data flows in the system.

In fact, DFDs may be partitioned into levels that represent increasing information flow and functional detail. Therefore, the DFD provides a mechanism for functional modeling as well as information flow modeling.

In the DFD, there are four symbols, A Square defines a source (originator) or destination of system data. An Arrow identifies data flow- data in motion .It is pipeline through which information flows. A circle or a bubble (or a oval bubble) represents a process that transforms incoming data flow(s) into outgoing data flow(s) An open rectangle is a data store-data at rest , or temporary repository of data.

30

ER DIAGRAM:

An E-R diagram can express the overall logical structure of a database graphically. E-R diagrams are simple and clearqualities that may well account in large part for the widespread use of the E-R model. Such a diagram consists of the following major components: Rectangles: which represent entity sets Ellipses: which represent attributes Diamonds: which represent relationship sets Lines: which link attributes to entity sets and entity sets to relationship sets Double ellipses: which represent multi-valued attributes Dashed ellipses: which denote derived attributes Double lines: which indicate total participation of an entity in a relationship set Double rectangles: which represent weak entity sets

Objects
There are three main objects on an ER Diagram: 1. Entities 2. Relations 3. Attributes

31

Entities
An entity is a concept or object in the database. Entities are concepts within the data model. Each entity is represented by a box within the ERD. Entities are abstract concepts, each representing one or more instances of the concept in question. An entity might be considered a container that holds all of the instances of a particular thing in a system. Entities are equivalent to database tables in a relational database, with each row of the table representing an instance of that entity.

Attributes
The Supplier Name, Supplier Address, Telephone Number etc. A given attribute belonging to a given entity occurrence can only have one value. Therefore, if a supplier could have more than one address or telephone number then this should be determined before defining the attributes of that entity type. In this example the defined entity may require two or three address and/or telephone number attributes. It is the maximum practical instances of a given attribute that should be catered for in the entity type definition.

32

Relationships
Relations are the connections between two or more entities. Relationship lines indicate that each instance of an entity may have a relationship with instances of the connected entity, and vice versa.

Mapping cardinalities, or cardinality ratios, express the number of entities to which another entity can be associated via a relationship set. Mapping cardinalities are most useful in describing binary relationship sets, although they can contribute to the description of relationship sets that involve more than two entity sets. Following are the types of cardinalities: One to one One to many Many to one Many to many

33

8.4 SYSTEM TESTING Testing

The system development life cycle involves the phases of testing and debugging after the requirement analysis, designing and coding. The project in question was tested , debugged and implemented successfully. Two strategies of software testing adopted for the new system are as follows: Code testing Specification testing

LEVELS OF TESTING
In order to uncover the errors present in different phases, we have the concept of levels of testing. The basic levels of testing are:

Client Needs -----------------------------------Acceptance Testing Requirements--------------------------------- System Testing Design------------------------------------------Integration Testing Code Unit------------------------------------- Unit Testing

34

Code testing
Code testing was carried out to see the correctness of the logic involved and the correctness of the modules. Tests were conducted based upon sample and live data as well. All the modules are checked separately for assuming correctness and accuracy in all the calculations.

Specification testing
It examines the specification stating about what program should do and how it performs under various conditions. This testing strategy is better strategy since it focuses on the way the software is expected to work.

Unit Testing
During the phase of unit testing different constituent modules were testing against the specifications produced during the design for the modules. Unit testing is essentially for the verification of the code produced during the coding the phase, and goal is to test the internal logic of the modules. The modules once tested were then considered for integration and use by others.

White box testing

During this phase of the testing phase SDLC, server developed was tested while considering a valid value corresponding to each of variable defined and corresponding to each function defined. During this phase values corresponding to each variable viz. URL filtering, word filtering and scheduling was done and desired results were obtained.

35

Black box testing

This phase of testing deals with input/output testing. Black box testing was performed on the software developed, corresponding to valid inputs provided desired outputs were obtained.

Integration Testing
The next level testing that was performed is often referred to as integration testing. During this phase many unit tested modules were combined into subsystems, which were then tested. The goal here was to see if modules can be integrated properly. Here the emphasis was on testing interfaces between different constituent modules of system.

Functionality Testing
Here the entire software system was tested. The reference document for this process is the requirements document, and the goal was to see if software solution meets its requirements. This level of testing is essentially a validation exercise, and in many situation it is the only validation activity.

36

Stress testing
Proxy server developed for the specified purpose was testing under heavy load, i.e. a large no. of clients were made to sit in lab and were asked to send requests for loging in and then were asked to request for text on internet. System responded to request as desired.

Acceptance testing
Acceptance was performed in the real environment with realistic data of the client to demonstrate if the software developed is working satisfactorily. Here the main focus was on the external behaviour of the system; the internal logic of the program was not emphasized.

TESTING OBJECTIVES:
The main objective of testing is to uncover a host of errors, systematically and with minimum effort and time. Stating formally, we can say, Testing is a process of executing a program with the intent of finding an error. A successful test is one that uncovers an as yet undiscovered error. A good test case is one that has a high probability of finding error, if it exists. The tests are inadequate to detect possibly present errors. The software more or less confirms to the quality and reliable standards.

37

8.5 SYSTEM MAINTENANCE

System maintenance is an extremely important activity in the life of a software product that starts after the implementation phase. It is one form of change or rework. For proper maintenance of this system, I am spending a good time on documentation so that I or some other person can easily understand this system later when there is a need for maintenance. Because of the full development being Object Oriented and MS support with this product, this system can be easily connected to any other MS product with a very small effort. Except Web support, more modules can also be easily added because of the 3 tier approach in design; any development or modification is as simple as creating a new application. We dont have to follow the old patterns; we can just start with a new style and add the new modules in to the older one without any problem.

Corrective Maintenance:
Almost all software that is developed has residual errors or bugs in them. Many of these Surfaces only after the system have been in operation, sometimes for a long time. These errors once discovered need to be removed, leading to the software to be changed. This is called Corrective Maintenance.

38

Adaptive Maintenance:
Even without bugs, software frequently undergoes change. The software often must be upgraded and enhanced to include more features and provide more services. This requires modification of the software. This type of maintenance is known as the Adaptive Maintenance

Perfective Maintenance
This is actually the most common type of maintenance encompassing enhancements both to the function and the efficiency of the code and includes all changes, insertions, deletions, modifications, extensions, and enhancements made to a system to meet the evolving and/or expanding needs of the user. A successful piece of software tends to be subjected to a succession of changes resulting in an increase in its requirements. This is based on the premise that as the software becomes useful, the users tend to experiment with new cases beyond the scope for which it was initially developed. Expansion in requirements can take the form of enhancement of existing system functionality or improvement in computational efficiency.

Though efforts have been made to develop error free systems, but no system is perfect, room for improvement is always there. Thus proper documentation for the system has been done so that it will be easy to handle any breakdown or any other type of system maintenance activity.

39

9. MODULES IN THE PROJECT

Following are the modules of our application: Hostels Inventory Gate pass

Hostels
In this module, all the information regarding the various hostels of the college, their wardens, the floors in a particular hostel, the rooms on each floor, the mess etc will be provided. It will maintain the record of each and every room allotted to various students on a particular floor in a particular hostel. It will also maintain the information about the students. Moreover information about when a student is going to vacate, how many rooms are vacant and at which floor in which hostel, what kind of room a student is taking 1-seater, 2-seater or 3-seater, whether it is ordinary or AC.

Inventory
The inventory module will include the details regarding the hostel fee, mess fee, the issued facilities to the students like matrices, quilts, blankets, pillows, buckets and other necessary things. A full-fledged record will be kept and maintained for this. Using this record, it will become very easy for the warden and other

40

authenticated authorities to maintain a check on each and every thing. It will also become very easy to allocate various resources to the students, moreover maintaining the record of the resources.

Gate pass
Basically, this module will keep the record regarding the entry and exit of the students. Every student will be provided a gate pass id that will maintain a check on his/her entry and exit time. It will also maintain a record of the students coming late to the hostel than the prescribed time limit. Moreover a record is maintained whenever a student goes for a vacation or at home.

41

BIBLIOGRAPHY:

42

Books Referred ASP .Net 3.5 for Professionals ASP.Net 2.0 unleashed

Websites Referred http://msdn.microsoft.com/en-us/library/default.aspx http://www.w3schools.com/ http://www.dotnetspider.com/