Student Help Center - Project Report

STUDENT HELP CENTER

A major project report submitted to

Rajiv Gandhi Proudyogiki Vishwavidhyalaya, Bhopal

in partial fulfillment of the award of

the degree of

Bachelor of Engineering

in

Computer Science

DEPARTMENT OF COMPUTER SCIENCE

SUSHILA DEVI BANSAL COLLEGE OF TECHNOLOGY

INDORE – 453331

Page | 1www.pankajjha.co.nr

STUDENT HELP CENTER

A major project report submitted to

Rajiv Gandhi Proudyogiki Vishwavidhyalaya, Bhopal

in partial fulfillment of the award of

the degree of

Bachelor of Engineering

in

Computer Science

Project Guide: Submitted By:

Mrs. Ruchi Vijaywargiya Pankaj Kumar Jha

Mr. Neeraj Mehta (0829cs061065)

Sudhir Kumar

(0829cs061109)

DEPARTMENT OF COMPUTER SCIENCE

SUSHILA DEVI BANSAL COLLEGE OF TECHNOLOGY

INDORE – 453331


ACKNOWLEDGEMENT

We express deep gratitude for enthusiasm and valuable suggestions that we got from our

guide Mrs. Ruchi Vijaywargiya and Mr. Neeraj Mehta for successful completion of the

project. This project was not possible without the invaluable guidance of our project guide.

We are also thankful to our project coordinator Mr. Arjun Singh Parihar, for his technical

guidance, encouragement and support.

We are deeply indebted to Mrs. Ruchi Vijaywargiya, Head Department of Computer

Science & Information Technology Engineering, for providing us support and resources for

successful completion of this project.

We pay deep regards to our Director Dr. N. Dagdee and our Executive Director Dr. P.C.

Sharma, who are instrumental in setting standards for the students to achieve. Finally, we are

thankful to all the people who are related to the project directly or indirectly.

Pankaj Kumar Jha

(0829cs061065)

Sudhir Kumar

(0829cs061109)


SUSHILA DEVI BANSAL COLLEGE OF TECHNOLOGYINDORE, 453331

CERTIFICATE

This is to certify that PANKAJ KUMAR JHA (0829CS061065), SUDHIR

KUMAR (0829CS061109) have completed their project work, titled

“STUDENT HELP CENTER” as per the syllabus and have submitted a

satisfactory report on this project as a part of fulfillment towards the degree of

“BACHELOR OF ENGINEERING” (Computer Science) from RAJIV

GANDHI PROUDYOGIKI VISHWAVIDHYALAYA,BHOPAL.

Signature Signature

Internal Examiner External Examiner


Table of Contents

1. Introduction........................................................................................................................7

1.1 Purpose........................................................................................................................71.2 Scope...........................................................................................................................71.3 Problem in Existing System........................................................................................71.4 Statement of Problem..................................................................................................7

2. Software Requirement Analysis.........................................................................................9

2.1 Introduction.................................................................................................................92.1.1 Purpose...............................................................................................................102.1.2 Document Conventions......................................................................................102.1.3 Intended Audience and Reading Suggestions....................................................102.1.4 Product Scope.....................................................................................................112.1.5 References..........................................................................................................11

2.2 Overall Description...................................................................................................112.2.1 Product Perspective............................................................................................112.2.2 Product Functions...............................................................................................122.2.3 User Classes and Characteristics........................................................................122.2.4 Operating Environment......................................................................................122.2.5 Design and Implementation Constraints............................................................132.2.6 User Documentation...........................................................................................13

2.3 External Interface Requirements...............................................................................132.3.1 User Interfaces...................................................................................................132.3.2 Hardware Interfaces...........................................................................................132.3.3 Software Interfaces.............................................................................................132.3.4 Communications Interfaces................................................................................14

2.4 Functional Requirement............................................................................................142.4.1 System Features.................................................................................................14

2.5 Other Nonfunctional Requirements...........................................................................142.5.1 Performance Requirements................................................................................152.5.2 Safety Requirements..........................................................................................152.5.3 Security Requirements.......................................................................................15

2.6 Project Plan................................................................................................................162.6.1 Team Members...................................................................................................162.6.2 Division of Work................................................................................................162.6.3 Time Schedule....................................................................................................16

3. Analysis............................................................................................................................17

3.1 Methodology Used....................................................................................................173.2 Use Case Diagram.....................................................................................................17

