avnish verma 2

8/6/2019 avnish verma 2

1/62

Online Exam

A

PROJECT REPORTSubmitted in partial fulfillment of the Requirements

For the award of Master of Computer Application Degree

RAJIV GANDHI PROUDYOGIKI VISHWAVIDYALAYA

BHOPAL (M.P.)

MINOR PROJECT REPORT

Guided by : Submitted by :Mr Anil Chowdhary

Prof. Kiran parwani (0807CA091010)

Mr Avnish Verma

(0807CA091018)

Mr Lokendra Singh Dhakar(0807CA091049)

PG DEPARTMENT OF COMPUTER SCIENCE & APLLICATIONS

SHRI VAISHNAVSM INSTITUTE OF MANAGEMENT

INDORE

SESSION : Jan Jun 2011


2/62

ACKNOWLEDGEMENT

We would like to take this opportunity to record our deep sense of gratitude to althose who helped us in achieving this target.

First and foremost, we would like to express our gratitude towards Prof. P.R. Pal ,Head of Department of MCA, SVIM Indore. It was proud enough for us to simply beawarded a project under his able guidance. He was present all along the work, with his ideasinspiration and encouragement, and provided a masterly all through our work.

We would also like to thank our Project Manager and Project guide Prof.Kiran Parwanifor

having faith in our project & reviewing the entire part of it with a great attention. All the corrections &embellishments for the betterment of the project are made only due to his unendurable support.

We would also like to thank all our batch mates. Their suggestion, ideas, criticism

were of great help to us. Though it was extended on a NO THANKS basis, it would be unfaiif we do not express our gratitude towards their limitless efforts.

Last but not the least, we express our deep appreciation towards our family members& friends for providing us kind support and encouragement.

Mr Anil Chowdhary

Mr Avnish VermaMr Lokendra SinghDhakar


3/62


4/62

SHRI VAISHNAVSM INSTITUTE OF MANAGEMENT, INDORE


CERTIFICATE OF APPROVAL

This foregoing dissertation work is hereby approved as a creditable study of a Computer

Application Subject carried out and presented in a manner satisfactory to warranty its

acceptance as a prerequisite to the degree for which it has been submitted. It is

understood that by this approval the undersigned do not necessarily endorse or approve

any statement made, opinion expressed or conclusion drawn therein, but approve the

thesis only for the purpose for which it has been submitted.

(Internal Examiner) (External Examiner)


5/62

SHRI VAISHNAVSM INSTITUTE OF MANAGEMENT, INDORE


DECLARATION

We, Mr Anil Chowdhary,Mr Avnish Verma and Mr SLokendra Singh Dhakar, students

of Master of Computer Application, , Shri Vaishnav of Institute Management, Indore

hereby declare that the work presented in this Minor Project is outcome of my own

work, is bonafide, correct to the best of my knowledge and this work has been carried

out taking care of Engineering Ethics. The work presented does not infringe any

patented work and has not been submitted to any University for the award of any degree

or any professional diploma.

Mr Anil Chowdhary

Enroll.No. 0807CA091010

Mr Avnish Verma


Mr Lokendra Singh Dhakar



6/62

C O N T E N T SC O N T E N T S

S. No. Particular Page

1 Title of the project 01

2 Identity of client/organization 02

3 Problem Investigation 03

Introduction to Existing System 03

Goal & Need of project 03

Objective 03

Solution suggested 03

4 Theory of system 05

Concept of project 05

Various processes running 06

5 System analysis 07

(I)Information Gathering 07

(a) Online Observation 07

(b) Interviews 07

(c) Questionnaires 08

(II) Process model used 09

(a) Select model 09

(b) Advantage of select model 10

(III) Limitations to current system 10

(IV) Introductions to proposed system 11

(V) Merits of proposed system 11

(VI) Project resources 11


7/62

(a) Required documents 12

(b) Hardware & software requirements 12

(c) Time 12

(VII) Team organization 12

(IX) Specify the role in team 12

(X) Schedule 12

6 Feasibility study 13

7 System Design 17

DFD 17

UML 20

ERD 26

Data base design 28

Work Break Structure 33

Gantt Chart/ Pert Chart 34

8 Tools used and descriptions 35

Front end 35

Back end 44

Reasonfor tools selected 44

9 Implementation 46

(I)Programming approach followed 46

(a)Top Down Approach / Bottom Up Approach 46

(II) Administrative function 47

(III) User function 47

(IV) Screen layouts 48


8/62

(a)Forms Layouts 48

(b)Reports Layouts 55

10 Testing 63

QA Plan 64

Testing 64

Objectives of testing methods 65

Testing methods 66

11 Maintenance 73

12 Conclusion 74

(a) Conclusion and discussion 74

(b) Limitations 74

