User Tools
specification
Differences
This shows you the differences between two versions of the page.
|
specification [2014/01/24 08:11] hutch [Checklist] |
specification [2014/01/24 08:16] (current) hutch |
||
|---|---|---|---|
| Line 3: | Line 3: | ||
| - **Complete System Description.** Use a block diagram to break the project down into all of its constituent subsystems. The block diagram will need to be hierarchical, i.e., it will start out at the top showing the organization of the major subsystems along with their interconnections. Each of the subsystems will need to be described using additional block diagrams. In this system description, a description of the interfaces between the subsystems is most important. Where wires or cables are involved, make sure to specify interface conventions such as bit-width, bit-order, wire-count, etc. Most bugs occur at interfaces. | - **Complete System Description.** Use a block diagram to break the project down into all of its constituent subsystems. The block diagram will need to be hierarchical, i.e., it will start out at the top showing the organization of the major subsystems along with their interconnections. Each of the subsystems will need to be described using additional block diagrams. In this system description, a description of the interfaces between the subsystems is most important. Where wires or cables are involved, make sure to specify interface conventions such as bit-width, bit-order, wire-count, etc. Most bugs occur at interfaces. | ||
| - ** Software Organization. ** You will organize and implement your software using the principles that you learned in ECEN 330. You must use state machines and a task scheduler to implement your system. In general, it makes sense to create a block diagram that illustrates the various state machines and their interconnections. Each state-machine should be described using state-diagrams as described in the book. Keep your state machines as simple as possible, with as few states as possible. | - ** Software Organization. ** You will organize and implement your software using the principles that you learned in ECEN 330. You must use state machines and a task scheduler to implement your system. In general, it makes sense to create a block diagram that illustrates the various state machines and their interconnections. Each state-machine should be described using state-diagrams as described in the book. Keep your state machines as simple as possible, with as few states as possible. | ||
| - | - ** Testing and Verification Plan ** You must describe how you will go about testing each of the sub-systems (software and hardware). You must provide details about your testing and verification plan. Each major block in the system must be tested and must have an associated test plan. | + | - ** Testing and Verification Plan ** You must describe how you will go about testing each of the sub-systems (software and hardware). You must provide details about your testing and verification plan. Each major block in the system must be independently tested and must have an associated test plan. |
| - ** Hardware Inventory. ** You must have a list of the required hardware components, parts, and their associated costs in the specification. | - ** Hardware Inventory. ** You must have a list of the required hardware components, parts, and their associated costs in the specification. | ||
specification.1390576319.txt.gz · Last modified: 2014/01/24 08:12 (external edit)
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 3.0 Unported
