This course investigates software engineering techniques for maintaining intellectual control of software projects. Software engineering is not a synonym for "programming". In the big picture, software engineering consists of the following tasks:

• Requirements analysis: Determining what the software should do, expressed in the language of the customer
• Specification: Describing the requirements in a technical manner
• Design and Implementation: Building software to meet the needs of the customer
• Verification: Determining that the implementation meets the specification
• Validation: Determining that the implementation meets the needs of the customer

Several different software projects will be developed in parallel during the semester. All of the above activities will be performed for each project. You will rotate between the projects throughout the semester. Requirements analysis and some specification work will be done individually; other tasks will be performed in teams.

• Write a requirements document using use-case analysis
• Write boundary specifications using black boxes
• Design a user interface to correspond to a black box specification
• Validate a black box against its requirements document
• Design a user interface to correspond to a black box specification
• Understand and apply the Design-by-Contract concept
• Write fully automated unit tests
• Perform a software inspection
• Formally verify the correctness of a method
• Write clear and correct technical prose

• An excellent resource for the activity described in the title.

• In-depth examination as to how to formally verify code. Relatively easy to follow, given the subject matter.

• Good overview of the theory of black-box specification. A challenging but worthwhile read.

For each category above, the total points earned will be divided by the total points possible to yield a percentage. These percentages will be weighted as given above. A final average of at least 90 earns an A; 80 earns a B; 70 earns a C; 60 earns a D; below 60 is failing.

Team Projects: Some projects will be assigned to teams. All members of a team will receive the same grade for the submission. Students should keep in mind that procrastination will affect not only their grade, but the grade of other students. When a team project is underway, every team member has the responsibility to communicate with their teammates.

Writing Assignments and W2 credit: All writing assignments will be graded for both technical correctness and writing quality. If you elect to receive W2 credit for this course, you will also be required to revise your written assignments to correct issues in writing quality identified by the instructor. These revisions must all be satisfactory in order to receive W2 credit.

Extra Credit: Extra credit opportunities will be available throughout the semester. Each unit of extra credit will add one-tenth of a point to your final semester average.

Late Homework Policy: All homework assignments will include a time of day at which they are due. Late assignments lose one letter grade for every 24 hour period that they are submitted after the deadline. Weekends are not included in this computation. So if an assignment is due at 5 pm Friday and it is submitted before 5 pm Monday, it will be one day late. There will be no exceptions to this policy, although emergencies will be handled on a case-by-case basis.

Computer Lab Facility: You will receive an account that enables you to use the Linux machines in MCReynolds 316. Be sure to review the lab policy page: http://ozark.hendrix.edu/linux/policies.html