You are on page 1of 29

Project Report

On
COLLEGE WEBSITE MANAGEMENT
SYSTEM.

SUBMITTED BY:Preeti Bhati


Rekha Kamariya
MCA 5TH SEM iii Year

SUBMITTED TO:Sunita Mam

Index
SN

Particular

1.

Introduction

2.

System Analysis

Page

Introduction
Software Requirements Specifications
Objective of system
3.

Feasibility Study

4.

System Design
Input & output
Table design

5.

Equipment Employed

6.

Data Flow Diagram

7.

Entity Relationship Diagrams

8.

Screen Slots of Form

9.

Testing & Debugging

10.

Conclusion

11.

Coding

12.

Bibliography

1. Introduction:1) Purpose:
The purposes of this application are as follows:

The software is for automation of college


It provides following facilities

to Operator :
o Can enter details related to a particular course
o Can provide membership to students

Admin :
o Can read and write information about any member.
o Can update, create, and delete the record of membership as per
requirement and implementation plans.

2) Scope :
The different areas where we can use this application
are :

Any education institute can make use of it for


Providing information about courses, faculty, well-equipped labs and classroom.

It can be used in colleges and modifications can be easily done according to


requirements.

3) Overview:
Project is related to college website management which provides

services to its

members. Any person can become a member of the college by filling a prescribed form.
They can get themselves registered easily.

4) Functionality:

Online membership.

Keeps the track of admission and students n entire college activities .

ii) Objective Of The Project :The main objective while implementing the project College website Management System
was to minimize the work and at the same time increase the speed of the work done.

This new system is built with the following objective:


1)

Information retrieval will become easy.

2)

Maintenance of database as well as overall project

will

become

easy.
3)

Security

measure

will

be

adopted,

by

maintaining

the

login

of

username and the password.


4)

Data

redundancy
system

will
is

built

be

greatly

using

looking into duplication of efforts


procedures.

reduced

ASP.NET

as

because
front-end.

this

new

It

entails

, bottlenecks and inefficient existing

System Analysis
2) (i) Introduction :System analysis is the performance management and documentation of activities related
to the four life cycle phases of any software namely:

The Study Phase

The Design Phase

The Development Phase

The Operators Phase

System analysis is a vast field of study through which system analyst puts his thoughts
and searches for the solution of problem. He has to get a clear idea of what he has in hand
and what he has to produce. He has to extract the essence of expectations. He has to
satisfy the user in the very possible way. System analysis needs and should include the
following steps of study:
Study of current methods, the basic inputs available and output desired.
The splitting of a variable inputs into (.dbf) files so as to reduce
redundancy and increase consistency.
Give the idea of key field (if any) .
Ideas regarding code generation.

Software Analysis starts with a preliminary analysis and later switches on to a detailed
one. During the preliminary analysis the Analyst takes a quick look at what is needed and
whether the cost benefits. Detailed analysis studies in depth all the cornered factors,
which builds and strengthens the software.
A system study is a step-by-step process used to identify and then developed the software
needed to control the processing of specific application. System study is also known as
SDLC (Software Development Life Cycle).

Steps of SDLC are:


1. Problem Definition
2. Feasibility Study
3. System Analysis
4. System Design
5. Implementation
6. Post Implementation
7. Maintenance

2)(ii) Software Requirements Specifications ;SRS (Software Requirement Specification) is a document that completely describes what
the proposed should do, without describing how the software does it.
Purpose :

The purpose of the project is to develop a system which is user

friendly, easy to use , maintain and satisfies all the requirements of the user.
Performance Requirement
1) The operation time should be small and the throughput should be high.
2) It should produce timely and accurate result.

Software Quality Attributes

i)

Maintainability Since it is directly associated with the database, so


there is very little maintainability problem with this tool.

ii)

Portability Since there is very limited usage of separate forms, this tool
is very much portable. This tool uses several canvases on the same form.

iii)

Flexibility This tool is very much flexible for future enhancements.

2) (iii) Objectives of System : To reduce workload of staff.


To reduce the delay in processing time.
To reduce the delay in receipt generation.
To provide the user-friendliness in all possible ways.
To provide greater flexibility.
Make maintenance changes easy, To store data in a centralized location to reduce
redundancy and increase consistency.
2(iv) Proposed System Environment :The system environment can be classified into two categories
Hardware environment
Software environment

