Specification Document - Part 1 Instructions Assignment due at the end of the second week. It is common for group members to do some risk reduction activities.
Students sometimes experiment with the programming language that they have chosen for their project.
They will do a 'quick and dirty' coding of some of the functions specified in their requirements specification. This activity is called a 'proof of concept' and can save time later in the quarter. There are numerous formats to use. See the TA's and Labs information page for templates. A possible template for the SRS is given in the textbook at the ends of chapter 3 and chapter 4.