CAPSTONE PROJECT REPORT

(ONLINE COUNSELLING SYSTEM)

Submitted by

Devika Nag

Registration No: 10812468

Programme B.Tech

Section K28E3

Under the Guidance of

( MR. AMAN KAMBOJ)

Discipline of CSE

Lovely School of Technology

Lovely Professional University, Phagwara

1 | P a g e

CERTIFICATE

This is to certify that DEVIKA NAG bearing Registration no. 10812468 has

completed capstone project titled, “ONLINE COUNSELLING SYSTEM”

under my guidance and supervision. To the best of my knowledge, the present

work is the result of her original investigation and study. No part of the work

has ever been submitted for any other degree at any University.

The project is fit for submission and the partial fulfillment of the conditions

for the award.

Signature and Name of the Research SupervisorDesignationSchoolLovely Professional UniversityPhagwara, Punjab.

Date: 6th March 12

2 | P a g e

DECLARATION

I, DEVIKA NAG , student of B.TECH-MBA PC-160 under Department of

computer Science of Lovely Professional University, Punjab, hereby declare that all

the information furnished in this dissertation / capstone project report is based on my

own intensive research and is genuine.

This dissertation / report does not, to the best of my knowledge, contain part of my

work which has been submitted for the award of my degree either of this university or

any other university without proper citation.

Date : 25th Nov2011

DEVIKA NAG

Registration No.10812468

3 | P a g e

ACKNOWLEDGEMENT

I take this opportunity to present my votes of thanks to all those guidepost who really acted

as lightening pillars to enlighten our way throughout this project that has led to successful

and satisfactory completion of this study.

We are really grateful to our teacher for providing us with an opportunity to undertake this

project in this university and providing us with all the facilities. We are highly thankful to

Mr. AMAN KAMBOJ for his active support, valuable time and advice, whole-hearted

guidance, sincere cooperation and pains-taking involvement during the study and in

completing the assignment of preparing the said project within the time stipulated.

Lastly, We are thankful to all those, particularly the various friends , who have been

instrumental in creating proper, healthy and conductive environment and including new and

fresh innovative ideas for us during the project, their help, it would have been extremely

difficult for us to prepare the project in a time bound framework.

4 | P a g e

Contents

1. Organization Overview……………………………………………………………….6

2. Profile of the Problem…………………………………………………………………6

3. Existing System………………………………………………………………………..7

3.1 Introduction……………………………………………………………………………7

3.2 Existing Software.……………………………………………………………………...8

3.3 DFD for present system………………………………………………………………8-10

3.4 What’s new in the system to be developed…………………………………………….11

4Problem Analysis………………………………………………………………………….11

4.1Product definition…………………………………………………………………...11-12

4.2 Feasibility Analysis…………………………………………………………………13-15

4.3Project Plan………………………..……………………………………………………16

5 Software Requirement Analysis….………………………………………………………17

5.1 Introduction..…………………………………………………………………………...17

5.2 General Description……………………………………………………………………...17

5.3 Specific Requirements…………………………………………………………………...18

6 Design…..…………………………………………………………………………………19

6.1 System Design…………………………………………………………………………19

6.2 Design Notations…………………………………………………………………………20

6.3 Detailed Design………………………………………………………………………21-23

6.4 Entity Relational Diagram……………………………………………………………..24

6.5 Flowcharts………………………………………………………………………………..25

6.6 Pseudo Code…………………………………………………………………………….26

7 Testing……………… …………………………………………………………………..29

7.1 Functional Testing………………………………………………………………………29

7.2 Structural Testing………………………………………………………………………30

7.3 Level of testing…………………………………………………………………………30

7.4 Testing the Project…………………………………………………………………….31

8 Implementation…………………………………………………………………………34

5 | P a g e

8.1 Implementation of Project………………………………………………………………35

8.2 Post Implementation and Software maintenance…………………………………………35

9 Project Legacy………………………………………………………………………………36

9.1 Current status of the project………………………………………………………………36

9.2 Remaining areas of the concern…………………………………………………………..36

9.3 Technical and managerial lessons learnt………………………………………………….36

10 User Manual………………………………………………………………………………..37

11 Source Code………………………………………………………………………………..43

12 Bibliography……………………………………………………………………………….124

6 | P a g e

1. ORGANIZATION OVERVIEW

The name of my organization is Lovely Professional University (Lpu). It has a 600 + Acres

