Developing Achusi System as A Business System Solution for CV.X (Inventory and Sales Subsystem) - Binus e-Thesis

(1)

v

BINUS INTERNATIONAL UNIVERSITAS BINA NUSANTARA

_________________________________________________________________

Major Computer Science Stream Networking Sarjana Komputer Thesis Semester [Even] Year 2006/2007

DEVELOPING ACHUSI SYSTEM AS BUSINESS SYSTEM SOLUTION FOR C.V. X

(SALES, INVENTOR Y, AND ANALYSIS SUBSYSTEM )

Danie Susanto (0700675305)

Abstract

This paper is a summary about our thesis that is about making information system for a consumer goods distributor company. The major problem of the company is the transaction is still done in paper based and incomplete/unorganized historical database.

In making the thesis we are using modified waterfall model as the system development life cycle. Using that SDLC the business software is made including the hardware architecture as the place to run the software. The modules of the software are separated into three parts for the three members of the groups while the other part such as analysis and design is made together by the three members of the group. Those three parts of modules are Inventory and Sales (including sales transaction and analysis) subsystem will be made by Danie Susanto; Accounting (including account receivable and account payable) subsystem will be made by William Hartanto; and Utility, Cost, and Bonus subsystem will be made by Willy Suryadi. Those modules are made on top of C# Language in Windows Form and using Microsoft SQL Server Express as the DBMS.

Besides that, the new business system is made to improve the business process to use the software in day to day transaction. In this new business system, new posts are created such as logistic manager, sales manager, and accounting manager. Another new post are administrator that is intended for inputting the day to day transaction and warehouse person as the man who is responsible for stocks in the warehouse.

By making software, preparing the hardware, and the new system to run the business daily activities, the company’s business process will move one step forward in this information era.

(2)

vi

PREFACE

At the first, I want to thank God for his guidance and blessings so that I can finish the thesis on the schedule with the expected result. This thesis is made as the final duty to graduate from Bina Nusantara University and gain Sarjana Komputer Degree majoring in Computer Science.

One of the purposes of this thesis is to implement what I have learnt during his study in Bina Nusantara University and also learns new things before I start my career.

I would also like to express my gratitude to all of those who have helped me whether it is directly or indirectly in completing this thesis:

• Bina Nusantara University which provides me with the facilities to complete my

thesis.

• Erwien Nurwihatman, M.Kom as my thesis supervisor who always support and

guide us how to make a good thesis until the last moment.

• Ir. Tri A. Budiono. M.I.T., as Head of School of Computer Science, Binus

International, Universitas Bina Nusantara who issues the thesis rules as the guidance for me and team members in developing the thesis.

• Mr. Kiki Purwanto as my project sponsor, the one who gives the requirement,

verifies the system, and shares his business knowledge.

• Mr. Raymondus Kosala Phd., Mr. Yahya H. Msc., Mr. Adrianus Haryo MSCS.,

(3)

vii

• Aida Wiguna, MM. my aunt who shares her knowledge about business.

• All the staff of University of Bina Nusantara who give their support in the thesis

period.

• My family who always give their pray and support.

• My group members who were willing to work with me and helped each other

almost everyday whether it is on campus or in the one of the group member’s house from the start to the end of the thesis period.

• All other friends who have supported and helped me during the thesis

development.

Final words, this thesis is devoted to the company in order to have a better system in day to day transaction and as the example for those who wants to develop information system solution with .NET Programming Language and using Waterfall SDLC.

Jakarta, July 20th, 2007

(4)

viii

LIST OF FIGURES

Figure 2.1 Example of Transaction viewed as a system ... 11

Figure 2.2 IS Cycle ... 12

Figure 2.3 Database elements... 13

Figure 2.4 Components of the database environment ... 15

Figure 2.5 Level of Abstraction in a DBMS ... 17

Figure 2.6 Works_In Relationship Set ... 19

Figure 2.7 An entity relationship diagram for Works_In... 19

Figure 2.8 Departments Table ... 20

Figure 2.9 Un- normalized Table ... 22

Figure 2.10 Comparison of DFD symbol sets... 25

Figure 2.11 Data Flow Diagram... 27

Figure 2.12 Flow Chart Symbols ... 28

Figure 2.13 Class Diagram Symbols... 29

Figure 2.14 Example of Use Case Diagram... 31

Figure 2.15 The layers in the .NET Framework 2.0 ... 34

Figure 2.16 Client-Server Model ... 41

Figure 2.17 Two-tier architecture... 43

Figure 2.18 Types of Client/Server Computing ... 44

Figure 2.19 Phases in waterfall model ... 49

Figure 2.20 Communication Phase ... 50

Figure 2.21 Planning Phase ... 51

Figure 2.22 Requirement Analysis Phase ... 52

Figure 2.23 Design Phase... 53

Figure 2.24 Constructing Phase ... 54

Figure 2.25 Testing Phase ... 55

Figure 3.1 Company Organizational Structure ... 59

Figure 3.2 Context Diagram... 64

Figure 3.3 Level 0 Data Flow Diagram... 65

Figure 3.4 Inventory Level 1 DFD... 66

