Praktikum Analisis dan Perancangan system informasi.pptx

pengantara untuk memulai praktikum

1. Praktikum Analisis dan Perancangan sistem informasi Masrul Indrayana

2. The System Development Process

3. The Process

4. General Principles ISD Methodology Get the system users involved Use a problem-solving approach Establish phases and activities Document throughout the development Establish standard; database, software, interface Manage the process and projects Justify IS as capital investments Don’t be afraid to cancel or revise the scope Divide and conquer Design system for growth and change 4

5. Where do ISDP come from? PIECES for classifying problems (james wetherbe, 1994): P the need to correct or improve PERFORMANCE I the need to correct or improve INFORMATION (and data) E the need to correct or improve ECONOMICS C the need to correct or improve CONTROL or security E the need to correct or improve EFFICIENCY of people and processes S the need to correct or improve SERVICE the player 5

6. 6

7. FAST Methodology

8. Requirements Discovery Approaches Fact-finding Techniques Sampling of existing documentation, reports, forms, files, databases , and memos Research of relevant literature, benchmarking , site visits Obeservatioan of the current system and the work environment Questionnaires and surveys Interviews of managers, users, and technical staff Joint Requirem e nt Planning ; The analyst as facilitator for a workshop will typically run from three to five full working days

9. Identify Business Actors By focusing on the actors, you can concentrate on how the system will be used (not how it will be built) Actor should be named with a noun or noun phrase Where to look for potential actors? Context diagram ; Existing system documentation and user manuals ; Minutes of project meetings and workshops ; Existing requirement documents, project charter , or statement of work Ask? Who or what provides inputs to the system? Who or what receives output from the system? Are interfaces required to other systems? Are there any events that are automatically triggered at a predetermined time? Who will maintain information in the system?

10. Identify Business Requirement Use Cases A typical IS may consist of dozens of use cases Identify only the m ost critical, complex , and important one s , essential use case Ask? What are the main tasks of the actor? What information does the actor need from the system? What information does the actor provide to the system? Does the system need to inform the actor of any changes or events that have occurred ? Does the actor need to inform the system of any changes or events that have occurred ?

11. Context Diagram

12. Use Case Diagram

13. Document Business Requirements Use-case Narratives

14. ERD Perpustakaan

15. ERD dan Tabel Datahttps://www.yworks.com/yed-live/

16. ERD dan Tabel Datahttps://www.yworks.com/yed-live/

17. Tabel Akhir