Design Document

It's now time for you to represent the design of your G1 project based on the requirements you created. You are not required to reverse engineer the system to determine its current design. Based on your current understanding of the system, along with your requirements, represent the design using one (or more) of the architecture styles discussed in the lecture. You are the software architect / technical lead.

Your document should be in Word or PDF file format and filename should be as follows:

Team_Design.

(Note: This assignment will not require you to create UML diagrams. You are simply required to identify a high-

level architecture and explain each of component. You will create UML diagrams in CSS 370.)

Your task is to create a design document that contains the following:

1. Project team: List the names of each member of the group.

2. Introduction

• Purpose of the design document

• Project title

• What is the product?

• What type of software is this? Refer to the Lecture on Software Topics.

2 Who are the product's customers? (0.5 pt) Who are the users? (0.5 pt)

Who created it (i.e. who is the organization funding this project)? (0.5 pt)

Architecture

Based on your current understanding of the system, explain the main architectural

style/pattern(s) used by your project. (Note: it is OK to combine architecture

styles.) Explain your selection? How does it fit your project? (5 pts) What are the

alternatives? (2 pts) Explain why you did not choose those alternatives (5 pts).

Draw the high-level architecture. Make sure the direction of the arrows follows

the architecture style as explained in lecture. (5 pts)

•

• What non-functional requirements does this style satisfy (include IDs)? (1.5 pts).

Are there non-functional requirements that you are not able to satisfy (include IDs)?

Explain (1.5 pts)

3 Module Design (10)

For each module you drew in item #2, provide the following:

Labels on modules correspond to your project and the purpose (i.e., you will lose

points if you simply copy labels on lecture). (2 pts)

The purpose of the module: State the generic purpose of the module (e.g., see

figure below). (Appropriate items to address here include such topics as: What secret

does this module hide? Does the module represent a specific data type or data format?)

(5 pts)

Functional requirement this module satisfies (2 pts). Make sure you specify the

user story ID from your G3 (1 pt).

Credits: S Hendrickson & RN Taylor