1 / 26

Requirements

Requirements. Analisa dan Perancangan Sistem Informasi. Outlines . Requirements. Requirements. Requirements are the voice of customer They’re hard to get right. Story About Requirements. Story about the rain. Story about misperception. Apakah Requirement Itu ?.

havily
Download Presentation

Requirements

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

  2. Outlines • Requirements • ... ADSI - Universitas Narotama

  3. Requirements Requirements are the voice of customer They’re hard to get right ADSI - Universitas Narotama

  4. Story About Requirements Story about the rain Story about misperception ADSI - Universitas Narotama

  5. Apakah Requirement Itu? • Kemampuan yang harusdimilikiuntukmencapaisesuatu. • Kemampuanataucirikhususyang harusdimilikiolehsistem. • Berasaldari client, contract, standard, atauspesification. ADSI - Universitas Narotama

  6. KenapaSulit? • Sering kali, user tidakmengetahuisecarapastiapa yang benar-benarmerekainginkan. • Perbedaankepentingan. • Melibatkan orang. ADSI - Universitas Narotama

  7. Evolusi Requirement • Product vision (1/2 halaman) • User requirements (2 halaman features list) • Sangatumum, dan • Terkadangtidaklengkap. ADSI - Universitas Narotama

  8. EvolusiRequirement (cont’d) • System requirements (50 halaman) • Lebihmendetail, dibuatoleh SE dariuser requirements, • Dapatberfungsisebagaikontrak/pengikatdengan user, dan • Dapatberisisebagiankecildesign. ADSI - Universitas Narotama

  9. Evolusi Requirement (cont’d) • Software requirements document (250 halaman) • User requirement + system requirement + detail lebihmendalam. • Digunakanoleh internal. ADSI - Universitas Narotama

  10. Macam – Macam Requirement • Functional Requirement • Non-Functional Requirement • Lainnya: • Environmental • Scheduling • Specific ADSI - Universitas Narotama

  11. Functional Requirements • Menggambarkanapayang sistemharuslakukan. • Apa input/output-nya. • Apasaja data yang harustersimpan. • Apasajakomputasi/algoritma yang diperlukan. • Konsep, fungsi, fitur, informasi, atapunbehaviours. Inibiasanyatermasukpadadaftar yang dimulaidengan kata “sistemakan…”. ADSI - Universitas Narotama

  12. ContohFunct. Requirements • The system mustallow easy and efficient data entry and reporting. • The system mustallow remote backup and restore capability of data. • The system shallstore a history of client record changes. • …. ADSI - Universitas Narotama

  13. Non-Functional Requirements • Syarat/konstrain yang harusterpenuhiataudiikutiyaitu: • Response time • Throughput • Resource usage • Reliability • Availability • Security • Recovery from failure • Cost • Technology to be used • Organization structure should not be…. • Metodology to be used. ADSI - Universitas Narotama

  14. Requirements yang Lain • Environmental Requirements: • Hardware, equipment, communications, interfaces, software, languages, standards, … • Scheduling Requirements: • Delivery date, … ADSI - Universitas Narotama

  15. Yet Another Requirements • Concious Requirements: adapadapikiran user. • Unconcious Requirements: tidakdisebutkan. • Undreamed of Requirement: sesuatu yang akanditanyakanoleh user ketikamerekasadar. ADSI - Universitas Narotama

  16. Tool yang DapatDigunakan • General tools: word processor, spreadsheet, …. • Kelebihan: flexible, ubiquitos (adadimanasaja). • Kekurangan: poor tracability & other support, tidakmudahuntuk di-maintain. • Requirement tools: Rational Rose, Poseidon UML, Astah, Power Designer, Visio, … • Kelebihan: good tracking seperti support, danterstruktur. • Kekurangan: tidak flexible, overkill untuk project skalakecil. ADSI - Universitas Narotama

  17. Requirements Specification • Narative. Menggunakanbahasa natural (Bahasa Indonesia, Inggris, …) • Kelebihan: flexible • Kekurangan: ambigu. Susah untukmenemukan requirement yang terkait. Requirement terkadangtidakdapatdigambarkansecaraefektifolehbahasaitusendiri. ADSI - Universitas Narotama

  18. Requirements Specification (cont’d) • Graphical. UML, DFD, ERD, … • Kelebihan: digunakansecaraumum. • Kekurangan: memilikisemantik yang tidakterikat. ADSI - Universitas Narotama

  19. Requirements Specification (cont’d) • Matematical. Finite State Machines, Petri Nets, … • Kelebihan: tidakambigu. • Kekurangan: perluwaktumemahaminya. ADSI - Universitas Narotama

  20. BagaimanaMendapatkan Requirements? • Observasi • Interview • Brainstorming • Prototyping • User Stories • Intensive Brainstorming atau Joint Application Development (JAD) • …. ADSI - Universitas Narotama

  21. TantangandanResikonya • Kurangmemahamipermasalahansebenarnya. • Requirement berubahdengancepat. • Tidakmudahuntukmenetapkan requirements secaratepat. ADSI - Universitas Narotama

  22. Requirement Pitfalls • Mengasumsikan requirement dilakukanolehdeveloper. • Konsumenbingungdengandeveloper begitujuga vice versa. • Dialog/komunikasiantar developer yang kurang. • Perubahan requirements yang kurangdiantisipasi. • Terlaluterburu-burumendapatkanrequirements. ADSI - Universitas Narotama

  23. Mendapatkan Requirements • Dwight Eisenhower, pemimpinpasukansekutupadaPerangDunia II mengatakan: • “the plan is nothing; the planning is everything.” • “the discovery is nothing; the discovering (the exploring) is everything.” Kualitasdari…. Proses dari…. ADSI - Universitas Narotama

  24. Requirements yang Berkualitas • Correct – hanyaperspektif yang dapatmenentukan. • Feasible – benardapatditerapkan. • Necessary – setiap requirement dapat di-trace kembalikeasalnya. • Unambiguous – satupersepsi. • Verifiable – bagaimanadapatdiketahuibahwarequirement telahdiimplementasikandenganbenar? • Prioritized – nilaidarifungsi yang disediakan. ADSI - Universitas Narotama

  25. Latihan: • Dapatkan requirement dari: • Perpustakaan, • Akademik, • …. ADSI - Universitas Narotama

  26. Referensi: • ArisTjahyanto, 2005, ADSI, ITS Surabaya ADSI - Universitas Narotama

More Related