(c) Difficulties encountered during project 75

(d) Suggestion for future extension of work 75

13 Bibliography 76


9/62

1. PROBLM INVESTIGATION


10/62

1. PROBLM INVESTIGATION:

1.1 INTRODUCTION TO EXISTING SYSTEM:

In todays many system of online examination is available in the market many of in this

system has provide a little thing some systems are not gui based and some are not user friendly etc.

The whole process of assigning test and evaluating their scores after the test, was done manually

till date. Processing the test paper i.e. checking and distributing respective scores used to take time

when the software was not installed

The existing system is manual entry of up keeping of the details of the persons who are registered

already. And it is very difficult for each person to come to the exam center. It is very difficult to the

students from far distance to reach the exam center. This system is required to prepare

registration\application form, question paper for the students and required to print a lot of numbermanually. To calculate how many students registered, and verification of details of these students in a

month by hand is very difficult. This requires quite a lot of time and wastage of money as it requires

quite lot of manpower to do that. Another factor that takes into account that is the possibility of errors

and which requires verification and checking of data relating to various operations which is done

manually. The limitation of existing system is that it is not all personalized. It cannot be used for

personal and quick reference. Even the other staff members can make quick entries if the responsible

persona.

1.2.1 GOAL OF THE PROJECT:1.This project gives better utilization of time and

give fast result of the exam condu by the organization.This system is LAN base so we need to

lan system for run this project1. Planned approach towards working: - .

2. Accuracy: - The level of accuracy in the proposed system will be higher. All operation would be

done correctly and it ensures that whatever information is coming from the center is accurate.

3. Reliability: - The reliability of the proposed system will be high due to the above stated reasons.

The reason for the increased reliability of the system is that now there would be proper storage of

information.

4. No Redundancy: - In the proposed system utmost care would be that no information is repeated

anywhere, in storage or otherwise. This would assure economic use of storage space and consistency

in the data stored.


11/62

5. Immediate retrieval of information: - The main objective of proposed system is to provide for a

quick and efficient retrieval of information. Any type of information would be available whenever the

user requires.

6. Immediate storage of information: - In manual system there are many problems to store the

largest amount of information.

7. Easy to Operate: - The system should be easy to operate and should be such that it can bedeveloped within a short period of time and fit in the limited budget of the user

1.2.2 NEED OF THE PROJECT:

Online Examination is very helpful to users. The aim of this project is to provide quick, immediate

and easy way to appear the exam. It can provide special advantages to the students/applicants that

can't be found anywhere else through partnerships with agencies/boards that are conducting the

multiple choice type examination. Its working is that students allow registering for the exam andteacher allows registering for conducting the exam. This will continue to grow - ultimately providing a

wide breadth of services for beneficial to the students.

Online examination questions can be categorized according to topic, types, etc. (libraries) .The

online examination system makes provision for difficulty levels of items. A test can be compiled with

questions from different topics/libraries. A "serial number" is provided for each question according to

topic, etc. Questions can be converted to the databank from existing databanks. Tests can be created

on a random basis per student.

1.3 OBJECTIVES OF PROPOSED SYSTEM:

. The modern computerized system is developed with the aim to overcome the drawbacks of

existing system. The proposed system has got many advantages. People from different parts of the

world can register very easily. The new system is more personalized. It is maze in such a manner that

all the new users can understand all the options in it very easily. It is made in a quick and easy

referential manner.

Access to all important matters are not always locked and can be opened easily at the time of urgency.

The advantages of proposed system are that security is maintained in the new system. Securities for all

important data are maintained confidentially. As it is easily understandable and user friendly, quick

entries can be made in this system.

1.3.1 User Characteristics


12/62

Every user should be:

Comfortable of working with computer.

He must have knowledge in online field.

He must also have basic knowledge of English too.

1.3.2 Constraints GUI is only in English. So it is a big constraint that the user must know English language to operate

this software.

Login and password is used for identification of user and there is no facility for guest.

1.4 SOLUTION SUGGESTED:

Ecolab Solutions, in collaboration with Lamarck BV of the Netherlands, offers world-class Online

testing capabilities, processes and infrastructure to clients. The modular solution frame-work

comprises of four key systems and services as below.

Modular OnlineTesting SolutionFramework

Test Centre Infrastructure: Central to the solution is a network oprofessional and secure Test Centers where candidates can take an exam at a Tes

Centre of their choice, anywhere in the world.

Test-Delivery Platform:A universal test delivery platform is hosted to enable th

Examination Body to develop their tests in a standard "off the shelf" tesenvironment and deliver the exams, online.

Registration System: An online registration interface that enables the candidate

to register for an exam through the web site of the Examination Body.

Support System: A support team to provide assistance to candidates and th

Examination Body.

A state-of-the-art dashboard display of data, providing the Examination Body real time information on

all logistical aspects (for example, the number of registrations, exam fees collected, irregularities and

candidate satisfaction).

For further information on the Online Exam solutions write to


13/62

2. THEORY OF SYSTEM

2. THEORY OF SYSTEM:

2.1:- CONCEPT OF PROJECT

The SYSTEM table space contains the data dictionary - and often (by default) indexes and

clusters. (A data dictionary consists of a special collection of tables that contains information

about all user objects in the database). Since version 8i, the Oracle RDBMS also supports

"locally managed" table spaces, which can store space management information in bitmaps in

their own headers rather than in the SYSTEM table space (as happens with the default

"dictionary-managedtablespaces.

The Oracle DBMS can store and execute stored procedures and functions within it. PL/SQL


14/62

(Oracle Corporation's proprietary procedural extension to SQL), or the object-oriented language

Java can invoke such code objects and/or provide the programming structures for writing them.

RESUME

The developed system is flexible and changes can be made easily. The system is developed

with an insight into the necessary modification that may be required in the future. Hence the

system can be maintained successfully without much rework.

One of the main future enhancements of our system is to add a mail response from the

administrator to the user. So that the user can understand whether he/she is eligible for

appearing the exam, directly from the exam, directly from the administrator.

2.2 VARIOUS PROCESSES RUNNING:

Since the application Online Exam is developed in the JAVA language, it supportsmultithreading and is able to handle all the activities and processes running in parallel. There are

several activities are maintain by the application at a single unit of time in this application.

For example, to add, update or remove any record in the database, the application needs to get the

Connection first from the controller of the application. There are multiple threads can be generated by

the controller to do these kind of tasks.

Also, allocating and reallocating award to any IPD patient, the bed and ward records automatically be

modified.

Also, the same Application can be run on several machines connected on the same intranet.


15/62

3. SYSTEM ANALYSIS

3. SYSTEM ANALYSIS:


16/62

Analysis is a software engineering task that bridges the gap between system level requirement

engineering and software design. System Requirement engineering activities result in the specification

of softwares operational characteristics, indicate softwares interface with other system elements, and

establish constraints that software must meet. Requirement analysis allows the software engineer to

refine allocation and build models of data, functional and behavioral domains that will be treated by

software.

3.1 INFORMATION GATHERING:

Information Gathering is an art and a science .Whether the trust of the activities is the initial

investigation or a feasibility study .The aim is primarily to develop an understanding of the problem

faced by the user and the nature of the operation .Understanding how each activity operates requires

access to information. There are many information gathering tools for gathering information

accurately

3.1.1 Online Observation:

Observer comments and ratings for individual sessions are available as an Appendix to

This report. Generally,

o Observers gave uniformly high ratings

o Sessions on Nutrition, Risk Management, and Medication Management seem to be

especially well-received

o Scope, style, and length of commentary varied significantly among observers,

making analysis challenging

Most of the comments submitted were descriptive, listing materials, equipment, content,

strategies, and activities. For qualitative analysis, comments that were not merely

descriptive were identified and divided into three broad types: Positive Comments,

Negative Comments/Concerns and Suggestions. Further examination identified five

significant topic areas addressed by observer comments:

o Physical Setting and Equipment

o Student Behaviors

o Instructor Strategies and Behaviors


17/62

o Curriculum and Materials

o Training Activities

Following is a summary of the commentary within each topic area; representative

comments are included in italics.

3.1.2 Interviews:

One of the most important ways of gathering information are interviews ,the interview simply

is talk to experts to know how things are implement, if the interview was good, they often produce

accurate information.

We have done an online interview and some telephonic interviews with the manager of our

client Premier Biosoft to know what are their actual demand, requirements and expectations from this

project. Also, we took an interview of an employee at a hospital reception to know how their systems

works in detail and what the receptionist function should be.

3.1.3 Questionnaires:

A questionnaire is a research instrument consisting of a series of questions and other prompts for

the purpose of gathering information from respondents. Questionnaires are one of the most popular

methods of conducting scholarly research. They provide a convenient way of gathering information

from a target population

3.2 PROCESS MODEL USED:

3.2.1 Select model:

A software engineer must incorporate a development strategy that encompasses the process,

methods and tools layers and generic phases. This referred as a process model or a software engineer

paradigm. The process model used in our project is Incremental Model.


18/62

This model combines elements of linear sequential model with the iterative nature of

prototyping model. This model applies linear sequences in a staggered fashion as time passes; each

linear sequence produces a deliverable increment of the software. Customer uses the core product. As

a result of the use and evaluation, a plan is developed for the next increment. This process is repeated

following the delivery of each increment, until the complete product produced.

The incremental model delivers software in small but usable pieces called increments.

We've to use the following phases at each step of the modeling:

Requirement Analysis: In this phase of our project, the requirements of the system are analyzed

which enables to understand the nature of the software to be built. The information domain, required

function, behavior, performance and interfaces are studied.

Design: In this phase we had to decide the data structure, software architecture, interface &

algorithmic details of the project. Then this design is translated into coding in the next step.

Coding: The design was translated into machine readable form in this step.

Testing: In this phase, new components that is which are not the reusable ones and interfaces of

the system had to be tested.

3.2.2 Advantages of selected model:

1. It combines the iterative nature of prototyping model and linear nature of linear Sequential

model.

2. Number of people required is less.

3. Easy to add quality.

4. The system is designed so that it can be delivered in piece.


19/62

3

LIMITATIONS TO CURRENT SYSTEM:

Lack of security of data.

Unable to keep necessary record secure and safe for a long time.

Time consuming in processing.

Consumes large volume of paper work.

Unnecessary extra Manual work.

No direct role for the higher officials.

To avoid all these limitations and make the system working more accurately it needs to be

computerized.

3.4 INTRODUCTION TO PROPOSED SYSTEM:

The modern computerized system is developed with the aim to overcome the drawbacks of

existing system. The proposed system has got many advantages. People from different parts of

the world can register very easily. The new system is more personalized. It is maze in such a

manner that all the new users can understand all the options in it very easily. It is made in a

quick and easy referential manner. Access to all important matters are not always locked and

can be opened easily at the time of urgency. The advantages of proposed system are that

security is maintained in the new system. Securities for all important data are maintained


20/62

confidentially. As it is easily understandable and user friendly, quick entries can be made in this

system.

3.5 MERITS OF PROPOSED SYSTEM:

The system is very simple in design and to implement. The system requires very low system resources

and the system will work in almost all configurations.

Ensure data accuracys.

Security of data from other than users.

Administrator controls the entire system

Managing a huge amount of data in the database related to all users and patients.

Greater efficiency.

Minimize manual data entry.

User friendly and interactive User Interface.

Laboratory maintenance is easy.

Tough calculation of Patient billing makes automatic and easy.

Easy managing all equipments and their records in the store room.


21/62

4. PROJECT RESOURCES

4.1 PROJECT RESOURCES:

4.1.1 REQUIRED DOCUMENTS:


22/62

Information of various Packages of Java.

Information about main processes of Java.

Java documentation.

4.1.2 HARDWARE AND SOFTWARE REQUIREMENTS

4.1.2.1 Hardware Requirements:

Operating System:

Windows 2000, Windows ME, Windows XP and Mac OS X (10.4)

For Windows:

Processor: PC AT /Pentium as required or high level CPU.

Memory: Minimum 256MB (512 MB Recommended)

Monitor: With at least 800,600 resolutions.

Hard disk: 500 MB (1 GB Recommended)

For Mac

Processor: IMAX power PC G3 350

Memory: Minimum 256MB

Monitor: With at least 800,600 resolutions.

Hard disk: 500 MB (1 GB Recommended)

Mouse

This is a web based application so it also requires all network facilities.

4.1.2.2 Software Requirements

Platform: J2ME

Database: My SQL

IDE: Netbeans

4.1.3 TIME:


23/62

The project training has been taken by the candidate spent by the candidate in the company

during his whole project training was 6 days a week and 10 hours per day. The Timing schedule

during the training was from 9:00 am to 7:00pm per day, and days are from Monday to Saturday.

During analysis phase we analyzed that the duration of building the allocated project module is

near around 3 to 4 months.

4.2 TEAM ORGANIZATION:

The project Online Exam is developed by a team of Three members. The candidates made

the whole project Online Exam .

Team for the project There is a team of three members made the project Online Exam. Everyone

has contributed towards the development to persons full capabilities as required. Communication is

horizontal with our team members consist of three members, and vertical with each other.

4.2.1 ROLE OF THE CANDIDATE:

1. Anil Chowdhary Made module of coding Department of project Online Examt.

2. Avnish Verma - Made module of documantaion of project Online Exam.

3. Lokendra Singh Dhaka - Made module of Layout and Ward Department of project

online Exam.

The team size for Online Exam project is three. Every candidate worked as a

developer for the Online Exam in the team. And the role of every candidates is distributed among

the several phases of the SDLC.

The main phases of SDLC undertaken by the candidate:

1. Project analysis: This is the important role played by the candidates i.e. to analyze the

requirements of the client for the concerned module. The candidate analyzed the requirements and

expectations of the client.


24/62

2. Designing: In this phase the candidates is designed the database for the project module required as

per the analysis done by the candidate. Along with this, the candidate designed different module forms

that are required by the application.

3. Development: This is the implementation phase of the original project with the help of

programming language. As here we are using java as the developing language. The candidatedeveloped the logical functionality of the application that actually makes the program in the running

condition on the machine.

4. Testing: Testing is another phase handled by the candidate. In this phase, the candidate is

responsible for test the implemented project by manual testing and also by using different testing tools

available in the organization.

5. Deployment: At last after the application is finished, the deployment phase is covered in which the

candidate will be responsible for deployment of the application along with the all other members of

the project. The deployment of the application will be on available Operating System in the client's

machine.

4.3 SCHEDULE:

No Milestone name milestone descriptionTime line-week noFrom the start of

the project

1Requirement

Specification

Complete specification of the requirements.

Add any assumption that we might have. 1-2 weeks

2 Technology familiarizationUnderstanding of the technology needed to

implement the project. 3-4 weeks

3 DesigningDesigning the database and forms to

implement the Project.2-3 weeks

4 CodingActual Development of the project on

machine. 2-3 weeks

5 Testing

The system should be thoroughly tested by

running all the test cases written for the

system.

2-3 weeks

6 Documentation Project Report 1 week

7 Final review 1 week


25/62


26/62

5. FEASIBILITY STUDY

5. FEASIBILITY STUDY:


27/62

The initial investigation poi nts to the question whether the project is feasible. A feasibility is

conducted to identify the best system that meets the all the requirements. This includes an

identification description, an evaluation of the proposed systems and selection of the best system for

the job The requirements of the system are specified with a set of constraints such as system

objectives and the description of the out puts. It is then duty of the analyst to evaluate the feasibility of

the proposed system to generate the above results. Three key factors are to be considered during thefeasibility study.

Steps in feasibility analysis

Eight steps involved in the feasibility analysis are:

i) Form a project team and appoint a project leader.

ii) Prepare system flowcharts.