3.2.1 Student Use Case................................................................................................183.2.2 Faculty Use Case................................................................................................193.2.3 Librarian Use Case.............................................................................................203.2.4 Administrator Use Case.....................................................................................21

3.3 Activity Diagram.......................................................................................................223.3.1 Activity Diagram of Student & Faculty.............................................................223.3.2 Activity Diagram of Librarian...........................................................................233.3.3 Activity Diagram of Administrator....................................................................24

3.4 Sequence Diagram.....................................................................................................253.5 Class Diagram...........................................................................................................26

4. Design..............................................................................................................................27

4.1 Architectural Design..................................................................................................27


4.1.1 System Architecture Diagram............................................................................274.2 Database Design........................................................................................................27

4.2.1 Interface Design:................................................................................................284.2.2 Data Dictionary..................................................................................................29

4.3 User Interfaces...........................................................................................................30

5. Implementation................................................................................................................34

5.1 Language and database system used for the implementation....................................345.2 Features of language and database used for the system............................................345.3 Reason for selecting database and language used.....................................................355.4 Description of third party tool used...........................................................................36

6. Testing..............................................................................................................................37

6.1 White box Testing.....................................................................................................376.2 Black Box Testing.....................................................................................................376.3 Test case and results..................................................................................................37

7. Future Scope and Limitations..........................................................................................39

7.1 Scope.........................................................................................................................397.2 Limitation..................................................................................................................39

8. Conclusion........................................................................................................................40

9. References........................................................................................................................41


1. Introduction

1.1 Purpose

The main purpose of this web application is to provide complete solution to a student

regarding difficulties faced by him in a college. So it is useful to the End Users to know what

are the requirements and recommendations of the website. Developers can use this

application to enhance the developed website or may develop a new website right from

scratch. This is also knowledgeable for the users to get the information about database

handling and maintenance.

1.2 Scope

This project is intended to all educational organizations who want to manage the information

about the all faculty & students. Administrator can insert, delete, and update the information

of all faculty & students. Normal user can only retrieve the information about him. eLibrary,

Online assessment submission, online attendance status of students, mid semester and RGPV

results, Technical Support can be done by this website. Student & faculty can request

important documents & download using this website.

1.3 Problem in Existing System

The problem faced by any organizations or colleges is how they inform absent students about

their attendance and assignment regularly, this web application is better platform for both

students and faculties to resolve their problems. Students are also faced problems regarding

issue and returns of book in time to the librarian. They can also suggest the book which is

helpful for him.

1.4 Statement of Problem

The various problems faced by the students are that where they can gather information about

the college and how they know about the college. Students are always in doubt for selecting

right or best college. If new student which are not belong to that state or country, they faced a

lot of problems related to college information, city information, transportation detail, and

hostel or accommodation information. Students are also in doubt if they are inside college is


that where they get information about the various facilities provided by the college like

account section, Labs information, Assessment submission process, Mid semester scheduling

information and so many. Parents of student which cannot come college and want to get

information about their candidate but due to manual work they get very few information or

sometimes they don’t.


2. Software Requirement Analysis

2.1 Introduction

This Student Help Center is developed for an educational organization which provides

various services, events & information about their institution for the students and faculty.

Student Help Center provides details of the careers information and various facilities offered

to students studying at the College. It provides various utilities needed by the student for their

project works.

Student Help Centre provides information for students as well as faculty. Faculties have the

facility to provide online notes and assignment needed by the students.

Student Help Center provides online assessment & notes posting facilities in doc or pdf

format for Faculty and online assessment submission for students.

Student Help Center provide eLibrary facility in which student and faculty can read various

books, journals and magazines available in our library. Student can download various course

related books through it. Students can request a book for issue or deposit to librarian.

Student Help Center provides Technical Support for Students and faculties for find a solution

about their hardware as well as software related problems. They can download software also.

Student help center also provides information regarding admission criteria as well as

branches available in college.

Student Help Center maintains the whole database of the students and the faculties who so

ever is concerned with the college. Various information regarding mid semester and rgpv

final exams are updated along with the facility to lookup the results.

Student Help Center provides online feedback form. Student can post online feedback to the

faculty.


2.1.1 Purpose

This project is intended to all educational organizations who want to manage the information

about the all faculty & students. Administrator can insert, delete, and update the information

of all faculty & students. Normal user can only retrieve the information about him. eLibrary,

Online assessment submission, online attendance status of students, mid semester and RGPV

