Database System For Lexus Car (PVT) LTD.: Pg.D.ISM 506 User-Centered Database Design

Database System for Lexus Car (Pvt) Ltd.
Individual Assignment
Pg.D.ISM 506 User-centered Database Design
506 User-Centered Database Design Pg.D.ISM 2009/10
Table of Contents
Abstract ....................................................................................................... 3 1 The Organization .......................................................................................4 1.1 Organizational Structure .....................................................................5 1.2 Company Database..............................................................................5 1.3 Company Operations............................................................................5 2 Drawbacks of the Existing System..............................................................6 3 Objectives of the Study..............................................................................8 4 Future Expansions......................................................................................9 5 Comprehensive study on Database Developments Methodologies............9 5.1 The Relational Model..........................................................................10 5.2 The Network Data Model....................................................................11 5.3 The Hierarchical Data Model..............................................................11 5.4 The Object Relational Model...............................................................12 5.5 The Object Oriented Model ................................................................12 5.6 The Data Warehousing.......................................................................13 5.7 The Web Databases............................................................................13 6 Compare Database Methodologies...........................................................13 7 Choosing a Data Model for Lexus Car (Pvt) Ltd........................................17 7.1 Used Methodology & Sample Data.....................................................18 8 Entity Relationship Diagram.....................................................................21 9 Implementation Strategy and Recovery Management.............................27 10 Conclusions............................................................................................28
M.L.A Perera 2009/10/PGDISM/080
11 List of References...................................................................................29
Abstract
The Lexus Car (Pvt) Ltd is a Leading Car Manufacturer having its own patent for small city cars in Sri Lanka. This document explains the existing business process of the company and the proposed Database Methodology / Model for the company vehicle Order Processing & after Sales Services System. Lexus Appointed me as an In-house Consultant for Identify & Propose Suitable Database System for there vehicle Order Processing & after Sales Services System. Currently Lexus runs on a Manual system totally based on Spreadsheets. The motive behind proposing the new Database system is to implement an efficient, modern and cost-effective information system where it integrates Vehicle Order Processing & after Sales Services, which is the key business areas of the company I have analyzed the entire business process and identified the areas need to be automated based on current demands and scope of the business and its requirements as well as suggestions of the staff and the management. Study attempts to analyze strengths, identify weaknesses and successes of the existing manual system of Sales and Order Processing Department of Lexus Car (Pvt) Ltd. For this all the operations of the existing manual system had studied, plus analyzed all personals involve within each operation, all data used to a particular operation, sources and sinks of the data, how to format data, what each persons duty and sequence of operations. Finally proposed a database system to handle Vehicle Orders & after sales services more efficiently. This provides the benefits of streamlined operations, enhanced
administration and control, an efficient information system, improved response to customer care, cost control and increased profitability and minimized cost and frauds.
The Organization
Lexus is an automobile company based in Sri Lanka. As the business challenges that face organizations grow in complexity and strategic significance, an integrated approach to establishing enterprise-wide efficiency and flexibility has never been more important. Currently over 200 employees have been employed for the operations all over the country. Since the launch in 2003 the vehicles has been very well accepted in the market while being the pioneers of designing, developing and manufacturing , customer care and make every effort to meet customer satisfaction. After sales support play major role of the business.
Company Strength
The Guidance of the professionals in the Automobile Industry having wider experience Factory trained mechanical & technical staff who is dedicated & alert at any emergency Well equipped, ultra modern workshop facility in line with todays needs Making sure that customer expectations are always satisfied in the long run with providence to 24 hour mobile service around the clock at any emergency Special attention in service quality
1.1 Organizational Structure
1.2 Company Database

Lexus Car (Pvt) Ltd Currently uses a manual system, where all the operations information is kept manually in notebooks and file forms. The main concern of the company is its Vehicle Order Processing & after Sales Services System. The company stores all the necessary information such as Customer Details, Vehicle Order Details, Customer Payment Details, Vehicle Details, and Vehicle Maintenance Details etc. My initial investigation shows that company is having a many number of information flows. Some of them were much unstructured. I planned Information gathering stage with extra cautiousness, because it dealt with many security reasons and their valuable time.
1.3 Company Operations

