TRAINING PENGENALAN INFORMATION TECHNOLOGY QUALITY ASSURANCE

TRAINING TEKNOLOGI INFORMASI

Description

This   three-day  foundation  course  is  designed  for  learning  and
understanding  IT  quality concepts. It provides an excellent overview
of the entire IT quality professional area.

It further provides a macro introduction of the quality assurance area
by  introducing  and  reviewing  the  principles  expounded by leading
quality experts.
This  training   also  addresses the important aspects to consider for
those  organizations  that  desire  to properly organize their quality
initiative  for improved productivity and organizational integrity. It
includes certain case study analyses to reaffirm topic areas covered.

The  training  introduced  the important quality principles, concepts,
responsibilities   and   vocabulary,  will  conduct  a  brief  quality
management  self-assessment, will learn how to implement an IT quality
program  and  will  learn how to build a short term action program for
your IT organization.

This  training  also  addresses  the important aspects to consider for
those  organizations  that  desire  to properly organize their quality
initiative for improved productivity and organizational integrity.

Objectives

Participants  will  learn to implement detailed Information Technology
Quality Assurance programs, policies and procedures, including:
* Learning   the   fundamentals   of  software  quality  principles,
concepts, responsibilities, and vocabulary.
* Each   participant   will   conduct  a  brief  quality  management
self-assessment.
* Provide a step-by-step process to implement an IT quality program.
* Learn  where  your  organization  is and where it wants to be in a
quality function.
* Learn  how  to  make  it  happen and where to start on the quality
journey.
* Help   you   build  a  short  term  action  program  for  your  IT
organization by completing a quality action plan.

* Where  and  how  to  apply  Information  Technology QA concepts to
achieve maximum quality benefit
* Quality factors that must be considered on every IT  project
* Project and quality metrics
* Detailed analysis of the Software Engineering Institute’s concepts
for  IT Quality Assurance and how to apply

Target Audience
* Quality Assurance Managers/Supervisors/Analysts
* IT Managers
* Project Leaders
* IT Service Users
* QA Leaders

Course Contents and Descriptions

I.General Quality Management
1. Quality principles
1. Benefits of software quality
Describe  the  benefits that software quality engineering can
have at the organizational level.
2. Organizational and process benchmarking
Use  benchmarking at the organizational, process, and project
levels to identify and implement best practices.

1. Ethical and Legal Compliance
1. ASQ Code of Ethics
Determine   appropriate   behavior  in  situations  requiring
ethical   decisions,   including   identifying  conflicts  of
interest, recognizing and resolving ethical issues, etc.
2. Legal and regulatory issues
Define and describe the impact that issues such as copyright,
intellectual   property   rights,   product  liability,  data
privacy,  the  Sarbanes-Oxley Act, etc., can have on software
development.

1. Standards and models
Define and describe the following standards and assessment models:
ISO   9000   standards,  IEEE  software  standards,  and  the  SEI
Capability Maturity Model Integrated (CMMI).

1. Leadership skills
1. Organizational leadership
Use  leadership  tools and techniques, such as organizational
change  management, knowledge-transfer, motivation, mentoring
and coaching, recognition, etc.
2. Facilitation skills
Use  various  approaches  to manage and resolve conflict. Use
negotiation  techniques  and  identify possible outcomes. Use
meeting management tools to maximize performance.
3. Communication skills
Use  various  communication  elements (e.g., interviewing and
listening skills) in oral, written, and presentation formats.
Use   various   techniques   for  working  in  multi-cultural
environments,  and  identify  and  describe  the  impact that
culture and communications can have on quality.

1. Team Skills
1. Team management
Use various team management skills, including assigning roles
and  responsibilities, identifying the classic stages of team
development    (forming,   storming,   norming,   performing,
adjourning), monitoring and responding to group dynamics, and
working   with   diverse   groups  and  in  distributed  work
environments.
2. Team tools
Use   decision-making   and   creativity   tools,   such   as
brainstorming,  nominal  group technique (NGT), multi-voting,
etc.

1. Software Quality Management
1. Quality Management System
1. Quality goals and objectives
Design   quality  goals  and  objectives  for  programs,
projects, and products that are consistent with business
objectives.  Develop  and  use  documents  and processes
necessary   to   support   software  quality  management
systems.
2. Customers and other stakeholders
Describe  and  distinguish  between  various stakeholder
groups,  and  analyze  the effect their requirements can
have on software projects and products.
3. Planning
Design  program plans that will support software quality
goals and objectives.
4. Outsourcing
Determine  the  impact that acquisitions, multi-supplier
partnerships,  outsourced  services,  and other external
drivers can have on organizational goals and objectives,
and design appropriate criteria for evaluating suppliers
and subcontractors.
2. Methodologies
1. Cost of quality (COQ)
Analyze  COQ categories (prevention, appraisal, internal
failure,  external failure) and their impact on products
and processes.
2. Process improvement models
Define  and  describe elements of lean tools and the six
sigma  methodology, and use the plan-do-check-act (PDCA)
model for process improvement.
3. Corrective action procedures
Evaluate   corrective   action   procedures  related  to
software  defects,  process  nonconformances,  and other
quality system deficiencies.
4. Defect prevention
Design  and  use  defect  prevention  processes  such as
technical   reviews,   software  tools  and  technology,
special training, etc.
3. Audits
1. Audit types
Define  and  distinguish  between  various  audit types,
including process, compliance, supplier, system, etc.
2. Audit roles and responsibilities
Identify    roles   and   responsibilities   for   audit
participants:  client,  lead auditor, audit team members
and auditee.
3. Audit process
Define  and  describe  the steps in conducting an audit,
developing   and   delivering   an   audit  report,  and
determining appropriate follow-up activities.

1. Systems and Software Engineering Processes
1. Lifecycles and process models
Evaluate  various software development lifecycles (iterative,
waterfall,  etc.) and process models (V-model, Feature Driven
Development,  Test  Driven  Development,  etc.)  and identify
their benefits and when they should be used.
2. Systems architecture
Identify   and   describe  various  architectures,  including
embedded   systems,  client-server,  n-tier,  web,  wireless,
messaging,  collaboration  platforms, etc., and analyze their
impact on quality.
3. Requirements engineering
1. Requirements types
Define  and  describe  various  types  of  requirements,
including  feature, function, system, quality, security,
safety, regulatory, etc.
2. Requirements elicitation
Describe  and use various elicitation methods, including
customer   needs  analysis,  use  cases,  human  factors
studies,   usability   prototypes,   joint   application
development (JAD), storyboards, etc.
3. Requirements analysis
Identify  and  use  tools  such  as  data  flow diagrams
(DFDs),  entity  relationship  diagrams (ERDs), etc., to
analyze requirements.
4. Requirements management
1. Participants
Identify   various  participants  who  have  a  role  in
requirements  planning, including customers, developers,
testers,   the   quality   function,   management,  etc.
(Understand)
2. Requirements evaluation
Assess  the  completeness,  consistency, correctness and
testability   of   requirements,   and  determine  their
priority.
3. Requirements change management
Assess the impact that changes to requirements will have
on  software  development  processes  for  all  types of
lifecycle models.
4. Bidirectional traceability
Use various tools and techniques to ensure bidirectional
traceability  from requirements elicitation and analysis
through design and testing.
5. Software analysis, design, and development
1. Design methods
Identify  the  steps  used  in software design and their
functions,  and  define and distinguish between software
design  methods  such  as  object-oriented  analysis and
design (OOAD), structured analysis and design (SAD), and
patterns.
2. Quality attributes and design
Analyze   the   impact   that  quality-related  elements
(safety,  security, reliability, usability, reusability,
maintainability, etc.) can have on software design.
3. Software reuse
Define   and   distinguish   between   software   reuse,
reengineering, and reverse engineering, and describe the
impact these practices can have on software quality.
4. Software development tools
Select  the  appropriate  development  tools  to use for
modeling,  code  analysis,  etc., and analyze the impact
they   can   have   on   requirements   management   and
documentation. (Analyze)
5. Software development methods
Define and describe principles such as pair programming,
extreme  programming,  cleanroom,  formal methods, etc.,
and their impact on software quality.

1. Maintenance management
1. Maintenance types
Describe   the   characteristics   of  corrective,  adaptive,
perfective, and preventive maintenance types.
2. Maintenance strategy
Describe  various factors affecting the strategy for software
maintenance,   including   service-level  agreements  (SLAs),
short-  and  long-term  costs,  maintenance releases, product
discontinuance, etc., and their impact on software quality.

1. Project Management
1. Planning, scheduling, and deployment
1. Project planning
Use  forecasts,  resources,  schedules,  task  and  cost
estimates, etc., to develop project plans.
2. Project scheduling
Use  PERT  charts,  critical  path  method  (CPM),  work
breakdown  structure (WBS), Scrum, burn-down charts, and
other tools to schedule and monitor projects.
3. Project deployment
Use  various  tools,  including  milestones,  objectives
achieved,  task  duration, etc., to set goals and deploy
the project.
2. Tracking and controlling
1. Phase transition control
Use  phase  transition control tools and techniques such
as  entry/exit  criteria,  quality  gates, Gantt charts,
integrated master schedules, etc.
2. Tracking methods
Calculate project-related costs, including earned value,
deliverables,  productivity, etc., and track the results
against project baselines.
3. Project reviews
Use  various types of project reviews such as phase-end,
management,  and  retrospectives or post-project reviews
to  assess  project  performance  and  status, to review
issues  and  risks,  and to discover and capture lessons
learned from the project.
4. Program reviews
Define  and  describe  various methods for reviewing and
assessing   programs  in  terms  of  their  performance,
technical accomplishments, resource utilization, etc.
3. Risk management
1. Risk management methods
Use   risk   management   techniques  (assess,  prevent,
mitigate, transfer) to evaluate project risks.
2. Software security risks
Evaluate  risks specific to software security, including
deliberate  attacks  (hacking, sabotage, etc.), inherent
defects  that  allow  unauthorized  access  to data, and
other   security  breaches,  and  determine  appropriate
responses to minimize their impact.
3. Safety and hazard analysis
Evaluate  safety  risks  and hazards related to software
development and implementation and determine appropriate
steps to minimize their impact.
2. Software Metrics and Analysis
1. Metrics and measurement theory
1. Terminology
Define   and  describe  metrics  and  measurement  terms
including  reliability,  internal and external validity,
explicit and derived measures, etc.
2. Basic measurement theory and statistics
Define  the  central limit theorem, and describe and use
mean,  median,  mode,  standard deviation, variance, and
range.  Apply  appropriate  measurement scales (nominal,
ordinal, ratio, interval) in various situations.
3. Psychology of metrics
Describe  how  metrics  and  measuring affect the people
whose  work  is being measured and how people affect the
ways in which metrics are used and data are gathered.
2. Process and product measurement
1. Software metrics
Use  metrics  to assess various software attributes such
as  size,  complexity,  number of defects, the amount of
test   coverage  needed,  requirements  volatility,  and
overall system performance.
2. Process metrics
Measure  the  effectiveness  and  efficiency of software
using  functional verification tests (FVT), cost, yield,
customer  impact,  defect detection, defect containment,
total  defect  containment  effectiveness (TDCE), defect
removal   efficiency   (DRE),   process  capability  and
efficiency, etc.
3. Metrics reporting tools
Use   various  metric  representation  tools,  including
dashboards,  stoplight  charts,  etc., to report results
efficiently.
3. Analytical techniques
1. Sampling
Define  and  distinguish between sampling methods (e.g.,
random,   stratified,  cluster)  as  used  in  auditing,
testing, product acceptance, etc.
2. Data collection and integrity
Describe  the importance of data integrity from planning
through  collection  and  analysis,  and  apply  various
techniques    to    ensure    its   quality,   accuracy,
completeness, and timeliness.
3. Quality analysis tools
Describe  and  use  classic  quality  tools (flowcharts,
Pareto   charts,  cause  and  effect  diagrams,  control
charts,  histograms,  etc.)  and  problem-solving  tools
(affinity and tree diagrams, matrix and activity network
diagrams,  root  cause  analysis,  etc.) in a variety of
situations.
3. Software Verification and Validation
1. Theory
1. V&V methods
Select  and  use V&V methods, including static analysis,
structural  analysis,  mathematical  proof,  simulation,
etc.,  and  analyze  which tasks should be iterated as a
result of modifications.
2. Software product evaluation
Use  various evaluation methods on documentation, source
code,  test  results,  etc.,  to  determine whether user
needs and project objectives have been satisfied.
2. Test planning and design
1. Test strategies
Select  and analyze test strategies (test-driven design,
good-enough,  risk-based, time-box, top-down, bottom-up,
black-box,  white-box, simulation, automation, etc.) for
various situations.
2. Test plans
Develop   and   evaluate   test  plans  and  procedures,
including   system,  acceptance,  validation,  etc.,  to
determine whether project objectives are being met.
3. Test designs
Select  and  evaluate  various  test  designs, including
fault insertion, fault-error handling, equivalence class
partitioning, boundary value, etc.
4. Software tests
Identify   and   use   various  tests,  including  unit,
functional,    performance,   integration,   regression,
usability,   acceptance,   certification,  environmental
load,   stress,   worst-case,  perfective,  exploratory,
system, etc.
5. Tests of supplier components and products
Determine  appropriate levels of testing for integrating
third-party components and products.
6. Test coverage specifications
Evaluate   the   adequacy   of  specifications  such  as
functions,  states,  data  and time domains, interfaces,
security,     and     configurations     that    include
internationalization and platform variances.
7. Code coverage techniques
Identify  and  use  techniques such as branch-to-branch,
condition,   domain,   McCabe’s  cyclomatic  complexity,
boundary, etc.
8. Test environments
Select  and  use  simulations,  test libraries, drivers,
stubs,  harnesses,  etc.,  and  identify  parameters  to
establish  a  controlled  test  environment  in  various
situations.
9. Test tools
Identify   and  use  utilities,  diagnostics,  and  test
management tools.
3. Reviews and inspections
Identify  and  use  desk-checks, peer reviews, walk-throughs,
Fagan and Gilb inspections, etc.
4. Test execution documentation
Review  and  evaluate  documents such as defect reporting and
tracking  records,  test completion metrics, trouble reports,
input/output specifications, etc.
5. Customer deliverables
Assess  the  completeness of customer deliverables, including
packaged  and  hosted  or downloadable products, license keys
and  user  documentation,  marketing  and training materials,
etc.
4. Software Configuration Management
1. Configuration infrastructure
1. Configuration management team
Describe   the   roles   and   responsibilities   of   a
configuration management group.
[NOTE:   The   roles   and   responsibilities   of   the
configuration  control  board  (CCB) are covered in area
VII.C.2.]
2. Configuration management tools
Describe  these  tools  as  they  are  used for managing
libraries, build systems, defect tracking systems, etc.
3. Library processes
Describe  dynamic, static, and controlled processes used
in  library  systems  and  related  procedures,  such as
check-in/check-out, merge changes, etc.
2. Configuration identification
1. Configuration items
Describe  configuration  items  (documentation, software
code,  equipment,  etc.), identification methods (naming
conventions,   versioning   schemes,   etc.),  and  when
baselines are created and used.
2. Software builds
Describe  the  relationship  between software builds and
configuration management functions, and describe methods
for controlling builds (automation, new versions, etc.).
3. Configuration control and status accounting
1. Item, baseline, and version control
Describe  processes  for documentation control, tracking
item  changes,  version  control, etc., that are used to
manage  various  configurations,  and describe processes
used   to  manage  configuration  item  dependencies  in
software builds and versioning.
2. Configuration control board (CCB)
Describe  the  roles and responsibilities of the CCB and
its members and the procedures they use.
[NOTE:   The   roles   and   responsibilities   of   the
configuration   management  team  are  covered  in  area
VII.A.1.]
3. Concurrent development
Describe  the  use  of  configuration management control
principles in concurrent development processes.
4. Status accounting
Discuss various processes for establishing, maintaining,
and reporting the status of configuration items.
4. Configuration audits
Define   and  distinguish  between  functional  and  physical
configuration  audits  and  how  they are used in relation to
product specifications.
5. Product release and distribution
1. Product release
Review  product release processes (planning, scheduling,
defining  hardware  and software dependencies, etc.) and
assess their effectiveness.
2. Archival processes
Review the source and release archival processes (backup
planning  and  scheduling,  data  retrieval, archival of
build  environments,  retention  of  historical records,
offsite storage, etc.) and assess their effectiveness.

Case Studies  Exercises

During  the  course,  several  case  studies/exercises are introduced.
Attendees have an opportunity to apply their expertise, in the context
of the course material, to typical software quality assurance issues.

Trainer :
Dr. Ir. Fauzi Hasan, MM, MBA
Dr.  Fauzi Hasan Pada saat ini adalah President American Academy untuk
Chapter   Indonesia   yang  melingkupi  American  Academy  of  Project
Management  dan American Academy of Finance Management yang berpusasat
di Colorado Spring, Colorado USA.

Pengalaman  Dr.  Fauzi  Hasan  diperkaya  dengan  keterlibatannya pada
beberapa proyek terkait Business Process Modeling dan Improvement yang
selaras dengan standard dan metodologi CMMI (Capability Maturity Model
and  Integration),  dimana  dalam  akhir  dekade  ini  banyak membantu
organisasi  Pemerintah  dan  Bank dalam membangun dan mengimplementasi
Crisis  Management Strategy seperti pembuatan BCP (Business Continuity
Plan) dan DRP (Disaster Recovery Plan).

Dr.   Fauzi   Hasan   telah   memberikan   kontribusi  langsung  untuk
penyelesaian  dan keberhasilan penerapan Frameworks dan Best Practices
seperti: ITIL, COBIT, PMBOK, Prince2, TOGAF, ISO 20000, ISO 27000, ISO
38500, COSO dan yang lain  diberbagai bidang industri. Sebagai seorang
profesioal  yang  kompeten  di  bidang  teknologi informasi, manajemen
proyek  dan  proses  bisnis ini dibuktikan dengan dimilikinya sejumlah
sertifikat  Internasional  terkait tata kelola teknologi informasi dan
industri (IT and Industrial Goverannce).

Dr.  Fauzi  Hasan  dalam  karirnya  sebagai executive telah bekerja di
beberapa   perusahaan  lokal  maupun  internasional  seperti:  Philips
Netherlands,  Sony  ,  Warner Lambert, Singapore Technology Logistics,
Hewlett-Packard,  EMTEK Group, Intergraph,  Jatis eCom-Sumitomo Group,
dan ERESHA Group.

JADWAL TRAINING TAHUN 2026

03 – 04 Januari 2026 | 16 – 17 Januari 2026

06 – 07 Februari 2026 | 20 – 21 Februari 2026

05 – 06 Maret 2026 | 19 – 20 Maret 2026

03 – 04 April 2026 | 23 – 24 April 2026

07 – 08 Mei 2026 | 21 – 22 Mei 2026

05 – 06 Juni 2026 | 25 – 26 Juni 2026

09 – 10 Juli 2026 | 23 – 24 Juli 2026

06 – 07 Agustus 2026 | 20 – 21 Agustus 2026

04 – 05 September 2026 | 18 – 19 September 2026

08 – 09 Oktober 2026 | 22 – 23 Oktober 2026

06 – 07 November 2026 | 26 – 27 November 2026

04 – 05 Desember 2026 | 18 – 19 Desember 2026

Metode Training

1. Tatap Muka/offline
2. Online via zoom

Kota Penyelenggaraan jika offline :

1. Bandung
2. Jogjakarta
3. Surabaya
4. Jakarta

fasilitas yang didapatkan

1. Training Kit Eksklusif
   • Tas
   • Name Tag
   • Modul
   • Flash disk
   • Ballpoint
   • Block Note
   • Souvenir
2. Harga yang Reliable
3. Trainer Kompeten di bidangnya
4. Pelayanan Maksimal untuk peserta
5. Penjemputan dari dan ke bandara

Investasi :

Public training : Rp. 4.500.000 (minimum 3 pax)

In House Training : on Call