User Tools

Site Tools


specification

This is an old revision of the document!


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:

  1. 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.
  2. 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.
  3. Hardware Inventory. You must have a list of the required hardware components, parts, and their associated costs in the specification.
specification.1388772342.txt.gz · Last modified: 2014/01/03 11:05 by hutch