Sunday, December 4, 2011

INTRODUCTION

          I have completed a preliminary investigation of the Company Calibration Center Booking System. The investigation was a result of a systems request from the manager of Company Calibration Center, on November 27, 2010.

SYSTEM SUMMARY REQUEST

Lately, Company Calibration management noticed a decline in customer satisfaction as manifested by increased customer complaints.  Management has traced the bulk of complaints to increased delivery times and excessive delays when   booking scheduled maintenance.Coupled with the sudden unexpected success of Company Calibration, management and staff  have not been able to maintain their commitment of excellent service to all their customers, resulting in lost business and a negative business image.

FINDINGS

On the basis of the organizational chart, I have analyzed and studied each staff’s functions in the general layout of the business.  Interviews were set up with the manager and  mechanics operations were observed.  Current manual system documents were also reviewed.

RECOMMENDATIONS

            It is essential for a business to keep a competitive advantage by providing quality service to the customers.  Yet the overwhelming increase in customer volume has affected the service delivery.   Based  on the  findings gathered from the  study of the manual system  and  the  cost/benefit analysis,  I recommend   that  the   proposed   project   be   taken to  the next step, system analysis, so that a more in-depth study would be performed. 


            The following system requirements are recommended for the proposed system:
             1. Database Management System.  The DBMS will be the cornerstone for successful implementation of five other system recommendations:

TIME AND COST ESTIMATES

            I estimate that 1 month will be required for a program to perform the requested computerized invoicing system. Interviews will be scheduled with the manager, the cashier and the senior mechanic. Total of 48 hours of staff interviewing and observation is expected.  The following is an estimate of costs for performing the systems analysis:

EXPECTED BENEFITS

EXPECTED BENEFITS

Tangible:
            -    Minimize and eventually eliminate customer complaints
            -    Reduce paper-based transactions, errors and costs
Intangible:
            -    Increase customer satisfaction
            -    Increase levels of service
            -    Improve information availability
            -    Enhance corporate image

FEASILBILITY STUDY

FEASILBILITY STUDY

TECHNICAL FEASIBILITY
             The management will buy the equipments to be used (printer) and must maintain the computer and printer if there is a problem. The equipment must be checked by a technical assistance or an IT analyst.

Appendix


Appendix A

Company Calibration Center Organizational Chart

Manager

·         Record keeping

·            Suppliers

Requirements Checklist

Input
·         The system should accept and store input regarding customer information such as
o    owner’s name
o    Address
o   Contact number
o   Customer’s vehicle information

Use Case Diagram

Use Case Diagram

CONTEXT DIAGRAM

CONTEXT DIAGRAM

Systems Analysis and Design: Context Diagram

DATAFLOW DIAGRAM

DATAFLOW DIAGRAM

Systems Analysis and Design: Dataflow Diagram

ENTITY RELATIONAL DIAGRAM

 ENTITY RELATIONAL DIAGRAM

Systems Analysis and Design: Entity Relational Diagram

Data Dictionary

Entity
Attribute
Alias
Desription
Data Type
Customer
Name
refers to the customer's name
it contains the first name, midle initial and surname
string
address
refers to the customer's location
it contains the location where the customer can be track
string
contact no.
refers to the customer's phone number
it contains the  personal or business contact number of the customer
number
date
Date
it  contains the date when the customer has a transaction to the establishment
date/time
P roblems
problems
refers to the problem of the vehicle
it contains all the problems of the vehicle that the customer wants to be solved
string
solved
refers to the solved problem of the vehicle
it contains all the solved problems of the vehicle
string
Books
transaction_no
refers to the number of every customer
it contains the number of how many transaction has a customer has
autonumber
plate_no
 refers to the plate_no of the vehicle
it contains the plate_no of the vehicle of the customer
string
date
refers to the date when the customer has a transaction
it contains the the date when the customer has a transaction
 date/time
Vehicle
plate_no
 refers to the plate_no of the vehicle
it contains the plate_no of the vehicle of the customer
string
Engine
refers to the engine name of the vehicle
it contains  the engine name of the vehicle
string
vehicle Name
refers to the vehicle name of the vehicle of the customer
it contains the vehicle name of the vehicle of the customer
string
color
refers to the color of the vehicle
it contains the the color of the vehicle
string

DATA DESIGN


Order Unnormalized Form

systems analysis and design: DATA DESIGN

systems analysis and design: DATA DESIGN