requirements determination ( penentuan kebutuhan )

24
Requirements Determination (Penentuan Kebutuhan)

Upload: sue

Post on 25-Feb-2016

115 views

Category:

Documents


3 download

DESCRIPTION

Requirements Determination ( Penentuan Kebutuhan ). Tujuan. Memahami bagaimana cara mendefinisikan kebutuhan ( requirement ) ? Mampu menerapkan teknis analisa kebutuhan Mengetahui macam-macam teknik pengumpulan kebutuhan. Kebutuhan ( Requirements ). - PowerPoint PPT Presentation

TRANSCRIPT

Requirements Determination (Penentuan

Kebutuhan)

Slide 2

Tujuan Memahami bagaimana cara mendefinisikan

kebutuhan (requirement) ? Mampu menerapkan teknis analisa kebutuhan Mengetahui macam-macam teknik

pengumpulan kebutuhan

Slide 3

Kebutuhan (Requirements) Requirement determination merupakan tahap

penting pada SDLC karena merupakan awalan pembangunan sistem.

A requirement menyatakan apa saja yang harus mampu dilakukan sistem atau karakteristik seperti apa yang harus dimiliki sistem.

Identifikasi kebutuhan dilakukan dari perspektif pengguna.

Fokus pada “what” dari sistem & kebutuhan user.

Slide 4

Functional Requirement Is a process the 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.

Slide 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

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

Berpengaruh scr tidak langsung thd proses selanjutnya, misalnya untuk menentukan tipe antarmuka, hardware & software, dan arsitektur fisik sistem

Slide 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

Slide 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 differencesmodifiability or extensibility—ability to add

(unspecified) future functionalityevolvability—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

Slide 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

Slide 10

Requirements Definition Is a straightforward text report that simply

lists the functional and nonfunctional requirements in an outline format.

Slide 11

Example of Requirements Definition

Slide 12

Slide 13

ExerciseTentukan mana yang tmsk kebutuhan functional

& non-functional : Sistem harus mampu :

1. Diakses oleh pengguna web2. Mencantumkan logo dan theme warna perusahaan3. Membatasi akses pada informasi tertentu4. Menampilkan informasi biaya aktual dan anggaran5. Menyediakan laporan manajemen6. Menyimpan informasi penjualan yang diperbarui setidaknya

sehari sekali7. Waktu respon untuk pre-defined query adalah max. 2

detik,sedangkan untuk ad-hoc query max. 10 menit8. Mencantumkan informasi dari seluruh anak perusahaan9. Mencetak laporan tiap cabang sesuai dengan jenis bahasa

yang umum digunakan di tiap cabang10. Menyediakan rangking untuk kinerja staf penjualan

Slide 14

Requirements Analysis Techniques

Basic process of analysis :understanding the as-is system identifying improvementsdeveloping requirements for the to-be system

Drives the kind of information that is gathered and how it is ultimately analyzed.

Slide 15

Determining Requirements 3 macam teknik :

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 changedevelop a concept for a new system (the to-be

system)

Slide 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 problemsRoot cause analysis

identifying the root cause of the problemsfocus on the solutions

Slide 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 costingexamines the cost of each major process or step

in a business processfocus on th most costly process

Informal benchmarkingstudying how other organizations perform a

business process

Slide 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 analysisidentify how each and every new technology

could be applied to the business processActivity 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

Slide 19

How to select?

Slide 20

Tugas Kelompok Review lah salah satu dari website berikut :

www.amazon.comwww.google.comwww.youtube.comwww.yahoo.comwww.blogger.comwww.wikipedia.comwww.ebay.comwww.flickr.com

Definisikan requirements definition untuk situs tsb. Buatlah daftar kebutuhan functional dari situs yang anda observasi tsb selengkap mungkin.

Hasil kerja kelompok ditulis di kertas A4, huruf TNR 11 spasi 1.5. Dikumpulkan dalam format doc/docx via email [email protected] paling lambat pada pertemuan selanjutnya.

Slide 21

Evaluation (15 Menit-Open Book) Deskripsikan istilah-istilah berikut :

1. Business process improvement2. The as-is system3. Requirement definition4. functional requirements5. non-functional requirements

Slide 22

Evaluation (15 Menit-Open Book) Deskripsikan istilah-istilah berikut :

1. Business process reengineering2. The to-be system3. Duration analysis4. functional requirements5. non-functional requirements

Slide 23

Evaluation (15 Menit-Open Book) Deskripsikan istilah-istilah berikut :

1. Business process automation2. Problem analysis3. Activity-based costing4. functional requirements5. non-functional requirements

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