The System starts by a customer placing an order. The Customer is given a quotation of different types of vehicles and he can select a vehicle according to his desire. There are
two types of customers such as Normal Customers and Permit Customers where Lexus Car (Pvt) Ltd. Is the authorized person for the Government Vehicle Permit as its the Locally Assembled Motor Car Manufacturer. Customer has to be register before he place an order. The customer has to fill the Customer Order Form including his Personal Details and Vehicle Order Details and then a Sales and Marketing Representative will record the Customer and Order Details in a notebook. Customer is given the Performa Invoice and he has to pay a 30% of it as an Advance Payment and then the company considered as the order is confirmed. The Customers can settle their payments in another two installments. The company sends a Commercial Invoice to the customer with the Engine Number and Chassis Number of his vehicle. Permit Customers have to submit their VAT and TIN (Tax Identification Number) Certificates to the company which are essential to clear the Permit Holders Vehicle Components without Tax. And also the customers have to settle their 1st installment payment during that time. When the vehicle is completed Vehicle Completion Data send to the customer by informing him to settle the balance payment and request for the data which are needed to register the vehicle. When customer settle the payment and provide the necessary data for Vehicle Registration with the registration payment, the vehicle data send to the RMV for the registration. After the vehicle received a Registered Number, the vehicle is delivered to the customer with giving a 50,000km or 2 years warranty period. And also Lexus Car (Pvt) Ltd provides an after sales service to their customers.
2 Drawbacks of the Existing System

Data Redundancy and Inconsistency
In the event of any Customer Transaction specific information was needed, searches would have to be carried out across many files written manually to locate the piece of data that is required. Inability to provide summarized and specific information, without reading and filtering through much data.
Data has to be manually entered in the relevant files there by involving the human factor leading to human error.
Less Efficiency
Information of a specific entity such as the Transactions that are done with a specific Customer required much of man power on the path of searching the relevant file and manually calculating the information. This was time consuming, expensive and led to errors. And also do not contain up-to-date data.
Data Isolation
Information was not readily available, as any request on information would go through the manual files. Thus the person responsible for the handling of the file would manually search the entity. This caused bottlenecks, with data and information not being readily available.
Difficult to keep backups

Vulnerability of data if fire, floods or any such like act of nature or terrorism were to take place. An automated system on the other hand, would provide for back up facility at multiple locations and possible on line access to minimize system down time.
More space to store data

In the case of happening to maintain cabinets to store manual files, the space problem is critically raised, as the data written on manual files grows higher.
Data security is less

The threat of insecurity of data as anyone can change or misplace a very important data.
High Cost
Since the process is being carried out by people which is less efficient and error prone, increases the cost for the process. Report generation is more complex.
3 Objectives of the Study

The study has analyzed the current manual system, identified the weakness and negative points and designed a database system to meet the objectives of Company Staff. My objectives were to increase the efficiency and operational effectiveness of the Sales Department by handling transaction smoothly and accurately, and provide quality service to other departments, and the management of the unit and to ensure that the system functions well. The study has introduced a database system for the Vehicle Order Processing & after Sales Services System, in order to provide a quick and efficient service to reduce and simplify the complex work done by the staff while minimizing fraud and operational cost to a large percentage. The objectives of the study according to the terms of reference are, To analyze the existing manual system and detect its inefficiencies. To decrease the workload of employees by the reduction of manual work. To provide better services for users and customers. To reduce cost. To increase the security of the system. To decrease data redundancy, isolation and inconsistency.
4 Future Expansions
Organizations Expansions
Currently Lexus Car (Pvt) Ltd Company manufactures mainly motor cars, vans & cabs namely Lexus Car (Pvt) Ltd. In near future they are planning to introduce more number of vehicle models such as Economical Models etc. And also they are planning to Tractors & Normal Fully Conditioned Buses to the market in future. Their Train Manufacturing process is under the initial planning process. Therefore I am planning to design our database system is more flexible to their future business expansions. The Lexus Car (Pvt) Ltd Company is currently takes their customer payments only in cash or cheques. So we have decided to design our system which will able to accept customer credit cards also.
Comprehensive study on Database Developments Methodologies

Benefits of the Database Approach (Date 2003)
1. The Data can be shared 2. Redundancy can be reduced 3. In Consistency can be avoided ( to some extent) 4. Transaction support can be provided
5. Integrity can be maintained 6. Security can be enforced 7. Conflicting requirements can be balanced 8. Standards can be enforced
5.1 The Relational Model
What is a Relational Database?

