ANALYSIS-Amey and Mahesh Updated

8/8/2019 ANALYSIS-Amey and Mahesh Updated

1/47

PROJECT REPORT TITLED

CHS

SUBMITTED BY

MAHESH VARAK

&

AMEY RANGNEKAR

UNDER THE GUIDANCE OF

PROF. (MRS.) SHITAL PATIL

SUBMITTED TO

DEPARTMENT OF INFORMATION TECHNOLOGY

VIVEKANAND EDUCATION SOCIETYS

COLLEGE OF ARTS, SCIENCE & COMMERCE

SINDHI SOCIETY, CHEMBUR MUMBAI 400071

2009- 2010

A Project Report titled


2/47


3/47


4/47

Developments in software engineering have given rise to

many modern innovative and useful software. The ever

growing need for software is the real reason for it. This

report is also going to introduce you to such a step.

Nowadays the computers are being used in almost

every field. To make work more easier and time saving, the

computers with new software versions, new technologies are

being developed. They are not only used in large scale

organization but also in small scale organization to make

work easier. Therefore we have designed a system, CHS

which is used to automate the manual process of calculating

the Charges and other functions of a Housing Society.

CHS software is being prepared for the Prashant

CHS located n Kandivli (E). Our designed system consists of

salient features: it will help to store records related to house

owners of the Society more efficiently and sort them as per

the convenience of the client. The system will automate the

process for managing his functions and make it much more

easier and faster.


5/47

ACKNOWLEDGEMENT

We have great pleasure in presenting this project entitled, CHS

and we grab this opportunity to convey our immense regards

towards all the distinguished people who have their invaluable

contributions in the hour of need.

First of all we express my vote of thanks to our V.E.S.

College and PrincipalMrs. Dr.J.K. Phadnis.

We would also like to thank our Coordinator, HOD Mrs.

Jayalakshmi Shrinivasan & Project guide Mrs. Shital Patil

for his timely support in the completion of this project.

We are highly obliged to the teaching members of the

Information technology who have spared efforts in making the

project a successful endeavor. We would also like to thank non-

teaching staff members Sushil.

We would like to thank all others, who have extended their

support to complete this project.

Last but not the least we extend our sincere thanks and

appreciation to our family without their support and motivation

this project was not possible


6/47

PERT / CPM

PERT/CPM is a method of scheduling a project based on individualtasks or activities. A PERT/CPM chart is a charting method that showsrelationships among tasks. PERT/CPM stands for project evaluation and reviewtechnique/critical path method.

By defining which tasks can be done concurrently and which ones must bedone serially. The longest path, from the first task to the lat task, of dependenttasks is called as critical path, because if any of the tasks on that path slips, thenthe entire project schedule will slip. Other tasks not on the critical path usuallyhave some slack time. The slack time for a task is the amount of time that the taskcan slip without affecting the schedule.

A PFRT/CPM chart graphically shows these dependencies, the critic path,and the slack times. It has definitely proved an effective tool for us to develop the

project schedule. It is always juggling act to balance the availability and work load.Developing a PERT/CPM is a four-step process:

Identify all the tasks. Determine the amount of work to complete each task. For each task, identify the immediate predecessor task. Chart the tasks on the PERT/CPM chart, calculating start and finish time for

each task.


7/47

The description of the PERT Node Box is as

follows:

The other charting technique used is the Gantt chart. A

Gantt chart presents the task as horizontal bars where the

vertical ticks are calendar days and weeks. Thus a Gantt chart

does not show the dependencies quite as graphically, but it does

show calendar information well.

Earlies

t

Activit

yLates

tFinis

h

Time

Activity Duration

Lates

tFinis

h

Time

Earlies

t

Finish

Time

Float

Analysis

And

Design

n

stru

ctloat


8/47


9/47

WORK BREAKDOWN STRUCTURE FOR

PROJECT PLANNING

Sr. No Activity Days

1 Requirement Gathering1.1 Meet Client 1

