Computer · Part C - Software, Algorithms and Computation · Major topic 13 of 39

Software Engineering, Architecture and Quality

Building and maintaining reliable software with evidence, teamwork, lifecycle discipline and controlled change.

180 items insideCOM-13

Also look at: Science & Technology: Computer Architecture, Operating Systems, Programming and Software SystemsChemistry: Industrial, Process & Chemical Engineering ChemistryChemistry: Analytical Chemistry & Quantitative Analysis

  1. 1

    Historical evolution — key dates

    • The NATO software engineering conference highlights the “software crisis”.1968
    • Structured methods, lifecycle models, modularity and testing disciplines expand.1970s
    • Object-oriented analysis/design, CASE tools and design patterns mature.1980s-1990s
    • The Agile Manifesto popularizes values for iterative development.2001
    • Continuous integration, DevOps, cloud services and microservices reshape delivery.2000s-2010s
    • Platform engineering, secure-by-design practices, software supply-chain assurance and AI-assisted development expand.2020s
  2. 2

    Requirements engineering

    • Stakeholder analysis; elicitation; interview; observation; user story; use case; scenario; requirements specification
      8 more points
      • Stakeholder analysis
      • Elicitation
      • Interview
      • Observation
      • User story
      • Use case
      • Scenario
      • Requirements specification
    • Functional/non-functional requirements; prioritization; acceptance criteria; traceability; change control
      5 more points
      • Functional/non-functional requirements
      • Prioritization
      • Acceptance criteria
      • Traceability
      • Change control
    • Feasibility, risk, assumptions, constraints, requirement conflict and validation.
  3. 3

    Design and architecture

    • Modules; interfaces; cohesion/coupling; separation of concerns; dependency inversion; information hiding
      6 more points
      • Modules
      • Interfaces
      • Cohesion/coupling
      • Separation of concerns
      • Dependency inversion
      • Information hiding
    • Layered; client-server; event-driven; pipe/filter; hexagonal/ports-and-adapters; microkernel; microservices; serverless
      8 more points
      • Layered
      • Client-server
      • Event-driven
      • Pipe/filter
      • Hexagonal/ports-and-adapters
      • Microkernel
      • Microservices
      • Serverless
    • Monolith vs distributed system; API-first; domain-driven design; bounded context; event sourcing; CQRS concepts
      6 more points
      • Monolith vs distributed system
      • API-first
      • Domain-driven design
      • Bounded context
      • Event sourcing
      • CQRS concepts
    • Architecture decision records; quality attributes; threat model; architectural fitness functions
      4 more points
      • Architecture decision records
      • Quality attributes
      • Threat model
      • Architectural fitness functions
  4. 4

    Implementation practice

    • Coding standards; naming; code review; pair/mob programming; refactoring; reuse; dependency management
      7 more points
      • Coding standards
      • Naming
      • Code review
      • Pair/mob programming
      • Refactoring
      • Reuse
      • Dependency management
    • Error handling; configuration; logging; telemetry; feature flags; secrets; documentation; technical debt
      8 more points
      • Error handling
      • Configuration
      • Logging
      • Telemetry
      • Feature flags
      • Secrets
      • Documentation
      • Technical debt
  5. 5

    Verification and validation

    • Unit, component, integration, contract, system, acceptance, smoke, regression and end-to- end testing.
    • Equivalence partitioning; boundary analysis; decision tables; state-transition tests; coverage; mutation testing
      6 more points
      • Equivalence partitioning
      • Boundary analysis
      • Decision tables
      • State-transition tests
      • Coverage
      • Mutation testing
    • Mock/stub/fake; test fixture; test pyramid; flaky test; reproducible test environment; test data management
      6 more points
      • Mock/stub/fake
      • Test fixture
      • Test pyramid
      • Flaky test
      • Reproducible test environment
      • Test data management
  6. 6

    Quality models

    • Correctness; reliability; availability; security; usability; accessibility; performance; maintainability; portability
      9 more points
      • Correctness
      • Reliability
      • Availability
      • Security
      • Usability
      • Accessibility
      • Performance
      • Maintainability
      • Portability
    • ISO/IEC quality models; defect density; escaped defects; mean time to detect/repair; customer outcomes
      5 more points
      • ISO/IEC quality models
      • Defect density
      • Escaped defects
      • Mean time to detect/repair
      • Customer outcomes
  7. 7

    Lifecycle and process

    • Waterfall; V-model; iterative/incremental; spiral; agile; Scrum; Kanban; XP; Lean; hybrid processes
      10 more points
      • Waterfall
      • V-model
      • Iterative/incremental
      • Spiral
      • Agile
      • Scrum
      • Kanban
      • XP
      • Lean
      • Hybrid processes
    • Backlog; sprint; iteration; release plan; definition of ready/done; retrospectives; continuous improvement
      7 more points
      • Backlog
      • Sprint
      • Iteration
      • Release plan
      • Definition of ready/done
      • Retrospectives
      • Continuous improvement
  8. 8

    Maintenance and evolution

    • Corrective/adaptive/perfective/preventive maintenance; legacy modernization; migration; deprecation
      4 more points
      • Corrective/adaptive/perfective/preventive maintenance
      • Legacy modernization
      • Migration
      • Deprecation
    • API compatibility; semantic versioning; schema migrations; backward/forward compatibility; end-of-life management
      5 more points
      • API compatibility
      • Semantic versioning
      • Schema migrations
      • Backward/forward compatibility
      • End-of-life management
  9. 9

    Software risk and assurance

    • Risk register; probability/impact; failure mode and effects analysis; fault tree; rollback; disaster recovery
      6 more points
      • Risk register
      • Probability/impact
      • Failure mode and effects analysis
      • Fault tree
      • Rollback
      • Disaster recovery
    • Secure SDLC; privacy-by-design; threat modelling; code provenance; SBOM; dependency scanning; signed artifacts
      7 more points
      • Secure SDLC
      • Privacy-by-design
      • Threat modelling
      • Code provenance
      • SBOM
      • Dependency scanning
      • Signed artifacts
  10. 10

    Metrics and governance

    • Lead time; cycle time; deployment frequency; change failure rate; defect trends; customer feedback; value stream
      7 more points
      • Lead time
      • Cycle time
      • Deployment frequency
      • Change failure rate
      • Defect trends
      • Customer feedback
      • Value stream
    • Metrics misuse; Goodhart’s law; engineering ethics; estimation uncertainty; sustainable pace
      5 more points
      • Metrics misuse
      • Goodhart’s law
      • Engineering ethics
      • Estimation uncertainty
      • Sustainable pace
  11. 11

    Advanced practice

    • Formal methods; safety-critical software; high-assurance development; design by contract; model-based engineering
      5 more points
      • Formal methods
      • Safety-critical software
      • High-assurance development
      • Design by contract
      • Model-based engineering
    • Architecture for scale; multi-tenant systems; regulated software; long-lived systems; software economics
      5 more points
      • Architecture for scale
      • Multi-tenant systems
      • Regulated software
      • Long-lived systems
      • Software economics