Codes, life cycle assessment

S. SLTAC Guidelines for Life-Cycle Assessment A Code of Practice, Proceedings from the SETAC workshop held in Sesirabra, Portugal, March 31-April 3, 1993. 

Advisory Group are considering different facets of LCA. In 1993, they developed the Code of Practice ,the first worldwide accepted technical framework for LCA. This was an important step towards the harmonisation of the method and has initiated and supported the standardisation process by ISO. Between 1997 and 2000, ISO produced the international series of standard defining the different stages of the LCA methodology (ISO 14040 1997, ISO 14041 1998, ISO 14042 2000 ° as well as ISO 14043 2000° ). As mentioned above, these standards were replaced by two improved editions of life cycle assessment standards in 2006 (ISO 14040 2006 and ISO 14044 2006°). 

Consoli, F., D. Allen, I. Boustead, et al. 1993. Guidelines for life-cycle assessment A Code ofPractice , J. Seguin and B. Vigon (eds). Report of SETAC Workshop—Sesimbra, Portugal, March 31 to April 3. Society of Environmental Toxicology and Chemistry (SETAC), Sesimbra, Portugal. 

SETAC, Society for Environmental Toxicology and Chemistry, Guidelines for Life-Cycle Assessment Code of Practice , Brussels, Belgium, 1993. 

Guidelines for Life-Cycle Assessment A Code of Practice" in proceedings of SETAC Workshop, Sesimbra, Portugal, Society of Environmental Toxicology and Chemistry... 

All documents of the life cycle (including software programs) should be reviewed before their issue. The checking criteria are to be established in the SOPs describing document content. A competent person must check the document structure and content. The Source Code Review of software programs should be carried out only for those parts of the source code that were categorized as particularly critical in the risk assessment. 

In addition to the need for calibration to deal with local circumstances, a problem with the COCOMO-type approach is that the number of lines of code that an application will require will be difficult to assess at the beginning of the software development life cycle and will only be known with certainty when the software has actually been coded. Lines of code are also difficult for the user community to grasp and thus validate. 

The last question is to determine if we could use such data for reliability prediction. Early in the process, for example, at the requirements definition and analysis phase, our knowledge of the attributes and characteristics of the software development process is limited coding personnel and coding languages are undetermined, the design approach may not be defined, etc. Hence, our reliabihty assessment will be uncertain. The more we move into the life cycle process, the more information becomes available, and hence our uncertainty bound reduces. Let us call M the model of the process, that is, the set of characteristics that define the process. The characteristics of such model may include... 

---