Instructor | Announcements | Course Info | Class Material | Schedule | Project | Grade | General Policy | Related Links


CmpE 203
Software Engineering Management
Fall 2011
College of Engineering




Richard Sinn
Office Hours: After class, by appointment or email only

Richard is currently a Senior Security Architect/Principal Architect at eBay. He looks over various security architecture projects for all of eBay. Before eBay, he was the Security Architect at various business units (Real Time Communication group, Yahoo Community, Yahoo Communications) at Yahoo from 2005 to 2011. Prior to Yahoo, he held various senior positions at IBM, Oracle and different Silicon Valley startup companies. Richard is an inventor and has filed over sixteen invention disclosures (patents). He is also a frequent writer for various magazines and journals, and a frequent speaker at regional and national technology conferences. As a scholar and supporter for academia, he has been teaching in the Computer Engineering and Computer Science departments at San Jose State University since 1998. He also served as Adjunct Professor at the University of Minnesota.



Check back every now and then for updates.


Students who do not provide documentation of having satisfied the class prerequisite and co-requisite requirements (if any) by the second class meeting will be dropped from the class.

New Prereq check procedure

We will adopt a new procedure (akin to that used by some of the other engineering departments):
At the beginning of the term, have all the students in the class provide a copy of their transcripts, with the prerequisite class grade highlighted. The instructor will then check off against the roster, and drop any and all students who do not provide such proof of having completed the prerequisite with a satisfactory grade.
For classes with co-requisite requirements (such as CMPE 110), the student will provide the transcript (proving that the class has already been passed) or a printout from MySJSU (proving that the student is currently enrolled).
Add the following to the class greensheet: ”Students who do not provide documentation of having satisfied the class prerequisite and co-requisite requirements (if any) by the second class meeting will be dropped from the class.



Bring a computer to class. You will need that for lecture / lab assignment.

Class schedule is under:



Add permission code

Old procedure below. Come to class and check out what is the new add procedure.

Students asking for permission codes should complete the request form available on the department wiki at <>.

The instructor collects thee forms on the first day of classes and passes them all to Lee Chang (who will serve as a clearinghouse). Print your own or More forms will be available in the department office.

No Open university student add in general.


Honesty Pledge can be downloaded here.


Class time:

Every Wednesday at 6:30pm

Class room:

ENG 343




Course Information


Development of software systems from the perspective of project management within the dynamic and complex nature of software technologies and environments; development lifecycle, communications, team dynamics, planning, estimation, scheduling, risk analysis, metrics tracking, problem management, and configuration management. Prerequisite: Classified graduate standing or graduate advisor consent



Apart from big term project(s) and presentation, there are homework assignments, a mid-term exam and a final exam. Some exams might be take-home. The weightings for grading are: Term Project(s) 30%, Homework 20%, Midterm 15%, Final Exam 15%, Team Presentation 10% and Lecture/Lab assignments 10%.

No Late Assignment Submission. Put everything in an envelop when submit any material.




Policy Info

Academic Dishonesty

This is just a reminder that ALL cases of academic dishonesty (plagiarism, cheating, etc) should be reported to the chair.

In order be fair to the students we have to maintain a uniform process for handling such cases - there really is no faculty discretion once a case of plagiarism or cheating has been discovered - ALL cases will be reported.

The most relevant Senate policy w.r.t this is S07-2. The policy defines academic dishonesty as follows (please note the very low tolerance definition of plagiarism):

San José State University defines cheating as the act of obtaining or attempting to obtain credit for academic work through the use of any dishonest, deceptive, or fraudulent means. Cheating includes:

1.1.1. Copying, in part or in whole, from another’s test or other evaluation instrument including homework assignments, worksheets, lab reports, essays, summaries, quizzes, etc.;

1.1.2. Submitting work previously graded in another course without prior approval by the course instructor or by departmental policy;

1.1.3. Submitting work simultaneously presented in two courses without prior approval by both course instructors or by the department policies of both departments;

1.1.4. Using or consulting sources, tools or materials prohibited by the instructor prior to, or during an examination;

1.1.5. Altering or interfering with the grading process;

1.1.6. Sitting for an examination by a surrogate, or as a surrogate;

1.1.7. Any other act committed by a student in the course of their academic work that defrauds or misrepresents, including aiding others in any of the actions defined above.

San José State University defines plagiarism as the act of representing the work of another as one's own without giving appropriate credit, regardless of how that work was obtained, and submitting it to fulfill academic requirements.

Plagiarism includes:

1.2.1 Knowingly or unknowingly incorporating the ideas, words, sentences, paragraphs, or parts of, or the specific substance of another's work, without giving appropriate credit, and representing the product as one's own work;

1.2.2 Representing another’s artistic/scholarly works such as musical compositions, computer programs, photographs, paintings, drawing, sculptures, or similar works as one's own.




Class Material

Lecture Notes

Required Textbooks:



Core Reference:






Software Engineering Overview

Aug 24, 2011 - Wed


Aug 31, 2011 - Wed


Sept 6, 2011 - Tue - Last Day to Drop Courses without a D


Sept 7, 2011 - Wed


Sept 13, 2011 - Tue - Last Day to Add Courses & Register Late


Sept 14, 2011 - Wed


Sept 21, 2011 - Wed


Case Study

Sept 28, 2011 - Wed

  • Case Study: Software Engineering Management
  • Technical Communication
  • Planning and scheduling
  • Reading: ch 11, 12
  • Lab: Govwork Analysis
  • Homework 2 Due



Quality Management

Oct 5, 2011 - Wed


Oct 12, 2011 - Wed


Oct 19, 2011 - Wed


Oct 26, 2011 - Wed

Project Management


Nov 2, 2011 - Wed

  • Guest Speaker - QA Management
  • Reading: ch 24 - 26


Nov 9, 2011 - Wed



Nov 16, 2011 - Wed


Nov 23, 2011 - Wed

  • Thanksgiving - NO CLASS


Nov 30, 2011 - Wed

Semester Presentation


Dec 7, 2011 - Wed

  • Study Day
  • No Class
  • Extra Credit Homework assigned Due Dec 9
  • Make sure you read all the assigned chapters before the exam.


Dec 14, 2011 - Wed - Final Exam

  • Final:
Cmpe 203 Final
Dec 14, 2011 (Wednesday)
Time: 6:30pm
Room: ENG 343
Time limit: 1 hour 15 min

Comprehensive, covering all topics.

Check grade at my.sjsu around the end of year. Grade will be only given over there (no email).

Open book and notes. No computer and Internet connection.

Reference Chapters:

  • The Goals and Terminology of Software Engineering (Chapter 1)
  • Introduction to Quality and Metrics in Software Engineering (Chapter 2)
  • Software Process (Chapter 3)
  • Agile Software Processes (Chapter 4)
  • Quality in the Software Process (Chapter 5)
  • Software Configuration Management (Chapter 6)
  • Principles of Software Project Management I: Organization, Tools, and Risk Management (Chapter 7)
  • Principles of Software Project Management II: Estimation, Scheduling, and Planning (Chapter 8)
  • Quality and Metrics in Project Management (Chapter 9)
  • Principles of Requirements Analysis (Chapter 10)
  • Analyzing High-Level Requirements (Chapter 11)
  • Analyzing Detailed Requirements (Chapter 12)
  • Quality and Metrics in Requirements Analysis (Chapter 13)
  • Online Chapter - Formal and Emerging Methods (Chapter 14)
  • Principles of Software Design (Chapter 15)
  • The Unified Modeling Language (Chapter 16)
  • Software Design Patterns (Chapter 17)
  • Software Architecture (Chapter 18)
  • Detailed Design (Chapter 19)
  • Design Quality and Metrics (Chapter 20)
  • Online Chapter - Advanced and Emerging Methods in Software Design (Chapter 21)
  • Principles of Implementation (Chapter 22)
  • Quality and Metrics in Implementation (Chapter 23)
  • Refactoring (Chapter 24)
  • Introduction to Software Testing (Chapter 25)
  • Software Maintenance (Chapter 29)





Term Project

Please refer to the project document.



Email to check your grade if necessary.


General Policy

The university and departmental policies and deadlines for course drop will be applied. Makeup exams cannot be offered, except under exceptional conditions, such as documented serious illness/accident, etc., and only at the professor's discretion.

Each student is responsible for his/her individual assignment, and must not copy anyone else's work. Students who borrow solutions from others will find themselves unable to pass the course. The minimum penalty for every student involved in the duplication of individual assignments or exams will be receiving a zero score on the submitted work.

For group project, all the work has to be done by your OWN group. Do not try to download "free code" from the Internet and hand in as a project. WE WILL FIND OUT. Do not share your work with others. So DO YOUR OWN WORK and EARN your grade.


Related Links



Instructor | Announcements | Course Info | Class Material | Schedule | Project | Grade | General Policy | Related Links