CS3733-B03 Assignments

Homework assignments are due before class on the due date. Late assignments will generally not be accepted. See the course policies page for more details.

In the following assignment table, only those assignments with due dates are ones that you will need to turn in for credit. You are encouraged to do the other assignments to deepen your understanding of the material, or to gain skills with specific tools and techniques. Those assignments with an X in the Team column are team assignments and are to be done as a team, with the team getting the grade.

#
 Description
Assigned
Due
Team
1
  • Identify your team members and post them to the Teams forum on myWPI.
  • Do exercise T2, p. 14 of the text. This is the first document that should go in your project notebook. Make sure you put your team name, team members, and date on the document.
    (/cs/bin/turnin submit cs3733 hw1 homework1.doc)
16-Mar
18-Mar
X
2
 Get your project notebook started. This should be a loose leaf binder with sections that follow the outline. Put your first homework in the section on Other Process Documents.
18-Mar
  
X
3
 Write your initial project plan, initial iteration plan, vision, and risk list for the class project. Turn in copies of these documents for grades. (/cs/bin/turnin submit cs3733 hw3 homework3.zip)
21-Mar
25-Mar
X
4
 Do General Exercise 3.4 in the text, page 173. At the end of your discussion, indicate which method of specifying user interfaces you would use for the course project, and why. (/cs/bin/turnin submit cs3733 hw4 homework4.doc)
2-Apr

6-Apr

  
5
 Prepare your marketing presentation using the marketing presentation template as a guide.
1-Apr
8-Apr
X
6

Consider the lifetime of a defect in software. The defect must be reported (found), then it must be evaluated and assigned a status (fix, defer, or not a bug). If the status is that it must be fixed, it must be scheduled, then assigned. The assigned developer must fix it, it must be tested, and then integrated and shipped. If it is deferred, nothing happens to it until someone decides that it will be fixed, or that it really isn't a defect. Things that are not defects are dropped from the "bug" list as are fixed defects.

Construct a UML statechart diagram that shows the states a defect goes through, including the events that trigger the transitions from state to state. Make sure that you name the states and events with understandable names.

If you use a tool that produces an electronic form of the diagram, submit it using the command:
/cs/bin/turnin submit cs3733 hw6 <your file name>
17-Apr
23-Apr
  

 

Modified: 17-Apr-2004
Gary Pollice