Standardisation
The practice of establishing and adhering to standards to ensure consistency, compatibility, and quality in software development.
Also Known As
- Consistency
- Normalization
- Re-Use
- Standardization
- Uniformity
Related
Addresses / Mitigates
- Feature Fit Risk: Ensures that the features conform to predefined standards, reducing variability and potentially widening accessibility.
- Operational Risk: Reduces operational errors by providing clear guidelines and protocols.
- Communication Risk: Improves communication by using a common language and standardized terms.
- Lock-In Risk: Using software that adheres to standards allows for swapping out components and promotes competition amongst dependencies.
Attendant Risks
- Inflexibility Risk: May limit creativity and flexibility by enforcing strict adherence to standards.
- Schedule Risk: Adhering to standards can introduce scope creep during the implementation phase.
- Compliance Risk: Ensuring continuous compliance with evolving standards can be challenging.
Description
"Standardization (or standardisation) is the process of developing and implementing technical standards. It can help to maximize compatibility, interoperability, safety, repeatability, or quality." - Standardization, Wikipedia
Standardisation involves creating, implementing, and enforcing standards and guidelines to ensure consistency, compatibility, and quality across software projects. This practice helps in maintaining uniformity, reducing complexity, and improving communication among team members and stakeholders.
See: