Requirements Determination ( Penentuan Kebutuhan )

1. Requirements Determination (PenentuanKebutuhan)

2. Tujuan • Memahamibagaimanacaramendefinisikankebutuhan (requirement) ? • Mampumenerapkanteknisanalisakebutuhan • Mengetahuimacam-macamteknikpengumpulankebutuhan

3. Kebutuhan (Requirements) • Requirement determination merupakantahappentingpada SDLC karenamerupakanawalanpembangunansistem. • A requirement menyatakanapasaja yang harusmampudilakukansistemataukarakteristiksepertiapa yang harusdimilikisistem. • Identifikasikebutuhandilakukandariperspektifpengguna. • Fokuspada “what” darisistem & kebutuhan user.

4. Functional Requirement • Is a processthe system has to perform or information it needs to contain • These requirements are the technical specifications, system design parameters and guidelines, data manipulation, data processing, and calculation modules etc, of the proposed system.

5. Contoh Functional Requirement • Purchasing System : • Supports user defined vendor types • Supports unique vendor address and contact information for vendor corporate address, remit to address, and ship to address • Supports automatic purchase order generation default by vendor • Supports minimum and maximum receipt allowances by vendor • Supports tracking of last price paid for an item • Supports calculation of purchased price variances (PPV) • Supports online inquiry or report to compare actual vs. expected purchase costs • Allows purchase order price to default to last amount paid • Tracks vendor performance on late deliveries • Tracks vendor performance on order fill rates

6. Non-functional Requirement • Is a behavioural property that the system must have, such as performance & usability • Include constraints and qualities. • Qualities : properties or characteristic of the system that will affect the user satisfaction. Type : run-time and development-time qualities. • Berpengaruhscrtidaklangsungthdprosesselanjutnya, misalnyauntukmenentukantipeantarmuka, hardware & software, danarsitekturfisiksistem

7. Run-time Quality • Describe how well the functional requirements are satisfied. • Include : • usability (ease-of-use, learnability, memorability, efficiency, etc.) • configurability and supportability • correctness, reliability, availability • quality of service requirements such as performance (throughput, response time, transit delay, latency, etc.) • safety properties (so-called because they “prevent bad things from happening”), such as security and fault tolerance • operational scalability including support for additional users or sites, or higher transaction volumes

8. Development Quality • Describe the quality of the artifacts (architecture, design, code, etc.) of the development process. • Include : • localizability—ability to make adaptations due to regional differences • modifiability or extensibility—ability to add (unspecified) future functionality • evolvability—support for new capabilities or ability to exploit new technologies • composability—ability to compose systems from plug-and-play components • reusability—ability to (re)use in future systems

9. Source of Non-functional Req. • System constraints • User objectives, values, and concerns • Competitive analysis of feature • Development organization constraints • Development organization objectives, values, and concerns • Competitors and industry trends

10. Requirements Definition • Is a straightforward text report that simply lists the functional and nonfunctional requirements in an outline format.

11. Example of Requirements Definition

13. Exercise Tentukanmana yang tmskkebutuhan functional & non-functional : • Sistemharusmampu : • Diaksesolehpengguna web • Mencantumkan logo dan theme warnaperusahaan • Membatasiaksespadainformasitertentu • Menampilkaninformasibiayaaktualdananggaran • Menyediakanlaporanmanajemen • Menyimpaninformasipenjualan yang diperbaruisetidaknyaseharisekali • Wakturesponuntuk pre-defined query adalah max. 2 detik,sedangkanuntuk ad-hoc query max. 10 menit • Mencantumkaninformasidariseluruhanakperusahaan • Mencetaklaporantiapcabangsesuaidenganjenisbahasa yang umumdigunakanditiapcabang • Menyediakanrangkinguntukkinerjastafpenjualan

14. Requirements Analysis Techniques • Basic process of analysis : • understanding the as-is system • identifying improvements • developing requirements for the to-be system • Drives the kind of information that is gathered and how it is ultimately analyzed.

15. Determining Requirements • 3 macamteknik : • Business Process Automation (BPA) • Business Process Improvement (BPI) • Business Process Reengineering (BPR) • Those techniques : • help users critically examine the current state of systems and processes (the as-is system) • identify exactly what needs to change • develop a concept for a new system (the to-be system)

16. Business Process Automation • Means : • leaving the basic way in which the organization operates unchanged • using computer technology to do some of the work • Two techniques : • Problem analysis • asking the business users to identify problems with the as-is system and to describe how to solve them • focus on the problems • Root cause analysis • identifying the root cause of the problems • focus on the solutions

17. Business Process Improvement • Making moderate changes to the way in which the organization operates to take advantages of new opportunities offered by technology or to copy what competitors are doing • Techniques : • Duration analysis : • examination of the amount of time it takes to perform each process in the as-is system • Activity-based costing • examines the cost of each major process or step in a business process • focus on th most costly process • Informal benchmarking • studying how other organizations perform a business process

18. Business Process Reengineering • Changing the fundamental way in which the organization operates to take advantage of new ideas and new technology • Techniques : • Outcome analysis • focus on understanding the fundamental outcomes that provide value to customers • Technology analysis • identify how each and every new technology could be applied to the business process • Activity elimination • identify how the organization could eliminate each and every activity in the business process, how the function could operate without it, and what effects are likeli occur

19. How to select?

20. TugasKelompok • Review lahsalahsatudari website berikut : • www.amazon.com • www.google.com • www.youtube.com • www.yahoo.com • www.blogger.com • www.wikipedia.com • www.ebay.com • www.flickr.com • Definisikan requirements definition untuksitustsb. Buatlahdaftarkebutuhanfunctionaldarisitus yang andaobservasitsbselengkapmungkin. • Hasilkerjakelompokditulisdikertas A4, huruf TNR 11 spasi 1.5. Dikumpulkandalam format doc/docx via email gita.voyager@gmail.com paling lambatpadapertemuanselanjutnya.

21. Evaluation (15 Menit-Open Book) • Deskripsikanistilah-istilahberikut : • Business process improvement • The as-is system • Requirement definition • functional requirements • non-functional requirements

22. Evaluation (15 Menit-Open Book) • Deskripsikanistilah-istilahberikut : • Business process reengineering • The to-be system • Duration analysis • functional requirements • non-functional requirements

23. Evaluation (15 Menit-Open Book) • Deskripsikanistilah-istilahberikut : • Business process automation • Problem analysis • Activity-based costing • functional requirements • non-functional requirements

24. References • Dennis, Alan, et.al. System Analysis and Design with UML Version 2.0. John Wiley & Sons, Inc. • http://www.brighthub.com/office/project-management/articles/12259.aspx • Bredmeyer D., Malan R. Designing Non-functional Requirements. Bredemeyer Consulting.