Fall 2017 - CMPT 373 D100

Software Development Methods (3)

Class Number: 7661

Delivery Method: In Person


  • Course Times + Location:

    Mo, We, Fr 2:30 PM – 3:20 PM
    SUR 5100, Surrey

  • Exam Times + Location:

    Dec 11, 2017
    3:30 PM – 6:30 PM
    SUR 3310, Surrey

  • Instructor:

    Brian Fraser
    1 778 782-8112
    Office: SUR 4112
  • Prerequisites:

    CMPT 213 and (CMPT 276 or 275).



Survey of modern software development methodology. Several software development process models will be examined, as will the general principles behind such models. Provides experience with different programming paradigms and their advantages and disadvantages during software development.


This course exposes students to modern software development practices. Several software best practices will be introduced. Students will gain experience with different programming methodologies and their advantages and disadvantages during software development. The course is principally a laboratory course, with lectures, discussions, and project homework to supplement the laboratory work. Students will work in groups of roughly eight individuals on common projects, with groups assigned by the instructor. Each project will come with some specification of implementation language (generally Java or C++), development platform (such as Linux), and other technologies (such as BOOST, MySQL, or OpenGL). Students should be prepared to promptly learn new aspects of the project so they can contribute quickly (such as web or UI programming).

The weekly laboratory times are for mandatory project group meetings, including meetings and code reviews with the instructor. The primary goal of the laboratory work is to correctly follow and understand the development practices for the project; students are marked individually depending on their adherence to the model and contribution to the project. Projects will consist of multiple iterations and students will make weekly contributions. Students should expect to participate in class discussions and to give an informal presentation regarding their project or assigned specialty.


- Best practices: design patterns, refactoring, language-specific issues
- Agile software development: such as Scrum, extreme programming, test-driven development
- Managing complexity and designing maintainable software
- Software-engineering tools and environments
- Software development process models: component-based development, iterative processes
- Requirements gathering and teamwork


  • Project 50%
  • Reading responses 20%
  • Exercises and in-class activities/quizzes 30%
  • To be confirmed in the first week of classes.



Reference Book:
Clean Code, Robert C Martin, Prentice Hall, 2009, 9780132350884


Code Complete, 2nd Edition, Steve McConnell, Microsoft Press, 2004
Required readings assigned from this book.
ISBN: 9780735619678

Registrar Notes:

SFU’s Academic Integrity web site http://students.sfu.ca/academicintegrity.html is filled with information on what is meant by academic dishonesty, where you can find resources to help with your studies and the consequences of cheating.  Check out the site for more information and videos that help explain the issues in plain English.

Each student is responsible for his or her conduct as it affects the University community.  Academic dishonesty, in whatever form, is ultimately destructive of the values of the University. Furthermore, it is unfair and discouraging to the majority of students who pursue their studies honestly. Scholarly integrity is required of all members of the University. http://www.sfu.ca/policies/gazette/student/s10-01.html