BAB 4 PERANCANGAN SISTEM 4.1 Activity Diagram Activity Diagram digambarkan untuk menjelaskan alur dari proses bisnis yang diusulkan. Dimulai dari Non Member mendaftar sampai pengetahuan diperoleh karyawan (Employee). Gambar 4.1 Activity Diagram 84
85 4.2 Event Table Event table dibawah ini diperoleh dari proses bisnis usulan yang telah digambarkan pada bab 3. Event Table menggambarkan user (Actor) yang berhubungan dengan sistem, alur datanya dan penyebab terjadinya event tersebut. Tabel 4.1 Event Table No Event Trigger Source Use Case Response Destination 1 Non-Member Non- Non- Melakukan Notification Admin melakukan Sign Up Member dapat menjadi member Member Sign Up 2 Member Member Member Membuat ide Ide Admin membuat ide dapat memberikan ide 3 Member atau Member Member Menulis Comment - Admin menulis comment atau Admin dapat memberikan komentar atau Admin comment 4 Member Member Member Memberikan Suggestion Admin Memberikan Suggestion memberikan kritik dan saran yang diterima admin Suggestion 5 Member Merubah Profile Merubah profile sesuai dengan ketentuan Member Merubah Member Profile Profile Admin
6 Admin merubah Profile 7. Admin membuka member control 8. Member atau Admin membuat article 9 Admin merespon ide 10. Admin membuat kategori Merubah profile sesuai ketentuan yang ada Memastikan data pelanggan benar dan valid Member atau Admin memberikan informasi di article Member mengetahui respon dan Admin memberikan status terhadap ide Ada kategori baru 86 Admin Merubah Profile - Admin Profile Data Membuka Notification Member Pelanggan Member Control Member Membuat Article Member atau article Admin Admin Merespon ide Responded - Idea Admin Membuat Kategori - kategori 11. Admin Ada sub Admin Membuat sub Sub - membuat sub kategori kategori Kategori kategori baru 12. Admin Telah keluar Admin Mencatat Product Member mencatat produk baru produk knowledge produk baru
87 13. Admin Mengetahui Admin Membuat Laporan - membuat jumlah laporan member laporan member member member terdaftar setiap bulan 14. Admin Mengetahui Admin Membuat Laporan ide - membuat proses ide- laporan ide laporan ide ide dari pelanggan tiap bulan 15. Employee Mencari dan Employee Melihat View Ideas - melihat Mengetahui knowledge knowledge pengetahuan dari pelanggan
88 4.3 Use case and Domain Classes 4.3.1 Use Case Diagram Use case diagram menjelaskan interaksi antara user dengan sistem yang didapatkan dari hasil event table. Terdapat 15 event dan 4 aktor yang berperan dalam menjalankannya.
89 Gambar 4.2 Use Case Diagram 4.3.2 Use Case Description Use case description menjelaskan detail proses dari use case diagram yang disusun berupa list. Tabel 4.2 Use Case Description : Melakukan Sign Up Name Use Case : Melakukan Sign Up Main Flow : 1. Non-Member membuka menu Sign Up. 2. Non-Member mengisi username. 3. Non-Member mengisi password. 4. Non-Member mengulangi password yang diisi. 5. Non-Member mengisi e-mail. 6. Non-Member mengisi Fullname. 7. Non-Member memilih gender. 8. Non-Member mengisi date of birth. 9. Non-Member mengisi address. 10. Non-Member mengisi phone number. 11. Non-Member meng-upload hasil scan identity card. Exception Condition : -
90 Tabel 4.3 Use Case Description: Membuat ide Name Use Case : Membuat ide Main Flow : 1. Member membuka menu share idea. 2. Member mengisi title dari ide yang akan di buat. 3. Member memilih category yang sudah disediakan. 4. Member mengisi description dari ide. 5. Member meng-upload image jika ada. 6. Member juga dapat melakukan search ide. Exception Condition : - Tabel 4.4 Use Case Description: Menulis Comment Name Use Case : Menulis Comment Main Flow : 1. Member atau admin memilih salah satu judul ide. 2. Member atau admin otomatis masuk ke halaman idea comment. 3. Member atau admin memberikan comment terhadap ide. 4. Member atau admin melakukan share comment. 5. Member atau admin dapat melakukan like atau dislike pada ide tersebut. Exception Condition : 3. Jika member tidak bisa memberikan comment Member harus melakukan log in terlebih dahulu. Member harus memilih judul ide dan article.
91 Tabel 4.5 Use Case Description: Memberikan Suggestion Name Use Case : Memberikan Suggestion Main Flow : 1. Member membuka menu Suggestion. 2. Member mengisi kritik dan saran pada kotak dialog yang disediakan. 3. Member melakukan submit suggestion tersebut. Exception Condition : - Tabel 4.6 Use Case Description : Merubah member profile Name Use Case : Merubah member profile Main Flow : 1. Member membuka menu member profile. 2. Member memilih menu edit profile. 3. Member dapat mengganti address. 4. Member dapat mengganti phone. 5. Member dapat mengganti e-mail. 6. Member dapat merubah picture. 7. Member dapat merubah password pada menu change password. Exception Condition : -
92 Tabel 4.7 Use Case Description: Merubah admin profile Name Use Case : Merubah admin profile Main Flow : 1. Admin membuka menu admin profile. 2. Admin dapat merubah picture. 3. Admin dapat merubah password pada menu change password. Exception Condition : - Tabel 4.8 Use Case Description: Membuat article Name Use Case : Membuat article Main Flow : 1. Member atau admin membuka menu share article. 2. Member atau admin mengisi title dari article yang akan di buat. 3. Member atau admin memilih category yang sudah disediakan. 4. Member atau admin mengisi description dari article. 5. Member atau admin meng-upload image jika ada. 6. Member atau admin juga dapat melakukan search article. Exception Condition : -
93 Tabel 4.9 Use Case Description: Membuka Member control Name Use Case : Membuka Member control Main Flow : 1. Admin membuka menu member control. 2. Admin melihat daftar member yang akan di validasi. 3. Admin memilih data member yang valid dengan meng-klik tombol approve. 4. Member yang valid pindah ke dalam daftar approved member. 5. Admin dapat melakukan pencarian member. 6. Admin dapat menghapus member yang telah terdaftar. Exception Condition : - Tabel 4.10 Use Case Description: Merespon ide Name Use Case : Merespon ide Main Flow : 1. Admin membuka menu response ideas. 2. Admin memilih judul ide member. 3. Admin memilih status ide. 4. Admin memberikan comment terhadap ide dari member. Exception Condition : -
94 Tabel 4.11 Use Case Description: Membuat Kategori Name Use Case : Membuat Kategori Main Flow : 1. Admin membuka menu new category. 2. Admin memasukkan nama kategori baru. Exception Condition : - Tabel 4.12 Use Case Description: Membuat Sub Kategori Name Use Case : Membuat Sub Kategori Main Flow : 1. Admin membuka menu new category. 2. Admin memilih kategori. 3. Admin memasukkan nama sub kategori baru. Exception Condition : -
95 Tabel 4.13 Use Case Description: Mencatat Produk Name Use Case : Mencatat Produk Main Flow : 1. Admin membuka menu new product. 2. Admin memasukkan nama produk. 3. Admin memilih kategori. 4. Admin memilih sub kategori. 5. Admin mengisi keterangan produk. 6. Admin upload gambar produk. Exception Condition : - Tabel 4.14 Use Case Description: Membuat laporan member Name Use Case : Membuat laporan member Main Flow : 1. Admin membuka menu ideas report. 2. Admin memilih tahun. 3. Admin melihat member report. 4. Admin dapat mencetak member report. Exception Condition : -
96 Tabel 4.15 Use Case Description: Membuat laporan ide Name Use Case : Membuat laporan ide Main Flow : 1. Admin membuka menu ideas report. 2. Admin memilih tahun. 3. Admin melihat ideas traffic. 4. Admin melihat responded ideas data. 5. Admin dapat mencetak ideas traffic dan responded ideas data. Exception Condition : - Tabel 4.16 Use Case Description: Melihat Knowledge Name Use Case : Melihat Ide Main Flow : 1. Employee membuka View Knowledge. 2. Employee melalukan pencarian pengetahuan sesuai dengan yang diinginkan. 3. Employee melihat pengetahuan sesuai dengan kategori yang tersedia. Exception Condition : -
97 4.3.3 Domain Model Class Diagram Domain model class diagram menunjukkan hal-hal penting bagi pekerjaan user. Tiap class hanya terdiri dari atribut, class dan atribut didapatkan dari proses dalam sistem. Antar class dihubungkan dengan multiplicity. Pada domain model class diagram tidak disertakan method. Gambar 4.3 Domain Model Class Diagram
98 4.3.4 State Machine Diagram State machine diagram menjelaskan state/status pada tiap class. Jadi tiap class memiliki hasil operation yang telah dikerjakan pada sistem. Gambar 4.4 State Machine Diagram: Member Gambar 4.5 State Machine Diagram: ide
99 Gambar 4.6 State Machine Diagram: Article Gambar 4.7 State Machine Diagram: Komentar Gambar 4.8 State Machine Diagram: Suggestion
100 Gambar 4.9 State Machine Diagram: Admin Gambar 4.10 State Machine Diagram: Responded Ideas Gambar 4.11 State Machine Diagram: Produk
101 Gambar 4.12 State Machine Diagram: Category Gambar 4.13 State Machine Diagram: Sub Category Gambar 4.14 State Machine Diagram: Employee
102 4.4 The Design Discipline 4.4.1 Use Case Realization 4.4.1.1 Design Class Diagram Design class diagram merupakan penyempurnaan dari domain class diagram. Dalam class diagram ini ditambahkan method pada tiap class menunjukkan informasi yang dikerjakan pada sistem.
103 Gambar 4.15 Design Class Diagram 4.4.1.2 First Cut Design Class Diagram First cut design class diagram merupakan pengembangan dari domain class diagram. Pada class diagram ini tidak perlu method dan menggunakan navigation visibility.
Gambar 4.16 First Cut Design Class Diagram 104
105 4.4.1.3 System Sequence Diagram Setelah pembuatan Use Case Diagram dan Class Diagram, maka dibuatlah System Sequence Diagram (SSD). SSD dibuat untuk menggambarkan proses hubungan Actor dengan System pada setiap Use Case. Gambar 4.17 System Sequence Diagram: Sign Up Gambar 4.18 System Sequence Diagram: Edit member
106 Gambar 4.19 System Sequence Diagram: Share idea Gambar 4.20 System Sequence Diagram: Comment
107 Gambar 4.21 System Sequence Diagram: Edit admin profile Gambar 4.22 System Sequence Diagram: Suggestion
108 Gambar 4.23 System Sequence Diagram: Article Gambar 4.24 System Sequence Diagram: Response Idea
109 Gambar 4.25 System Sequence Diagram: Member Control Gambar 4.26 System Sequence Diagram: Product Knowledge
110 Gambar 4.27 System Sequence Diagram: Category Gambar 4.28 System Sequence Diagram: Sub Category
111 Gambar 4.29 System Sequence Diagram: Member report Gambar 4.30 System Sequence Diagram: Idea report
Gambar 4.31 System Sequence Diagram: View Knowledge 112
113 4.4.1.4 First Cut Sequence Diagram First Cut Sequence Diagram digambarkan setelah System Sequence Diagram. First Cut Sequence Diagram digambarkan untuk menjelaskan hubungan actor dengan handler dari setiap usecase dan object class nya. First cut Sequence Diagram: Sign Up Gambar 4.32 First Cut Sequence Diagram: Sign Up
114 First cut Sequence Diagram: Edit Member Gambar 4.33 First Cut Sequence Diagram: Edit Member
115 First cut Sequence Diagram: Share Idea Gambar 4.34 First Cut Sequence Diagram: Share idea
116 First cut Sequence Diagram: Comment Gambar 4.35 First Cut Sequence Diagram: Comment
117 First cut Sequence Diagram: Edit admin profile Gambar 4.36 First Cut Sequence Diagram: Edit admin profile
118 First cut Sequence Diagram: Suggestion Gambar 4.37 First Cut Sequence Diagram: Suggestion
119 First cut Sequence Diagram: Article Gambar 4.38 First Cut Sequence Diagram: Article
120 First cut Sequence Diagram: Response Idea Admin :add_new_response_idea_ handler :Ide add_new_respon_ide(id_iderespond) :Admin create_new_respon_ide(id_iderespond) :Idea responded get_ide(id_ide) description(judul, tgl, deskripsi, image) get_admin(id_admin)) description(username) add_status(status_respond) add_status(status_respond) add_response(admin_comment) add_response(admin_comment) save() save() Gambar 4.39 First Cut Sequence Diagram: Response idea
121 First cut Sequence Diagram: Member control Gambar 4.40 First Cut Sequence Diagram: Member control
122 First cut Sequence Diagram: Produk Gambar 4.41 First Cut Sequence Diagram: Idea report
123 First cut Sequence Diagram: Category Gambar 4.42 First Cut Sequence Diagram: Category
124 First cut Sequence Diagram: Sub Category Gambar 4.43 First Cut Sequence Diagram: Sub Category
125 First cut Sequence Diagram: Member Report Gambar 4.44 First Cut Sequence Diagram: Member report First cut Sequence Diagram: Idea Report
126 Gambar 4.45 First Cut Sequence Diagram: Idea report First cut Sequence Diagram: View Knowledge Gambar 4.46 First Cut Sequence Diagram: View Knowledge
127 4.4.1.5 Data Access Sequence Diagram Data Access Sequence Diagram digambarkan setelah First Cut Sequence Diagram. Data Access Sequence Diagram digambarkan untuk menjelaskan hubungan actor dengan handler, object class, dan Data Access dari setiap object. Data Access Sequence Diagram:Sign Up Gambar 4.47 Data Access Sequence Diagram: Sign Up
128 Data Access Sequence Diagram:Edit Member Gambar 4.48 Data Access Sequence Diagram: Edit Member
129 Data Access Sequence Diagram:Share Idea Gambar 4.49 Data Access Sequence Diagram: Share idea
130 Data Access Sequence Diagram:Comment Gambar 4.50 Data Access Sequence Diagram: Comment
131 Data Access Sequence Diagram:Edit admin profile Gambar 4.51 Data Access Sequence Diagram: Edit admin profile
132 Data Access Sequence Diagram:Suggestion Gambar 4.52 Data Access Sequence Diagram: Suggestion
133 Data Access Sequence Diagram:Article Gambar 4.53 Data Access Sequence Diagram: Article
134 Data Access Sequence Diagram:Response idea Gambar 4.54 Data Access Sequence Diagram: Response idea
135 Data Access Sequence Diagram:Member Control Gambar 4.55 Data Access Sequence Diagram: Member control
136 Data Access Sequence Diagram: Produk Gambar 4.56 Data Access Sequence Diagram: Produk
137 Data Access Sequence Diagram:Category Gambar 4.57 Data Access Sequence Diagram: Category
138 Data Access Sequence Diagram:Sub Category Gambar 4.58 Data Access Sequence Diagram: Sub Category
139 Data Access Sequence Diagram:Member report Gambar 4.59 Data Access Sequence Diagram: Member report
140 Data Access Sequence Diagram:Idea report Gambar 4.60 Data Access Sequence Diagram: Idea report
141 Data Access Sequence Diagram:View Knowledge Gambar 4.61 Data Access Sequence Diagram: View Knowledge
142 4.4.1.6 View Layer Sequence Diagram View Layer Sequence Diagram adalah penggambaran Sequence yang paling lengkap, digambarkan setelah Data Access Sequence Diagram. View Layer Sequence Diagram digambarkan untuk menjelaskan hubungan actor dengan Boundary, handler, object class, dan Data Access nya dari setiap object. View Layer Sequence Diagram : Sign Up Gambar 4.62 View Layer Sequence Diagram: Sign Up
143 View Layer Sequence Diagram : Edit Member Profile Gambar 4.63 View Layer Sequence Diagram: Edit Member Profile
144 View Layer Sequence Diagram : Share Idea Gambar 4.64 View Layer Sequence Diagram: Share Idea
145 View Layer Sequence Diagram : Comment Gambar 4.65 View Layer Sequence Diagram: Comment
146 View Layer Sequence Diagram : Suggestion Gambar 4.66 View Layer Sequence Diagram: Suggestion
147 View Layer Sequence Diagram : Edit Admin Profile Gambar 4.67 View Layer Sequence Diagram: Edit admin profile
148 View Layer Sequence Diagram : Article Gambar 4.68 View Layer Sequence Diagram: Article
149 View Layer Sequence Diagram : Response Ideas Gambar 4.69 View Layer Sequence Diagram: Response Idea
150 View Layer Sequence Diagram : Member Control Gambar 4.70 View Layer Sequence Diagram: Member control
151 View Layer Sequence Diagram:Produk Gambar 4.71 View Layer Sequence Diagram: Produk
152 View Layer Sequence Diagram:Category Gambar 4.72 View Layer Sequence Diagram: Category
153 View Layer Sequence Diagram:Sub Category Gambar 4.73 View Layer Sequence Diagram: Sub Category
154 View Layer Sequence Diagram : Member Report Gambar 4.74 View Layer Sequence Diagram: Member report
155 View Layer Sequence Diagram : Idea Report Gambar 4.75 View Layer Sequence Diagram: Idea report
156 View Layer Sequence Diagram:View Knowledge Gambar 4.76 View Layer Sequence Diagram: View Knowledge
157 4.4.1.7 Communication Diagram Communication Diagram digambarkan untuk menjelaskan Method yang digunakan pada setiap handler dan object class. Communication Diagram dibuat berdasarkan pada First Cut Sequence Diagram. Sign Up Gambar 4.77 Communication Diagram: Sign Up Edit member Profile Gambar 4.78 Communication Diagram: Edit member profile
158 Share Idea Gambar 4.79 Communication Diagram: Share idea Comment Gambar 4.80 Communication Diagram: Comment
159 Edit Admin Profile Gambar 4.81 Communication Diagram: Edit admin profile Suggestion Gambar 4.82 Communication Diagram: Suggestion
160 Article Gambar 4.83 Communication Diagram: Article Response Ideas Gambar 4.84 Communication Diagram: Response Idea
161 Member Control Gambar 4.85 Communication Diagram: Member control Produk Gambar 4.86 Communication Diagram: Produk
162 Category Gambar 4.87 Communication Diagram: Category Sub Category Gambar 4.88 Communication Diagram: Sub Category
163 Member Report Gambar 4.89 Communication Diagram: Member Report Idea Report Gambar 4.90 Communication Diagram: Idea Report
164 View Knowledge Gambar 4.91 Communication Diagram: View Knowledge
165 4.4.1.8 Update Class Diagram Update Class Diagram adalah penggambaran Class Diagram yang paling lengkap dan kompleks. Update Class Diagram adalah pengembangan dari First Cut Class Diagram. Method dari setiap handler dan Object Class didapat dari Communication Diagram.
166 Gambar 4.92 Update Class Diagram 4.4.1.9 Package Diagram Di bawah ini gambar Package Diagram : View Layer Login MainWindow Share_idea Share_article Suggestion Member_control Sign Up Comment View_Knowledge Response_idea New_Product New_Category Member Edit_Member Admin Edit_admin_profile Idea_report Member_report Domain Layer Login MainMenu Article Suggestion SubCategory Sign Up Member Ide Komentar Add_new_member_handler Employee IdeaResponded Admin Start_edit_member_ Profile_handler Category Add_new_produk _handler Produk View_knowledge_ handler Add_new_ide_handler Add_new_article_ handler Add_new_komentar_handler Add_new_response_ idea_handler Start_edit_admin_ profile_handler Start_edit_member_control_ handler Add_new_category _handler Add_new_suggestion_ handler Print_laporan_member_ handler Print_laporan_ide_handler Add_new_category_ handler Add_new_subcategory_ handler Data Access Layer MemberDA AdminDA IdeDA ArticleDA ProdukDA KomentarDA SuggestionDA CategoryDA SubCategoryDA IdeaRespondedDA EmployeeDA Gambar 4.93 Package Diagram
167 4.4.2 Design Activities and Environment 4.4.2.1 Deployment Environment Multi Computer : Aplikasi ini terdiri dari beberapa user yang dapat membuka semua aplikasi secara bersamaan. Non Member dan Member dapat membuka dimana saja mengingat aplikasi ini diperuntukkan untuk customer. Kemudian Admin dan Karyawan dapat mengakses secara online mengingat perusahaan mempunyai beberapa cabang yang tersebar tidak di semua kota. Semua jenis hardware computer memiliki spesifikasi yang berbeda pada setiap user. Gambar 4.94 Deployment Environment
168 4.4.2.2 Deployment Architecture Centralized architecture : Letak server terdapat pada 1 tempat yaitu di perusahaan pada cabang Jakarta. Server yang digunakan terpusat mengingat supaya data yang diperoleh selalu real time dan penyebaran data nya sendiri lebih optimal. Gambar 4.95 Deployment Architecture
169 4.4.2.3 Software Architecture Three Layer : Aplikasi ini menggunakan tiga layer yaitu View Layer, Business Logic Layer dan Data Layer. Aplikasi dan database terdapat pada server yang berbeda. Dengan tujuan lebih mudah dalam pengelolaan server dan data yang dimiliki lebih aman. Gambar 4.96 Software Architecture
170 4.5 Struktur Tabel Tabel 4.17 Struktur Tabel Member Field Type Size Null Key Id_member Varchar 10 No Primary key Username_member Varchar 30 No - Password_member Varchar 20 No - Email_member Varchar 50 No - Nama_member Varchar 500 No - Kelamin_member Varchar 10 No - TglLahir_member Varchar 100 No - Alamat_member Varchar 500 No - Telp_member int 15 No - Tgl_daftar Date - No - Identity_member Image - No - Status_approve Varchar 10 No - Tgl_approve Date - Yes - Foto_profile Image - Yes - Tabel 4.18 Struktur Tabel Ide Field Type Size Null Key Id_ide Varchar 10 No Primary Key Id_member Varchar 10 No Foreign Key Id_category Varchar 50 No Foreign Key Id_subCategory Varchar 50 Yes Foreign Key Tgl_ide Date - No - Judul_ide Varchar 500 No - Deskripsi_ide Varchar 1000 No - Like_ide int 11 Yes - Dislike_ide Int 11 Yes - Image_ide Image - Yes - Tabel 4.19 Struktur Tabel Article Field Type Size Null Key Id_article Varchar 10 No Primary key Id_member Varchar 10 No Foreign key Id_admin Varchar 10 No Foreign key Id_category Varchar 50 No Foreign Key Id_subCategory Varchar 50 Yes Foreign Key Tgl_article Date - No - Judul_article Varchar 500 No - Deskripsi_article Varchar 1000 No - Like_article int 11 Yes -
171 Dislike_article Int 11 Yes - Image_article Image - Yes - Tabel 4.20 Struktur Tabel Komentar Field Type Size Null Key Id_komentar Varchar 10 No Primary key Id_ide Varchar 10 No Foreign key Id_article Varchar 10 No Foreign key Id_member Varchar 10 No Foreign key Id_admin Varchar 10 No Foreign key Tgl_komentar Date - No - Isi_komentar Varchar 1000 No - status_komentar Varchar 100 No - Tabel 4.21 Struktur Tabel Suggestion Field Type Size Null Key Id_suggestion Varchar 10 No Primary key Id_member Varchar 10 No Foreign key Id_category Varchar 50 No Foreign Key Id_subCategory Varchar 50 Yes Foreign Key Isi_suggest Varchar 1000 No - Tgl_suggest Date - No - Tabel 4.22 Struktur Tabel Admin Field Type Size Null Key Id_Admin Varchar 10 No Primary key Username_admin Varchar 10 No - Password_admin Varchar 20 No - Foto_admin Image - No - Tabel 4.23 Struktur Tabel Idea Responded Field Type Size Null Key Id_ideRespond Varchar 10 No Primary Key Id_ide Varchar 10 No Foreign Key Id_Admin Varchar 10 No Foreign Key Id_employee Varchar 10 No Foreign Key Tgl_respond Date - No - Status_respond Varchar 100 No - Admin_comment Varchar 1000 No - Rating int 11 Yes -
172 Tabel 4.24 Struktur Tabel Produk Field Type Size Null Key Id_produk Varchar 10 No Primary Key Id_Admin Varchar 10 No Foreign Key Id_category Varchar 50 No Foreign Key Id_subCategory Varchar 50 Yes Foreign Key Nama_produk Varchar 100 No - keterangan_produk Varchar 1000 No - Gambar_produk Image - No - Tabel 4.25 Struktur Tabel Category Field Type Size Null Key Id_category Varchar 50 No Primary Key Id_Admin Varchar 10 No Foreign Key Nama_category Varchar 100 No - Tabel 4.26 Struktur Tabel Sub Category Field Type Size Null Key Id_SubCategory Varchar 50 No Primary Key Id_category Varchar 50 No Foreign Key Id_Admin Varchar 10 No Foreign Key Nama_SubCategory Varchar 100 No - Tabel 4.27 Struktur Tabel Employee Field Type Size Null Key Id_Employee Varchar 10 No Primary key Username_ Varchar 10 No - Employee Password_ Varchar 20 No - Employee Nama_employee Varchar 100 No - Jabatan_employee Varchar 100 No -
173 4.6 Navigation Diagram Gambar Navigation Diagram: Gambar 4.97 Navigation Diagram
174