A Project Report on “india Hot Property ” r.d.e.c. Ghaziabad

8/14/2019 A Project Report on india Hot Property r.d.e.c. Ghaziabad

1/104

A

Project Report

On

INDIA HOT PROPERTY

R.D.E.C.Ghaziabad

Submitted By:

Arvind Kumar

M.B.A. Final

0823170008

1


2/104

Certificate

This is to certify that the Project entitled INDIA HOT PROPERTY a genuine work

done by Arvind Kumar student of R.D.E.C. Ghaziabad under my supervision and

guidance.

Mr . Atish KumarS/W Developer

(Logical Infopath Pvt. Ltd.)

.

1


3/104

Declaration

This is to certify that the project report titled INDIA HOT PROPERTYwhich I gave to LOGICAL INFOPATH PVT LTD requirementmanagements of marketing Program. This study is submitted for theapproval to the R.D.E.C. Ghaziabad .

I declare that the form and content of the

above mentioned project are original and have not been submitted in part or

full for any other degree or diploma of this or any other organization

Institute/ University.

Signature :

Name :Arvind Kumar

Enroll. No. : 0823170008

1


4/104

Acknowledgement

At the very outset we have the great pleasure in expressing our deep sense of gratitude torespected Prof. Kumar Siddhartha , H.O.D. M.B.A. Department, R.D.E.C. Ghaziabad,who gave us the opportunity to carry out this project.

The euphoria and happiness of successfully completing any task is incomplete without

thanking the people who have directly or indirectly helped us in preparation of this project.

We also have the great pleasure in expressing our vote of thanks to our respected

Director, Miss . Preeti Arora and Mr. Atish Kumar, S/W Developer of Logical

Infopath Pvt. Ltd. under whose able guidance, encouragement, deep personal interest

and supervision this work has taken its present shape.

1


5/104

Preface

www.indiahotproperties.com is Indias largest Real Estate website,visited by thousands of property buyers/sellers/lessors everyday.Advertising your projects, properties and services onindiaproperties.com offers you tremendous mileage.Indiahotproperties is open to innovative advertising concepts for thatextra brand visibility and mileage.

Web site comprises following modules: Administration Module User Module Advertisement Module Search Module Sell/Lease Out module

Purchase/Rent Module Member & Agent Module Property Tools Module City Description Module Database Design

This websi te i s developed to faci l ita te and manage the variouspeoples to search for their Propert ies .This web si te is developedin ASP.Net, MsSql Server 2000 and Java Script for designing. Wealso use HTML, DHTML and XML.

First part of report gives all information about the project, about thecompany under which we developed.

Second part of the report over the problem Definition, Methodologywe have used and System Requirements.

2


6/104

Third part covers the Design of the system, main functions, howdata is f lowing between different modules, Relat ion ship betweendifferent entities, database used.

Fourth part of the report describes the project plan assumption we

have made.Fifth part covers the Screen shots of the project

In Sixth part describes the coding standards and conventions used.

1


7/104

Executive Synopsis

www.indiahotproperties.com is Indias largest Real Estate website,visited by thousands of property buyers/sellers/lessors everyday.Advertising your projects, properties and services onindiaproperties.com offers you tremendous mileage.Indiahotproperties is open to innovative advertising concepts for thatextra brand visibility and mileage.

2


8/104

About Company:

Logical Infopath Pvt Ltd Delhi

Our capability of addressing technologies like .Net, j2EE, and AutomatedTesting tools, with varied domain expertise leads to on time and withinbudget completion of software development projects.

2


9/104

Problem Definition&

Description

Statement about the Problem

2


10/104

Till date searching the property were done by the persons own self from the

property Dealer or through Internet sites there was a limitation of matching

choice of your property but these sites takes much time in searching and

purchasing a property. In both the cases the time was very essential. So to

solving this problem a stock of problems can be listed in the existing system.

After gaining an in-depth knowledge to the various processes and the manner in

which they are carried out, it was realized that these were not only tedious and

cumbersome but also error prone. These bottlenecks are featured in

consideration with the overall aspects of the present functioning system.

Following are the problems in the existing system:

Increased time taken by personnel. It is very

1


11/104

TimeConsideration

tedious job to find a proper material as per your

choice and for the other. At the time of searching property all the records

have to be scanned and even after the people

cant be sure that they will be able to find a

proper property . In addition, owner wants to update their records

each time a deletion or addition. And the transactions of payments with the client

also take a lot of time.

CostConsideration

A large number of peoples are involved to

maintain the whole system that is very

expensive. The cost also increases to the buyer with the

increasing of shop maintenance.

1


12/104

Other diverseproblems

A large number of manpower is involved to

maintain the whole system, which is very

expensive and cumbersome. Unreliable and inefficient data entry. Lesser user friendly. Redundant data storage. Use of a lot registers for maintain records.

1


13/104

HardwareHardware

&&

Software RequirementSoftware Requirement

Hardware Requirements:

Server

Processor : Pentium 3,500 MHz (or above).

1


14/104

RAM : 128 MB (or above).

HDD : 20 GB (or Above).

Client

Processor : Celeron 500 MHz or above, Pentium 2,350 MHz or above.

RAM : 64 MB (or Above).

HDD : 10 GB (or Above).