Hardware Environment

The application front-end (client) will be designed on machines with


Windows 98/ Window XP, Pentium III processors, 64/128 MB RAM.
The database will be running on Windows OS, Pentium III processors, 64
MB RAM.
Mouse as pointing device.

Software Environment
The application front end will be designed using ASP.NET 6.0.
The database has been designed on Microsoft Access (Office Package ).

3) Feasibility Study:. FEASIBILITY STUDY impact of the organization, ability to meet needs and
effective use of the resources. It focuses on these major questions:
1. What are the users demonstrable needs and how does a
candidate system meet them?
2. What resources are available for given candidate system?
3. What are the likely impacts of the candidate system on
the organization?
4. Whether it is worth to solve the problem?

Steps in feasibility analysis

Eight steps involved in the feasibility analysis are:

Form a project team and appoint a project leader.

Prepare system flowcharts.

Enumerate potential proposed system.

Define and identify characteristics of proposed system.

Determine and evaluate performance and cost effective of each proposed system.

Weight system performance and cost data.

Select the best-proposed system.

Prepare and report final project directive to management.

In feasibility study phase we had undergone through various steps which are describe
as under:
1. Identify the origin of the information at different level.
2. Identify the expectation of user from computerized
system.
3. Analyze the draw back of existing system (manual)
system.

Types :3.1) Technical feasibility:

A study of resource availability that may affect the ability to achieve an


acceptable system. This evaluation determines whether the technology needed for
the proposed system is available or not.

3.2) Economical feasibility:Economic justification is generally the Bottom Line consideration for most
systems. Economic justification includes a broad range of concerns that includes cost
benefit analysis. In this we weight the cost and the benefits associated with the
candidate system and if it suits the basic purpose of the organization.

3.3)Operational Feasibility:it is mainly related to human organizations and political aspects. The points to be
considered are:
What changes will be brought with the system?
What organization structures are disturbed?

3.4) Schedule feasibility:Time evaluation is the most important consideration in the development of project. The
time schedule required for the developed of this project is very important since more
development time effect machine time, cost and cause delay in the development of
other systems. A reliable College Website Management System can be developed in the
considerable amount of time

4.SYSTEM DESIGN :DESIGN STRATEGY

The design strategy is a vital aspect of the system to be developed. The design of the
software reflects the basic understanding of the problem. For designing a good system
what we have to be is to get correct definition of the problem and analyze the problem
thoroughly.
The design of a system should be such that if a small portion is changed. The rest of the
system should be unaffected. This is the flexibility of the system. Greater the system
flexibility greater will be the system reliability. While carrying out the job of designing of
a new system one has to consider many factors. These factors include the drawbacks and
limitations of the present manual system as well as of the features and advantages of the
proposed system. It should be designed in such a manner that even a layman can run it
without any difficulty.

An important quality of a software must enjoy is user friendliness. It can be achieved in


many ways like providing menu, giving context sensitive help, doing automatic
validation to input data, etc. Another main factor is speed efficiency. In order to achieve
speed efficiency, the program should be designed accordingly and the user is provided
with a compiled copy of the software package with necessary data file format rather than
source code.
Design of input and output formats is equally important for any design. The output
format should be designed in such a way that it must reflect all the required information
in detail. The design of the database itself such as type of data stored, size of data etc.
Some of the decisions made during database design are:
Which data items are to be recorded and in which database.
Length of each record, based on the characteristics of the data items on which it
is based.
Data whos unauthorized change must be prevented.
Data, which must be avoided from redundancy.
Maintenance of data integrity etc.
Avoid over writings.
Prevents invalid data access and changes.
Having all this, a positive interaction with clients at every stage of development is the
core around which the software is built.

4) (i) INPUT DESIGN


Input design is the process of converting user-originate inputs to a computer-based
format. The goal of design input data is to make data entry as easy, logical and free. The
most common source of data processing errors is inactive input data. Effective design of
the input data minimizes the error made by data entry operators. Catching errors on input
is far less costly than correcting after data storage is complete.