iii) Select the best-proposed system.

iv) Prepare and report final project directive to management

5.1 Technical feasibility

The main consideration is to be given to the study of available resources of the organization where the

software is to be implemented. Here the system analyst evaluates the technical merits of the system

giving emphasis on the performance, reliability, maintainability.

By taking the consideration before developing the proposed system, the resources availability of the

organization was studied. The organization was immense computer facilities equipped with

sophisticated machines and the software hence this technically feasible.

Technical Feasibility in this project:

It is technically feasible with the help of J2ME built in classes and database managing software

SQl.

5.2 Economical feasibility

Economic feasibility is the most important and frequently used method for evaluating the

effectiveness of the proposed system. It is very essential because the main goal of the proposed system

is to have economically better result along with increased efficiency. Cost benefit analysis is usually

performed for this purpose. It is the comparative study of the cost verses the benefit and savings that

are expected from the proposed system. Since the organization is well equipped with the required hard

ware, the project was found to be economically.


28/62

5.3 Operational Feasibility

An estimate should be made to determine how much effort and care will go into the developing of the

system including the training to be given to the user. Usually, people are reluctant to changes that

come in their progression. The computer initialization will certainly affected the turn over, transfer

and employee job status. Hence an additional effort is to be made to train and educate the users on the

new way of the system.

