Catalog description: 

"Principles for engineering requirements analysis and design of large complex software systems. Software process models. Methods of project planning, tracking, documentation, communication, and quality assurance. Analysis of engineering tradeoffs. Group laboratory project. Technical oral and written presentations. 3 lectures, 1 laboratory. Prerequisite: CSC/CPE 103 with a grade of C- or better, and CSC/CPE 357 or CSC/CPE 353."

Course Objective:
To learn skills required to produce and maintain a high-quality software product on time and within budget.  This is the first in a 2 course sequence in Software Engineering.  It is generally assumed that the student plans to take CPE 309 in the next term. 

Prerequisites:
CPE 103 and [CSC 357 or CSC 353].  

Course Description
Principles of Software Engineering at the basic level.  This is taught through software requirements elicitation, analysis and documentation. Team process infrastructure is emphasized.  The course touches on resource estimation to support appropriate levels of quality. The main deliverables include a Software Requirements Specification (SRS) and a corresponding architectural design.

Course Tools
The software engineering profession is rife with tools; there are literally thousands of tools available to [supposedly] help software development. In CPE 308, the focus is placed on process - not tools.  You are welcome to utilize tools in addition to the ones we cover in class.  The basic tools we may use are:

• English 
• Unified Modeling Language diagrams
• Other formal notations for describing specifications in a pricise and concise manner
  
• Some line drawing tool (e.g. for data flow diagrams)
• Analytic tools such as FSM's, State Diagrams, DFD's
  
• Customer (Domain) related tools we find necessary
  

Team Project
All of the work in CSC 308 is connected to a project. You will work in a team to carry out each phase of the project.  

The project itself will have to meet standards of the Instructor, the Customer and the needs of CSC 308.  Project standards will be discussed in Lab and Lecture.  

2 Minute Talks

Note that you can avoid the written answers to reading questions if you are willing to give additional extemporaneous two minute talks on the course readings. In this case, you will be asked to answer, without prior notice, questions about the course readings for the week.

Project Journal
Each individual is required to keep a journal and bring it to every class meeting. Every entry in the notebook must be dated and clearly labeled. The major objectives of the notebook are writing practice and engineering experience; write every entry in your own words. The notebook must contain, at a minimum:

• Your name, contact information and group logo on the outside.
• Lists of assigned action items.
• Notes on action item work.
• Notes on interviews, research, tools and anything else of project interest.
• Weekly status reports.
• Answers to reading questions.
  (note you can avoid this requirement with two minute talks)
• A timelog for time spent on the course / project
  

Examinations

There will be one written midterm and a final examination.  

Grading
All grading in CSC 308 is done in a "wholistic" manner.  You do not pass or fail on simple "numbers" and "numbers" mean no more than any other abstraction (a 50% is not necessarily an "F", neither is a 90% necessarily an "A").  The goal is for students to learn a mature approach to software engineering.  Look at definitions of this term.  It involves your ability to perform well in individual assignments, perform well as part of a team, to execute a rationally derived process to achieve a quality requirements document and software architecture. 

The project is the cornerstone of this course and is the primary basis of your course grade. The project grade is assigned on an individual basis; each student will earn a project grade of A, B ... or F assigned subjectively.  A prerequisite to earn an A is to accept and complete action items on your group deliverables.  Coat-tail hanging or non-performance by an individual will result in a course grade of F. You are required to participate fully in your group project.  You must perform as part of a team, this is paramount.

I expect each member of a well-run group to receive an A. You cannot receive a passing course grade until your portion of the project is completed satisfactorily. In addition, any deliverable document is not final (not graded) until it is signed by the customer, each member of the group intending to continue in the 308/309 sequence, and the instructor.

The project evaluation is done as if you were a corporate employee. Each project deliverable must be completed in a professional way; when finished the deliverable will be assigned a grade. Work may be returned until it reaches a professional standard. If substandard work is turned in toward the end of the quarter, all group members will earn a course grade of F.

Your course grade will also be affected by homework, the contents of your journal,  exams, weekly status reports, your 2 minute talks as follows:

• All homework must be completed satisfactorily to pass the course; homework is an individual assignment.
• A satisfactory journal must be completed to pass the course; your journal may be checked and graded regularly. Missing entries mean that the work is not done (it is not done until it is documented in a rational manner.)
• Each missed or unsatisfactory status report will lower your course grade one grade. (e.g. A to A-)
• 2 minute talks are graded pass/fail. Each failed or missed talk will lower your course grade one grade. You can make up one failure by giving another talk at a later time. Reasons to earn an F on a two minute talk:

  Use of notes or slides without prior permission.
  Use of the words "basically" or "like" (or other words of equivocation).
  Insufficient content or substance (teach the class something useful or interesting!)
  

