dbms srs(sunny kumar gupta)

PONDICHERRY UNIVERSITY

SYNOPSIS

D E C I S I O N S U P P O R T S Y S T E M

Submitted by

SUNNY KUMAR GUPTA

MASTER OF COMPUTER SCIENCE

(2009-2012)Reg. No-1092438

ACKNOWLEDGEMENT

I am very grateful to all the people who

helped me to prepare this project “Decision

Support System” .At very outset, I express my

gratitude to the PONDICHERRY UNIVERSITY for

providing me an opportunity to conduct a project.

I express my gratitude to my guide and my

teacher Mr.SRI NIVASAN Those most valuable

guidance and super vision enable me to complete

this project .No appreciation is good enough for

the efficient guidance of encouragement. I have

received from him to time completing the project

report.

.

Lastly , I pay my sincere regards to my Parents

and very thanksful to my mother who always

encourage me to achieve the goal in my life.

SUNNY KUMAR GUPTA

Reg. no.-1092438

DECLARATION BY THE STUDENT

I DO THE HERE BY THE DECLARE THAT THE PROJECT

WORK ON “Decision Support System “HAS BEEN DONE

BY ME. AGAIN I DECLEARE THAT NEITHER ANY PART OF

THIS PROJECT HAS BEEN COPIED FROM ANY WHERE NOR

THIS PROJECT HAS BEEN SUBBIMITTED TO ANY OTHER

ANY UNIVESIRY/INSTITUTAION OR NOT PRESENTED ANY

WHERE OF AWARDED OF DEGREE

IN THE UNIVERITY OF ELSE, ANYWERE, ANYTIME,

BEFORE...

(………………..)

Table of Contents

Acknowledgements...........................................................................................................iiiSynopsis.............................................................................................................................iv1. Introduction....................................................................................................................1

1.1 About the Project...............................................................................................21.1.1 Objectives of the Project.....................................................................21.1.2 Features...............................................................................................3

1.2 Plan of the Report..............................................................................................32. Problem Definition and Feasibility Analysis...............................................................5

2.1 Introduction........................................................................................................62.2 Problem Definition.............................................................................................62.3 Feasibility Analysis............................................................................................6

2.3.1 Operational Feasibility........................................................................72.3.2 Technical Feasibility...........................................................................72.3.3 Economical Feasibility........................................................................8

2.4 Recommended Implementation.........................................................................83. Software Requirements Specification..........................................................................9

3.1 Introduction......................................................................................................103.1.1 Purpose of SRS.................................................................................103.1.2 Scope of the Product.........................................................................103.1.3 Definitions, Acronyms and Abbreviation.........................................103.1.4 Overview...........................................................................................11

3.2 General Description.........................................................................................113.2.1 Product Perspective...........................................................................113.2.2 Product Function...............................................................................123.2.3 General Constraints...........................................................................123.2.4 Assumptions and Dependencies.......................................................12

3.3 Specific Requirements.....................................................................................123.3.1 Functional Requirements..................................................................123.3.2 External Interface Requirements.......................................................133.3.3 Performance Requirements...............................................................133.3.4 Documentation Requirements...........................................................143.3.5 Fault Tolerance.................................................................................143.3.6 Design Constraints............................................................................143.3.7 Other Requirements..........................................................................143.3.8 Attributes...........................................................................................15

4. System Design – Preliminary......................................................................................17

4.1 Introduction......................................................................................................184.2 Basic Design Approach....................................................................................194.3 Design Concepts..............................................................................................204.4 Architectural Overview....................................................................................21

4.4.1 Advantages........................................................................................224.5 User Interface Design......................................................................................24

4.5.1 Input Design......................................................................................244.5.2 Output Design...................................................................................24

5. System Design – Detailed.............................................................................................255.1 Introduction......................................................................................................265.2 Modules – Purpose and Description................................................................26

5.2.1 Input Module.....................................................................................275.2.2 Output Module..................................................................................27

5.3 Activity Diagram.............................................................................................305.4 Use Case Diagram............................................................................................325.5 Sequence Diagram...........................................................................................34