5.4 Time Feasibility: -

A system is good but if it cannot be developed in the desired schedule then it has no use. Our

project is time feasible because we have developed the project in given time period. Time feasibility

check whether the project can be completed within the time frame suggest by customer.

Time feasibility in this project:

As per this project was assigned for four months duration and also study suggest that this much

time is enough to complete the project therefore the project is also feasible as far as time is considered


29/62

6. SYSTEM DESIGN


30/62

6. SYSTEM DESIGN:

Design Phase: -

Design is meaningful engineering representation of something that is to be built. Design

focuses on four measure areas of concern: Data, Architecture, Interfaces and Component. After

analysis the system design will start on the basis of analysis of the system. Data design focus on

definition of data structure, Architectural design defines the relationship among major structural

elements of the program. An interface implies a flow of information and a specific type of behavior.

Design Principles: -

Problem partitioning and hierarchy

Identify every process of each module

Abstraction

Modularity

Top down and bottom up strategies

Proper data flow from one module to other module

7.1 DFD


31/62

7.2 UML:

7.2.1 Use Case Diagrams: The Use Case model is about describing what our system will do at a

high-level and with a user focus for the purpose of scoping the project and giving the application some

structure. The Use Cases are the unit of estimation and also the smallest unit of delivery. Each

increment that is planned and delivered is described in terms of the Use Cases that will be delivered in

that increment.

(Use Case Diagram for Administrator)


32/62

6.3 ERD


33/62


34/62

SystemStudy

DatabaseDesign

DesignForms

ApplicationCoding

IntegrationAnd Testing

User Manual and

Documentation

(15/03) (25/03) (05/04) (01/05) (15/05) (01/06)


35/62

