Course Outline

QA/CI

  • What is Quality Assurance (QA)?
  • What is Continuous Integration (CI)?
  • The costs associated with software development, refactoring, and fixing errors
  • Identifying and understanding project requirements
  • Benefits to the organization

Domain-Driven Design (DDD)

  • Software development based on business requirements and assumptions in DDD
  • Challenges in communication between IT and Business
  • Domain Model

Best Practices for Government

  • KISS (Keep It Simple, Stupid) principle and DRY (Don't Repeat Yourself)
  • Coding standards
  • Creating reusable code through Object-Oriented Programming (OOP) and design patterns
  • Identifying and reducing cyclomatic complexity

Software Metrics for Government

  • Weight Method per Class
  • Response For a Class
  • Depth of Inheritance Tree
  • Coupling Between Objects
  • Lack of Cohesion of Methods
  • Number of Children
  • Cyclomatic complexity
  • Metrics class
  • Model Metrics
  • Metrics for use

Software Testing for Government

  • What, when, and how to test?
  • The methods of "white-box" and "black box" testing
  • The role of testing in agile methodologies for government
  • TDD (Test-Driven Development) and its potential impact on project costs
  • Unit testing
  • Behavioral tests
  • Functional tests

Refactoring for Government

  • What is refactoring?
  • Debt technology
  • Code smell
  • Refactoring patterns

Documentation for Government

  • The role of documentation in agile methodologies for government
  • What to document?
  • Types of documentation
  • Documentation and agile methodologies, or the principle of "Working software over comprehensive documentation"
  • Standard XMI
  • Automatic generation of documentation

Tools and Environment for CI in Government

  • Tools and environment for Continuous Integration (CI)

Agile and CI/QA for Government

  • Planning and incremental development
  • Embracing change
  • Short stages
  • Interdisciplinary team
  • Extreme Programming, code review
  • Individuals and interactions over processes and tools

Summation for Government

  • Discussion
  • Questions
  • How to begin the process of implementation?

Introduction to Testing for Government

  • Functional tests
  • Regression tests
  • User Acceptance Tests (UAT)
  • Unit tests
  • Usability tests
  • Non-functional tests
  • Performance tests
  • Load tests
  • Stress tests
  • Soak tests

Test or Not to Test for Government

  • Who makes decisions about what to test?
  • The cost of testing irrelevant items
  • Calculating ROI (Return on Investment) and analyzing potential failures
  • The role of the Test Manager

The Process of Testing for Government

  • Testing as a process and strategy
  • Identifying testing needs
  • Gathering requirements (use cases, user stories)
  • Scoping (choosing and prioritizing scenarios)
  • Designing tests
  • Preparing data
  • Preparing the environment
  • Creating or recording tests
  • Performing the test
  • Analysis and reports
  • Conclusions and improvement
  • When to conclude testing

Product Owner and Tests for Government

  • The role of the customer representative in test priority
  • Prioritizing tests
  • Writing effective user stories for UAT
  • Acceptance criteria
  • Group exercise to produce customer requirements, write user stories based on these requirements, and create tests
 28 Hours

Number of participants


Price per participant

Testimonials (1)

Upcoming Courses

Related Categories