Assignment 3 - Full Design and Specification

At this point in the project, you have come up with an initial design. You have selected your team (or opted to work individually), and will be developing a full specification.

For this deliverable, please provide a team name! (Be as creative as you like)

Design Specification

We will be following the Design-by-Level theory for the design specification. From your previous assignment, you have already completed the conceptual-model. You may optionally submit any revisions you have.

Semantic Level Design

Semantic diagram gives an organized listing of the functionality of a system. This should include at least 4 functions, with their parameters, description, feedback, and errors.

Syntactic Diagram

This is a listing of user actions and system responses. You should have at least a high level syntactic diagram, and then go into detail on 2 subsystems. These two subsystems could be the commands that are in your task analysis for instance.

Lexical Model

This is a glossary for each of the user actions and system responses that you have highlighted in your syntactic diagram.

Documentation and Guidelines

Prepare a 1 page piece of documentation describing your product to your user. This can be done in paragraphs, using lists, or images. The more self-evident the tool is the better! There is no need to discuss things like the operating system, files to install, etc. Assume the system is already running and you have 1 page to inform the user about what is interesting about your tool.

Secondly, prepare a list of guidelines document that your team is going to use to implement this project. These could be style guidelines for instance about how different components will go together. These could also be team guidelines, discussing how the code would be organized, what color schemes will be used, or other ideas you have. This document need not be longer than 1 page (but if you find it helpful, you can expand as long as you like). Your guidlines should have the following:

Here are some resources to get inspiration from.


A storyboard is a 'comic book' like sketch of your user using your product. In the previous assignment, you created a functionality and use case scenario. Pick one of the functionalities, and draw out the storyboards for the three scenarios highlighted.

You may draw your storyboard on paper and scan it (or take a photo) and embed the photo in the final deliverable.

Task-Command Analysis

Perform a task-command analysis using the KLM model. You should perform the task-command analysis for each of your 3 functionalities that you highlighted in your previous assignment. Make sure to have an analysis at the end, where you can comment on improvements/insights found after doing the analysis (if it is perfect, then comment why).


Throughout your assignment, state any assumptions that you may have. In each catagory, the goal is that this is self-evident, but you may add additional information as you see fit.


Please use bulleted lists and tables where appropriate. Start to think of your deliverables as a blueprint, such that another team in the class could follow along with your project. Use pictures, video, and add elements as you see appropriate. Be sure to cite all references!

Grading Rubric and Submission

You will submit your homework as a pdf on Blackboard for the CS 5340 course. Please do not e-mail me your submission. You may use tools like Google Docs, Microsoft Word, or Libre Office to generate .pdf files for submission.

The following rubric will be used to evaluate your work: