Simon Fraser University
Engaging the World

Course Outlines

Spring 2019 - CMPT 475 E100

Requirements Engineering (3)

Class Number: 6536

Delivery Method: In Person

Overview

  • Course Times + Location:

    Jan 3 – Apr 8, 2019: Wed, 5:30–8:20 p.m.
    Burnaby

  • Exam Times + Location:

    Apr 10, 2019
    Wed, 7:00–10:00 p.m.
    Burnaby

  • Prerequisites:

    CMPT 275 or 276, MACM 201 and 15 units of upper division courses. Recommended: co-op experience.

Description

CALENDAR DESCRIPTION:

Software succeeds when it is well-matched to its intended purpose. Requirements engineering is the process of discovering that purpose by making requirements explicit and documenting them in a form amenable to analysis, reasoning, and validation, establishing the key attributes of a system prior to its construction. Students will learn methodical approaches to requirements analysis and design specification in early systems development phases, along with best practices and common principles to cope with notoriously changing requirements.

COURSE DETAILS:

Software requirements involve both design and understanding of what is needed by the application. This is a creative activity that calls for abstract models to analytically analyze and to reason out requirements. Design decisions and conformance criteria, making sure these are well understood prior to coding. Starting with software requirement analysis methodologies, abstraction principles and specification paradigms. Students will learn how to use modeling as an effective instrument for making software systems more reliable, the requirements gathering process more predictable, and overall improve the quality of the resulting product. Students will evaluate contrasting methodologies and how to ensure high quality requirements be provided to the development stage of software engineering process.

Topics

  • Requirements position in the Software Development Lifecycle (SDLC)
  • Scoping
  • Methods for requirements analysis
  • Design Models
  • Functional and Non-Functional Requirements
  • Risk Identification and Management
  • Requirements Management
  • Completeness and Consistency checking
  • Formal Specifications
  • Importance of User Community to Requirements Engineering

Grading

NOTES:

Assignments/project 50% midterm 20% final 30%

Students must attain an overall passing grade on the weighted average of exams in the course in order to obtain a clear pass (C- or better).

Materials

MATERIALS + SUPPLIES:

  • Software Engineering, 10th Edition, Ian Sommerville, Addison-Wesley, 2015, 9780133943030, General reference to basic software engineering principles
  • Facts and Fallacies of Software Engineering, Robert L. Glass, Addison-Wesley, 2003, 9780321117427
  • The Logic of Failure, Dietrich Dorne, Basic Book, 1996, 9780201479485
  • Code Complete, Steve McConnell, Microsoft Press, 2004, 9780735619678
  • Managing Software Requirments A Use Case Approach 2nd Edition, Dean Leffingwell Don Widrig, addison wesley, 2003, 9780321122476

REQUIRED READING:

Software Requirements 3rd edition
Karl Wiegers
Microsoft press
2014
ISBN: 9780735679665

Registrar Notes:

SFU’s Academic Integrity web site http://www.sfu.ca/students/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

ACADEMIC INTEGRITY: YOUR WORK, YOUR SUCCESS