Instructions CMPS115 Milestone 3-SRS part 2 Linda Werner Software Requirements Specification Document part 2 Instructions Assignment due at the end of the fourth 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 Information Page for templates. In addition, available from campus IP's, see IEEE Standard 830-1993 Recommended Practice for Software Requirements Specifications.