Software Design

The focus of this week is to design the software to be developed for the RWP. This is based upon the WBS developed last week.

UI – the deliverable for each teams User Interface will be a site map. This is typically a diagram that provides a tree-like structure showing the individual pages of the UI and the path that will be taken to reach each page. The intent is to illustrate the complexity of the site. Make sure each page has a unique name/title that adequately summarizes the purpose of each page.

Interfaces to legacy or Commercial Off the Shelf Software (COTS) - The deliverable will be a diagram that illustrates the expected Input/Output that will be provided either to or from the external tools.

Database – the deliverable will be a set of tables representing the schema of the database tables, fields, keys, etc. Another deliverable may be an Entity Relationship Diagram (ERD).

Algorithms – These are the back-end processes that make the magic happen. Each process must have a unique name that adequately summarizes its purpose. The most common form for ease of explanation is likely to be an old-fashioned logical flow chart. UML diagrams may also be used. Be sure to show the start and stop states, and identify the I/O.

Your best guidance is to view the efforts of previous teams in previous semesters.