Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                

E-Property Project Report

Download as pdf or txt
Download as pdf or txt
You are on page 1of 60

TABLE OF CONTENTS

Sl. No. CONTEXT Pg. No.

1. ABSTRACT 01

2. INTRODUCTION 02-04
3. SOFTWARE ENVIRONMENT 05-08

4. SYSTEM STUDY 09-10

5. SYSTEM DESIGN 11-13


6. CODING 14-35

7. SCREEN-SHOTS 36-44

8. SYSTEM TESTING 45-54


9. TABLE DESIGN STRUCTURE 55-56

10. IMPLEMENTATION 57

11. MAINTENANCE 58

12. BIBLIOGRAPHY 59
ABSTRACT
PROJECT:

E-property is software application software to track customer details and property


details. Software have the provision to collect all the details of each customers details as well
selling, buying property details contains property category, budget, city, area, square-feet,
property image, managing selling buying list and request of buyer details.

OBJECTIVE:

There are several advantages of employing a Real Estate management system for admin,
buyers and sellers. Real Estate management system save time, money, space and simplify the
often tedious task of maintain customer details, property details and other records.

SCOPE:
E-property helps to minimize the real estate agencies daily workload in easy way. In the
modern world, where maintain buyer seller information and property complete information
has become a very big problem, it has become very important to avoid the wastage of time in
modern big real estate agencies as well builders. This system proves to be useful in reducing
wastage of unnecessary workload, time and maintenance free. This E-property Management
system enables buyers to search property based on various criterias like type, budget, area
and city. If buyers are like to meet the seller or to visit site, have option to send request to
seller. It is exactly like wish-list for buyers as well sellers. So that buyer and seller can meet
and discuss about properties.

RESOURCES REQUIRED: -
Development Tool: - VB 6.0
Database: - oracle 10g

1 E-PROPERTY
INTRODUCTION
The project entitled E-property is to be developed for maintaining the real estate
agents activities like, customer details (Buyers & Sellers), property details, budget, area,
property categories etc. The system is efficient in generating reports which will help in the
maintenance of the datas related to real estate day to day activities very easily. E-property is
software application software to track customer details and property details. Software have
the provision to collect all the details of each customers details as well selling, buying
property details contains property category, budget, city, area, square-feet, property image,
managing selling buying list and request of buyer details. E-property helps to minimize the
real estate agencies daily workload in easy way. In the modern world, where maintain buyer
seller information and property complete information has become a very big problem, it has
become very important to avoid the wastage of time in modern big real estate agencies as
well builders. This E-property Management system enables buyers to search property based
on various criterias like type, budget, area and city. If buyers are like to meet the seller or to
visit site, have option to send request to seller.

Existing System

The existing system is not automated fully as only the accounts are automated with the
accounting software. The Property details and Customer follow-ups are maintained in excel
which will take more time to search from the long lists, property individual details are not
maintained through system so it is very difficult to maintain the details. As the current data is
maintained through ledgers and excel sheet so there is no proper reports for facilitation of the
administration of the showroom.

Disadvantages of the Existing System

Only accounts is systemized

Lack of reports

Customer Details & Property details are maintained in excel Sheet which leads to the
inaccurate information.

Customer data are not maintained properly which leads the follow-ups slow.

2 E-PROPERTY
Proposed System

The proposed system overcomes the disadvantages of the existing system and records the
entire activities happening in the business place. It helps to improve business in vertical
angle. The reports generated will enhance the efficiency of the application. Buyers can get the
details of available properties area wise, budget wise as well size (square feet) wise. If they
like to buy, have option to send request to user that easily we can connect Buyer and Seller
easily.

Advantages of the proposed System

Entire activities of the business are recorded through the system.

Customer Data is maintained.

Reports generated will be more useful for management to take the quick business
decisions.

Customer database is maintained which will be helpful for intimating the service
completion details and new offers

Customer follow-ups are maintained which will be an added advantage of this system.

Modules use in this Project:

Admin Login
o Add Category
o Add States
o Add Cities
o View States and Cities
o New Customer Approval
o All customer Details
o New Property Approval
o All Property Details
o Sales Details
o Service Details

3 E-PROPERTY
Customer Login
o Change Password
o Sell Property
o My Selling List
o Buyer request
o Search Property
o
Hardware and Software requirement:

Hardware Requirement

Processor : Intel Core Duo 2.0 GHz or more


RAM : 1 GB or More
Harddisk : 80GB or more
Monitor : 15 CRT, or LCD monitor
Keyboard : Normal or Multimedia
Mouse : Compatible mouse

Software Requirement

Front End : Visual Baisic 6.0

Software Required : Visual Basic 6.0 IDE

Back End : Oracle 10g

Operation System : Windows 7

4 E-PROPERTY
SOFTWARE ENVIRONMENT
Features of Visual Basic: Visual Basic is a flexible, high level, structured
programming language.

Visual Basic includes certain low level features that are normally available only
in assembly or machine language.

Visual Basic is widely available, commercial interpreter are available for most
personal computer, mini computers and main frames.

Visual Basic is largely machined independent. Programs written in visual basic


are easily ported from one computer to another.

Your programs interface may include the familiar controls that window users
already know how to operate-such as command buttons, option list, text boxes and
scroll bars.

With just a few mouse actions, you can add any combination of these controls
to a program.

As a result design tasks that used to require many hours of detailed


programming efforts can how be completed in minutes.

In Visual Basic you can quickly design the visual elements of any new
programming project.

5 E-PROPERTY
The Programming Process: These standards steps are to be followed while
creating Visual Basic Programs:

1. Deciding what your application is do by creating an overall design.


2. Creating the Visual Basic portion of the application (the serene and menus
that the users will interact with)
3. Adding the Visual Basic programming language code to tie the Visual Basic
elements together and to automate the program.

4. Testing the application to locate and remove any bugs.

5. Compiling the tested application and distribute the Compiled application to


the end users.

VISUAL BASIC 6.0:

Visual basic includes a special helpers system called a debugger that the
programmer can use to help locate bugs that appear during testing. The
debugger is an interactive monitoring system that you turn on and off
inside Visual Basic that helps you locate statements that may contain
bugs.

Programming Maintenance

Apart from the bugs, the programmer has to maintain the program he
/she has created. Program Maintainance is a term used for the updating
of a program after the program after the program is put into use. This
updating may be a result of the users request or a change in the way the
program needs to operate.

6 E-PROPERTY
Project:
A project is a collection of files that make up your application. A single

Application might consist of several files and the projects is the


collection of those files.

Multiple Documents Interface (MDI)

It allows the application to contain multiple documents windows. In


effect, this interface lets your work with several sets of data in multiple
window with in the program. Each document window is called a child window.

Single Document Interface (SDI)

It limits the application take on a window Explorer- like interface with


topic summaries in the left window a n details for a selected topic in the
right pane.

7 E-PROPERTY
ORACLE 10G:
oracle10g is Oracle's grid computing product group including a
database management system (DBMS) and an application server. In addition to
supporting grid computing features such as resource sharing and automatic load
balancing, 10g products automate many database management tasks.
ORACLE 10G FEATURES:

Application Development

Availability

Business Intelligence

Clustering

Content Management

Database Overall

Database Security

Grid Computing

Grid Management

Information Integration

Location Services

Performance and Scalability

8 E-PROPERTY
SYSTEM STUDY

FEASIBILITY STUDY

The feasibility of the project is analyzed in this phase and business proposal is put forth with

a very general plan for the project and some cost estimates. During system analysis the

feasibility study of the proposed system is to be carried out. This is to ensure that the

proposed system is not a burden to the company. For feasibility analysis, some

understanding of the major requirements for the system is essential.

Three key considerations involved in the feasibility analysis are

ECONOMICAL FEASIBILITY

TECHNICAL FEASIBILITY

SOCIAL FEASIBILITY

ECONOMICAL FEASIBILITY

This study is carried out to check the economic impact that the system will have

on the organization. The amount of fund that the company can pour into the research and

development of the system is limited. The expenditures must be justified. Thus the developed

system as well within the budget and this was achieved because most of the technologies

used are freely available. Only the customized products had to be purchased.

9 E-PROPERTY
TECHNICAL FEASIBILITY:

This study is carried out to check the technical feasibility, that is, the technical

requirements of the system. Any system developed must not have a high demand on the

available technical resources. This will lead to high demands on the available technical

resources. This will lead to high demands being placed on the client. The developed system

must have a modest requirement, as only minimal or null changes are required for

implementing this system.

SOCIAL FEASIBILITY

The aspect of study is to check the level of acceptance of the system by the

user. This includes the process of training the user to use the system efficiently. The user

must not feel threatened by the system, instead must accept it as a necessity. The level of

acceptance by the users solely depends on the methods that are employed to educate the user

about the system and to make him familiar with it. His level of confidence must be raised so

that he is also able to make some constructive criticism, which is welcomed, as he is the final

user of the system.

10 E-PROPERTY
SYSTEM DESIGN
Systems design is the process of defining the architecture, components, modules,

interfaces, and data for a system to satisfy specified requirements. Systems design could be

seen as the application of systems to product development. There is some overlap with the

disciplines of system analysis and system architecture.

Logical design:
The logical design of a system pertains to an abstract representation of the data flows, inputs

and outputs of the system. This is often conducted via modelling, using an over-abstract (and

sometimes graphical) model of the actual system. In the context of systems, designs are

included. Logical design includes (ER diagrams).

Physical design:
The physical design relates to the actual input and output processes of the system. This is

explained in terms of how data is input into a system, how it is verified authenticated, how it

is processed, and how it is displayed. In physical design, the following requirements about

the system are decided.

1. Input requirement,

2. Output requirements,

3. Storage requirements,

4. Processing requirements,

5. System control and backup or recovery.

11 E-PROPERTY
Put another way, the physical portion of systems design can generally be broken

down into three sub-tasks:

1. User Interface Design

2. Data Design

3. Process Design.

ER DIAGRAM:

12 E-PROPERTY
DFD: DATA FLOWING:

13 E-PROPERTY
CODING
WELCOME
Option Explicit

Private Sub Form_Load()

End Sub

Private Sub Timer1_Timer()

If ProgressBar1.Value = 100 Then

Me.Hide

Timer1.Enabled = False

Home.Show

Else

ProgressBar1.Value = Val(ProgressBar1.Value) + Val(1)

End If

Label3.Caption = ProgressBar1.Value

End Sub

HOME
Option Explicit

Private Sub Command1_Click()

Sample.Show

End Sub

14 E-PROPERTY
Private Sub Form_Load()

End Sub

Private Sub Image1_Click()

End

End Sub

Private Sub Image3_Click()

AdminLogin.Show

End Sub

Private Sub Image5_Click()

CutomerLogin.Show

End Sub

Private Sub Image6_Click()

NewUser.Show

End Sub

ADMIN LOGIN
Private Sub Command1_Click()

Dim rcnt As Integer

Dim un, pw As String

Dim rex As RegExp

15 E-PROPERTY
Set rex = New RegExp

rex.Pattern = "^[a-zA-Z0-9]{1,10}$"

If Not rex.Test(Text1.Text) Then

MsgBox "Enter Proper UserName", vbExclamation, "Check Your Input"

Text1.SetFocus

ElseIf Not rex.Test(Text2.Text) Then

MsgBox "Enter Proper Password", vbExclamation, "Check Your Input"

Text2.SetFocus

Else

recn

un = Text1.Text

pw = Text2.Text

connectdb

rec.CursorLocation = adUseClient

rec.Open "select * from rs_admin where uname='" & un & "' and pwd='" & pw & "'", con,
adOpenDynamic, adLockOptimistic

rcnt = rec.RecordCount

If rcnt = 1 Then

RS.adnam = un

Me.Hide

Home.Hide

AdminHome.Show

16 E-PROPERTY
Else

Label5.Caption = "Login info is not correct"

clr

End If

rec.Close

End If

End Sub

Private Sub Form_Load()

Dim ap, src, nwpath As String

Dim oPic As StdPicture

Me.AutoRedraw = True

src = "/Images/bg1.jpg"

ap = App.Path

nwpath = ap + src

Set oPic = LoadPicture(nwpath)

PaintPicture oPic, 0, 0, Me.ScaleWidth, Me.ScaleHeight

Set oPic = Nothing

Me.Visible = True

Text1.SetFocus

17 E-PROPERTY
End Sub

Private Sub Image1_Click()

Unload Me

End Sub

Private Sub Image2_Click()

End

End Sub

Sub clr()

Text1.Text = ""

Text2.Text = ""

End Sub

ADMIN HOME
Private Sub Command1_Click()

On Error Resume Next

With Adodc1.Recordset

.AddNew

.Fields(0) = Text1.Text

End With

End Sub

Private Sub Command2_Click()

On Error Resume Next

Adodc1.Recordset.Delete

18 E-PROPERTY
End Sub

Private Sub Command3_Click()

With Adodc1.Recordset

.Fields(0) = Text1.Text

.Update

End With

End Sub

Private Sub Form_Load()

Set Text1.DataSource = Adodc1.Recordset

Text1.DataField = "stname"

End Sub

Private Sub Image2_Click()

Unload Me

End sub

ADD CATEGORY
Sub Command1_Click()

With Adodc1.Recordset

.AddNew

.Fields(0) = Text1.Text

End With

End Sub

Private Sub Command2_Click()

On Error Resume Next

19 E-PROPERTY
Adodc1.Recordset.Delete

End Sub

Private Sub Command3_Click()

With Adodc1.Recordset

.Fields(0) = Text1.Text

.Update

End With

End Sub

Private Sub Form_Load()

Set Text1.DataSource = Adodc1.Recordset

Text1.DataField = "ctname"

End Sub

Private Sub Image2_Click()

Unload Me

End Sub

ADD STATES
Option Explicit

Private Sub Command1_Click()

On Error GoTo adst

20 E-PROPERTY
recn

connectdb

rec.CursorLocation = adUseClient

Dim cname, sname As String

Dim rcnt As Integer

sname = Combo1.Text

cname = Text1.Text

rec.Open "select cname from rs_cities where cname='" & cname & "'", con, adOpenDynamic,
adLockOptimistic

rcnt = rec.RecordCount

rec.Close

con.Close

If rcnt = 0 Then

connectdb

rec.Open "insert into rs_cities(cname,sname)values('" & cname & "','" & sname & "')", con,
adOpenDynamic, adLockOptimistic

If rec.State = 1 Then

MsgBox "City not Added", vbOKOnly + vbCritical, "Error"

Else

MsgBox "City Added successfully", vbOKOnly + vbInformation, "Done"

Label3.Caption = "City Added successfully"

clr

End If

Else

21 E-PROPERTY
MsgBox "City Info Exist", vbOKOnly + vbExclamation, "Error"

End If

adstexit:

Exit Sub

adst:

MsgBox "Close the window and try again", vbOKOnly + vbCritical, "Error"

Resume adstexit

End Sub

Private Sub Command3_Click()

clr

End Sub

Sub clr()

Text1.Text = ""

Combo1.Text = ""

End Sub

Private Sub Form_Load()

Adodc1.Refresh

With Adodc1.Recordset

Do Until .EOF

Combo1.AddItem ![stname]

22 E-PROPERTY
.MoveNext

Loop

End With

End Sub

Private Sub Image2_Click()

Unload Me

End Sub

Private Sub Label5_Click()

Me.Hide

StatesCities.Show

End Sub

ADD CITIES
Private Sub Command1_Click()

With Adodc1.Recordset.AddNew.Fields(0) = Text1.Text

End With

End Sub

Private Sub Command2_Click()

On Error Resume Next

Adodc1.Recordset.Delete

End Sub

Private Sub Command3_Click()

With Adodc1.Recordset.Fields(0) = Text1.Text.Update

23 E-PROPERTY
End With

End Sub

Private Sub Form_Load()

Set Text1.DataSource = Adodc1.Recordset

Text1.DataField = "ctname"

End Sub

Private Sub Image2_Click()

Unload Me

End Sub

CUSTOMER LOGIN
Option Explicit

Private Sub Command1_Click()

Dim rcnt As Integer

Dim em, pw As String

recn

em = Text1.Text

pw = Text2.Text

24 E-PROPERTY
connectdb

rec.CursorLocation = adUseClient

rec.Open "select * from rs_usr where uemail='" & em & "' and upwd='" & pw & "'", con,
adOpenDynamic, adLockOptimistic

rcnt = rec.RecordCount

If rcnt = 1 Then

RS.cusnam = em

Me.Hide

Home.Hide

CustomerHome.Show

Else

Label5.Caption = "Login info is not correct"

clr

End If

rec.Close

End Sub

Private Sub Command2_Click()

clr

End Sub

Sub clr()

Text1.Text = ""

Text2.Text = ""

25 E-PROPERTY
End Sub

Private Sub Form_Load()

Me.Visible = True

Text1.SetFocus

End Sub

Private Sub Image1_Click()

Unload Me

End Sub

Private Sub Image2_Click()

End

End Sub

CUSTOMER HOME
Option Explicit

Private Sub buyreqst_Click()

Request.Show

End Sub

Private Sub chngpwd_Click()

ChangePassword.Show

End Sub

Private Sub cusquit_Click()

Set rec = Nothing

26 E-PROPERTY
Unload Me

Home.Show

End Sub

Private Sub cussell_Click()

End Sub

Private Sub cusrch_Click()

Search.Show

End Sub

Private Sub Form_Load()

With Image1

Image1.Left = (Screen.Width - .Width) / 2

End With

With Label1

Label1.Left = (Screen.Width - .Width) / 2

End With

Label1.Caption = RS.cusnam

End Sub

Private Sub selllist_Click()

27 E-PROPERTY
MySellingList.Show

End Sub

Private Sub sellprop_Click()

SellProperty.Show

End Sub

CHANGE PASSWORD
Option Explicit

Private Sub Command1_Click()

On Error GoTo chpwd

Dim cpwd, npwd, rpwd, sesn As String

Dim rcnt As Integer

cpwd = Text1.Text

npwd = Text2.Text

rpwd = Text3.Text

sesn = RS.cusnam

If npwd = rpwd Then

recn

connectdb

rec.CursorLocation = adUseClient

28 E-PROPERTY
rec.Open "select uemail,upwd from rs_usr where uemail='" & sesn & "' and upwd='" & cpwd &
"'", con, adOpenDynamic, adLockOptimistic

rcnt = rec.RecordCount

recn

If rcnt = 1 Then

connectdb

rec.Open "update rs_usr set upwd='" & npwd & "' where uemail='" & sesn & "'", con,
adOpenDynamic, adLockOptimistic

If Not rec.State = 1 Then

MsgBox "Password Updated Successfully", vbOKOnly + vbInformation, "Message"

clr

Else

MsgBox "Password Not Updated", vbOKOnly + vbCritical, "Message"

clr

End If

Else

MsgBox "Current Password is not correct", vbOKOnly + vbExclamation, "Message"

clr

End If

Else

MsgBox "Retype Password is Mismatch", vbOKOnly + vbExclamation, "Message"

clr

End If

chpwdexit:

Exit Sub

29 E-PROPERTY
chpwd:

MsgBox "Close the window and try again", vbOKOnly + vbCritical, "Error"

Resume chpwdexit

End Sub

Private Sub Command3_Click()

clr

End Sub

Sub clr()

Text1.Text = ""

Text2.Text = ""

Text3.Text = ""

End Sub

Private Sub Form_Load()

End Sub

Private Sub Image2_Click()

Unload Me

End Sub

NEW USER
Private Sub Combo1_Click()

Dim stnam As String

30 E-PROPERTY
stnam = Combo1.Text

rec.Open "select * from rs_cities where sname='" & stnam & "'", con, adOpenDynamic,
adLockOptimistic

Combo2.Clear

Do Until rec.EOF

Combo2.AddItem rec.Fields("cname")

rec.MoveNext

Loop

rec.Close

End Sub

Private Sub Command1_Click()

On Error GoTo adusr

recn

connectdb

rec.CursorLocation = adUseClient

Dim ustatus, fnam, lnam, gen, dob, stat, cit, ema, pw, adr As String

Dim mob, rcnt As Integer

fnam = Text1.Text

lnam = Text2.Text

mob = Text5.Text

31 E-PROPERTY
ema = Text3.Text

pw = Text4.Text

adr = Text6.Text

stat = Combo1.Text

cit = Combo2.Text

dob = DTPicker1.Value

ustatus = "No"

If Option1.Value = True Then

gen = "Male"

Else

gen = "Female"

End If

rec.Open "select uemail,umobile from rs_usr where uemail='" & ema & "' or umobile='" & mob &
"'", con, adOpenDynamic, adLockOptimistic

rcnt = rec.RecordCount

rec.Close

con.Close

If rcnt = 0 Then

connectdb

rec.Open "insert into


