User Tools
specification
Differences
This shows you the differences between two versions of the page.
|
specification [2014/01/03 11:10] hutch |
specification [2014/01/24 08:16] (current) hutch |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== Specification ====== | ====== Specification ====== | ||
| Before you start any project, especially a group project, you need to put together a detailed specification. The specification (along with a schedule) helps you to stay on track during the course of the project. In this case you will be writing a specification for the laser-tag project. This specification must contain the following major sections: | Before you start any project, especially a group project, you need to put together a detailed specification. The specification (along with a schedule) helps you to stay on track during the course of the project. In this case you will be writing a specification for the laser-tag project. This specification must contain the following major sections: | ||
| - | - **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. It is at the interfaces are that most bugs occur. | + | - **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 about 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. | + | - ** 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 components (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. | ||
| - | Your specification will be graded three times. The first grading will be consist of a partial grade along with feedback for improvement. The second grading will consist of a partial grade and feedback for improvement. The third grading will consist of a partial grade and further suggestions for improvement. The final grade for the specification will be based upon the prior partial grades. It is not possible to improve the grade for the specification after the third grading, so you need to do a good job on each of the three grading in order to receive a good grade on the overall specification. | + | **Notes:** |
| + | - Hand-drawn figures are unacceptable. All diagrams must be drawn using graphical-drawing software of your choice, e.g., Visio, or some such. Also, the overall document must be created using Word, Pages or some equivalent. You will submit your specification as a PDF file. Other formats will not be accepted. | ||
| + | - Specifications are living documents. You will need to update the specification as you go along so anticipate the need for constant updates at the onset. | ||
| + | - Points will be lost for incorrect grammar or misspelled words. | ||
| + | |||
specification.1388772633.txt.gz · Last modified: 2014/01/03 11:10 by hutch
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 3.0 Unported
