3653223-analisis-dan-perancangan-sistem-informasi.pdf.pptx

digital

1. ANALISIS dan PERANCANGAN SISTEM (INFORMASI) Amril Samosir , S.Kom , M.T.I [email protected] Khasanah Software IT-Solution

2. 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 Eunak ❑ Prasyarat : ■ Sistem Informasi (TIFS 1437) ❑ Penunjang : ■ Prakt. AnaNsis & Perancangan Sistem ❑ Tools : ■ Easy CASE ■ Ivlicrosoft Access ■ Microsoft Visio ■ IA icrosoft Project

3. MATERI 1. Pendahuluan : Kontrak Pembelajaranf RPP 2. Konsep Dasar Sistem 3. Analisis Sistem 4. Siklus Hidup Sistem 5. Perancangan Sistem Secara Igor 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.1\lanajemen pengembangan sister 13.Study Kaus

4. 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)

5. PUSTAKA ❑ Kenneth E. Kendall dan Julie E. Kendall, System Analysis and Design 8th Edition, Pearson Education Ltd,2011(printed only) ❑ Gary B. Shelly dan Harry]. Rosenblatt, System Analysis and Design 8th Edition, Course Technology, 2010 (ebook available) ❑ Arthur M. Langer, Analysis and Design of Information Systems 3rd Edition, Springer-Verlag London Limited, 2008(ebook available) ❑ Jeffrey L. Whitten dan Lonnie D. Bentley, Systems Analysis and Design Methods 7th Edition, McGraw- Hill Irwin, 2007 (ebook available)

6. Penilaian Acuan Patokan

7. IS and IT An information system IS is an arrangement of people, data, processes, and information technology that interact to collect, process, store, 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, image, and voice networks).

8. Tve VLATEIG- `PROQUCT 41. 4h1 4 V INFORMATION SYSTEMS C PA 4 4 1-8 Transaction Processing Systems Management information Systems Decision Support Systems Executive Information Systems Expert Systems Communications & Collaboration Systems Office Automation Systems 11&

9. Systems Development Life Cycle (SDLC) ❑ Project Planning ❑ System Analysis ❑ System Design ❑ Construction/Implementation ❑ Integration and Testing ❑ Installation ❑ Operation & Maintenance

10. SDLC Phases D Project Planning ■ Put project in context ■ Small part of a much larger system? ■ New system or modify old? D System Analysis ■ Define user requirements ■ Analyze tasks • Develop specifications El System Design - Define the system to be built • Logical design • Physical design

11. SDLC Phases (continued) ❑ Construction ■ Write or buy) the code ❑ Integration and Testing ■ Unit testing, system testing, acceptance testing ❑ Installation ■ Testing, training, conversion ❑ Operations & Maintenance ■ Put into production ■ Fix bugs, add facilities 11

12. Anolisis istern Studi Kdayakan Anali si s Kebutuhan Perubahan lingkup I Kebutulian Si stein besoin Sistem I es x 111 Si stem kebutuhan Kesal alma a tau ma salali yan2 tak memund-inkan ement sl dilaksanakan Perancangan konseptua1 Peranca112a11 fisik Implementasi Sistem Peinroaainan Pengujiall Si stem Siap B erop er a si landiri d ImplementaA kulailLf. lenztap acb Operosi don perminta all balu Petnelihoro,on 12

13. An ali si s Si stem Des in istem P ET an c an gan Konseptmal Ev aluasi P enyi ap an Spe si fikasi Penyi apan Lap oran Alt ematif Rancangan Rancangan Si stem Rancangan Kons eptual Per<nicangan Fi sik Rancangan Rancangan Rancangan Rancangan Rancangari Rancangan Keluaran Platform Ant armulca Basis data Modul Kontrol dan - Pemakai & - - Masukan Si st em Dokum ent asi R_ enc an a Penguji an Ren c aria Kony ersi Impl ement asi Si stem Op er asi dan Pemeliharaan 13

14. Generic Life Cycle Models ❑ The Waterfall Model ❑ Prototyping ❑ Iterative and Incremental Development ❑ The Unified Process Life Cycle

15. Waterfall Life Cycle System [ Engineering V [ Requirements Analy sis T ID es ign V F Requirements specification Functional specification Acceptance test specifications J Unit test report Sub-system test report System test report Acceptance test report F C onstruction F Software architecture specification System test specification Design specification Sub-system test specification Unit test specification Change requests Change request report V Testing Completed system ...- 1..## V Installation Maintenance

16. TLC (traditional ife cycle) with Iteration System Engineering A The cost of this form of iteration increases as the project progresses making it impractical and not effective R equirem eats hip. Analysis A D as ign A C onstruction Testing I Installation Maintenance 41

17. 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 I=1 Therefore, this model is only appropriate when the requirements are well-understood

18. Strengths of TLC ❑ Provide a very structured way to system development ❑ Tasks in phases may be assigned to specialized teams. ❑ Project progress evaluated at the end of each phase, and assessment made as to whether the project should proceed

19. 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 Define analysis ■ o bje ctive s V Sp e cify Eva lu ate C o nstru ct

20. 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 1:1 The feasibility and usefulness of the system can be tested, even though, by its very nature, the prototype is incomplete

21. Prototyping — Problems: ❑ The client may perceive the prototype as part of the final system ❑ The prototype may divert attention from functional to solely interlace issues ❑ Prototyping requires significant user involvement ❑ Managing the prototyping life cycle requires careful decision making

22. Incremental Development t al peg' we] h gathering ,( Al 44' vjer f pis lurii r.," Further *mink based on user - ur con NI lents Planning •-• User evaluation The Spiral Model Risk analysis F FF F ••• '4 -•% Software development (Boeh m. 1988) R/ th 11S ‘ Med 0/ n ?JO al re(' 'filo) lel Its sk s based f.:F7 reOdiOlt I-0 )/ Go, no-go decision Risk assessment Progress tovvaids final system hTrrelop tevt unt

23. Incremental Development era we pro• em so \nig: repeats activities, each can be viewed as a mini-project ❑ Incremental delivery, either external or internal release 1:1 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

24. Unified Process Life Cycle SYSTEM DEVELOPMENT LIFE CYCLE ITERATION INCEPTION ELABORATION 1 1r PHASE CONSTRUCTION 1 r TRANSITION PHASES ARE NOT ANALYSIS, DESIGN, AND IMPLEMENT; INSTEAD, EACH ITERATION INVOLVES A COMPLETE CYCLE OF REQUIREMENTS, DESIGN, IMPLEMENTATION, AND TEST DISCIPLINES The Unified Process System Development Life Cycle

25. Unified Process Life Cycle Project Phases IricLptJtor! Elaboration Construct( 41 Transition 3 A Requirements Analysis Design Implementation Test I Y ❑ o ❑ a o 0 a a Illr ❑ 0 0 --. o ❑ 1 AE a ❑ IL E 0 o U Workflows Sipe of square relative to the spent on workflows

26. 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; ■ Elaboration focuses requirements capture and determining the structure of the system; ■ Construction's main aim is to build the software system; ■ Transition deals with product installation and rollout.

27. Choose Appropriate Life Cycle • • Prototyping, Spiral and UP life cycle models are highly adaptive THE APPROPRIATE SDLC VARIES DEPENDING ON THE PROJECT PREDICTIVE ADAPTIVE SRC SDLC REQUIREMENTS WELL REQUIREMENTS AND NEEDS UNDERSTOOD AND WELL DEFINED, UNCERTAIN, LOW TECHNICAL RISK, HIGH TECHNICAL RISK. Predictive versus adaptive approaches to the SDLC

28. Problem Biaya (Kasus Gunung Es) Allah sis„ D esain„ Intl ent a si, Konversi Peiil d ih ar a an 28

29. Distribusi Usaha Pengembangan Sistem Analisis Sistem 20% Pengujian 45% Derain i ste m 15% Peng kodean 20%

30. (a) ) Kebutuhan p emakai Kebutuhan pemakai yang menurat analis si stem cukup direalisasikan scat wawancara menurut anali s si stem (c) (d) P emro gram me la kukan Si stem yang seb enamya p enyederhanaan htinginkan ol eh p emakai 30

31. System Designers and System Builders System designer - a technical specialist who translates system users' business requirements and constraints into technical solution. She or he designs the computer databases, inputs, outputs, screens, networks, and software that will meet the system users' requirements. System builders - a technical specialist who constructs information systems and components based on the design specifications generated by the system designers.

32. Systems Analysts Systems analyst - a specialist who studies the problems and needs of an organization to determine how people, data, processes, and information technology can best accomplish improvements for the business. • A prograrnmerianalyst includes the responsibilities of both the computer programmer and the systems analyst. • A business analyst focuses on only the non-technical aspects of systems analysis and design. 1-32

33. Where Do Systems Analysts Work? Financial Management Budget Finance Accounting Human Resources Emplvernent Se! 4 ices 1389rJorory Compliruv4: Lrrployt-e 13c-refts Executive Mena gerneni Operations Ccniror Sales and Deiribution Research & Development Market Research Prodwl rriginooring —F Industrial Engireering I nforrnation Services Ti Systems De veto-mem Data 14 1 Management Mehra* Services ftJOTE; Thir igwr demorelralea hero we wlll [roars retierferfie nOte4 in the riot 10 144 Ilgure. The numbered bullets rider to In- tend references that explain the bullet Financial SYsledrei loam Systems Analysts; Hannan Reseorte System* Team Systems Analysts Purchasing Dorm r Computing *sterns Ana lysis r l..oartrnemaj Customer Computing Semi:* 0 g ()o pal Imri ntal Cetrup SyslalreY H Anarysts o Systems Analysts Ar Systems Operations Analysts Research & plt.sriatontei Tectiricat Drruciopment Computing Suppor I SyS60.1115 Syx1r2rest learn Ananests Systems Unassigned Analysis DeveloiderS 4rAl Systems AnatesN 1-33 Figure 1-2 Systems Analysts in a Typical Organization

34. 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 -1 4

35. The Systems Analyst as a Facilitator Irrarion,q 4:Unmakes Information l:Iper technology vendors aiE Systems analyst • • User N Network administrator System owner Datii bage Considunit Interface 1-35 :1(11 Eli rimiritir3 r design ex iwrt

36. Ringkasan ❑ Metode Pengembangan Sistem ❑ Case tools

37. STRUCTURED ANALYSIS Description Represents the system in terms of data and the promises that act upon that data System development is organized into phases. wkh deliverables, and milestones to measure- progress The SIX( waterfall model typically consists of five phases. Iterauon is possible among the phases,as shown in figure I Modeling Data ilcpw diavrarns (OF Ds) and tools process descripuons.which are described in Chapter 5. Pro Traditional method. which has been Ary popular o'er time. Relies heavily on written cbcumentation. Frequent phase iteration can provide flexibility compardble with other methods.Well-suited to prowl( management tools and techniques Cons Changes can be costly, especially In later phases. Requirements are defined eau-ly,and can change durrng dedelopment. Users might not be able to dimcrrbe theft Peeds with they can see examples of features and functions. OBJECT-ORIENTED AG ILEiADWFTIVE ANALYSIS HETHCOS Views the system in terms of St rises intense objects that combine data and team-based effort. as pro cesses. The obiects shown in Figures f-28 and represent actual people, I -29. Brealo (development transacuons.and events, as process down into cycles. shown in Figure I-26. or iterations that add Compared to structured functionality Each analysis. 0.0 phases tend to Iteration is designed, be more in fel-act ire_ Can use built. and tested In an the waterfall model or the ongoing process. model that stresses v-eater Atternpts to reduce iteration, as shown in major risks by incremental Rpre l steps In short time Inter4S.Typically uses a spiral mcdel. as shown In FLEure11-30_ Various obiect.oriented &warns Uses tools that facilmate depict system actors, methods, team ownniunicat ion, such and messages, which are as collaborative software, described in Chapter 6. In tE.r ac rive pre ten at ions, tr additional whitebcords and face-to-face cocoa. nItegrates easily whh Very flexible and efficient obleot-oriented programming in dealing with change . Languages-Code Is modular and Stresses team interaction reusable. which can reduce cost and re4I4xts 4 set of and development drne- Easy to commuraty-based v-ailuet mainta.in and expand as new Frequent tielwer-eibleE objects lari be cloned usrng eontaintie validate the Inherited properti es _ project and reduce risk. Somewhat noreer method might Team members need a be less familiar to deielopment high level of technical and team mernbers. Interaction of communications skills. (bigots and classes can be Lack of structure and complex in larger systems, documeritadon can Introduce risk factors. Overall project might be suhlect to scope change as user requirements change.

38. Peeee f'foirrinvp IftieS011.01. Flu"we •Pas• PAW. MsOW - ihmiihre 4_ • U P1444 •• • DOW 1 Noir Iviaa•el•A Pliro4 Sioftrai 41.i IN MI • 1.01+ft•stral.- I C", Apia r owl seoi ergros muee 1&"l en* wpr►l FIGURE 1.15 The phasti and delnerables el the SOLC are shown in the waterFall model. laosnesinel

39. Object Oriented Analysis Planning AnalySis Testin Prototypes F IGURE 1.27 In this model. p6nning, anslysis. and design ta3lcs interact conunuously. Interactive models often Are used vodi 0-0 development rned-p)ds.

40. Agile Methods agile lincah, ouick. easy C1)7141■ ri Maim C re, Offitailvot Choi/ore* biormi it milky mks Vk► hot 4iffierdiAi. Direrwuki larmior. Proveivie Mulcts* OF emitraIrmlf igrektygia 161111/M ION1.01 J1114.40Craer g. MOCIPOPOI• 01. norl 30,411•11 C pplu• 'weir ewe opi ptelxi FIGURE 1 - 30 Able methods typically use a spiral model...Asa represents 3 semi of iterwacess.or versoons.based an user feedback

41. 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, screen gen, report gen)