|
792 Phillips Road || Arroyo Grande, CA 93420-5019 || Phone: (805) 489-5309
|
||||||
|
|
System DefinitionThis is the requirements definition part of the problem. We use whatever it takes to ferret out the needs of you and your users. Interviews, questionnaires, and prototyping are some of the most successful methods. These methods will include object methodology as it applies. During this phase we'll also determine the best platform and operating system for satisfying your needs. Some ExamplesWe developed a Human Resources database for a medium sized company. Extensive end user participation in the requirements phase shortened the development process and ensured that the end product was what the users wanted. We used Access to quickly develop a prototype of the database for presentation to users. Once the definition was complete, we used a simple conversion program to automatically create the database definition for use with SQL Server. This data base became the springboard for defining an Intranet application that would give company employees easy access their own benefits information as well as access to descriptive information and forms for all company benefits programs.We developed an electronic Timecard system to provide a company with more accurate and timely acquisition of employee charges to contracts. Since the existing paper Timecard was such an integral part of the business process, the new system was defined to be as much as like the existing paper product as possible. This meant minimum impact on existing processes and a minimum of training required for employees to use the new system. The initial platform was chosen to be Windows 3.11 for maximum utilization of the existing machines available to employees. As new platforms and WEB development support became available, we enhanced the system so that Windows 95/98/NT desktop clients as well as Unix and MAC browser clients could be supported. We developed a CASE tool to support requirement definition and provide rapid affinity analysis and generation of cluster graphs. If the affinity analysis is performed with respect to data item/entity usage, the cluster graph provides a systematic way of identifying the content of individual tables in a database. A database defined in this manner will be optimized with respect to data item usage. For our level of responsibility in recent system definition activities see this.
|
||||||
|
|
|||||||