Figure 3.5 Sales Level 1 DFD... 68

Figure 3.6 Payment Level 1 DFD ... 70

Figure 3.7 Purchasing Level 1 DFD... 72

Figure 3.8 TO Selling Flow Chart... 73

Figure 3.9 OP Selling Flow Chart ... 75

Figure 3.10 Delivering and Product Return Flow Chart ... 77

Figure 3.11 Payment Flow Chart ... 79

Figure 4.1 The New Company Organizational Structure... 86

Figure 4.2 The New Context Diagram ... 90

Figure 4.3 Purchase DFD... 91

Figure 4.4 Sales OP DFD... 93

Figure 4.5 Sales TO DFD... 95

Figure 4.6 Sales Target DFD... 97

(9)

xiii

Figure 4.8 Purchasing Order Flow Chart ... 100

Figure 4.9 Purchase Product Delivery Flow Chart ... 102

Figure 4.10 TO Selling Flow Chart... 104

Figure 4.11 OP Selling Flow Chart ... 106

Figure 4.12 Delivering TO and Returned Product Flow Chart... 108

Figure 4.13 Entity Relationship Diagram ... 137

Figure 4.14 Class Diagram (Part 1 of 4) ... 138

Figure 4.18 Use Case Diagram (Sales Transaction) ... 142

Figure 4.19 Use Case Diagram (Top Urgent) ... 143

Figure 4.20 Use Case Diagram (Purchase Transaction) ... 143

Figure 4.21 Use Case Diagram (Stock Mutation) ... 144

Figure 4.22 Use Case Diagram (Stock Adjust)... 144

Figure 4.23 Use Case Diagram (Stock Amount)... 145

Figure 4.24 Use Case Diagram (Analysis Subsystem) ... 145

Figure 4.25 Login, Unlock Login, and Main Menu State Transition Diagram... 146

Figure 4.26 File Menu State Transition Diagram ... 146

Figure 4.27 Master Menu State Transition Diagram... 146

Figure 4.28 Inventory Menu State Transition Diagram... 147

Figure 4.29 Transaction Menu State Transition Diagram... 147

Figure 4.30 Accounting Menu State Transition Diagram... 147

Figure 4.31 Account Receivable Menu State Transition Diagram ... 148

Figure 4.32 Account Payable Menu State Transition Diagram ... 148

Figure 4.33 Accounting Reports Menu State Transition Diagram (Part 1 of 2) ... 148

Figure 4.34 Accounting Reports Menu State Transition Diagram (Part 2 of 2) ... 148

Figure 4.35 Analysis Menu State Transition Diagram... 149

Figure 4.36 Utility Menu State Transition Diagram ... 149

Figure 4.37 System Topology ... 153

Figure 4.38 User Interface Design 1: Stock Mutation ... 156

Figure 4.39 User Interface Design 2: Stock Adjust ... 156

Figure 4.40 User Interface Design 3: Invoice ... 157

Figure 4.41 User Interface Design 4: Search Product, Search Customer, and Search Supplier ... 157

Figure 4.42 User Interface Design 5: Reports with Search Mode ... 158

Figure 4.43 User Interface Design 6: Reports without Search Mode ... 158

Figure 4.44 User Interface Design 7: Change Top Urgent ... 159

Figure 5.1 Testing Phase ... 160

Figure 6.1 System Layout Diagram for Internal Respondents... 188

Figure 6.2 System Content Awareness Diagram for Internal Respondents ... 189

Figure 6.3 System Aesthetics Diagram for Internal Respondents ... 190

Figure 6.4 System User Experience Diagram for Internal Respondents... 190

Figure 6.5 System Consistency Diagram for Internal Respondents... 191

Figure 6.6 System Minimal User Effort Diagram for Internal Respondents ... 192

Figure 6.7 System Readable Diagram for Internal Respondents ... 192

(10)

xiv

Figure 6.9 System Menu Classification Diagram for Internal Respondents... 194

Figure 6.10 System Usefulness Diagram for Internal Respondents... 194

Figure 6.11 System Layout Diagram for External Respondents... 196

Figure 6.12 System Content Awareness Diagram for External Respondents... 196

Figure 6.13 System Aesthetics Diagram for External Respondents ... 197

Figure 6.14 System User Experience Diagram for External Respondents ... 198

Figure 6.15 System Consistenc y Diagram for External Respondents ... 198

Figure 6.16 System Minimal User Effort Diagram for External Respondents ... 199

Figure 6.17 System Readable Diagram for External Respondents ... 200

Figure 6.18 System Satisfaction Diagram for External Respondents ... 200

Figure 6.19 System Menu Classification Diagram for External Respondents... 201

Figure 6.20 System Usefulness Diagram for External Respondents ... 202

Figure 6.21 Evaluation Conclusion Diagram for Internal Respondents ... 203

Figure 6.22 Evaluation Conclusion Diagram for External Respondents ... 205

(11)

xv

LIST OF TABLES

Table 3.1 Sales Area Schedule ... 58

Table 4.1 Bonuses Entity ... 110

Table 4.2 Building Entity... 111