1.2 Determine scope and objective 2

1.3 Reviewing different technologies to implement theproject

2 Analysis

2.1 Selecting the appropriate protocol 6

2.2 Selecting The technology 5

2.3 Objectives & scope of project 6

2.4 Feasibility study of requirement 6

3 Design

3.1 Designing the architecture of the software 5

3.2 Designing the flow of software 7

3.3 Designing the algorithm to suit the requirement 5

3.4 Designing the UI 5

4 Coding

4.1 Implementing the algorithms 10

4.2 Coding the different modules 10

4.3 Integrating the modules 5


10/47

5 Testing

5.1 Deploying the software on emulator 4

5.2 Testing each module on emulator 5

5.3 Finding defects and fix them 8

5.4 Testing on mobile 6

5.5 Checking the validations 1

5.6 Verifying the software according to requirements 2


11/47

Gantt chart

A Gantt chart is a graphical representation of the duration

of tasks against the progression of time. A Gantt chart is a

popular type of bar chart that aims to show the timing of tasks or

activities as they occur over a period of time. Although the Gantt

chart did not initially indicate the relationship between activities

this has become more common in current usage as both timing

and interdependencies can be identified.

In project management, a Gantt chart can show when the

project terminal elements start and finish, summary elements

(shown) or terminal element dependencies (not shown). A

terminal element is defined as the smallest task tracked as part of

the project effort.

Since the initial introduction ofGantt charts, they have becomean industry standard as a key project management tool for

representing the phases, tasks and activities that are scheduled as a

part of a Project Work Breakdown Structure or timeline of

activities.


12/47

TASK Dec Jan Feb Mar

1 2 3 4 1 2 3 4 1 2 3 4 1 2 3 4

1.Planning Phase

Define the

problem

Work breakdown

structure

Product Project

Schedule

2.Analysis Phase

Gather

Information

Define System

Requirement

Objectives and

feasibility

3.Design Phase

Design each

component

Design database

Design system

flow


13/47

4.Coding Phase

Write Code for

Individual

component

Integrate the

components

5.Testing Phase

Unit Testing

System testing

Integration testing

6.Implementatio

nPhase

Base Line Schedule

Actual Time


14/47

Process involved

We should adopt a process model thatdescribes the various phases involved in software

development.

The most basic process model used in web

site development should be familiar to most people or

simply Top-down Approach. The basic web projectprocess starts with a big picture & narrows down to the

specific steps necessary to complete the site. The

model starts with a planning stage, then a design

phase, then implementation & testing, & ends with a

maintenance phase. In software engineering this model

is often called the Modified Waterfall Model or

sometimes the Software Lifecycle Model, because it

describes the phases in the lifetime of software. Each

stage in the waterfall model proceeds one after another

until conclusion.

Even though, this process does not deal

well with change, this is a simple model for the site

design continues to be very popular & it is easy to

understand & easy to follow.


15/47

The Modified Waterfall Model works better

in most cases than the classic waterfall model. It has

the same breakdown of development tasks, but has the

additional feature of feedback to make things better.

A MODIFIED WATERFALL MODEL

V & V: Verification and Validation

PROBLEM

REQUIREMENT

DESIGN

IMPLEMENTATION &

UNIT TESTING

INTEGRATION &

SYSTEM TESTING

RELEASE

OPERATION &

V & V

V & V

V & V

V & V

V & V

V & V


16/47

TABLE OF CONTENT

SERIAL

NO.

CONTENTS PAGE

NO.

1. ANALYSIS PHASE 1

A. System Study 2

Problems statement. 3

Problem with current system. 4

Questionnaire 5

Objectives and Scope of the

system

6

Advantages of existing system. 7

B. Feasibility Study

Cost Benefit Analysis(CBA)

C. Requirement Specification

Tools & Technology used.

2. DESIGN PHASE

Class Diagram

Activity Diagram

Sequence Diagram


17/47

