SOFTWARE ENGINEERING

Session 4 – Requirement Engineering

DEPARMENT OF COMPUTER SCEINCE Contact Person |

ENGINEERING AND SCIENCE arao.ternorio05@gmail.com
hcmfe6a
 Objetivu
• Komprende konaba saida maka requirements
engineering
• Hatene no Komprende konaba tipu husi
requirements
• Komprende konaba User and system requirements
• Komprende konaba Functional and non-functional
requirements
Saida maka Requirement ?
Bele temi defenisaun husi requirement..

DEPARTMENT OF COMPUTER SCIENCE

SCHOOL OF ENGINEERING AND SCIENCE
 Requirements engineering
• Prosesu estabelesimentu service nebe costumer
hakarak husi sistema no limitasaun nebe nia opera
no dezenvolve ba.
• Rekezitus nee rasik maka deskrisaun konaba
servisu sistema no limitasaun sira nebe maka sei
produs durante prosesu engenharia de rekezitus.

Chapter 4 Requirements engineering 4

 What is a requirement?
• Requirement : buat nebe ita hakarak, presija ou
sujere ba (Davis,1993).
• Tuir IEEE, Requirement :
• Kondisaun ou abilidade nebe presija husi user hodi
rezolve problema ruma ou atu atinji objetivu.
• Kondisaun ou kapasidade nebe tenki iha husi sistema ou
komponente sistema hodi kompleta kontratu, standar,
spesifikasaun ou dokumentus formal seluk tan.

Chapter 4 Requirements engineering 5

 Objetivu husi Analiza Requirement

• Komprende konaba user nia hakarak ba kriasaun

software hodi resolve obstaklu nebe hasoru.
• Defini saida maka tenki halo ou opera husi software
hodi bele responde ba necesidade husi user

• Razaun atu halao analiza requirement tamba :

• Mosu idea hodi hadia problema nebe mosu iha Sistema
atual,
• Mosu idea hodi halo software foun ida.
 Types of requirement
• User requirements
• Statement iha linguajen simples ho diagrama konaba
service husi sistema nebe atu uza, no obstaklu ba ninia
operasaun. Halo ba customers.
• System requirements
• Dokumentus stuturadus ida, nebe defini deskrisaun
detailhu konaba funsaun Sistema, ninia service no
obstaklu operasionais husi sistema. Husi dokumentus
nee, bele sai hanesan kontratu entre client and
contractor.

Chapter 4 Requirements engineering 7

e.g. User and system requirements
• User requirements
• Sistema bele halao operasaun ba prosesamentu dadus
livru nebe iha biblioteka.
• System requirements
• Sistema bele atende aumenta dadus livru nebe
hatama(input) husi user
• Sistema bele halo atende hadia(edit) dadus livru nebe
rai iha database ida
• Sistema bele atende hamos(delete) dadus livru.

Chapter 4 Requirements engineering 8

 System requirements
• Spesifikasaun nebe detailhu husi funsaun Sistema,
service no obstaklu husi user requiments
• Sai hanesan baze hodi konstrui Sistema
• Hatama ba Sistema kontratu
• Rekezitus ba Sistema bele defini ou dezenha utiliza
model system

Chapter 4 Requirements engineering 9

 User requirements
• Tenki deskreve necesidade funsionais no non-
funsionais iha forma nebe bele atu komprende husi
user system nebe laiha konhesimentu tekniku nebe
klean.
• User requirements definidu utiliza linguagen
natural, tabela no diagrama atu nunee user bele
komprende.

Chapter 4 Requirements engineering 10

 Functional and non-functional requirements

• Functional requirements
• Statements konaba service sistema ida, nebe tenki fornesidu, oinsa
sistema tenki reajen ba input no oinsa sistema tenki komporta iha
situasaun nebe espesífiku.
• Non-functional requirements
• Limitasaun ba service ou funsaun nebe oferese husi sistema hanesan
obstaklu ba tempu, obstaklu ba prosesu dezenvolvimentu, standar no
seluk tan.
• Domain requirements
• Rekezitus husi domain aplikasaun konaba sistema no nebe refleta ba
karaterístika husi domain refere.

Chapter 4 Requirements engineering 11

 Functional requirements
• Functional requirement temi mos necesidade
operasional husi sistema
• Deskreve funsionalidade ou service husi sistema.
• Functional requirement relasiona ho funsaun ou
prosesu transformasaun nebe tenki halao husi
software
• Rekizitus funsionais sistema tenki deskreve service
system ho detailhu.

Chapter 4 Requirements engineering 12

 E.g. Functional Requirement

• Sistema tenki rai (save) detalhu dadus konaba livru

nian,
• Sistema tenki bele prosesa dadus ema nebe
empresta livru iha biblioteka
• Sistema tenki bele print relatoriu konaba livru nebe
iha biblioteka
• Sistema tenki identifika funsionáriu ida-idak ne'ebé
uza sistema ne'e tuir ninia númeru funsionáriu ho
númeru dijitu 8.

Chapter 4 Requirements engineering 13

 Non-functional Requirements
• Necesidade ida nebe defini karater husi software
hanesan velosidade(speed), loloos(accuracy), ou
frekuénsia (frequency)
• Non-functional requirements karik importante liu
do que rekezitus functional requirements. Se nee
maka la atinji, sistema dalaruma bele la uza.

Chapter 4 Requirements engineering 14

 E.g. Non-unctional Requirement

• Tempu atu fo sai informasaun maximu durante

minutu 1
• Sistema tenki bele prosesa dadus to’o tokon record
1 ba kada tranzasaun
• Sistema bele uza ho multi user tuir autoridade nebe
defini ona.

Chapter 4 Requirements engineering 15

 Metrics Spesifikasaun ba
Non-functional Requirements
Property Measure
Speed Processed transactions/second
User/event response time
Screen refresh time
Size Mbytes
Number of ROM chips
Ease of use Training time
Number of help frames
Reliability Mean time to failure
Probability of unavailability
Rate of failure occurrence
Availability
Robustness Time to restart after failure
Percentage of events causing failure
Probability of data corruption on failure
Portability Percentage of target dependent statements
Number of target systems

Chapter 4 Requirements engineering 16

 Etapa Analiza Requirement
• Teknikamente analiza necesidade software
kompostu husi sequensia de atividade hanesan :
• Estuda no entende ninia problema
• Identika necessidades User
• Defini requisitus software
• Kria dokumentus ba espesifisaun rekizitus
• Review necessidades
 Requirements completeness and
consistency
• Iha nia prinsipiu, rekizitus tenki kompletu no konsistente
• Kompletu
• Tenki inklui deskrisaun husi fasilidade tomak nebe
necessáriu.
• Konsistente
• Labele iha konflitu ou kontradisaun iha deskrisaun
fasilidade sistema.
• Iha pratika, imposivel hodi produs dokumentus ba rekezitus
nebe kompletu no konsistente.

Chapter 4 Requirements engineering 18

 Contact Person |
arao.ternorio05@gmail.com
hcmfe6a

Perguntas ruma..
Konaba introdusaun ba materia..

DEPARTMENT OF COMPUTER SCIENCE

SCHOOL OF ENGINEERING AND SCIENCE