| Group: Core Application Design |
Weight 60.0 |
| Section: Functional Requirements |
*Weight:*50.0 |
| Question |
Type |
Weight |
Document Uploa |
Question 1.1.1
Each functional requirement from the Application Requirements Specification is addressed.
0 - One or more major functional requirements are missing or incorrectly addressed.
1 - One or more minor functional requirements are missing or incorrectly addressed.
2 - All requirements are addressed but require more detail to move into the next phase.
3 - All requirements are met and are ready to move on for further development. |
Scale (0-3) |
30.0 |
Require |
Question 1.1.2
Each functional requirement is represented in at least one Sequence Diagram.
0 - One or more major functional requirements are not detailed by sequence diagrams.
1 - One or more minor functional requirements are not detailed by sequence diagrams.
2 - All requirements are addressed but require more detail to move into the next phase.
3 - All requirements are met and are ready to move on for further development. |
Scale (0-3) |
20.0 |
Required |
Question 1.1.3
Required business algorithms are clearly accounted for in the design.
0 - One or more major algorithms are not covered by the design.
1 - All algorithms are covered by the design, but one or more major algorithm requires significant clarification.
2 - All algorithms are covered by the design, but one or more require more detail to move into the next phase.
3 - All requirements are covered and are ready to move on for further development. |
Scale (0-3) |
30.0 |
Required |
Question 1.1.4
Design provides a complete technical solution for the customer.
0 - Design is incomplete or missing one or more major document or area of detail.
1 - Design covers majority of solution but may miss some number of small details.
2 - Design is complete but needs minor clarifications.
3 - Design provides a complete and clear solution that is suitable for further development. |
Scale (0-3) |
20.0 |
Required |
| Section: Major Architectural Concerns |
*Weight:*20.0 |
| Question |
Type |
Weight |
Document Upload |
Question 1.2.1
The technologies chosen for the development of code is appropriate.
1 - One or more major technologies are inappropriate or misused.
2 - One or more minor technologies (peripheral to meeting requirements) are inappropriate or misused.
3 - All technologies are appropriate, but non-optimal.
4 - All technologies are appropriate and optimal. |
Scale (0-3) |
25.0 |
Required |
Question 1.2.2
Concurrency is appropriately addressed with regard to the specific needs of this application.
1 - Concurrency needs are not fully covered by the design.
2 - Concurrency needs are addressed but missing major details.
3 - Concurrency needs are met, but are not clearly addressed, or could be improved.
4 - Concurrency needs are clearly met and fully defined. |
Scale (0-3) |
25.0 |
Required |
Question 1.2.3
Configuration is appropriately addressed with regard to the specific needs of this application.
1 - Major configuration details are missing.
2 - Most configuration details are present but one or more foreseeable configuration detail are missing.
3 - Current configuration needs are clearly defined.
4 - Current and future configuration needs are clearly defined. |
Scale (0-3) |
25.0 |
Required |
Question 1.2.4
Security is appropriately addressed.
1 - Security needs are incorrectly addressed or are missing.
2 - Security needs are addressed, but flaws exist in the approach or require significant clarification.
3 - Security needs are properly addressed, but require minor clarification.
4 - Security needs are properly and clearly addressed. |
Scale (0-3) |
25.0 |
Required |
| Section: Standards Based Technical Requirements |
*Weight:*10.0 |
| Question |
Type |
Weight |
Document Upload |
Question 1.3.1
The technologies chosen for the development of persistence mechanisms is appropriate and clearly defined.
1 - Persistence is inappropriately or incompletely defined.
2 - Persistence is defined but the approach has minor flaws that will need to be resolved.
3 - Persistence is correct, but requires more detail.
4 - Persistence is appropriately and clearly defined. |
Scale (0-3) |
40.0 |
Required |
Question 1.3.2
Logging is appropriately addressed with regard to the specific needs of this application.
All major details regarding logging are included. |
Yes/No |
20.0 |
Required |
Question 1.3.3
Exception handling is appropriately addressed with regard to the specific needs of this application.
All major details regarding exception handling are included. |
Yes/No |
20.0 |
Required |
Question 1.3.4
Transactionality is appropriately addressed.
Any necessary transactions and their management are addressed. |
Yes/No |
15.0 |
Required |
Question 1.3.5
Internationalization and/or branding is appropriately addressed.
All major details regarding internationalization or branding are addressed. |
Yes/No |
5.0 |
Required |
| Section: Component Design |
*Weight:*20.0 |
| Question |
Type |
Weight |
Document Upload |
Question 1.4.1
Existing components used in the design are appropriate.
1 - One or more components is inappropriate for this application.
2 - One or more components may require un-specified changes or upgrades to be used in this application.
3 - All components are appropriate but may have better alternatives.
4 - All components used are appropriate and ready to be used for this application. |
Scale (0-3) |
20.0 |
Required |
Question 1.4.2
The design does not miss any useful existing components.
There are no extra existing components which could improve this application. |
Yes/No |
10.0 |
Required |
Question 1.4.3
New generic components used in the design are appropriately separated from the application specific functional and technical requirements.
1 - One or more major area of custom functionality are presented in generic components.
2 - One or more minor area of custom functionality are presented in generic components.
3 - Component functionality is appropriate, but may require clarification to be produced.
4 - Component functionality is clear and correct. |
Scale (0-3) |
10.0 |
Required |
Question 1.4.4
New generic components deal with a single problem domain and are useful for future projects.
Components do not group inappropriate or future-unsafe areas of functionality. |
Yes/No |
10.0 |
Required |
Question 1.4.5
New generic components are appropriately extensible.
Components will not require a full major version to perform simple upgrades, et cetera. |
Yes/No |
10.0 |
Required |
Question 1.4.6
Components are appropriately scoped in size and complexity.
1 - One or more components is too large or complex.
2 - One or more components is too small or simple.
3 - All components are of appropriate size but obvious improvements may be made.
4 - All components are appropriately and optimally scoped. |
Scale (0-3) |
20.0 |
Required |
Question 1.4.7
Dependencies between all components are mapped appropriately.
No circular or inappropriate references. |
Yes/No |
5.0 |
Required |
Question 1.4.8
Each functional requirement is clearly and directly tied to one or more components.
1 - One or more major functional requirements is incompletely or incorrectly addressed by a component based solution.
2 - One or more minor functional requirements is incompletely or incorrectly addressed by a component based solution.
3 - All requirements are addressed but require more detail to move into the next phase.
4 - All requirements are met and are ready to move on for further development. |
Scale (0-3) |
10.0 |
Required |
Question 1.4.9
Components are utilized as much as possible to reduce assembly competition complexity.
As much code as possible is produced via components instead of being deferred to assembly. |
Yes/No |
5.0 |
Required |
| Group: Design Details |
Weight 20.0 |
| Section: Deployment and Integration |
*Weight:*10.0 |
| Question |
Type |
Weight |
Document Upload |
Question 2.1.1
Existing systems affected by this application are clearly defined.
Guideline goes here. |
Yes/No |
10.0 |
Required |
Question 2.1.2
Existing systems providing data to this application are clearly defined.
Guideline goes here. |
Yes/No |
10.0 |
Required |
Question 2.1.3
Existing systems utilizing this application are clearly defined.
Guideline goes here. |
Yes/No |
10.0 |
Required |
Question 2.1.4
Deployment issues are appropriately addressed.
1 - One or more significant deployment details are missing.
2 - One or more minor deployment details are missing.
3 - Deployment details are present but require slight clarification.
4 - Deployment details are present and clear. |
Scale (0-3) |
70.0 |
Required |
| Section: Tiering and Logic Isolation |
*Weight:*20.0 |
| Question |
Type |
Weight |
Document Upload |
Question 2.2.1
A clear delineation exists between presentation, business logic, and persistence.
1 - One or more major feature is not appropriately delineated.
2 - One or more minor feature is not appropriately delineated.
3 - All functionality is appropriately delineated but may require minor clarification.
4 - All functionality is appropriately and clearly delineated. |
Scale (0-3) |
40.0 |
Required |
Question 2.2.2
The presentation and persistence layers are not used to apply business rules to data.
Guideline goes here. |
Yes/No |
30.0 |
Required |
Question 2.2.3
The persistence layer's schema is independent of the business entities used by the business logic and presentation.
Guideline goes here. |
Yes/No |
10.0 |
Required |
Question 2.2.4
The logical design of each layer is appropriate and potentially re-usable.
Guideline goes here. |
Yes/No |
20.0 |
Required |
| Section: Data Model and Entity Relationships |
*Weight:*10.0 |
| Question |
Type |
Weight |
Document Upload |
Question 2.3.1
The Data Model is appropriate and correctly normalized for the project requirements.
Guideline goes here. |
Yes/No |
45.0 |
Required |
Question 2.3.2
The data model is clear and well organized.
Guideline goes here. |
Yes/No |
45.0 |
Required |
Question 2.3.3
Appropriate DDL are provided for the data model.
Guideline goes here. |
Yes/No |
10.0 |
Required |
| Section: Design Extensibility and Flexibility |
*Weight:*20.0 |
| Question |
Type |
Weight |
Document Upload |
Question 2.4.1
The design is not overly complex given the stated scope of the requirements AND the stated future intentions of the application.
1 - The complexity of the design will directly impact the ability to complete the current application.
2 - The complexity of the design may directly impact future versions.
3 - The application is appropriately scoped but requires clarification for future versions.
4 - The application is appropriately scoped and clearly provides a viable scope for future versions. |
Scale (0-3) |
40.0 |
Required |
Question 2.4.2
Are architecture defined interfaces appropriate and optimal?
1 - One or more major interface is inappropriate or poorly designed.
2 - One or more minor interface is inappropriate or poorly defined.
3 - All interfaces are appropriate but could easily be improved.
4 - All interfaces are appropriate and cannot be easily improved. |
Scale (0-3) |
40.0 |
Required |
Question 2.4.3
The design provides an appropriate level of configurability to facilitate future expansion with a minimum of code change.
Minor or obvious functionality changes should favor configurability. |
Yes/No |
20.0 |
Required |
| Section: Performance |
*Weight:*20.0 |
| Question |
Type |
Weight |
Document Upload |
Question 2.5.1
Solution appropriately leverages horizontal and vertical scalability to meet performance goals.
Guideline goes here. |
Yes/No |
25.0 |
Required |
Question 2.5.2
Solution meets all current load needs.
1 - Design will not meet current performance goals.
2 - Design should meet current goals but performance is not explicitly addressed.
3 - Design explicitly addresses performance but needs clarification.
4 - Design explicitly and clearly addresses stated current performance needs. |
Scale (0-3) |
75.0 |
Required |
| Section: Future Scalability of Design |
*Weight:*10.0 |
| Question |
Type |
Weight |
Document Upload |
Question 2.6.1
The design accounts for stated future requirements in a scalable fashion.
1 - Design will not meet future performance goals due to scalability problems.
2 - Design should meet future performance requirements but scalability is not explicitly addressed.
3 - Design explicitly addresses scalability but needs clarification.
4 - Design explicitly and clearly addresses stated future scalability needs. |
Scale (0-3) |
50.0 |
Required |
Question 2.6.2
The design does not preclude useful approaches to scale the application in the future.
Guideline goes here. |
Yes/No |
50.0 |
Required |
Question 2.6.3
Risks due to unfamiliar, new, or exotic technology are appropriately documented.
Guideline goes here. |
Yes/No |
0.0 |
Required |
| Section: Assembly |
*Weight:*10.0 |
| Question |
Type |
Weight |
Document Upload |
Question 2.7.1
Architecture maps to appropriate assembly competitions.
Guideline goes here. |
Yes/No |
50.0 |
Required |
Question 2.7.2
Are all resources shared between assembly competitions defined clearly?
Guideline goes here. |
Yes/No |
50.0 |
Required |
| Group: Documentation |
Weight 15.0 |
| Section: Written Documentation Quality |
*Weight:*30.0 |
| Question |
Type |
Weight |
Document Upload |
Question 3.1.1
All required documents are provided and are of sufficient content.
1 - Multiple documents are missing or incomplete.
2 - One document is missing or incomplete.
3 - All documents are present but may be mislabled or improperly organized.
4 - All documents are present and appropriate. |
Scale (0-3) |
60.0 |
Required |
Question 3.1.2
All documents are formatted appropriately.
Guideline goes here. |
Yes/No |
20.0 |
Required |
Question 3.1.3
There are no frequent spelling or grammatical errors.
Guideline goes here. |
Yes/No |
20.0 |
Required |
Question 3.1.4
The language used is comprehensible by people who speak English as a second language.
Guideline goes here. |
Yes/No |
0.0 |
Required |
| Section: Diagrams |
*Weight:*15.0 |
| Question |
Type |
Weight |
Document Upload |
Question 3.2.1
Sequence diagrams are complete and include sufficient detail.
Guideline goes here. |
Yes/No |
45.0 |
Required |
Question 3.2.2
Class diagrams are complete and include sufficient detail.
Guideline goes here. |
Yes/No |
45.0 |
Required |
Question 3.2.3
All diagrams use the correct color coding.
Guideline goes here. |
Yes/No |
10.0 |
Required |
| Section: Testing |
*Weight:*15.0 |
| Question |
Type |
Weight |
Document Upload |
Question 3.3.1
Test plan comprehensively covers the functional requirements.
Guideline goes here. |
Yes/No |
30.0 |
N/A |
Question 3.3.2
Test plan comprehensively covers the technical requirements.
Guideline goes here. |
Yes/No |
30.0 |
N/A |
Question 3.3.3
Test plans are achievable and provide sufficient detail.
Guideline goes here. |
Yes/No |
40.0 |
N/A |
| Section: Component Documentation |
*Weight:*40.0 |
| Question |
Type |
Weight |
Document Upload |
Question 3.4.1
Are components designed with a uniform and clear approach to all technical issues?
Guideline goes here. |
Yes/No |
10.0 |
Required |
Question 3.4.2
Are components specifications clear and direct?
Guideline goes here. |
Yes/No |
40.0 |
Required |
Question 3.4.3
Are components complete and ready to launch with all necessary peripheral documentation?
Guideline goes here. |
Yes/No |
50.0 |
Required |
| Section: Secondary Documentation |
*Weight:*0.0 |
| Question |
Type |
Weight |
Document Upload |
Question 3.5.1
Any XML Schemas or DTD documents are provided.
Guideline goes here. |
Yes/No |
25.0 |
Required |
Question 3.5.2
All stub code files used to generate class diagrams are provided.
Guideline goes here. |
Yes/No |
25.0 |
Required |
Question 3.5.3
All standards documents are provided, if required.
Guideline goes here. |
Yes/No |
25.0 |
Required |
Question 3.5.4
All secondary documents are pertinent to the project.
Guideline goes here. |
Yes/No |
25.0 |
Required |
| Group: Prototype |
Weight 5.0 |
| Section: Prototype |
*Weight:*100.0 |
| Question |
Type |
Weight |
Document Upload |
Question 4.1.1
Prototype is clear and illustrates the architecture clearly.
1 - Prototype is missing or incomplete.
2 - Prototype is complete but does not accurately illustrate one or more major functional requirement.
3 - Prototype is complete, but would benefit from more detail.
4 - Prototype is complete and fully illustrates the architecture. |
Scale (0-3) |
60.0 |
Required |
Question 4.1.2
Prototype is easily deployable.
1 - Prototype cannot be deployed.
2 - Prototype can be deployed with major changes.
3 - Prototype can be deployed with minor changes.
4 - Prototype can be deployed with only configuration changes. |
Scale (0-3) |
40.0 |
Required |
