Councelling System PDF

APPLICATION ON STUDENT COUNSELLING SYSTEM
INDEX
Sl.No
PARTICULARS
PAGE. NO
Introduction
3-4
Objective and Scope of the Project
5-9
Theoretical Background definition of problem Statement
10-12
System analysis and design
13-17
4.1
Requirement Analysis
4.2
System Design
4.3
Use case model
System Planning (PERT Chart)
18-21
Methodology Adopted
22-27
6.1
Waterfall model
System Implementation & Details of Hardware & Software

Used.
7.1
System Implementation
7.2
Hardware Requirement
7.3
Software Requirement
28-32
System Maintenance and Evaluation
33-35
Cost and Benefit Analysis
36-39
RANI CHANNAMMA UNIVERSITY, BELGAUM
PAGE | 0
10
Detailed Life Cycle of the Project

10.1
E-R Diagram
10.2
Data Flow Diagram
40-44
11
Input and Output Screen Designs
45-49
12
Process Involved
51-52
13
Methodologies Used for Testing
53-58
14
User or Operational Manual ,Annexure,References
59-62
PAGE | 1
ABSTRACT
The Online Counseling System is developed to enhance counseling. The
software will be great relief to the students. The Online Counseling System is developing to
enhance the counseling, which fully works as an online. This software will be great relief to
the student for Reporting, Registration and searching the information about college and
university.
This software gives an overview of the entire institute in a sort interval time
and will be also great help to University to manage in the whole counseling procedure by their
paper work and reducing their time.
PAGE | 2
Introduction
PAGE | 3
INTRODUCTION OF THE PROJECT

Types of information Online, and Efficient and systematic maintenance of the huge
Database, speeding up queries and faster processing are also be factor for going for this
project.
This system is applicable for any other university /Institute, which is work as
an online. The package will require data to be entered in user-friendly forms.
This system provide the scope of online working using the internet such as Student reporting, counseling, Institute registration for counseling, searching the information
of counseling procedure and total Seats of college etc.
There are fallowing modules and forms are used-
(1) Institute Record.

(2) Student Record.
(3) Counseling.
(4) Categorys selection form.
(5) Reporting, Withdraw.
PAGE | 4
OBJECTIVE AND
SCOPE OF THE
PROJECT
PAGE | 5
Objective:
Online counseling System is fully work as online using the internet, which is
provides facility online such as- Student Counseling, Managing the student record, Managing
the Institute record and Searching the any other information about Counseling
procedure/Institutes, this types of information easy to search through the website.
PAGE | 6
Scope of the Project

Reduce the problem, which is faced in Existing System. So In the proposed
system, Online Counseling System will
provide the on line facility for reporting /
registration or access any type of information about the college/university and globally
maintain all the information by the university and this project consist fallowing modules are:(1) Institute Record: Provide the fallowing types of facilities using different options: Insert:- This part allow any new institute, if we want to participate in counseling then
enter its details regarding the institute -
Institute Code ,Name of the institute, Name of the
city, Category wise total number of seats i.e. General Seats, OBC Seats, SC/ST seats.
Search: - It provides Searching for any institute details.
- On the basis of its code.
- On the basis of its name.
Delete: - If any institute Withdraw from counseling then this part will help in deleting
that
institute record.
Display: - It will help in displaying complete information about institute code name,
city, and total seats according to category.
2) Student record: This module has two parts: Search: - This will provide help in searching record of any student who is allotted
seats in an institute during counseling procedure.
PAGE | 7
Delete: - This will allow to deleting record of any student after counseling. The
deletion can be on the basis of Roll no, Name.
(3) Counseling: This is the third and important module .It is divided into category wise counseling. So
there are three modes of counseling.
(a) General counseling:Candidates in General Category enter in this counseling then he is allotted to
see the status of vacant and occupied general eats in every institute the process
STATUS if the satisfied he is allotted seats .In this procedure candidate fill the
complete form which includes details
Name, Roll No, Rank, Sex, Category, etc.
But any Student want to withdraw after allotted the seats then can be withdraw with
the help in deleting the student record.
b) OBC counseling:Candidates in OBC Category enter in this counseling then he is allotted
to see the status of vacant and occupied general eats in every institute the process
STATUS if the satisfied he is allotted seats . In this procedure candidate fill the
complete form which includes detailsName, Roll No, Rank, Sex, Category, etc.
But any Student want to withdraw after allotted the seats then can be withdraw with
the help in deleting the student record
PAGE | 8
(c) C/ST Counseling:Candidates in SC/ST Category enter in this counseling then he is allotted to
see the status of vacant and occupied
general seats in every institute the process
STATUS if the satisfied he is allotted seats .In this procedure candidate fill the complete
form which includes details
Name,
Roll no, Rank, Sex, Category, etc.

