Report Content for any project

8/18/2019 Report Content for any project

1/33

A Training Report

Submitted to the Faculty of Computer Application, Pacific University,

In partial fulfillment of the requirement for the degree of

MASTER OF COMPUTER APPLICATION

Submitted by:

MOHAN LAL PATEL

Internal Guide Training In-charge

< Name of Guide > Mr !e"e#$ !a#$ora

Asst. Professor %Soft&are Engineer'Address: !"-#$ Sha%ti Nagar$ &dai'ur

(()). India. Tel No.:*+-+,"+)!!)

/-mail: de0softcreations1gmail.comcontact1de0softcreations.com

FACULT( OF COMPUTER APPLICATIONPACIFIC UNI)ERSIT(* U!AIPUR

23A 4 ")(

5ogo6f

3om'any


2/33

3ertificate

This is to certify that the 'ro7ect re'ort entitled as 8 title of 'ro7ect9 submitted

to aculty of 3om'uter A''lication$ Pacific &ni0ersity$ &dai'ur for 'artial fulfillment

of the re;uirement for the degree of Ma#ter of Co+p,ter Application is an original

or% carried out by Mo$an Lal Patel under my obser0ation.

The matter embodied in this 'ro7ect re'ort is a genuine or% done by the

student and has no been submitted hether to this college or any other &ni0ersity=

Institute for the fulfillment of re;uirement of any course of study.

Signature of Guide


3/33


4/33

Table Of Contents

. Introduction?????????????????????

.. 60er0ie???????????????????.

.". Sco'e????????????????????...

.( @efinition$ Acronyms and abbre0iations???????

. Technology??????????????????..

". Be;uirements Analysis=Identify the needs.....

".. Be;uirement s'ecification...???????.???.....

".". Cardare and S= Be;uirements?????????..

(. easibility Study????..?????????..?????

(. 3ost estimation?????????????????

(." easibility re'ort????????????????..

. System Analysis...?????????????..?????.

!. @esign Analysis ???????????????.???...

. /-B @iagram??????????????????..??.

. @ata lo @iagram = &se 3ase????????????.?

,. @atabase @esign D Belationshi'???????????.?..

+. Screen shots = Interface @esign?????????????..

). Testing 2ethods???????????????????.

. 3onclusion?????????????????????.

". Beferences = #ibliogra'hy ????????????..?......s

Intro0,ction12


5/33

33 O"er"ie&

The main ob7ecti0e of the document is to illustrate the re;uirements of

the Pro7ect 8Title of project9. The @ocument gi0es the detailed descri'tion of the

both functional and non-functional re;uirements 'ro'osed by the user. The document

is de0elo'ed after number of consultations and considering the com'lete re;uirement

s'ecification of the gi0en 'ro7ect. This document is ser0ing as a guide to the

de0elo'ers$ testers$ designers on one hand and a softare 0alidation document for the

'ros'ecti0e client on the other. The final 'roduct of the team ill be meeting the

re;uirements of this document.

34 Scope

e describe here the features that are in the sco'e of current a''lication.

A Searc$ing: searching the details of the @onor and acce'tor in the database

and retrie0e them in single clic%.

5 Role 5a#e0 A,t$entication: The system allos the user to 7ust enter the login

name and 'assord D then the system ill dynamically chec% for the role D

'ro0ide access accordingly.

C A0+in Acco,nt Manage+ent: 3reate=@elete users in the system.

36 !efinition* Acron7+# an0 a88re"iation#

U#er1 user could be a student or a tutor at different conditions.

A0+in1 admin or administer is the 'erson res'onsible for maintaining ebsite.

HTTP 1 Cy'erteEt Transfer Protocol is a transaction oriented client=ser0er 'rotocol

beteen a eb broser D a eb Ser0er.

HTTPS1 Secure Cy'erteEt Transfer Protocol is a CTTP o0er SS5 Fsecure soc%et

layer.

TCP9IP1 Transmission 3ontrol Protocol=Internet Protocol$ the suite of communication

'rotocols used to connect hosts on the Internet. T3P=IP uses se0eral 'rotocols$ the to

main ones being T3P and IP.


6/33

. Tec$nologie#

A#pNet1 As'.Net su''orts strongly ty'ed languages li%e H#.N/T$ 3 and much

more.As'.Net 'ages get com'iled instead of being inter'reted thus their eEecutions'eed id faster than ASP Page. As'.Net im'ro0es 'erformance by using ser0er side

caching.

ASP.N/T is a set of eb de0elo'ment tools offered by 2icrosoft. Programs li%e

Hisual Studio .N/T and Hisual eb @e0elo'er allo eb de0elo'ers to create

dynamic ebsites using a 0isual interface. 6f course$ 'rogrammers can rite their

on code and scri'ts and incor'orate it into ASP.N/T ebsites as ell. Though it

often seen as a successor to 2icrosoftJs ASP 'rogramming technology$ ASP.N/T also

su''orts Hisual #asic.N/T$ KScri't .N/T and o'en-source languages li%e Python and

Perl.

ASP.N/T is built on the .N/T frameor%$ hich 'ro0ides an a''lication 'rogram

interface FAPI for softare 'rogrammers. The .N/T de0elo'ment tools can be used

to create a''lications for both the indos o'erating system and the eb. Programs

li%e Hisual Studio .N/T 'ro0ide a 0isual interface for de0elo'ers to create theira''lications$ hich ma%es .N/T a reasonable choice for designing eb-based

interfaces as ell.

S:l2Ser"er 4;;1 S;l Ser0er is used to ;uery the database and get results of the ;uery

from the database. #esides constructing ;ueries to 0ie data e can also insert ne

data and u'date eEiting data.

A relational @#2S from 2icrosoft that is a ma7or com'onent of the indos Ser0er

System. It is 2icrosoftJs high-end client=ser0er database and is closely integrated ith

2icrosoft Hisual Studio and the 2icrosoft 6ffice System. Numerous editions are

a0ailable$ including those for /nter'rise$ @e0elo'er$ or%grou' and -bit 'latforms.

4 Re:,ire+ent Anal7#i# 9 I0entif7 t$e nee0#12

http://www.techterms.com/definition/scripthttp://www.techterms.com/definition/asphttp://www.techterms.com/definition/apihttp://www.techterms.com/definition/scripthttp://www.techterms.com/definition/asphttp://www.techterms.com/definition/api


7/33

43 Soft&are Re:,ire+ent# #pecification

System re;uirements are eE'ressed in a softare re;uirement document. The

Softare re;uirement s'ecification FSBS is the official statement of hat is re;uired

of the system de0elo'ers. This re;uirement document includes the re;uirements

definition and the re;uirement s'ecification. The softare re;uirement document is

not a design document. It should set out hat the system should do ithout s'ecifying

ho it should be done. The re;uirement set out in this document is com'lete and

consistent.

The softare re;uirement s'ecification is 'roduced at the culmination of the

analysis tas%. The function and 'erformance allocated to softare as 'art of

system engineering are refined by establishing a com'lete information

descri'tion$ a detailed functional descri'tion$ a re'resentation of system

beha0ior$ an indication of 'erformance re;uirement and design constraints

a''ro'riate 0alidation criteria$ and other information 'ertinent to re;uirement.

The introduction to softare re;uirements s'ecification states the goals and

ob7ecti0es of the softare$ describing it in the conteEt of the com'uter based

system.

The Information @escri'tion 'ro0ides a detailed descri'tion of the 'roblem

that the softare must sol0e. Information content$ flo and structure are

documented.

A descri'tion of each function re;uired to sol0e the 'roblem is 'resented in

the unctional @escri'tion.

Halidation 3riteria is 'robably the most im'ortant and ironically the most

often neglected section of the softare re;uirement s'ecification.

Softare re;uirement s'ecification can be used for different 'ur'ose. Cere are

the ma7or uses.

Not clearly understood by the de0elo'er. If this is the case$ a careful analysis 4

in0ol0ing much interaction ith the user should be de0oted to reaching a clear

statement of re;uirements$ in order to a0oid 'ossible misunderstandings.


8/33

Sometimes$ at the beginning of a 'ro7ect$ e0en the user has no clear idea of

hat eEactly the desired 'roduct is. Thin% for instance of user interface $ a user

ith no 're0ious eE'erience ith com'uter 'roducts may not a''reciate the

difference beteen $ say menu dri0en interaction and a command line

interface. /0en an eEact formation of system functions and 'erformance may

be missing an initial descri'tion 'roduced by an ineE'erienced user.

It s'ecifies the eEternal system beha0iors.

" It s'ecifies constraints on the im'lementation.

( It is easy to change.

It ser0es as reference tool for system maintainers.

! It record forethought about the life cycle of the system. It characteriLes acce'table res'onse to undesired e0ents.

44 F,nctional Re:,ire+ent#1

• The System must 'ro0ide folloing functionalitiesM

• ee'ing records of admission of customers.

• %ee'ing the records of 'roducts.

• %ee'ing the daily sell .

• Storing the feedbac% gi0en by the customer.

• %ee'ing details about the 'roduct it is deli0ered

or not.etc.

• Storing the items selected by the customer in the tem'orary storage.

46 Perfor+ance Re:,ire+ent#1

In order to maintain an acce'table s'eed at maEimum number of u'loads alloed

from a 'articular customer ill be any number of users can access the system at any

time. Also connections to the ser0ers ill be based on the criteria of attributes of the

user li%e his location$ and ser0er ill be or%ing hole "O times.

4= Non F,nctional Re:,ire+ent#1


9/33

olloing Non-functional re;uirements ill be there in the Insurance on internet:

i. Secure access of confidential data Fcustomers details.

ii. " O a0ailability.

iii. #etter com'onent design to get better 'erformance at 'ea% time.

i0. leEible ser0ice based architecture ill be highly desirable for future eEtension

Non functional re;uirements define system 'ro'erties and constraints It arise through

user needs$ because of budget constraints or organiLational 'olicies$ or due to the

eEternal factors such as safety regulations$ 'ri0acy registration and so on.

Harious other Non-functional re;uirements are:

. Security

". Beliability

(. 2aintainability

. Portability

!. /Etensibility

. Beusability

. A''lication Affinity=3om'atibility

,. Besource &tiliLation

4 E?ternal Interface Re:,ire+ent#1

43 U#er Interface1

&ser of the system ill be 'ro0ided ith the Gra'hical user interface$ there is no

command line interface for any functions of the 'roduct. The user ill get " 'ages

. 5ogin 'age folloed by Passord

44 Har0&are @ Soft&are Re:,ire+ent12

Soft&are Re:,ire+ent#

Client on Intranet1 3lient Softare$ eb #roser

.e8 Ser"er1 6'erating System Fany

!ata 5a#e Ser"er1 S;l Ser0er ")),

Micro#o f t )i#,a l S t,0 i o 4;3; F .N et f ra me o r% .)

ASP.N/T i th 3

46 Har0&are Re:,ire+ent#3 Processor : Intel Pentium


10/33

4 Processor S'eed : ".) GCL

6 BA2 SiLe : "! 2#

= Card @is% : G#

2onitor : !9 color SHGA 2onitor

3ache 2emory : "! # #urst 3ache

B 3@-B62 : !"O 3@ B62 @ri0e

eyboard : 2icrosoft

2ouse : 2icrosoft Fo'tical mouse

4= Co++,nication Interface#

The to 'arties should be connected through either by 5AN or AN for the

communication.

Fig3

4 /eneral Con#traint#* A##,+ption#* !epen0encie#* /,i0eline#1

=3 /eneral Con#traint#

The interface ill be in /nglish only.

The system is or%ing for single ser0er.

Sender

Becei0er

There is no maintainability or bac%u' so a0ailability ill get affected.

The system is a single user system.

G&I features a0ailable.


11/33

=4 A##,+ption# an0 !epen0encie#

The 'roduct does re;uire bac%-end database ser0er SQ5 for storing the username and

'assord for different ty'es of user of the system as ell as 0arious databases

regarding 0arious insurance information.

A##,+ption#1

&ser must be trained for basic com'uter functionalities.

&ser must ha0e the basic %noledge of /nglish

The system must be able to res'ond to database softare ithin reasonable time.

Front2en0 %,#er interaction'1

• The 'roduct ill re;uire a com'uter ith an a''lication 'rogram or ith any

other a''lication 'rogram and an communication channel.

• The s'eed of the communication channel Fif any must be$ at a minimum ",.,

%b's in order to su''ort message transfer in reasonable time.

Pro0,ct F,nction#

A0+in1 F,nction#

3 Admin can 0ie all the users$ 0ideos$ tas%s and to acce't or re7ect them.

4 Admin can delete any record or its feedbac% if it stands against ebsite rules.

6 Admin is res'onsible for data a0ailability.

3 Fea#i8ilit7 St,0ie#12


12/33

easibility study is done so that an ill-concei0ed system is recogniLed early in

definition 'hase. @uring system engineering$ hoe0er$ e concentrate our

attention on four 'rimary areas of interest. This 'hase is really im'ortant as before

starting ith the real or% of building the system it as 0ery im'ortant to find out

hether the idea thought is 'ossible or not.

/conomic easibility: An e0aluation of de0elo'ment cost eighted against the

ultimate income or benefit deri0ed from the de0elo'ed system.

Technical easibility: A study of function$ 'erformance and constraints that

may affect the ability to achie0e an acce'table system.

6'erational easibility: A study about the o'erational as'ects of the system.

63 TECHNICAL ANAL(SIS

@uring technical analysis$ the technical merits of the system are studied and at the

same time collecting additional information about 'erformance$ reliability$

maintainability and 'redictability.

Technical analysis begins ith an assessment of the technical 0iability of the

'ro'osed system.

hat technologies are re;uired to accom'lished system function and

'erformanceR

hat ne materials$ methods$ algorithms or 'rocesses are re;uired and hat

is their de0elo'ment ris%R

As the softare is 0ery much economically feasible$ then it is really im'ortant for

it to be technically sound. The softare ill be built among:

2S SQ5 S/BH/B as #ac% /nd

ASP.N/T as ront /nd

64 Financial Fea#i8ilit71

• Is the 'ro7ect 'ossible$ gi0en resource constraintsR

• Are the benefits that ill accrue from the ne system orth the costsR

• hat are the sa0ings that ill result from the system$ including tangible and

intangible onesR

• hat are the de0elo'ment and o'erational costsR

66 OPERATIONAL FEASI5ILIT(

The 'ro7ect is o'erationally feasible. This 'ro7ect is being made for thecon0enience of the 'atients and doctors only. This system ill greatly reduce a


13/33

huge burden of doctors. So because of the abo0e stated ad0antages the users of the

system ill not be reluctant at all.

= S7#te+ Anal7#i# an0 !e#ign 12 This system is all about the con0erting the sho''ing

System from manual to online.

3ustomer can buy 'roducts online after login to the site.

Administrator is adding 'roduct to database.

Administrator can edit or delete the 'roducts from the database.

3ustomer can rite feedbac% for the 'roduct or ser0ices.

Admin can see daily sell and feedbac% gi0en by customer.

Administrator is adding the deli0ery re'ort to the database.

#oth admin and customer can see the deli0ery re'ort.

Acti"it7 !iagra+

5ogin Acti0ity @iagram

!e#ign Anal7#i#12 !ata Flo& !iagra+ 9 U#e Ca#e12

A @ata lo @iagram F@@ is a diagram that describes the flo of data and the

'rocesses that change or transform data throughout a system. Its a structured analysis


14/33

and design tool that can be used for flocharting in 'lace of$ or in association ith$

information oriented and 'rocess oriented system flocharts. hen analysts 're'are

the @ata lo @iagram$ they s'ecify the user needs at a le0el of detail that 0irtually

determines the information flo into and out of the system and the re;uired data

resources. This netor% is constructed by using a set of symbols that do not im'ly a

'hysical im'lementation. The @ata lo @iagram re0ies the current 'hysical

system$ 're'ares in'ut and out'ut s'ecification$ s'ecifies the im'lementation 'lan etc.

our basic symbols are used to construct data flo diagrams. They are symbols that

re'resent data source$ data flos$ and data transformations and data storage. The

'oints at hich data are transformed are re'resented by enclosed figures$ usually

circles$ hich are called nodes.

!ata Flo& !iagra+ S7+8ol#12

Source or @estination of data

@ata lo

Process

Storage

Step# to Con#tr,ct !ata Flo& !iagra+#

our ste's are commonly used to construct a @@

Process should be named and numbered for easy reference. /ach name should be

re'resentati0e of the 'rocess.

The direction of flo is from to' to bottom and from left to right.

hen a 'rocess is eE'loded into loer le0el details they are numbered.

The names of data stores$ sources and destinations are ritten in ca'ital letters.


15/33

R,le# for con#tr,cting a !ata Flo& !iagra+

Arros should not cross each other.

S;uares$ 3ircles and files must bear names.

@ecom'osed data flo s;uares and circles can ha0e same names.

3hoose meaningful names for dataflo.

@ra all data flos around the outside of the diagram.

U#e Ca#e !iagra+


16/33

,#e ca#e i0 1

U#e ca#e na+e 1 5ogin

Principal actor 1 Admin

Pre2con0ition 1 Admin is registered in system

S,cce## en0 con0ition 1 Admin successfully logged inS,cce## faile0 con0ition 1 Admin in not logged in

Trigger e"ent 1 Admin selects login o'tion.

Scenario 31 Admin enters his login id D 'assord and system chec%s

if it eEists in database. And redirect to home 'age.

!ata Flo& !iagra+

@ata lo @iagram is ay of eE'ressing flo of the system in a gra'hical form$

hich leads to a modular design. This is also %non as bubble chart or business

'rocess diagram. It has the 'ur'ose of clarifying system re;uirements and identifying

ma7or transformation.

The @ata lo @iagram shos the flo of data or information. It can be 'artitioned

into single 'rocesses or functions. @ata lo @iagrams can be grou'ed together or

decom'osed into multi'le 'rocesses.

CA!%CONTEDT ANAL(SIS !IA/RAM'

ero Le"el !F!

Fig 12 ero le"el !F!

3 le"el !F! for college #7#te+ in #t,0ent recor0#12


17/33

ig. le0el @@

le0el @@ for student record dis'lay and 'rocess is continuing neEt student

record:-


18/33

ig :- le0el @@

E2R !iagra+12


19/33


20/33

!ata8a#e !e#ign @ Relation#$ip12


21/33

A database design is a collection of stored data organiLed in such a ay that the data

re;uirements are satisfied by the database. The general ob7ecti0e is to ma%e

information access easy$ ;uic%$ ineE'ensi0e and fleEible for the user. There are also

some s'ecific ob7ecti0es li%e controlled redundancy from failure$ 'ri0acy$ security and

'erformance.

A collection of relati0e records ma%e u' a table. To design and store data to the

needed forms database tables are 're'ared. To essential settings for a database are:

• Primary %ey: - The field that is uni;ue for all the record occurrences.

• oreign %ey: - The field used to set relation beteen tables. NormaliLation is a

techni;ue to a0oid redundancy in the tables.

!ATA 5ASE TA5LE !ESI/N1

3 Login ta8le


22/33


23/33

St,0ent Secon0 7ear E?a+ ta8le

St,0ent T$ir0 7ear E?a+ ta8le


24/33

B St,0ent Fo,rt$ 7ear E?a+ recor0 ta8le

St,0ent Fir#t 7ear Atten0ance recor0 ta8le


25/33

St,0ent Secon0 7ear Atten0ance recor0 ta8le

3; St,0ent T$ir0 7ear Atten0ance recor0 ta8le

33 St,0ent Fo,rt$ 7ear Atten0ance recor0 ta8le12


26/33

34 Ne& 5oo infor+ation Recor0 in#ert li8rar7 ta8le12

36 La8 infor+ation ta8le12


27/33

3= 5oo i##,e infor+ation recor0 #a"e ta8le12


28/33

Screen #$ot# 9 Interface !e#ign12

Te#ting Met$o0#12


29/33

Testing 60er0ie

The aim of testing 'rocess is to identify all defects in a softare 'roduct. Testing is

any acti0ity aimed at e0aluating the softare for ;uality results it 'roduces and the

;uality of results it can handle. Testing a 'rogram consists of sub7ecting the 'rogramto attest cases and obser0ing if the 'rogram beha0es as eE'ected .If the 'rogram fails

to beha0e as eE'ected $then the condition under $hich failures occurs are noted for

later debugging and correction .There are many stages of testing de'ending on the

com'leEity of the softare.

Le"el# of Te#ting

The basic le0el s of testing are :

. &nit Testing

". Integration Testing

(. System Testing

. Acce'tance Testing

The le0els of Testing attem't to detect different ty'es of faults. The relation of faults

introduces in different 'hases and the different le0els of testing are shon:

&ser Needs Acce'tance Testing

Be;uirement System Testing

@esign Integration Testing

3ode &nit Testing

Unit Te#ting


30/33

&nit testing has been under ta%en hen a module has been coded and

successfully re0ieed. &nit testing is the testing of different units or modules of

system in isolation .Is 'rogrammers res'onsibility to thin% of the ad0antage of doing

unit testing before integration testing is that it ma%es debugging easier .If an error is

detected hen a module is being tested along ith se0eral modules$ it ould be

difficult to determine hich module eEactly has an error.

In the current system 5ac% city Cealth center$ unit testing has been eEclusi0ely done

after finishing e0ery module.

Integration te#ting

6nce a 'rogram or module has been unit tested the module interface in order

to ensure that there are no errors in the 'arameter 'assing$ hen one module in0ol0es

other modules. @uring integration testing$ different-different modules of the system

are integrated in a 'lanned manner i.e. the order in hich they are combined to realiLe

the full system.

The 0arious a''roaches of integration testing are:

. #ig #ang A''roach

". To'-@on a''roach

(. #ottom-&' A''roach

. 2iEed A''roach

6ne of the abo0e four a''roaches 2iEed A''roach has been used for the 'ro'osed

system. A miEed a''roach integration testing follos a combination of to' don and

bottom u' testing a''roach. In the to'-don a''roach$ testing can start only after the

bottom le0el module is ready. The miEed testing can start as a hen modules become

a0ailable.

or the 'ro'osed e ha0e also eEtensi0ely used regression testing. Begression testing

is the 'ractice of running an old test suite after change to the system or after each bug

fiE ensure no ne bug has been introduced as a result of the change made or bug

fiEed.

S7#te+ Te#ting


31/33

System testing is actually a series of different test hose 'rimary 'ur'ose is to

eEercise the com'uter based system$ all or% to 0erify that system elements ha0e

been 'ro'erly integrated and 'erformed allocated function.

Its focus is to 'ro0e that the com'leted system does hat it should. This test is

conducted in a formal manner. The testers use scenario-based system test scri'ts that

ha0e 'redicted out'uts. The test results are recorded in structured test logs .The

structured test logs and scri'ts dri0e the system testing 'rocess.

System testing acti0ities are intended to 'ro0e that the system meets its ob7ecti0es.

Testing 'ro0es that the system meets its re;uirements. This is not entirely true unless

one considers acce'tance testing because the 'ur'ose of acce'tance testing is to

demonstrate that the system meets the user re;uirement .Acce'tance testing is

0alidation 'rocess. System testing in the strictest testing re'resents an eEternal 0ie

of the system.

This is true because re;uirements re'resents the e0entual system i.e. user of the

system Fan eEternal 0ie.&se does not understand nor do they care about ho the

system or%s as long as it is usable. System testing should be a''roached from this

'ers'ecti0e.

A far as the 'ro'osed 85ac% city Cealth 3enter softare9 is considered it meets these

re;uirements.

U#er Acceptance Te#ting

Perfor+ance te#ting

Some of the 'erformance testing done for the 'ro'osed system is:-

. Stress Testing:-Stress testing is done to e0aluate system 'erformance hen it is

stressed for short 'eriods of time .Pro0iding a range of abnormal and e0en illegal

in'ut condition so as to stress the ca'ability of the softare. In'ut data 0olume$ in'ut

data rate$ 'rocessing time$ utiliLation of memory etc are tested beyond the designed

ca'acity.

". Holume Testing:-This testing is done to chec% hether the data structures ha0e been

designs successfully for eEtraordinary situation.

Peer Be0ie


32/33

A al%through a''roach ith friends and scenarios as a''lied for testing.

Suggestions related to 'resentation and re'ort generation ere incor'orated.

Test Plan and Test 3ases

The com'onents hich are de0elo'ed are:-

. The online a''lication submits

". A''ro0al of the online a''lication

(. Issue against A''ro0ed a''lications

. Be'ort Generation

Since the hole 'ro7ect is not yet de0elo'ed and only fe com'onents are carried out$

The unit testing as carried out by se'arately o'erating the com'onents .The testing

of online submission 'art as carried out by chec%ing the all form 0alidation and

chec%ing the database after the form submission .The a''ro0al 'art as carried out by

testing ith the data hich are inserted in the database in the online submission

'art .The issue and re'ort 'ortion is also tested by the same data hich ere

'rocessed in the testing of a''ro0al of a''lication 'ortion.

Re#,lt

Testing is an essential stage of the softare de0elo'ment life cycle. If is 'erformed

'ro'erly by folloing an organiLations standards the end result ill be more robust

'rograms going to the system integration testing and finally a a system ith lo

maintenance. Pro'er coding and unit testing are basic ste's to ensure that the system

being built ill or% once it is 'ut together .3onsultancy center has been tested and

built to all searches related to doctors hos'itals diseases etc.

Concl,#ion12

The 'ro7ect has been de0elo'ed successfully and the 'erformance of the system has

been found satisfactory. The security has been incor'orated as re;uired by any

'lacement firm. &se of com'uter hel's the user in reducing the time asted in non-

'roducti0e or%. It further hel's the user in ha0ing immediate access to the

information as ell as to share the limited resources effecti0ely.

&ser friendly menu dri0en interface has been 'ro0ided to the user to interact ith the


33/33

system. &sers can tra0erse through the ebsite 'ro0ided the users ha0e the access

right set. The users can register themsel0es through a registration form and then can

use the ser0ices of the ebsite.

Reference# 9 5i8liograp$7 12

.e8 Reference#

.google.com

.dotnets'ider.com

5i8liograp$7 12

5oo# hich I referred for the reference

• A Programmers Introduction to c".)$ Third /dition: A Press

• #eginning. N/T Scri't "nd /dition$ by ilton

• The 3om'lete Beference SQ5

• The 3om'lete Beference CT25.

http://www.google.com/http://www.dotnetspider.com/http://www.google.com/http://www.dotnetspider.com/

Date post:	07-Jul-2018
Category:	Documents
Upload:	kajal
View:	213 times
Download:	0 times

Report Content for any project

Documents