{'fraction_non_alphanumeric': 0.01867219917012448, 'fraction_numerical': 0.0027662517289073307, 'mean_word_length': 5.264069264069264, 'pattern_counts': {'":': 0, '<': 0, '<?xml version=': 0, '>': 0, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 1, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
Compliance of CMMI Process Area  with Specification Based Development

The development of reliable systems is still a major challenge for software industry. Construction of such a system requires both process and product based quality assurance. Many process improvement models have been suggested in industry and found appropriate for achieving high quality products. Examples of such process improvement models are CMM/CMMI, Agile, SPICE, the ISO 9000 family etc. However, implementation of these process improvement models often adds significant extra efforts. To minimize process implementation costs we propose a formal specification based product development model which integrates product and process quality. Formal specification methods have been in practice since decades, and have been successful in the development of safety-critical systems. Some formal methods are VDM, Z, LOTOS, CSP and CASL. In particular, we investigate the compliance of CMMI process area with the formal specification language CSP-CASL. CMMI is based on the notion of process area, which is a cluster of best practices with particular goals in a certain area. For each of the relevant process areas, we show how formal specifications can contribute to achieve the specific goals of that process area. This integration is a new result for achieving process compliance parallel with product development. We demonstrate our approach with an industrial case study.