But any Student want to withdraw after allotted the seats then can be withdraw with the help
in deleting the student record.
Features: The proposed system will aim to automate all the activities and eliminate all the
drawbacks that the existing system of manual operation faces. The important features of
functionality of the proposed system are listed belowThe proposed system will save significant amount of time and effort invested by the
university every year.
The System fully works as an online.
Centralized maintain all information.
It helps the university to dynamically add records to the database.
Easy to Searching the information about college or university.
Easy to managing whole counseling procedure
PAGE | 9
THEORETICAL
BACKGROUND AND
DEFINATION OF
PROBLEM
PAGE | 10
Theoretical Background
Existing System: 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
PAGE | 11
Problem Definition
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 students 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
Further more, manual evaluation is prone to errors.
PAGE | 12
SYSTEM ANALYSIS
AND
DESIGN
PAGE | 13
4. System Analysis
System Analysis is a detailed study of the various operations performed by a system
and their relationship within and outside the system .It is a systematic technique that defines
goals and objectives the goal of the development is to deliver the system in the line with the
users requirements, and analysis is this process.
System study has been conducted with the following objectives in mind:
Identify the clients need.
Evaluate the system concept for feasibility.
Perform economical and technical analysis.
Allocate functional to hardware, software, people, database and other system

elements
Establish cost and schedule constraints.
Both hardware and software expertise is required to successfully attain the

objectives.
4.1 Requirement Analysis: Information gathering is usually the first phase of the software
development project. The purpose of this phase is to identify and document the exact
requirements for the system. The users request identifies the need for a new information
system and on investigation re-defined the new problem to be based on MIS, which supports
PAGE | 14
management. The objective is to determine whether the request is valid and feasible before a
recommendation is made to build a new or existing manual system continues.
4.2 SYSTEM DESIGN

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: 1. Logical Design
2. Physical Design
4.2.1 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 users requirements.
PAGE | 15
4.2.2 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 following1) Design the physical system
Specify input, output media
Design the database and specify backup procedures.
2) Plan system implementation
PAGE | 16
4.3 System design:

4.3.1 Use Case Model:
- User
- Process (Task)
- Tags <<
>>
PAGE | 17
USER REQURIMENTS
AND SYSTEM
PLANNING
PAGE | 18
5. PERT Chart
A Pert chart is a graphical representation of a projects schedule, showing the
sequence of tasks, which tasks can be performed simultaneously, and the critical path of tasks
that that must be completed on time in order for the project to meet its completion deadline.
The chart can be constructed with a variety of attributes, such as earliest and latest finish dates
for each task, and slack time between tasks.
A PERT chart can document an entire project or a key phase of a project. The chart
allows a team to avoid unrealistic timetables and schedule expectations, to help identify and
shorten tasks that are bottlenecks, and to focus attention on most critical tasks.
When to use it:
Because it is primarily a project-management tools, a PERT chart is most useful for
planning and tracking entire projects or for scheduling and tracking the implementation phase
of a planning or improvement effort.
How to use it:
Identify all tasks or project components. Make sure the team includes people with
firsthand knowledge of the project so that during the brainstorming session all component
tasks needed to complete the project are captured. Document the tasks on small note cards.
Identify the first task that must be completed. Place the appropriate card at the extreme left of
the working surface. Identify any other tasks that can be started simultaneously with task #1.
Align these tasks either above or below task #1 on the working surface.
PAGE | 19
Identify the next task that must be completed. Select a task that must wait to begin
until task #1(or a task that starts simultaneously with task #1) is completed. Place the
appropriate card to the right of the card showing the preceding task. Identify any other tasks
that can be started simultaneously with task #2. Align these tasks either above or below task
#2 on the working surface.
Continue this process until all component tasks are sequenced. Identify task durations.
Using the knowledge of team members, reach a consensus on the most likely amount of time
each task will require for completion. Duration time is usually considered to be elapsed time
for the task, rather than actual number of hours/days spent doing the work. Document this
duration time on the appropriate task cards.
Construct the PERT chart
Number each task, draw connecting arrows, and add task characteristics such as
duration, anticipated start date, and anticipated end date. Determine the critical path. The
projects critical path includes those tasks that must be started or completed on time to avoid
delays to the total project. Critical paths are typically displayed in red.
PAGE | 20
Given below is the PERT chart of the Project