Proprietary Software: Microsoft Visual Studio .NET

SQL Server 2000

Windows Server 2000 / Windows XP with Service Pack 2

Internet Information Server

2


15/104

Web-Browser: Internet Explorer 4 or Netscape 4x or upwards

2


16/104

ScopeScope

&&Objective of ProjectObjective of Project

Scope

The system is highly flexible one and is well efficient to make easy interactionswith the client. The key focus is given on data security, as the project is onlineand will be transferred in network. The speed and accuracy will be maintainedin a proper way.

This will be a user-friendly one and can successfully overcome strict and severevalidation checks. The system will be a flexible one and changes whenever canbe made easy. Using the facility and flexibility in .NET and SQL, the softwarecan be developed in a neat and simple manner there by reducing the operator'swork.

2


17/104

Since the project is developed in ASP.NET as a front-end and SQL as a back-end it can be modified easily and used for a long period.

Through this project I have tried to automate the task of: Category of property Features of property Details Of Property Price Details Special Offer List for Registered Users Property detail by Messaging Available Properties Information Member Management Member Id is generated automatically from the table by auto

generation Entering the details like Primary Information, Religious Background

Educational & Professional Information, Contact Information, and

Other Information. Checking Password and Confirm Password

Add Banners and Property Images Save time of Search Give a modification power to sites owner at any label. So,

Administrator of site can make any changes such like can add a new

property, Features and Property Details on the working windows. Administrator can also change the Banner and also can change the list

of special offer property.

1


18/104

Objective

TimeEffective and

Cost

Property site is available to anybody and anywhere.

This saves a lot of time of the customer and in a very

little time span the registered user may look the whats

a offer on the special products purchasing. This plancost offered is economic too.

1


19/104

DatabaseCreation

A database of the registered users will be created and

this will help the users to fetch the details of recent

property as per requirements. There is a separate

database for administrator for updating the site.

MobilityInternet is available to everybody anywhere anytime

here, this makes the site highly mobile.

Informative

The site has all the necessary details about the

concerned property and materials hence, provide all the

relevant information therefore. For example, searching

of appropriate property has done, then the information

of purchasing is provided to registered users by mailing.

WideApproach

Any person can visit it. User can register with or without

photographs. Therefore it has a wide range of users.

Security

Proper authorization and authentication provisions have

been made for the security of the site so that only the

registered users can look the special offer details.

Without proper login no one is allowed to access the

special offer list of this site.

Flexible

The site is flexible to any expansion or contraction in thefuture. For example: Magazines section can be added,

sending, telegrams can be included etc.

1


20/104

SYSTEM ANALYSISSYSTEM ANALYSIS

ANALYSIS OF PROPOSED SYSTEM:

Indiahotproperties web site is a distributedproject. Projects can be categorized in twoways:-

1. Local area network Projects

2. Distributed projects

Local area Network projects are thoseprojects where application has to be incooperated in the Local area network of the client i.e. with in its premises only. InLAN cases, server is not remotely locatedand client access this application through

2


21/104

this network. Here the question of platformindependence does not arise and we usetechnologies like: Visual Basic, Fox pro,D2K or C, C++.

But Distributed projects are those projectswhere application is remotely situated. Inthese kind of projects application isremotely situated on to the remote server from where client machine connects to theremote server and application isdownloaded on to client machine. Here thequestion of platform independence arisesand we use technologies like ASP.NET.

Data Gathering:This project is a Business to Consumer and is a well-commercial site of propertywhich serves Indians and others, with avariety of property.

Business system Elements:

2


22/104

ObjectivesConstraintsControlsInputProcessingOutputFeed Back

1. Objective: The system analyst must be

aware of exactly what the user requiresroom a specific system. That ismanagement goals or objectives mustbe fully understood.

1


23/104

2. Constraints: The analyst and the user must both recognize any limitations or constraints that may be imposed whenthe analyst is designing a computerizedsystem. Some types are:

Legal constraints Budgetary Constraints Equipment Constraints

3. Controls: The user must familiarize theanalyst with the ways in which errorsare minimized under the current system.

4. Input: All input data that server as their basis for, desired output must bestudied where all data used for processing originates. How often iseach type of input generate? If there are

code or abbreviations used for inputdoes the analyst have complete list of these. What happens to inputdocuments after has been processed?

2


24/104

5. Processing: The analyst must thenanalyze the processing or type of operations that are currently performedin order to achieve the desired results.

Feasibility Study

A feasibility study is conducted top select

the best system that meets performancerequirement. The key consideration infeasibility analysis is:

1. Economic Feasibility

2. Technical Feasibility

Economic Feasibility:

The proposed system is economicallyfeasible because the cost involved inpurchasing that hardware and the softwareare within approachable. The personal costlike salaries of employees hired are also

nominal, because working in this systemneed not required a highly qualifiedprofessional .The operating environment

2


25/104

costs are marginal .The less time involvedalso helped in its economical feasibility.

Technical Feasibility:

Hardwares used in this project are p3processor 733 MHz, 64 MB RAMS, 10 GBhard disk, floppy drive. These hard wareswere already available on the existingcomputer system. The software like MS-

ACCESS, VB, MS-WORD and operatingsystem used were already installed on theexisting. So no additional hardware andsoftware were required to purchase and itis technically feasible.

