Send your homework to the grader at the following address:
Only send one copy and include "CS251A" in the subject line. Make sure your homework is delivered no later than the deadline, or it won't be graded. About 7 – 10 days later the grader will reply with a rubric containing your grade and comments. Keep a copy of this and your homework in case there is a discrepancy in my records (which happens more often than I would care to admit.)
After you receive the rubric, if you have questions about the grading, send a query to the grader at the above address, again include "CS251A" in the subject line. If you are not satisfied with the grader's response, then bring it up with me.
In class we will use StarUML to create activity graphs to model several workflows from:
Representing workflows as activity diagrams
On your own, model the workflow called Work Breakdown Structure, and submit it by email to the grader. (Address will be posted soon.)
Here is the rubric the grader will use to evaluate your work: eval.txt.
Due: Friday, September 4 by noon.
In class we will use StarUML to create activity graphs to sketch several functional specifications from:
Writing functional specifications
On your own, write a functional specification for a social networking system (#7), and submit it by email to the grader.
Here is the rubric the grader will use to evaluate your work: eval.txt.
Due: Friday, September 18 by noon.
In class we will use StarUML to create class diagrams from:
Please complete the last problem—Meta Model.
Due: Thursday, October 1 by 11:59 PM
In class we will use StarUML to create analysis models from:
Submit a functional specification and requirements analysis document (RAD) for Halo.
Submit these documents (either as .doc or .html files, but please, no docx files).
Due: Tuesday, October 20 by 11:59 PM
This is a team project due at the end of the semester. Follow the link for details.