The relational database model was first defines in 1970 when E.F Codd introduced the idea of using the mathematical concept of the relational founds in set theory as a means to model data (Codd 1970). A relational system is one which is constructed in accordance with the group of principals that together from Codds relational model. One of the main advantages of a relational database over other databases is that the data are stored independently of the database application and not in the much more limiting sequential from. A relational database can be thought of as a collection of tables. The values in each column of a table stem from a common domain such that mathematically speaking a relation is a subset of the Cartesian product of the domains. Relations can map one-one, one-many, and many-many relationships within the same construct.
Why use a Relational Database

Relational database are design to cope with large quantities of complex information, to store this information in a form that can be easily accessed, to ensure that it is as accurate and that it maintains its accuracy. These points, plus some further ones which are not so relevant to this archaeobotanical database; are discussed clearly by Smith. (1992, 114). The relational model consists of the following five components (Date 2003) 1. An open-ended collection of scalar types (including in particular the type boolean or truth value) 2. A relation type generator and an intended interpretation for relations of types
10
generated thereby 3. Facilities for defining relation variables of such generated relation types 4. A relational assignment operation for assigning relational values to such relation Variables 5. An open-ended collection of generic relational operators ("the relational algebra") for deriving relation values from other relation values
5.2 The Network Data Model

The basic constructs of a network data model are logical record types represented by rectangles that correspond to entity sets and DBTG-set types represented by arrows that correspond to relationship types in the E/R model (CODASYL 1971). The most important construct in the network model is the set that relates the owner record type to one or more member record types. In case of many-many relationships, one must create a link record type between the two record types. Record occurrences correspond to entities, data items to attributes, and set occurrences to relationships. The network model compared with the relational model shows that the former uses predefined access paths through set mechanisms, while the latter does not and all possible routes are dynamically materialized; the former specifies certain integrity constraints to the data structure, while the latter only declares them as adjuncts to the data structure. Four major areas of data definition are structure, physical placement, access path, and integrity and privacy constraints highlighted by Michaels, Mittman and Carlson (1976). the relational model includes neither physical placement nor access paths, and there is clear separation between structure and constraints.
5.3 The Hierarchical Data Model

In this model, the data is represented by a tree structure where each node corresponds to one record type. The record type at the top of the tree is known as the root, and the elements at the lowest levels, which have no children, are called leaves. No child record type can have more than one parent segment type, whereas in the network structure, as
11
long as the child is in a different set, it can have more than one parent owner. Therefore, many-many relationships cannot be handled directly in the hierarchical model. A set type represents the relationship between the owner record type and member record type in a network sense, and it is formally declared; but it is implied in the Hierarchical model. No child segment occurrence can exist without its parent, while can be defined in the network data model by a singular set for which the owner is the "SYSTEM, where the SYSTEM has only one occurrence in the network model.
5.4 The Object Relational Model

Object relational database management systems add new object storage capabilities to the relational systems at the core of modern information systems. These new facilities integrate management of traditional fielded data, complex objects such as time-series and geospatial data and diverse binary media such as audio, video, images, and applets. By encapsulating methods with data structures, an ORDBMS server can execute complex analytical and data manipulation operations to search and transform multimedia and other complex objects. As an evolutionary technology, the object/relational (OR) approach has inherited the robust transaction- and performance-management features of it s relational ancestor and the flexibility of its object-oriented cousin. Database designers can work with familiar tabular structures and data definition languages (DDLs) while assimilating new objectmanagement possibilities. Query and procedural languages and call interfaces in ORDBMSs are familiar: SQL3, vendor procedural languages, and ODBC, JDBC, and proprietary call interfaces are all extensions of RDBMS languages and interfaces. And the leading vendors are, of course, quite well known: IBM, Informix, and Oracle. 11. (Unixspace)
5.5 The Object Oriented Model
12
Object Oriented Model adds database functionality to object programming languages. They bring much more than persistent storage of programming language objects. Object DBMSs extend the semantics of the C++, Smalltalk and Java object programming languages to provide full-featured database programming capability, while retaining native language compatibility. A major benefit of this approach is the unification of the application and database development into a seamless data model and language environment. As a result, applications require less code, use more natural data modeling, and code bases are easier to maintain. Object developers can write complete database applications with a modest amount of additional effort. (Unixspace)
5.6 The Data Warehousing

Data warehouse is a repository of an organization's electronically stored data. Data warehouses are designed to facilitate reporting and analysis. A data warehouse houses a standardized, consistent, clean and integrated form of data sourced from various operational systems in use in the organization, structured in a way to specifically address the reporting and analytic requirements.
5.7 The Web Databases

Web databases provide a simple, inexpensive and effective tool for query and reporting of data on a web page. These databases offer an alternative to client/server databases and HTML lists or tables. A web page database is an interactive system used to search, sort and display records. These systems provide small screen footprints, fast response time and a technique to reduce web server processing.
6 Compare Database Methodologies

Data Base Model Advantages Disadvantages
13
1.
Hierarc hical Model
Simple to construct and operate on natural hierarchically organized domains Adding and deleting records is easy Language is simple; uses constructs like GET, GET UNIQUE, GET NEXT, GET NEXT WITHIN PARENT etc Can model complex relationships compare to hierarchical model Conceptual simplicity Data access flexibility
Little scope for Query optimization & Pointer path restrict access In Hierarchical model Many to many (M: N) relationships cannot be handled. Data duplication will happen due to hierarchical structure Database contains a complex array of pointers that go through a set of records Structure is difficult to change Lack of structural independence Relational databases are not suited in implementing spatial (3d design, CAD)databases or handling image data
2.
Networ k Model
3.
Relatio nal Model
Data are stored independently of the database application and not in the much more limiting sequential from Relations can map one-one, one-many, and manymany relationships within the same construct. design to cope with large quantities of complex information Stored data can be easily accessed Relational databases provide the users with simple operations to manipulate data in the databases and retrieve it. Relational databases support the concept of users and user rights (Higher Security) Performance, power, and support to new hardware technologies as also
14
4.
Object Oriented Model
flexibility and a capacity to meet all types of data needs Relational databases are scalable and provide support for the implementation of distributed systems Proposed to meet the needs of complex database applications Add database functionality to object-oriented programming languages Unification of the application and database development into a seamless data model and language environment Applications require less codes & code bases are easier to maintain Users will be able to access a large amount of information
Expensive in development Required added training cost for users Inability to work with existing systems
5.
Data Warehous e
One powerful feature of data warehouses is that data from different locations can be combined in one location. Providing Data Mining facilities Data Warehouses can create a structure which will allow changes within the stored data to be transferred back to operational systems Data warehouses can work in conjunction with and, hence, enhance the value of operational business applications, notably customer relationship management systems
Before data can be stored within the warehouse, it must be cleaned, loaded, or extracted. This is a process that can take a long period of time Compatibility issues with existing & new systems Requires Specific training to maintain Security risk, because access via internet
Difficult to maintain & Higher maintain cost
15
6.
Web Database s
Economical and fast implementation for web page designers
Not able to handle rage complex environment Server overload and Bandwidth utilization affect the performance Low performance in web applications Expensive in development
7.
Object Relationa l Model
More power, greater flexibility, better performance, and greater data integrity Extensibility - Users are able to extend the capability of the database server; this can be done by defining new data types, as well as user-defined patterns. This allows the user to store and manage data. Complex types - It allows users to define new data types that combine one or more of the currently existing data types. Complex types aid in better flexibility in organizing the data on a structure made up of columns and tables. A field may also contain an object with attributes and operations Ability to query complex applications and ability to handle large and complex applications
Required added training cost for users
Data Sources (Compare Database Methodologies): 1. Elmasri, Ramez., and Navathe, Shamkant B., Fundamentals of Database Systems (4th edn.): Addison Wesley, 2003. 2. Exforsys, Website [Accessed on 23 Mar 2010] Available at: http://www.exforsys.com/tutorials/datawarehousing/advantages-and-disadvantages-to-using-a-data-warehouse.html
16
3. Wikipedia, Website [Accessed on 23 Mar 2010] Available at: http://en.wikipedia.org/wiki/Database 4. Web Developers Virtual Library, Website [Accessed on 23 Mar 2010] Available at: http://www.wdvl.com/Authoring/DB/WebPage/
Choosing a Data Model for Lexus Car (Pvt) Ltd
The choice of a data model depends on the users, the decisions, and on the capabilities of the DBMS that could be used. There is a diverse community of users facing a multiple-criteria decision support system. The Database system should therefore provide information to all levels of management in a batch or in an interactive mode. The users including decision-makers at all levels, researchers, and analysts need standard reports and interaction with the database for data retrieval, modeling, or computation in order to solve structured, semi-structured, or unstructured problems. Codd (1980), McGee (1976), Michaels (1976), and Ullman (1982) outline several factors for database evaluation: being easy to use, easy to understand, easy to manipulate, and easy to implement. These factors should be taken into account while designing the database component. From these four points of view, the relational model is a very promising approach because of its suitability to non procedural languages, its separation between structural elements and physical elements maintain data independence, and it simplicity in data structure and data manipulation. In fact, researchers, decision-makers, and analysts have found that viewing data in the form of a table relation is conceptually simple. Multiple-criteria decision support systems have requirements not only for data manipulation but also for facilities for data analysis. The network model is more complex than the relational because of its rigid structure, and its bundling four areas of data definition into one construct, which make it, lose its data independence.
17
Where many-many relationships exist, the hierarchical structure is even more complex and rigid than the network structure. The user, as Date (2003) points out, is forced to devote more time and effort to solving problems that are introduced by the hierarchical data structure and that are not intrinsic to the questions being asked, Of course, hierarchies are a natural way to model truly hierarchical structures from the real world, From an updating operation point of view, the hierarchical model possesses more undesirable properties than the previous two logical data models. Generally, the relational model is more appealing in the environment. From company point of view I can suggest Relational Model for this process because of following benefits, Can avoid the Higher Training cost, Easy Administration, Low Infrastructure cost, less expensive DBMS Systems ex. Ms SQL, supports for future expansions by less no of modifications, an efficient, Improved response to customer care, Security, decrease data redundancy, isolation inconsistency, Complex data can be easily accessed etc.
7.1 Used Methodology & Sample Data