results, Technical Support can be done by this website. Student & faculty can request

important documents & download using this website

2.1.2 Document Conventions

Main headings:

Font: Times New Roman 18 BOLD

Sub Heading:

Font: Times New Roman 14 BOLD

Body text:

Font: Times New Roman 12

2.1.3 Intended Audience and Reading Suggestions

End Users: End users are the one’s who will be using website the most. This SRS clearly

suggests the requirements of the web application. So it is useful to the End Users as well to

know what are the requirements and recommendations of the website.

Developers: The SRS is also useful to the developers who wish to develop their own website.

They can use SRS as directly to enhance developed website or may develop a new website

right from scratch.

Testers: Because the website is large in size, all the testers testing the website should read

SRS carefully to go through all the links of the website during testing.


2.1.4 Product Scope

This project is intended to all educational organizations who want to manage the information about

the all faculty & students. Administrator can insert, delete, and update the information of all faculty &

students. Normal user can only retrieve the information about him. eLibrary, Online assessment

submission, online attendance status of students, mid semester and RGPV results, Technical Support

can be done by this website. Student & faculty can request important documents & download using

this website.

2.1.5 References

Dynamic Web Publication Second Edition Tech Media

“Mastering in ASP” Mac Millan

Beginning of Visual C# 2005 by Wrox

Professionals of Visual C# 2005 by Wrox

2.2 Overall Description

2.2.1 Product Perspective

Since all the educational organizations have website which provide various

information regarding their organization but not much helpful for student as well as faculty.

All organization must to record all the information about student & faculty, library,

attendance & results. As the data is huge it is tiresome to keep up the paper work for the

same. Therefore it is necessary to provide an online web portal which helps the organizations

to retain the complete record of the students & faculties & also provide extra services for

student and faculty. There are much more website available to keep the information. But,

there is some of the aspect which is unturned till now like online assessment submission,

elibrary & chatting facility. Due to this problem we need to develop this website, which

provides various services & events for students and faculty & replace all existing websites.


2.2.2 Product Functions

User can login with user id and password

User can retrieve their information.

User can find online assessment and notice board, online technical support

User can see online attendance sheet

A way in which user can request any book, magazine, journal

User can easily download an important documents regarding their study purpose

A way in which a student can see their midsem and rgpv results

A way in which the various facility provided by the organization can be easily

available on this website.

2.2.3 User Classes and Characteristics

Administrator: - He can perform all operation specified in website.

Normal user: -He can only retrieve the information regarding to him

2.2.4 Operating Environment

Software Requirement:

S.No Softwares

1. MS Visual Studio 2005 For front End Design

2. SQL Server 2000 For Database Task

3. Adobe Photoshop CS-4 For Editing & Creating Photo

4. Adobe Flash Professional CS-4 For Developing & Editing Flash Movie

5. IE Tester For Testing Web Pages in Various IE

6. Windows XP Platform for performing all these tasks

7. IIS For running Website In a System

Hardware Requirement

S.No

1. Processor Pentium IV and above

2. RAM 256MB

3. Processor Speed 1.6 GHz and above


2.2.5 Design and Implementation Constraints

Designer should have knowledge about technology specified in a requirement specification

and development should be intended to requirements specified during requirement Analysis.

2.2.6 User Documentation

The solution must have enough documentation to teach the users how to use this website. The

documentation provided in this web application should be clear enough to act as the first line

of support for any problem. This web application will work on any windows based operating

system. This web application needs proper maintenance and updating every day. Web

application SHC is applicable only through internet connection.

2.3 External Interface Requirements

2.3.1 User Interfaces

We will provide a very easy GUI which will be very helpful to the operators. And it will

generate an appropriate error message if anything goes wrong with the entry or anything else.

In this if customer not having user id then he can’t see the details because we will provide a

unique id to every customer for its product and if the customer lost that id then he must

inform to the service station for its id.

2.3.2 Hardware Interfaces

As Such there is no hardware requirement for this system. We will try to make this system

with minimum resources so that it will be fruitful to every customer to run this on very low

configuration too, but for this we need a net connection which will connect them to the

server.

2.3.3 Software Interfaces

This system would run on operating systems like Windows XP, Vista, and Windows 7 having

.NET framework 2.0 or upper. Database is maintained by the SQL SERVER 2000/2005 and

the Programming tool used is Microsoft Visual Studio 2005. A web browser is needed to run

this application.


2.3.4 Communications Interfaces

