SOFTWARE ENGINEERING

Session 3 – Software process model

DEPARMENT OF COMPUTER SCEINCE Contact Person |

ENGINEERING AND SCIENCE arao.ternorio05@gmail.com
f5yvrq5
Computer Science Software Engineering 1
 Objetivu
• Komprende saida maka software process;
• Komprende no hatene aktividade jeral iha process
software;
• Karakteristika husi software process nebe diak;
• Process Models iha Software Engineering;
• Komprende konaba Plan-driven and agile processes
ho ninia faze tomak.

Computer Science Software Engineering 2

 Software Engineering Layers

• Software process hanesan framework ida hodi

dezenvolve software nebe kualidade.

Computer Science Software Engineering 3

 Software Engineering Layers

• Foku husi software engineering maka atu hatan ba

kualidade “Quality Focus”. Kualidade nee, traduzida ba
medidas (metrics), kobre maintainability, dependability,
usability, no efeciency.
• Process : defini sikuensia de servisu (framework), nunee
dezenvolvimentu software bele halao ho sistematikamente.
• Methods: define oinsa software atu konstrui, inklui ninia
metodu nebe utiliza hodi halao analiza necesidade, design,
implementasaun, no teste. Por ezemplu structured method,
object-oriented methods, etc.
• Tools: software nebe ho karater automátikus ou
semiautomátikus nebe nia funsaun hodi suporta kada etapa
iha dezenvolvimentu software. e.g: CASE, CAD, no seluk tan.
Computer Science Software Engineering 4
Saida maka
software process???
Bele temi tok mai..

DEPARTMENT OF COMPUTER SCIENCE

SCHOOL OF ENGINEERING AND SCIENCE

Computer Science Software Engineering 5

 Software Process

“
• Software Process: Série de aktividades nebe foka
ba produsaun produtu software
(sommerville,2007).
• Software Process: sequensia de etapa nebe utiliza
hodi dezenvolve no halo manutensaun ba software.
• Software Process: framework tékniku no jestaun
hodi aplika method, tools nomos komponente
rekursu humanu hodi dezenvolve software.

Computer Science Software Engineering 6

 Software Process
• Software process barak nebe la-hanesan maibe hotu-
hotu involve iha:
• Specification – Defini saida maka tenki halo husi sistema;
• Design and implementation – Defini organizasaun husi
sistema no implementasaun sistema;
• Validation – cek katak sistema halao saida maka customer
hakarak;
• Evolution – muda sistema hodi hatan ba mudansa husi
necesidade customer.
• Software process model hanesan reprezentasaun
abstrata husi procesu ida. Software process model
aprezenta deskrisaun husi prosesu ida husi perspektiva
partikular.
Computer Science Software Engineering 7
 Software Process Descriptions

• Wainhira ita deskreve no deskuti konaba prosesu,

babain ita kolia konaba aktividade iha prosesu nee,
hanesan defini data model, designing a user interface,
etc. no oinsa manda ativitidade nee.
• Deskrisaun konaba prosesu inklui mos:
• Products(produtu), nebe sai hanesan outcomes husi process
activity ida;
• Roles(knaar), nebe refleta responsabilidade husi ema nebe
involve iha prosesu;
• Pre- and post-conditions, hanesan declarações(statements)
nebe los (true) antes no depois process activity ida
promulgada ou produtu nee produzidu.

Computer Science Software Engineering 8

 Plan-driven and agile processes

• Plan-driven processes : prosesu ida, iha nebe

aktividade prosesu tomak planeiadu antes no nia
progresu sei sukat bazeia ba planu refere.
• Iha agile processes, planeiamentu ho karater
incremental no fasil liu atu muda ninia prosesu hodi
hatan ba rekezitus customer nian.
• Iha pratika barak maka inklui ona : plan-driven and
agile approaches.
• Laiha process software nebe los ou sala.

Computer Science Software Engineering 9

 The Waterfall Model

Computer Science Software Engineering 10

 Waterfall model phases
• Iha faze identifikadas nebe ketak-ketak iha waterfall
model:
• Requirements analysis and definition
• System and software design
• Implementation and unit testing
• Integration and system testing
• Operation and maintenance
• Desvantagem husi waterfall model maka difisil atu
akomoda mudansas depois de prosesu lao ona. Em
prinsípiu, faze ida tenki remata antes hakat ba faze
tuir mai.

Computer Science Software Engineering 11

 Waterfall model problems
• Fahe projetu iha ninia etapa nebe diferente, halo nia
difisil atu hatan ba mudansa husi necesidade customer
nian.
• Tamba nee, model nee so deit uza wainhira rekezitus
komprende ho diak no mudansa tenki naton deit durante
prosesu design.
• Business systems balun iha rekezitus nebe estáveis.
• Waterfall model dalabarak liu uza, ba projeitu systems
engineering nebe nia sistema dezenvolvidu iha varius
lokais.
• Iha situasaun hanesan nee, natureza plan-driven iha waterfall
model ajuda tebes atu koordena servisu.

Computer Science Software Engineering 12

 Incremental development

Computer Science Software Engineering 13

 Incremental development benefits

• Kustu hodi akomoda mudansa ba rekezitus

customer sei reduz.
• Kuantidade ba analiza no dokumentasaun nebe tenki
repete sei menus ona, kompara ho waterfall model.
• Fasil liu atu hatan ba feedback husi customer ba
servisu nebe halo tiha ona.
• Customer bele comment ba demonstrasaun software no
hare oinsa mudansa barak nebe aplika ona.
• Rapidu liu manda no fahe software nee ba
customer
• Customers bele uza no hetan valor husi software, sedu
liu kompara ho waterfall process.
Computer Science Software Engineering 14
 Incremental development problems