Campus: A technology driven campus, spreed over 600 + acres of lush green area on NH-1 at

the entry of Jalandhar city.

LPU provides a Professional learning Environment that acts as a catalyst for the exponential

growth of students academics as well as extracurricular abilities.

LPU is India’s Largest University with 25,000+ students (on one campus) from across 26

States of India and 16 Countries around the world.

LPU is duly recognized by UGC and other Apex Bodies and has accreditations of various

national and International bodies and associations.

LPU has a strong internationalization strategy where LPU wants to be regarded as a

university with a global perspective. LPU has 25+ international tie-ups.

7 | P a g e

2. PROFILE OF THE PROBLEM

The profile of the problem is that in previous time, counseling of any university or colleges was held

through paper work, that means for attending that counseling we had to arrived on the place where

university/colleges is located. But now we can track student and perents contacts at the individual

level.

So with the help of counseling system we can solve the problem through:-

Referral Tracking:- Track referrals to and from outside professionals as well as

referrals made internally within your organization. Simultaneously track multiple

referrals for individual students

Guideince Curriculum:-With the Deep Well Data Service (DWDS) Elementary

Counseling Data System, counselors are able to track their delivered curriculum by

date.

Counselor Time Sheet:- Counselors can track their time spent in the four objective

areas of Individual Planning, System Support, Curriculum Development, and

Responsive Service. These categories can be added to or modified to meet the needs

of your project.

8 | P a g e

3.1 EXISTING SYSTEM

Introduction:-

Present system or Existing system of “Counseling Management System” working

manually or computerized in a building. Therefore all types works are maintain in

building. So maintain all the counseling procedure very difficult.

If we are reporting, then we need go to the University and get a form for reporting

and fill the form and submit in the queue conditions. Then verify there form by the

university and maintain the record in computer or register.

The system is mainly related to online counseling management system. Which is

developing an online web based application system, it is necessary to make a

thorough study of the existing system .There is no online Counseling Management

System .The all the information not maintains globally. Therefore to maintain all the

information of university is very difficult.

Limitations of the Existing System: -

The maintenance of various records and procedure of reporting are being done

manually by the counseling department. This leads to many drawbacks some of

which are:

It is a time consuming process.

Proper arrangements should be made before and after the examination -which is both

money spending and time consuming.

As the number of student’s increases counseling process becomes more and more

difficult.

Not globally maintain the information

Evaluating of answer sheets also consumes heavy amount of time.

Difficult to management the all types of information of college or university.

Existing Software:-

9 | P a g e

There are a number of attributes of software that can serve as requirements. It is important

that required attributes by specified so that their achievement can be objectively verified. The

following items provide a partial list of examples.

The input system will allow for inputting numbers, operands, special symbols and letters of

the alphabets.

DFD of present system:-

0 Level Diagram

Request for Reporting

10 | P a g e

Student Counseling Process

University Database

1 Level Diagram

11 | P a g e

2 Level Diagram

12 | P a g e

What’s new in the system to be developed:-

The new in this system is as follow:-

The candidates can submit the documentation form of counseling by website.

We can do the changes like modify, delete, choices etc until we submit the form, and we can

transfer the fees from online transaction.

No time consuming.

13 | P a g e

4. Problem Analysis

Product definition:-

C#.NET

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

programming language.

The language, and implementations thereof, should provide support for software engineering

principles such as strong type checking, array bounds checking, detection of attempts to use

uninitialized variables, and automatic garbage collection. Software robustness, durability,and

programmer productivity are important.

The language is intended for use in developing software components suitable for deployment

in distributed environments.

Source code portability is very important, as is programmer portability, especially for those

programmers already familiar with C and C++.

Support for internationalization is very important.

C# is intended to be suitable for writing applications for both hosted and embedded systems,

ranging from the very large that use sophisticated operating systems, down to the very small

having dedicated functions.

Although C# applications are intended to be economical with regard to memory and

processing power requirements, the language was not intended to compete directly on

performance and size with C or assembly language.

FEATURES

There are no global variables or functions. All methods and members must be declared

within classes. Static members of public classes can substitute for global variables and

functions.

Local variables cannot shadow variables of the enclosing block, unlike C and C++. Variable

shadowing is often considered confusing by C++ texts.

14 | P a g e

C# supports a strict Boolean datatype, bool. Statements that take conditions, such as while

and if, require an expression of a type that implements the true operator, such as the boolean