[Waterfall Model]
Start
: 10
Analysis
: 10
Designing
: 15
Coding
: 50
Testing
: 07
Report
: 04
End
: 96 Days
START
10
10
10
REQUIREMENT
10
20
ANALYSIS
10
10
20
85
92
35
50
85
20
15
35
TESTING
CODING
DESIGNING
85
92
35
85
92
96
96
96
REPORT
92
20
35
END
96
96
96
PAGE | 21
METHODOLOGY
ADOPTED
PAGE | 22
6.1 WATERFALL MODEL

The WATER FALL MODEL is a model which was developed for software
development; that is to create software. It is called as such because the model develops
systematically from one phase to other in a downward fashion, like a waterfall. The history of
waterfall model is somewhat disrupted. It is often said or believed that the model was first put
forth by Winston Royce in 1970.
The most probable phases through which it process downwards are
Requirement Analysis.
Design.
Implementation.
Verification.
Maintenance.
Here the linear ordering of these activities is critical. End of the phase and the output of one
phase is the input of other phase. The output of each phase is to be consistent with the overall
requirement of the system. Some of the qualities of spiral model are also incorporated like
after the people concerned with the project review completion of each of the phase the work
done.
PAGE | 23
WATER FALL MODEL was being chosen because all requirements were known
beforehand and the objective of our software development is the computerization/automation
of an already existing manual working system.
Requirement Analysis:
During this phase research is being conducted which includes brainstorming about the
software, what it is going to be and what purpose is it going to fulfill. Requirement analysis is
done in order to understand the problem. Here identifying what is needed for the system
solution and how the system will achieve its goal is analyzed. The main activity of this phase
is to document the requirements in the software requirement specification document.
PAGE | 24
Design:
The purpose of design phase is to figure out how to satisfy the requirements
enumerated in the System Requirements Specification document. The design phase produces
a presentation that will be used by the following phase, the development phase. This
representation should serve two purposes. First, from this representation, it should be possible
to verify that all the requirements are satisfied. Second, this representation should give
sufficient information for the development phase to proceed with the coding and
implementation of the system. Design is usually split into two levels: high-level design and
low-level design or a detailed design. The design steps produce the system design description
(SDD) document that will be used by development teams to produce the programs that realize
the design.
Implementation:
Upon getting the system design specifications document the actual coding would be
started. Before starting the actual coding requirements are divided into the models / units. In
actual coding initially develop the small programs called unit. After implementing all units
the integration would be started in the next phase. The developed units model functionality is
tested separately in this phase to check whether the unit models meet the specified
requirements.
Verification:
As the programs are coded, they are also tested. In addition, after the coding is
complete, the product is subjected to testing. Testing is the process of exercising the software
PAGE | 25
product in pre-defined ways to check of the behaviour is the same as expected behaviour. By
testing the product, an organization identifies and removes as many defects as possible before
shipping it out.
Once the software undergoes testing successfully, it has to be verified with different
values of inputs to get the excepted outcomes. Verification is the process of evaluating a
system or component to determine whether the products of the given phase satisfy the
conditions imposed at the start of that phase.
Maintenance:
Once the product is tested and verified, it is given to the customers who deploy it in
their environments. As the users start using the product in their environments, they may
observe discrepancies between the actual behaviour of the product and what they were given
to expect. Such discrepancies could end up as product defects, which need to be corrected.
The product now enters the maintenance phase, wherein the product is maintained or changed
to satisfy the changes that arise from customer expectations, environmental changes, etc.
Maintenance is made up of corrective maintenance, adaptive maintenance and perfective
maintenance.
Advantages of waterfall model:
This is linear simple model to implement and easy to maintain.
The project requires the fulfilment of one phase, before proceeding to the next.
Therefore if there is a fault in this software it will be detected during one of the initial phases
and will be sealed off for correction.
PAGE | 26
A lot of emphasis is laid on paperwork in this method as compared to the newer
methods.
The waterfall method is also well known amongst the software developers therefore it
is easy to use. It is easier to develop various software through this method in short span of
time.
Disadvantages of waterfall model:
The biggest disadvantage of such system is it wont to go back. If there is problem in
design phase, it creates a complication in the implementation phase.

