Kuliah Sistem Pakar
Pertemuan X
Tahap III, IV
Prototyping dan
Pengembangan Sistem
Phase III
Rapid Prototyping and Demonstration
Prototype

Prototyping, suatu proses untuk menghasilkan
suatu prototipe

Prototype, ide bagi pembuat maupun pengguna
(potensial) tentang cara suatu sistem akan
berfungsi dalam bentuk lengkap dan bagaimana
sistem nantinya akan dikembangkan maupun
diperbaiki
Rapid Prototyping
and a Demonstration Prototype

Build a small prototype

Test, improve, expand

Demonstrate and analyze feasibility

Complete design
Rapid Prototyping
Crucial to ES development
 Small-scale system
 Includes knowledge
representation
 Small number of rules
 For proof of concept

Rapid Prototyping Process
Start
Rancangan
Prototype
Refinement dari
Pengembangan
Sistem
Ya
Perlu
Perbaikan ?
Analisis
Hasil
Tidak
Akhir
Prototyping
Evaluasi, Pakar,
Sumbang Saran
Pengguna
Akuisisi
Pengetahuan dan
Representasi
Testing,
Studi Kasus
Prototyping:
ES Development Life Cycle (PADI)
Planning
Analysis
Design
Implementation
Prototype
Keuntungan dan Daya Tarik
Prototipe

Keuntungan
 Memperoleh gambaran Sistem




Memperoleh gambaran Perbaikan/Perawatan
Memperoleh gambaran ide, Hardware, Software
serta Network (optional)
Memperkenalkan dan menjual Sistem pada calon
“user” yang skeptis.
Mendemonstrasikan Sistem (sederhana)
Keuntungan dan Daya Tarik (lanjutan)





Daya Tarik
Terjadi komunikasi yang baik antara
sistem
“perancang” dengan user
Perancang dapat bekerja lebih baik dalam
menentukan kebutuhan user
User berperan lebih aktif dalam
pengembangan
sistem
Aplikasi sistem lebih mudah karena
keterlibatan user secara aktif, sehingga
user mengetahui apa yang diharapkan.
Phase IV
Pengembangan Sistem









Develop the knowledge base
Define the potential solutions
Define the input facts
Develop an outline
Draw a decision tree
Create a knowledge map
Create the knowledge base
Test, evaluate, and improve (knowledge base)
Plan for integration
Development and Maintenance of Expert Systems
Problem Identification and Feasibility Analysis
1.
–
–
–
The problem must be suitable for an expert to solve it.
Find an expert for the project
Cost effectiveness must be established
2. System Design and Expert System Technology
Identification
–
–
–
The system is designed with integration other subsytems
and databases
Domain knowledge
Knowledge and inferencing is established with simple cases
3. Development of Prototype
–
–
Knowledge Engineer works with the expert
Specific Tool is chosen for the project
Development and Maintenance of Expert Systems
(Continued)
4. Testing and Refinement of Prototype
– Test with simple cases
– Deficiencies in performance are noted.
– End users test the prototypes.
5. Complete and Field the Expert System
– The interaction with the environment,, users, and other
information systems is tested
– Documented
– User training
6. Maintain the System
– The system is kept current by updating the knowledge base
– Interfaces with other information systems are maintained
Development and Maintenance of Expert Systems
(Continued)
4. Testing and Refinement of Prototype
– Test with simple cases
– Deficiencies in performance are noted.
– End users test the prototypes.
5. Complete and Field the Expert System
– The interaction with the environment, users, and
other information systems is tested
– Documented
– User training
6. Maintain the System
– The system is kept current by updating the KB
– Interfaces with other information systems are
maintained
Development & Maintenance of ESs
Problem Identification and
Feasibility Analysis
System Design and ES
Technology Identification
Development of
Prototype
Testing and Refinement
of Prototype
Is the Performance
Satisfactory?
No
Yes
Complete and
Field the ES
ES Ready for Use
Maintain ES
Pengembangan Sistem Pakar
Team
Problem
Development Team
Expert
Knowledge
Engineer
Akuisisi
Programmer
ES
Software
Format
Representasi
Pengetahuan
Computer
Simulated
Expert
Answer
Conclusion
Solution
Decission
Recomendation
User
Problems to
Solve
Roles in Expert System
Development
Expert
– Knowledge
 Knowledge Engineer
– Knowledge acquisition tactics include
interviews, protocol analysis, observation, and
analysis of cases
– Must select a tool with the application of the
knowledge acquisition facility
 User
– End user with a simple shell
– Prototypes are used

Persyaratan Sistem Pakar yang Baik
(Pertemuan 10/06 -)










Dikembangkan untuk menjawab kebutuhan
Kecepatan pemrosesan tinggi
Menambah kepakaran “user”
Mudah diperbaiki
Dapat menjawab pertanyaan sederhana
Dapat bertanya untuk mendapat info tambahan
Mudah diubah
Pengguna harus merasa menguasai SP
Tidak sulit bagi pengguna pemula
Kebutuhan input harus jelas dan sederhana
Sampai Jumpa
di
Pertemuan XI
Selamat Belajar, Semoga
Sukses