Collaboration Diagram

E-R Diagram

Use Case Diagram

Event Table

4. IMPLEMENTATION PHASE

Screen Layouts.

5. TESTING PHASE

Types of testing

5. VALIDATION.

6. SYSTEM MAINTENANCE &

EVALUATION.

7. FUTURE ENHANCEMENT OF OUR

PROJECT

8. BIBLIOGRAPHY

Books referred, Sites Visited, andEncyclopedia


18/47

1. ANALYSIS PHASE

A.SYSTEM STUDY

1. PROBLEM STATEMENT The existing system of Prashant Co-Operative HousingSociety is not automated, so our aim is to automate it.

The processes such as keeping the records of all thehouse owners and other miscellaneous work(painting,

leakage or any other repair work)is in the form ofhardcopy which is space consuming and the calculation ofthe maintenance amount is done manually which is timeconsuming.

The processes such as parking charges, penalty chargeon the delayed payment and keeping the track of ownerswho have given their rooms on rent are maintained indifferent record books. Hence it becomes a tedious taskfor the person concerned to go through all the record

books while preparing the bills.The proposed system will overcome all this problemsfaced by the existing system.

2. PROBLEMS WITH THE CURRENT SYSTEM: -

Lack of immediate retrievals: -Theinformation is very difficult to retrieve and tofind particular information.

Lack of immediate information storage: -The information generated by varioustransactions takes time and efforts to be storedat right place.


19/47

Error prone manual calculation: - Manualcalculations are error prone and take a lot of

time this may result in incorrect information.

Preparation of accurate and promptreports: - This becomes a difficult task asinformation is difficult to collect from variousregisters.

Privacy of information cannot be maintained.

Generating report details on yearly, monthly andweekly basis is tedious.

There is no proper authorization i.e. anyone cangain access to records.

Therefore, to defeat all these problems, we

are developing software which will meet all the needs of

the current system .Our software will ensure that our

client has fast and easy access to records.


20/47

3. QUESTIONNAIRE FOR STRUCTURED QUERY

ANALYSIS AND DESIGN:-

What is the current system?

Do you have any automated system or is it manual?

What are the flaws in the current system?

How is the system going to help you overcome the above flaws?

What is current systems input and output?

Will they remain same for the new system?

Any extra feature that you want to add?

Any due dates for the completion?

Can you give any document, which will help us to understand thecurrent system and requirements of the new system?

Who all are the different users of the system?


21/47

Choices of front end and back end?

If they are ready to give money, what is the cost of the system?

4. OBJECTIVES AND SCOPE OF THE SYSTEM

CHS system is designed to maintain the data more efficiently

and sort it as per the needs of the client. The proposed system will grant

access only to the legitimate user thus providing proper authorization to theuser.

By using the proposed system, the user can calculate

maintenance bill of the house owner, set new charges for housing society

enter details regarding his/her flat. It will also help to maintain the details

like mode of payment, date of payment, fine calculation etc .Based on the

details provided the user can calculate monthly bill for each room owner.

Our software uses GUI to make it more userfriendly. The

system is easy to understand, easy to use and offers the simplicity of fast

point and click service to our client. The visual interface makes the

everyday aspect of calculating and reporting fast. It offers user a

centralized point of control.

Thus the designed software will surely help the CHS to meet

their requirement.


22/47

Each of the modules is designed as forms in Visual Basic .Net

and is connected to a backend developed in ORACLE 10G. The

application is developed in IDE environment so as to maintain and retrieve

information with ease and in a convenient and efficient manner.

5. ADVANTAGES OF THE SYSTEM

Planned approach towards working: - The working in the

organization will be well planned and organized. The data will be

stored properly in data stores, which will help in retrieval of

information as well as its storage.

No Redundancy: - In the proposed system utmost care would be

that no information is repeated anywhere, in storage or otherwise

i.e. a centralized point of control.

Immediate retrieval of information: - The main objective ofproposed system is to provide for a quick and efficient retrieval of

