Sekilas Mengenai Komponen Arsitektur SQA

Komponen Software terdiri dari : data, code, procedure, documentation

Tantangan (challenge) SW :
==> uniqueness of SW development proces : complexity(large number of operational mode), visibility of product (invisible), nature of develpment and production process (kesalahan hanya dapat diketahui di fase developmnt saja)

==>lingkungan pembangunan metode SQA
pupils, hobbies, engineer-economics-mngmnt, profesional SW development
contrak kondisinya, butuh teamwork
buth relasi customer suplier
cooperation and coordination dg SW team lain
interface dg SW sistem lain
butuhnya lanjutkan project meski anggota berubah
butuhnya maintain SW pd periode tertentu

==>mengapa perlu quality : karena quality itu perlu untuk menhgindari SW error

==>SW Quality : derajat dimana sistem, komponen, atw prosess sesuai dg requiremenmt yg dispesifikasikan dan kebutuhan customer and user

==> quality faktor Mc Call :
correctness,->kebutuhan benar
reliability,-> batas min kegagalan
efficiency-> resource need
integrity-> security, autorization
usability-> kemampuan user atw staff untuk operasikan SW
maintenability->
flexibility-> user nya flexibel
testability
portability--> dpt adaptasi atw dijalankan di 2 kondisi
reusability->
interoperability-> interface dg other SW system,

==>SQA Komponen
      =>preproject SQA components : contract review, developmnet and quality plan
      =>komponen PLC:
  fase development :
review (formal design review==> melibatkan pihak external team, dan peer review==> beruntun,       internal team)
expert opinion==> untuk penilaian kualitas
software testing ==>
whitebox (ke dalam, code) blackbox(tampilan)
SW maintanence
external participant(sub contrak)
fase operatipnal and maintenence:
Sw maintenence

==>MACAM TESTING
unit testing==> per unit software atau hardware tertentu
modul testing ==> per modul
integration testing==> integrasi anatar modul software dan hardware, apakah seirama
system and functional testing==> secara keseluruhan apakah sesuai dg requirment awal
acceptance==>apakah sesuai dg custemer requirement, cocok apa gak
beta testing==> ad hoc,meibatkan user customer
Regression ==> cek jika ada perubahan, apakah tetep sesuai track awal
tools testing ==> RTM,

==>element development plan===> 9 knowledge area : cost, time, risk, procurement, quality, humen resourece, communication, scope, integration
===> PLC : inisiasi, planning, execution(req, desain, testing), closing=>produk, reengineering
===> SDLC : waterfall===> req definition, analisis, design, coding, system test, installation and
convertion, operation and maintenance
       
=>quality infrastructure componen
procedure, W.I
supporting device : template, checklist
training instruction : staff training, retraining, certificating
preventif action , corrective,
configuration management==> tools nya auudit, dependency tracking, reporting and support change rule, versioning, req tracing, repository, support linier evolution and tree

=>quality management
        => standart' components
        =>organizational base-human components