type. While C++ also has a boolean type, it can be freely converted to and from integers, and

expressions such as if(a) require only that a is convertible to bool, allowing a to be an int, or

a pointer. C# disallows this "integer meaning true or false" approach on the grounds that

forcing programmers to use expressions that return exactly bool can prevent certain types of

common programming mistakes in C or C++ such as if (a = b) (use of assignment = instead

of equality ==).

In C#, memory address pointers can only be used within blocks specifically marked as

unsafe, and programs with unsafe code need appropriate permissions to run. Most object

access is done through safe object references, which always either point to a "live" object or

have the well-defined null value; it is impossible to obtain a reference to a "dead" object , or

to a random block of memory. An unsafe pointer can point to an instance of a value-type,

array, string, or a block of memory allocated on a stack.

Code that is not marked as unsafe can still store and manipulate pointers through the system.

Managed memory cannot be explicitly freed; instead, it is automatically garbage collected.

Garbage collection addresses the problem of memory leaks by freeing the programmer of

responsibility for releasing memory which is no longer needed.

In addition to the try...catch construct to handle exception.

Multiple inheritance is not supported, although a class can implement any number of

interfaces. This was a design decision by the language's lead architect to avoid complication

and simplify architectural requirements throughout CLI.

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

considered safe, such as widening of integers. This is enforced at compile-time, during JIT,

and, in some cases, at runtime. There are no implicit conversions between booleans and

integers, nor between enumeration members and integers (except for literal 0, which can be

implicitly converted to any enumerated type). Any user-defined conversion must be

explicitly marked as explicit or implicit, unlike C++ copy constructors and conversion

operators, which are both implicit by default. Starting with version 4.0, C# supports a

"dynamic" data type that enforces type checking at runtime only.

15 | P a g e

Enumeration members are placed in their own scope.

C# provides properties as syntactic sugar for a common pattern in which a pair of methods,

accessor (getter) and mutator (setter) encapsulate operations on a single attribute of a class.

Full type reflection and discovery is available.

C# currently (as of version 4.0) has 77 reserved words.

Checked exceptions are not present in C#. This has been a conscious decision based on the

issues of scalability and versionability.

Feasibility Analysis:-

Feasibility is the determination of whether or not a project is worth doing. The process

followed in making this determination is called a feasibility study. In other words a

feasibility study is carried out to select the best system that meets performance requirements.

Once it has been determined that a project is feasible, the analyst can go ahead and prepare

the project specification which finalizes project requirements. Generally, feasibility studies

are undertaken within tight time constraints and normally culminate in a written and oral

feasibility The contents and recommendations of such a study will be used as a sound basis

for deciding whether to proceed, postpone or cancel the project. Thus, since the feasibility

study may lead to the commitment of large resources, it becomes necessary that it should be

conducted competently and that no fundamental errors of judgment are made. In the conduct

of the feasibility study, the analyst will usually consider seven distinct, but interrelated types

of feasibility. Three of them, which are used hugely, are as follows:

Technical Feasibility

Operational Feasibility

Economic Feasibility

TECHNICAL FEASIBILITY

This is concerned with specifying equipment and software that will successfully satisfy the

user requirement. The technical needs of the system may vary considerably, but might

16 | P a g e

include:The facility to produce outputs in a given time.Response time under certain

conditions.Ability to process a certain volume of transaction at a particular speed.Facility to

communicate data to distant location In examining technical feasibility, configuration of the

system is given more importance than the actual make of hardware.The configuration should

give the complete picture about the system’s requirements: How many workstations

required? How these units are interconnected so that they could operate and communicate

smoothly. What speeds of input and output should be achieved at particular quality of

printing. This can be used as a basis for the tender document against which dealers and

manufacturers can later make their equipment bids. Specific hardware and software products

can then be evaluated keeping in view with the logical needs.

At the feasibility stage, it is desirable that two or three different configurations will be

pursued that satisfy the key technical requirements but which represent different levels of

ambition and cost. Investigation of these technical alternatives can be aided by approaching a

range of

suppliers for preliminary discussions. Out of all types of feasibility, technical feasibility

generally is the most difficult to determine.

ECONOMICAL FEASIBILITY

Economic analysis is the most frequently used technique for evaluating the effectiveness of a

proposed system. More commonly known as cost/benefit analysis; the procedure is to

determine the benefits and savings that are expected from a proposed system and compare