User-friendly input design enables quick error detecting and correction. Verification and
validation is the most important in input design. Since the system is used interactively, it
has two types of inputs. Interactive input-which is the point contact of the user with the
system and the input to the internal system i.e. Databases. For full efficiency of the
system, it is necessary that the input must be accurate. Since the user of the system may
not be a technical person and may not know input concepts so it is required that he warn,
prevent and correct invalid data entry.
There are many ways that can be designed to handle such a situation. We can prevent the
user entering invalid data into the databases by warning, neglecting or messaging
appropriately. The user is then allowed to input correct data. Some help provisions may
aid the user to point out the error. In this system inputs are collected from terminals
through keyboard.

4) (ii)OUTPUT DESIGN
Output design has been an ongoing activity from the very beginning of the project. The
objective of the output design is to convey the information of all past activities, current
status and to emphasize important events. The output generally refers to the results and
information that is generated from the system.The output design of the system is
accomplished keeping in mind the following activities:
Determine what information is to display.
Decide whether to display or print the information retrieved, processed, generated
from the system.
Arrange the presentation of information in an acceptable format.
Decide how to distribute the output to the intended recipients.
In the output design phase one or more output media can be selected. Out of which the
most common ones are CRT displays and print out. Here only CRT display has been
attempted. A rapid enquiry is obtained from CRT displays. From design is made
interesting and attractive. Easy understanding and effectiveness is made possible.

Equipments Employed :i) Front End :MICROSOFT ASP.NET

ASP.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.

ASP.NET Web Server Controls Overview


When you create ASP.NET Web pages, you can use these types of controls:

HTML server controls HTML elements exposed to the server so you can
program them. HTML server controls expose an object model that maps very
closely to the HTML elements that they render.

Web server controls Controls with more built-in features than HTML server
controls. Web server controls include not only form controls such as buttons and
text boxes, but also special-purpose controls such as a calendar, menus, and a tree
view control. Web server controls are more abstract than HTML server controls in
that their object model does not necessarily reflect HTML syntax.

Validation controls Controls that incorporate logic to enable you to what users
enter for input controls such as the TextBox control. Validation controls enable
you to check for a required field, to test against a specific value or pattern of
characters, to verify that a value lies within a range, and so on. For more
information, see ASP.NET Validation Controls.

User controls Controls that you create as ASP.NET Web pages. You can embed
ASP.NET user controls in other ASP.NET Web pages, which is an easy way to
create toolbars and other reusable elements. For more information, see ASP.NET
User Controls.

HTML Server Controls


HTML server controls are HTML elements (or elements in other supported markup, such
as XHTML) containing attributes that make them programmable in server code. By
default, HTML elements on an ASP.NET Web page are not available to the server.
Instead, they are treated as opaque text and passed through to the browser. However, by
converting HTML elements to HTML server controls, you expose them as elements you
can program on the server.
The object model for HTML server controls maps closely to that of the corresponding
elements. For example, HTML attributes are exposed in HTML server controls as
properties.
Any HTML element on a page can be converted to an HTML server control by adding
the attribute runat="server". During parsing, the ASP.NET page framework creates
instances of all elements containing the runat="server" attribute. If you want to reference
the control as a member within your code, you should also assign an id attribute to the
control.

The page framework provides predefined HTML server controls for the HTML elements
most commonly used dynamically on a page: the form element, the input elements (text
box, check box, Submit button), the select element, and so on. These predefined HTML
server controls share the basic properties of the generic control, and in addition, each
control typically provides its own set of properties and its own event.
HTML server controls offer the following features:

An object model that you can program against on the server using familiar objectoriented techniques. Each server control exposes properties that enable you to
manipulate the control's markup attributes programmatically in server code.

A set of events for which you can write event handlers in much the same way you
would in a client-based form, except that the event is handled in server code.

The ability to handle events in client script.

Automatic maintenance of the control's state. When the page makes a round trip
to the server, the values that the user entered into HTML server controls are
automatically maintained and sent back to the browser.

Interaction with ASP.NET validation controls so you can verify that a user has
entered appropriate information into a control.

Data binding to one or more properties of the control.

Support for styles if the ASP.NET Web page is displayed in a browser that
supports cascading style sheets.

Pass-through of custom attributes. You can add any attributes you need to an
HTML server control and the page framework will render them without any
change in functionality. This enables you to add browser-specific attributes to
your controls.

