Easy to:
- build (compile, package)
- install, deploy
- configure
- operate, monitor, supervise, control
- decommission
Deployability is a…
Measure of cost, time or process effectiveness for a deployment, for a series of deployments over time.
Typical Acceptance Criteria
Scenario Response Measures for “Deployability” from [Bass et al.]
Bass et al. define deployability as a property, and somehow omit other operational characteristics.
Cost in terms of
- Number, size and complexity of affected artifacts
- Average/worst-case effort
- Elapsed clock or calendar time
- Money (direct outlay or opportunity cost)
- New defects introduced
Extend to which this deployment affects other functions or quality attributes.
- Number of failed deployments
- Repeatability of the process
- Traceability of the process
- Cycle time of the process
What Stakeholders mean by operable
Stakeholder | (potential) Expectation for operable |
---|---|
User | - |
Product-Owner | - |
Management | * appropriate operational costs * appropriate licensing cost for required 3rd party software, like database, middleware |
Developer | * automated test and build * appropriate automation of deployments * appropriate similarity of development and production environments |
Tester | - |
Admin | * easy to build and deploy * appropriate monitoring facilities * appropriate procedures for crisis management in place * appropriate management of credentials required |
Domain-Expert | - |
Others | - |
Qualities tagged with #operable
- Appropriateness recognizability
- Auditability
- Autonomy
- Backward compatibility
- Change failure rate
- Compatibility
- Controllability
- Cycle time
- DORA Metrics
- Deployability
- Deployment frequency
- Devops-Metrics
- Ease of Use
- Expected physical environment
- Installability
- Interaction capability
- Interoperability
- Latency
- Lead time for changes
- Learnability
- Legal Requirements
- Mean time between failures
- Mean time to recovery
- Observability
- Operability
- Operational and Environment Requirements
- Portability
- Releasability
- Replaceability
- Traceability
- Understandability
- Upgradeability
- Usability
- User error protection
Requirements tagged with #operable
- Available 7x24 with 99% uptime
- Availability
- High availability
- Interaction capability
- Operability
- Reliability
- User error protection
- Core functions can be used on multiple OSs
- Compatibility
- Flexibility
- Interaction capability
- Portability
- Fast deployment
- Cycle time
- Deployment frequency
- Extensibility
- Lead time for changes
- Operability
- Time behaviour
- Fast rollout of changes
- Efficiency
- Operability
- Speed
- Time to Market
- Independent replacement of subsystem
- Adaptability
- Agility
- Changeability
- Efficiency
- Maintainability
- Interoperable with Java 12
- Backward compatibility
- Compatibility
- Interoperability
- Low effort deployment
- Compatibility
- Interoperability
- Portability
- Portable Business Data Checker
- Adaptability
- Flexibility
- Portability
- Quick unit tests
- Testability
- Restored to fully functional state 12h after complete failure
- Availability
- High availability
- Interaction capability
- Mean time to recovery
- Operability
- Reliability
- Rollout of a new feature
- Agility
- Changeability
- Maintainability
- Severe errors are detected and the system shuts down into safe state
- Dependability
- Operability
- Reliability
- Safety
- System can run >12h without re-booting the operating system
- Availability
- High availability
- Mean time between failures
- Reliability
- Stability
- System runs offline
- User Interface can be used in Current Browsers
- Compatibility
- Flexibility
- Interaction capability
- Interoperability
- Portability