79995348 Project Report Online Exam System 2011

Online Exam System and Data Sharing 2011

1

CAPSTONE PROJECT REPORT

ONLINE EXAMINATION SYSTEM AND DATA SHARING

Submitted by

Shoyab Mohammad Siddiquee

B-Tech –(Honers)-(CSE)

Reg no. 10805456

Under the Guidance of:

Faculty Coordinator

Ms.Saloni

Lecturer,CSE/IT School of Electronics and Electrical Engineering

Department of

Lovely School of Technology and Sciences

Lovely Professional University, Phagwara

July to December 2011


2

Declaration

I hereby declare that the project was entitled “ONLINE EXAMINATION SYSTEM AND

DATA SHARING” is an authentic record of my own work carried out at Lovely Professional

University as requirement of industry intern project for the award of degree of B.TECH

(HONERS)-CSE ,Lovely Professional University ,phagwara under the guidance of SALONI

(faculty coordinator) during July to December ,2011

(signature of student)

NAME:- Shoyab Mohammad Siddiquee

REG. NO.:-10805456

Date:-26 NOV 2011

Certified that the above statement made by the student is correct to the best of our knowledge and belief.

Faculty Coordinator

(signature)


3

Acknowledgement It is a pleasure of mine to find myself penning down these lines to express my sincere thanks to

all my coordinators to give me this opportunity of preparing this project, to enhance my

professional practice. I express my deep sense of gratitude to my project officer Ms. Saloni to

give me knowledge about the topic and concept related to this particular project. Without his

guidance I cannot imagine to complete my project on time.

My deepest gratitude to all my coordinators and teachers for always boosting my moral and

providing me encouraging environment.

Name:-Shoyab Mohammad Siddiquee

Reg. No.-10805456

Course:-B.tech(Honers)-CSE


4

CONTENT╆S

INTRODUCTION 5

NATURE OF PROJECT: WEB BASED APPLICATION 6

EXISTING SYSTEM 8

PROBLEM ANALYSIS 11

Product Definition, Acronyms and Abbreviations 11

FEASIBILITY STUDY 12 WHAT ARE THE USER╆S DEMONSTRABLE NEEDS╂ 13

HOW CAN THE PROBLEM BE REDEFINED? 13

SOFTWARE REQUIREMENT ANALYSIS 15

PURPOSE 15

OVERVIEW/INTRODUCTION 16

PROBLEM/NEED 18

SOLUTION/APPROACH 20

SCOPE 22

ASSUMPTIONS, DEPENDENCIES, CONSTRAINTS FOUNDATION & IMPACT 25

SPECIFIC REQUIREMENTS 26

TECHNICAL REQUIREMENTS 28

GENERAL DESCRIPTION 29

OVERVIEW OF FUNCTIONALITY 30

Diagrams 31

Flow chart of Login 32

Use Case Diagram 33

Sequence Diagram 34


5

Data Flow Diagram 35

E-r Diagram 36

Database design 37

Reference 38

Introduction

This is a Education based website which have 2 modules one is student(user) and second is

administrator . Administrator can upload and make quiz's and online test's and other education

related application's and create events for student's. student can make here own account in which

he can give online test and in the end the final result is shown and result goes emailed to his

registered email Id .there is some small games applications for the primary school student who

can play and learn with these games.

Administration and student both can share own data on this website by uploading and

downloading it. this is a part of the e-data sharing.

The present example is lionshare and ZOHO website's which is used in LPU for online student

test's but they don't have concept of e-data sharing.

The main aim of this project report is to highlight the features as follows: -

• To show how the project is developing.

• To show the details of design.


6

• To show how the users can work with the software.

• To show what requirements are included in project?

NATURE OF PROJECT: WEB BASED APPLICATION

A Web application is an application that is accessed via Web browser over a network such as the

Internet or an intranet. It is also a computer software application that is coded in a browser-

supported language and reliant on a common web browser to render the application executable.

Web applications are popular due to the ubiquity of a client, ability to update and maintain Web

applications without distributing and installing software on potentially thousands of client

computers is a key reason for their popularity.

Web based applications have evolved significantly over recent years and with improvements in

security and technology there are plenty of scenarios where traditional software based

applications and systems could be improved by migrating them to a web based application.

Below are some of the core benefits of web-based applications.

•Cross platform compatibility.

Most web-based applications are far more compatible across platforms than traditional installed