Table 4.3 Cost Entity... 112

Table 4.4 Customer Entity ... 113

Table 4.5 Employee Entity... 114

Table 4.6 Login Entity ... 115

Table 4.7 Payroll Entity ... 116

Table 4.8 Product Entity... 117

Table 4.9 Purchase_Invoice Entity... 119

Table 4.10 Purchase_Invoice_Detail Entity... 119

Table 4.11 Sales_Invoice Entity... 120

Table 4.12 Sales_Invoice_Detail Entity... 121

Table 4.13 Stored_In Entity... 122

Table 4.14 Supplier Entity ... 123

Table 4.15 Supplier_Has_Product Entity... 123

Table 4.16 Stock_Mutation Entity ... 124

Table 4.17 Stock_Opname Entity ... 125

Table 4.18 Top_Urgent Entity ... 125

Table 4.19 Bonuses Attribute... 128

Table 4.20 Building Attribute ... 129

Table 4.21 Cost Attribute ... 129

Table 4.22 Customer Attribute... 129

Table 4.23 Employee Attribute ... 130

Table 4.24 Login Attribute ... 130

Table 4.25 Payroll Attribute ... 131

Table 4.26 Product Attribute ... 132

Table 4.27 Purchase_Invoice Attribute ... 132

Table 4.28 Purchase_Invoice_Detail Attribute ... 133

Table 4.29 Sales_Invoice Attribute ... 133

Table 4.30 Sales_Invoice_Detail Attribute ... 134

Table 4.31 Stored_In Attribute... 134

Table 4.32 Supplier Attribute ... 134

Table 4.33 Supplier_Has_Product Attribute ... 135

Table 4.34 Stock_Mutation Attribute... 135

Table 4.35 Stock_Opname Attribute... 136

Table 4.36 Top_Urgent Attribute ... 136

Table 5.1 Stock Mutation Module Testing... 164

Table 5.2 Good Stock Adjust Module Testing... 165

Table 5.3 Bad Stock Adjust Module Testing ... 165

Table 5.4 Product Outflow Draft Module Testing ... 166

(12)

xvi

Table 5.6 Bad Stock Report Module Testing... 167

Table 5.7 Good Stock Adjust Report Module Testing... 168

Table 5.8 Bad Stock Adjust Report Module Testing ... 169

Table 5.9 Stock Mutation Report Module Testing... 169

Table 5.10 Stock Adjust List Module Testing ... 170

Table 5.11 Stock Mutation List Module Testing ... 171

Table 5.12 Stock Invoice Module Testing ... 173

Table 5.13 Returned Product Sales Invoice Module Testing... 174

Table 5.14 Purchase Invo ice Module Testing... 176

Table 5.15 Returned Product Purchase Invoice Module Testing... 177

Table 5.16 Product Shipment Monitoring Report Module Testing ... 178

Table 5.17 Reprint Sales Invoice Module Testing... 179

Table 5.18 Purchase Invoice Data Module Testing ... 179

Table 5.19 Sales Summary per Customer Module Testing... 180

Table 5.20 Sales Summary per Product Module Testing... 181

Table 5.21 Sales Mapping Module Testing ... 182

Table 5.22 Stock Necessity Evaluation Report Module Testing ... 183

Table 5.23 Change Top Urgent Module Testing... 184

Table 5.24 Integration Testing ... 186

Table 6.1 System Layout Table for Internal Respondents... 188

Table 6.2 System Content Awareness Table for Internal Respondents ... 189

Table 6.3 System Aesthetics Table for Internal Respondents... 189

Table 6.4 System User Experience Table for Internal Respondents... 190

Table 6.5 System Consistency Table for Internal Respondents... 191

Table 6.6 System Minimal User Effort Table for Internal Respondents ... 191

Table 6.7 System Readable Table for Internal Respondents ... 192

Table 6.8 System Satisfaction Table for Internal Respondents ... 193

Table 6.9 System Menu Classification Table for Internal Respondents... 193

Table 6.10 System Usefulness Table for Internal Respondents... 194

Table 6.11 System Layout Table for External Respondents ... 195

Table 6.12 System Content Awareness Table for External Respondents... 196

Table 6.13 System Aesthetics Table for External Respondents... 197

Table 6.14 System User Experience Table for External Respondents... 197

Table 6.15 System Consistency Table for External Respondents... 198

Table 6.16 System Minimal User Effort Table for External Respondents ... 199

Table 6.17 System Readable Table for External Respondents ... 199

Table 6.18 System Satisfaction Table for External Respondents ... 200

Table 6.19 System Menu Classification Table for External Respondents ... 201

Table 6.20 System Usefulness Table for External Respondents... 202

Table 6.21 Evaluation Conclusion Table for Internal Respondents... 202

Table 6.22 Evaluation Conclusion Table for External Respondents ... 205

Table 6.23 Evaluation Conclusion Table for All Respondents ... 207

Developing Achusi System as A Business System Solution for CV.X (Inventory and Sales Subsystem) - Binus e-Thesis

Abstract

PREFACE

TABLE OF CONTENTS

LIST OF FIGURES

LIST OF TABLES