ENGENHARIA SOFTWARE

1.      Temi tok faktorizasaun-faktorizasaun mosu iha tempo kotuk engenharia software:

a.       La konsege organizasaun atu prediksaun tempo esforso no folin ba mudansa software.

b.      Kualidade software nebe produsaun la diak ou diak.

c.       Halo mudansa tetu folin software no hardware

d.      Aumenta uluk importante hosi software

e.       Mundansa teknologi software

f.       Mudansa teknologi hardware

g.      Nescesidade nebe aumenta hasoru hardware

h.      Nescessidade sei hardware nebe boot liu no kompleks

2.      Hasoru buat sira nebe hetan sai sasan tetu iha hili lingua pemrogram. Type ou lalaok hosi problema bisnis, tekniko ou nebe seluk tan?

a.       Difisil hosi problema nebe hasoru

b.      Hatene lingua pemrogram nebe hosi programmer

c.       Type ou lalaok halo data ou dadus, ou modelu batch processing ou online processing

d.      Hakarak lingua pemrogram nebe ita nian

e.       Hakarak program-program pustaka (libtary) nebe iha no hetan mudansa hosi lingua nebe sei hili

f.       Hatene hosi lingua pemrograam nebe mak sei uza

g.      Modelu hosi lingua pemrogram, compiler ou interpreter

h.      Halo lingua pemrogram karik iha mudansa-mudansa foun

i.        Halo mudansa hosi lingua pemrogram iha modifikasaun program sei akontese mudansa

j.        Konfigurasaun ssoftwaare no system software nebe uza ona.

3.      Jelaskan apa yang dimaksud dengan

a.      Programming in the large

In  software  development,  programming  in  the large can involve programming by larger  groups  of  people  or  by  smaller  groups  over  longer  time periods.  Either of these conditions  will  result  in  large, and hence complicated, programs that can be challenging for maintainers to understand.

With programming in the large, coding managers place emphasis on partitioning work into  modules with precisely-specified interactions. This requires careful planning and careful documentation.

With  programming  in the large, program changes can become difficult.^[2] If a change operates  across module boundaries, the work of many people may need re-doing. Because of this,  one  goal  of  programming  in  the  large involves setting up modules that will not need altering in the event of probable changes. This is achieved by designing modules so they have high cohesion and loose coupling.

Programming  in  the  large  requires  abstraction - creating  skills.   Until   a   module becomes   implemented  it  remains  an  abstraction.  Taken  together,  the abstractions should create  an  architecture  unlikely  to  need  change.  They  should  define interactions that have precision and demonstrable correctness.

b.      Programming in the small

In software development, programming in the small describes the activity of writing a  small  program.  Small  programs  are  typified by being small in terms of their source code size,  are  easy  to  specify, quick to code and typically perform one task or a few very closely related  tasks  very well.

Programming  in  the  small  can involve programming by individuals or small groups over  short  time periods and may involve less formal practices (for instance less emphasis on documentation  or  testing),  tools  and programming languages (e.g. the selection of a loosely typed scripting language in preference to a strictly typed programming language).

Programming  in  the  small  can  also  describe  an  approach  to  making  a prototype software  or  where  rapid   application   development   is   more    important   than stability or correctness.

In   computer   science    terms,   programming   in the small   deals  with short-lived programmatic behavior, often executed as a single ACID transaction and which allows access to local logic and resources such as files, databases, etc.

ENGENHARIA SOFTWARE

1.      Saida mak hanesan modern ba software?

a.       Defenisaun software:

Software katak hanesan dadus elektronik nebe rai no aruma hosi komputador, dadus hanesan ikus hetan hari hosi komputador iha modelu program hotu ou instruksaun hotu nebe hetan lao. Iha mos defenisaun seluk hosi software hanesan mos software nebe halo no kontrola software.

b.      Mudansa entre software no hardware

