System Analysis and Design for Toyota Cars - SAP Implementation

The report reflects the business process change in Toyota Cars. The organization is going to implement a SAP based system within its environment. The To-Be process, designed in this report, demonstrate the changes in the Toyota Car’s environment.

Running head: SYSTEM ANALYSIS AND DESIGN
System Analysis and Design
Name of the Student
Name of the University

1SYSTEM ANALYSIS AND DESIGN
Executive Summary
The report reflects the business process change in Toyota Cars. The organization is going to
implement a SAP based system within its environment. The implementation of new system
always demands changes in the exiting business processes. The To-Be process, designed in this
report, demonstrate the changes in the Toyota Car’s environment. The biggest change can be
seen the working method of the staff. The whole paper based works will be replaced with
automated processes. In order to cope with the change, the users of the system will be trained
during the project lifecycle.

2SYSTEM ANALYSIS AND DESIGN
Table of Contents
Introduction: 3
TASK 1: Time Management Plan: 3
TASK 2: “TO BE” Process 7
Task 3: Comparing “AS IS” and “TO BE” Process 7
Task 4: Entity Relationship Diagram 8
Task 5: Data Normalization 8
TASK 6: Testing 16
TASK 7: Training 16
TASK 8: System Changeover 16
TASK 9: Report to Top Management 17
Conclusion: 18
Bibliography: 19

3SYSTEM ANALYSIS AND DESIGN
Introduction:
SAP is the abbreviation of Systems Applications and Products within the domain of Data
Processing. The SAP ISs are consist of various completely integrated software modules. These
software modules are designed for supporting every aspect of business virtually. The ERP is the
ICT product that is implemented in an organization for supporting business process management.
Business process change is done within an organization to implement significant improvement in
productivity.
The report represent the business processes change, change handling process, database of
product sale and invoice generation and project time line based on the case study of Toyota Cars.
The To-Be process signifies which parts of the organization will be improved to support
proposed changes. The ERD shows the insight basic database structure.
TASK 1: Time Management Plan:
Task Name Duratio
n Start Finish Predecessor
s
Resource
Names Cost
SAP Implementation 124 days Thu
5/24/18
Tue
11/13/18 $10,840.00
Planning 19 days Thu
5/24/18
Tue
6/19/18 $1,888.00
Problem Definition 3 days Thu
5/24/18
Mon
5/28/18
Project
Manager $288.00
Project Charter
Development 3 days Tue
5/29/18
Thu
5/31/18 2 Project
Manager $288.00
Project Staff
Employment 4 days Fri 6/1/18 Wed
6/6/18 3 Project
Manager $384.00
Selection of SDLC
Model or Software
Development Life Cycle
1 day Thu
6/7/18
Thu
6/7/18 4
Analyst,
Project
Manager
$160.00
Project Schedule
Development 2 days Fri 6/8/18 Mon
6/11/18 5 Project
Manager $192.00
Project Budgeting 4 days Tue Fri 6 Project $384.00