information. Any type of information would be available whenever

the user requires.

Immediate storage of information: - In manual system there are

many problems to store the largest amount of information.

Automated Process: - It allows the client toautomate and streamline the entire operation.


23/47

Security: -This system provides security thatallocates specific access privileges to user who login.

Error Avoidance: -The typographical mistakes ofthe user, while entering the data will be debugged atthe same time. Hence our client will not face theproblems raised by the typographical mistakes.

B. FEASIBILITY STUDY

An important outcome of the preliminary investigation is thedetermination that the proposed system is feasible. There are

three aspects in the feasibility study portion of the preliminary

investigation.

1. Economical Feasibility2. Technical Feasibility3. Operational Feasibility

Economical Feasibility:

In the short term, it is quite a big investment as per the

vendors point of view. But in the long run; it gives profit and

allows the vendor to achieve his goals. The proposed system

crosses the level beyond the break-even point where the ROI is

far more than initial investment.

Technical Feasibility:

As our proposed system is still in the process of evolving,

it requires technical staff for further development and also for its

implementation.


24/47


25/47

Due to available information can make betterdecision(leading to additional cash flows).

Increase staff moral from using the state of the art toolsfor running the business.

C.REQUIREMENT SPECIFICATION

1. HARDWARE AND SOFTWARE USED

Hardware requirement:

Processor 1.91 GHz or more

RAM 512 MB or more

Hard disk 80 GB or more

Software requirement:


26/47

Operating system Windows 2003, Windows NT, Windows

XP, Windows VISTA, Windows 98

Software to be used Microsoft Visual Studio. Net

Framework, Oracle10g

TOOLS AND TECHNOLOGY USED

1. Visual Basic . NET:

Microsoft visual basic is the fastest and easiest way to

create applications for Microsoft windows whether one is an

experienced professional or brand new to windows

programming. Visual Basic provides us with a complete set of

tools to simplify rapid application development.

So what is Visual Basic? The Visual Basic part refers to

the methods used to create graphical user interface (GUI).

Rather than writing numerous lines of code to describe the


27/47

appearance and location of interface elements you simplify

add already built objects on the screen.

The part refers basic (Beginners all-Purpose symbolicinstruction code), a language used by programmers more

than any other language in the history of computing. Visual

Basic has evolved from the original basic language and now

contains several hundred statements, functions and

keywords.

Beginners can create useful applications by learningjust a few keywords, yet the power of program allows

professionals to accomplish anything that can accomplished

using any other Windows Programming Language.

2. ORACLE 10.G

An independent Comparative Management Cost Study from

the Edison Group proves Oracle Database 10g offers superior

manageability, resulting in significant advantages and cost

savings over Microsoft SQL Server 2000 and 2005. The latest

report demonstrates that Oracles manageability advantage over

SQL Server has increasedsince the last comparison. In theprevious study, Oracle Database 10g release1 had a 30% time

advantage and 20% complexity differential with Microsoft SQLServer 2000, compared to the 38% time and 30% complexity

differential that Oracle Database 10g Release2 now holds over

SQL Server 2005.


28/47

In the side-by-side comparison Oracle Database 10g

beats Microsoft SQL Server because with Oracle:

Typical DBA functions are 38% faster Requires 30% fewer steps, making it less complex

Business can save up to US $31,664 annually per databaseadministrator (DBA)


29/47

DESIGN PHASE

The design phase gives an insight of the proposed

system, thereby providing a precise view of the system.

The design phase includes:

1. Logical Design:-

It includes Class Diagram, Event Table, CollaborationDiagram, Sequence Diagram, Activity Diagram, State

Transition Diagram, Information Structure, Site map

2. Physical Design:-

It includes System Flow Chart

CLASS DIAGRAM


30/47

VIDEO RENTAL

Cd_id, cd_name, customer_id,

customer-name, issue_date,

charges

check(), buy(), return()

