5. Results of Study
After studying Young-Young Customer Service system our team has found many human and system needs for the project. The technologies used in the existing system is creating problems for any update. For example to create revenue report requested by CEO it is actually easier to create in Financial System but nobody knows how to write a new program in the Financial System. We need to address this problem by hiring a programmer who is familiar with the technology used in the Financial System. Since Treasurer would like to keep the existing Financial System it is better to add the new functionality in the Financial System. Re- engineering Financial System is going to cost more but in the long run benefits outweigh costs. Currently customer information is entered in the Financial System. By re-engineering Financial System we can reduce redundant data entry. Customer order information is entered in the Customer Service System and Financial System can get information from the Customer Service System.
There is going to be one database and all the systems are going to access the database.
Financial Department and Inventory Control Department are facing problems in getting information about orders on time. It is better if the database is accessed directly from customer engineers pocket PC’s for update of information. Web based interface for customer information update is recommended.
A prototype is developed by our team members and is presented to the management to have a look and feel of the system. Prototype helps in the process of understanding business functionalities and interface.
With the given time frame of six months our team would like to use RAD (Rapid Application Development) methodology for development of Customer Service System.
Users are involved in every step of the development and their input is considered.
Users will have a visual model when agreeing with the business requirements.
Work plan and function point analysis was created for customer service system. Function point analysis gives function point count and it is used to estimated how complex the system is going to be. It also gives approximate time required to complete the project.
Hardware and software engineering are not nearly as expensive as they used to be. Commercial off the shelf (CDTS) materials can be acquired from bidders, a comparable costs or even purchasing readymade programs that can be tailored specifically to Young- Young’s financial system requirements. Technical expertise is affordable and available. Option 1 allows room to engineer for future growth and compatibility which equals numerous other potential systems in the long run.
Option 2 increases the probability of errors or setbacks due to many moving parts. Coding schemes and translation programs must be compatible and have the potential to cost more when problems arise.
Option 3 has no initial cost to Young-Young but the costs in human errors do to the need for double entry and not to mention more man hours will cost Young-Young more dollars in the long run. At this point option 3 is not considered feasible at all.