6. Coding, Testing and Implementation.........................................................................366.1 Coding..............................................................................................................37

6.1.1 Naming Conventions........................................................................376.1.2 Comments.........................................................................................376.1.3 Statements construction and Indentation..........................................37

6.2 Testing..............................................................................................................386.2.1 Content Testing.................................................................................396.2.2 Interface Testing...............................................................................396.2.3 Navigation Testing............................................................................406.2.4 Component Testing...........................................................................406.2.5 Configuration Testing.......................................................................406.2.6 Security Testing................................................................................406.2.7 Performance Testing.........................................................................40

6.3 Implementation................................................................................................416.4 Integration Issues.............................................................................................41

7. Conclusion and Foreseeable Enhancements..............................................................427.1 Conclusion.......................................................................................................437.2 Future Enhancements.......................................................................................44

Bibliography ....................................................................................................................45Appendix – Screen Shots.................................................................................................47

1.INTRODUCTION

1.1 About The Project:-

The current package which is being used by

PONDICHERRY UNIVERSITY by its very nature is not

able to completely avoid duplication of work,

non-availability of the latest position in the

master record considerable human error because of

non-user friendly environment of the expected

level of data, problem relating to timely

correction of errors/creation of records: all of

which translate into delays unhappy customer,

lowered employee morale and ultimately non-too-

fussy image of the organization.

Thus, there is an urgent need for a more advanced

and efficient package.

1.1.1 Objectives Of The Project

This project involves the

development of Decision Support System.

This system performs the task of

managing/supporting and maintaining the

whole management of the MBA Students for

searching best MBA colleges in

India/World.

The project functions rights from

the entry for opening various accounts,

Searching best MBA College in

India/World, various reports. The whole

system has been developed in VB (Visual

Basic) to solve almost all the problem

faced by existing system. Input, output,

designing makes the system more users

friendly and thereby make an easy

understanding of the task performed in

the system.

Throughout the project, the emphasis

has been made to develop it as easy to

use and also user friendly. The user can

retrieve information immediately. Error

messaging strategy, validation and

verification check has been incorporated

in various stages of development.

Reports provided increase the power of

the software.

1.1.2 Features

To reduce the workload of the staff.

To reduce the delay in processing time.

To reduce the delay in generating reports.

To maintain reliable and update database.

To provide user friendliness in all possible

ways.

To provide great flexibility.

To make maintenance and changes easily.

To store data in a centralized locations.

To all the requirements of the bank.

2. Problem Definition and Feasibility Analysis

INTRODUCTIONS:-

PROBLEM DEFINITION

The current Decision Support System

is being developed with a view to

manipulate data associated with

Registration such as New User

Registration:-. This system will take

care of all the activities that are

concerned with above. After the

development of this system, the works,

which were done manually such as issuing

of comparing best colleges (overall,

Fresher, work experiences, women,

alumni, aspirants, students) and

searching of that, will be automated.

This system is mainly concentrating

on the comparison of colleges, inwards

and outwards as the title suggests.

The advantage of this system will

help to minimize the response time,

usually used to take much time and the

user had to wait for the same.

From this model it is clear that

There are various user processes.

Each process in turn may have several

other process associated with it.

All process works in an adequate range

and manipulates user data in least

time with accuracy.

The data would be stored and used also by the

Server.

2.3 FEASIBILITY ANALYSIS

Testing project feasibility:

Preliminary investigation examine project feasibility, the likelihood the system will be useful to the organization. Three important tests of feasibility are studied and described below:

Operational feasibility

Technical feasibility

Economic feasibility

Operational Feasibility:

Proposed projects are beneficial only if they

can be turned into information systems that

will meet the operating requirements of the

organization. This test of feasibility asks

if the system will work when it is developed

and installed. Are there major barriers to

implementation? Some of the important

questions that are useful to test operation

feasibility of a project are given below:

Is there sufficient support for the project

from the management? Form users? If the

present system is well liked and use to the

extent that persons will not be able to see

reasons for a change, there may be

resistance.

Are current business methods acceptable to

the users? If they are not, users may welcome

a change that will being about a more

operational and useful system.

Have the users been involved in the planning

and development of the project? If they are

involved at the earliest stage of project

development, the chances of resistance can be

possibly reduced.

Will the proposed system cause harm? Will it

produce poorer in any case or area? Will the

performance of staff member fall down after

implementation?

Technical Feasibility:

There are a number of technical issues

which are generally raised during the

feasibility stage of the investigation. They

are as follows:

Does the necessary technology exist to

do what is suggested (and can it be

acquired)?

Does the proposed equipments have the

technical capacity to hold the data required

to use the new system?

Can the system be upgraded if developed?

Are there technical guarantees of

accuracy, reliability, ease of access and

data security?

Economic Feasibility:

A system that can be developed

technically and that will be used if

installed must still be profitable for the

organization. Financial benefits must equal

or exceed the costs. The analysts raise

various financial and economic questions

during the preliminary investigation to

estimate the following:

The cost to conduct a full system

investigation.

The cost of hardware and software for the

class of application being considered.

The benefit in the form of reduced costs or

fewer costly errors.

The cost if nothing changes (i.e. the

proposed system is not developed).

RECOMMENDED IMPLEMENTATION

Implementation is the process of having

systems personal check out and put new

equipment into use, train users, install the

new application, and construct any files of

data needed to use it. Depending on the size

of the organization that will be involved in

using the application and the risk associated

with its use, systems developers may choose

to test the operation in only one area of the

firm. Sometimes this will run the old and new

systems together to compare the results.

Implementation includes all those activities

that take place to convert from the old

system to the new. The new system may be

totally new, replacing an existing manual or

automated system, or it may be a major

modification to an existing system.

Implementation is an ongoing process.

Implementation would cover the following

steps:

1. Configuring of the computer system.

2. Loading of the developed software on the

computer.

3. Training of operators at the Decision

Support System locations.

4. Error identification and corrections

there off.

4. System Design – Preliminary

4.1 Introduction 4.2 Basic Design Approach 4.3 Design Concepts

SYSTEM DESIGN

The system is designed based on

the objectives set for the new

information system in the strategic

plan. Our outmost objective is as

follows:

1)Increasing the Registration profit.

2)Securing the candidate intact with the

Decision Support System (Reg.).

3)Improving candidate facilities for

decision of selecting best MBA College

in India/World.

4)Understanding candidate requirements.

5)Suggesting a logical organization of

data.

6)Monitoring and control decision.

7)Up to the time of the system proposal, we

have concerned themselves with the local

design of the system. Although we have

decided that specific software should be

purchased as well as interface like

Visual Basic (VB). After the system

proposal is agreed to, we concern

themselves with the physical design of

the system. Here we create, detailed

specification for every aspect of the

system. This includes form designer,

file organization, procedural steps and

so on.

The following are the major steps in

system design:

1)Specification of data elements, records

and files.

2)Specification in input forms, data

preparation formats and identification

of personnel who will complete them.

3)Specification of system output.

4)Development of system flow charts

5)Development of feedback and control

procedures.

6)Development of program specifications.

7)Development of operating specifications.

8)Resource planning and implementation:

a) Phasing out the existing system.

b) Training user or personnel.

c) System review and parallel

operation.

4.5 User Interface Design

4.5.1 Input Design 4.5.2 Output Design

5. System Design – Detailed

5.1 Introduction 5.2 Modules – Purpose and Description

5.2.1 Input Module 5.2.2 Output Module

Design

Module Design

The modules are designed using ORACLE 10g &

VISUAL BASIC 6.0. The functional details of

modules are given below :

Master Module

This module is responsible for ::

Entry/modification/searching/viewing of

records and all other related information.

It consists of the following sub-module:

i) Add Module

This module is responsible for entry of

details of all the codes.

ii) Edit Module

The objective of this module is to

modification & deletion of records. It edits

the value of.

iii)Report Module

This module provides report of

organization.

DESIGN PATTRNS

The design of input play very significant

role in getting the correct output. It covers

all phases of input from creation of initial

data (original recording) to actual entering

the data to the system for processing. The

input design is the link that ties the

information system into the world of its

users. Some features of design may very

depending on whether the system is batch-

oriented or on –line. Here, we will discuss

the various objectives of input design. They

focus on:

Avoiding delay

Avoiding errors in data

Keeping the process simple

Each of the five objectives of input design

is briefly discussed below:

1. Avoiding Delay

When processing is delayed owing to data

preparation or data entry, the cause is

called a bottleneck. Avoid bottlenecks when

designing input should always be one of the

objectives of the analyst.

2. Avoiding Errors in Data

The third objective deals with errors. In one

sense, the rate at which errors occur is

dependent on the quantity of data. Since the

lower the amount of data is inputted, there

are fewer opportunities for the error to

occur.

Firstly, the analyst can reduce this number

by reducing the volume of data that must be

entered for each transaction.

Secondly, the analyst can also affect error

rates of an operation through design.

The manner in which data must be entered can

reduce the chance of errors.

Still, a third aspect of error control is the

need to detect errors when they do occur.

Checks and balances in the data entry

programs, called input validation techniques,

also detect errors in input.

2. Keeping the Process Simple

Perhaps the best advice to analysts is to achieve all of the objectives mentioned in the simplest manner possible. The best-designed system fits the people who will use it in the way that is comfortable for them, and at the same time it6 provides the error control methods management acceptable to the users. In contrast, one will have to work to get users to accept complex or confusing input designs, and there is no guarantee he will succeed in installing and running complex system. So it is advisable to avoid

complexity when there are simple alternatives.

Input Verification and control:

There are many methods which are commonly

used to verify data entering the system as

input. Some of them are:

Key Verification:

A second operator rekeys the data already

recorded. This method is used for verifying

data recorded in punched cards or on

diskettes and magnetic tape. Then two

floppies are compared to correct record by

record which mismatched during comparison

after verifying, from the original documents.

This is most effective method used by

computer service bureaus for data validation.

Visually Displaying an Identifying

Characteristic:

When using a terminal, a part number is

entered. Displayed in the VDT is the

description of the part, which is then

visually confirmed by the operator.

Verification of Codes:

The pay and fringe benefits are calculated

for employee’s based upon their payroll

status. Assuming that the valid status code

an error massage would be generated

Verification of data type:

Some input fields should contain only numeric

data while others should contain only

alphabetic data. The fields can be edited to

make certain that only the right type of data

is recorded in each field.

Activity Diagram

Use Case Diagram

6. Coding, Testing and Implementation

Frontpage Interface

Frontpage Coding

Dim con As New ADODB.Connection

Dim rs As New ADODB.Recordset

Private Sub Command1_Click()

Frame1.Visible = True

List1.Visible = False


End Sub


List1.Visible = True


End Sub




End Sub


Form8.Show

Form1.Visible = False









End Sub




End Sub


Form3.Show









End Sub


con.Open "Provider=Microsoft.Jet.OLEDB.4.0;Data

Source=C:\Documents and Settings\sunny\My Documents\

Downloads\dss\access_dss.mdb;Persist Security

Info=False"

con.CursorLocation = adUseClient

rs.Open "select * from new_user_reg", con,

adOpenDynamic, adLockReadOnly

While rs.Fields("user_id").Value <> Text1.Text And

rs.Fields("pw1").Value <> Text2.Text

rs.MoveNext

Wend

If rs.Fields("user_id").Value = Text1.Text And

rs.Fields("pw1").Value = Text2.Text Then

Form9.Show

Else

MsgBox ("u have enter invalid userid nd password")

End If

rs.Close

Set rs = Nothing

con.Close

Set con = Nothing

End Sub

Private Sub e_Click()

End

End Sub

Private Sub Form_Load()

Text1.Text = ""

Text2.Text = ""

End Sub

Private Sub h_Click()

'CommonDialog1.FileName = "C:\Documents and Settings\

sons\My Documents"

CommonDialog1.ShowHelp

'FileName = CommonDialog1.FileName

End Sub

Private Sub Label7_Click(Index As Integer)


Form2.Visible = True

End Sub

Private Sub Label9_Click(Index As Integer)

Form3.Show








End Sub

Private Sub List1_Click()

If (List1.Text = "Criteria Search") Then

Form9.Show



End If

End Sub


If (List2.Text = "Top 50 College in INDIA") Then

Form10.Show



End If

End Sub

Private Sub o_Click()

CommonDialog1.FileName = "C:\Documents and Settings\

sons\My Documents"

CommonDialog1.ShowOpen

FileName = CommonDialog1.FileName

End Sub

Private Sub p_Click()

'CommonDialog1.FileName = "C:\Documents and Settings\

sons\My Documents"

CommonDialog1.ShowPrinter


End Sub

Private Sub s_Click()

CommonDialog1.FileName = "C:\Documents and Settings\

sons\My Documents"

CommonDialog1.ShowSave

FileName = CommonDialog1.FileName

End Sub

Private Sub Text1_Change()

'Text1.SetFocus

End Sub

Criteria Search Interface

Criteria Search Coding

'Dim FSys As Object

Private Sub Combo1_Click()



If (Combo1.Text = "India") Then





Line2.Visible = True


Label12.Visible = True






Combo3.Visible = True

Frame3.Visible = False

Label17.Visible = False


Combo2.Visible = False



Check1.Value = 0

Check2.Value = 0

Check3.Value = 0

Check4.Value = 0

Check5.Value = 0

Check6.Value = 0

Check7.Value = 0

Check8.Value = 0

Check9.Value = 0

Check10.Value = 0

Check11.Value = 0

Check12.Value = 0

Check13.Value = 0

Check14.Value = 0

Check15.Value = 0

Check16.Value = 0

Check17.Value = 0

Check18.Value = 0

Check19.Value = 0

Check20.Value = 0

ElseIf (Combo1.Text = "Out-Side India") Then














Combo2.Visible = True






Check1.Value = 0

Check2.Value = 0

Check3.Value = 0

Check4.Value = 0

Check5.Value = 0

Check6.Value = 0

Check7.Value = 0

Check8.Value = 0

Check9.Value = 0

Check10.Value = 0

Check11.Value = 0

Check12.Value = 0

Check13.Value = 0

Check14.Value = 0

Check15.Value = 0

Check16.Value = 0

Check17.Value = 0

Check18.Value = 0

Check19.Value = 0

Check20.Value = 0

ElseIf (Combo1.Text = "Select") Then


















Line2.Visible = False


End If

End Sub


Form1.Show




Combo1.Text = "Select"

End Sub


Check6.Value = 0

Check7.Value = 0

Check8.Value = 0

Check9.Value = 0

Check10.Value = 0

Check11.Value = 0

Check11.Value = 0

End Sub


Check13.Value = 1

Check14.Value = 1

Check15.Value = 1

Check16.Value = 1

Check17.Value = 1

End Sub


Check13.Value = 0

Check14.Value = 0

Check15.Value = 0

Check16.Value = 0

Check17.Value = 0

End Sub


Check21.Value = 1

Check22.Value = 1

Check23.Value = 1

End Sub


Check21.Value = 0

Check22.Value = 0

Check23.Value = 0

End Sub


Check18.Value = 0

Check19.Value = 0

Check20.Value = 0

End Sub


Check18.Value = 1

Check19.Value = 1

Check20.Value = 1

End Sub




End Sub




End Sub


Form8.Show









TabStrip1.Visible = False




End Sub




End Sub


Form3.Show









TabStrip1.Visible = False




End Sub


Check1.Value = 1

Check2.Value = 1

Check3.Value = 1

Check4.Value = 1

Check5.Value = 1

End Sub


Check1.Value = 0

Check2.Value = 0

Check3.Value = 0

Check4.Value = 0

Check5.Value = 0

End Sub


Check6.Value = 1

Check7.Value = 1

Check8.Value = 1

Check9.Value = 1

Check10.Value = 1

Check11.Value = 1

Check11.Value = 1

End Sub


Form9.WindowState = 2

TabStrip1.Visible = True


If (Combo1.Text = "Select") Then




















End If

End Sub

Private Sub Label14_Click()


End Sub

Private Sub Label19_Click()


'CommonDialog1.Filter = "All Files|*.*"

'CommonDialog1.InitDir = "C:\Documents and Settings\sunny\My Documents\Downloads\MBA IMAGES\usacode.txt"

'CommonDialog1.Flags = cdlOFNHideReadOnly

'CommonDialog1.ShowOpen


'Set TStream = FSys.opentextfile("C:\Documents and Settings\sons\My Documents\Downloads\MBA IMAGES\usacode.txt", ForReading)

End Sub


If (List1.Text = "Criteria Search") Then


TabStrip1.Visible = True





















End If

End Sub


If (List2.Text = "Top 50 College in INDIA") Then

Form10.Show



End If

End Sub

Submit Button Coding With Database

Connectivity


'con.Open "Provider=Microsoft.Jet.OLEDB.4.0;Data

Source=G:\Project in VB\dss\access_dss.mdb;Persist

Security Info=False"

con.Open "Driver={Microsoft ODBC for

Oracle};Server=xe;Uid=system;Pwd=rajnish"

con.CursorLocation = adUseClient

rs.Open "select * from new_user_reg", con,

adOpenStatic, adLockOptimistic

'rs.LockType = adLockOptimistic

'rs.Open "select * from new_user_reg", con

rs.AddNew

rs.Fields("user_id").Value = Form3.Text1.Text

rs.Fields("pw1").Value = Form3.Text2.Text

rs.Fields("pw2").Value = Form3.Text3.Text

rs.Fields("prefix").Value =

Form3.Combo1.List(Combo1.ListIndex)

rs.Fields("first_n").Value = Form3.Text4.Text

rs.Fields("init").Value = Form3.Text5.Text

rs.Fields("last_n").Value = Form3.Text6.Text

rs.Fields("address1").Value = Form3.Text7.Text

rs.Fields("address2").Value = Form3.Text8.Text

rs.Fields("city").Value = Form3.Text9.Text

rs.Fields("postal_code").Value = Form3.Text10.Text

rs.Fields("country").Value =


rs.Fields("state/province").Value =


rs.Fields("email").Value = Form3.Text11.Text

rs.Fields("@example_com").Value =


rs.Fields("gender").Value =


rs.Fields("birth_date_dd").Value =


rs.Fields("birth_date_mm").Value =


rs.Fields("birth_date_yy").Value =


rs.Fields("birth_country").Value =


rs.Fields("COUNTRY_c").Value =


rs.Fields("native_l").Value = Form5.Text1.Text

rs.Fields("other_l").Value = Form5.Text2.Text

rs.Fields("business_majors").Value =

Form6.Text1.Text

rs.Fields("prof_major").Value = Form6.Text2.Text

rs.Fields("other_major").Value = Form6.Text3.Text

rs.Fields("ugi").Value = Form6.Text4.Text

rs.Fields("ug_GPA").Value = Form6.Text5.Text

rs.Fields("ug_year").Value =


rs.Fields("g_degree").Value =


rs.Fields("gi").Value = Form6.Text6.Text

rs.Fields("g_major").Value = Form6.Text7.Text

rs.Fields("g_GPA").Value = Form6.Text8.Text

rs.Fields("gg_year").Value =


rs.Fields("t_GMAT_score").Value = Form6.Text9.Text

rs.Fields("date_taken1_month").Value =


rs.Fields("daie_taken1_yeaar").Value =


rs.Fields("TOEFL_tta_score").Value =


rs.Fields("score").Value = Form6.Text10.Text

rs.Fields("date_taken2_month").Value =


rs.Fields("date_taken2_year").Value =


rs.Fields("current_empl").Value = Text1.Text

rs.Fields("job_title").Value = Text2.Text

rs.Fields("ywc_empl").Value =

Combo1.List(Combo1.ListIndex)

rs.Fields("y_fulltime_work").Value =

Combo2.List(Combo2.ListIndex)

rs.Fields("ur_info").Value = Text3.Text

rs.Update

MsgBox "Data Saved Successfully"

rs.Close

Set rs = Nothing

con.Close

Set con = Nothing

End Sub

College Comparision Interface




Form10.Frame1.Visible = True

Form10.Check1.Value = 0






















Command19.Visible = False

























End Sub


Form12.WindowState = 2

End Sub




End Sub




End Sub




End Sub




End Sub




End Sub




End Sub




End Sub




End Sub




End Sub




End Sub




End Sub




End Sub




End Sub




End Sub




End Sub




End Sub




End Sub




End Sub




End Sub




End Sub




End Sub




End Sub




End Sub


Form8.Show




End Sub




End Sub




End Sub




End Sub




End Sub

Comparision Of Top 50 Colleges Interface

TESTING

Testing plays a critical role in quality

assurance for software. Due to its limitations of

the verification methods for the previous phases,

design and requirement faults also appear in the

code. Testing is used to detect these errors, in

addition to the errors introduced during coding

phase. There are two approaches to testing:

functional and structural. In functional testing

the internal logic of the system to be tested is

not considered and test cases are decided based

on requirement specifications. Equivalence class

portioning, boundary value analysis, and cause

effect graph are examples of methods for

selecting test cases for functional testing. In

structural testing, the test cases are decided

entirely on the internal logic of the program.

The most common methods are: i) control-flow

based criterion are statement coverage and branch

coverage and ii) common data flow based criteria

are all definitions and all users. As the goal of

testing is to detect faults in the programs,

different levels of testing are often used. The

levels of testing are classified as unit testing,

integration testing, system testing and

acceptance testing. Testing process usually

starts with a test plan, which is the best

document guiding the entire testing of the

software.

Navigation Testing

IMPLEMENTATION

Implementation is the process of having systems

personal check out and put new equipment into

use, train users, install the new application,

and construct any files of data needed to use it.

Depending on the size of the organization that

will be involved in using the application and the

risk associated with its use, systems developers

may choose to test the operation in only one area

of the firm. Sometimes this will run the old and

new systems together to compare the results.

Implementation includes all those activities that

take place to convert from the old system to the

new. The new system may be totally new, replacing

an existing manual or automated system, or it may

be a major modification to an existing system.

Implementation is an ongoing process.

Implementation would cover the following

steps:

5. Configuring of the computer system.

6. Loading of the developed software on the

computer.

7. Training of operators at the Hospital

Management’s locations.

8. Error identification and corrections

there off.

7. Conclusion and Foreseeable Enhancements

Future Enhancements Of The Application

1) The project can be easily updatable in

future if required.

2) The project contains data dictionaries

which will help in

Updation future

3) The project can be easily implemented

4) The project comprises features which can

be the required

in coming days

REFERENCES

ORACLE:

o SQL Complete Reference - SQL

Press

Software Engineering and System Analysis:

o System Analysis an Design- Elias M. Awad

o Software Engineering(Practitioners App.)-

R. S. Pressman

o Software Engineering- Pankaj Jalote

RDBMS and SQL:

o An Introduction to Database System-

Bipin C. Desai

o SQL: The Complete Reference -

Groff & Weinberg

Visual Basic 6.0

o Mastering Database Programming with VB 6-

E. Petroutsos

o VB 6 Programming Black Book- S.Holzner

o Mastering VB 6- E. Petroutsos

Hardware Details :

HP Laptop

Processor : intel CORE i3

RAM : 2GB

Hard Disc : 500GB

Cache : 512 KB

BIBLIOGRAPHY

Software Engineering and System Analysis:

o System Analysis an Design- Elias M. Awad

o Software Engineering(Practitioners App.) -

R. S. Pressman

o Software Engineering- Pankaj Jalote

dbms srs(sunny kumar gupta)

Documents

project report

project work

specific requirements

functional requirements

performance requirements

documentation requirements

feasibility analysis

operational feasibility