7.TOOLS USED & DESCRIPTION

7. TOOLS USED AND DESCRIPTION:

Front end used: JAVA, Net beans

Back end used: MY SQL

Database used: MY SQL

Querying language: SQL


36/62

7.1 FRONT END USED:

Technology used (JAVA):

The language used is JAVA. The characteristics of java are:

Platform Independence

Object Oriented

Robust

Interpreted

Distributed

Dynamic

Safe and Secure

Multithreading

7.2 BACK END USED:

MySQL:

MySQL is the world's most popular open source database software, with over 100 million copies

of its software downloaded or distributed throughout its history. With its superior speed, reliability,

and ease of use, MySQL has become the preferred choice for Web, Web 2.0, SaaS, ISV, Telecom

companies and forward-thinking corporate IT Managers because it eliminates the major problems

associated with downtime, maintenance and administration for modern, online applications.

7.3 REASONS FOR TOOLS SECTED:

7.3.1 Reasons to use JAVA language as the front end language:

Java has been used just because of the platform independence and the facility of capturing packet

flowing on the network irrespective of its destination.

The basic reasons to use Java are:


37/62

Platform Independence: One of the most compelling reasons to move to java is its platform

independence. This feature helps to run our software on various operating systems.

Safe and Secure: This security feature helps in confining our software to the Java Environment

and not allowing it to access the other parts of computer. Java is one of the first programminglanguages to consider security as part of its design. The java language, compiler, interpreter and the

runtime environment were each developed with security in mind. The compiler, interpreter, API, and

java compatible browsers all contain several levels of security measures that are designed to reduce

the risk of security compromise, loss of data and program integrity, and damage to system user.

Object Oriented: This feature allows us to design our software from any blank state. This feature

of JAVA makes it simple and easy to extend our software.

Distributed Nature: Since JAVA handles TCP/IP protocols and designed for the distributed

environment of the Internet therefore this feature brings an unparalleled level of abstraction to client-

server programming.

Ease of Documentation and Maintenance

Java software is essentially self-documenting when doc comments and the java doc tool are used togenerate software documentation

7.3.2 Reasons to Use MySQL as the back end:

1. Scalability and Flexibility

The MySQL database server provides the ultimate in scalability, sporting the capacity to handle

deeply embedded applications with a footprint of only 1MB to running massive data warehouses

holding terabytes of information. Platform flexibility is a stalwart feature of MySQL with all flavors


38/62


39/62

8. Open Source Freedom and 24 x 7 Support

Many corporations are hesitant to fully commit to open source software because they believe they

can't get the type of support or professional service safety nets they currently rely on with proprietary

software to ensure the overall success of their key applications. The questions of indemnification

come up often as well. These worries can be put to rest with MySQL as complete around-the-clock

support as well as indemnification is available through MySQL Enterprise

9. Lowest Total Cost of Ownership

By migrating current database-drive applications to MySQL, or using MySQL for new

development projects, corporations are realizing cost savings that many times stretch into seven

figures. Accomplished through the use of the MySQL database server and scale-out architectures that

utilize low-cost commodity hardware, corporations are finding that they can achieve amazing levels of

scalability and performance, all at a cost that is far less than those offered by proprietary and scale-up

software vendors. In addition, the reliability and easy maintainability of MySQL means that database

administrators don't waste time troubleshooting performance or downtime issues, but instead can

concentrate on making a positive impact on higher level tasks that involve the business side of data.


40/62

8. IMPLEMENTATION

8. IMPLEMENTATION:

8.1 PROGRAMMING APPROACH FOLLOWED:

8.1.1 Top down Approach / Bottom up Approach

Top-down and bottom-up are strategies of information processing and knowledge ordering,

mostly involving software, but also other humanistic and scientific theories. In practice, they can be


41/62

seen as a style of thinking and teaching. In many cases top-down is used as a synonym ofanalysis or

decomposition, and bottom-up ofsynthesis.

The Top Down Approach :-

A top-down approach is essentially breaking down a system to gain insight into its

compositional sub-systems. In a top-down approach an overview of the system is first formulated,

specifying but not detailing any first-level subsystems. Each subsystem is then refined in yet greater

detail, sometimes in many additional subsystem levels, until the entire specification is reduced to base

elements. A top-down model is often specified with the assistance of "black boxes" that make it easier

to manipulate. However, black boxes may fail to elucidate elementary mechanisms or be detailed

enough to realistically validate the model.

Advantages of top-down programming:-

Separating the low level work from the higher level objects leads to a modular design.

Modular design means development can be self contained.

Having "skeleton" code illustrates clearly how low level modules integrate.

Much less time consuming (each programmer is only involved in a part of the big project).

Easy to maintain (if an error occurs in the output, it is easy to identify the errors generated

from which module of the entire program).

