Introduction to Software Engineering


CMPS 115Software MethodologyFall 2011 Syllabus Emphasizes the characteristics of well-engineered software systems. Topics include requirements analysis and specification, design, programming, verification and validation, maintenance, and project management. Practical and research methods are studied. Imparts an understanding of the steps used to effectively develop computer software.

 

 

Students with Disabilities
"If you qualify for classroom accommodations because of a disability, please submit your Accommodation Authorization Letter from the Disability Resource Center (DRC) to me as soon as possible, preferably within the first week of the fall quarter. Contact DRC by phone at 831-459-2089 or by email at drc@ucsc.edu for more information."

Instructor: Linda Werner
Office:
Eng 2, 249
Office Hours:
Tues and Thurs 4-5pm and other days and time by appointment.
Class location, hours:
Eng 2, 192, TTh 2-3:45pm
Preparation for first class:
read chap 1 of textbook
Textbook:
Object-Oriented Software Engineering by Stephen R. Schach, McGraw Hill, 2008, ISBN 978-0-07-352333-0.
Labs:
BE 105
A:  Mondays, 1:00-2:00pm
B:  Wednesdays, 3:30-4:30pm
Email: linda@soe.ucsc.edu
Final:
Thurs, Dec 8, 8:00-11:00am. 

 TA's and labs:

Tutors/Graders: Dominic Arcamone and Ben Ross
Email: darcamon@ucsc.edu
Email: bpross@ucsc.edu
Labs:  BE 105
A:  Mondays, 1:00-2:00pm
B:  Wednesdays, 3:30-4:30pm
Each student is required to enroll in and attend a weekly lab (the same one of these scheduled labs each week).

Team Project:

Students are required to collaborate in teams of 5-6 people to undertake a significant software engineering project. The software project is structured as a collection of documentation and code deliverables. This project requires a substantial amount of work, and demands good teamwork. See information in the course tools (titled Resources: FiringTeamMember.pdf) for appropriate team member behavior and consequences. You are required to complete one of the projects from the following list. The project system is required to run on the machines located in the class lab or on hardware approved by the instructor.

  • The textbook's term project - Osric's Office Appliances and Decor - see page 524
  • A game or other system of your choice and approved by instructor
  • software system to assist in Alice research project

Here are links to information that will help you with the team aspect of your project:

  • Teamwork Guide written by Ed Parrish (former cmps115 student and TA. Currently he is a professor at Cabrillo College.
  • Groups That Work More on groups, with tips for how to identify and resolve group problems.

End-of-chapter suggested problems:
Look in the table that follows under the column heading "Reading/Homework DUE" for lists of problems.

Evaluation: Work in CMPS115 is divided into two main components.

  • Individual work (44%).
  • Team work: the deliverables for the team project. This part includes individual components such as the project reflection essay (56%).

The individual work component consists of the following parts:

  • Research paper assignments including class attendance and participation: 20%
  • Exams (based on end-of-chapter problems, project work, lectures): 24%


A minimum of 50% on the two main components is necessary but not sufficient to pass this class. This means, if you receive less than 50% on any one of the two components, 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 project. The project is designed to be done by people working together. The in-class quizzes and final exam are to be done by each student, working alone. Students may work together to complete the work required with the research papers, however, copying other students' work is not permitted. 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 in that portion of this class and result in a no-pass or failing grade. Students are encouraged to read the campus policies regarding academic integrity.

Project Deliverables Project deliverables are due at stated date and time as indicated in syllabus. If written documents are required (ie. user manual) they are to be neat and clear, with proper English spelling and syntax throughout. All project program online instructions are required to be clearly written with proper English spelling and syntax.  All code and other documents (ie. user manual, daily scrum status reports) need to be under control of a version control system (such as subversion). Additionally, a record of changes to these documents is required. This part of each deliverable is worth 10% and is called presentation in each grading sheet. Each of the grading sheets itemizes the points given for each part of that deliverable.

Homework: All homework (project milestones, research paper assignments (read-and-comment), suggested end-of-chapter problem sets, and textbook reading assignments) is listed in the syllabus. The due dates are given. To prepare a 'read-and-comment' assignment, you are required to read the listed paper. You are also required to submit approximately one half page of comments about what you have read. This needs to be a well-written document using correct English. Please see the writing tutors for help. These comments can be: 1. ideas you had about the topic before you read the paper and your impressions about this after finishing the paper, or 2. a question you had about the paper before you finished reading and the answer you found from the paper, or 3. a lingering question you have about the topic and explain why the paper doesn't address it.


You are NOT required to bring a copy of your 'read-and-comment' submission to class. Be prepared for pop quizzes based on the homework including the 'read-and-comment' papers. See the syllabus for details.

Instructors and Assistants