them with costs.

If benefits outweigh costs, a decision is taken to design and implement the system.

Otherwise, further justification or alternative in the proposed system will have to e made if it

is to have a chance of being approved. This is an ongoing effort that improves in accuracy at

each phase of the system life cycle.

OPERATIONAL FEASIBILITY

It is mainly related to human organizational and political aspects. The points to be considered

are:-

17 | P a g e

What changes will be brought with the system?

What organizational structures are disturbed?

What new skills will be required? Do the existing staff members have these skills? If not, can

they be trained in due course of time?

Generally project will not be rejected simply because of operational infeasibility but such

considerations are likely to critically affect the nature and scope of the eventual

recommendations. This feasibility study is carried out by a small group of people who are

familiar with information system techniques, who understand the parts of the business that

are relevant to the project and are skilled in system analysis and design process.

Project Plan

Planning and Scheduling is the detailed study of the various operations performed by a

system and their relationships within and outside of the system. During Planning and

Scheduling, data are collected on the available files, decision points, and transaction handled

by the present system. The planning and decision making is the good criteria to the

development of the project.

System analysis is simply uses several types of model and System Testing to their development

that is why the project get completed.

18 | P a g e

Requirements Analysis

Design

Coding

Testing

Maintenance

5. Software Requirement Analysis

Introduction:-

PROBLEM DEFINITION

Problem definition encompasses those tasks that go into determining the needs or conditions

to meet for buying books. It can be a long and arduous process. Analysis includes several

techniques to elicit the requirements from the customer. Historically, it included such things

as holding interviews and creating requirements lists. More modern techniques include

prototyping, and use cases. Where necessary, the analysis can be combination of these

methods to establish the exact requirements of the stakeholders, so that a system that meets

the business needs is produced.

Requirement Specification

Microsoft Windows XP/Vista Professional Operating System

Microsoft Visual Studio 2008

Microsoft SQL Server 2005

General Description:-

Data from students seeking admission will be stored with the help of an integrated

database application. The database would be linked to a frontend creating a user friendly

interface for easy access and manipulation of data as well as report generation.

The information flow would be as:

Login page:

Verifies user identity and grant the appropriate access to ensure data security.

Admin view page:

Displays the various operations that can be performed by the

19 | P a g e

administrator on the database.

This includes:

Access to candidate’s database

View complete list

Generate list of eligible students

Apply filter

Generate list of selected students

Export to Excel

Fill registration form

Access to counseling page

Take printout

Registration page:

Allows details to be entered in the database through forms

The resulting list of records can also be exported to an excel spreadsheet.

Specific Requirement Analysis:-

Information gathering is usually the first phase of the software development project. The purpose of

this phase is to identify and doucument the exact requirements for the system. The user’s request

identifies the need for a new information system and on investigation re-defined the new information

system and on investigation re-defined the new problem to be based on MIS, which supports

management. The objective is to determine whether the request is valid anf feasible before a

recommendation is made to build a new or existing manual system continues.

The major steps are:- Defining the user requirements, Studying the present system to verify the

problem, and defining the performance expected by the candidate to use requirements.

Language (Front-End) : .NET FRAMEWORK 2008

Database (Back-End) : Microsoft SQL Server 2005

Operating System : Windows NT/2000/XP/VISTA

20 | P a g e

6. Design

System Design

Introduction: -

The objective of the system design is to deliver the requirements as specified in the

feasibility report. System design involves first logical design (logical design) and then

physical construction (detailed design) of the system. The logical design describes the

structure and characteristics of features, such as the outputs, inputs, files, databases, and

procedures. The physical construction produces actual program software, files, and a working

system.

System design goes through two phases of development: -

Logical Design

Physical Design

Logical Design:-

We know that a data flow diagram shows the logical flow of a system and defines the

boundaries of the system. Logical design specifies the user need at a level of details that

virtually determine the information flow into and out of the system and the required data

resources. Logical design describes the inputs, outputs, database and procedures .All in a

format that meets the user’s requirements.

Physical Design:-

It provides the working system by defining the design specification that tells programmers

exactly what that candidate system must do. In short it can state that physical design is the

implementation of the logical design.

Physical system design consists of the following-

Design the physical system

Specify input, output media

21 | P a g e

Design the database and specify backup procedures.

Design physical information flow through the system and a physical design walkthrough.

Plan system implementation

Module Description:-

