Presentation on theme: "ANALISIS dan PERANCANGAN SISTEM (INFORMASI)"— Presentation transcript:
1 ANALISIS dan PERANCANGAN SISTEM (INFORMASI) Catur Iswahyudi, S.Kom, S.EDepartment of Informatics EngineeringInstitute of Science and Technology AKPRIND Yogyakarta
2 Gambaran Umum Prasyarat : Penunjang : Tools : Tujuan : Kompetensi : 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 lunakPrasyarat :Sistem Informasi (TIFS 1407)Penunjang :Prakt. Analisis & Perancangan SistemTools :Easy CASEMicrosoft AccessMicrosoft VisioMicrosoft Project
3 MATERI Pendahuluan : Kontrak Pembelajaran, RPP Konsep Dasar Sistem Analisis SistemSiklus Hidup SistemPerancangan Sistem Secara UmumPendekatan Perancangan TerstrukturPemodelan Sistem (DFD)FlowchartPerancangan Sistem Terinci (Output dan Input)Perancangan Sistem Terinci (Basisdata)Pengujian dan Jaminan Kualitas SistemManajemen pengembangan sistemStudy Kasus
4 Kalau diringkas Perencanaan sistem (System Planning) Analisis Sistem (System Analysis)Perancangan Sistem (System Design)Implementasi Sistem (System Implementation)Pendukung sistem dan Keamanan (System Support and Security)
5 PUSTAKAKenneth E. Kendall dan Julie E. Kendall, System Analysis and Design 8th Edition, Pearson Education Ltd, 2011 (printed only)Gary B. Shelly dan Harry J. 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 Skor Nilai Akhir :Dasar :SK No. 073/Skep/Rek/2008, tanggal 20 Peb 2008NA = 0,5*Tugas+0,2*UTS+0,2*UAS+0,1*HadirA NA = 80 – 100B NA = 60 – 79C NA = 40 – 59D NA = 20 – 39E NA =
7 IS and ITAn 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).
9 Systems Development Life Cycle (SDLC) Project PlanningSystem AnalysisSystem DesignConstruction/ImplementationIntegration and TestingInstallationOperation & MaintenanceTesting
10 SDLC Phases Project Planning System Analysis Put project in contextSmall part of a much larger system?New system or modify old?System AnalysisDefine user requirementsAnalyze tasksDevelop specificationsSystem Design - Define the system to be builtLogical designPhysical design
11 SDLC Phases (continued) ConstructionWrite (or buy) the codeIntegration and TestingUnit testing, system testing, acceptance testingInstallationTesting, training, conversionOperations & MaintenancePut into productionFix bugs, add facilities
14 Generic Life Cycle Models Merge Sort4/12/2017 7:44 PMGeneric Life Cycle ModelsThe Waterfall ModelPrototypingIterative and Incremental DevelopmentThe Unified Process Life Cycle
15 Waterfall Life Cycle Requirements specification Merge Sort4/12/2017 7:44 PMWaterfall Life CycleRequirements specificationFunctional specificationAcceptance test specificationsUnit test reportSub-system test reportSystem test reportAcceptance test reportCompleted systemSoftware architecture specificationSystem test specificationDesign specificationSub-system test specificationUnit test specificationChange requestsChange request report
16 TLC (traditional life cycle) with Iteration Merge Sort4/12/2017 7:44 PMTLC (traditional life cycle) with IterationThe cost of this form of iteration increases as the project progresses making it impractical and not effective
17 Merge Sort4/12/2017 7:44 PMProblems with TLCReal projects rarely follow such a simple sequential life cycleLapsed time between systems engineering and the final installation is longIterations are almost inevitable in real projects but are expensive & problematic with the TLCUnresponsive to changes during project as iteration is difficultTherefore, this model is only appropriate when the requirements are well-understood
18 Strengths of TLC Provide a very structured way to system development Merge Sort4/12/2017 7:44 PMStrengths of TLCProvide a very structured way to system developmentTasks 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 Merge Sort4/12/2017 7:44 PMPrototyping Life CycleNot intended to deliver the final working systemQuickly built up to explore some aspects of the systemMay be used as part of other iterative life cyclePerform an initial analysis. All software development activity utilizes valuable resources. Embarking upon a prototyping exercise without some initial analysis is likely to result in an ill-focused and unstructured activity producing poorly designed software.Define prototype objectives. Prototyping should have clearly stated objectives. A prototyping exercise may involve many iterations, each iteration resulting in some improvement to the prototype. This may make it difficult for the participants in a prototyping exercise to determine if there is sufficient value to continue the prototyping. However, with clearly defined objectives it should be possible to decide if they have been achieved.Specify prototype. Although the prototype is not intended for extended operation it is important that it embodies the requisite behaviour. It is almost certainly the case that the prototype will be subject to modification and this will be easier if the software is built according to sound design principles.Construct prototype. Since it is important that prototype development is rapid, the use of a rapid development environment is appropriate. For example, if an interactive system is being prototyped, environments such as DelphiTM or Visual Basic® can be most effective.Evaluate prototype and recommend changes. The purpose of the prototype is to test or explore some aspect of the proposed system. The prototype should be evaluated with respect to the objectives identified at the beginning of the exercise. If the objectives have not been met then the evaluation should specify modifications to the prototype so that it may achieve its objectives. The last three stages are repeated until the objectives of the prototyping exercise are achieved.
20 Prototyping – Advantages Merge Sort4/12/2017 7:44 PMPrototyping – AdvantagesEarly demonstrations of system functionality help identify any misunderstandings between developer and clientClient requirements that have been missed are identifiedDifficulties in the interface can be identifiedThe feasibility and usefulness of the system can be tested, even though, by its very nature, the prototype is incomplete
21 Prototyping – Problems: Merge Sort4/12/2017 7:44 PMPrototyping – Problems:The client may perceive the prototype as part of the final systemThe prototype may divert attention from functional to solely interface issuesPrototyping requires significant user involvementManaging the prototyping life cycle requires careful decision making
22 Incremental Development Merge Sort4/12/2017 7:44 PMIncremental DevelopmentThe Spiral Model (Boehm, 1988)
23 Incremental Development Merge Sort4/12/2017 7:44 PMIncremental DevelopmentIterative problem solving: repeats activities, each can be viewed as a mini-projectIncremental delivery, either external or internal releaseNew release = new functionality + (improved) previous releaseSeveral approaches to structuring iterationsDefine and implement the key system functionsFocus on one subsystem at a timeDefine by complexity or risk of certain components
24 Unified Process Life Cycle Merge Sort4/12/2017 7:44 PMUnified Process Life CycleThe Unified Process System Development Life Cycle
25 Unified Process Life Cycle Merge Sort4/12/2017 7:44 PMUnified Process Life Cycle
26 Unified Process Life Cycle Merge Sort4/12/2017 7:44 PMUnified Process Life CycleCaptures many elements of best practiceThe 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 Merge Sort4/12/2017 7:44 PMChoose Appropriate Life CycleTCL is highly predictivePrototyping, Spiral and UP life cycle models are highly adaptivePredictive versus adaptive approaches to the SDLC
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 AnalystsSystems 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 programmer/analyst 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.
34 Skills Needed by the Systems Analyst Working knowledge of information technologyComputer programming experience and expertiseGeneral business knowledgeGeneral problem-solving skillsGood interpersonal communication skillsGood interpersonal relations skillsFlexibility and adaptabilityCharacter and ethics