ESOF 427
Software Design and Architecture
Fall 2014

Montana Tech
Computer Science & Software Engineering


This page lists the programming assignments for the course. When an assignment is released, the assignment column will link to a detailed description of the assignment.

0Mon 9/8 11amKeyboard, design draftindividual
1Thurs 9/11 11amKeyboard, UML class diagrampair
2Thurs 9/18 11amKeyboard, implementation of tracespair
3Mon 10/13 11amPrefix refactoringpair
4Mon 10/27 11amKeyboard refactoringpair
5Mon 11/24 11amPattern zooindividual
6Thurs 12/11 11:30amFinal projectpair

Submission. All assignments need to be submitted via Moodle. In the event of a Moodle failure, email your submission to me before the deadline. You should upload all the source files required by the assignment. You should also include any other files required to run your solution. The top of every source file should include your name, username, and a description of what the file does.

Deadline and late policy. All assignments are due at the stated date and time. Assignments arriving even one minute late are considered late. You get a total of four free late days. Each late day buys you a 24-hour extension to a submission deadline. If you are out of free late days, any further late submissions will be given a zero. On designated pair assignments, the pair only has as many late days as the student with the fewest remaining late days. Late days do NOT apply to presentations, papers, or exams.

Grading. Your code will be graded on correctness, programming style (including comments), and efficiency. Partial credit is possible so if you run out of time, submit what you have. If you want to do well, start well in advance of the deadline. This allows time to seek help if you run into trouble. Software bugs can be difficult to find and are often easily found after a good night's sleep.

Collaboration policy. Programming is a creative process and no two programmers will solve the same problem in the same way. You are encouraged to discuss how to design a solution to a given problem with your classmates. But when it comes time to convert your design into code, you must write the code yourself. Be sure not to leave copies of your code where others might be able to access it (such as in the recycling bin of a lab computer). You may adapt code from the CSCI 446 course materials provided you cite what code you used in your program's comments.

Under no circumstances should you copy another person's code. Copying code from another student can result in an F in the course. Novices often mistakenly believe simple transformations can disguise a copied program. In actuality, copied programs often reveal themselves quite easily during grading. We can also use sophisticated software such as MOSS to detect plagiarized code.

Pair programming. For designated assignments, you are encouraged (but not required) to pair program with another student in the class. In pair programming, both people work side-by-side at the computer on the same program. One person is the driver who actively types at the computer or records a design. The other person is the navigator who watches the work of the driver, identifies problems, asks clarifying questions, and makes suggestions. About every half-an-hour, the pair should switch roles. Before starting pair programming, you should watch this video. A pair should submit one solution with both partner's names and usernames in the header of the submitted files.

Page last updated: October 27, 2014