software. Typically, the minimum requirement would be a web browser like Internet Explorer,

Fire fox, Netscape etc. These web browsers are available for a multitude of operating systems

and so whether you use Windows, Linux, or Mac OS you can still run the web application.

•More manageable

Web based systems need only be installed on the server placing minimal requirements on the end

user workstation. This makes maintaining and updating the system much simpler as usually it

can all be done on the server. Any client updates can be deployed via the web server with

relative ease.


7

•Highly deployable

Due to the manageability and cross platform, support deploying web applications to the end user

is far easier. They are also ideal where bandwidth is limited and the system and data is remote to

the user. At their most deployable, you simply need to send the user a website address to log in

to and provide them with internet access.

This has huge implications allowing you to widen access to your systems, streamline processes,

and improve relationships by providing more of your customers, suppliers, and third parties with

access to your systems.

•Secure live data

Typically, in larger systems those are more complex data is stored and moved around separate

systems and data sources. In web-based systems, these systems and processes can often be

consolidated reducing the need to move data around.

Web based applications also provide an added layer of security by removing the need for the user

to have access to the data and back end servers.

•Reduced costs

Web based applications can dramatically lower costs due to reduced support and maintenance,

lower requirements on the end user system and simplified architecture.

By further streamlining your business operations because of your web, based application

additional savings can often be found.


8

EXISTING SYSTEM

In this section we will discuss about already existing manual system of operation. In system

study we first analyze the drawbacks of the existing system or shortcoming of the existing

system. We study there are changes required in the system. By system study we find following

drawbacks in existing system.

Complicated:

When large number of students arrives for the examination, to maintain the huge no of students

on a single place for examination It takes lots of time and management of such large no. of

students is a difficult task .

Redundancy:

As data is maintained in different files and register, there is possibility that duplication data is

stored thus wastage of storage space.

Time Consuming:

The system is manual system, it takes lot of time for the examination for example in its difficult

to manage and keep record of each student simultaneously. It is difficult to handle more than one

visitor at a time. It is difficult to provide examination system service for 24 hours a day.

Record Management:

It is a very tangible job in manual database system.

Inaccuracy:

Some time there may be chance of wrong calculation in result generation. Existing system is not

according to current demand.

No Report Generation:

In Existing, system there is not any automatic report/result generation facility.


9

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.

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.

What’s new in the system to be developed?

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

1.Proposed System is automated and web based system so that's why it has very fast processing

speed.

2.Records management is very easy job in database.

3.There may be not any chance of wrong calculation of amount.

4.Proposed system is according to current demand.

5.In Proposed system there is automatic report/result generation facility.

6.Security and privacy is possible by using user name and password.


10

Software system attributes

1. 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 further details. Reports screen

contains text boxes and drop down lists, so that reports can be produced.

2. Security:

Application will allow only valid users to access the system. Access to any application resource

will depend upon user’s designation. There are three types of users namely Administrator, Event

Poster and Organizer. Security is based upon the individual user ID and Password.

3. Maintainability:

The installation and operation manual of Online Examination System will be provided to the

user. Also functionality and help will be provided to the online users.

4. Availability:

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

5. Portability:

The application is developed in ASP.NET. It would be portable to other operating system

provided .NET Framework is available for the OS.


11

Acceptance criteria

The software should meet the functional requirement and perform the functionality effectively

and efficiently.

1.A user-friendly interface with proper menus.

2.Data transfer should be accurate and within a reasonable amount of time keeping in

mind the network traffic.

3.The system should not allow entry of duplicate key values.

4.System should have the ability to generate transactional Logs to avoid any accidental

loss of data.

5.Log file should also be generated.

6.Data integrity is maintained and redundancy is reduced.

PROBLEM ANALYSIS

Product Definition, Acronyms and Abbreviations

.NET Framework 3.5: A software development platform created by Microsoft Corporation.

C#: Language used for developing the web based application.

ASP.NET: A set of web development technologies marketed by Microsoft.

GUI: Graphical User Interface.

IIS: Internet Information Services, a set of Internet-based services for servers using Microsoft

Windows.


12

UI: User Interface.

SQL Server 2008 In build in VS 2010: Database server for storing the data

Visual Studio 2010: An advanced integrated development environment by Microsoft.

Mozilla/Internet Explorer: The browser for navigating the internet.

FEASIBILITY STUDY

Depending on the results of initial investigation the survey is expanded to more detailed

feasibility study. The objective of feasibility study is not to solve the problem but to acquire a

sense of its scope during the study the problem definition is crystallized and aspects of the

problem to be included in the system are determined. Consequently, costs and benefits are

determined with greater accuracy.

Types of Feasibility

There are various measures of feasibility that helps to decide whether a particular project is

feasible or not. These measures include-

1.Technical Feasibility

2.Operational Feasibility

3.Economical and Financial Feasibility

Technical Feasibility Study

The technical issues raised during the technical feasibility analysis are:

1.Does the necessary technology exist to do what is suggested?

Yes, necessary technologies exists, Project will be develop using asp.net, SQL server 2008, .net

framework 3.5 and C# language.


13

Will the proposed system & components provide adequate responses to inquiries, regardless of

the number or locations of users?

Yes it can be achieved by having a good bandwidth dedicated to the website and good

networking.

Can the system be expanded?

System is build using 2 tier architecture (can be expendable to 3-tier), and proper documentation

so that new person can join and understand project and add something new to the project.

Operational Feasibility Study

We have designed front end in ASP.net by getting the information from the end user, which help

us in designing the GUI according to the end user’s requirements. The end users can easily

understand and expand it in the future.

Economical Feasibility Study

It involve estimating cost and benefits that can be tangible and intangible because of confusing

between the types of costs it is sometimes very difficult to divide the benefits out weight the cost.

WHAT ARE THE USER’S DEMONSTRABLE NEEDS?

User needs a web-based system, which will remove all the above-mentioned Problems that, the

user is facing. The user wants a web-based system, which will reduce the bulk of paperwork,

provide ease of work, flexibility, fast record finding, modifying, adding, removing and

generating the reports.

HOW CAN THE PROBLEM BE REDEFINED?

We proposed our perception of the system, in accordance with the problems of existing system

by making a full layout of the system on paper. We tallied the problems and needs by existing

system and requirements. We were further updating in the layout in the basis of redefined the


14

problems. In feasibility study phase we had undergone through various steps, which are

described as under:

How feasible is the system proposed?

This was analyzed by comparing the following factors with both the existing system and

proposed system.

Cost:

The cost required in the proposed system is comparatively less to the existing system.

Effort:

Compared to the existing system the proposed system will provide a better working environment

in which there will be ease of work and the effort required will be comparatively less than the

existing system.

Time:

Also the time required generating a report or for doing any other work will be comparatively

very less than in the existing system. Record finding and updating will take less time than the

existing system.

Labor:

In the existing system the number of staff required for completing the work is more, while the

new system will require quite less number of staff.


15

R E Q U I R E M E N T A N A L Y S I S

SOFTWARE REQUIREMENT ANALYSIS

1.1. Purpose

1.This Web Application provides facility to conduct online examination world wide.

2.It saves time as it allows number of students to give the exam at a time and displays the

results as the test gets over, so no need to wait for the result. It is automatically generated by

the server.

3.Administrator has a privilege to create, modify and delete the test papers and its particular

questions.

4.User can register, login and give the test with his specific id, and can see the results as

well.

1.2. Document Conventions

The following are the list of conventions and acronyms used in this document and the project as

well:

Administrator: A login id representing a user with user administration privileges to the software


16

User: A general login id assigned to users

Client: Intended users for the software

Examiner: Checks the test n gives result

1.3. Scope

Scope of this project is very broad in terms of other manually taking exams.

Few of them are:-

1.This can be used in educational institutions as well as in corporate world.

2.Can be used anywhere any time as it is a web based application(user Location doesn’t matter).

3.No restriction that examiner has to be present when the candidate takes the test.

2. Overall Description

2.1. Product Perspective

The proposed Online Exam System and Data sharing is an on-line Exam System.

The online test created for taking online test has following stages

1.Login

2.Test

3.Result

Login:-

There is a quality login window because this is more secure than other login forms as in a normal

login window there are multiple logins available so that more than one person can access to test


17

with there individual login. But in this project there is only one login id i.e. administrator id and

password by which a person enter the site. Hence it is more secure and reliable than previously

used on-line test simulators.

TEST:

Test page is the most creative and important page in this project. It consists of 2 modules

namely:

1.Subject selection

2.Utilities

Subject selection:-

From the given choices the candidate can select his field (like C, C++ and JAVA etc) for taking

on with the test.

Utilities:-

It includes:-

1.Skip and come back to the question afterwards if needed.

2.Gives the list of attempted and unattempted questions and can go to any question directly and

can either attempt or change the answer of the already attempted question.

2.2. Product Features

There are three different users who will be using this product:

1.University chancellor who will be acting as the administrator.

2.Students who will be accessing the OES online.

The features that are available to the Administrator are:


18

1.The administrator has the full fledged rights over the OES.

2.Can create/delete an account.

3.Can view the accounts.

4.Can change the password.

5.Can hide any kind of features from the both of users.

6.Insert/delete/edit the information of available on OES.

7.Can access all the accounts of the faculty members/students.

The features available to the Students are:

1.Can view The different categories of Test available in their account.

2.Can view their marks.

3.Can view the various reading material.

4.Can view and modify its profile but can modify it to some limited range.

5.Can pay their fee online.

The features available to the Examiner are:

1.Can view The different categories of Test conducted by users.

2.Can view their marks.

3.Can view and modify Results.

2.3. User Classes and Characteristics

There are various kinds of users for the product. Usually web products are visited by various

users for different reasons.

The users include :

1.Chancellor who will be acting as the controller and he will have all the privileges of

administrator.

2.Students who will be using the above features by accessing the OES online.

3.Examiner who will prepare& load database into the software.


19

2.4. Operating Environment

The product will be operating in windows environment. Also it will be compatible with the IE

6.0. Most of the features will be compatible with the Mozilla Firefox & Opera 7.0 or higher

version. The only requirement to use this online product would be the internet connection.

2.5. Design and Implementation Constraints

The whole implementation is done in two modules. The first one is Administrator and the second

is Examinee.

Module I:-

This first module tracks the path of Administrator. In this module it shows

how the admin can log into the system with a valid password and can add new valid user to the

database. His name and examid is saved in the database .Also he can manipulate the database

and add new question in the database from the webpage itself. It also shows how many questions

are in database.

Module II:-

This second module track the path for the examinee .The examinee can log into the system with

a valid ID issued by the admin. After successfully login into the system the examinee moves to

the instruction web page where he will get instruction about the examination process. Then after

clicking the start button the exam starts and timer also starts .In this manner examinee can take

up the test and clicking the submit button , he will get the result of that section immediately. At

the end system displays the initial web page.


20

2.6. User Documentation

The product will include user manual. The user manual will include product overview, complete

configuration of the used software, technical details, backup procedure and contact information

which will include email address. The product will be compatible with the Internet Explorer 6.0

or higher.

2.7 Assumptions and Dependencies

Full working of OES is dependent on the availability of Internet connection.

Assumptions:

In general it has been assumed that the user has complete knowledge of the system that means

user is not a naïve user. Any data entered by him/her will be valid. To make the software as user

friendly as possible but at the same time keeping in minds user requirements.

1.Server OS should be Windows NT/2000/XP/7

2.Client PC should be Windows 7/NT/WorkStation or Windows 2000/xp/vista//7

with latest service pack.

1.Dependencies:

It depends that the one should follow the international standards for the generating the User ID &

should fill the related information in the proper format.

3. System Features

3.1. Database – Storage

3.1.1. Description and Priority

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

university which include

1.Profile of both users

2.Student details


21

3.My account

4.Test results

3.1.2. Stimulus / Response Sequences

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

Logs into the Online Exam system. 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.

Examination:

First of all the user/examinee gets a valid identification number (same as the roll no for a normal

examination).The user can log on with this identification no. and can take up the examination.

After logging in the user can see various options and can choose the option from the menu.

3.2. Functional Requirements

This section gives the list of Functional and non functional requirements which are applicable to

the Online Exam System. Functional requirements are nothing but the services provided by the

system to its end users.

There are three sub modules in this phase.

1.Candidate module.

2. Examiner module.

3. Administrator module.

The functionality of each module is as follows.


22

Candidate module: The candidate will logon to the software and take his examination. He can

also check his previous examinations marks and his details. The candidate will get result

immediately after the completion of the examination.

Examiner module: The database is prepared & loaded into the software. Selection for

examination can be done language wise by the examiner. The results will be displayed

immediately after completion of the examination.

Administrator module: The administrator collects all the results after successful completion of

the examination and sends to the head quarters as and when required.

3.2.1 Interface Requirements

This section describes how the software interfaces with other software

products or users for input or output.

3.2.1.1 User Interface

Application will be accessed through a Browser Interface. The interface would be viewed best

using 1024 x 768 and 800 x 600 pixels resolution setting. The software would be fully

compatible with Microsoft Internet Explorer for version 6 and above. No user would be able to

access any part of the application without logging on to the system.

1)Non Functional Requirements

4.1. User Interfaces

Application will be accessed through a Browser Interface. The interface would be viewed best

using 1024 x 768 and 800 x 600 pixels resolution setting. The software would be fully

compatible with Microsoft Internet Explorer for version 6 and above. No user would be able to

access any part of the application without logging on to the system.


23

4.2. Hardware Interfaces

Server Side:

1.Operating System: Windows 9x/xp ,Windows ME

2.Processor: Pentium 3.0 GHz or higher

3.RAM: 256 Mb or more

4.Hard Drive: 10 GB or more

Client side:

1.Operating System: Windows 7 or above, MAC or UNIX.

2.Processor: Pentium III or 2.0 GHz or higher.

3.RAM: 256 Mb or more

4.3. Software Interfaces

Client Side : .HTML, Web Browser, Windows XP/2000/Vista/7

Web Server: .HTML, Windows XP/2000/Vista/7

4.4. Communications Interfaces

The Customer must connect to the Internet to access the

Website:

1.Dialup Modem of 52 kbps

2.Broadband Internet

3.Dialup or Broadband Connection with a Internet Provider.

4.Other Nonfunctional Requirements

5.1. Performance Requirements


24

Some Performance requirements identified is listed below:

1. The database shall be able to accommodate a minimum of 10,000 records of students.

2. The software shall support use of multiple users at a time.

There are no other specific performance requirements that will affect development

5.2. Safety Requirements

The database may get crashed at any certain time due to virus or operating system failure.

Therefore, it is required to take the database backup.

5.3. Security Requirements

Some of the factors that are identified to protect the software from accidental or malicious

access, use, modification, destruction, or disclosure are described below. Keep specific log or

history data sets

1.Assign certain functions to different modules

2.Restrict communications between some areas of the program

3.Check data integrity for critical variables

4.Later version of the software will incorporate encryption techniques in the user/license

authentication process. Communication needs to be restricted when the application is validating

the user or license. (i.e., using https).

5.4. Software Quality Attributes

The Quality of the System is maintained in such a way so that it can be very user friendly to all

the users. The software quality attributes are assumed as under:

1)Accurate and hence reliable.

2) Secured.


25

3) Fast speed.

4) Compatibility.

ASSUMPTIONS, DEPENDENCIES, CONSTRAINTS FOUNDATION & IMPACT

ASSUMPTIONS

1.The project can be failed due to lack of bandwidth available and other hardware issues like

failure of web server, failure of network.

2.The project can be affected, if not properly documented.

3.The project can be affected, if properly backup have not taken time to time.

4.The project can be affected due to insufficient knowledge to manpower and lack training etc.

5.The success of project can be affected, if marketing policy is not properly defined.

6.The project can be affected, if any specific data requirements are not provided to developers.

7.The project can be affected if database server fails.

DEPENDENCIES

1.The project depends on properly defined requirements.

2.The project depends upon a design document.

3.The project depends upon users.

4.The project will depend upon good and attractive marketing policies so that people must use it.

5.The project depends upon provision web server and good bandwidth Internet.

6.The development of project will depend upon retention of developers.


26

7.The execution of project is depends upon well normalized database management system.

ISSUES & CONSTRAINTS

1.The project will only work with certain operating environment.

2.The product will only work within a particular network environment.

3.The database can be limited (in means of storage) if not properly handled.

4.The database items are not available to developer.

5.Logical problems may arise in development process.

6.The requirements may gradually change by client. Those are not part of original requirements.

7.Shortcomings in software design.

OTHER POTENTIAL REQUIREMENTS

1.Maintain and update tickets, event and service information.

2.Profiles to be viewed and maintained.

3.Organizer should be categorized.

4.Communication between organizer and Event Poster.

SPECIFIC REQUIREMENTS

BUSINESS REQUIREMENTS

1.The Online Examination System will be available 365 X 24 X 7 without any implication.

2.The Online Examination System should maintain all the login of all end users.

3.The Online Examination System should earn to maintain the system and services


27

LOGICAL DATA REQUIREMENTS

To develop this project, Developer requires different types of data which will be mentioned in

Design document.

PERFORMANCE REQUIREMENTS

The Project performance will be based on following parameters:

1.Up to date Hardware, on which the application will be ported.

2.Normalized Database

3.Data backup policies

4.Well Designed Modules

5.Documentation

6.Rugged Testing

QUALITY REQUIREMENTS

The Quality of System will be determined and analyzed using various factors:

1.Conformance to requirements

2.Scalability

3.Correctness

4.Completeness

5.Absence of Bugs


28

6.Fault – Tolerance

7.Extensibility

1.Maintainability

2.Absence of Bugs

8.Documentation

Irrespective of Software Quality factors that tend to increase the application scalability are:

1.Readability

2.Ease of maintenance, testing, debugging, fixing, modification and portability

3.Low complexity

4.Low resource consumption

5.Less Compilation and Run time warnings

6.Well Documented

EXTERNAL INTERFACE REQUIREMENTS

We will support and test this product on two major web browsers: Microsoft Internet Explorer

and Mozilla Firefox. The user will login to perform the various tasks. All information will be

stored in a database on a server. The users will be able to perform their various roles within this

setting. All information will be sent over the web to the server where it will be stored and

processed.


29

TECHNICAL REQUIREMENTS

HARDWARE REQUIREMENTS

1.Pentium IV Processors

2.256 Ram

3.Server Machine

4.Client Machine

5.5 GB Hard Drive

SOFTWARE REQUIREMENTS

1.Microsoft Windows XP/Vista/Window7

2.Microsoft Visual Studio 2005

3..Net Framework 2.0

4.Microsoft SQL Server 2005

5.Internet Explorer 6.0 or above

TECHNOLOGIES USED

This project is a web application that is developed in ASP.NET having SQL Server 2005 as back

end.

1.Presentation Layer - Microsoft ASP.NET 2005

2.Business/Logic Layer – Microsoft C#. Net 2008

3.Database Layer - Microsoft SQL Server 2008


30

4.Client Side – html ,JavaScript, Ajax

5.Web Development Language – HTML, CSS

GENERAL DESCRIPTION

Project description is all about its four entities which are:

1. Administrator

2. User Account

3. Visitor

User Personas and Characteristics

The user personas to be considered are as follows:

Administrator: Deals with licensing and maintenance issues. Has a more in depth

understanding of the application organization and function.

User Account: User Account is a person who is interested in creating Exam and using organizer

services.

Visitor: Anyone who requests any page of the website is a visitor.

PRODUCT PERSPECTIVE

The entire tool is web based. Only an internet browser will be required for interfacing with the

application. Application requires communication with database located at server. Database will

contain all items pertaining to users.


31

OVERVIEW OF FUNCTIONALITY

Exam organiser

Functionality:

1. Registration: For creating an Event, Event poster has to register and provide his

information which will be stored in the database.

2. Create Exam: Admin will create an Exam event, and provide information about the

Exam on take test page and upload Exams and Documents and save it. This information

3. Request for organizing event: User can requesting the Admin to organize and create

the Exams And request for any documents.

Visitors

Functionality:

1. view Exams list: Visitors can view coming exams, results of old Exams, users profiles.

Administrator

Functionality:

1. Create and Delete Accounts: Administrator can create and delete accounts of any user.


32

D E S I G N

Activity Diagram:-


33

class diagram


34

sequence diagram


37

DATA BASE DESIGN:-

TABLE1-REGISTRATION

Field name Data type Constraints Use rName Varchar(50) Primary key Not null Password Numeric(15) Not null Re password Numeric(15) Not null Email Address Varchar(50) Not null Full Name Varchar(50) Not null Country Varchar(50) Not null

TABLE2-LOGON

Field name Data type Constrants User name Varchar(50) Primary key Not null Password Numeric(50) Not null


38

References

This web application has been prepared on the basis of discussion with Team

members, faculty members and also taken information from following books & website

1.4.1 Websites:

1) www.alexa.com

2) Fundamental of Software Engineering By Rajiv Mall

3) Software Engineering : A practitioner’s approach Ed. By Pressman, Roger

4) Software Engineering Seventh Edition Ian Sommerville

5) Software Engineering Ed.2 by Jalota & Pankaj.

6) Schaum’s Series, “Software Engineering”

Date post:	24-Apr-2015
Category:	Documents
Upload:	darell-floranda
View:	308 times
Download:	0 times