Sekolah Tinggi Teknologi Adisutjipto Yogyakarta Materi Kuliah Analisa dan Perancangan Sistem Semester Ganjil 2014 / 2015 E.N. Tamatjita e-mail : tamatjita@gmail.com Wednesday, October 1, 2014 - Ansis STTA tamatjita Gasal 2014/2015-1
Pendahuluan INTI : Mahasiswa memahami konsep analisa dan perancangan sistem yang baik dan tepat yang digunakan dalam dunia bisnis. Bagaimana membuat analisan dan percangan menggunakan model struktural dan model berorientasi obyek. Mahasiswa mempelajari berbagai diagram yang digunakan dalam tahapan SDLC (System Development Life Cycle). SASARAN : Mampu memahami konsep dari SDLC (System Development Life Cycle). Mampu menganalisa sistem berjalan yang dijadikan studi kasus. Mampu membuat sistem usulan dan merancang sistem serta memperbarui sistem lama dengan sistem baru. Mampu mengembangkan dan menerapkan penggunaan beberapa diagram dalam tahapan analisa dan perancangan. Mampu bekerja dalam tim untuk pengembangan Sistem Informasi baru. Mampu membuat analisa dan perancangan sistem secara utuh baik menggunakan model struktural maupul model berorientasi obyek. DAFTAR PUSTAKA : Dennis, Alan et all, 2005, Systems Analysis and Design with UML Version 2.0 An Object-Oriented Approach, Second Edition, John Wiley & Sons, Inc., Virginia, New Jersey Sarno, Riyanarto, 2012, Analisis dan Desain Berorientasi Servis untuk Aplikasi Manajemen Proyek, Edisi Pertama, Penerbit Andi, Yogyakarta Valacich, Joseph S. et all, 2004, Essentials of Systems Analysis and Design, Second Edition, Pearson Education International, Prentice Hall, Upper Saddle River, New Jersey Wednesday, October 1, 2014 - ANSIS STTA tamatjita Gasal 2014/2015 2
Pertemuan Ke-2 Lanjutan Peraturan Perkuliahan Yang Harus Di Taati : Hadir tidak boleh terlambat dari 20 menit Syarat mengikuti UAS, kehadiran >= 60% Disiplin : Pakaian sbb : Kerapian dan kesopanan berpakaian Baju berkrah dan bersepatu Tidak menggunakan asesoris yang tidak semestinya Bobot Komponen Penilaian : Nilai / Angka Huruf Bobot Predikat 80 100 A 4 Sangat Baik 65 79,99 B 3 Baik 55 64,99 C 2 Cukup 40 54,99 D 1 Kurang 0 39,99 E 0 Sangat Kurang Wednesday, October 1, 2014 - ANSIS STTA tamatjita Gasal 2014/2015-3
Komponen Nilai Penilaian individu, meliputi : Ujian Tengah Semester 20 % Ujian Akhir Semester 30 % Kehadiran 20 % Penilaian Tugas Mandiri dan Tugas Kelompok : Tugas Mandiri 10 % Tugas Kelompok Paper+Presentasi 20 % Wednesday, October 1, 2014 - ANSIS STTA tamatjita Gasal 2014/2015-4
Tahapan-tahapan dalam SDLC 1. Perencanaan, Lanjutan Wednesday, October 1, 2014 - ANSIS STTA tamatjita Gasal 2014/2015 5 -
Dalam SDLC tahapan Perencanaan digambarkan dalam : Di kutip dalam buku Hoffer, Chapter 1, hal 11, Modern Systems Analysis and Design Wednesday, October 1, 2014 - ANSIS STTA tamatjita Gasal 2014/2015 6 -
Problems with Waterfall Approach System requirements locked in after being determined (can't change) Limited user involvement (only in requirements phase) Too much focus on milestone deadlines of SDLC phases to the detriment of sound development practices
Alternatives to Traditional Waterfall SDLC Prototyping CASE tools Joint Application Design (JAD) Rapid Application Development (RAD) Agile Methodologies extreme Programming
Prototyping Iterative development process: Requirements quickly converted to a working system System is continually revised Close collaboration between users and analysts
CASE Tools Computer-Aided Software Engineering Software tools providing automated support for systems development Project dictionary/workbook: system description and specifications Diagramming tools Example products: Oracle Designer, Rational Rose
Joint Application Design (JAD) Structured process involving users, analysts, and managers Several-day intensive workgroup sessions Purpose: to specify or review system requirements
Rapid Application Development (RAD) Methodology to decrease design and implementation time Involves: prototyping, JAD, CASE tools, and code generators
Agile Methodologies Motivated by recognition of software development as fluid, unpredictable, and dynamic Three key principles Adaptive rather than predictive Emphasize people rather than roles Self-adaptive processes
extreme Programming Short, incremental development cycles Automated tests Two-person programming teams Coding and testing operate together Advantages: Communication between developers High level of productivity High-quality code