1. The other negative aspect of this model is that a huge amount of time is also wasted.
2. Another disadvantage of this method is that the testing period comes quite late in the
development process; whereas in various other developmental programs the designs
would be tested a lot sooner to find the flaw at a time when a lot of time has been
wasted.
3.The waterfall model assumes that the requirements of a system can be baseline before
the design begins. This is possible for system designed to automate an existing manual
system. For our system, (Online Counseling System) this is a new system, determining
the requirement is difficult, as the user does not even know the requirements.
4.Freezing the requirements usually requires choosing the hardware.
5.The waterfall model stipulates that the requirements be completely specified before the
rest of the development can proceed.
PAGE | 27
SYSTEM
IMPLEMENTATION
AND DETAILS OF
HARDWARE &
SOFTWARE USED
PAGE | 28
7.1 System Implementation

Implementation uses the design document to produce code. Demonstration that the
program satisfies its specifications validates the code. Typically, sample runs of the program
demonstrating the behavior for expected data values and boundary values are required. Small
programs are written using the model: -
Write/Compile/ Test
It may take several iterations of the model to produce a working program. As

programs get more complicated, testing and debugging alone may not be enough to produce
reliable code. Instead, we have to write programs in a manner that will help insure that errors
are caught or avoided.
Top-Down Implementation: -
Top down implementation begins with the user-invoked module and works
toward the modules that do not call any other modules. The implementation may precede
depth-first or breadth-first.
Bottom-Up Implementation: -
Implementation begins with modules that do not call any other modules and
works toward the main program. Test harness (see below) is used to test individual modules.
The main module constitutes the final test harness.
PAGE | 29
Stub Programming: -
Stub programming is the implementation analogue of top-down and

stepwise refinement. It supports incremental program development by allowing for error and
improvement. A stub program is a stripped-down, skeleton version of a final program. It
doesn't implement details of the algorithm or fulfill all the job requirements. However, it does
contain rough versions of all subprograms and their parameter lists. Furthermore, it can be
compiled and run. Extensive use of procedures and parameter are the difference between stub
programs and prototypes. Quick and dirty prototypes should be improved--they should be
rewritten. A stub program helps demonstrates that a program's structure is plausible. Its
procedures and functions are unsophisticated versions of their final forms, but they allow
limited use of the entire program. In particular, it may work for a limited data set. Often the
high-level procedures are ready to call lower-level code, even if the more detailed
subprograms haven't even been written. Such sections of code are commented out. The
comment brackets can be moved, call-by-call, as the underlying procedures are actually
written.
Incremental Program Development: -
As program become more complex, changes have a tendency to introduce

unexpected effects. Incremental programming tries to isolate the effects of changes. We add
new features in preference to adding new functions, and add new function rather than writing
new programs. The program implementation model becomes:
------ Define types/compile/fix;
PAGE | 30
------ Add load and dump functions/compile/test;
------ Add first processing function/compile/test/fix;
------ Add features/compile/test/fix;
------ Add second processing function/compile/test/fix;
------ Keep adding features/and compiling/and testing/ and fixing.
7.2 HARDWARE REQUIREMENT:

Standard PC consisting of the following:
Min 1GB RAM
Min 1GB Hard disk
Minimum System Requirement

Operating system
Windows XP or Vista OS or later
Processor
Pentium 4 1.6GHz Intel Core 2 Duo
Memory
512MB
PAGE | 31
7.3 SOFTWARE REQUIREMENT

-
Windows 7, XP
Microsoft Visual Studio 2015:

Microsoft
Visual
Studio is
an integrated
development
environment (IDE)
from Microsoft. It is used to develop computer programs for Microsoft Windows, as well
as web sites, web applications and web services. Visual Studio uses Microsoft software
development platforms such as Windows API, Windows Forms, Windows Presentation
Foundation, Windows
Storeand Microsoft
Silverlight.
It
can
produce
both native
code and managed code.
SQL server 2012:

Microsoft SQL Server is a relational database management system developed
by Microsoft. As a database, it is a software product whose primary function is to store and

retrieve data as requested by other software applications, be it those on the same computer or
those running on another computer across a network (including the Internet). There are at
least a dozen different editions of Microsoft SQL Server aimed at different audiences and for
workloads ranging from small single-machine applications to large Internet-facing
applications with many concurrent users. Its primary query languages are T-SQL and ANSI
SQL.
PAGE | 32
SYSTEM
MAINTENANCE
&
EVALUATION
PAGE | 33
SYSTEM MAINTENANCE
The process of changing a system after it has been delivered and is in used is called
software maintenance. The changes may involve simple changes to correct coding errors,
more extensive changes to correct design errors of significant enhancement to correct
specification errors or accommodate new requirements. Maintenance therefore, means
evolution. It is the process of changing a system to maintain its ability to survive.
There are three different types of software maintenance:
1. Corrective maintenance:
It is concerned with fixing reported errors in the software. Coding errors are usually
relatively cheap to correct; design errors are more expensive as they may involve the
rewriting of several programs, components. Requirements errors are the most expensive to
repair because of the extensive system redesign which may be necessary.
2. Adoptive maintenance:
Means changing the software to some new environment such as a different hardware
platform or for use with a different operative system. The software functionality does not
radically changed.
3. Perfective Maintenance:
Involves implementing new functional or non-functional system requirements. These are
generated by software customers as they are organization or business changes.
PAGE | 34
In the project the following modules are maintained:
Result displaying
Working of graph
retrieving of images
Report generating
Message popup
The keys to reduce the need for maintenance are
1. More accurately defining the users requirement
2. Preparation of system documentation
3. Making use of existing tools and techniques of software development to Software engineer
in
charge of maintenance of the software.
4. Preparation of user guide or manual.
PAGE | 35
COST AND BENEFIT

ANALYSIS
PAGE | 36
COST ANALYSIS
The cost of a project is derived not only from the estimates of effort and size but
from other parameters such as hardware, travel expenses, telecommunication costs, etc,
should also be taken into account. Software cost estimation is the process of predicting the
amount of effort required to build a software system. Models provide one or more
mathematical algorithms that compute cost as a function of a number of variables. Size is a
primary cost factor in most models and can be measuring using lines of code or function
points. Models used to estimate cost can be categorized as either cost models or constraint
models.
COCOMO is an example of a cost model. Software cost estimation is the process
of predicting the amount of effort required to build a software system. Cost estimates are
needed throughout the software lifecycle. Preliminary estimates are required to determine the
feasibility of a project. Detailed estimates are needed to assist with project planning. The
actual effort for individual tasks is compared with estimated and planned values, enabling
project managers to reallocate resources when necessary. The article is intended for those who
are new to project cost estimation techniques, and those who would like to have a feedback on
COCOMO II model.
Our objective is to describe in a simple way basic cost estimation steps, tools and
assumptions, having a real project in mind, and supplying only necessary details on the
project itself. COCOMO (Constructive Cost Model) is a model that allows software project
managers to estimate project cost and duration.
PAGE | 37
The model is simple and well tested

Provides about 20% cost and 70% time estimate accuracy
In general, COCOMO estimates project cost, derived directly from person-months effort, by
assuming the cost is basically dependent on total physical size of all project files, expressed in
thousands single lines of code (KSLOC).
The estimation formulas have the form:

Effort (in person-months) = a x KSLOCb
Where
SLOC: Single lines of code
a : is a coefficient
b: Scaling factor
PAGE | 38
COST ESTIMATION OF THE PROJECT
Effort of person= a,
Working time = b,
Where a= 2 people=1700
b = 5 months
so, a*b
= 1700*2*5
= 17000
Total cost of project = 17000/-
PAGE | 39
DETAILED LIFE CYCLE

OF THE
PROJECT
PAGE | 40
10.1 ENTITY RELATIONSHIP DIAGRAM
Entity Relationship Model
U_ name
Category
Roll no
Rank
Student
U_ adds
U_ code
Name
University
Counseling
College
Selection
of college
Affiliation
C_ adds
C_ code
C_ name
PAGE | 41
10.2 DATA FLOW DIAGRAM

