c
1
|
Explicitness and Unambiguity |
Is the development process defined explicitly and unambiguously? |
Yes or No |
“Yes” is preferable to “No” (Max) |
c
2
|
Rationale |
Has the process been rationalized through providing extensive and precise explanations? |
Yes or No |
“Yes” is preferable to “No” (Max) |
c
3
|
Completeness |
A complete process definition includes definitions for: development cycle, lifecycle, roles, activities, modeling language, artifacts, practices/ techniques, rules, and umbrella activities. |
Ratio of the number of existing definitions to the total. |
A higher value is preferable to a smaller value (Max) |
c
4
|
Generic development lifecycle coverage |
Which phases of the generic development cycle are covered by the development process? Generic phases include: inception, analysis, design, implementation, test, deployment, maintenance, support, and postmortem. |
Ratio of the number of covered phases to the total number of generic phases. |
A higher value is preferable to a smaller value (Max) |
c
5
|
Smooth transition |
Is the transition between the phases smooth? |
Yes or No |
“Yes” is preferable to “No” (Max) |
c
6
|
Seamless transition |
Is the transition between the phases seamlessness? |
Yes or No |
“Yes” is preferable to “No” (Max) |
c
7
|
Adequate products |
Does the development process produce the products typically associated with the generic development activities (feasibility analysis, requirement specification, design, modeling, documentation, test, training and deployment)? |
Ratio of product types supported to the ideal number of product types. |
A higher value is preferable to a smaller value (Max) |
c
8
|
Modeling coverage |
Do the products include models (analysis and design)? |
Yes or No |
“Yes” is preferable to “No” (Max) |
c
9
|
Consistency |
This criterion evaluates the level at products complement each other. |
High, Medium (overlapping exist that can result in inconsistencies) or Low |
“High” is preferable to “Low” (Max) |
c
10
|
Tangibility/Visibility |
This criterion evaluates the level at the products are tangible, understandable, and testable to end-users. |
High, Medium or Low |
“High” is preferable to “Low” (Max) |
c
11
|
Standards |
Are there any specific standards for the products? |
Yes or No |
“Yes” is preferable to “No” (Max) |
c
12
|
Process based on functional/non-functional requirements |
Is the development process based on requirements? |
Yes or No |
“Yes” is preferable to “No” (Max) |
c
13
|
Non-functional requirements verification |
Are the non-functional requirements addressed? |
Yes or No |
“Yes” is preferable to “No” (Max) |
c
14
|
Traceability |
Can the products be traced to the requirements? |
Yes or No |
“Yes” is preferable to “No” (Max) |
c
15
|
Requirements change |
Does the development process let changes in requirements? |
Yes or No |
“Yes” is preferable to “No” (Max) |
c
16
|
Available and published documents |
Is the development process published and available to users? |
Published and available (2), Published but not available (1); No published and not available (0) |
A higher value is preferable to a smaller value (Max) |
c
17
|
Process enactment documentation |
Is the running process documented? |
Yes or No |
“Yes” is preferable to “No” (Max) |
c
18
|
Size/Complexity |
Size/complexity is defined as a function of building blocks of the development process. |
Total number of practices, roles, products, and phases/ stages. |
A lower value is preferable to a higher value (Min) |
c
19
|
Practicality |
This criterion evaluates the level at the process is practical, based on issues affecting practicality, such as support for umbrella activities, independence from specific tools, pragmatic techniques, concrete rules, and non-overlapping activities. |
High, Medium or Low |
“High” is preferable to “Low” (Max) |
c
20
|
Practicability |
This criterion evaluates the level at process development is practicable, through providing effective activities or techniques such as suitability filters and instantiation/ adaptation methods. |
High, Medium or Low |
“High” is preferable to “Low” (Max) |