Software nebe hanesan ba hotu-hotu nee hanesan hardware katak sai hardware nebe hetan servisu ba lalaok nebe halo ona, nebe bai-bain hanaran instruksaun set. No hardware mesak hetan raba hosi ita ema nia liman, I mos software la hetan kaer hosi ita ema nia liman liu hosi fisik tamba hetan operaaun.

HISTORIA SOFTWARE

Tuir lolos ita labele hanoin oinsa mudansa hardware iha mos modelu hosi hardware primitive ou tempo uluk nebe sei uza aljabar. Bele mos nebe sei uza reprezentasaun ho binary digit (bit) I mos valor 1 (los ona/on) I mos 0 (sala/off), modelu nebe oi-oin nee aumenta arska I mos modelu ida-idk husik hela no mos grupo bit sai nebe (4 bit), byte (8 bit), word (2 byte), double word (32 bit).

Modelu software ba primeiru hanesan monta hamutuk ou tutan fiu entre ba parte iha komputador. Modelu iha acces komputador hanesan uza punched card  kartu nebe halo kuak. Uza komputador iha neba sei halo program hotu ba mesin hotu nia hakarak hanesan. Ba tempo agr nee software hanesan ida ba ida ho software, uza komputador hotu print out. Prosesu nebe halo iha komputador laran hotu tuir instruksaun nebe liu tuir nia prosesu.

Ba tempo stabil uza komputador barak mak uza ona laos deit hosi peneliti no akademi deit. I mos hosi industry /projek. Ba tempo agora nee software komesa besik sai ona produk hotu. Tuir software nebe halao hosi komputador laos ona ida-ida, maibe hanesan prosesu barak nebe halo liu hosi( multi talsking), software hotu bele halo uza barak (multi user) liu hosi lalais ou fo liu (real time). Ba tempo agora nee komesa konhecementu sistema bsis dadus, nebe fahe entre program (pemroses) ho dadus (nebe sei prosesu).

TEMPO MIKRO

Halao I mosluan PC no linha ou rade komputador iha tempo nee, software mos mudansa atu halo nescesidade ema. Software hetan mudansa sai software sistema nebe servisu internal no software aplikasi nebe uza ba liu hosi presiza nebe hanesan automatika nebe iha software laran.

TEMPO MODERNU

Agora nee software hetan ona iha nebe deit, komputador hotu hahu kompletu ho software nebe hetan sinkronkan no PC. I mos sasan hanesan telfoni, tv, I mos ba mesin fase. AC no microwave iha ona software atu halo operasaun sasan nee.

Software hotu laos ona servisu segelentir ema, maibe sai ona servisu ema barak, no hira-hira mak iha parte prosesu nebe hanesan disiplin materi. Software agora komesa ona konhecementu lian no dezenu.

2.      Hatete tok siklus software!

Iha teknologi sitema informasaun uza hanesan funsaun organizasaun nebe seluk ho sistema informasaun nebe presiza prosesu dadus komputador. Funsaun informaaun fahe hosi funsaun uza, funsaun sistema informasaun nee laos uza mesak.

Projetu mudansa sistema hotu halao hosi tim projetu hari hosi analisis system pemrogram, iha organizasaun nebe aprezenta kona ba no mos sei prrosesu hosi projetu hotu no sistema (system developmentlife cycle), nebe liu hosi relative hanesan analisis, sistema nebe servisu hamutuk no uza atu defenisaun nescesidade informasaun espesifikasaun sira. Nescesidade- nescesidade hanesan hotu iha informaaun ba funsaun sistema.

Hasorru modelu haat (4) iha analisis sistema:

1.      Survey sistema nebe lao

2.      Identifikasi nescesidade

3.      Identifikasi nescesidade sistema nebe presiza atu nescesidade informasaun nebe uza.

4.      Halo ou hatoo relatorio sistema

Implemeentasaun akontese iha nebe sistema monta no lao iha sasan komputador. Dalaruma sistema foun presiza mudansa ou hakarak formal atu implementasaun, karrik sistema implementasaun ona, tenke iha hanoin no kontinua resmi no evaluasi sistema foun la kontinua nee tenke halo komentariu uza nian.