• Processo nee la-visível(la-bele atu hare).

• Dirigente/Managers presija rezultadu servisu hodi sukat
ninia progressu. Se Sistema dezenvolvidu ho lalais, kustu
sei la-efetivu hodi produs dokumentus nebe refleta ba
kada versaun husi Sistema.
• Strutura husi sistema sei hasai tuir mudansa foun.
• a não ser que, tempu no osan nebe hasai ba re-
struturasaun hodi hadia software, mudansa dalabarak
liu estraga ninia strutura. Hatama mudansa iha software
sei difisil no karun.

Computer Science Software Engineering 15

 Reuse-oriented software engineering

Computer Science Software Engineering 16

 Reuse-oriented software engineering

• Bazeia ba re-utilizasaun sistemátika nebe ninia

sistema integradus husi komponentes iha ou
sistemas COTS (Comercial-off-the-shelf)
/Commercial pronto para utiliza.
• Etapas husi processu
• Component analysis;
• Requirements modification;
• System design with reuse;
• Development and integration.
• Reuse agora nee sai hanesan abordagem standard
hodi konstrui tipu barak iha business system.

Computer Science Software Engineering 17

 Types of software component in
Reuse-oriented
• Web services nebe dezenvolvidu adapta ho
standards service no disponíveis para chamada
remote(distansia dook).
• Kolesaun husi objetu nebe dezenvolvidu hanesan
pakote hodi integra ho komponente framework
hanesan .NET or J2EE.
• Stand-alone software systems (COTS) nebe
konfiguradu no utiliza ba ambiente espesífiku.

Computer Science Software Engineering 18

 Process activities
• Iha baze process activities 4 hanesan specification,
development, validation and evolution, organizadu
ho diferente iha prosesu dezenvolvimentu nebe
diferente.
• Iha waterfall model, organizadu iha sequências,
enquantu iha dezenvolvimentu incremental ho
intercalada.

Computer Science Software Engineering 19

 Software specification
• Prosesu nebe estabelese, service saida maka presija no
dezafiu iha operasaun no dezenvolvimentu sistema.
• Rekezitus iha engineering process :
• Feasibility study
• Téknikamente no finanseiramente viável hodi konstrui sistema?
• Requirements elicitation and analysis
• Saida maka presija/hakarak husi stakeholders ba sistema?
• Requirements specification
• Defini rekezitus ho detalhu
• Requirements validation
• Verifika validade rekezitus

Computer Science Software Engineering 20

 The requirements engineering process

Computer Science Software Engineering 21

 Software design and implementation

• Prosesu muda espesifikasaun sistema sai sistema

nebe bele atu ezekuta.
• Software design
• Dezenhu strutura software nebe realiza espesifikasaun;
• Implementation
• Tradus strutura nee ba programa nebe bele ezekuta;
• Aktividade husi design and implementation
relasionadus no bele mos intercalados.

Computer Science Software Engineering 22

 A general model of the design process

Computer Science Software Engineering 23

 Design activities
• Architectural design, wainhira ita identifika strutura
Sistema tomak, komponente prinsipais (dalaruma temi
sub-systems ou modules), sira nia relasaun no oinsa sira
halo distribuisaun.
• Interface design, wainhira ita defini interfaces entre
komponentes sistema.
• Component design, wainhira ita foti kada komponente
Sistema no design oinsa nia bele opera.
• Database design, wainhira ita design strutura sistema
data no oinsa bele atu reprezenta iha database ida.

Computer Science Software Engineering 24

 Software validation
• Verification and validation (V & V) : ho objetivu atu
hatudu katak Sistema ida hanesan ho ninia
spesifikasaun no hatan rekezitus customer.
• Involve verifikasaun no revizaun ba processos no
testes ba sistema.
• Testes ba Sistema involve ejekusaun Sistema ho
teste kazu nebe hatun husi spesifikasaun data real
nebe sei produs husi Sistema.
• Teste maka aktividade V&V nebe barak liu utiliza.

Computer Science Software Engineering 25

 Stages of testing

Computer Science Software Engineering 26

 Testing stages
• Development or component testing
• Komponentes individuais nebe testadus
independentemente;
• Komponentes bele iha forma funsaun ou objeitu ou
agrupamentu koherente iha entidade nee.
• System testing
• Teste ba Sistema em jeral. Teste propriedades nebe iha
importante tebes.
• Acceptance testing
• Teste ho customer data hodi verifika katak Sistema
atende ba necesidade customer.

Computer Science Software Engineering 27

 Task - Squad
Model Process Group  Esplika konseitu husi model
Spiral Model nee, ninia faze, strength no
weakness no wainhira
Prototype Model maka uza model nee.
Rapid Application Development (RAD)
V-model  4 students/squad
 Task presented next week
Extreme Programming (XP) (according to schedule)
Scrum  Presentation material
made in .ppt
Dynamic Systems Development Model (DSDM)
 Send it to classroom
Lean Software Development [LSD]
Kanban
Feature Driven Development

Computer Science Software Engineering 28

Perguntas ruma..
Konaba esplikasaun ba materia ohin..

DEPARTMENT OF COMPUTER SCIENCE

SCHOOL OF ENGINEERING AND SCIENCE

Computer Science Software Engineering 29