It is common practice to draw the context-level data flow diagram first, which shows
the interaction between the system and external agents which act as data sources and data
sinks. This helps to create an accurate drawing in the context diagram. The system's
interactions with the outside world are modeled purely in terms of data flows across
System Boundary. The context diagram shows the entire system as a single process, and
gives no clues as to its internal organization.
This context-level DFD is next "exploded", to produce a Level 1 DFD that shows some of the
detail of the system being modeled.
LEVEL 0: CONTEXT LEVEL
PAGE | 42
LEVEL 1 : TOP LEVEL

The Level 1 DFD shows how the system is divided into sub-systems (processes), each
of which deals with one or more of the data flows to or from an external agent, and which
together provide all of the functionality of the system as a whole. It also identifies internal
data stores that must be present in order for the system to do its job, and shows the flow of
data between the various parts of the system.
PAGE | 43
LEVEL 2: Detailed Level DFD

This diagram demonstrates the flow of data showing each single process in detail. If
level 1 DFD is bird eye view than detailed level DFD is microscopic view.
PAGE | 44
INPUT
AND
OUTPUT
SCREEN DESIGN
PAGE | 45
LOGIN FORM
Form 1:
It is the main form to Login/Register for councelling
PAGE | 46
ADMIN. HOME PAGE
Form 2:
Admin. Can view all result n can view overall performance of ranking related to their
specific course.
PAGE | 47
ALL STUDENTS DETAILS
Form 3:
Admin can view students details with their images n allocate the set for student.
PAGE | 48
MANAGE COLLEGE
Form 4:
Admin can add new college view college and delete college.
.
PAGE | 49
PROCESS
INVOLVED
PAGE | 50
Process Flowchart Diagram

Process Flowchart Diagram or PFD is also known as the system flow diagram or SFD.
The main reason of using process flowchart is to show the relation between major parts of the
system. Process Flowchart Diagram or PFD does not include minor parts or components of
the system like piping ratings or piping systems. In many organizations, users term process
flow diagrams as flowchart.
Process flowcharts
Process flowcharts are used primarily in process engineering and chemical industry
where there is a requirement of depicting the relationship between major components only.
These process engineering and chemical industry are least concerned about the minor
components involved in the system. Process flow diagrams for single unit or multiple units
differ in their structure and implementation. Process flow diagrams for multiple units do not
include detailed information and are known as the schematic flow diagrams or block flow
diagrams.
Process flow diagrams

