Abstract

Explicit, formal representations of software processes are needed to help understand software development and maintenance processes, to analyze these processes prior to execution, to guide the execution of these processes, and finally to improve software processes in an evolutionary fashion. The creation of formal process representations includes activities such as requirements analysis, specification, design, coding, integration, and testing. We conducted a case study within TRW which involved the creation of formal process specifications and designs using MVP-L, an existing process notation. This paper describes the study, the lessons learned about process representation in general, and the lessons learned about the language MVP-L in detail.

Citations