Project - Examination Paper

7/31/2019 Project - Examination Paper

1/46

Before computers were introduced in

the field of examination or in other

area, all the system were handled

manually. But now, they are handled

with computerized system.

In computer oriented systems, the

capabilities of computers and human

are blended to take advantage of the

unique capabilities of each other.

Computers differ from the manual

2


2/46

system in at least three important

capabilities.

1) Accuracy : There is a greater

potential for accuracy. Once the

data is entered correctly into the

system in a machine readable

format, it is not necessary to re-

enter it again. This reduces the

number of times humans are

involved. Of course, the computer

is vulnerable to the entry of invalid

data.

2) Data Collection and

Communication : Methods for

collection and communication data

are fast and more efficient. Modern

3


3/46

computers allow data

communication networks to be

established to collect data and to

respond to inquiries.

3) Data Storage : Another way, in

which manual and human-machine

system differ is the quantities of

data that can be stored and

accessed. In computers, data are

kept in master files usually

magnetic storage device, in a

machine readable form. A

collection of related files forms a

database. Database allows for

centralized storage of data,

thereby eliminating the need for

multiplicity of redundant files.

4


4/46

OUTLINE OF THE PROJECT

The Project performs the technical

support for the Online Examination Site.

5


5/46

The objective of the system are :-

Introduction to online examination.

Technology used in the Online

Examination system.

System analysis and approach to the

system.

Design.

Implementation

Testing and Evaluation

Project Category :

The category of this project is Web

Application.

Hardware and Software Requirements

Processor : INTEL P4 and above.

RAM : 512 MB and above.

6


6/46

Input Device : Mouse or Keyboard

Output Device: VDU (Minimum VGA,

SVGA

Support), Printer.

Software Specification for Server

Operating System:Windows

XP/Windows 7

Web Server : IIS

Tools & Languages Used

Platform : .NET Framework (3.5)

Front End : ASP. NET

Database Layer : Type 4 Driver (SQL

Client)

Database Used : MS SQL Server

Language : Vb, Java Script.

7


7/46

About the Technology

The .NET Framework is partitioned into

modules, each with its own distinct

responsibility. The higher tiers request

services only from the lower tiers, so

.NET is hierarchal. The modified

architectural layout of the .NET

Framework is illustrated in the figure

below.

8

VB.NETC#

Jscript. NET VB.NET Languages

Common Language Specification (CLS)

Common type System (CTS)

.NET Framework Class Library (FCL)

ASP.NETWeb Forms, XML Web Services

WindowsForms

Console

ADO.NET .NET RemotingCommon Language Runtime

[Just-in-Time Compilers, Garbage Collector, Security Manager, and so on]


8/46

Common Language Infrastructure (CLI)

The .NET Framework is a managed

environment. The CLR monitors the

execution of .NET applications and

provides required services. It manages

memory, handles exceptions, ensures

security and much more.

Language interoperability is one goal

of .NET. .NET languages share a

Common Language Specification (CLS),

Common Type System (CTS) and

9

Operating System

Modified architectural layout of .NET Framework


9/46

Framework Base Class Library (FCL).

Web Services, ADO.NET, Windows or

console applications and Remoting

execute on CLR. In .NET, the

programming language like C#, VB.NET

or Jscript.NET has similar experience

except little differences. .NET abstracts

lower-level services, while retaining

most of their flexibility.

Assemblies, Application domains and

metadata are brought to CLR

environment before they are executed.

Once they are brought to the execution

environment, CLR takes the

responsibility of managing and

executing it.

10


10/46

The important components of .NET

Framework are:

Common Language Runtime

Assemblies

Application Domains

Common Type System

Metadata and Self-describing

Components

Common Language Specifications

.NET Framework Class Library

11


11/46

Software Development Life Cycle

The Waterfall Model :-

It is the simplest and the widely used

process model for software

development. Here the phases involved

in the software development are

organized in a linear order.

In a typical waterfall model, a project

begins with the feasibility analysis. On

successfully demonstrating the

feasibility of a project, the requirements

analysis and project planning begins.

The design starts after completing the

requirements analysis and coding starts

after completing the design phase. On

12


12/46

completing the coding phase, testing is

done. On successful completion of

testing, the system is installed. After

this, the regular operation and

maintenance of the system takes place.

The important characteristics of this

model are

the process of software

development consists of a linear set

of distinct phases

requirements analysis

project planning

system design

detailed design

coding and unit testing

system integration and testing

13


13/46

Each phase is distinct and is

mandatory for every project

irrespective of project size

Every phase has a well defined entry

and exit criteria

At every phase there is a provision

for verification and validation, which

helps in correction of errors.

The importance of this model is that

it allows for communication between

the customer and the software

developer and specifies what, when

the product will be delivered, and at

what cost.

The weakness with this model is

that, it requires a complete set of

user requirements before the

commencement of design. Which is

14


14/46

difficult to give since requirements

keep changing according to needs

and time.

DFD0 LEVEL DFD

15

USER USER

ADMIN

Request forRegistration/Login

Apply for Buying Product

Request Accepted

Set ProductsStructure

Set Stock


15/46

1-LEVEL DFD (ADMIN SECTION)

16

ONLINE SHOPPING AND

INVENTORY

ADMIN

Get Apply ID

Request forLogin

RequestAccepted

Product. setsuccessfully

Stock Mgmt. Set successfully

ADMIN Request forLogin


16/46

1-LEVEL DFD (USER SECTION)

17

ADMIN

Set ProductStructure

Set Stock Mgmt.

Request Accepted

Product. setsuccessfully

Stock set successfully

STUDENT

ONLINE SHOPPING AND

INVENTORY

0.1

Request for Login

Apply for Product

Update Profile


17/46

2-LEVEL DFD (USER SECTION)

18

STUDENT

ONLINE SHOPPING AND

INVENTORY

0.1

Request for View Bill

Request for ChangingPassword

Request Accepted

Apply Id

Successfully Updated

Bill Obtained

Password ChangedSuccessfully

USERLoginValidation0.1.1 Obtain

bill 0.1.7

Id/Password

SuccessfullyLogin


18/46

2-LEVEL DFD (ADMIN SECTION)

19

Userrelatedportal0.1.2

ProductDetails0.1.3Apply forbil l0.1.4

tblUsertblbill

tblproduct

ViewProduct.details Apply Appearing

BillGenerationstart 0.1.6

AdminoginValidation

0.1.1

tbladmin

Id/Password


19/46

E-R DIAGRAM

1 1

20

AdminRelatedPortal0.1.2

UserSetting0.1.4

tbluser

SuccessfullyLogin

BillSettiing0.1.3

Set Bill

tblbill

Set User

tblquestion tblanswer

qId question

qsetId

aId qId

answer

isCorrec

t

applyId

adminId


20/46

M

M

1 M M

M

M

M

1 M

21

negMarksmarks

tblqset

qsetId

setNo.

examId

tblexamination

qualification

per

InMDegre

e

exam.Name

total

Time

startDate

lastApplydate

fees

total

Marks

maxAge

perIn

HSLC

perInB

Degree

perInHS

tblapply

examId

tblresult tblstudent

perInBDegre

e

qualificati

on

perInHSLC

C

stdId

password

stdname

address city

country State

perInMDegree

phNo

dob

photoPath

perInHS

email

stdId

applyDate

qsetId

examId

resultId

applyId

marks

grade

tbladmin

password


21/46

REQUIRED DATABASE

22


22/46

23


23/46

24


24/46

25


25/46

26


26/46

27


27/46

28


28/46

STUDENT SELECTION

29


29/46

30


30/46

31


31/46

32


32/46

33


33/46

34


34/46

35


35/46

36


36/46

37


37/46

38


38/46

39


39/46

FOLLOWING TESTINGS ARECONDUCTED SUCCESSFULLY

Testing

Unit Testing

Initially, each program

component (module) is tested

independently verifying the

component functions with the

types of input identified by

studying components design.

Such a testing is called Unit

Testing (or component or module

testing). Unit testing is done in a

controlled environment with a

predetermined set of data fed

into the component to observe

40


40/46

what output actions and data are

produced.

Integration Testing

When collections of components

have been unit-tested, the next

step is ensuring that the

interfaces among the

components are defined and

handled properly. This process of

verifying the synergy of system

components against the program

Design Specification is called

integration Testing.

System Testing

41


41/46

Once the system is integrated,

the overall functionality is tested

against the Software

Requirements Specification

(SRS). Then, the other non-

functional requirements like

performance testing are done to

ensure readiness of the system

to work successfully in a

customers actual working

environment. This step is called

System Testing.

Volume Testing

The test addresses the handling

of large amounts of data in the

system. This includes

Checking of whether data

structures have been defined

42


42/46

large enough to handle all

possible situations.

Checking the size of

fields, records and files to see

whether they can

accommodate all expected

data, and

Checking of systems

reaction when data sets

reach their maximum size.

Configuration Testing

This testing analyzes the various

software and hardware

configurations specified in the

43


43/46

requirements. (e.g. system to

serve variety of audiences)

Compatibility Testing

The tests are needed when a

system interfaces with other

systems (e.g. system to retrieve

information from a large

database system).

Security Testing

This testing ensure the security

requirements (testing

characteristics related to

availability, integrity, and

confidentiality of data and

services).

44


44/46

Timing Testing

Include response time,

transaction time, etc. Usually

done with stress test to see if the

timing requirements are met

even when the system is

extremely active.

Quality Testing

This tests evaluate systems

reliability, maintainability and

availability. These tests include

calculation of mean time to

failure and mean time to repair,

as well as average time to find

and fix a fault.

45


45/46

CONCLUSION

While developing the system a

conscious effort has been made to

create and develop a software package,

making use of available tools,

techniques and resources that would

generate a proper Online Examination

site.

46


46/46

While making the system, an eye has

been kept on making it as user friendly,

as cost-effective and as flexible as

possible.

As such one may hope that the system

will be acceptable to any user and will

adequately meet his/her needs.

As in case of any system development

process, there are a number of

shortcomings, there have been some

shortcomings in the development of this

system also.

Documents

Project - Examination Paper