Presentation is loading. Please wait.

Presentation is loading. Please wait.


Similar presentations

Presentation on theme: "ANALISIS dan PERANCANGAN SISTEM (INFORMASI)"— Presentation transcript:

Catur Iswahyudi, S.Kom, S.E Department of Informatics Engineering Institute 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 lunak Prasyarat : Sistem Informasi (TIFS 1407) Penunjang : Prakt. Analisis & Perancangan Sistem Tools : Easy CASE Microsoft Access Microsoft Visio Microsoft Project

3 MATERI Pendahuluan : Kontrak Pembelajaran, RPP Konsep Dasar Sistem
Analisis Sistem Siklus Hidup Sistem Perancangan Sistem Secara Umum Pendekatan Perancangan Terstruktur Pemodelan Sistem (DFD) Flowchart Perancangan Sistem Terinci (Output dan Input) Perancangan Sistem Terinci (Basisdata) Pengujian dan Jaminan Kualitas Sistem Manajemen pengembangan sistem Study 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 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 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 2008 NA = 0,5*Tugas+0,2*UTS+0,2*UAS+0,1*Hadir A  NA = 80 – 100 B  NA = 60 – 79 C  NA = 40 – 59 D  NA = 20 – 39 E  NA =

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


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

10 SDLC Phases Project Planning System Analysis
Put project in context Small part of a much larger system? New system or modify old? System Analysis Define user requirements Analyze tasks Develop specifications 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



14 Generic Life Cycle Models
Merge Sort 4/12/2017 7:44 PM Generic Life Cycle Models The Waterfall Model Prototyping Iterative and Incremental Development The Unified Process Life Cycle

15 Waterfall Life Cycle Requirements specification
Merge Sort 4/12/2017 7:44 PM Waterfall Life Cycle Requirements specification Functional specification Acceptance test specifications Unit test report Sub-system test report System test report Acceptance test report Completed system Software architecture specification System test specification Design specification Sub-system test specification Unit test specification Change requests Change request report

16 TLC (traditional life cycle) with Iteration
Merge Sort 4/12/2017 7:44 PM TLC (traditional life cycle) with Iteration The cost of this form of iteration increases as the project progresses making it impractical and not effective

17 Merge Sort 4/12/2017 7:44 PM 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

18 Strengths of TLC Provide a very structured way to system development
Merge Sort 4/12/2017 7:44 PM 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
Merge Sort 4/12/2017 7:44 PM 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 Perform an initial analysis. All software development activity utilizes valuable re­sources. 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 proto­typing exercise may involve many iterations, each iteration resulting in some improv­ement 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 proto­type 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 Sort 4/12/2017 7:44 PM 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, even though, by its very nature, the prototype is incomplete

21 Prototyping – Problems:
Merge Sort 4/12/2017 7:44 PM 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

22 Incremental Development
Merge Sort 4/12/2017 7:44 PM Incremental Development The Spiral Model (Boehm, 1988)

23 Incremental Development
Merge Sort 4/12/2017 7:44 PM 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

24 Unified Process Life Cycle
Merge Sort 4/12/2017 7:44 PM Unified Process Life Cycle The Unified Process System Development Life Cycle

25 Unified Process Life Cycle
Merge Sort 4/12/2017 7:44 PM Unified Process Life Cycle

26 Unified Process Life Cycle
Merge Sort 4/12/2017 7:44 PM 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
Merge Sort 4/12/2017 7:44 PM Choose Appropriate Life Cycle TCL is highly predictive Prototyping, Spiral and UP life cycle models are highly adaptive Predictive versus adaptive approaches to the SDLC

28 Problem Biaya (Kasus Gunung Es)

29 Distribusi Usaha Pengembangan Sistem

30 Problem Kesalahpahaman

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

33 Where Do Systems Analysts Work?

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

35 The Systems Analyst as a Facilitator

36 Ringkasan Metode Pengembangan Sistem Case tools

37 Metode Pengembangan Sistem

38 Structured Analysis

39 Object Oriented Analysis

40 Agile Methods agile=lincah, quick, easy

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)

42 Contoh Visible Analyst – Visible system
System Architect – Telelogic IBM company Rational Software - IBM


Similar presentations

Ads by Google