analisis perancangan sistem informasi

ANALISIS dan PERANCANGANSISTEM (INFORMASI) Catur Iswahyudi, S.Kom, S.E email:[email protected] Department of Informatics Engineering Institute of Science and Technology AKPRIND Yogyakarta Gambaran Umum  Tujuan :   Agar mahasiswa mengerti dan mampu menggunakan teknik-teknik serta perangkat untuk analisis, perancangan, dan pemodelan sistem. Kompetensi :  Mampu mengimplementasikan Analisis & Perancangan Sistem menggunakan alat bantu perangkat lunak  Prasyarat :  Sistem Informasi (TIFS 1407)  Penunjang :  Prakt. Analisis & Perancangan Sistem  Tools :     Easy CASE Microsoft Access Microsoft Visio Microsoft Project MATERI 1. Pendahuluan : Kontrak Pembelajaran, RPP 2. Konsep Dasar Sistem 3. Analisis Sistem 4. Siklus Hidup Sistem 5. Perancangan Sistem Secara Umum 6. Pendekatan Perancangan Terstruktur 7. Pemodelan Sistem (DFD) 8. Flowchart 9. Perancangan Sistem Terinci (Output dan Input) 10.Perancangan Sistem Terinci (Basisdata) 11.Pengujian dan Jaminan Kualitas Sistem 12.Manajemen pengembangan sistem 13.Study Kasus Kalau diringkas 1. Perencanaan sistem (System Planning) 2. Analisis Sistem (System Analysis) 3. Perancangan Sistem (System Design) 4. Implementasi Sistem (System Implementation) 5. Pendukung sistem dan Keamanan (System Support and Security) System Analysis and Design 8th Edition. Course Technology. McGraw-Hill Irwin. Whitten dan Lonnie D. Systems Analysis and Design Methods 7th Edition. Pearson Education Ltd. 2008 (ebook available)  Jeffrey L. Kendall. Bentley. Shelly dan Harry J. Analysis and Design of Information Systems 3rd Edition. Springer-Verlag London Limited. 2007 (ebook available) . Rosenblatt. 2011 (printed only)  Gary B. Kendall dan Julie E.PUSTAKA  Kenneth E. System Analysis and Design 8th Edition. 2010 (ebook available)  Arthur M. Langer. 19 .2*UTS+0.5*Tugas+0.Penilaian Acuan Patokan  Skor Nilai Akhir :  Dasar : SK No.1*Hadir  A  NA = 80 – 100     B  NA = 60 – 79 C  NA = 40 – 59 D  NA = 20 – 39 E  NA = 0 . tanggal 20 Peb 2008  NA = 0.2*UAS+0. 073/Skep/Rek/2008. process. data. and provide as output the information needed to support an organization. Information technology is a contemporary term that describes the combination of computer technology (hardware and software) with telecommunications technology (data. store. image. processes. and voice networks). and information technology that interact to collect.IS and IT An information system (IS) is an arrangement of people. 1-7 . 1-8 . Systems Development Life Cycle (SDLC) Project Planning System Analysis System Design Construction/Implementation Integration and Testing Installation Operation & Maintenance st i Te ng        9 . SDLC Phases  Project Planning     System Analysis     Put project in context Small part of a much larger system? New system or modify old? Define user requirements Analyze tasks Develop specifications System Design .Define the system to be built   Logical design Physical design 10 . system testing. add facilities 11 . acceptance testing Installation   Write (or buy) the code Testing.SDLC Phases (continued)  Construction   Integration and Testing   Unit testing. conversion Operations & Maintenance  Put into production  Fix bugs. training. 12 . Analisis Sistem Desain Sistem Perancangan Konseptual Penyiapan Spesifikasi Rancangan Evaluasi Alternatif Rancangan Penyiapan Laporan Rancangan Sistem Konseptual Perancangan Fisik Rancangan Keluaran dan Masukan Rancangan Platform Dokumentasi Rancangan Antarmuka Pemakai & Sistem Rancangan Basis data Rencana Pengujian Implementasi Sistem Operasi dan Pemeliharaan 13 Rancangan Modul Rancangan Kontrol Rencana Konversi . Generic Life Cycle Models  The Waterfall Model  Prototyping  Iterative and Incremental Development  The Unified Process Life Cycle . Waterfall Life Cycle Requirements specification Functional specification Acceptance test specifications System System Engineering Engineering Requirements A nalysis Analy sis Unit test report Sub-system test report System test report Acceptance test report Completed system Design Design Construction Software architecture specification System test specification Design specification Sub-system test specification Unit test specification Change requests Change request report Testing Code Installation Code M aintenance Maintenance . TLC (traditional life cycle) with Iteration The cost of this form of iteration increases as the project progresses making it impractical and not effective . Problems with TLC  Real projects rarely follow such a simple sequential life cycle  Lapsed time between systems engineering and the final installation is long  Iterations are almost inevitable in real projects but are expensive & problematic with the TLC  Unresponsive to changes during project as iteration is difficult  Therefore. this model is only appropriate when the requirements are well-understood .  Project progress evaluated at the end of each phase. and assessment made as to whether the project should proceed .Strengths of TLC  Provide a very structured way to system development  Tasks in phases may be assigned to specialized teams. Prototyping Life Cycle • Not intended to deliver the final working system • Quickly built up to explore some aspects of the system • May be used as part of other iterative life cycle Initial analys is Define objectives Specify Prototyping com pleted Evaluate Cons truct . by its very nature. even though.Prototyping – Advantages  Early demonstrations of system functionality help identify any misunderstandings between developer and client  Client requirements that have been missed are identified  Difficulties in the interface can be identified  The feasibility and usefulness of the system can be tested. the prototype is incomplete . Prototyping – Problems:  The client may perceive the prototype as part of the final system  The prototype may divert attention from functional to solely interface issues  Prototyping requires significant user involvement  Managing the prototyping life cycle requires careful decision making . 1988) . no-go decision Risk assessment Progress towards final system User evaluation Software development Develop first increment Develop next increment The Spiral Model (Boehm.Incremental Development Initial requirements gathering and project planning Planning Risk analysis Risk analysis based on user reaction to plan Further planning based on user comments User evaluation of increments Risk analysis based on initial requirements Go. Incremental Development  Iterative problem solving: repeats activities. each can be viewed as a mini-project  Incremental delivery. either external or internal release  New release = new functionality + (improved) previous release  Several approaches to structuring iterations  Define and implement the key system functions  Focus on one subsystem at a time  Define by complexity or risk of certain components . Unified Process Life Cycle The Unified Process System Development Life Cycle . Unified Process Life Cycle . Unified Process Life Cycle  Captures many elements of best practice  The phases are:  Inception is concerned with determining the scope and purpose of the project.  Construction's main aim is to build the software system. .  Elaboration focuses requirements capture and determining the structure of the system.  Transition deals with product installation and rollout. Spiral and UP life cycle models are highly adaptive Predictive versus adaptive approaches to the SDLC .Choose Appropriate Life Cycle • TCL is highly predictive • Prototyping. Problem Biaya (Kasus Gunung Es) 28 . Distribusi Usaha Pengembangan Sistem 29 . Problem Kesalahpahaman 30 . networks.System Designers and System Builders System designer – a technical specialist who translates system users’ business requirements and constraints into technical solution. System builders – a technical specialist who constructs information systems and components based on the design specifications generated by the system designers. outputs. and software that will meet the system users’ requirements. inputs. 1-31 . She or he designs the computer databases. screens. processes.Systems Analysts Systems analyst – a specialist who studies the problems and needs of an organization to determine how people. • A business analyst focuses on only the non-technical aspects of systems analysis and design. • A programmer/analyst includes the responsibilities of both the computer programmer and the systems analyst. data. and information technology can best accomplish improvements for the business. 1-32 . Where Do Systems Analysts Work? 1-33 . Skills Needed by the Systems Analyst  Working knowledge of information technology  Computer programming experience and expertise  General business knowledge  General problem-solving skills  Good interpersonal communication skills  Good interpersonal relations skills  Flexibility and adaptability  Character and ethics 1-34 . The Systems Analyst as a Facilitator 1-35 . Ringkasan  Metode Pengembangan Sistem  Case tools . Metode Pengemban gan Sistem . Structured Analysis . Object Oriented Analysis . Agile Methods agile=lincah. quick. easy . screen gen.CASE tools     UML-Unified Modelling Language IBMS-Information Base Modelling System IDE-Integrated Development Tools Individual tools     Modelling tools Documentation tools Engineering tools Construction tols (apps gen. report gen) . Contoh  Visible Analyst – Visible system  System Architect – Telelogic IBM company  Rational Software .IBM .