CMPS 115 SYLLABUS

CMPS 115 -- Software Methodology Syllabus

See FAQ's for information about the final exam.

[Homepage] | [TA's and labs] | [FAQ's] | [Project] | [Homework] | [Exams]

Instructor Information

Office: BE 157C
Hours: Tuesday and Thursday 2-2:30 and by appointment
Email: linda@cse.ucsc.edu
PowerPoint Slides

TA's and labs

This section contains information about the TA's and the lab times and activities. The two labs are located in Jack Baskin Engineering 109. The times are Tuesday, 10am-11am and Wednesday, 2pm-3pm. Each student is required to attend the same one of these scheduled labs each week. Your project system is required to run on the machines located in this lab.

Supplements

This section contains additional information from the instructor to supplement the lectures. Project milestone information is found here. Materials will be added here as they become available. One source of useful information for cmps115 is found at the course newsgroup ucsc.class.cmp115.

FAQ's (Frequently Asked Questions): See if your question is here!

Required Text:

Software Engineering An Object-Oriented Perspective. Eric J. Braude, Wiley, 2001.
This book is available at the BayTree Bookstore. The publisher has a website here. See this for the slides used in class. In addition, there are answers to the "general" exercises at the end of every chapter, Java source code for the case study found in the book, and the case study documentation (which can be used as templates for your milestones). Optional texts are the following:
Introduction to the Personal Software Process. Watts S. Humphrey, Addison-Wesley, 1997.
UML Distilled -Applying the Standard Object Modeling Language. Martin Fowler with Kendall Scott, Addison-Wesley, 1997.
The Mythical Man-Month . Frederick P. Brooks, Jr., Addison-Wesley, 1995.

Evaluation:

A minimum of 50% on the first three aspects of the grade is necessary but not sufficient to pass this class. This means, if you receive less than 50% on any one of the first three parts, you will not pass. Just because you receive at least 50% on each part does not imply that you will necessarily pass. You cannot pass this class if you do not do the inspection. You cannot pass this class if you do not do the project. You cannot get an A if you do not do the homework.
Working Together: The project is designed to be done by people working together. The in-class quizzes, final exam, and the homeworks are to be done by each student, working alone.
Academic Dishonesty: Any confirmed academic dishonesty including but not limited to copying another's homework, cheating on exams, and copying project work without giving credit to the author of the work products, will constitute a failure of the computer ethics portion of this class and result in a no-pass or failing grade. Students are encouraged to read the campus policies regarding academic integrity.

Homework: Turn in homework in class on Tuesday of each week. Place the homework on the table at the front of the room. Late work will NOT be accepted or graded. Homework is graded in terms of being done using correct grammar, complete sentences, being readable, and referring correctly to software engineering tools and techniques that have been discussed in class or read in the previous week's assigned readings.

Exams: The first quiz will be on April 12. The second quiz will be on May 3. The third and last quiz will be on May 24. The final exam is scheduled for Tuesday, June 5, from 4-7pm. The final exam is to be taken by all students who do not achieve a good class performance. Class performance requires an average of 80% or better on in-class quizzes.

Other Instructional Material

Syllabus

Date Topic Reading Task
March 27 Introduction and Software Process Introduction and Chapter 1, part 1 ad-hoc group meeting and class exercise
March 29 Inspections and Project Management Chapter 1(6.2), Chapter 2, part 1 inspection video and groups chosen
April 3 Paper Prototypes and Requirements Analysis Rettig's paper and Chapter 3 homework 1 due and projects chosen
April 5 Requirements Specification Chapter 3 SRS part 1 inspection
April 10 Requirements Specification Chapter 4, part 1 homework 2 due, paper prototype design exercise
April 12 review Chapters 1-4 paper prototype test, quiz
April 17 Software Architecture Chapter 5 homework 3 due, design exercises
April 19 Software Architecture Chapter 5 SRS part 2 inspection
April 24 Detailed Design Chapter 6 homework 4 cancelled, design exercises
April 26 Detailed Design Chapter 6 ARCH inspection cancelled
May 1 Unit Implementation Chapter 7 homework 5 due, software verification
May 3 review Chapters 1-7 DD inspection, quiz
May 8 Unit Testing Chapter 8 homework 6 due
May 10 Unit Testing Chapter 8 UT inspection
May 15 Industry Speaker Chapter 9 homework 7 cancelled, Industry Speaker
May 17 Integration, V&V Chapter 9 CODE inspection
May 22 Maintenance Chapter 10 homework 8 due, project exercises
May 24 review Chapters 8-9 quiz
May 29 System Test Chapter 9 STD inspection
May 31 Project Display in lab Entire Project Notebook due including system test document
June 5, 4-7pm Final Final final exam