The Customer must connect to the Internet to access the Website:

Dialup Modem of 52 kbps.

Broadband Internet.

Dialup or Broadband Connection with a Internet Provider.

2.4 Functional Requirement

2.4.1 System Features

2.4.1.1 Description and Priority

Proposed Database is intended to store, retrieve, update, and manipulate information related

to the help centre which include

Student information

Faculty details

2.4.1.2 Stimulus/Response Sequences

Responses for Administrator: The administrator can Login and Logout. When the

Administrator Logs into the help center Application, the system will check for validity of

login .If the Login and password are valid, the response to this action is the administrator will

be able to modify, view, add, deleting and all other functions that can be performed on the

database.

2.5 Other Nonfunctional Requirements

Non-Functional Requirements: Functional requirements specify only working requirements

of the system. Non-functional requirements encompass the operating environment

requirements specifying the hardware and software required for the proposed system to work

as well as the performance and ergonomics requirement.


2.5.1 Performance Requirements

For the effective performance of the system a minimum of RAM requirement is 512MB or

more of OS like XP and 1GB for OS like Vista and Windows 7. The performance would also

be affected by the other software installed on the machine. The browsing speed of the Internet

Connection would play a crucial role on the performance of the system. Preferable browsing

speed would be 1.5Mbps or more. At any instance of time any number of users can access the

website and download the information required.

2.5.2 Safety Requirements

The user must have a registered account to use all facility of the website. The administrator

account is needed to create the login id and password of normal user, and then the normal

user can retrieve the data only.

2.5.3 Security Requirements

We are going to develop a secured database for the Help centre. There are different categories

of users namely student, faculty, administrator etc. Depending upon the category of user the

access rights are decided. It means if the user is an administrator then he can be able to

modify the data, delete, append etc. All other users only have the rights to retrieve the

information about database. User ID and Password is asked to confirm that the User is the

authenticate person. The safety part of the system will be based on the facilities provided by

the OS and the inherent security features provided by the operating system.


2.6 Project Plan

2.6.1 Team Members

Pankaj Kumar Jha

0829cs061065

Email Id- [email protected]

Sudhir Kumar

0829cs061109

Email Id- [email protected]

2.6.2 Division of Work

The whole project is divided into four parts. These are as

Analysis including functional and non functional requirements

Design including architectural, database and interface design

Coding

Testing

The roles of team members individually:

1st Member- 1st member has performed the functional portion of analysis, database design as

well as interface design.

2nd Member- 2nd member has performed non – functional portion which contains requirements

gathering, front end design and interface design.

2.6.3 Time Schedule

Tentative time requirement for a part of project to be completed is approximately 3 to 4

months.


3. Analysis

3.1 Methodology Used

We are using object oriented approach in developing this application. The key ideas of the

object oriented approach are:

Objects

Encapsulation

Class and Inheritance

Instances and Instantiation

Methods and Messages

One of the main principles in the object oriented (OO) approach is that of abstraction, not of

data structures and processes separately but both together. In developing our project, we have

created different classes and defined methods for them which are called through objects. We

have defined the structure of an object to represent student and then a new object for faculty.

3.2 Use Case Diagram

A Use Case Diagram is a type of behavioral diagram defined by the UML and created from a

Use Case analysis. It shows the system’s use cases as icons, and their relationships to other

use cases and the actors of the system. It also displays the relationship among actors and use

cases.


3.2.1 Student Use Case

The given below Use Case Diagram consist an actor which is student and also contents of

events performed by students. From this use case it is clear that which events are done by

students or say what privileges are given to students.


3.2.2 Faculty Use Case

The given below Use Case Diagram consist an actor which is faculty and also contents of

events performed by faculty. From this use case it is clear that which events are done by

faculty or say what privileges are given to faculty.


3.2.3 Librarian Use Case

The given below Use Case Diagram consist an actor which is librarian and also contents

of events performed by librarian. From this use case it is clear that which events are done

by librarian or say what authentication are provided to librarians.


3.2.4 Administrator Use Case

The given below Use Case Diagram consist an actor which is administrator and also

contents of events performed by administrator. From this use case it is clear that

administrator is super controller of all users and also activates or deactivates their

accounts.


3.3 Activity Diagram

3.3.1 Activity Diagram of Student & Faculty


3.3.2 Activity Diagram of Librarian


3.3.3 Activity Diagram of Administrator


3.4 Sequence Diagram


3.5 Class Diagram


