Semester Project expand

Project Milestones

Click here for case description, example project, tools and tutorials, and submission details.


(Click on any item in the table below to see a description.)

Project Deliverable Schedule
Deliverable Due Date
Project posted 01/22
See the link for "Case: Description of Current System" above.
Team selection 01/22
Teams will consist of four students. Since individuals are best at determining those whose schedules and personalities meshes best with yours, students will arrange their own teams. Be sure to seek out teammates with similar goals and work ethics. For example, ask if the potential team members are willing to work hard for an A or are more than happy to settle for a C. Having similar goals and willingness to work make a huge difference in whether the team is compatible! Be sure to also take into account class load, work schedule, and whethere team members live in the same city (if it impacts availability).
Deliverable 1: Functional Decomposition 01/29
Using the description of the current system as a basis, provide results of the following steps:

Steps:

  1. Develop a functional decomposition of the current system.
    • Include a listing of all business functions.
  2. Next, consolidate (or group) the business functions.

Refer to the example in the notes: link.

  • The example first shows a list of all the functions, and then shows the grouping.

Your deliverable will consist of the results from both steps. Be sure to label each step clearly.

Deliverable 2: Current Logical DFD 02/07
Develop the DFD for the current logical system. You should provide
  • Context Diagram
  • Level 0 diagram
  • Level 1 diagram for every process shown on Level 0 diagram
  • Level 2 diagram when needed, but decompose at least one of the processes that appears on one of the Level 1 diagrams
  • textual descriptions of low level processes
Deliverable 3: Partial Physical DFD 02/12
Provide a physical DFD for the following subsystems in the current system.
  • Return Defective/Unwanted Equipment
  • Maintain Inventory
Deliverable 4: Partial Data Dictionary 02/16
Provide a partial version of the data dictionary that includes the following:
  • 3 Data Flows:
    • Payment Type
    • Equipment Information
    • Purchase Agreement
  • 3 Data Elements:
    • Reason for Return
    • Equipment Type
    • Serial Number
  • 3 Data Stores:
    • Inventory File
    • Customer File
    • Sales History File
  • 1 Data Structure:
    • Returned Equipment Information
Deliverable 5: Partial System Structure Chart 02/21
Provide a structure chart for the following subsystems in the current system.
  • Return Defective/Unwanted Equipment
  • Maintain Inventory

Be sure to show couples and flags.

Deliverable 6: Process Specifications 02/26
Process Specifications

For the complete requirement, visit process specification details.

  • Provide process specifications for a minimum of ten functional primitives.
  • Select from Structured English, Decision Tables, or Decision Trees.
    • Provide each of the following for the expanded Customer Returns Defective/Unwanted Equipment process:
      • A process specification in the form of a Decision Tree
      • A process specification in the form of a Decision Table
      • A process specification in the form of a Structured English
  • Recall that process specifications are the same as process descriptions, mini-specs, transform descriptions, document procedures.
Peer Evaluation Form (trial run) 03/01
Evaluate each of your team members. This is an early warning so that perceived slackers have an opportunity to modify their behavior. (link)
  • If you plan on giving everyone in your team the same scores, fill out one form for the overall team, but list each name in the Team Member field.
Deliverable 7a: Future Logical System (functional decomposition) 03/05
Functional decomposition of future system (decomposition and grouping of processes)
  • Include a summary of all business functions.
  • Include the consolidation (grouping) of business functions.
Deliverable 7b: Future Logical System (DFD) 03/12
Develop the DFD for the future logical system.
  • Your future logical DFD should include and expand upon the current logical DFD.
  • Expand or decompose your DFD down as many levels as your functional analysis requires.
    • Multiple processes must be taken as far as Level 2.
      • Rule of thumb: Stop when you can explain the process in one to two sentences.
  • Provide textual descriptions of low level processes.
Deliverable 8a: Use Case Diagrams 03/26
Provide use case diagrams for the following subsystems in the future system.
  • Return Defective/Unwanted Equipment
  • Maintain Inventory
Deliverable 8b: Use Case Descriptions 03/28
Provide textual use case descriptions (at the (Kite Level) for the following subsystems in the future system.
  • Return Defective/Unwanted Equipment
  • Maintain Inventory
Deliverable 9: Activity Diagram 04/02
Provide activity diagrams (example) for the "Return Equipment" and "Maintain Inventory" (aka Fulfillment) subsystems in the future system.
Deliverable 10 UML Class Diagram* 04/04
Provide a UML class diagram of the complete future system. "Three compartment" design is not required. In other words, do not be concerned about attributes and behaviors.

Be sure, however, to show multiplicity for each relationship and note any generalization relationships.
Finalized Project (see Technical Report Format) 04/19
Completed website and digital copy are due today.
Create a folder in your classweb account called "finalProject". Upload the following:
  • High-quality PDF version of report.
  • A note (doc or txt) providing me with the URL or index.htm location of the main page of your web site version of the project. A shortcut will also serve this purpose.
  • Zip file containing files for the two items above (redundancy for safety).
Be sure to submit your peer evaluations ASAP.
Peer Evaluation Form 04/23
Evaluate each of your team members. This is your final assessment of each team member's contributions. (link)
  • If you plan on giving everyone in your team the same scores, fill out one form for the overall team, but list each name in the Team Member field.


Case

Current System

Future System

Examples

Example Case

Website

Example Technical Report

Diagramming Tools

LucidChart (DFD Design Tool – via Google)

LucidChart (DFD Design Tool – via LucidChart)

Draw.IO (an alternative DFD design tool)

Shapes for Draw.IO

Website Tools and Tutorials

Create Classweb Account

Image Map tutorial (for DFDs)

Popup tutorial (for functional primitives)

Web Design Notes

Submission

Technical Report Format

Example Technical Report

Submission checklist:

  • High-quality PDF version of report
  • Web site version of report with clickable parent processes on each level of the DFD that link to child processes (or primitive descriptions), allowing easy traversal of DFD
  • Zip file containing files for the two items above (redundancy for safety)
  • Peer evaluations submitted individually by and for each team member

Project Assessment Sheet

 
X
use Case
X
kite level use Case
X
activityDiagram