CSCI 441: Software Engineering


Software Engineering Project Report Guidelines

    (1) PROJECT PROPOSAL

    Each project team will submit a detailed project proposal - which describes the overall overview of the intended project work.
    A descriptive guideline on writing a comprehensive proposal is found here: Project Proposal

    (2) REPORTS

    Sample Projects and Reports

    Note: Examples of software engineering projects and reports are available here.
    These curated projects give overview on how to write and develop a software engineering project. The projects and reports are available here.


    The overall report shall consists of three different reports:
          1.   Report #1: System Specification — Iteration 1 (a & b)
          2.   Report #2: System Design — Iteration 2 (a & b)
          3.   Report #3: (all previous sections from Report #2 included — and updated with relevant revisions and new content)

    Report #1: System Specification — Iteration 1 (a & b)
    This report shall be submitted in three steps:
          1.   Part 1 (Section 1: Customer Problem Statement  and   Section 2: Goals, Requirements, and Analysis)
          2.   Part 2 (Section 3: Use Cases  and  Section 4: User Interface Specification )
          3.   Entire Report #1  (all sections included)

    Report #1

    Report #2: System Design -- Iteration 2 (a & b)
    This report shall be submitted in three steps:
          1.   Part 1 (Section 5: Analysis and Domain Modeling)
          2.   Part 2 (Section 6: Interaction Diagrams and Section 7: Class Diagram)
          3.   Entire Report #2  (all sections included)

    Report #2

    Report #3: Specification & Design -- Iteration 3 (Revised and Collated)  

    Report #3

    Project Presentations/Demonstrations
    There will be project demonstrations/presentations on specific dates within the project work lifecycle:

          1.  Demo #1

          2.  Demo #2

    Project e-Archive Submission
    Student project team will submit their e-archive files to a cloud repository. Do not email your eArchive as an attachment because the mail server as the file maybe too large to upload or the mail server will discard it as a possible virus. You may read the guidelines on the final project e-archive submission here:

          1.  Project e-Archive

    OTHER COURSE CONTENT
    We'll study other course materials for effective software engineering practices:

    Software Evolution

    Systems Dependability and Security:

          1.  Dependable Systems

          2.  Reliability Engineering

          3.  Safety Engineering

    Mike Mireku Kwakye
    Wed Apr 03 12:14:16 EDT 2024