4. Design

4.1 Architectural Design

4.1.1 System Architecture Diagram

4.1.2. Description of Architectural Design

System architecture represents the necessary strategic design decisions sufficient to

form that system.

A stable architecture is essential to every successful system for two reasons.

First, the creation of a stable architecture helps drive the highest risks out of the

project.

Second, the presence of a stable architecture provides the basis upon which the system

may be continuously evolved with minimal scrap and rework.

In web application development, three-tier architecture refers to separating the

application process into three specific layers.

It improves performance and scalability

4.2 Database Design

Microsoft SQL Server data is stored in Database. The data in a database is organized into the

logical components visible to users. A database is also physically implemented as two or

more files on disk. When using a database, you work primarily with the logical components

such as tables, views, procedures and users. The physical implementation of files is largely

transparent. Typically, only the database administrator needs to work with the physical


implementation. Each instance of SQL Server has four system databases (masters, model,

tempdb, and msdb) and one or more user database. Some organizations have only one user

database, containing all the database for their organization. Some organizations have different

databases for each group in their organization, and sometimes a database used by a single

application. For example, an organization could have one database for recording uploaded

documents, one to maintain downloaded documents and so on. Sometimes, an application

uses only one database, other applications may access several databases. When connecting to

an instance of SQL Server your connection is associated with a particular database on the

server. This database is called the Current Database. You are usually connected to a database

defined as your default database by the system administrator. SQL Server allows you to

detach databases from an instance of SQL Server, then reattach them to another instance, or

even attach the database back to the same instance. If you have a SQL Server database file,

you can tell SQL Server when you connect to attach that database file with a specific

database name.

4.2.1 Interface Design:

Interface Design focuses on three areas of concern:

The design of interfaces between website components.

The design of interfaces between the website and other non-human producers and

consumers of information.

The design of the interface between a human and the computer.

User interface design creates an effective communication medium between a human and a

computer following a set of interface design principles, design identities interface objects and

actions and then creates a screen layout that forms the basis for a user interface prototype. A

website developer designs the user interface by applying an iterative process that draws on

predefined design principles. It begins with the identification of user, task, and environment

requirements.

The golden rules for the interface design:


a) Place the user control-

Provide for flexible interaction.

Hide technical internals from the casual user.

Allow user interaction to be interruptible and undoable.

Streamlined interaction as skills level advance and allow the interaction to be customized.

Design for direct interaction with objects that appear in the screen.

b) Reduce the user’s memory load-

Reduce demand on short term memory.

Establish meaningful defaults.

Disclose information in a progressive fashion

Defined shortcuts that is intuitive.

The visual layout of the interface should be based on a real world metaphor.

c) Make the interface consistent

Allow the user to put the current task into a meaningful context.

Maintain consistency across a family of application.

4.2.2 Data Dictionary

Table - Registration

Field Name Data type Size Description

Fname Varchar 50 First Name

Lname Varchar 50 Last Name

UserId Varchar 50 User Id

PWD Varchar 15 Password

Email Varchar 50 Email


4.3 User Interfaces

Fig. 4.3.1 Student Help Center – Home Page


Fig. 4.3.2 Student Help Center – Registration Page


Fig. 4.3.3 Student Help Center – Login


Fig. 4.3.4 Student Help Center – Student Control Panel Page


5. Implementation

5.1 Language and database system used for the implementation

Scripting language used is C#:

C# is intended to be a simple, modern, general-purpose, object-oriented

programming language.

C# is more type safe than C++. The only implicit conversions by default are those

which are considered safe, such as widening of integers and conversion from a

derived type to a base type.

Database System used is Microsoft SQL Server 2000:

It is a full-featured relational database management system (RDBMS) that offers a

variety of administrative tools to ease the burdens of database development,

maintenance and administration.

It optimizes queries efficiently, it fine tunes the indexes, it performs efficient

transactions build efficient stored procedures and analyze the execution plans.

5.2 Features of language and database used for the system

Main Features of C#

C# supports Data Encapsulation, inheritance, polymorphism, interfaces.

(int, float, double) are not objects in java but C# has introduces structures(structs)

which enable the primitive types to become objects

int i=1;

string a=i.Tostring(); //conversion (or) Boxing

Scalable and Updatable

.NET has introduced assemblies, which are self-describing by means of their

manifest. Manifest establishes the assembly identity, version, culture and digital

signature etc. Assemblies need not to be register anywhere. \