SUPPLIER

manufacture(),

count(), test(),

invoice(), supply()

SHOPKEEPER

buy(), count(),

sell(), check(),

invoice()

CUSTOMER

buy(), pay(), return(),

check()


31/47

Use Case Diagram

User

Owner

SEQUENCE DIAGRAM

Enter Owner

Details

Enter Ownership

Details

Enter Flat

Details

Search a Required

Detail

Calculate

Maintenance

Charge

Generate a Bill

Send Bill to Owner

Set Due Dates

Does Payment

Check Due

Dates

Fine If late

Payment


32/47

Provides details

sets owner id

asks for Flat type

provides details

asks for Flat Details

provides

Flat Details

SEQUENCE DIAGRAM

BILL

ISSUER

SOCIETY CHARGE

MGMT

OWNER

BILL

ISSUER

SOCIETY CHARGE

MGMT

OWNER


33/47

charge Calculated on basis of details

Generates Bill

Sends Bill toOwner

Does Payment

Checks Payment Date

Charges Fine if Late

ACTIVITY DIAGRAM

LOGIN

VALIDATE THE

USER/ADMIN Enter to Main

page

Back to login

page .

Admin

Login

Treasurer

Login

Add New

User

Updates current

Member

Update

Char es

Calculates

Maintenance

Calculate

FineGenerate


34/47

Matched correctly Login failed


35/47

1) COLLABORATION DIAGRAM

DOES PAYMENT

FINE IF LATE

ADDS

ADDS

MEMBER

PROVIDES

PERSONAL

INFORMATION

GIVES

BILL

GIVES

MODIFIED

INFORMATIO

N

UPDATES

CHANGES

ADMIN

USER

MEMBER

1

7

23

64

5

8


36/47

6) EVENT TABLE


37/47

EVENT TRIGGER SOURCE ACTIVITY RESPONSE DESTINAT

N

1) LOGIN LOGIN

MONITORING

ADMIN VERIFICATIO

N

ACCESS TO

SYSTEM

ADD USE

2) LOGIN LOGIN

MONITORI

NG

USER VERIFICATIO

N

ACCESS TO

SYSTEM

MAIN PAG

3) USER

ADDS

MEMBER

ORDER

INFORMAT

ION

USER ENTER

MEMBER

DETAILS

MEMBER

ENTERED

MAIN PAG

4) UPDATE

MEMBER

INFORM

ATION

SCANS

RECORDS

USER SEARCH

PARTICULAR

MEMBER

SEARCH

COMPLETED

MAIN PAG

5) UPDATE

CHARGE

S

CHARGE

UPDATION

USER UPDATE THE

CHARGES

CHARGE

UPDATED

MAIN PAG

6) CALCUL

ATEBILL

SCANS FOR

MEMBERDETAILS

USER SEARCH FOR

MEMBERDETAILS

CALCULATE

BILL

MAIN PAG

7) GENERA

TE BILL

FOR

MEMBER

BILL

GENERATI

ON

USER GENERATE

BILL

PRODUCES

BILL

MAIN PAG


38/47

IMPLEMENTATION PHASE


39/47

TESTING

Software Testing is an empirical investigation conducted to

provide stakeholders with information about the quality of the

product or service under test , with respect to the context in

which it is intended to operate. This includes, but is not limited

to, the process of executing a program or application with the

intent of finding software bugs. It can also be stated as the

process of validating and verifying that a software program

/application/product meets the business and technical

requirements that guided its design and development, so that it

works as expected and can be implemented with the same

characteristics.

Each phase of software development has a parallel

testing activity as shown in the figure:-

DEFIFINE SYSTEM TEST

DEFIFINE INTEGRATION TEST

DEFIFINE UNIT TEST

REQUIREMENTS SYSTEM TEST

DESIGNSPECIFICATION

INTEGRATIONTEST

UNIT

SPECIFICATION

UNIT TEST


40/47

1. The requirements document provides input to the

