The best definition I found regarding a SEP is stated by Jim Arlow in "UML2 and the Unified Process." He says, "a software engineering process defines the who, what, when and how of developing software. In its simplest form, a SEP is the process in which we turn user requirements into software." This basically captures the essence of why we use and implement software processes in our development life cycles; we want to give the customer the product that he ordered in the first place. However, we also want to do it in an organized, cost effective way that helps us complete the development of the product in the least time possible.