COMP 380

Team Project #2

Due: 10/29 (TTH) or 10/30 (MW)

As a team effort develop two high-level design diagrams for the problem of Project #1. Although if this were a real project, you would ordinarily only pick one of these to produce, please create both a procedurally oriented structure chart and an object oriented (UML) class diagram. The purposes of this project are to both understand how to create an architectural design for a software problem and to understand the differences between traditional, procedural methods and an object-oriented approach.

The DFDs (Data Flow Diagrams) created in Project #1 should serve as the basis for the structure chart, and the ERDs (Entity Relationship Diagrams) should provide the basis for the UML class diagrams.

In a real design effort after producing one of the above models of the system, you would provide high-level descriptions of each of the operational modules (functions or methods) identified in the diagrams created. These descriptions would outline how each module works and specify precisely how each interfaces to other modules of the system. For this project, create such descriptions for the module that approves, or verifies the acceptability of, a student’s proposal for a concentrated studies package (or set of electives required by the major) and for all of the functions or methods that this module communicates with (i.e., invokes or sends messages to).

Each high-level description should contain the following:

· A processing narrative (explanation of what the module does including a list of all other modules called)

· An interface description (a precise description of the input and output parameters, that is, the information received by and returned from the module, including everything needed by other modules in order to communicate with it, e.g., the types of the inputs and outputs)

· Descriptions of any global data items or structures used

· Identification of files (databases) accessed or changed

· Description of any error messages produced

· Description of any design restrictions or limitations.