of 35
8/10/2019 Fee Management Project Report (1) (1)
1/35
1.INTRODUCTON
1.1 MOTIVATION:
The objective of this system is to makes the less paper work. And make the account
department more reliable.
Provide better services to students and account department.
Provide meaningful, consistent, and timely data and information to the management.
We can easily find out the record of the student.
1.2 Why FEES MANAGEMENT:
Today the technology is fast advancing and it becomes the duty of a professional to utilize it
properly and make it available to the masses. verything is computerized and online. !or that
purpose fast, powerful and smaller computers are developed for commercial and scientific
applications. "ots of paper work done by account office to maintain the fees record. When
students come to know their fees record one have to search in papers. Which was reduced by this
fees management.
1.4 Challenges in FEES MANAGEMENT:
An analyst is responsible for performing following tasks#
$athered all facts about the present system.
%tudied strength and weakness of the current system.
&etermined 'what( must be done to solve the problem.
Prepared a functional specifications document.
&esigning ad in flash for the front page
)
8/10/2019 Fee Management Project Report (1) (1)
2/35
*omputer is useful in lot of fields like educational and private sectors. +t needs different
softwares and application. %o this project is working in the field that is beneficial for the
college. We can perform various tasks like we can see all the information of the college
online, upload and download papers and application forms, view e-am and sessional results,
and discuss any problem online, future students can view the college details.
1. !RO"#EM STATEMENT
The various problem faced by them are#
"ot of manual work is to be done.
/anual working is more error prone.
asily find out the fees record of the students.
1.$ !RO"#EM OUT#INE
At the beginning we studied about the problems that are faced by the accountant, like fees
submission, find out records, and general info about students.
0e1uirement
At first we collected all the re1uirements from the college and account staff. Also talked to the
lectures concerned with it. We discussed about the problems and related topics to them.
Analysis
After collecting the data and information, we discussed about the real needs of !ees
/anagement. We analyzed the problem. And according to the needs we started framing of our
project.
Designing
After analyzing the needs we decided no of forms which we need and re1uired forms suitable for
our project. After this we started the designing of forms i.e. about their lookup or appearance.
And according to the forms re1uired we designed our database for storing the huge record.
C%&ing
According to the design of forms database tables we applied the re1uired logic to make the form
working. !irst we selected the logic and put s1l 1ueries in it. After this we implemented it into
the form.
23
8/10/2019 Fee Management Project Report (1) (1)
3/35
Tes'ing ( C%s' es'i)a'i%n
After coding phase i.e. applying the logic we tested each form whether there are working or not.
!irst we tested individually each form, then integrated each form and then tested further.
And according to the working hrs and labor re1uired we calculate the cost of the project. 4y
putting this in to cost estimation formula.
5.RE*UIREMENT ANA#+SIS AND RE#ATED WOR,
2.1 S+STEM ANA#+SIS
%ystem Analysis refers into the process of e-amining a situation with the intent of improving it
through better procedures and methods. %ystem design is the process of planning a new system
to either replace to or compliment an e-isting system. 4ut before any planning is done, the old
system must be thoroughly understood and the re1uirements determined. %ystem analysis is
therefore the process of gathering and interpreting facts, diagnosing problems and using the
information to recomment improvements in the system. +n other words system analysis means a
detailed e-planation or description.
2.2 IDENTIFICATION OF NEED
The first step of %ystem Analysis process involves the identification of need. The analyst meets
with the customer and end user 6if different from customer7. +dentification of need is the starting
point in the evolution of a *omputer based system. The analyst assists the customer in defining
the goals of the system viz#
What information will be produced8
What information is to be provided8
What functions and performance are re1uired8
9ow the basic 1uestion that arises in identification of need is 'Why this system8(
22
8/10/2019 Fee Management Project Report (1) (1)
4/35
With the advent of demanding applications and need of application we need a real time system,
which can help us view information about college online. !uture %tudent can view all info and
facility, and current student can view their results and records online and discuss their problems
with others.
2.4 -a&/ae An& S%0'/ae Reie)en's
O3ea'ing Sys'e): Windows :P with ++%.
The system will be built on windows compatible environment. The
application will be web based developed using .9T technology.
F%n'en /icrosoft ;isual studio 533>>>> F'2FAMLR) 'imese7 -oman"(n0s
5
8/10/2019 Fee Management Project Report (1) (1)
18/35
8/10/2019 Fee Management Project Report (1) (1)
19/35
8/10/2019 Fee Management Project Report (1) (1)
20/35
8/10/2019 Fee Management Project Report (1) (1)
21/35
8/10/2019 Fee Management Project Report (1) (1)
22/35
&eig&t) +:"(
8/10/2019 Fee Management Project Report (1) (1)
23/35
9J"-eortour$e*="Crstal-eortour$e+"Wi!t&="J>+"/( 9J"-eortour$e*="Crstal-eortour$e+"Wi!t&="J>+"/(
8/10/2019 Fee Management Project Report (1) (1)
24/35
KlConne$tion$on = ne7KlConne$tion;"server=.!ata0ase=eesui!=sa"
rote$te!voi!PageBLoa!;o0e$tsen!er8 EventArgse
X rote$te!voi!utton+BCli$1;o0e$tsen!er8 EventArgse $on.en; KlComman!$m!=ne7KlComman!;"insert into a!!re$or!values;?"Y'eto+.'etY"?8?"Y'eto4.'etY"?8?"Y'eto9.'etY"?8?"Y'eto.'etY"?8?"Y'eto:.'etY"?8?"Y*ro*o7nList+.ele$te!UalueY"?"8$on $m!.Ee$uteonZuer; $on.Close; 'eto+.'et = "" 'eto4.'et = "" 'eto9.'et = "" 'eto.'et = "" 'eto:.'et = ""
XX
Fee s
8/10/2019 Fee Management Project Report (1) (1)
25/35
KlComman!$m! = ne7KlComman!;"insert into eesu0mit values ;?"Y'eto+.'et Y "?8?"Y 'eto4.'et Y "?8?"Y 'eto9.'et Y "?8?"Y'eto.'et Y "?8?"Y 'eto:.'et Y "?8?"Y 'etoG.'et Y "?8?"Y'eto.'et Y "?"8 $n.$on $m!.Ee$uteonZuer;
'eto9.'et = "" 'eto.'et = "" 'eto:.'et = "" 'etoG.'et = "" 'eto.'et = ""
X rote$te!voi!'etoGB'etC&ange!;o0e$tsen!er8 EventArgse inta int0 = Convert.'ont94;'eto:.'et.'otring;
int$ = Convert.'ont94;'etoG.'et.'otring; a = 0 2 $ 'eto.'et = a.'otring; X rote$te!voi!'eto9B'etC&ange!;o0e$tsen!er8 EventArgse $n.$on.en; KlComman!$m! = ne7KlComman!;"sele$t sname8sees rom a!!re$or!7&ere rollno=?"Y'eto9.'et Y "?"8 $n.$on Kl*ata-ea!er!r = $m!.Ee$ute-ea!er;
i;!r.-ea!; 'eto.'et = !r[>\.'otring; 'eto:.'et = !r[+\.'otring;
!r.Close; $n.$on.Close; X XX
BB
8/10/2019 Fee Management Project Report (1) (1)
26/35
4.9 MODU#ES WIT- SNA!S-OTS
-%)e !age:
A
8/10/2019 Fee Management Project Report (1) (1)
27/35
GUI TESTING
In'e0a5e 'es'ing.*ontrols 6te-tbo-, combo bo-, icon7, menu, hyperlinks will be tested to check
whether they works properly and visible properly or not and they are working properly or not.
Page design will be tested for validation. ;alidation of each input object 6like te-tbo-, combo
bo-7 will be tested as mentioned in specification like mandatory input control should not be
empty before submitting the form etc.
Se5i'y 'es'ing. Attempted access without a proper password to the system to see information
will be tested.
Usa
8/10/2019 Fee Management Project Report (1) (1)
28/35
&ata present in database 6data should not be added to database7
mpty filed 6null values7 for mandatory field 6that should accepted7
To test email address 6abcdNjgjg.comformat should be used7
*orrect format 6should be accepted7
+ncorrect format 6without N, without '.(, use '.( 4efore 'N( etc7 6should not be accepted
.9TEST CASES
Uni' Tes'ing
1. #OGIN MODU#E
G%al:Able to verify whether the member is authorized or not.
Tes'e& Fn5'i%nali'y2. Able to establish connection with database.
5. Able to verify member authorization.
Tes' Resl's
2. *onnection stablished
5. !ailed to check the member details in thedatabase
!%
8/10/2019 Fee Management Project Report (1) (1)
29/35
Tes' Resl's2. stablish connection5. %tores %tudent details in the database
/odule worked correctly in first attempt.
9. Dis5ssi%n 0%) )%&le
G%al:Able to Add items to the cart.
Tes'e& Fn5'i%nali'y2. stablish database connection.
5. %how the previous added threads
Tes' Resl's
2. *onnection stablished
5. rror while retrieving values fromdatabase
!%
8/10/2019 Fee Management Project Report (1) (1)
30/35
Tes' Resl's
2. Application is accessible anywhere.
5. /odules functionality could efficiently
communicate with each other after integration.
. !ERFORMANCE TESTING
ENTIRE S+STEM
G%als:
1. Able to perform well when more than two clients accessing the database simultaneously.
2. Availability of application when more than two clients accessing the application
simultaneously.
9. %peed of response from the server.
Tes'e& C%n&i'i%ns
2. &atabase Performance.
5. Availability of application.B. 0esponse to user re1uests.
!%
8/10/2019 Fee Management Project Report (1) (1)
31/35
*an anybody access the protected
area of the website
9o, without logging in
user cannot access the
protected area of the site.
Test Pass
69o Action7
Attempted access without a proper
password to the system to see
information will be tested.
Attempts succeeded8
9o, the attempt will not be
succeeded, and the user
will remain on the first
page only.
Test Pass
69o Action7
.4 Tes'ing S))ay
%oftware testing re1uires ma-imum and sufficient amount of time in the whole development
process. +ts objective is to identify and resolve all the errors found, and to check whether the
system developed is according to the user re1uirements or not. To fulfill this objective, unit
testing, integration testing, usability testing, $D+ testing, security testing, and were planned and
e-ecuted.
ach step is accomplished through a series of systematic test techni1ues that assist in the design
of test cases. With each testing step, the level of abstraction with which site is considered is
broadened.
*ollege Website was tested through the planned steps of testing at various stages and errors
were identified and resolved to a greater e-tent. %ystem failure or success is dependent on the
testing to a greater e-tent as regressive and successive testing uncovers all the errors and
ensures that the functionality of the system is according to the re1uirements with certain
other parameters like system performance, user interface etc.
. C%s' EBala'i%ns
B)
8/10/2019 Fee Management Project Report (1) (1)
32/35
In'%&5'i%n '% 'he COCOMO M%&el
This is a simple online cost model for estimating the number of personmonths re1uired to
develop software. The model also estimates the development schedule in months and produces
an effort and schedule distribution by major phases. This model is based on 4arry 4oehmJs
*onstructive *ost /odel 6*?*?/?7. This is the toplevel model, 4asic *?*?/?, which is
applicable to the large majority of software projects.
Cere is what 4oehm says about the model# O4asic *?*?/? is good for rough order of
magnitude estimates of software costs, but its accuracy is necessarily limited because of its lack
of factors to account for differences in hardware constraints, personnel 1uality and e-perience,
use of modern tools and techni1ues, and other project attributes known to have a significant
influence on costs.O !or more detailed information about *?*?/? and software cost estimating
in general, + s'%ngly recommend reading Software Engineering Economics 62)K27, by 4arry
4oehm.
The *?*?/? ++ model makes its estimates of re1uired effort 6measured in Person/onths
P/7 based primarily on your estimate of the software projectJs size 6as measured in thousands of
%"?*, Q%"?*77#
ffort R 5.)@ S A! S 6Q%"?*7
Where
A! +s the ffort Adjustment !actor derived from the *ost &rivers
+s an e-ponent derived from the five %cale &rivers
As an e-ample, a project with all 9ominal *ost &rivers and %cale &rivers would have an A! of
2.33 and e-ponent, , of 2.3))G. Assuming that the project is projected to consist of K,333 source
lines of code, *?*?/? ++ estimates that 5K.) Person/onths of effort is re1uired to complete
it#ffort R 5.)@ S 62.37 S 6K72.3))GR 5K.) Person/onths
@3
http://sunset.usc.edu/Research_Group/barry.htmlhttp://sunset.usc.edu/Research_Group/barry.htmlhttp://sunset.usc.edu/Research_Group/barry.htmlhttp://sunset.usc.edu/Research_Group/barry.htmlhttp://sunset.usc.edu/Research_Group/barry.htmlhttp://sunset.usc.edu/Research_Group/barry.htmlhttp://sunset.usc.edu/Research_Group/barry.htmlhttp://sunset.usc.edu/Research_Group/barry.htmlhttp://sunset.usc.edu/Research_Group/barry.htmlhttp://sunset.usc.edu/Research_Group/barry.htmlhttp://sunset.usc.edu/Research_Group/barry.html8/10/2019 Fee Management Project Report (1) (1)
33/35
8/10/2019 Fee Management Project Report (1) (1)
34/35
$. C%n5lsi%n:
This establishes the basic re1uirements of the programmer. 9ow, the programmer and users have
a full knowledge of the methods, classes and the methods to be used in the code. All the objects
are well defined and the structure is crystal clear to the programmer. The project has been able to
achieve most of its objectives and features within the estimated schedules and 1uality features.
We have to say that for sure that the project was really tough to put our skills to the worst
possible test and it gives us immense satisfaction that we have come through successful. +t helps
us to develop a system, which is helpful in saving the time of a user. The users e-pect an
interface that would be user friendly and customizable so we have to keep in mind these factors
too. All together the *ollege website fulfilled the project specification re1uirements.
+n effect, this project had helped in providing the programmers
with a tool to reduce their programming time substantially and to minimize their programming
efforts.
@5
8/10/2019 Fee Management Project Report (1) (1)
35/35
. "i