The success of any project is depended upon the accuracy of available data. Accurate information can be collected with the help of certain methods/ techniques. Specifically I under took following fact finding activities when design the database. Gathered information from existing documentation and forms By visiting each section where I consider for database. Observation of the work environment. Interviews: Existing systems are not documented well and I have to interview related personals to get clear idea about the database and new requirements.
Sample data
Here I have listed few sample data obtain by the Surveys & Interviews Customer_Master
18
Customer_Payment_Details
Receipt No R00000 1 R00000 2 R00000 3 Date 2007/09/ 28 2007/03/ 14 2008/03/ 18 Amt 10000 00 50000 0 25000 00 PayMo de Ch Ca Ca PayTer m A F F TotPaidA mt 200000 120000 300000 CusID ..0 01 .00 2 001 PerInvNo 2008/07/11- 001 2007/04/23..002 2006/05/16- 001
Maintenance_Master
MaintCode M001 M002 M003 M004 M005 M006 M007 Description Re-Boring Engine Repair Body Painting Wheel Alignment Oil Changing Break Adjustment Engine Tuning Price 13000 18000 25000 8000 12000 3500 11500
Vehicle_Repair_Details
19
RepairCod e R0001 R0002 R0003 R0004 R0005
PerInvNo 2008/07/11001 2007/04/23002 2006/05/16.003 2006/07/27.001 2006/09/28005
WarrStat us N Y Y N N
NoofTime s 03 01 02 02 03
ReceivedDate 2009/05/12 2008/04/30 2007/01/28 2007/06/19 2008/09/09
DelivedDate 2009/06/10 2008/08/05 2007/04/01 2007/06/30 2008/09/20
Vehicle_Maintenance_Details
RepairCode R0001 R0002 R0003 R0004 R0005 MaintCode M005 M001 M003 M003 M007
20
506 User-Centered Database Design
Pg.D.ISM 2009/10
8 Entity Relationship Diagram
21
506 User-centered Database Design Pg.D.ISM 2009/10
Data Dictionary
Analyst: 1. 2. Project Date Version Entity No : Vehicle Order Processing and Maintenance System. : ... : 1.0 : 01
Entity Name : Customer_Master Description : Contain information about the customer Primary Key : CusID
Name CusID Title Initials Surname Addr1 Addr2 Addr3 CusType NIC ResNo MobNo Data Type udt_CusID varchar varchar varchar varchar varchar varchar char char char Char Size 10 05 15 30 20 20 20 01 10 11 11 Title No. Initials Surname Address Line 1 Address Line 2 Address Line 3 Customer Type National Identity Card No Resident No Mobile No Description Customer Identification
udt_CusID - varchar(10) Entity No : 02 : Customer_Permit_Details. : Contain information about the customer permit : PermitNo : CusID
Size 15 10 14 09 04 05 Description Customer Permit No Customer Identification No. Value Added Tax No Tax Identification No Customer Permit Cylinder Capacity Vehicle CIF Value
Entity Name Description Primary Key Foreign Key

Name PermitNo CusID VATNo TIN CusPercc CIFVal
Data Type udt_InvNo udt_CusID char char int money
udt_InvNo - varchar(21) udt_CusID - varchar(10)
22
Entity No
: 03 : Customer_Order_Details : Contain information about the customer vehicle orders : PerInvNo : CusID
Data Type udt_InvNo varchar udt_CusID udt_VModel money money money money char char char datetime datetime Size 21 10 10 07 08 08 08 08 14 17 01 10 10 Description Performa Invoice No Invoice Details Customer ID Model Code Vehicle Amount VAT Amount Option Amount Total Amount Engine No Chassis No Vehicle Status Completed Date Delivered Date

Name PerInvNo InvDate CusID ModelCode VehiAmt VATAmt OptAmt TotAmt EngNo ChassisNo VehiStatus ComDate DeliDate
udt_InvNo - varchar(21) udt_CusID - varchar(10) ,udt_VModel - varchar(5) Entity No : 04 : Customer_Payment_Details : Contain information about the customer payments : ReceiptNo : CusID,PerInvNo
Data Type smallint varchar udt_InvNo money char char money udt_CusID Size 07 10 21 08 02 01 08 10 Description Receipt No Receipt Date Performa Invoice No Receipt Amount Payment Mode Payment Term Total Paid Amount Customer ID

Name ReceiptNo Date PerInvNo Amt PayMode PayTerm TotPaidAmt CusID
udt_InvNo - varchar(21) udt_CusID - varchar(10)
Entity No
: 05
Entity Name : Maintenance_Header Description : Contain information about the maintenance Primary Key : MaintCode
23
Name MaintCode Description Price
Data Type udt_MaintCode varchar money
Size 04 30 08
Description Maintenance Code Description Maintenance Price
udt_MaintCode - char(4) Entity No : 06 : Vehicle_Repair_Details : Contain information about the repairs : RepCode : PerInvNo
Data Type udt_RepCode udt_InvNo char int varchar datetime Size 05 21 01 04 10 10 Description Repair Code Performa Invoice No Warranty Status No of Repairs Times Received Date Delivered Date

Name RepCode PerInvNo WarrStatus NoofTimes ReceivedDate DelivedDate
udt_RepCode - char(5) udt_InvNo - varchar(21) Entity No : 07 : Vehicle_Maintenance_Details : Contain information about the maintenance details : RepCode, MaintCode : RepCode, MaintCode
Data Type udt_RepCode udt_MaintCode Size 05 04 Description Repair Code Maintenance Code

Name RepCode MaintCode
udt_RepCode - char(5) udt_MaintCode - char(4)
24
Entity No
: 08 : Vehicle_Lisence_Details : Contain information about the license details : PerInvNo,RegPayDate : PerInvNo,RegPayDate

Data Type udt_InvNo varchar char datetime datetime char Size 21 10 01 10 10 07 Description Performa Invoice no Register Payment date Special No Request Send Date Receive Date Vehicle ID

Name PerInvNo RegPayDate SpecialNoRequest SendDate ReceivedDate VahiID
udt_InvNo - varchar(21) Entity No : 09 : Customer_Option_Details : Contain information about the customer option details : PerInvNo,OptCode : PerInvNo,OptCode
Data Type udt_InvNo udt_OptCode Size 21 07 Description Performa Invoice No Option Code

Name PerInvNo OptCode
udt_InvNo - varchar(21) udt_OptCode - varchar(7) Entity No : 10
Entity Name : Vehicle_Option_Header Description : Contain information about the Option Primary Key : OptCode
Name OptCode Description Price Category Data Type udt_OptCode varchar money char Size 07 30 08 02 Description Option Code Description Option Price Vehicle Category
udt_OptCode - varchar(7)
25
Entity No
: 11
Entity Name: Vehicle_Option_Details Description : Contain information about the vehicle option details Primary Key : OptCode,ModelCode Foreign Key : OptCode,ModelCode
Name OptCode ModelCode Data Type udt_OptCode udt_VModel Size 07 07 Description Vehicle Option Code Vehicle Model Code
udt_OptCode - varchar(7) udt_VModel - varchar(5) Entity No : 12
Entity Name Vehicle_Model_Deails Description : Contain information about the Vehicle Models Primary Key : ModelCode
Name ModelCode Description FType CC Category Transmission Status VAmt VATAmt Data Type udt_VModel varchar char int varchar char char money money Size 07 30 01 04 10 01 01 08 08 Description Model Code Description Fuel Type Cylinder Capacity Vehicle Category Transmission Vehicle Status Vehicle Amount VAT Amount
udt_VModel - varchar(5) Entity No : 13 : Repair_Option_Details : Contain information about the options taken when repairing the : RepairCode,OptCode : RepairCode,OptCode
Data Type udt_RepCode udt_OptCode Size 05 07 Description Repair Code Option Code
Entity Name Description vehicle Primary Key Foreign Key

Name RepairCode OptCode
udt_RepCode - char(5) udt_OptCode - varchar(7)
26
Implementation Strategy and Recovery Management
Implementation Strategy
The required human resources for usage and administration will be identified and will be trained. Then the system will be introduced and will run in parallel with the manual system for a time period of 3 to 6 months. There will be a separate set of users to do the past data entry operations to make the data up-to-date and no more manual file reference is required. The DBMS chosen for the implementation of the database is Microsoft SLQ Server due to its ease of integration with application platform. It is fully compatible with the future enhancements, it provides various features to facilitate easy and secure access to data from the web and it is also highly scalable and reliable.
Recovery Management
All password columns will be kept encrypted so that no one can read the data even with access at the data table Level. A mirror copy of the data files will always be maintained at two different physical locations (DR Site), one at the server and the other in another server at another physical location which will be updated in batches in every 1 hour.
Software Damages
The system can be damaged by the wrong use of the software. This can be done by employees who do not have a good will to the company, by mistake or by hackers. These errors can be audited and be corrected on regular basis. These are minimized by assigning supervisors and by letting data entry to be done in groups. Outside data transfer media will not be permitted, to prevent virus and Trojan attacks. A firewall will be implemented at the server to prevent from unauthorized users accessing the network. In Case of any disaster at the main building the database will be restored from the backup obtained available at the remote location.
27
Hardware Damages
The server and the individual pcs in the network will be checked on a daily / weekly basis and a weekly status report will be obtained from the system administrator. If there is any replace or substitute required for any hardware component which shows malfunctioning will be looked at immediately specially in the case of servers and mirror devices. If a working hard disk crashes during working the mirror disks will take over (RAID & Redundancy). If they too crash there will always are Backup hardware or Server Mirror / Server Fail Over will be kept for quick replacement.
10 Conclusions
As mentioned earlier the scope of the project is including Order Processing Systems. Hereby I would like to let you know that I have put my dedicated effort to design this system perfectly and according to requirements and constraints. When designing this system I have intended to build the system to make the system more convenient or more user friendly to the users who intend to use our system. By this proposed system I intend to give benefits like: User friendliness Reduce data redundancy Maintain consistency of data Security Reduce Cost Improved response to customer care & Increase profits of the Company
Performance of the designed system will be more than clients expectations. There wont be heavy traffic on the network when network is implemented. Since only small amount of data transfer is required by the system.
28
One of the main objectives was any requirement must meet its future needs. So spending little bit more now will certainly save lot of cost in the future. But this decision is left to the management. As all management try to minimize cost and maximize gain, cost of implementing this system also will be crucial to the management. But benefits they can gain, by replacing manual system with the computerized system will be huge. Since the system is designed to make life easy to users and cost effective, I hope that the user will be able to learn about how the system works in one time. This will reduce the cost that will involve with user training. Apart from aiding to normal process, system is designed to be able to generate reports regarding various issues. I should also recommend the new system to run parallel with the existing normal system for some time after implementation, so the two systems can be compared. So if there are incompatibilities with the new system and the old system, they can be corrected.
11 List of References
1. Date, C. J., Introduction to Database Systems (8th edn.), pp. 18-20: Addison-Wesley,
2003.
2. Codd, E.F., A relational model for large shared data banks. Communications of the
ACM 13, 1970, pp. 377-87.
3. Smith, D.J., Database fundamentals fro archaeologists, pp. 114 in Ross S., Moffett J.
and Henderson J. (eds.), Computing for Archaeologists. Oxford: University Committee for Archaeology, 1992.
4. Date, C. J., Introduction to Database Systems (8th edn.), pp. 64: Addison-Wesley, 2003.
5. CODASYL Database Task Group Report, 197l, CODASYL, Association for Computing Machinery, New York, April 1971.
6. Michaels, A. S. , Mittman, B. , and Carlson, C. R. , ''A Comparison of the Relational

and CODASYL Approaches to Data-Base Management, ACM Computing Surveys, Vol. 8, No. 1, March 1976, pp. 125-150. 7. Unixspace, Database Models, Website [Accessed on 22 Mar 2010] Available at: http://www.unixspace.com/context/databases.html
29
8. Elmasri, Ramez., and Navathe, Shamkant B., Fundamentals of Database Systems (4 th

edn.): Addison Wesley, 2003. 9. Exforsys, Website [Accessed on 23 Mar 2010] Available at: http://www.exforsys.com/tutorials/data-warehousing/advantages-anddisadvantages-to-using-a-data-warehouse.html 10. Wikipedia, Website [Accessed on 23 Mar 2010] Available at: http://en.wikipedia.org/wiki/Database 11. Web Developers Virtual Library, Website [Accessed on 23 Mar 2010] Available at: http://www.wdvl.com/Authoring/DB/WebPage/
12. Codd, E. F., "Data Models in Database Management, in Proceedings of the Workshop
on Data Abstraction Databases, and Conceptual Modeling, ACM Order Number 474800, 1980, pp. 112-114. 13. McGee, W. C., "On User Criteria for Data Model Evaluation, ACM Transactions on Database Systems, Vol. 1, No. 4, December 1976, pp. 370-387. 14. Ullman, J. D., "Principles of Database Systems", Computer Science Press, Second edition, 1982,
15. Codd, E. F., "A Relational Model of Data for Large Shared Data Banks,
Communications of the Association for Computing Machinery, Vol. 13, No. 6, June 1970, pp. 377-387.
30

Database System For Lexus Car (PVT) LTD.: Pg.D.ISM 506 User-Centered Database Design

Transféré par

Informations du document

Description originale:

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Database System For Lexus Car (PVT) LTD.: Pg.D.ISM 506 User-Centered Database Design

Transféré par

Droits d'auteur :

Formats disponibles

Database System for Lexus Car (Pvt) Ltd.

Pg.D.ISM 506 User-centered Database Design

506 User-Centered Database Design Pg.D.ISM 2009/10

M.L.A Perera 2009/10/PGDISM/080

506 User-Centered Database Design Pg.D.ISM 2009/10

M.L.A Perera 2009/10/PGDISM/080

506 User-Centered Database Design Pg.D.ISM 2009/10

M.L.A Perera 2009/10/PGDISM/080

506 User-Centered Database Design Pg.D.ISM 2009/10

1.1 Organizational Structure

1.2 Company Database

1.3 Company Operations

506 User-Centered Database Design Pg.D.ISM 2009/10

2 Drawbacks of the Existing System

M.L.A Perera 2009/10/PGDISM/080

506 User-Centered Database Design Pg.D.ISM 2009/10

Difficult to keep backups

More space to store data

Data security is less

506 User-Centered Database Design Pg.D.ISM 2009/10

3 Objectives of the Study

M.L.A Perera 2009/10/PGDISM/080

506 User-Centered Database Design Pg.D.ISM 2009/10

Comprehensive study on Database Developments Methodologies

M.L.A Perera 2009/10/PGDISM/080

506 User-Centered Database Design Pg.D.ISM 2009/10

5.1 The Relational Model

What is a Relational Database?

Why use a Relational Database

506 User-Centered Database Design Pg.D.ISM 2009/10

5.2 The Network Data Model

5.3 The Hierarchical Data Model

506 User-Centered Database Design Pg.D.ISM 2009/10

5.4 The Object Relational Model

5.5 The Object Oriented Model

M.L.A Perera 2009/10/PGDISM/080

506 User-Centered Database Design Pg.D.ISM 2009/10

5.6 The Data Warehousing

5.7 The Web Databases

6 Compare Database Methodologies

M.L.A Perera 2009/10/PGDISM/080

506 User-Centered Database Design Pg.D.ISM 2009/10

Hierarc hical Model

Relatio nal Model

M.L.A Perera 2009/10/PGDISM/080

506 User-Centered Database Design Pg.D.ISM 2009/10

Object Oriented Model

Difficult to maintain & Higher maintain cost

M.L.A Perera 2009/10/PGDISM/080

506 User-Centered Database Design Pg.D.ISM 2009/10

Economical and fast implementation for web page designers

Object Relationa l Model

Required added training cost for users

M.L.A Perera 2009/10/PGDISM/080

506 User-Centered Database Design Pg.D.ISM 2009/10

Choosing a Data Model for Lexus Car (Pvt) Ltd

M.L.A Perera 2009/10/PGDISM/080

506 User-Centered Database Design Pg.D.ISM 2009/10

7.1 Used Methodology & Sample Data

M.L.A Perera 2009/10/PGDISM/080

506 User-Centered Database Design Pg.D.ISM 2009/10

M.L.A Perera 2009/10/PGDISM/080