Online Counseling System with the fallowing modules: -

Counseling – Helps in Category wise counseling

Institute record –covering Details regarding Institute

Student record - covering Details regarding Students

Design Notations:-

Data Process Data Storage Entity

Relationship

Flow

Input/Output

22 | P a g e

Detailed Design

There are some symbols that are used in the drawing of business process diagrams (data flow

diagrams). These are now explained, together with the rules that apply to them.

Flow diagrams in general are usually designed using simple symbols such as a rectangle, an

oval or a circle depicting a processes, data stored or an external entity, and arrows are

generally used to depict the data flow from one step to another.

A DFD usually comprises of four components. These four components can be represented by

four simple symbols. These symbols can be explained in detail as follows: External entities

are represented by squares; Processes (input-processing-output) are represented by rectangles

with rounded corners; Data Flows are represented by arrows; and finally, Data Stores are

represented by open-ended rectangles.

Data flow diagrams present the logical flow of information through a system in graphical or

pictorial form. Data flow diagrams have only four symbols, which makes useful for

communication between analysts and users. Data flow diagrams (DFDs) show the data used

and provided by processes within a system. DFDs make use of four basic symbols.

Create structured analysis, information flow, process-oriented, data-oriented, and data

process diagrams as well as data flowcharts.

External Entity

An external entity is a source or destination of a data flow which is outside the area of study.

Only those entities which originate or receive data are represented on a business process

diagram. The symbol used is an oval containing a meaningful and unique identifier.

Data Process

A process shows a transformation or manipulation of data flows within the system. The

symbol used is a rectangular box which contains 3 descriptive elements:

23 | P a g e

Firstly an identification number appears in the upper left hand corner. This is allocated

arbitrarily at the top level and serves as a unique reference.

Secondly, a location appears to the right of the identifier and describes where in the system

the process takes place. This may, for example, be a department or a piece of hardware.

Finally, a descriptive title is placed in the centre of the box. This should be a simple

imperative sentence with a specific verb, for example 'maintain customer records' or 'find

driver'.

Data Flow

A data flow shows the flow of information from its source to its destination. A data flow is

represented by a line, with arrowheads showing the direction of flow. Information always

flows to or from a process and may be written, verbal or electronic. Each data flow may be

referenced by the processes or data stores at its head and tail, or by a description of its

contents.

Data Store

A data store is a holding place for information within the system:

It is represented by an open ended narrow rectangle. Data stores may be long-term files such

as sales ledgers, or may be short-term accumulations: for example batches of documents that

are waiting to be processed. Each data store should be given a reference followed by an

arbitrary number.

External Entities

It is normal for all the information represented within a system to have been obtained from,

and/or to be passed onto, an external source or recipient. These external entities may be

duplicated on a diagram, to avoid crossing data flow lines. Where they are duplicated a stripe

is drawn across the left hand corner, like this. The addition of a lowercase letter to each entity

on the diagram is a good way to uniquely identify them.

24 | P a g e

Processes

When naming processes, avoid glossing over them, without really understanding their role.

Indications that this has been done are the use of vague terms in the descriptive title area -

like 'process' or 'update'. The most important thing to remember is that the description must

be meaningful to whoever will be using the diagram.

Data Flows

Double headed arrows can be used (to show two-way flows) on all but bottom level

diagrams. Furthermore, in common with most of the other symbols used, a data flow at a

particular level of a diagram may be decomposed to multiple data flows at lower levels.

25 | P a g e

Entity Relational Diagram:-

26 | P a g e

student counseling

Roll no.category Rank

name U_code

U_name U_add

CollegeAffiliation

C_codeC_name

C_adds

Flowcharts:-

Counseling System Flow Chart

Yes

No

Yes

No

27 | P a g e

Counseling System Login Page

Main Page

Add Student

Registration Page Add More

View Seats Remaining

Generate Result

View Student Page List

Import To Excel

Print

Seats still left

Stop

Pseudo code

For login page

1. If student is not add then registered.

2. Already registered then view seats.

3. Search the marks.

4. Give rating.

5. Join group.

6. Display on site

28 | P a g e

7. Testing

7.1 FUNCTIONAL TESTING : - Functional testing is a type of black box testing that bases its

test cases on the specifications of the software component under test. Functions are tested by

feeding them input and examining the output, and internal structure program is rarely structured.

Test case design focuses on a set technique for the cases that meet overall testing objectives. In