You will be assigned a required laboratory meeting each week; each missed laboratory, without prior notification, will lower your course grade 3 grades. (e.g. A to B)

Late Work Policies
A software engineer has a responsibility to manage time effectively and turn in work on time. Deadlines are rarely absolute; if you are having a problem, discuss it well in advance; this advice applies to the workplace as well as any college class.

For CSC 308, the following nominal late policies apply:

• Homework
  Homework may be occasionally assigned. It must be turned in on the due date or you will receive a course grade of F. Unacceptable homework may be returned for resubmittal until it receives a passing grade. The first resubmittal may be turned in, without penalty, one week after it is returned. Failure to resubmit work on time or subsequent resubmittals will be penalized one grade per week or partial week.
• Status reports
  A missing status report will cost you one course grade; late status reports are not accepted.
• Reading questions
  Missed reading questions will cost you one course grade. If your reading questions receive a failing grade, you may resubmit them, without penalty, up to a week later. After a week, each unacceptable or late reading question will be penalized one grade per week.
• Project deadlines
  Project deliverables must be turned in on time, even if incomplete. If a significant part of a deliverable is missing, the individual responsible will be penalized 3 grades (e.g. A to B). Deliverables with a failing grade may be resubmitted, without penalty, up to one week later. Failure to resubmit work or subsequent resubmittals will be penalized one grade per week or partial week.
  Note: depending on circumstances, project deliverable penalties are assessed on an individual or group basis. If your group has a non-performer, turn in your deliverables on-time with an accurate credits section. The identity of the non-performer will be crystal clear.

Plagiarism
All work submitted is to be your own. Cooperative study and mutual aid are healthy learning methods and are strongly encouraged. You are especially encouraged to work with other groups.  Just cite sources of anything you have copied, summarized or discussed directly with another.  It is cheating to copy someone's work or allow someone to copy your work. It is cheating to copy material from a publication without giving credit. Plagiarism will result in a course grade of F.  When you find good ideas by other people, the best policy is to summarize other work in your own words and cite their work as the source for the principle you state.  Citing resources is not a sign of weakness of your own ideas, it is a sign that you can do research and build on others' work.

Communication
The best place to discuss the course is during lecture and laboratory times. Email is a poor substitute for direct communication and may not always be reliable. I do expect every student to obtain a Cal Poly email account; all email will be addressed to that account. Note also that email is not very reliable for contacting the instructor.  If you use an address not in the calpoly.edu domain, my spam filter may eliminate your message.  Please use very clear subject lines like "CSC 308."

All homework and project assignments will be placed on the Web and announced in lecture. Most class materials are available on the Web; be sure to check them regularly.

1. Job Assignments
   Each person must have an assigned job in each phase. See the job list to ensure that you meet this requirement.

2. Group Name and Logo
   It is important for each group to have an identity; part of that identity is established by having a name and logo. Both must be clearly visible on everything handed in by the group.

3. Group Meetings
   Each group meeting must be documented with a written meeting report . Handwritten reports on the form are acceptable. Meeting notes should be turned in each week at your group meeting. These meeting reports are especially important for those groups that experience difficulty completing the project.  Some member of the group will be tasked to scribe the report and archive them. 
   

4. Deliverables
   Every deliverable must be professionally done; assume you are working for a corporation and are turning in something to your boss. Some specific requirements are:
   
   • English structure, grammar and spelling must be of professional quality.
   • The group logo, section # and current date must be on the front page.
   • Write a credits page; who is responsible for each part of the deliverable?
   • Pages must be numbered.
   • Printing must be of high quality.

5. Status Reports
   Almost all managers require some kind of periodic status report. In this company, status reports are due, in your journal, at your assigned laboratory meeting. Status reports will be primarily graded on the quality of the writing and adherence to format; the grade can drastically affect your course grade (see grading).

6. Laboratory Meeting
   Your group will be assigned one laboratory period each week to meet with the boss. Attendance at this meeting is mandatory! Bring all current group work even if it is in draft form. In addition, each individual must bring her journal to each class and laboratory period.

7. Bad Words
   Don't use bad words in any context.  Please pay attention to this, generally do not use words of equivocation and ambiguity.  IF a sentence carries the same meaning (or becomes clearer) without an extra word or clause - leave it out!
   

8. Journal Review Due Dates
   Journal deliverables (e.g. status reports, readings) are due at the beginning of your group's first lab period after the assigned due date.