AUTOMATIC RESIDENT WELFARE

SUMMARY:

This case is about the Resident welfare association of a colony in south Delhi and its welfare activities. The tedious and time consuming book keeping work for the association is handled by Bobby George. The colony members however , are not very happy with Bobby’s performance.

Association has an outdated computer system developed n 1990 to track the billing and receipt of funds, because of which no one is able to maintain the system properly.

Some flaws of the existing systems are:

-The existing system takes lot of time to process the data.

-Member queries are not answered easily.

-When member information is entered into the system, each field is presented one at a time.

-This makes very difficult to return to a field and correct a value that has entered.

-Sometimes a new member is entered but disappears from the records.

And many more like this. So association has finally decided to upgrade the system rather develop the new system which is scalable.

CONCEPT:

This case clearly depicts the flaws of the existing system which is developed in 1990 . It is based on Foxpro , since the foxpro has become outdated , because of which no one is able to maintain the system properly. Like the exsting system takes lot of time to process the data etc.

So the association has decided to upgrade the system, rather develop the new system which is scalable. The reason has not been stated in the case but cost of installation seems  the main reason to not opting the new scalable system.

QUESTION AND ANSWERS:

1/  What requirements analysis strategy would you recommend for this situation? Explain your answer.

Ans:The strategy recommend by me goes like this: first of all approach Bobby because he handles all the book keeping work and ask him that what problems he and customers are facing while using the existing system and what according to him the system is supposed to be. Then for requirement analysis we should approach to colony members who are actually facing the problem because of outdated system. And based on that we should make the strategy for upgradetion in existing system that is what is the most important thing or upgrade we need to do first and so on.

2/ What are the different data attributes you would collect to maintain update data about members and events ?

Ans: Data attributes about the members:

- Member’s name (If member is new make the separate entry)

-Sex(M/F)

-Date of Birth

-Education Qualification

-Occupation

-Family Members(no.)

Data attributes about events :

-Event Name

-Event Date

-Event Head

-Event’s Chief Guest

-Total Estimated Cost

Etc

3/ After developing the system, what system conversion strategy would you adopt ?

Ans: After developing the system I would like to make sure that the system should be bit flexible and if possible then make it scalable ie the system should be extendable and the total no. of members should not be the limiting factor fotr the system and  by using latest softwares and programs make it efficient and remove all the flaws which previous system had.