1 / 59

Minggu 4,5,6,7

Materi Analisa Perancangan System. Minggu 4,5,6,7. Apa itu sistem ?. Sistem informasi ?. Sistem analis ?. Metodologi. Pendekatan ssadm. Ssadm stages. sdlc. Current system. Case study. steps. Gambarkan sistem secara umum (general)

shay
Télécharger la présentation

Minggu 4,5,6,7

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. MateriAnalisaPerancangan System Minggu 4,5,6,7

  2. Apaitusistem?

  3. Sisteminformasi?

  4. Sistemanalis?

  5. Metodologi

  6. Pendekatanssadm

  7. Ssadm stages

  8. sdlc

  9. Current system

  10. Case study

  11. steps • Gambarkansistemsecaraumum (general) Dalampenggambaransistemtersebut, sebutkansiapasaja user/actor/sistem lain yang berperandidalamnya. Simpulkanpermasalahanapasaja yang terjadidalamsistemtersebut. (see General Background.docx)

  12. 2. Investigasilingkungansistem

  13. Fact-finding techniques • Interview • clarification. • Forms and files • users’ agreement,

  14. Investigasiproses yang ada

  15. DFDs

  16. Elements of dfd

  17. Process & Data Flow

  18. External Entities & Data Stores

  19. Partial DFD example

  20. See – Materi APS – Pengenalan DFD.pptx DFD rules • Data flow diagram rules The analyst needs to be aware of some rules which apply to DFDs. These rules exist not to make life difficult, but to ensure consistency in diagramming. • Process rules Processes must have both inputs and outputs. If there is no input, but there is an output, then the output has been created from thin air. Sadly, this does not happen. If there is an input but no output, then the process is a waste of everyone’s time and should be scrapped. • Data flow rules Data flows must go through a process box. It is not allowed to have a data flow going directly from an external entity to a data store, for example. • External entity rules The label must be a noun, e.g. SUPPLIER. • Data store rules A data flow into a data store means update the data store. A data flow from a data store means retrieve data from the data store.

  21. Simple steps in data flow modelling • The main tasks to be completed, in order, are: 1 Draw a context diagram. 2 Draw a document flow diagram. 3 Draw a top-level data flow diagram. 4 Draw lower level data flow diagrams.

  22. Context Diagram & Document Flow Diagram

  23. Splitting the Steps – Study Case

  24. 2. Draw context diagram

  25. 3. Identify internal areas/departments

  26. 4. Draw Document Flow Diagram

  27. 5. Convert to top-level Data Flow Diagram

  28. Level 1 Current Physical DFD

  29. 6. Fungsional decomposition

  30. Cont…

  31. Limitation of DFD • Our current physical DFDs are now complete. They should give us a picture of what the Medical Centre currently does. They should be understandable and be useful as a communications tool with the user. However, there are limitations with DFDs. They don’t do everything (which is why we need other techniques). Here are a few limitations: • They don’t show us how the data is structured. • They don’t show the effect of time or sequence. • They may not help communicate with the user – they may be too complex. • They take a long time to draw and redraw. • They may never be complete While these limitations are real enough, the experienced analyst can use DFDs as a useful tool and not allow the limitations to become a problem.

  32. Tugas • Buat General Background darisistem yang andapilih. • Buat Problem/Requirements Catalouge • BuatDaftar External Entiti • Gambar Context Diagram • BuatDaftar Internal Entiti • GambarDokumen Flow Diagram • Gambar Top Level Data Flow Diagram • Gambar DFD Level 1 dan DFD level 2 masing – masingproses.

  33. Pemodelan Struktur Data

  34. Pemodelan Entitas/ Entity • Entitas • Things/ Sesuatu tempat informasi berada • People, customer, member, student • Object, product, recipes,

  35. Entity

  36. Atribut • Bits of Data yang menerangkan Entitas • Entitas MEMBER • Atribut

  37. Atribut

  38. Keys • Cara untuk mengidentifikasi sesuatu • Contoh orang, untuk mengidentifikasi digunakan NAMA • Primary Key, Key yang unik • MEMBER, MEMBERSHIP NUMBER • STUDENT, NRP • PATIENT, PATIENT NUMBER

  39. Relationship • Hubungan antar Entitas

  40. Relationship Type

  41. Datastore - Entity

  42. For Further study please read :System Analysis A Beginners Guide

  43. Analisa Data System Data entitas yang adapadasistem Masing-masingentitasdibuatkanatributnya dancontohisiannya 3. Memilih Key 4. MenentukanrelasidanTiperelasinya 5. Mencocokkandatastore DFD dengan diagram entitas 6. Membuat ERD.

  44. Logicalization • List Data Stores • Produce the logical data store/entity cross-reference • Remove time dependencies • Remove names and departments from the process boxes • Change processes so that they describe what is done to the data • Remove any physical references from the process box • Make sure that the data flows refer to logical items of data • Data flows between processes should be removed

  45. Business System Options • Identifikasialternative solusiuntukmenjawabhasilanalisis • Menentukan alternative solusi yang dipilih

More Related