definingsystem test cases and also drives the design phase.

2. The design phase consists of refining the design fromhighlevel down to detailed level. Each level defines a part

of the system and thus requires integration tests to

ensure that each component works as an

incremental element.

3. The unit phase provides specifications and eventuallythecode for each unit. Unit specifications are used to

define unit tests.

IMPLEMENT THE

UNITS


41/47

Testing For the CHS

A primary purpose for this testing is to detect softwarefailures so that defects may be uncovered and corrected.

This is a non-trivial pursuit. This testing cannot establish that

a product functions properly under all conditions but can

only establish that it does not function properly under

specific conditions. The scope of this software testing often

includes examination of code as well as execution of that

code in various environments and conditions as well as

examining the aspects of code: does it do what it is

supposed to do and do what it needs to do.

Testing is done on the following levels:

Unit Testing

The minimal software component( module) are tested

Each unit (basic component) of the software is tested toverify that the detailed design for the unit has beencorrectly implemented

Testing is done at the class level, and the minimal unittests include the constructors and destructors

In White Box Testing each function of the procedure ofthe system is tested in sequence


42/47

In Black Box Testing Specification-based testing isdone to find that each module gives specific output forparticular input

Integration testing

The interfaces and interaction between integratedcomponents are tested

Progressively larger groups of tested softwarecomponents corresponding to elements of thearchitectural design are integrated and tested until thesoftware works as a system

Four integration strategies exists:

TOP DOWN.

BOTTOM UP.

SANDWICH.

BIG BANG.

Bottom up approach is used

System testing

Testing is performed on the entire system in thecontext of a Functional Requirement Specification (FRS)and System Requirement Specification (SRS).

The behaviour and even the believed expectations ofthe customer are also tested.

SECURITY, SERVICEABILITY, PERFORMANCE testing arealso done.


43/47

Validations

User must confirm login when charges need to beupdated.

Two users cannot log in at the same time.

The Society charges updated are used for calculationsand old ones are stored in the database for reference.

The same flat number cannot be assigned to anotherOwner.

The user can edit the information wrongly entered. User get proper message when system is being closed . User get error message for invalid password.


44/47

User get error message for wrong format of DataEntered.

SYSTEM MAINTENANCE & EVALUATION

System maintenance is a modification of the software

product after delivery to accomplish one of the following

objectives:

Correct faults. Improve the performance or other attributes.


45/47

Adapt the product to a changedenvironment.

The terms support and maintenance describe activities that

occur after a system is made operational. Support activities

assist users in realizing the full benefits of the system

.Maintenance activities ensures that the system functions at

peak efficiency and that needed changes are implemented with

minimal disruption to the organization.

The performance of the system can be

measured by two factors, viz. the efficiency and the

effectiveness .the efficiency indicates the manner in whichthe inputs are used by the system. If the input-output ratio is

adverse, we say that the system is inefficient though it

produces the desired results .The effectiveness is the

measure for deciding whether the system provides the

desired output or not. When the system is ineffective, the

system is out of control and it needs a major correction. A

system has to be effective and efficient for the highest utility

to the user of the system .Broadly speaking, the

effectiveness is a measure of the productivity i.e. the

measure of the output against the input.

Throughout the lifecycle of the project it is put

through the test against efficiency and effectiveness quite

frequently .The stronger the system is, the lesser

maintenance the system requires .As of now, there is no

significant maintenance policy adopted or proposed for the

system.

FUTURE ENHANCEMENT


46/47

As per the task allocated to us we have

completed the project successfully. After

knowing and studying about the client

requirements, this is what we concluded to dofor the complete system.

But there are always chances for future

modifications for providing more facilities.

We would enhance our system by

adding Security module. This modulewould maintain records of visitors to

the society.

Another enhancement would include

personal details of employees who

work for the society like the sweeper,

electrician, watchmen etc.


47/47

Documents

ANALYSIS-Amey and Mahesh Updated