MCS 850 - Software Engineering
Module Supplement

Ensure you have all of the "standard" material: MCS 850 Module, and the 4 required texts.

UNIT IV  Application

"Engineering Option"

One common approach for the "application" unit is to create a software product following a software project development methodology.

Evidence of a successful project is from project documentation as well as the final product.

Refer to the section "Methods for Software Engineering" in your text for one possible outline.

In general, I expect the following phases to be completed and the following items produced:

0. Laboratory Notebook
    Keep a log of all your activity on the project in a laborartory notebook.

1. Requirements Phase
    The problem to be solved is identified
    The client's needs (as opposed to wants) are determined

    A Rapid Prototype is created
    Requirements Document is created

2. Specifications Phase
    Determine what the product is to do (not how it is to do it).
    Analysis of the problem is performed
    Specifications are the contract between client and developer

    Specification Document is created which explicitly describes the functionality of the product.

3. Design Phase
    Determine how the product (software) will solve the problem
    System or Architectural design involves "high-level" issues
    Detailed or Module design involves "low-level" issues

    A User's Manual is created
    Design Documentation is created outlining the choice of: algorithms, data structures, etc

4. Implementation Phase
    The software product is created

    Source Code, following Professional Programming Practice, is created
    Product Test Plans (both Black Box and White Box) are created and executed