4SYSTEM ANALYSIS AND DESIGN
6/12/18 6/15/18 Manager
Allocate Resources
Planning 2 days Mon
6/18/18
Tue
6/19/18 7 Project
Manager $192.00
Planning Phase
Complete 0 days Tue
6/19/18
Tue
6/19/18 8 $0.00
System Analysis and
Requirements 22 days Wed
6/20/18
Thu
7/19/18 $1,792.00
Identification of
Business Requirements 4 days Wed
6/20/18
Mon
6/25/18 9 Analyst $256.00
Identification of
System Requirement 3 days Tue
6/26/18
Thu
6/28/18 11 Analyst $192.00
Identification of User
Requirement 2 days Fri
6/29/18
Mon
7/2/18 12 Analyst $128.00
Verify Requirements 4 days Tue
7/3/18 Fri 7/6/18 13
Analyst,
Project
Manager
$640.00
Evaluating
Requirement 4 days Mon
7/9/18
Thu
7/12/18 14 Analyst $256.00
Documentation of
Requirement 5 days Fri
7/13/18
Thu
7/19/18 15 Analyst $320.00
System Analysis
Phase Complete 0 days Thu
7/19/18
Thu
7/19/18 16 $0.00
Entire System Design 41 days Fri
7/20/18
Fri
9/14/18 $3,088.00
Architecture
Designing of UK Library
Online System
4 days Fri
7/20/18
Wed
7/25/18 17 System
Designer $224.00
UML Diagrams
Designing 5 days Thu
7/26/18
Wed
8/1/18 19 System
Designer $280.00
Unit Design 2 days Thu
7/26/18
Fri
7/27/18 19 $0.00
Database Design 13 days Thu
8/2/18
Mon
8/20/18 $1,352.00
Selection of
Attributes and Entities 3 days Thu
8/2/18
Mon
8/6/18 20
SAP
Database
Developer,
System
Designer
$480.00
Schema Diagram
Creation 3 days Tue
8/7/18
Thu
8/9/18 23 System
Designer $168.00
Generate Entity
Relationship Diagram or
ERD
4 days Fri
8/10/18
Wed
8/15/18 24 System
Designer $224.00
Database 3 days Thu Mon 25 SAP $480.00

5SYSTEM ANALYSIS AND DESIGN
Normalization 8/16/18 8/20/18
Database
Developer,
System
Designer
SAP Design 12 days Tue
8/21/18
Wed
9/5/18 $840.00
User Interaction
Designing 4 days Tue
8/21/18
Fri
8/24/18 26 SAP
Designer $256.00
User Interface
Designing 5 days Mon
8/27/18
Fri
8/31/18 28 SAP
Designer $320.00
Functionality
Confirmation 3 days Mon
9/3/18
Wed
9/5/18 29 SAP
Developer $264.00
Network Diagram
Designing 2 days Thu
9/6/18 Fri 9/7/18 30 System
Designer $112.00
Network Design 5 days Mon
9/10/18
Fri
9/14/18 31 System
Designer $280.00
Completion of
Designing Phase 0 days Fri
9/14/18
Fri
9/14/18 32 $0.00
Development 41 days Mon
9/17/18
Mon
11/12/18 $3,912.00
Implement SAP 18 days Mon
9/17/18
Wed
10/10/18 33 SAP
Developer $1,584.00
Implement Unit
Application 12 days Thu
10/11/18
Fri
10/26/18 35 Coder $1,248.00
Implement Database 7 days Mon
10/29/18
Tue
11/6/18 36
SAP
Database
Developer
$728.00
Implement Network 4 days Wed
11/7/18
Mon
11/12/18 37 SAP
Developer $352.00
Complete of
Development 0 days Mon
11/12/18
Mon
11/12/18 38 $0.00
Deployment 1 day Tue
11/13/18
Tue
11/13/18 $160.00
Go Live 1 day Tue
11/13/18
Tue
11/13/18 39
Analyst,
Project
Manager
$160.00
Deployment
Completion 0 days Tue
11/13/18
Tue
11/13/18 41 $0.00