For details about how to convert an HTML element to an HTML server control, see How
to: Add HTML Server Controls to a Web Page Using ASP.NET Syntax.
Web Server Controls

Web server controls are a second set of controls designed with a different emphasis. They
do not necessarily map one-to-one to HTML server controls. Instead, they are defined as
abstract controls in which the actual markup rendered by the control can be quite
different from the model that you program against. For example, a RadioButtonList Web
server control might be rendered in a table or as inline text with other markup.
Web server controls include traditional form controls such as buttons and text boxes as
well as complex controls such as tables. They also include controls that provide
commonly used form functionality such as displaying data in a grid, choosing dates,
displaying menus, and so on.
Web server controls offer all of the features described above for HTML server controls
(except one-to-one mapping to elements) and these additional features:

A rich object model that provides type-safe programming capabilities.

Automatic browser detection. The controls can detect browser capabilities and
render appropriate markup.

For some controls, the ability to define your own layout for the control using
Templates.

For some controls, the ability to specify whether a control's event causes
immediate posting to the server or is instead cached and raised when the page is
submitted.

Support for themes, which enable you to define a consistent look for controls
throughout your site. For details, see ASP.NET Themes and Skins.

Ability to pass events from a nested control (such as a button in a table) to the
container control.

5) (ii) ABOUT BACK END:-

MICROSOFT ACCESS &


SQL SERVER 2008
Database: -A database is a set of data, organized for easy access. The database is the
actual data. It is the database that you will be accessing when you need to retrieve data.
Data Dictionary: -The data dictionary is a set of tables Access uses to maintain
information about the database. The data dictionary contains information about tables,
indexes, clusters, and so on.
DBA (Database Administrator): -The DBA is the person responsible for the operation,
configuration, and performance of the database. The DBA is charged with keeping the
database operating smoothly, ensuring that backups are done on a regular basis (and that
the backups work), and installing new software. Other responsibilities might include
planning for future expansion and disk space needs, creating databases and tablespaces,
adding users and maintaining security, and monitoring the database and retuning it as
necessary. Large installations might have teams of DBAs to keep the system running
smoothly; alternatively, the tasks might be segmented among the DBAs.

DBMS or RDBMS: -The Database Management System is the software and collection of
tools that manages the database. Access software is the DBMS. A Relational Database
Management System is a DBMS that is relational in nature. This means that the internal
workings access data in a relational manner. Access is an RDBMS.
Query: -A query is a read-only transaction against a database. A query is generated using
the SELECT statement. Users generally distinguish between queries and other transaction
types because a query does not change the data in the database.
Schema: -A schema is a collection of objects associated with the database.

Microsoft Access is a very effective DBMS tool which is generally used by all the users.
It is compatible with all types of systems & can be installed and used as and when
required.

6) Entity-Relationship Diagram :-

7)Data Flow Diagram (DFD) :-

8.) Future Scope :FUTURE SCOPE OF APPLICATION:


This application can be easily implemented under various situations.
We can add new features as and when we require. Reusability is
possible as and when require in this application. There is flexibility
in all the modules.
SOFTWARE SCOPE:

Extensibility: This software is extendable in ways that its original developers


may not expect. The following principles enhances extensibility like hide data
structure, avoid traversing multiple links or methods, avoid case statements on
object type and distinguish public and private operations.

Reusability: Reusability is possible as and when require in this


application. We can update it next version. Reusable software
reduces design, coding and testing cost by amortizing effort
over several designs. Reducing the amount of code also
simplifies understanding, which increases the likelihood that
the code is correct. We follow up both types of reusability:
Sharing of newly written code within a project and reuse of
previously written code on new projects.

Understandability: A method is understandable if someone other than the creator


of the method can understand the code (as well as the creator after a time lapse).
We use the method,
which small and coherent helps to accomplish this.

Cost-effectiveness: Its cost is under the budget and make within given time
period. It is desirable to aim for a system with a minimum cost subject to the
condition that it must satisfy the
entire requirement.

TESTING AND DEBUGGING


Software testing is a critical element of software quality assurance and represents the
ultimate reviews of specification, design and coding. Testing presents an interesting
anomaly of the software. During earlier definition and development phases, it was
attempted to build software from abstract concept to a tangible implementation.
The testing phase involves the testing of the developed system using
various set data. Presentation of test data plays a vital role in system testing. After
preparing the test data the system under study was tested using test data. While testing the
system by using test data errors were found and corrected. A series of tests were
performed for the proposed system before the system was ready for implementation. The
various types of testing done on the system are:
Unit Testing
Integration Testing
Validation Testing
User Acceptance Testing
System Testing

UNIT TESTING
Unit testing focuses verification effort on the smallest unit of software design, the
module. It comprises the set of test performed by the programmer prior to integration of
the unit into larger system. The testing was carried out during the coding stage itself. In
this step each module is found to be working satisfactorily as regards to the expected
output from the module.

INTEGRATION TESTING
Integration testing is a systematic technique for constructing the program structure while
at the same time conducting tests to uncover error associated within the interface. The
objective is to take unit tested modules and build a program structure that has been
dictated by design. All modules are combined in this step. The entire program is tested as
whole. And chaos in interfaces may usually result. A set of errors is encountered in such a
case.

The integration testing can be carried out using two methodologies:


# Top Down Integration
# Bottom Up Integration

The first one is done where integration is carried out by addition of minor modules to
major modules. While Bottom Up integration follows combination of smaller ones to
large one. Here Bottom Up Integration was encouraged. Even though correction was
difficult because the isolation of causes is complicated by the vastness of the entire

program, all the errors found in the system were corrected and then forwarded to the next
testing steps.

USER ACCEPTANCE TESTING


User acceptance of a system is the key factor for the success of any system. The system
under consideration was tested for users acceptance by constantly keeping in touch with
the perspective system user at the time of developing and making changes wherever
required. This is done with the regards to the following points:
A system may be defined as a set of instruction combined in the same form and directed
to some purpose.
Before any development is undertaken certain specifications are prepared which
objectively describe the application system. The System specifications are made after
consulting the end user managers of the relevant departments.
Software to be developed is planned on the basis of requirement of the user. The problem
definition statement description of present situation and goal to be achieved by news
system.
The success of system depends on how accurately a problem is defined, thoroughly
investigated carried out through choice of solution. User need identification and analysis
that are concerned with what the uses needs rather than what he/she wants. System
explains how to perform specific activities or task, which does what and what.

Scope & Result and Discussion:-

INTRODUCTION

Even the best system developed has some flaws or others. There always exist scope of
further improvement in the system. The effect of implementations of new computerized
system is found remarkable.
The following are the major improvement of the new system over the existing system.
A fully menu driven user-friendly computerized system has been developed
where the user can perform task like entering data, deleting and updating the
information with great ease.
All the operations are carried automatically preventing a lot of manual work.
Additional checks have also been incorporated into the system to avoid
duplications of data as far as possible.

SCOPE FOR FURTHER IMPROVEMENT:-

Every project whether large or small has some limitations no matter however diligently
developed. In some cases limitations is small while in other cases they may be broad also.
The new system has got some limitations. Major areas where modifications can be done
are as follows:

The security is limited so some additional arrangement could be made to provide


more security to the system.
There is no provision of complain handling so further it can be added.

MAIN ACHIEVEMENT OF THE SYSTEM:-

This project gives an overview of the College Website Management System


After entering into the project, user is left with several options via
a) The user can take new admissions.
b) The user can view the existing lists of students, which already have taken
admission.
c) The user can of course fee& take student record statements.
d) The user can also do several administrative works like managing,
modification of smart card & students entries.
It is a computerized system, which can be used very easily & effectively by the
administrators of the College Website Management System.

10) CONCLUSION :-

We come to a conclusion of our project that from a proper analysis of positive points
and constraints on the component, it can be safely concluded that this
product is a highly efficient GUI based component. This application is
working properly and meeting to all user requirements. This
component can be easily plugged in many other systems. So its a very
efficient working system and shall prove to be success etc.

10)Bibliography :

Beginning Java Objects: From Concepts to Code -by


Jacquie Barker)

Introduction to Java Programming (NIIIT publication)

The Complete Reference Java(McGrawhill; Herbert


Schildth- reprint 2008)

Introduction to MS-Access(Aptech)

Web Sites:

www.apache.org

www.wikipedia.com