test case design phase, the engineer creates a series of test cases that are, intended to “demolish”

the software that has been built.

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

Knowing the specific function that a product has been designed to perform, test can

be conducted that demonstrate each function is fully operational, at the same time

searching for errors in each function. This approach is known as black box testing.

Knowing the internal working of a product, test can be conducted to ensure that

internal operation performs according to specification and all internal components

have been adequately exercised. This approach is know as white-box testing.

Black box testing is designed to uncover errors. They are used to demonstrate that software

function are operations; that input is properly accepted and output is correctly produced; and that

integrity of external information is maintained (e.g. data files.). A black box examines some

fundamental aspects of a system with little regard for the internal logical structure of the

software.

White box testing of software is predicated on close examination of procedural details. Providing

test cases that exercise specific set of conditions and loops test logical paths through the

software. The “state of the program” may be examined at various points to determine if the

expected or asserted status corresponds to the actual status.

29 | P a g e

7.2 STRUCTURAL TESTING: - Structural system testing is designed to verify that the

developed system and programs work. The objective is to ensure that the product designed is

structurally sound and will function correctly. It attempts to determine that the technology has

been used properly and that when all the component parts are assembled they function as a

cohesive unit.

The quality of a product or item can be achieved by ensuring that the product meets the

requirements by planning and conducting the following tests at various stages

Unit Tests at unit level, conducted by development team, to verify individual standalone

units.

Integration Tests after two or more product units are integrated conducted by

development team to test the interface between the integrated units.

Functional Test prior to the release to validation manager, designed and conducted by the

team independent of designers and coders, to ensure the functionality provided against

the customer requirement specifications.

Acceptance Tests prior to the release to validation manger, conducted by the

development team, if any supplied by the customer.

Validation Tests prior to customer, conducted by the validation team to validate the

product against the customer requirement specifications and the user documentation.

Regression Testing is the re-execution of some subsets of tests already been conducted to

ensure that changes are not propagated unintended side effects.

7.3 LEVEL OF TESTING: -

In order to uncover the errors present in different phases, we have the concept of levels of

testing. The basic levels of testing are:

Client Needs Acceptance Testing

Requirements System Testing

30 | P a g e

Design Integration Testing

Code Unit Testing

Fig. Level of Testing

Integration Testing

In this process of testing it is incremented approach to construction of program structure.

Modules are integrated moving downward beginning with main control module. Modules

subordinate structure to main control module is incorporated into structure. This form of testing

is performed of software in five steps: -

1. Main control module is used as test driver and stubs (modules) are substituted for

all components subordinate to main control.

2. Depending on integration selected subordinate stubs are replaced one at a time.

3. Tests are conducted as each component is integrated.

4. On completing each set of tests another stub is replaced.

5. It is also tested to ensure that new errors have not been introduced.

In well-factored program structure decision-making occurs at upper levels in hierarchy and

therefore encountered first. If major control problem do exist, early recognition is essential. This

is termed as top-down integration testing.

Bottom-up integration testing begins construction and testing with atomic modules as the

components are integrated from the bottom-up, processing required for components subordinate

to a given level is always available and the need for stubs is eliminated.

31 | P a g e

Low-level components are combined into clusters that perform a specific software function.

A driver (a control program for testing) is written to coordinate test case input and output.

The cluster is tested.

Drivers are removed and clusters are combined moving upward in the program structure.

Each time a new module is added as part of integration testing, the software changes. New data

flow paths are established, new I/O can occur, and new control logic is invoked. These changes

cause problems with functions that previously worked flawlessly. In context of integration test

strategy

Successful tests result in discovery of errors and errors must be corrected. When software is

corrected some aspect of software configuration is changed.

Smoke testing

It is an integration testing that is commonly used when “shrink wrapped” software products are

being developed. It is designed as pacing mechanism for time critical projects, allowing us to

assess the project on frequent basis. This consists of steps: -

Software components are translated into code are integrated into a “build”. A build

includes all data files, libraries, reusable modules and engineered components.

A series of tests is designed to expose errors that will keep the build from properly

performing its function.

The build is integrated with other builds and the entire product is smoke tested daily.

Validation Testing prior to customer, conducted by the validation team to validate the product

against the customer requirement specifications and the user documentation.

7.4 TESTING THE PROJECT: -

The best testing is to test each subsystem separately as we have done in our project. It is best to

test a system during the implementation stage in form of small sub steps rather then large

