IEEE 24774-2012 pdf download IEEE Guide— Adoption of ISO/IEC TR 24774:201 0 Systems and Software Engineering— Life Cycle Management—Guidelines for Process Description
Not all elements need to be treated in all standards. Some standards will treat only process Title, Purposeand Outcomes, for example, leaving the activities for further elaboration by other standards.
The goals and objectives of performing a process can be described by using the elements of Title, Purpose.and Outcomes. These elements are used to describe intended results without the necessity of performingstructural decomposition of the process. Processes defined using Title, Purpose, and Outcomes provide acommon starting point for process implementation and process assessment.
NOTEThe distinction between a process and a procedure is a simple one. A procedure is a set of steps to befollowed that, when completed, might or might not achieve the intended objective. This is similar to following a recipe whencooking. On the other hand, process is executed with knowledge of the intended purpose and outcomes to achieve thedesired result.
3.2 The title element
The title of a process description is a short noun phrase that presents a descriptive heading for the processThe title identifies the principle concern of the process and distinguishes the process from other processes inthe model Because of the latter criterion, it may sometimes be necessary to change the title of a process. Forexample, one might have a “software design process” which is later renamed as a “software detailed designprocess” to distinquish it from a newly-invented “software architectural design process”
NOTE 1Process descriptions maybe used both to describe generic objects of a particular type (for example “projectmanagement process”), and to describe a particular instance of a generic type (for example “project management processfor project A”). For a process model or a standard the type description is suficient, but in other cases (for example projectplanning) generic process types are instantiated with respect to resources and time, When both generic types andparticular instances are described, in order to diferentiate between the two a typographical convention may be adopted(for example the title of the specific instance may be set in italic font).
NOTE 2The intent is to give a itle not a summary. Noun-verb or verb-noun phrases lead to an attempt to summarisethe purpose or process so that the title can stand for the purpose. This is often misleading. A descriptive noun phrase – thename of the process -is less open to misinterpretation and the temptation to let it stand in for the purpose.
3.3 The purpose element
The purpose of the process is stated as a high level, overall goal for performing the process. In cases whereprocesses might be thought to overlap, the purpose should be used to characterize the scope or bounds ofthe process.
Whenever possible, the purpose should be succinctly captured in a single sentence. Summarizing theactivities or outcomes of the process in the purpose statement should be avoided. Use of the conjunctionand” to connect multiple clauses should be avoided as it would indicate that the description is being written
IEEE 24774-2012 pdf download
PS:Thank you for your support!