DOKUMENTSI

Dokuntasi primeiro hatudu nescesidade ddokumentasi nebe tenke modern durante projek mosu sistema sai hanesan organisasi boot halo primeiru, mosu sistema formal atu tau hamutuk isu-isu hanesan metode nebe tenke uza dokumentasi akuntansi projek. Relatoriu ba oin servisu no prosedur –prosedur nebe mosu hahu document nebe halao modernu sistema hatudu katak organisasi no metode sukat no materi-materi nebe relasaun hotu iha leet atu hatudu iha juiz.

STUDY

Study katak analisis nebe halo hotu hatudu saida mak projek ou la funsaun study, atu responde hotu perguntas teknis, ekonomis, no operasional:

1.      Tekniko hanesan hari saida mak sitema nebe relasaun hanesan dalaruma ho teknologi nebe iha ona agora.

2.      Ekonomis hanesan hari saidaa mak sitema nebe relasi valor vantagen nebe liu nia ffolin

3.      Operasional kuidadu saida mak sistema nebe relasi iha valor iha tempo nee, ntaun lori sitema nebe uza no simu hosi uza ikus ona.

DIAGRAM

Hari hosi modelu barak document diagram arus logika I mos HIPO ou IPO ou tekniku-tekniku modelu nebe uza hosi tim projek no perguntas nebe klaru kona ba karakteristika operasional hosi sistema nebe relasi, kamus dadus dokumentasi bele deit ba databae, ba field nebe registu.

3. esplika tok saida ho modelu-modelu prosesu hanesan tuir mai nee:

a. waterfall

modelu sekuensial 1 linear ou dalaruma modelu hanesan paradigma modelu software nebe uluk liu. No mos barak mak uza, modelu nee relasi no sekuensial nebe komesa ba pasu no ba oin sistema ba sistema ba sistema hotu parte analisis, desaing, kode.

                       

  

 Modelu sistema informasaun

Modelu sistema informasaun primeiru komesa no hari hotu elemen ou komponente sistema no hili parte-parte nebe mak sei bele sasan modern software no kuidadu relasaun no hardware, user, no database.

Analisis nescesidaade software ba prroses nee halo analisis no tau hamutuk nescesidade sistema nebe hanesan domain informasaun. Funsaun nebe presiza sevisu ou informasaun nebe lori ba oin. Rezultadu analisis no tau hamutuk hanesan dokumentasi hare fali ba pelangan.

Ba prosesu desaing nescesidade software hotu hetan ona astes hanoin halo prosesu ba kode (coding). Prosesu nee focus ba strutura dadus, arsetektur dadus software representaaun interface, no detail algoritma procedural.

Kode hanesan prosesu ba desaing modelu nebe hetan komprende hosi mesin no uza lingua pemrogram. Depois de prosesu kode hotu, kontinua ho prosesu relasi ba program software, diak relasi logika internal, I mos relasi eksternal funsaun atu hare buat nebe dalaruma akontese problema no koko valor saida hari hosi hanesn no valor nebe hakarak.

Prosesu parte nebe ikus iha siklus hari no halo depois de software uza ba saida deit nebe itaa halo prosesu entre seluk:

Corrective Maintenance: koreksaun ou hetan problema ba software, nebe foun dteksi ba tempo software  nebe ita uza.

Adptive Maintenance: hanesan halao tuir mudansa nebe hanesan fatin nebe foun, hanesan hardware, peripeeral, sistema operasaun foun ezizi ba hari nebe aas iha sistema komputador, aumenta  driver no seluk tan.

Perfective maintenance: se software diak bele ona uza ou aumenta kapasidade hanesan fo funsaun-funsaun aumenta kinergia nebe aas no seluk tan.

b.modelu prototype

Metode prototype hanesan mos paradigm iha metode foun iha metode mudansa software iha nebe metode nee sei la evaluasi iha mundu mudansa software maibe evaluasi metode software nebe tuan hanesan system sekuensial bai-bain konhecementu ho naran SDLC ou waterfall development model.

Iha model prototype, prototype hosi software nebe valor hotu presentasi. Mudansa no prototype hetan beei-beik software  nebe mudansa.

Tekniku- tekniku prototypen hanesan:

a.       Modelu

b.      Desaing

c.       Simulasi

Tuir mai iha tan funsaun nebe nia karakteristika prosesu hari ba metode prototype hanesan:

a.       Hili hosi funsaun

b.      Tau hamutuk system informsaun

c.       Evaluasi

d.      Uza ba tuir mai

Metode nee dezenu kompletu hosi sitem software hanesan iha partee modelu nebe aas modelu servisu no program, hari sei iha identifikasaun nescesidade nebe uza, analisis system no halo study hasoru nescesidade liu hosi modelu interface, tekniku prosedur no nebe sei fahe.

Hari prototyping no focus ba salariu hanesan mos halo iput no format ou hamos output.

c.       Prosesu model nebe seluk , nebe to popular katak  spiral modelu. Modelu nee moz too ona halo konhecementu nebe iha tinan 1988 hosi Barry Boehm, ba artikel A spiral model of software Development and Enchancement.

Spiral model katak ida modelu evalusi uza metode interasi natural, nebe hosi modelu prototyping no hamutuk ho aspek sistematis nebe hari ho modelu waterfall. Parte desaing hotu uza modelu waterfall,I mos parte prototyping hanesan modelu nebe, software halo prototype (incomplete model), “blue print”-nya exemplo no hatudu ba user /customer atu hetan feedback- nya.

Sekarik prototype los ona ho hakarak user/ costomer, maka prosesu SE kontinia ho produk nebe halo no aumenta I mos hadia nia desvantagen hosi prototype.

Modelu nee mos kombinasi top-down, desaing ho bottom-up desaing iha nebe top-down desaing nafatin sistema global. Hafoin kontinua ho sistematiko, I mos bottom-up desaing fali. Top-down desaing bai-bain aplikasi ba modelu waterfall ho sequential, bottom-up desaing bai-baain aplikasi ba modelu protyping no feedback nebe presiza.

Hosi kombinasi rua hanesan kombinasi entre desaing ho prototyping, I mos top-down no buttom-up, I mos aplikasi ba modelu waterfall no prototype, maka spiral modelu nee hetan sai modelu prosesu valor kombinasaun hosi modelu rua. Hosi ida nee modelu nee bai-bain uza atu halo software no skala boot no kompleks.

Spiral modelu fahe ba parte hira framework aktivitas nebe hanaran ho teks regions, kebanyakan aktivitas-aktivita fahe ba paarte tolu to aktivitas neen

Tuir mai aktivitas-aktivitas nebe halo ihaa modelu spiral.

Customer communication

Aktivitas nebe presiza atu hari komunikasaun nebe efektif  entre developer ho user/ customer I mos kona ba nescesidade hosi customer.

Planning

Aktivitas nee presiza atu hari nescesidade hanoin fali tempo servisu, no informasaun seluk nebe presiza atu hari software.

Analysisi risk

Aktivitas analisis nee halao atu analisis daik nian liu hosi teknikal ou liu hosi manajerial, parte ida nee dalaruma laiha ba modelu prosesu i mos uza metode interasi, maibe so deit ba modelu spiral.

Engeneering

Aktivitas nebe presiza atu hari ida ou representasaun hosi aplikasi liu hosi teknikal.

Construction & Release

Aktivitas nebe presiza atu delop software, testing, instali no user/ costumer support hanesan training uza software I mos dokumentasi hanesan livru manual uza software.

Customer evaluation

Aktivitas nebe presiza atu hetan feedback hosi user/ costumer hahu evaluasi sira durante representasaun ba software tuir engeneering I mos ba implementasaun duranta instalasi software ba parte construction and release.

Tuir mai dezenu hosi modelu spiral hotu: