Get in Touch

Course Outline

Software Engineering (5 Days)

Day 1: Project Management

  • Distinctions between project management, line management, maintenance, and support
  • Project definition and types of projects
  • General management principles and specific project management techniques
  • Various management styles
  • Unique characteristics of IT projects
  • Foundational project processes
  • Iterative, incremental, waterfall, agile, and lean project methodologies
  • Project phases
  • Project roles and responsibilities
  • Project documentation and deliverables
  • Soft skills and human factors
  • Project management standards: PRINCE2, PMBOK, PMI, IPMA, and others

Day 2: Business Analysis and Requirements Engineering Fundamentals

  • Defining business objectives
  • Business analysis, business process management, and business process improvement
  • Separating business analysis from system analysis
  • System stakeholders, users, context, and boundaries
  • The necessity of requirements
  • Understanding requirements engineering
  • The boundary between requirements engineering and architectural design
  • Where requirements engineering is often overlooked
  • Requirements engineering in iterative, lean, and agile development, including continuous integration: FDD, DDD, BDD, TDD
  • Foundational requirements engineering process, roles, and deliverables
  • Standards and certifications: BABOK, ISO/IEEE 29148, IREB, BCS, IIBA

Day 3: Architecture and Development Fundamentals

  • Programming languages: structural and object-oriented paradigms
  • Object-oriented development: historical context and future prospects
  • Architectural attributes: modularity, portability, maintainability, and scalability
  • Definition and types of software architectures
  • Enterprise architecture versus system architecture
  • Programming styles
  • Programming environments
  • Common programming errors and prevention strategies
  • Modelling architecture and components
  • SOA, Web Services, and micro-services
  • Automated builds and continuous integration
  • The extent of architecture design in projects
  • Extreme programming, TDD, and refactoring

Day 4: Quality Assurance and Testing Fundamentals

  • Product quality: definitions, ISO 25010, FURPS, etc.
  • Product quality, user experience, Kano Model, customer experience management, and holistic quality
  • User-centred design, personas, and strategies for personalized quality
  • Adequate quality
  • Quality Assurance versus Quality Control
  • Risk strategies in quality control
  • Quality assurance components: requirements, process control, configuration and change management, verification, validation, testing, static testing, and static analysis
  • Risk-based quality assurance
  • Risk-based testing
  • Risk-driven development
  • Boehm’s curve in quality assurance and testing
  • The four testing schools: selecting the approach that fits your needs

Day 5: Process Types, Maturity, and Process Improvement

  • The evolution of IT processes: from Alan Turing and IBM to the lean startup
  • Processes and process-oriented organizations
  • Historical perspective on processes in crafts and industries
  • Process modelling: UML, BPMN, and more
  • Process management, optimization, re-engineering, and process management systems
  • Innovative process approaches: Deming, Juran, TPS, Kaizen
  • Is quality free? (Philip Crosby)
  • The need for and history of maturity improvement: CMMI, SPICE, and other scales
  • Special maturity types: TMM, TPI (for testing), Requirements Engineering Maturity (Gorschek)
  • Process maturity versus product maturity: correlations and causal relationships
  • Process maturity versus business success: correlations and causal relationships
  • Lessons from Automated Defect Prevention and the next leap in productivity
  • Initiatives: TQM, Six Sigma, agile retrospectives, process frameworks

Requirements Engineering (2 Days)

Day 1: Requirements Elicitation, Negotiation, Consolidation, and Management

  • Identifying requirements: what, when, and who
  • Stakeholder classification
  • Overlooked stakeholders
  • Defining system context and identifying requirement sources
  • Elicitation methods and techniques
  • Prototyping, personas, and elicitation through testing (exploratory and other methods)
  • Marketing and requirements elicitation: MDRA (Market-Driven Requirements Engineering)
  • Prioritizing requirements: MoSCoW, Karl Wiegers, and other techniques (including agile MMF)
  • Refining requirements: agile "specification by example"
  • Requirements negotiation: types of conflicts and resolution methods
  • Resolving internal conflicts between requirement types (e.g., security vs. usability)
  • Requirements traceability: purpose and methodology
  • Changes in requirement status
  • Requirements CCM, versioning, and baselines
  • Product view versus project view on requirements
  • Product management and requirements management within projects

Day 2: Requirements Analysis, Modelling, Specification, Verification, and Validation

  • Analysis as the iterative thinking process between elicitation and specification
  • The iterative nature of the requirements process, even in sequential projects
  • Natural language requirements: risks and benefits
  • Requirements modelling: advantages and costs
  • Rules for using natural language in requirements specification
  • Defining and managing a requirements glossary
  • UML, BPMN, and other formal/semi-formal modelling notations for requirements
  • Using document and sentence templates for requirements description
  • Requirements verification: goals, levels, and methods
  • Validation through prototyping, reviews, inspections, and testing
  • Requirements validation versus system validation

Testing (2 Days)

Day 1: Test Design, Execution, and Exploratory Testing

  • Test design: optimizing time and resources after risk-based testing
  • Test design "from infinity to here": understanding that exhaustive testing is impossible
  • Test cases and test scenarios
  • Test design across various test levels (from unit to system)
  • Test design for static and dynamic testing
  • Business-oriented and technique-oriented test design ("black-box" and "white-box")
  • Negative testing (breaking the system) and acceptance testing (supporting developers)
  • Achieving test coverage: various coverage measures
  • Experience-based test design
  • Deriving test cases from requirements and system models
  • Test design heuristics and exploratory testing
  • Timing of test case design: traditional versus exploratory approaches
  • Describing test cases: determining appropriate detail levels
  • Psiychological aspects of test execution
  • Logging and reporting during test execution
  • Designing tests for "non-functional" testing
  • Automated test design and Model-Based Testing (MBT)

Day 2: Test Organization, Management, and Automation

  • Test levels (or phases)
  • Who conducts testing and when? Various models
  • Test environments: cost, administration, access, and responsibility
  • Simulators, emulators, and virtual test environments
  • Testing within agile scrum
  • Test team organization and roles
  • The test process
  • Test automation: identifying automatable elements
  • Test execution automation: approaches and tools
 63 Hours

Custom Corporate Training

Training solutions designed exclusively for businesses.

  • Customized Content: We adapt the syllabus and practical exercises to the real goals and needs of your project.
  • Flexible Schedule: Dates and times adapted to your team's agenda.
  • Format: Online (live), In-company (at your offices), or Hybrid.
Investment

Price per private group, online live training, starting from 6500 € + VAT*

Contact us for an exact quote and to hear our latest promotions

Testimonials (3)

Provisional Upcoming Courses (Contact Us For More Information)

Related Categories