rs_usr(ufname,ulname,ugender,udob,uemail,upwd,umobile,ustate,ucity,uaddr,ustatus)values('" &
fnam & "','" & lnam & "','" & gen & "','" & dob & "','" & ema & "','" & pw & "','" & mob & "','" & stat
& "','" & cit & "','" & adr & "','" & ustatus & "')", con, adOpenDynamic, adLockOptimistic

If rec.State = 1 Then

MsgBox "Registration not Done", vbOKOnly + vbCritical, "Error"

Else

MsgBox "User Registration Done successfully", vbOKOnly + vbInformation, "Done"

32 E-PROPERTY
clr

End If

Else

MsgBox "User Info Exist", vbOKOnly + vbExclamation, "Error"

End If

adusrexit:

Exit Sub

adusr:

MsgBox "Close the window and try again", vbOKOnly + vbCritical, "Error"

Resume adusrexit

End Sub

Private Sub Command2_Click()

clr

End Sub

Private Sub Form_Load()

Dim ap, src, nwpath As String

Dim oPic As StdPicture

Me.AutoRedraw = True

src = "/Images/bg2.jpg"

ap = App.Path

nwpath = ap + src

33 E-PROPERTY
Set oPic = LoadPicture(nwpath)

PaintPicture oPic, 0, 0, Me.ScaleWidth, Me.ScaleHeight

Set oPic = Nothing

Me.Visible = True

Text1.SetFocus

recn

connectdb

Adodc1.Refresh

With Adodc1.Recordset

Do Until .EOF

Combo1.AddItem ![stname]

.MoveNext

Loop

End With

End Sub

Private Sub Image1_Click()

Unload Me

End Sub

Sub clr()

Text1.Text = ""

Text2.Text = ""

34 E-PROPERTY
Text3.Text = ""

Text4.Text = ""

Text5.Text = ""

Text6.Text = ""

Combo1.Text = ""

Combo2.Text = ""

DTPicker1.Value = Now

Option1.Value = False

Option2.Value = False

End Sub

35 E-PROPERTY
SCREEN SHOTS

HOME SCREEN

36 E-PROPERTY
ADMIN HOME:

37 E-PROPERTY
ADD STATES:

ADD CITIES:

38 E-PROPERTY
ADD CATEGORY:

CUSTOMER DETAILS:

39 E-PROPERTY
NEW USER REGISTRATION:

CUSTOMER LOGIN:

40 E-PROPERTY
WELCOME:

CHANGE PASSWORD:

41 E-PROPERTY
NEW USERS FOR APPROVAL:

NEW PROPERTIES FOR APPROVAL:

42 E-PROPERTY
PROPERTY DETAILS FOR SELLING:

MY SELLING LIST:

43 E-PROPERTY
SEARCH PROPERTIES:

44 E-PROPERTY
SYSTEM TESTING
The purpose of testing is to discover errors. Testing is the process of trying to
discover every conceivable fault or weakness in a work product. It provides a way to check
the functionality of components, sub assemblies, assemblies and/or a finished product It is the
process of exercising software with the intent of ensuring that the

Software system meets its requirements and user expectations and does not fail in an
unacceptable manner. There are various types of test. Each test type addresses a specific
testing requirement.

TYPES OF TESTS
Unit testing
Unit testing involves the design of test cases that validate that the internal program
logic is functioning properly, and that program inputs produce valid outputs. All decision
branches and internal code flow should be validated. It is the testing of individual software
units of the application .it is done after the completion of an individual unit before
integration. This is a structural testing, that relies on knowledge of its construction and is
invasive. Unit tests perform basic tests at component level and test a specific business
process, application, and/or system configuration. Unit tests ensure that each unique path of a
business process performs accurately to the documented specifications and contains clearly
defined inputs and expected results.

Integration testing

Integration tests are designed to test integrated software components to determine if


they actually run as one program. Testing is event driven and is more concerned with the
basic outcome of screens or fields. Integration tests demonstrate that although the
components were individually satisfaction, as shown by successfully unit testing, the

45 E-PROPERTY
combination of components is correct and consistent. Integration testing is specifically aimed
at exposing the problems that arise from the combination of components.

Functional test
Functional tests provide systematic demonstrations that functions tested are available as
specified by the business and technical requirements, system documentation, and user
manuals.

Functional testing is centered on the following items:

Valid Input : identified classes of valid input must be accepted.

Invalid Input : identified classes of invalid input must be rejected.

Functions : identified functions must be exercised.

Output : identified classes of application outputs must be exercised.

Systems/Procedures: interfacing systems or procedures must be invoked.

Organization and preparation of functional tests is focused on requirements, key functions,


or special test cases. In addition, systematic coverage pertaining to identify Business process
flows; data fields, predefined processes, and successive processes must be considered for
testing. Before functional testing is complete, additional tests are identified and the effective
value of current tests is determined.

System Test
System testing ensures that the entire integrated software system meets requirements. It
tests a configuration to ensure known and predictable results. An example of system testing is
the configuration oriented system integration test. System testing is based on process
descriptions and flows, emphasizing pre-driven process links and integration points.

White Box Testing

46 E-PROPERTY
White Box Testing is a testing in which in which the software tester has knowledge of
the inner workings, structure and language of the software, or at least its purpose. It is
purpose. It is used to test areas that cannot be reached from a black box level.

Black Box Testing


Black Box Testing is testing the software without any knowledge of the inner workings,
structure or language of the module being tested. Black box tests, as most other kinds of tests,
must be written from a definitive source document, such as specification or requirements
document, such as specification or requirements document. It is a testing in which the
software under test is treated, as a black box .you cannot see into it. The test provides
inputs and responds to outputs without considering how the software works

Unit Testing:

Unit testing is usually conducted as part of a combined code and unit test phase of the
software lifecycle, although it is not uncommon for coding and unit testing to be conducted as
two distinct phases.

Test strategy and approach


Field testing will be performed manually and functional tests will be written in detail.

Test objectives
All field entries must work properly.
Pages must be activated from the identified link.
The entry screen, messages and responses must not be delayed.

Features to be tested
Verify that the entries are of the correct format
No duplicate entries should be allowed
All links should take the user to the correct page.

47 E-PROPERTY
Integration Testing

Software integration testing is the incremental integration testing of two or more


integrated software components on a single platform to produce failures caused by interface
defects.

The task of the integration test is to check that components or software applications,
e.g. components in a software system or one step up software applications at the company
level interact without error.

Test Results: All the test cases mentioned above passed successfully. No defects
encountered.

Acceptance Testing

User Acceptance Testing is a critical phase of any project and requires significant
participation by the end user. It also ensures that the system meets the functional
requirements.

Test Results: All the test cases mentioned above passed successfully. No defects
encountered.

PROJECT TESTING

Testing is the most important phases in the software development activity. In software
development life cycle (SDLC), the main aim of the testing process in the quality, the developed software
is tested against attaining the required functionality and performance.

48 E-PROPERTY
During the testing process the software is worked with some particular test case and

the output of the test cases are analyzed whether the software is working according to the

expectations or not.

The success of the testing process in determining the error is mostly depends upon the test case
criteria, for testing any software we need to have a description of the expected behavior of the system and
method of determining whether the observed behavior confirmed to the expected behavior.

LEVEL OF TESTING

Since the error in the software can be injured at any stage. so, we have carry out the testing
process at different levels during the development. The basic levels of testing are

Unit Testing
Integration Testing
System Testing
Acceptance Testing.
The Unit Testing is carried out on coding.here different modules are tested against the
specification produced during design for the modules .In case of integration testing different
tested are combined into sub system and tested in case of the System testing the full software is
tested and in the next level of testing the system is tested with user requirement document
prepared.

UNIT TESTING

Unit testing mainly focused first in the smallest and low level modules, proceeding one at a
time. Bottom-up testing was performed on each module. As developing a driver program, the
test modules by developed or used. But for the purpose of testing modules themselves were used
as stubs, to print verification of the actions performed. After the lower level modules were tested,
the modules that the next higher level those make use of the lower modules were tested

Each module was tested against required functionality and test cases were developed to test
boundary values.

49 E-PROPERTY
The unit testing has been tested with sample data and adequate corrections were made as per the
user requirement, such that login module was tested with user id and code and appropriate error
messages are provided for errors like data entry error, id error,etc.

INTEGRATION TESTING

Integration testing is a systematic technique for constructing the program structure, while
at the same time conducting tests to uncover error associated with interfacing. As the system
consists of the number the edges of the two modules. The software tested under this incremental
bottom-up approach.

Bottom-up approach integration strategy was implemented with the following steps.

Low modules were combined into clusters that perform specific software sub function
The clusters were tested

TESTING PROCESS

A number of activities must be performed for testing software. Testing start with test plan.
Test plan identifies all testing related activities that need to be performed along with the schedule
and guide lines for testing. The plan also specified the levels of testing that need to be done, by
identifying the different testing units. For each unit specified in the plan first the test cases and
reports are produced. These report are analyzed.

TEST PLAN

Test plan is a general document for entire project, which defines the scope, approach to be
taken and the personal responsible for different activities of testing. The inputs for forming test
plan are

Project Plan
Requirements Document System Design

50 E-PROPERTY
There are two basic approaches for testing. They are:-

Functional Testing
Structural Testing

SYSTEM TESTING

Series of different tests whose primary purpose is to fully exercise the computer-based
system. It also tested to find discrepancies between the system and its original objective,
current specifications.10011

EXECUTION TESTING

This program was successfully loaded and executed. Due to programming there
were no execution errors as fall as possible

QUALITY ASSURANCE

Quality assurance defines the objectives of a project and reviews the overall
activities so that error are corrected early in the development process.

LEVELS OF QUALITY ASSURANCE

Quality Assurance comes in three main levels namely

Testing
Validation
Certification

51 E-PROPERTY
TESTING

In system testing a common view is to eliminate program errors. This is


extremely difficult and time consuming. Since designers cannot prove 100% accuracy. A
successful test, then, is one that find errors.

VALIDATION:

It checks the quality of the software in both simulated and live environments. In the
Simulated approach the developers test the product on their workplace to make the products
meet its requirements. In the Live Environment phase the product is given to the customer to
evaluate the products functionality.

Validation refers to the different set of activities that ensure that software correctly
implements a specific function and the software that been built is traceable to customer
requirements. Verification and validation can be defined in a way like:

Verification
Validation
Software validation is achieved through a series of black-box test that demonstrate
conformity with requirement. After each validation check a test has been conducted, one of
the two possible condition exists

The function or performance characteristics conform to specification and are expected


A deviation from specification is uncovered and a deficiency list is created

ALPHA AND BETA TESTING

The alpha testing is conducted at the developers site by the customer. the software is
used in the natural setting with the developerlooking over the developer and recording
errors and usages problems. Alpha test is conducted in controlled environment

The beta testing is conducted at one or more customer site by the end user of the
software. Unlike software testing the developer is generally not present. Therefore beta test is
live application of the software in an environment that cannot be controlled by the developer

52 E-PROPERTY
VALIDATION CHECK APPLIED IN THE PROJECT

The files entered in the project must only have the doc extension
The data entered must have only one format
One should not make a enter into without checking the password
The qc must enter into the status column only accepted or not accepted
File which are already be registered should not be registered once again or other
time
Qc cant enter the file which are not entered by the dc
Qc should enter the file into corresponding filenames registered by the dc
Files which are registered and not accepted for the first time should not be
registered again but the reentry of date and status should be done only

CERTIFICATION
Certification is to certify that the program or software package is correct and confirms
to standards. With growing trend towards purchasing ready to use software, certification has
become more important.

System Security
Software integrity has become increasingly important in the age of hackers and
firewalls. This attributes measures a system ability to withstand attacks (both accidental and
intentional) to its security. Attacks can be made on all three components of software program,
data, and documents

To measure integrity, two additional attributes must be defined

o Thread
o Security

53 E-PROPERTY
THREAD

Threat is the probability (which can be derived or estimated from empirical evidence)
that an attack of specific type occur with in a specific time.

SECURITY

Security is the probability (which can be estimated or derived from empirical evidence)
that attack on the specific type will be repelled.

SECURITY TESTING

Any computer based system that manages sensitive information or causes action that
can improperly harm(or benefit) individuals is the target for improper or illegal penetration.
Penetration spans a board range of activities; hackers who penetrate system for sport;
disgruntled employee who attempt to penetrate for revenge; dishonest individual who
penetrate for illicit personnel gains

Security testing to verify that protection mechanism built into a system will in fact
provide proper protection form improper penetration. During system testing, the tester plays
the role of the individual who desires to penetrate the system. Anything goes! The tester may
attempt to acquire password through external clerical means; may attack the system with
custom software designed to break down any defenses that have been constructed may
overwhelm the system thereby denying the service to other; may purposely cause system
errors.

54 E-PROPERTY
TABLE DESIGN STRUCTURE
Database Name: restate

Rs_admin
id Number, primary key
Uname Varchar2(100)
Pwd Varchar(200)

Rs_budget
bid Number, primary key
budget Varchar2(50)

Rs_category
ctid Number, primary key
Ctname Varchar2(100)

Rs_cities
Cid Number, primary key
Cname Varchar2(30)
Sname Varchar2(30)

Rs_meet
Mid Number, primary key
Pid Varchar2(30)
by_name Varchar2(30)
by_mob Varchar2(30)
by_ema Varchar2(40)
Sell_name Varchar2(30)
Sell_mob Varchar2(30)
Sell_ema Varchar2(40)
Updtdon Varchar2(50)

55 E-PROPERTY
Rs_property
Pid Number, primary key
Sid Number
Sname Varchar2(50)
Smobile Varchar2(30)
semail Varchar2(50)
Ptype Varchar2(50)
Pcity Varchar2(50)
Parea Varchar2(50)
Psqrfeet Varchar2(50)
Pbudget Varchar2(50)
Paddr Varchar2(200)
Pabout Varchar2(500)
Ppost Varchar2(50)
Ppic Varchar2(100)
Pstatus Varchar2(30)
Psold Varchar2(30)

Rs_states
stid Number, primary key
stname Varchar2(30)

Rs_usr
Uuid Number, primary key
Ufname Varchar2(30)
Ulname Varchar2(30)
Ugender Varchar2(10)
udob Varchar2(30)
Uemail Varchar2(30)
Upwd Varchar2(100)
Umobile Number
Ustate Varchar2(30)
Ucity Varchar2(30)
Uaddr Varchar2(200)
Ustatus Varchar2(10)

56 E-PROPERTY
IMPLEMENTATION

Implementation is used here to mean the process of converting a new or revised


system design into operational one; conversion is one aspect of implementation. the other
aspect is post implementation review and software and maintenance

There are three type of implementation:

Implementation of a computer system


Implementation of new computer system
Implementation of a modified application

IMPLEMENTATION OF THE COMPUTER SYSTEM

Its should be replace a manual system the problems encountered are converting files,
training users creating accurate files, and verifying printouts for integrity

IMPLEMENTATION OF NEW COMPUTER SYSTEM

Its should be replace an existing one this is usually a difficult conversion. if not
properly planned there can be many problems. Some large computer system have taken even
years to convert

IMPLEMENTATION OF A MODIFIED APPLICATION

Its should be replace an existing one using the same computer. This type of
conversion is relativity easy to handle, provided there are no major changes to the file

57 E-PROPERTY
MAINTENANCE
After the system has successfully implemented maintenance activity may require
continuous involvement of the developers. Provision must be made for environmental
changes, which may affect either the computer, or other parts of computer based system: such
activity is normally called maintenance. It includes both the improvement of system functions
and the correction of faults that arise during the operation of a system.

Maintenance activity may require the continuing involvement of a large proportion of


computer department resources. Maintenance works may arise due to two reasons.
Error that creep up during normal running.
Request for changes by the service providers. As part of the normal running of
the system when errors are found.

This maintenance work will help to ensure that the system works smoothly as
predicted in the open environment. Whenever a maintenance work arises, the work has to be
properly carried out with proper documentation. This is to avoid any form of changes in the
structure of the system.
For every maintenance work an amendment notification is to be issued. This notification will
have the required changes and also authenticated. On receipt of the amendment notification
the amendment log is prepared which records these courses of action that has been planned to
be taken. It also records the estimated and the actual completion of each of the activities.

58 E-PROPERTY
BIBLIOGRAPHY
Davis, Harold. Visual Basic 6 for Windows. Berkeley, CA: Peachpit Press, 2000.

Karve, Sandit. File Handling using VB6. 28 December 2007


<http://swik.net/SWiK/Dream.In.Code+Programming+Tutorials/File+Handling+in+Visual+
Basic+6+Part+1+-+Sequential+Files+in+Visual+Basic+Tutorials/bbv3x>.

Microsoft. MSDN Library. 1998.

Sandvig, Chris. ASCII Character Codes for VBScript and VB.NET (ISO 8859-1). 8 January
2008 <http://yorktown.cbe.wwu.edu/sandvig/docs/ASCIICodes.aspx>.

NAME OF THE BOOK AUTHOR NAME

1. Visual Studio complete reference 6.0 Noel Jecke

2. Programming in Visual Basic Julie Case Bradley

3. Visual Basic 6.0 Wright Brothers

59 E-PROPERTY

You might also like