32 | P a g e

chunks. We have tested each module separately i.e. have completed unit testing first and system

testing was done after combining /linking all different Modules with different menus and

thorough testing was done. Once each lowest level unit has been tested, units are combined with

related units and retested in combination. These proceeds hierarchically bottom-up until the

entire system is tested as a whole. Hence we have used the Top Up approach for testing our

system.

Appropriate Validation Checks

S .no Test cases Expected value Actual value

1 If incorrect username or

password.

Error message

must be

displayed

Displayed

2 If user log in Logout must

be displayed

Displayed

5 changes in marks description The new

description

must be saved

into database

Updated

6 If user log out The home

page must be

displayed

Displayed

33 | P a g e

8. IMPLEMENTATION

8.1 IMPLEMENTATION OF THE PROJECT: - The result indicated a considerable time

saving with the candidate system and comes out with fast and efficient development.

Implementation is the process of having system personnel check out and put new software into

use, trained user, installs the new application and constructs any strategies. Sometimes system

developers may choose to pilot the operation in only area of the firm, say in one department or

with only one or two persons. Sometimes they run old and new systems together to compare the

result.

The implementation phase is less creative than system design. Implementation means the process

of converting a new or a revised system design into an operational one. It is primarily concerned

with user training, site preparation, and file conversion. When the candidate system is linked to

terminals or remote sites, the telecommunication network and tests of the network along with the

system are also included under implementation.

Implementation is the realization of an application, or execution of a plan, idea, model, design,

specification, standard, algorithm, or policy.

In computer science, an implementation is a realization of a technical specification or algorithm

as a program, software component, or other computer system. Many implementations may exist

for a given specification or standard. For example, web browsers contain implementations of

World Wide Web Consortium-recommended specifications, and software development tools

contain implementations of programming languages.

In the IT Industry, implementation refers to post-sales process of guiding a client from purchase

to use of the software or hardware that was purchased. This includes Requirements Analysis,

Scope Analysis, Customizations, Systems Integrations, User Policies, User Training and

Delivery. These steps are often overseen by a Project Manager using Project Management

Methodologies set forth in the Project Management Body of Knowledge. Software

Implementations involve several professionals that are relatively new to the knowledge based

34 | P a g e

economy such as Business Analysts, Technical Analysts, Solutions Architect, and Project

Managers.

In political science, implementation refers to the carrying out of public policy. Legislatures pass

laws that are then carried out by public servants working in bureaucratic agencies. This process

consists of rule-making, rule-administration and rule-adjudication. Factors impacting

implementation include the legislative intent, the administrative capacity of the implementing

bureaucracy, interest group activity and opposition, and presidential or executive support.

8.2 POST IMPLEMENTATION AND SOFTWARE MAINTENANCE: - After the

installation phase is completed and the user staff is adjusted to the changes created by the

candidate system, evaluation and maintenance begin. Like any system, there is an aging process

that requires periodic maintenance of hardware and software. If the new information is

inconsistent with the design specifications, then changes have to be made. Hardware also

requires periodic maintenance to keep in tune with design specifications. The importance of

maintenance is to continue to bring the new system to standards.

For the maintenance it has to be regularly checked whether all the devices are working properly.

If any of the devices on network is not working then that has to be checked and amended in time.

35 | P a g e

9. PROJECT LEGACY

9.1 CURRENT STATUS OF THE PROJECT: - Till now, each modules, from index page to thanks page are working so fine, and the result of each pages are meeting to the requirements very well. The current status of the project is that the basics of discovering and

starting the projects are functional.

9.2 REMAINING AREAS OF CONCERN: - No remaining areas were left anymore. All the modules have been accomplished with required controls.

9.3 TECHNICAL AND MANEGERIAL LESSONS LEARNT: - During the development of system, I have learnt so many assets about tools, system language and many more like:

1) I got to know how the classes(eg dataReader, dataset) fetches data and create table.

2)Moreover, files like Class file helps me to create numerous method.

36 | P a g e

USER MANUAL

37 | P a g e

38 | P a g e

39 | P a g e

40 | P a g e

41 | P a g e

42 | P a g e

Bibliography

• WIKIPEDIA

• MICROSOFT ONLINE SUPPORT

• DATABASE AND .NET SUPPORT FROM ENVIGO MARKETING PRIVATE

LIMITED

• W3SCHOOLS

43 | P a g e