To scale our application we delete the old files and updating them with new ones. No

registering of dynamic linking library.


Updating software components is an error prone task. Revisions made to the code can

affect the existing program C# support versioning in the language. Native support for

interfaces and method overriding enable complex frame works to be developed and

evolved over time.

Microsoft® SQL Server™ 2000 features include:

Ease of installation, deployment, and use.

SQL Server 2000 includes a set of administrative and development tools that improve

upon the process of installing, deploying, managing, and using SQL Server across

several sites. SQL Server 2000 also supports a standards-based programming model

integrated with the Windows DNA, making the use of SQL Server databases and data

warehouses a seamless part of building powerful and scalable systems. These features

allow you to rapidly deliver SQL Server applications that customers can implement

with a minimum of installation and administrative overhead.

Data warehousing

SQL Server 2000 includes tools for extracting and analyzing summary data for online

analytical processing. SQL Server also includes tools for visually designing databases

and analyzing data using English-based questions.

5.3 Reason for selecting database and language used

The choice of C# and sql server 2000 is one of subjective preference.

Advantage of C#:

While many would argue that C++ is object-oriented, C# goes to another level. Even

simple data types can be treated as objects, meaning that an int has methods

associated with it

C# attempts to simplify the syntax to be more consistent and more logical while also

removing some of the more complex features of C++. For example, C# does away

with pointers. As a type-safe language, C# doesn't allow direct memory manipulation,

so pointers are no longer needed in C#.

C# has the ability to allow you to interoperate with any other language on the .NET

platform. C# also supports the concept of error handling across different languages.


Advantage of Server 2000:

SQL Server 2000 is generally accepted as easier to install, use and manage

5.4 Description of third party tool used

Crystal report 9.0 as:

For IT Professionals and Developers: More control over data connectivity.


6. Testing

6.1 White box Testing

White box testing also called as Glass Box Testing, is a test case design method that uses the

control structure of procedural design to derive test cases logical paths through the s/w are

tested by providing test cases that exercise specific sets of conditions and/or loops.

6.2 Black Box Testing

It alludes to test that are conducted at the s/w interface it is used to demonstrate that s/w

functions are operational , input is properly accepted and output is correctly produced and the

integrity of external information is maintained. It examine fundamental aspect of system with

little regard for the internal logical structure of the s/w it is also called Behavioral testing. It

enables the s/w engineering to derive sets of input conditions that will fully exercise all

functional requirement of program. It attempts to find error in following categories:

Incorrect or missing function.

Interface Errors.

Error in a Data structure or external database access.

Behavioral or performance error.

Initialization and termination error.

6.3 Test case and results

Module name: Registration

Input: Fname, Lname, UserId, PWD, Email, RePWD.

Output: The user is registered and redirected to Student Control Panel page.

Project Name:


Student Help Center

Test Case Name:Registration

Description:The responsibility of this module is to register the student and then redirect the student control panel

Scenario# Function to Test Expected Results Actual Result Remark1 Validity of duplicate

entryThe system should validate for the same name and user id

The system validated the same name and user id

Pass

2 Redirecting user based on the role that he belongs to

The user is redirected to the role’s home page

The user was redirected to the role’s home page

Pass

3 The user should be prompted if the password and confirm password are incorrect

The user should be prompted if password does not match

The user was prompted

Pass

4 No Empty fields must be allowed

The system should prompt user for the empty fields

The system prompted user of the empty fields

Pass

Conclusion: The student is registered successfully and is redirected to student control panel.


7. Future Scope and Limitations

7.1 Scope

User will have unique Id & Password.

Online assessment submission.

Administrator can get full access to database via his\her unique Id & password.

As it is a web based system so student can check notice board and attendance status

online through a unique code provided to him/her from this website.

User friendly Environment.

Strong Database Backup.

7.2 Limitation

As it is web based system so net connection with efficient speed is compulsory for

better performance.

.net framework 2.0 and above is necessary.

System must have a web browser

.


8. Conclusion

This project can be come in use at educational organization such as university,

Colleges, Institution. The Student Help Center can be extended to incorporate

following features.

Incorporating online technical support facility for student & faculty.

As this project is designed as per the requirements of educational organization,

it can be extended for larger organization satisfying their requirement as well.


9. References

SQL, PL/SQL The Programming language Of Oracle By Ivan Bay Ross.

Software Engineering by Roger.S.Pressmen


Documents

Student Help Center - Project Report