Software Requirements

COURSE REFERENCES
Main Reading
1. Software Engineering by Ian Sommerville,
8th edition, Addison-Wesley, 2006.
2. Software Engineering: A practitioner's
approach by Roger S. Pressman, 6
th

edition, McGraw-Hill International edition,
2005.
3. Software Requirements, by Karl E.
Wiegers , Microsoft Press 2003
2
LEARNING TARGET
What is a requirement?
What types of software requirements
are there?
What is Requirement Engineering?
What are Requirement Development
Process


3
Classic Life Cycle
(Linear Sequential Model)
Systems
Engineering
Analysis
Testing
Maintenance
Design
Coding
Prototyping Model
Requirements
Gathering
"Quick Design"
Build Prototype
Evaluate & Refine
Requirements
Engineer Product
A requirement is anything that drives
design choices (Lawrence 1997).
Requirements are a specification of what
should be implemented. They are
descriptions of how the system should
behave, or of a system property or
attribute. They may be a constraint on the
development process of the system

6
What is Requirement
SOFTWARE REQUIREMENT
Software requirements include three
distinct levels:
Business requirement
User requirement
Functional requirement
Business Requirement
Describe why the organization is
implementing the system the business
benefits the organization hope to achieve
The focus is on the business objectives of
the organization or the customer who
requests the system
Ex: an airline wants to reduce airport
counter staff cost by 25 percent. This goal
might lead to the idea of building a kiosk
that passenger can use to check in for their
flights at the airport
User Requirement
Describe goal or tasks the users must be
able to perform with the product that will
provide value to someone
Includes descriptions of product attributes
or characteristics that are important to user
satisfaction
Describe what the user will be able to do
with the system
Ex: a use case is Check in for a flight
using an airlines website or a kiosk at the
airport
Functional Requirement
Specify the behaviors the product will
exhibit under specific conditions.
They describe what the developers must
implement to enable users to accomplish
their task (user requirements), thereby
satisfying the business requirements
Ex: The passengers profile shall be able to
print boarding passes for all flight segments
for which he has checked in or if the
passengers profile does not indicate a
seating preference, the reservation system
shall assign a seat
Describe important characteristics or
properties of the system
Non-functional requirements describe how
well it does those things
Non-functional requirements describe the
quality attributes of the system.
Include the system availability, security,
reliability, performance, usability
Environment in which the system operates
such platform, portability, compatibility,
and constraints
11
Nonfunctional Requirement
12
Requirements Engineering
Requirements Development
Process

Requirements Development
Process
Elicitation: work with the customer on
gathering requirements
Analysis: process this information to
understand it, classify in various categories, and
relate the customer needs to possible software
requirements
Specification: Structure the customer input
and derived requirements as written documents
and diagrams
Validation: youll ask your customer to confirm
that what youve written is accurate and
complete and to correct errors.


Contoh Kasus: Sistem Informasi Rawat
Jalan Poliklinik ABC
Identifikasi Masalah
Permasalahan yang terjadi di Poliklinik ABC adalah
sebagai berikut:
1. Data-data yang disimpan di poliklinik masih
berjalan manual menggunakan kertas, padahal
kebutuhan akan data-data pasien rawat jalan,
rekam medis pasien serta dokter yang menangani
tiap pasien meningkat
2. Sistem yang dijalankan belum sepenuhnya
membantu pekerjaan, karena kebutuhan akan
data yang efektif dan efisien serta ada saat
dibutuhkan (availability) belum bisa terpenuhi
3. Penyediaan data yang banyak menyebabkan
overload data dan informasi kurang
Identifikasi Masalah
Penyimpanan data dalam bentuk kertas atau
manual menimbulkan resiko yang cukup besar,
seperti kebakaran, rusak atau bencana alam
yang bisa mengakibatkan data-data penting itu
hilang, sehingga diperlukan sistem yang bisa
menyimpan data lebih aman
Kebutuhan akan data yang efektif dan efisien
serta ada saat dibutuhkan (availability)
menjadi alasan utama untuk penyediaan
informasi yang akurat

Identifikasi Masalah
Data yang kurang lengkap menyebabkan
informasi pelayanan kesehatan juga
kurang, karena data tidak tersusun rapi
dan susahnya pencarian data yang
mengurangi kurangnya informasi dari data
tersebut
Dari berbagai alasan yang telah
diungkapkan di atas, maka pengembangan
Sistem Informasi Rawat Jalan Poliklinik ABC
ini dibuat untuk membantu menyelesaikan
permasalahan-permasalahan yang muncul.

Analisis Kebutuhan
Data yang dibutuhkan dalam
pengembangan Sistem Informasi ini
adalah :
Data Pasien: nama pasien, alamat, jenis
kelamin, tanggal lahir, agama, golongan
darah.
Data Dokter: nama dokter, alamat, jenis
kelamin, tanggal lahir.
Data Obat: nama obat, jenis obat,
aturan pakai, harga
Analisis Kebutuhan Data
Data Admin/Petugas: nama petugas,
alamat, jenis kelamin, tanggal lahir.
Data Pemeriksaan: data pasien, data
dokter, keluhan, diagnosa,
perlakuan/pemeriksaan, data obat
Data Biaya : data pasien, pemeriksaan,
total harga obat

Analisis Kebutuhan
Kebutuhan fungsional
Fungsi dari sistem ini adalah :
proses login untuk dokter dan petugas
proses pengelolaan data pasien, meliputi
input, update dan delete
proses pengelolaan data dokter, meliputi
input, update dan delete
proses pengelolaan data petugas,
meliputi input, update dan delete


Kebutuhan Fungsional
proses pendaftaran pasien, baik daftar
baru maupun pendaftaran untuk periksa
dilakukan oleh user petugas
proses searching/pencarian data (data
pasien, data dokter, data petugas, data
pemeriksaan, data obat)
proses pemeriksaan, dilakukan oleh user
dokter
proses pemberian obat, dilakukan oleh
petugas untuk diberikan kepada pasien