Process flow diagrams should include the information regarding the connection
between various systems. It also consists of the process piping and details of major parts.
Process flow diagrams are usually drawn on a large sheet of paper. Nowadays with the advent
PAGE | 51
of computers and new technology, we tend to use computerized process flow diagrams. In old
computer era, we used to draw process flow diagrams with the help of supporting software
manually but now we have many process simulators that automatically create process
flow diagrams. We can also make use of the Computer Aided Design (CAD) technology or
flow chart software to enhance our process flow diagram skills.
Flowcharts are maps or graphical representations of a process. Steps in a process are shown
with symbolic shapes, and the flow of the process is indicated with arrows connecting the
symbols. Computer programmers popularized flowcharts in the 1960's, using them to map the
logic of programs. In quality improvement work, flowcharts are particularly useful for
displaying how a process currently functions or can ideally function. Flowcharts can help you
see whether the steps of a process are logical, uncover problems or miscommunications,
define the boundaries of a process, and develop a common base of knowledge about a process.
Flowcharting a process often brings to light redundancies, delays, dead ends, and indirect
paths that would otherwise remain unnoticed or ignored. But flowcharts don't work if they
aren't accurate, if team members are afraid to describe what actually happens, or if the team is
too far removed from the actual workings of the process.
PAGE | 52
METHODOLOGY
USED
FOR
TESTING
PAGE | 53
TESTING
Testing is a process, which reveals errors in program. It is the major quality measure
employed during software development. During testing, the program is executed with a set of
conditions known as test cases and output is evaluated to determine whether the program is
performing as expected.
The Primary and Larger objective of testing is to deliver quality software. Quality software is
one that is devoid of errors and meets with a customers stated requirements.
If errors are found, then the software must be debugged to locate these errors in the
various programs. Corrections are then made. The program/system must be tested once again
after corrections have been implemented - this time with an additional objective of finding out
whether or not corrections in one part of the system have introduced any new errors elsewhere
in the system.
Once all errors are found, then another objective must be accomplished that is check whether
or not the system is doing what it is supposed to do. So another aspect of testing is that it must
also ensure that the system meets with user requirements.
Techniques of testing
Black Box Testing
White Box Testing
Equivalence Portioning
Boundary Value Analysis
The following are the methods of testing carried out in the project:
PAGE | 54
1. Unit Testing:
The most testing is the `micro scale of testing. It is used to test particular functions or
code modules. it is typically done by a programmer and not by tester, as it requires detailed
knowledge of the internal program design and code. Not always easily done unless the
application has a well-designed architecture with tight code; may require developing test
driver modules. Individual components are tested to ensure that they operate correctly. Each
component is tested independently without other system components.
2. Black Box Testing:
Black box testing is called as functionality testing. By this we can test the functionality
of the application; this testing will conducted after the project is completed. This is a
technique that assumes no knowledge of the internal of software program. It focuses the
attention of a tester on providing a certain input and getting the desired output. If the desired
output is not getting then
An error is reported and the system should be able to return back to its earliest status.
For example while filling the query form, the user should be prompted with error if fields are
blank or invalid entry is made. Also the error messages that have been displayed should be
very clear and consistent. While this test is being conducted the tester is not expected to
determine how many lines of code were executed to archive, were all loops executed etc.
PAGE | 55
Testing strategies:
A testing strategy is general approach to the testing process rather than a method of devising
particular system or components tests. Different strategies a may be adopted depending on the
type of system to be tested and the development process used.
The testing strategies which discuss in this are:

Top-down testing:
Where testing starts with the most abstract component and works downwards.
Bottom-up testing:
Where testing starts with the fundamental components and works upwards.
Back-to-back testing:
Which is used when versions of systems are available the systems are tested together
and their outputs are compared.
Large systems are usually tested using a mixture of these testing strategies rather than
any approach. Different strategies may be needed for different parts of the system and at
different stages in the testing process.
Whatever testing strategy is adopted, it is always sensible to adopt an incremental
approach to sub-system and system testing.
PAGE | 56
CONCLUSION
It has been a great pleasure for me to work on this exciting and challenging project. This project proved
good for me as it provided practical knowledge of not only programming in ASP.NET and C#.Net web
based application and no some extent Windows Application and SQL Server, but also about all handling
procedure related with University Management system. It also provides knowledge about the latest
technology used in developing web enabled application and client server technology that will be great
demand in future. This will provide better opportunities and guidance in future in developing projects
independently.
BENEFITS:
The project is identified by the merits of the system offered to the user. The merits of this project
are as follows:
This project offers user to enter the data through simple and interactive forms. This is very helpful
for the client to enter the desired information through so much simplicity.
The user is mainly more concerned about the validity of the data, whatever he is entering. There are
checks on every stages of any new creation, data entry or updation so that the user cannot enter the
invalid data, which can create problems at later date.
User is provided the option of monitoring the records he entered earlier. He can see the desired
records with the variety of options provided by him.
Data storage and retrieval will become faster and easier to maintain because data is stored in a
systematic manner and in a single database.
Allocating of sample results becomes much faster because at a time the user can see the records of last
years.
Easier and faster data transfer through latest technology associated with the computer and
communication.
Through these features it will increase the efficiency, accuracy and transparency
LIMITATIONS:
The size of the database increases day-by-day, increasing the load on the database back up and data
maintenance activity.
Training for simple computer operations is necessary for the users working on the system.
FUTURE IMPROVEMENT
PAGE | 57
It can be implemented to upload files with an huge amount of size with the support of various file
formats.
This System being web-based and an undertaking of Cyber Security Division, needs to be thoroughly tested
to find out any security gaps.
A console for the data centre may be made available to allow the personnel to monitor on the sites which
were cleared for hosting during a particular period.
Moreover, it is just a beginning; further the system may be utilized in various other types of auditing
operation viz. Network auditing or similar process/workflow based applications...
PAGE | 58
USER
OR
OPERATIONAL
MANUAL
PAGE | 59
How to Login for the First Time?
Step 1: Open any browser (use Internet Explorer, Firefox for better view) and enter the
website name.
Step 2: Enter and login. Click Submit button
Step 3: Enter Application Number which is on the application form. And fill application
form details
Annexure
Abbreviations are as follows:
PERT- Program Evaluation and Review Technique
COCOMO- Constructive Cost Model
ER Diagram- Entity Relationship Diagram
DFD- Data Flow Diagram
List of Figures:
System design
PERT Chart
Waterfall Model
PAGE | 60
Entity Relationship Diagram

Data Flow Diagram
Graphical representation form
REFERENCES AND BIBILOGRAPHY

Roger S. Pressman (1997) Software Engineering, A Practitioners Approach Tata
McGraw-Hill Publishing Company Limited.
The Complete Reference Visual Basic .NET Jeffery R. Shapiro Tata McGraw Hills
Software Engineering by Ian Sommerville
WEBSITES:
http://www.w3schools.com/default.asp
http://getbootstrap.com/
http://www.asp.net/signalr
http://www.asp.net/web-pages/overview
PAGE | 61

Councelling System PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Councelling System PDF

Uploaded by

Copyright:

Available Formats

APPLICATION ON STUDENT COUNSELLING SYSTEM

Objective and Scope of the Project

Theoretical Background definition of problem Statement

System analysis and design

Use case model

System Planning (PERT Chart)

System Implementation & Details of Hardware & Software

System Maintenance and Evaluation

Cost and Benefit Analysis

RANI CHANNAMMA UNIVERSITY, BELGAUM

APPLICATION ON STUDENT COUNSELLING SYSTEM

Detailed Life Cycle of the Project

Data Flow Diagram

Input and Output Screen Designs

Methodologies Used for Testing

User or Operational Manual ,Annexure,References

RANI CHANNAMMA UNIVERSITY, BELGAUM

APPLICATION ON STUDENT COUNSELLING SYSTEM

RANI CHANNAMMA UNIVERSITY, BELGAUM

APPLICATION ON STUDENT COUNSELLING SYSTEM

RANI CHANNAMMA UNIVERSITY, BELGAUM

APPLICATION ON STUDENT COUNSELLING SYSTEM

INTRODUCTION OF THE PROJECT

(1) Institute Record.

(5) Reporting, Withdraw.

RANI CHANNAMMA UNIVERSITY, BELGAUM

APPLICATION ON STUDENT COUNSELLING SYSTEM

RANI CHANNAMMA UNIVERSITY, BELGAUM

APPLICATION ON STUDENT COUNSELLING SYSTEM

RANI CHANNAMMA UNIVERSITY, BELGAUM

APPLICATION ON STUDENT COUNSELLING SYSTEM

Scope of the Project

provide the on line facility for reporting /

Institute Code ,Name of the institute, Name of the

RANI CHANNAMMA UNIVERSITY, BELGAUM

APPLICATION ON STUDENT COUNSELLING SYSTEM

RANI CHANNAMMA UNIVERSITY, BELGAUM

APPLICATION ON STUDENT COUNSELLING SYSTEM

general seats in every institute the process

Roll no, Rank, Sex, Category, etc.

The System fully works as an online.

Centralized maintain all information.

It helps the university to dynamically add records to the database.

Easy to Searching the information about college or university.

Easy to managing whole counseling procedure

RANI CHANNAMMA UNIVERSITY, BELGAUM

APPLICATION ON STUDENT COUNSELLING SYSTEM

RANI CHANNAMMA UNIVERSITY, BELGAUM

APPLICATION ON STUDENT COUNSELLING SYSTEM

RANI CHANNAMMA UNIVERSITY, BELGAUM

APPLICATION ON STUDENT COUNSELLING SYSTEM

It is a time consuming process.

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

Further more, manual evaluation is prone to errors.

RANI CHANNAMMA UNIVERSITY, BELGAUM

APPLICATION ON STUDENT COUNSELLING SYSTEM

RANI CHANNAMMA UNIVERSITY, BELGAUM

APPLICATION ON STUDENT COUNSELLING SYSTEM

Identify the clients need.

Evaluate the system concept for feasibility.

Perform economical and technical analysis.