Disadvantages of top-down programming:

Functionality either needs to be inserted into low level objects by making them return "canned

answers"manually constructed objects, similar to what you would specify if you were mocking

them in a test, or otherwise functionality will be lacking until development of low level objects is

complete.

The Bottom Up Approach :-

A bottom-up approach is piecing together systems to give rise to grander systems, thus

making the original systems sub-systems of the emergent system. In a bottom-up approach the

individual base elements of the system are first specified in great detail. These elements are then

linked together to form larger subsystems, which then in turn are linked, sometimes in many levels,

until a complete top-level system is formed. This strategy often resembles a "seed" model, whereby


42/62

the beginnings are small but eventually grow in complexity and completeness. However, "organic

strategies" may result in a tangle of elements and subsystems, developed in isolation and subject to

local optimization as opposed to meeting a global purpose

In a bottom-up approach the individual base elements of the system are first specified in great

detail. These elements are then linked together to form larger subsystems, which then in turn are

linked, sometimes in many levels, until a complete top-level system is formed. This strategy often

resembles a "seed" model, whereby the beginnings are small, but eventually grow in complexity and

completeness.

Object-oriented programming (OOP) is a programming paradigm that uses "objects" to design

applications and computer programs.

In Mechanical Engineering with software programs such as Pro/ENGINEER and Solid works

users can design products as pieces not part of the whole and later add those pieces together to form

assemblies like building LEGOS. Engineers call this piece part design.

This bottom-up approach has one weakness. We need to use a lot of intuition to decide the

functionality that is to be provided by the module. If a system is to be built from existing system, this

approach is more suitable as it starts from some existing modules.

The Approach we used in our Project (Bottom-Up Approach):

The language that we are using i.e. Java is purely an Object Oriented Language. So the

programming approach that we have adopted is also Object Oriented. So, we've used the Bottom-Up

Programming Approach in our project. Now the idea behind using OOP is the advantage that we get

from it like : extensible, maintainable, easy debugging and so on.

8.1.2 Designing Pattern Used:-

Apart from that technical information about Java is that the project Hospital Management is

based on the well known design pattern called the MVC (Model-View-Controller) Architecture.

Introduction: -

A design pattern describes a proved solution to a recurring design problem, placing particular

emphasis on the context and forces surrounding the problem, and the consequences and impact of the

solution.

There are many good reasons to use design patterns. Here are three:


43/62

1. They are proved. You tap the experience, knowledge and insights of developers who have used

these patterns successfully in their own work.

2. They are reusable. When a problem recurs, you don't have to invent a new solution; you follow the

pattern and adapt it as necessary.

3. They are expressive. Design patterns provide a common vocabulary of solutions, which you can

use to express larger solutions succinctly.

It is important remember, however, that design patterns do not guarantee success. You can

only determine whether a pattern is applicable by carefully reading its description, and only after

you've applied it in your own work can you determine whether it has helped any. One of these patterns

is Model-View-Controller (MVC).


44/62

8.4 SCREENLAYOUTS:

8.4.1 FORMS LAYOUT:


45/62


46/62


47/62


48/62

8.TESTING


49/62


50/62

Once source code has been generated software must be tested to uncover as many errors as

possible before delivery to the customer. The goal is to design a series of test cases that have a high

likelihood of finding errors. This technique enters the picture it provides systematic guidance for

designing test, Exercise the internal logic, Exercise the input and output domain of the program to

uncover errors in the program, functions, behavior and performance.

Software testing is a critical element of software quality assurance and the ultimate review of

specification, design and code generation .Testing of the software leads to uncovering of errors in the

software and reveal that whether software functional and performance requirement are met. Testing

also provides a good indication of software reliability as software quality as a whole. The result of

different phases are evaluated and then compared with the expected results. If the errors are uncovered

they are debugged and corrected. A strategy approach to software testing has the generic

characteristics:

Testing begins at the module level and works outwards towards the integration of the entire

computer based system

Different testing technique are appropriate at different point of time

Testing and debugging are different activities, but debugging must be accommodating in the

testing strategy.

A strategy for the software testing must be accommodate low level tests that are necessary to

verify that a small source code segment is performing correctly according to the customers

requirement and that of developers expectations .

Testing Principles:

All tests should be traceable to customer requirements.

Tests should be planned long before testing begins.

The Pareto principle applies to software testing.

To be most effective, testing should be conducted by an independent third party.

9.3 OBJECTIVES OF TESTING METHODS:

Testing is a process of executing a program with the intent of finding an error

A good test case is one which has a high probability of finding an as yet undiscovered error

A successful test is one that uncovers an as yet undiscovered error


51/62

Our objective is to design tests that systematically uncovers different classes of errors and to do so

with minimum amount of time and effort

9.4 TESTING METHODS AND STRATEGIES:

Any engineered product can be tested in one of two ways:

White-Box Testing - Knowing the internal workings of a product, tests can be conducted to ensure

that the internal operation performs according to specification and all internal components have been

adequately exercised. White box testing considers system to be like a white box, which means that

everything about the system is known to us. We know the different programs and procedures used in

the system, inputs supplied and the output produced by it. The developers of the system generally

carry out white box testing. They test the system against all odd conditions for extreme values.

Stages of white box testing: -

The first level of testing is UNIT TESTING .In the system the small modules are tested

against the specified production during the design for the modules.

Unit testing is essential for verification of the code produced during the coding phase and hence the

goal is set to test the internal logic of the modules. In this stage all validation checks are again

rechecked against wrong data.

The next level of testing is INTEGRATION TESTING. In this all the tested modules arecombined into subsystems, which are then tested. The goal here is to see if the modules were

integrated properly, the emphasis being on testing interfaces between modules.


52/62

Black-Box Testing Knowing that a product has been designed to perform, tests can be conducted

that demonstrate each function is fully operational, at the same time searching for errors in each

function.

Black box testing, also called Behavioral testing, focuses on the functional requirements of the

software. It enables the software engineer to derive sets of input conditions that will fully exercise all

functional requirements for a program. It is a complementary approach to White-Box testing that is

likely to uncover a different class of errors.


53/62

Black Box testing attempts to find errors in the following categories:

Incorrect or missing functions Interface errors

Errors in data structures

Behavior or performance errors

Initialization and termination errors

The end users carry out black box testing. Selecting some persons who does not belong to thedeveloper team can perform this testing. The system should be check for different inputs given in the

system for different options and what should be the output thus generated by the system for those

values. They can then evaluate whether the system is working properly as per user requirements or

not. Tests are designed to answer the following questions:


54/62


55/62

Dispatch form

Action Expected Output

Add click If any field is empty. Fill in the required fields

message is displayed

If required fields are

correct.

User Created Successfully.

If any of the information is

incorrect.

Message is displayed to

amend that particular

information field.

Modify Click If any field is empty. Fill in the required fields

message is displayed

Provided information in all

the fields is correct.

Customer entries modified

successfully

If any of the information is

incorrect. Message is displayed to

amend that particular

information field.


56/62


57/62

10. MAINTENANCE

10. MAINTENANCE:


58/62

Maintenance is a set of software engineering activities that occur after software has been

delivered to customer and put into operation. Software configuration is a set of tracking and control

activities that begin when a software development project begins and terminate only when the

software is taken out of operation.

We may define maintenance into four categories:

1. Corrective Maintenance

The process that includes diagnosis and correction of one or more errors are called corrective

maintenance.

2. Adaptive Maintenance

An activity that modifies software to properly interface with a changing environment is both

necessary and commonplace called adaptive maintenance.

1. Perfective Maintenance

As software is used recommendation for capabilities, modifications to existing functions and

general enhancements are required from users. To satisfy requests in this category, perfective

maintenance is performed.

4. Preventive Maintenance

When the software is changed to improve future maintainability or reliability or to provide a better

basis for enhancements is often called preventive maintenance.


59/62


60/62

11.1 CONCLUSION /DISCUSSION:

The project report entitled "ONLINE EXAMINATION" has come to its final stage. The system

has been developed with much care that it is free of errors and at the same time it is efficient and less

time consuming. The important thing is that the system is robust. Also provision is provided for future

developments in the system. The entire system is secured. This online system will be approved and

implemented soon.

The On line test System is developed using Java and sql fully meets the objectives of the

system for which it has been developed. The system has reached a steady state where all bugs

have been eliminated. The system is operated at a high level of efficiency and all the teachers

and user associated with the system understands its advantage. The system solvesthe

problem.Itwasintended to solve as requirement specification.

12. BIBLIOGRAPHY


61/62

12. BIBLIOGRAPHY:

Books for Core Java:

Eckel Bruce thinking in java 3rd addition, Prenhall Professional publication.

Mughal A. Khalid, A Programmers Guide to Java SCJP Certification,

Publication: Pearson Education.

Schildt Herb, Complete Reference Java J2SE 5 edition, Tata Mcgraw Hill publication.

Books for JSP and Servlets:

Basham Bryan, Sierra Kathy, Bert Bates, Head First Servlets and JSP,O'Reilly Media

Publication.

Bayross Ivan, Shah Sharman, Shah Vaishali, Bayross Cynthia, Java Server Programming for

Professionals,Publisher : The X team.

Sites on Internet:
http://www.java.net/http://www.java.net/


62/62

plus, The Jbuilder tutorial, used in apticraft Systems Pvt. Ltd.

avnish verma 2

Documents