D. Standards – 2 Roles of Software Engineering Standards
{"Image DocumentName": "D. Standards \u2013 2 Roles of Software Engineering Standards", "Image ImageDescription": "Naming: A standard can provide a succinct name for a complicated concept. Best Practices: Sometimes organizations want to adopt software development practices that are agreed by the community to represent best of breed . Badging :Organizations need a way to assert that their institutional practices conform to a constellation of best principles and practices.[Moore95] Contractual Agreement: In a complex information technology procurement, it is helpful and efficient to decouple complex technological issues from the business aspects of the agreement. Notes: Particularly when two parties are contracting for a complex item, it is helpful to have a standard specifying the details. For example, is it easier to judge the adequacy of a 20-page explanation of a supplier\u2019s verification and validation procedures or a simple claim that they conform to IEEE Std 1012? Practice standards describe practices that are consensually agreed to be sound. The need is met by badges formulated by expert authorities and sometimes independently certified, for example, ISO 9000 and SEI Capability Maturity Model levels. This usage is so important that we can expect to see new badges in the near future. Standards such as IEEE/EIA provide this service by setting norms which may be referenced rather than described in a contract. Module I. Business Practices and Engineering Economics. Module I. Business Practices and Engineering Economics.", "Image XResolution": "37", "Image YResolution": "37", "Image ResolutionUnit": "Pixels/Centimeter", "Image Software": "SlidePlayer", "Image YCbCrPositioning": "Centered"}