Tools Used:1. HTML, DHTML

2. Java Script

3. SQL SERVER-2000

4. ASP.Net

Promotion of the site:Site will be promoted through variousmeans:

2


26/104

1. Through personal approach bymarketing division.

2. Through telemarketing.

3. Through advertisement such like variousnewspapers etc.

4. Through web Marketing.

Methodology

System:

A system is the combination of people,devices, and methods interrelated inworking towards a common goal.

Information system:

An information system is a computer based

business, system that provides the dataprocessing capabilities information that anorganization needs to be informed aboutvarious aspects of its operation, are-

1. Value useful system & Provide accurateinformation

2. Provide timely information & Be capableof communicating that information to thepeople in the company who need it.

1


27/104

Software RequirementSpecification

Software Requirement Specification:

Purpose:

2


28/104

indiahotproperties is a well-knowncompany serving Indians and others, witha variety of properties that represent theproperty include Residential Flat, Land,Hotel, Shopping Complex.

User friendliness:

This project will have user-friendlyscreens. The screens designed will have

very simple functionality for retrieving/adding/ updating the in information.

Consistency:

The consistency in the proposed systemwill provide high efficiency due to smaller learning curves and increased dataintegrity.Compatibility:

This project offers great compatibility, as itwill be designed with proper methodology,new tools and technology

Security:This project is a secured system, which willprovide corporate level security. Only theauthorized people will be able to access

1


29/104

critical information. Also that will enable auser to view /edit/ add the information,based on roles and privilege assigned tothat user.

Reliability & Robustness:

This project is built with proper architecture and design and it will providea reliable and robust application to the

users.Performance:

The performance of this application will behigh because of its optimize design andsound architecture.

Extensibility:

This project has a modular design andwould provide the f lexibil ity of adding,future modules to the application

Flexibility:

This project has the flexibility of adding

new modules when needed.Methodology

One can perform cost estimation at anypoint in the software lifecycle. As the cost

2


30/104

of the project depends on the nature andcharacteristics of the project, at any point,the accuracy of the estimate will dependon the amount of reliable information wehave about the final product. Clearly whenthe product is delivered the cost can beaccurately determined, as all the dataabout the project and the resources spentcan be fully known by then. This is costestimation with complete knowledge aboutthe project. On the other extreme is thepoint when the project is being initiated or during the feasibility study. At this time wehave only some idea of the classes of datathe system will get and produce the major functionality of the system. There is agreat deal of uncertainty about the actualspecification of the system.

An estimation model for computer softwareuses empirically derived formulas to

predict effort as a function of LOC or FP isestimated. The empirical data that supportmost estimation models are derived from alimited sample of projects. For this noestimation model is appropriate for all

2


31/104

classes of software and in all developmentenvironment. The result obtained fromsuch models must be used judiciously.

The Structure of Estimation Models

A typical estimation model is derived usingregression analysis on data collected from

past software projects. The overallstructure of such models takes the form

E= A + B*(eV)

Where A, B and C are empirically derivedconstants, E is effort in person month andeV is the estimation variable (either LOCor FP).

In addition to the relationship noted in theEquation, the majority of estimation modelshave some form of project adjustmentcomponent that enables E to be adjustedby other project characteristics likeproblem complexity, staff experience anddevelopment environment.

3


32/104

Such uncertainty represent a range of possible final products not one preciselydefined product. Hence, the costestimation based on this type of information cannot be accurate. Estimatesat this phase of the project can be off fromthe actual final cost.

THE WATERFALL MODEL

The reason for choosing the Waterfallmodel in our project is:

The waterfall model is simple and isconsidered to be the base model of

SDLC (Software Development LifeCycle)

A sequence of phases is followed inthe waterfall life cycle model, with theexit of one phase certifying the entryinto the next phase.

1


33/104

It also verifies that each phase is in-line with the next phase, andtraceability of the requirements ismaintained through the phases.

Phases of Waterfall Life Cycle Modelare:

Analysis and Design

Awareness can be increased about thedifferent schemes of shopping sites.General public interests can be generatedin the sites.

1

Requirement Analysis

DesignCoding /Developmen

t

UnitTesting

IntegrationTesting

SystemTesting


34/104

Better Productivity and comforts can beprovided by the system.

Customers will be able to check their queries with ease.

Users can able to perform Transactionslike:

Maintaining the details in master fileswhich can be easily updated

Keeping Transactions Like:

1. Adding Property Type

2. Adding Property Features

3. Adding property Details

4. Modifying Property5. Modifying property Features and Details

6. Adding Property rates, electricity Rates

7.City Description

8. Adding Banners

Preliminary InvestigationIn preliminary Investigation to check that isthere is any need of this type of systemand shall we survive without this system, is

1


35/104

the system is feasible for us etc. First of all, the need of the system is checked. If the system is developed shall it give anyrevenue to us?

2


36/104

Feasibility StudyFeasibility Study

3


37/104

Feasibility Study

There are three types of Feasibility study:

(1) Technical Feasibility(2) Economical Feasibility

(3) Operational Feasibility

Technical Feasibility

Meaning: Can the work for the project be

done with current equipment existingsoftware technology and availablepersonnel? If new technology is needed,what is the likelihood that it can bedeveloped?

Reply: In this project the work cannot be

done by the current system becausecurrently all the records, filling,transactions, entries, are done by manuals.It is really time consuming and margin of error is more.

Yes, the current available personnel candevelop this system but special trainingshould be given to those personnel toimprove their skills. Yes new technology or software, which is currently working in the

1


38/104

market, is to be needed to develop thissystem.

It can be developed easily with thissoftware and for a long term it is workingeffectively and margin of error is less.

To run this product the followingtechnological consideration has to be keptin mind by the Company.

SQL server as back-end is a good DBMSsoftware with long-standing track record inindustry for the good technical aspect ,extensibil ity, concurrency and supportneeded for this purpose.

SQL server2000 and Windows NToperating system are used while makingthis product. Language such as .NET isalso used while making this project.

SQL server can run on the differentwindows operating systems from Windows95 to windows 2000, Win NT, and Win 98.

Economical Feasibility

Meaning: Are there sufficient benefits increating the system to make the costs

2


39/104

acceptable? Or Are the costs of notcreating the system so great that it isadvisable to undertake the project.

This will include three major costs asdescribed below:-

Cost of Hardware and Software Cost of software to be acquired to build

and run the product is a one time cost. Buying a back end database is the

major part of hardware and softwarecost. Comparison between the Oracledatabase high cost and better featureswith the SQL server low cost and better support for the same vendor operatingsystem make this decision needoriented.

Benefits in reduced cost, error and Savingswill be made by reduction of presentsystem expenses, time saving andincreased accuracy.

2


40/104

Cost Avoidance

Future cost reduction in from of reductionin the number of administrative staff needed and manual records maintains inorganization.

Rise in cost will be avoided.

Operational Feasibility

Meaning: The system will be used if it isdeveloped well then be resistance fromusers that undermine the possibleapplication benefits.

Dealer Support :

Dealer and user support for presentsystem is there, as the current procedureused takes more time and effort thanproposed system.

No major training and new skills arerequired as it is based on DBMS model.

It will help in the time saving and fastprocessing and dispersal of user requestand applications.

2


41/104

New product will provide all the benefits of present system with better performancesuchlike Improved information, better management and collection of the reports.

User Support :

User involvement in the building of presentsystem is sought to keep in mind the user specific requirement and needs.

User will have control over there owninformation. Important information such aspay-slip can be generated at the click of abutton.

Faster and systematic processing of user applications will save user fromcumbersome process of filling forms andsubmitting them at different places andthen waiting for applications to beprocessed.

Old method used for application approval,allocation of IDs, payments, etc. used hadgreater chances of error due to wronginformation entered

1


42/104

StructureStructure DesigningDesigning

2


43/104

DATA FLOW DIAGRAM

A newer graphic for defining input, processesand outputs is the data flow diagram. Only afew symbol are used, as shown in figure andthese symbols may be located in a rather informal way.1. Data Transformation

2. Temporary Data Storage

3. Data Flow

DATA FLOW DIAGRAM OF MESSAGE

MODULE:Context Level DFD

1

Admin Index Details

Indiahotproperties Search Result Property


44/104

SearchResults

LEVEL ONE DFDDFD 1

Login

Property type, Features of property,city, Banner DFD 2

Details

DFD3

2

AdminAdding &ModifyingProperty Propertys

Detail

Index property Property

Features

Search

Submit theDetails


45/104

DFD In Structural DesigningThis is the first step in the structure designmethod. In our project, there are two inputfiles: file1 and file2 and two outputs arerequired: the merit list and the waiting list.A high level DFD for this is given. Thediagram is fairly clear. First we receive theapplication forms. Then with the help of input file1 and file2 we check for thevalidation of forms, if correct then storethem in temporary database else they arerejected and send the rejection letter. Therecord from First level factoring: The first-level structure chart can easily be obtainedand is shown in f igure. In the structurechart, instead of having one output modulefor each of the three outputs, as is shownin the data flow diagram, we have only oneoutput module, which then invokes threeoutput modules for the different outputs.

Factoring I/O modules:The output module does not need anyfactoring. According to the designmethodology, the input module which

1


46/104

validates the input will have on inputmodule to get the array of validated formsby referring to the other input files. Thisinput module can then be factored intoother input modules to get the validationdone. The input module will get data frominput file2 and validate the given forms thestructure chart is shown in the figure.

Design Analysis:

Here we list each major requirement andthen list the modules in the structure chartthat implements that requirement.

Analysis using information flow Metrics:

Based on the structure chart the design of the system was first specified completely:This required formally specifying the datastructure and all the modules. For eachmodule we specified the purpose of themodule, its interface, the modules itinvokes, and the estimated size of themodule (in LOC). This formed the firstversion of the design document. The firstthing that could be noted was that when

2


47/104

specifying a complete design from thestructure chart the design usually expands.

We can develop the code for the givenproject using the sketched design in any of the languages which fit into the softwarerequirements.

Configuration Control Plan

In this project, we will only haveconfiguration control for the code. Thedesign will not be under configurationmanagement. The requirements areassumed to be frozen; any change will benegotiated with the management.

The configuration control board (CCB) willconsist only of the group leader. A modulewill be taken for configurationmanagement, only after it has beensuccessfully unit tested and its unit test

2


48/104

results have been approved by the groupleader. Change requests will be made tothe CCB through electronic mail, and therequester will have to justify the request.Request changes will generally be allowedif the change does not change theinterface of the module, and the project isnot behind the schedule. Changes that willmodify the module interface or affect other programmers will, in general, not beapproved unless there are good reasonsfor doing so. In this case, all the concernedparties will informed of the change throughelectronic mail.

Quality Assurance Plans

To ensure quality, the following documents(besides this plan and the requirementsdocument) will be produced during thedevelopment:

" System design document" Code

" Unit test plan

2


49/104

" System test reports

The following methods will be used for quality control:

" Preliminary design review

" Unit testing

" System test plan review

" System testing

It is felt that because the system is small,a detailed incremental testing is notneeded. A two-level testing is used: unittesting followed by system testing. Thesystem test plan, however, will bereviewed before the testing is performed.

No code review will be done.

Monitoring Plans

Three basic methods will be used for project monitoring - project logs, biweeklymeetings and reviews. Because we do not

have a time sheet processing system, eachproject member will keep a multipurposelog in which he will record the differentactivities he performs and the date and

2


50/104

duration of the activity. The failure anderror data obtained during testing will alsobe recorded in the log.

Cross checking of the log data can bedone by those events in which more thanone person of the team participated. Theformat of the log entries is:

Date

Time

Time

Time Activity

Comments

From

To InMinutes

Type

Activity type is one of the following:requirement understanding, design(system or detailed), coding, testing, reportwriting, meeting, debugging (includingcorrecting errors), and others. In the

comment f ield, the errors encounteredduring testing have to be recorded.

Reviews to be held are defined earlier. Inaddition to reviews, a biweekly meeting will

1


51/104

be held to discuss the progress of theproject.

Risk Management

The project has no major hazardsassociated with it. The only risks it has arethe cost and schedule risks. Althoughanalysis can easily be done regarding the

schedule risks involved, it is felt thatbecause the team has one part-timemember (who is largely under-used)schedule slippage can be easily handled.Similarly, because the costs are low in thissmall project, it is felt that an analysis of

the cost risk is unnecessary.

FLOW CHART

2


52/104

Checking DetailsEnter theDetails DetailsOut put

1

StartIndexAcceptAcceptthe

Details

Proc essingStop


53/104

Start

Login in with password & user nameMake RegistrationSearch the propertyLogoutSelect mode of

paymentMake Transactions

NAVIGATIONAL FLOW CHART

It would be helpful if you could provide us

with a navigational flow chart for your website. This is very much in the format of a family tree with your home page at thetop of the tree/chart with branches/links toall other pages and then sub pages

1

New user NoFlat No


54/104

User name

Sear ch

AddingFeatures

Modifying thedetailsAddingdetails

E-R DIAGRAM

1

UsersLoginValid User Password

PerformTransactionsAddingProperty


55/104

2


56/104

System TestingSystem Testing

&&ValidationValidation

1


57/104

High Level System DesigningThe purpose of this phase will be to design theoverall functioning of the proposed system andfinalize the input and output formats. Theadministrator and the projects teams shouldpresent the document of functionalspecifications in a language that can beunderstood. The client must approve thedesign, and the project team should then beable to move on to the subsequent phases

1


58/104

1

. NET FRONT ENDCONTAINS

User AdminSearch

DATA BASE IndiahotpropertiesProcess InputText File

Input Text File


59/104

Objective of System Testing Testing is vital to the success of any system,Testing is done at different stages within thedevelopment phase. System testing makes alogical assumption that if all parts of the systemare correct, the goals will be achievedsuccessfully, inadequate tests or no testingleads to errors that may come up after whencorrection would be extremely difficult. Another objective of testing is its utility as a user-oriented vehicle before implementation.

UnitTesting

Each module will be tested

individually so as to make the

individual component error free.

Also other attached modules will

also be error free.IntegrationTesting

Each module will be tested of its

effect on other modules by

integrating the modules. This will

remove further errors from the

system and may also result in

some changes in the individual;

1


60/104


61/104

close examinations of

procedural details. Providing

test cases that exercise specificsets of condition or loops tests

logical paths through the

software.

Black BoxTesting

This Testing method focuses

on the functional requirementsof the proposed software.

ConditionTesting

It is a test case design method

that exercise the logical

conditions contained in a

program module.

Data flowTesting

This method selects paths of a

program according to the

locations of definitions and

uses of variables in the

program.

1


62/104

The testing of the system was done on bothartificial and live data. The following types of tests are performed.

Unit TestingThis testing focuses verification on the module.Using procedural design description as aGuide; important control paths are tested touncover errors with in the boundaries of themodule. The relative complexity of tests anduncovered errors is limited by the constraintsscope established for unit testing. The unittesting can be conducted in parallel for severalmodules.

Integration TestingGenerally a combined approach known assandwich testing using features of top downtesting strategy for upper levels of the programstructure, coupled with the bottom up strategyfor subordinate modules.Functional testing

This is done for each module/sub module of thesystem. Functional testing serves as a meansof validating weather the functionality of thesystem confirms the original user requirementi.e. done the module do what is supposed to

1


63/104

do. The separate schedules were made for functional testing .it involves preparation of bugs listing for non-conformities.

