Project title

(Insert your team logo here)

Critical Design Review

Team name

Member 1

Member 2

Member 3

Member 4

Department of Computer Science and Engineering

TexasA&MUniversity

Date

Table of Contents

1Revised Proposal (20 points)

1.1Updates from the original proposal submission

1.2Needs statement

1.3Objective

1.4Marketing requirements

1.5Objective tree

1.6Requirements specification

1.7Background and technology survey

1.8Concept generation

1.9Concept evaluation

2Proposed design (50 points)

2.1Functional decomposition (15 points)

2.2Complete module-wise specifications (25 points)

2.2.1Module name (as shown in the Level-1 diagram)

2.3Acceptance testing (5 points)

2.4Integration testing (5 points)

3Project management (15 points)

3.1Work breakdown structure

3.2Timeline

3.3Costs

3.4Software engineering

3.5Team roles

4Preliminary results (15 points)

5References cited

1Revised Proposal (20 points)

1.1Updates from the original proposal submission

Describe any revisions you have made to the proposal, either based on feedback you received from the course instructor, or from additional information you have found since the proposal was written. Please organize this information as shown in Table 1.

Table 1. Example summary of revisions to the proposal

Section / Instructor feedback / Revisions made
Needs / Need statement does not include supportive statistics / The revised needs statement includes statistics on the prevalence of anxiety among adolescents, obtained from WHO
Needs / Need statement is poorly organized / The needs statement has been reorganized to
Objective tree / Items in the tree are different from the marketing requirements / We re-generated the objective tree using the marketing requirements
Background / No feedback provided / We recently found two more additional studies that are closely related to our proposed work and feel should be included
Functional design / Level-1design lacks details / We have redone the level-1 design by breaking the system down into sensing module, signal processing module and visualization module

1.2Needs statement

Include the revised section from the proposal (or the original one if no feedback was provided)

1.3Objective

Include the revised section from the proposal (or the original one if no feedback was provided)

1.4Marketing requirements

Include the revised section from the proposal (or the original one if no feedback was provided)

1.5Objective tree

Include the revised section from the proposal (or the original one if no feedback was provided)

1.6Requirements specification

Include the revised section from the proposal (or the original one if no feedback was provided)

1.7Background and technology survey

Include the revised section from the proposal (or the original one if no feedback was provided)

1.8Concept generation

Include the revised section from the proposal (or the original one if no feedback was provided)

1.9Concept evaluation

Include the revised section from the proposal (or the original one if no feedback was provided)

2Proposed design (50 points)

The Critical Design Review (CDR) defines a transition between the design stage of your project and the implementation/integration stages. In a typical project, all decisions have been made at this point concerning what will be built and how it will be tested. The objective of the CDR is to present a complete design of the system, an implementation plan and validation/testing procedures.

2.1Functional decomposition(15 points)

Provide a complete functional decomposition of your design in terms of a Level-0 diagram and a Level-1 diagram. This functional decomposition should reflect any feedback provided by the instructor at the time of the proposal. Please make sure to include a narrative that describes the system; do not just paste the Level-0 and Level-1 diagrams.

2.2Complete module-wise specifications (25 points)

For each module in the Level-1 diagram, provide a detailed design of how it will be implemented (both hardware and software), including (if applicable):

  • Circuit and logic diagrams
  • Hardware interfaces and pin-outs
  • Software libraries and processes with their inputs and outputs
  • Complete parts list

a common mistake when writing this section is to jump from a very high level description of the system (i.e., the Level-1 diagram) to a very specific detail (i.e., a microcontroller pin-out, or a piece of pseudo-code) without any details of what happens in between. As a guideline, every module for which you are providing specs should exist as a module in the Level-1 diagram, and every module in the Level-1 diagram should have its specs listed here. In other words, the two sections (functional decomposition and module-wise specs) must be complementary.

2.2.1Module name (as shown in the Level-1 diagram)

Provide a detailed design and specs for this module. (Repeat this subsection for each module in the Level-1 diagram.)

2.3Acceptance testing (5 points)

Include the revised acceptance test cases (or the original ones if no feedback was provided).

2.4Integration testing(5 points)

There are many interactions between the various modules in your system. Identify a subset of those interactions (e.g., 3 to 5 interactions) that are more likely to cause problems and generate integration tests for each –refer to section 7.2.3 in the textbook and the case studies in chapter 7 for examples. Each integration test should be described as a separate table.

3Project management(15 points)

3.1Work breakdown structure

Include an updated WBSthat reflects the complete system design (and any feedback from the instructor at the time of the proposal)

3.2Timeline

Include an updated Gantt chart that reflectsthe complete system design (and any feedback from the instructor at the time of the proposal).

3.3Costs

Include updated costs that reflect the complete system design (and any feedback from the instructor at the time of the proposal).

3.4Software engineering

Include an updated description of the software engineering methodology you are using.

3.5Team roles

Include an updated task matrix that reflects the complete system design (and any feedback from the instructor at the time of the proposal).

4Preliminary results (15 points)

Provide any test results and demo of completed parts of the system at the time of the CDR.

5References cited

Acknowledge all the documents that you used as references throughout the text. Please follow the APA citation standard for references, as described in the Problem Statement template.

TAMU CSCE 482/483 Critical Design Review 1/5