6SYSTEM ANALYSIS AND DESIGN
ID Task
Mode
WBS Task Name Duration Start Finish Predecessors
0 0 SAP Implementation 124 days Thu 5/24/18 Tue 11/13/18
1 1 Planning 19 days Thu 5/24/18 Tue 6/19/18
2 1.1 Problem Definition 3 days Thu 5/24/18 Mon 5/28/18
3 1.2 Project Charter Development 3 days Tue 5/29/18 Thu 5/31/18 2
4 1.3 Project Staff Employment 4 days Fri 6/1/18 Wed 6/6/18 3
5 1.4 Selection of SDLC Model or Software Development Life Cycle1 day Thu 6/7/18 Thu 6/7/18 4
6 1.5 Project Schedule Development 2 days Fri 6/8/18 Mon 6/11/18 5
7 1.6 Project Budgeting 4 days Tue 6/12/18 Fri 6/15/18 6
8 1.7 Allocate Resoruces Planning 2 days Mon 6/18/18 Tue 6/19/18 7
9 1.8 Planning Phase Complete 0 days Tue 6/19/18 Tue 6/19/18 8
10 2 System Analysis and Requirements 22 days Wed 6/20/18 Thu 7/19/18
11 2.1 Identification of Business Requirements 4 days Wed 6/20/18 Mon 6/25/18 9
12 2.2 Identification of System Requirement 3 days Tue 6/26/18 Thu 6/28/18 11
13 2.3 Identification of User Requirement 2 days Fri 6/29/18 Mon 7/2/18 12
14 2.4 Verify Requirements 4 days Tue 7/3/18 Fri 7/6/18 13
15 2.5 Evaluating Requirement 4 days Mon 7/9/18 Thu 7/12/18 14
16 2.6 Documentation of Requirement 5 days Fri 7/13/18 Thu 7/19/18 15
17 2.7 System Analysis Phase Complete 0 days Thu 7/19/18 Thu 7/19/18 16
18 3 Entire System Design 41 days Fri 7/20/18 Fri 9/14/18
19 3.1 Architecture Designing of UK Library Online System 4 days Fri 7/20/18 Wed 7/25/18 17
20 3.2 UML Diagrams Designing 5 days Thu 7/26/18 Wed 8/1/18 19
21 3.3 Unit Design 2 days Thu 7/26/18 Fri 7/27/18 19
22 3.4 Database Design 13 days Thu 8/2/18 Mon 8/20/18
23 3.4.1 Selection of Attributes and Entities 3 days Thu 8/2/18 Mon 8/6/18 20
24 3.4.2 Schema Diagram Creation 3 days Tue 8/7/18 Thu 8/9/18 23
25 3.4.3 Generate Entity Relationship Diagram or ERD 4 days Fri 8/10/18 Wed 8/15/18 24
26 3.4.4 Database Normalizaion 3 days Thu 8/16/18 Mon 8/20/18 25
27 3.5 SAP Design 12 days Tue 8/21/18 Wed 9/5/18
28 3.5.1 User Interaction Designing 4 days Tue 8/21/18 Fri 8/24/18 26
29 3.5.2 User Interface Designing 5 days Mon 8/27/18 Fri 8/31/18 28
30 3.5.3 Functionality Confirmation 3 days Mon 9/3/18 Wed 9/5/18 29
31 3.6 Network Diagram Designing 2 days Thu 9/6/18 Fri 9/7/18 30
32 3.7 Network Design 5 days Mon 9/10/18 Fri 9/14/18 31
33 3.8 Completion of Designing Phase 0 days Fri 9/14/18 Fri 9/14/18 32
34 4 Development 41 days Mon 9/17/18 Mon 11/12/18
35 4.1 Implement SAP 18 days Mon 9/17/18 Wed 10/10/18 33
36 4.2 Implement Unit Application 12 days Thu 10/11/18 Fri 10/26/18 35
37 4.3 Implement Database 7 days Mon 10/29/18 Tue 11/6/18 36
38 4.4 Implement Network 4 days Wed 11/7/18 Mon 11/12/18 37
39 4.5 Complete of Development 0 days Mon 11/12/18 Mon 11/12/18 38
40 5 Deployment 1 day Tue 11/13/18 Tue 11/13/18
41 5.1 Go Live 1 day Tue 11/13/18 Tue 11/13/18 39
42 5.2 Deployment Completion 0 days Tue 11/13/18 Tue 11/13/18 41
Project Manager
Project Manager
Project Manager
Analyst,Project Manager
Project Manager
Project Manager
Project Manager
6/19
Analyst
Analyst
Analyst
Analyst,Project Manager
Analyst
Analyst
7/19
System Designer
System Designer
SAP Database Developer,System Designer
System Designer
System Designer
SAP Database Developer,System Designer
SAP Designer
SAP Designer
SAP Developer
System Designer
System Designer
9/14
SAP Developer
Coder
SAP Database Developer
SAP Developer
11/12
Analyst,Project Manager
11/13
M J J A S O N D
Half 1, 2018 Half 2, 2018
Figure 1: Gantt Chart of SAP Development
(Source: Created by Author)
Figure 2: Work Breakdown Structure of Proposed Project
(Source: Created by Author)

7SYSTEM ANALYSIS AND DESIGN
TASK 2: “TO BE” Process
Task 3: Comparing “AS IS” and “TO BE” Process
The modified business processes will be greatly scalable and adaptive. The proposed
SAP system will carry out most of the back office processes automatically. The business
processes will be depended upon automated systems. The system will gather and retrieve the
required data easily. This will eliminate the hassle of paperwork. Thus, the staff will be able to
concentrate on his works properly.

8SYSTEM ANALYSIS AND DESIGN
Task 4: Entity Relationship Diagram
Figure 4: Entity Relationship Diagram
(Source: Created by Author)
Task 5: Data Normalization
Table: Payment
Attribute Constraint Data Type
Payment_ID Primary Key Varchar (40)
Payment_Date Varchar (40)
Payment_Amount Varchar (40)
Invoice_Date Varchar (40)
Invoice_Amount Varchar (40)
Order_Quantity Varchar (40)

9SYSTEM ANALYSIS AND DESIGN
Order_Date Varchar (40)
Order_Amount Varchar (40)
Model Varchar (40)
Make Varchar (40)
Manufacturer Varchar (40)
Cost Varchar (40)
License_number Varchar (40)
Name Varchar (40)
Address Varchar (40)
Contact Varchar (40)
Card_Holder_Name Varchar (40)
Number Varchar (40)
CVV Varchar (40)
Expiery_Date Varchar (40)
First Normal Form: In order to be in the first normal form, the database tables must not
have any multivalued attribute. The following database table is consisting of single valued
attributes.

10SYSTEM ANALYSIS AND DESIGN
Table: Payment
Attribute Constraint Data Type
Payment_ID Primary Key Varchar (40)
Payment_Date Varchar (40)
Payment_Amount Varchar (40)
Invoice_Date Varchar (40)
Invoice_Amount Varchar (40)
Order_Quantity Varchar (40)
Order_Date Varchar (40)
Order_Amount Varchar (40)
Model Varchar (40)
Make Varchar (40)
Manufacturer Varchar (40)
Cost Varchar (40)
License_number Varchar (40)
Name Varchar (40)
Address Varchar (40)

11SYSTEM ANALYSIS AND DESIGN
Contact Varchar (40)
Card_Holder_Name Varchar (40)
Number Varchar (40)
CVV Varchar (40)
Expiery_Date Varchar (40)
Second Normal Form: The second normal form entails that the non-key attributes must
be depended on the primary key only. Make, Manufacturer, Cost, License_number are depended
on the model of the car. Therefore, the new table of car will be like.
Table: Car
Attribute Constraint Data Type
Car_ID Primary Varchar (40)
Model Varchar (40)
Make Varchar (40)
Manufacturer Varchar (40)
Cost Varchar (40)
License_number Varchar (40)

12SYSTEM ANALYSIS AND DESIGN
As the first normal form demands that every table must have a primary key, we have
provided Car_ID as the primary key of Car table.
Customer address and contact number is depended on the customer name. Therefore, the
new customer table will be as following.
Table: Customer
Attribute Constraint Data Type
Cust_ID Primary Varchar (40)
Name Varchar (40)
Address Varchar (40)
Contact Varchar (40)
The Payment table will be as following.
Table: Payment
Attribute Constraint Data Type
Payment_ID Primary Key Varchar (40)
Cust_ID Foreign key, reference to
Customer table
Varchar (40)
Car_ID Foreign key, reference to car Varchar (40)

13SYSTEM ANALYSIS AND DESIGN
table
Payment_Date Date
Payment_Amount Decimal (12,2)
Invoice_Date Date
Invoice_Amount Decimal (12,2)
Order_Quantity Varchar (40)
Order_Date Date
Order_Amount Decimal (12,2)
Card_Holder_Name Varchar (40)
Number Varchar (40)
CVV Varchar (40)
Expiery_Date Varchar (40)
Third Normal Form: In order to be in third normal form, the database tables must not
have any transitive dependency. If we remove the transitive dependency, then the following
tables are discovered.
Table: Payment
Attribute Constraint Data Type

14SYSTEM ANALYSIS AND DESIGN
Payment_ID Primary Key Varchar (40)
Invoice_ID Foreign key, reference to
Invoice table
Varchar (40)
Card_ID Foreign key, reference to
Card table
Varchar (40)
Payment_Date Date
Payment_Amount Decimal (12,2)
Table: Invoice
Attribute Constraint Data Type
Invoice_ID Primary Key Varchar (40)
Invoice_Date Date
Invoice_Amount Decimal (12,2)
Table: Order
Attribute Constraint Data Type
Order_ID Primary Key Varchar (40)

15SYSTEM ANALYSIS AND DESIGN
Cust_ID Foreign key, reference to
Customer table
Varchar (40)
Car_ID Foreign key, reference to car
table
Varchar (40)
Quantity Varchar (40)
Date Date
Amount Decimal (12,2)
Table: Order
Attribute Constraint Data Type
Card_ID Primary Key Varchar (40)
Card_Holder_Name Varchar (40)
Number Varchar (40)
CVV Varchar (40)
Expiery_Date Varchar (40)

16SYSTEM ANALYSIS AND DESIGN
TASK 6: Testing
The system will be tested through black box and white box testing. Other than that
system will be debugged by the programmers themselves in the testing phase. The test team will
test the developed unit and check whether these units are able to carry out desired functions. The
test team will send a document to development team after each test. This document will hold the
information on the outcome of the test. Test will also include the unit testing.
TASK 7: Training
The management of Toyota cars will be trained to see auto generated reports. In addition
to that, they will also generate reports for head of every department. The management will have a
chat section. They will get trained to make full use of chat interface. The staff will be trained to
get required information from the system and input information. The sales team will be trained to
get customer information and inventory details. The inventory staff will get order details from
the system and input the status of delivery. The training will be provided to each team members
twice a week. The content writer will create a manual of the system. This manual will be shared
among all the users.
TASK 8: System Changeover
i. Change Identification: The initial move toward deal with the change is
distinguishing it. The proposed framework will change the entire interior
procedure of The SAP. The correspondence medium, data get to and numerous
different things will change through the course of time. The change will happen
additionally association wide as the information gather, handling and data age
process will increment essentially.

17SYSTEM ANALYSIS AND DESIGN
ii. Presenting a Strong Business Case to Stakeholders: The capable individual will
meet the prerequisite of every single partner. The partners will be furnished with
enough data so that can comprehend the significance of the undertaking and have
confidence in it. They will get measurable and quantitative data on the effect of
proposed change.
iii. Change Planning Arranging is a critical advance toward overseeing change. The
Project Manager of SAP System Development Project will perceive how the
change will influence the present procedure. What's more, the undertaking
supervisor will distinguish the procedures after the framework arrangement. The
PM will design the change administration according to the business target of The
SAP with the goal that change can have best effect on the association. This
arranging will incorporate the end-clients and their advantage.
TASK 9: Report to Top Management
To,
The CEO,
Toyota Cars
Subject: SAP Implementation at Toyota Cars
Sir,
With due regard I need to inform Project Manager that the attempted project is one of
the methods for actualizing computerized forms with Toyota Cars. The Information System will
enter information from all the conceivable sources and create information for business help. The

18SYSTEM ANALYSIS AND DESIGN
project has six stages, for example, arranging, investigation, outline, actualize, test and send. The
extent of the project is to actualize an association wide system that can deal with business
procedures and bolster Toyota's destinations. It is prescribed to PM that System Post
Implementation must be completed appropriately.
Conclusion:
From the above report it can be concluded that SAP implementation will be a huge
advantage to Toyota Cars. The business process change will provide a great advantage to
productivity by automating the back processes. The staff and management of the organization
will be able to concentrate on their core works. Moreover, management will be able to see
accurate and desired data quickly. The whole process is based on the architecture of the system.
The system will be collecting and storing data virtually, thus eliminating the need of any paper
based works. Moreover, the organization will be able to store data as long as they require.

19SYSTEM ANALYSIS AND DESIGN
Bibliography:
Al-Masree, HK, 2015, ‘Extracting Entity Relationship Diagram (ERD) from relational database
schema’, International Journal of Database Theory and Application, vol. 8, no. 3, pp.15-26.
Barokati, N, Wajdi, N & Barid, M, 2017, ‘Application Design Library With gamification
concept. Jurnal Lentera: Kajian Keagamaan’, Keilmuan dan Teknologi, vol. 3, no. 1, pp.93-102.
Becker, J, Delfmann, P, Eggert, M & Schwittay, S 2012, ‘Generalizability and applicability of
model-based business process compliance-checking approaches—a state-of-the-art analysis and
research roadmap’, Business Research, vol. 5, no. 2, pp.221-247.
Briggs, JA, Wolvetang, EJ, Mattick, JS, Rinn, JL & Barry G 2015, ‘Mechanisms of long non-
coding RNAs in mammalian nervous system development, plasticity, disease, and evolution’,
Neuron, vol. 88, no. 5, pp.861-877.
Bruton, K, Raftery, P, O'Donovan, P, Aughney, N, Keane, MM & O'Sullivan, DTJ 2014,
‘Development and alpha testing of a cloud based automated fault detection and diagnosis tool for
Air Handling Units’, Automation in Construction, vol. 39, pp.70-83.
Byatt, N, Pbert, L, Hosein, S, Swartz, HA, Weinreb, L, Allison, J & Ziedonis, D 2016, ‘PRogram
In Support of Moms (PRISM): development and beta testing’, Psychiatric Services, vol. 67, no.
8, pp.824-826.
Chavan, MM & Dongre, YV 2015, ‘MULTI-NODE DATABASE APPLICATION
DEPLOYMENT ON LAMP ARCHITECTURE’, International Journal of Advances in
Engineering & Technology, vol. 7, no. 6, p.1721.

20SYSTEM ANALYSIS AND DESIGN
de Oliveira, FB, Bartscher, M, Neuschaefer-Rube, U, Tutsch, R & Hiller, J 2017, ‘Creating a
multi-material length measurement error test for the acceptance testing of dimensional computed
tomography systems’, KU Leuven, Leuven iCT, pp.07-09.
Fleming, QW & Koppelman, JM 2016, Earned value project management, Project Management
Institute.
Kerzner, H & Kerzner, HR 2017, Project management: a systems approach to planning,
scheduling, and controlling, John Wiley & Sons.
Sarkar, D, Jana, T & Saha, S, 2015, ‘LMPID: A manually curated database of linear motifs
mediating protein–protein interactions’, Database, 2015.
Schwalbe, K 2015, Information technology project management, Cengage Learning.
Zhai, C & Lafferty, J 2017, ‘A study of smoothing methods for language models applied to ad
hoc information retrieval’, In ACM SIGIR Forum, vol. 51, no. 2, pp. 268-276, ACM.