System TestingSystem testing is done when the entire systemhas been fully integrated. The purpose of thesystem testing is to test how the differentmodules interact with each other and whether

the system provides the functionality that wasexpected.It consists of the following steps.1. Program Testing2. String Testing3. System Testing

4. System Documentation5. User Acceptance TestingValidations and verificationsTesting Testing presents an interesting anomaly for thesoftware engineer. During earlier softwareengineering activities, the engineer attempts tobuild software from an abstract concept to atangible product. Now comes testing. Theengineer creates a series of test cases that areintended to demolish the software that has

2


64/104

been built. In fact, testing is the one step in thesoftware process that could be viewed(psychologically, at least) as destructive rather

than constructive.Software engineers are by their natureconstructive people. Testing requires that thedeveloper discard preconceived notions of thecorrectness of software just developed andovercome a conflict of interest that occurs whenerrors are uncovered.If testing is conducted successfully (accordingto the objectives stated previously), it willuncover errors in the software. As a secondarybenefit, testing demonstrates that softwarefunctions appear to be working according tospecification, that behavioral and performance

requirements appear to have been met. Inaddition, data collected as testing is conductedprovide a good indication of software reliabilityand some indication of software quality as awhole. But testing cannot show the absence of errors and defects, it can show only thatsoftware errors and defects are present. It is

important to keep this (rather gloomy)statement in mind as testing is beingconducted.Testing principles:

2


65/104

Before applying methods to design effectivetest cases, a software engineer mustunderstand the basic principle that guide

software testing.All tests should be traceable to customer requirements.Tests should be planned long before testingbegins.80 percent of all errors uncovered during

testing will likely be traceable to 20 percent of all program components. The problem, of course, is to isolate these suspect componentsand to thoroughly test them.Testing should being in the small andprogress toward testing in the large.Exhaustive testing is not possible.To be most effective an independent third partyshould conduct testing.A rich variety of test case design methods haveevolved for software. These methods providethe developer with a systematic approach totesting. More important, methods provide a

mechanism that can help to ensure thecompleteness of tests and provide the highestlikelihood for uncovering errors in software.Any engineered product (and most other things)can be tested in one of two ways.

1


66/104

(1) Knowing the specified function that aproduct has been designed to perform, testscan be conducted that demonstrate each

function is fully operational while at the sametime searching for errors in each function.(2) Knowing the internal working of a product,tests can be conducted to ensure that all gearsmesh, that is, internal operations areperformed according to specifications and allinternal components have been adequatelyexercised. The first test approach is calledblack box testing and the second, white-boxtesting.White box testing, sometimes called glass-boxtesting is a test case design method that usesthe control structure of the procedural design to

derive test cases. Using white-box testingmethods, the software engineer can derive testcases that(1) Guarantee that all independent paths withina module have been exercised at least once,(2) Exercise all logical decisions on their trueand false sides,(3) Execute all loops at their boundaries andwithin their operational bounds, and(4) Exercise internal data structures to ensuretheir validity.

1


67/104

White-box testing of software is predicated onclose examination of procedural detail.

Providing test cases that exercise specific setsof conditions and/or loops tests logical pathsthrough the software. The status of theprogram may be examined at various points todetermine if the expected or asserted statuscorresponds to the actual status. Basis pathtesting is a white-box testing technique firstproposed by Tom McCabe. The basis pathmethod enables the test case designer toderive a logical complexity measure of aprocedural design and use this measure as aguide for defining a basis set of executionpaths. Test cases derived to exercise the basisset are guaranteed to execute every statementin the program at least one time during testing.Black box testing, also called behavioraltesting, focuses on the functional requirementsof the software. That is, black box testingenables the software engineer to derive sets of input conditions that will fully exercise all

functional requirements for a program. Blackbox testing is not an alternative to white-boxtechniques. Rather, it is a complementaryapproach that is likely to uncover a differentclass of error than white-box methods. When

1


68/104

computer software is considered, black boxtesting alludes to tests that are conducted atthe software interface. Although they are

designed to uncover errors, black-box tests areused to demonstrate that software functions areoperational, that input is properly accepted andoutput is correctly produced and that theintegrity of external information is maintained. Ablack-box test examines some fundamentalaspect of a system with a little regard for theinternal logical structure of the software. Blackbox testing attempts to find errors in thefollowing categories:(1) Incorrect or missing functions,(2) Interface errors,(3) Errors in data structures or external

database access,(4) Behavior or performance errors, and(5) Initialization and termination errors.By applying black-box techniques, we derive a

set of test cases that satisfy the followingcriteria:

(1)Test cases that reduce, by a count that isgreater than one, the number of additionaltest cases that must be designed to achievereasonable testing and

3


69/104

(2)Test cases that tell us something about thepresence or absence of classes of errors,rather than an error associated only with the

specific test at hand.White-box testing should not, however, bedismissed as impractical. A limited number of important logical paths can be selected andexercised. Important data structures can beprobed for validity. The attributes of both blackand white box testing can be combined toprovide an approach that validates the softwareinterface and selectively ensures that theinternal workings of the software are correct.

VALIDATION CHECKSThe major decisions of a validation stage areconcerned with handling errors and distributionof data. The data relevant to the system entersit through a set of validation procedures. Oftenthey are caused by a generalized inputvalidation package tailored for the needs of aparticular system.There are various ways of handling errors opento the designer that includes rejection of theitem of input or processing the next item, writingerror record and signaling the appropriatemessage to the user. Error procedures must

1


70/104

be specified in detail showing decisions, actionsand exceptions.In most of the cases where error occurs anerror message is popped to the user who issupposed to realize the fact and do thenecessary steps. The program developed ischecked thoroughly for errors by testing it withdata and the errors that are raised during thiscan be clarified. The program may halt duringan unpredictable error.

TestingTesting

&&

3


71/104

ImplementatioImplementationn

1


72/104

TESTING (TESTING TECHNIQUE SANDTESTING STRATEGIES) ANDIMPLEMENTATIONUnit testing of the modules is done so as tocheck that each of the modules works, as theyshould be. Following is the module wise testingof this project:

Test Case1:

Login FormValid User name and PasswordInput=Login Id, PasswordOutput: Corresponding Form ShowImplementation of Test Case:User Enters valid User name and Password(administrator, User). Login Values are mappedin database table to check login id andpassword is ok. If entry exits then Loginprocess will be successful.

Test Case 2:Wrong user Id and Password:Input: Wrong Login Id and Password:Output: Error Message generated

2


73/104


74/104

EVALUATIONIn evaluation we prepare the team to evaluatethe system. The review team prepares a formalreview plan around the objectives of the review,

the type of evaluation to be carried out and thetime schedule required. An overall plan coversthe following areas:

Administrative plan: Review area objectives,operating costs, actual operating performanceand benefits.Personnel requirements plan: Reviewperformance objectives and trainingperformance to data.Hardware plan: Review performancespecifications.

3


75/104

All plans have been done by taken proper careand seriousness and each module is evaluatedusing simulated data. This review not only

evaluated how well the current system isdesigned and implemented, but also is avaluable source of information that can beapplied to the next system project.Project Management PlanThis Project management Plan for theHelpdesk explains the following:

It provides an overview of the project interms of its purpose, what it covers & what itdelivers.

It provides an insight into the structure of theproject team & resources needed.

It also explains the software developmentlife cycle adopted for the project in terms of the phases, iterations, and work procedures.

The way project will be managed throughout itslife cycle, in terms of detailed phase wise plan,process of monitoring, control & process of riskmanagement. Also, the plan of supporting

activities required for project management ismentioned.PurposeThis plan details the strategy to administer,monitor and control the Helpdesk project. It is to

1


76/104

be used, along with project status reports, tomanage and track the project by the ProjectLeader and the Project Management Office.

ScopeThis version of PMP covers projectmanagement & software engineeringmethodology for the FG project.

2


77/104

ResponsibilitiesResponsibilitiesOf Of

Team MembersTeam Members

2


78/104

ResponsibilitiesProject Manager

Ensure adequate resources are available Facilitate required training for the team Review the plans, estimates and deliverable Participates on module end reviews Project Initiation and wind up. Ensure that the project follows the Quality

Management System. Represent the project status in meeting and

escalate any issues/risks o senior management.

Project Leader Customer interaction Developing and administering the projects

PMP Requirement Management Resolution of technical issues between

project team Provide Inputs and feedback to the Module

Leader on Technical and Non-Technicalissues Design Review Ensuring Timeliness and quality of all

deliverables1


79/104

Ensuring Projects Defined SoftwareProcess identified in PMP are followed

Status reporting to PM Review of test plans & test cases Plan and Participate in Review and Audits

Module Leader Technical assistance and guidance to the

team Design Backups Requirement Analysis Participation in Reviews and Audits Prepare Release Note. Integration of all developed units. Prepare installable & release to testing

team. Coding Code reviews Self Testing

Developers Coding

1


80/104

Code Review Self Testing Repair defects Peer Review Review of unit test cases.. Participate in Review & Audits

Configuration Controller (CC)For CC the responsibilities are defined how

tools will be used during project developmentTesting Engineer Develop Test Plan Develop Test Cases Conduct Testing Report Testing Result Tailoring Decisions

and Projects Defined Software Process

1


81/104

Projects DefinedProjects Defined

Life CycleLife CycleForForIndiahotpropertiesIndiahotproperties

1


82/104

Projects Defined Life Cycle (PDSP)

Our team will develop the software inaccordance with PDSP iterative lifecycle.Artifacts and evidence of results of softwaredevelopment activities will be managed andcontrolled as per Software ConfigurationManagement Plan and made available tosupport management reviews, metrics

calculations, quality audits, product evaluations,and preparation of product deliverables.Phases of Life cycleFour distinct phases are followed in the project,which are Inception, Elaboration, andConstruction & Transition. Which are indicatorsof the progress of the project.

1. Inception this phase brings to light anoriginal vision of a potential product, andtransform it into an actual project. Thefollowing important activities will be done inthis phase-

Feasibility Study of existing process. Collection of core projects requirement One or more prototype development

1


83/104

Initial Risk assessment and Initialproject management plan showingphase and iterations

Test planning Estimation Phase end reviews

2. Elaboration the main goal of this phase isto more thoroughly analyze the problemdomain, to define and stabilize the architecture,and address the highest risk element of theproject. The following important activities will bedone in this phase-

Detailed Project Management plan is

prepared. Most of the Critical project risks are

mitigated. Review of prototype by customer and

rework. Re-estimation Review of requirements and approval High Level Design Low Level Design Review of test plan

1


84/104

System Test cases identification. Phase end review

3. Construction in this phase theconstruction of product is made. The followingimportant activities will be done in this phase-

Coding of Modules Unit testing & Code review. The Software product integration on the

required platform. Re-estimation Close of open defects Peer Reviews of code Self testing by developers Phase end review

4. Transition in this phase the product is putin the hands of its end user. The importantactivities will be done in this phase are:

System testing to validate the new systemagainst user expectations

Training of users and maintainers.

Project windup activities. Each phase emphasizes on some keyaspects of the development essential for thepurpose of demonstrating progress on the

1


85/104

project. Each phase end is a key milestonewith defined goals, which is described in theProject plan section of this PMP.

IterationEach phase is broken into one or moreiterations. From a technical perspective thesoftware development is seen as a succession

of iterations, through which the software under development evolves incrementally.Iteration is a complete development loopresulting in a release (internal or external) of anexecutable product, a subset of the finalproduct under development, which growsincrementally from iteration to iteration tobecome the final system.The project has multiple iterations as defined inthe SDP and at the end of the each iterations, abuild will be made and will be delivered to thecustomer. The core procedure followed and themajor activities performed herein are

described in subsequent sections.Requirements ManagementFollowing activities will be performed for Requirements Management:

1


86/104


87/104

Select and customize coding standards Develop units Code Self test will be done before submitting it to

Code Review Code review will be done by peers, by the

method of walkthrough Unit test by test engineers. Integration of components Integration testing Preparation of Installable Release to testing team Outputs Integrated and tested units Peer Review Code Review Log

TestingFollowing activities will be performed for Testing:

Develop Test Plan Review test plan

1


88/104

Develop test cases Review test cases Execute integration test Execute System test

Outputs Test plan Test cases Testing records and defect List

DeploymentFollowing activities will be performed for Deployment:

Secure the deliverable Prepare appropriate media, ensure

correctness of version and check product

integrity Check for virus, worms or any other element

that could cause a damage Prepare Delivery Note, in case of final

delivery Close Field Defects

Get Acceptance Certificate from customer Get the Project Evaluation Form filled by the

Customer User Acceptance Plan

1


89/104

No separate acceptance plan would be made. Itwould be found accepted, if developed moduleis delivered as per requirements mentioned in

SR.Project EstimatesThe Helpdesk Project Manager & ProjectLeader will do estimation for the project.Phase Plan and Milestones

Phase Iteration

Major Milestones& Releases

StartDate

EndDate

Inception

Iteration -1

Prototype ? ?

Inception

Iteration -1

SR ? ?

Elaboration

Iteration -2

DesignDocument

? ?

Elaboration

Iteration -2

SystemTest plan

? ?

Construc

tion

Iteratio

n 3

Beta

Version

? ?

Transition

Iteration 4

FinalRelease

? ?

? = Till now not known

1


90/104

MaintenanceMaintenance

&&Security MeasureSecurity Measure

1


91/104

MAINTENANCE

Maintenance is the last part of the SystemDevelopment Life Cycle that is actually theimplementation of the post-implementationreview plan.When this system is installed it is used for longperiod. The average life of a system is 4 to 6years and maximum used for 10 years.

However, this period of use brings with it theneed to continually maintain the system, butthis system can be modified and newtechnologies can be used which are prevalentin market at that period of time.SECURITY MEASURES TAKEN

Security options provided with the SQL server and Win NT are relied upon heavily for securityof the organizational information and user privacy:Users are provided with the login name andpassword to use to login to the site. Users aredivided into their categories so that only links

that are visible to them are links they haveaccess to. Links those are not required by theuser or not required to perform their duties arehidden from them.

1


92/104

Provide two type of security mode one isWINDOWS NT authentication and other is SQLServer mix mode. If user log on the site using

Windows NT domain then first security mode isgood to use. If there exists the combination of system that runs on Operating system as WIN95/98 then it is the only option available to logon to server. Mix mode authentication is morecomplex as it has more layer of processingsecurity.

1


93/104


94/104

as the project is online and will be transferred innetwork. The speed and accuracy will bemaintained in a proper way.

This will be a user-friendly one and cansuccessfully overcome strict and severevalidation checks. The system will be a flexibleone and changes whenever can be made easy.Using the facility and flexibility in .NET andSQL, the software can be developed in a neatand simple manner there by reducing theoperator's work. Since the project is developedin .NET as a front-end and SQL as a back-endit can be modified easily and used for a longperiod.

CONCLUSION

Working on the project was good experience. Iunderstand the importance of Planning anddesigning as a part of software development.

2


95/104

But its very difficult to complete the program for single person.Developing the project has helped us someexperience on real-time developmentProcedures.

2


96/104

SNAP SHOTS

Home Page

1


97/104

Sell

1


98/104

Emi Calculator

1


99/104

Buy

1


100/104

Admin Login:

3


101/104

Admin Login - AddAdvertisementPackage

3


102/104

1


103/104

Bank Loan Details:

3


104/104

***End of Project Report ***

Documents

A Project Report on “india Hot Property ” r.d.e.c. Ghaziabad