[ Project ] - Radford



[pic]

[pic]

Software Design Document

Andrew Doyle

Chad Sloan

Stephanie Shaver

Ethan Bowyer

Software Engineering I

radford.edu/~team14

April 07, 2011

[pic]

Revisions

|Version |Primary Author(s) |Description of Version |Date Completed |

|Final Draft #1 |Andrew Doyle |Completed all the sections |04/06/2011 |

| |Ethan Bowyer | | |

| |Chad Sloan | | |

| |Stephanie Shaver | | |

|Review & Approval |

Requirements Document Approval History

|Approving Party |Version Approved |Signature |Date |

|Andrew Doyle |1 | |04/07/2011 |

|Dr. T. L. Lewis | | | |

Requirements Document Review History

|Reviewer |Version Reviewed |Signature |Date |

|Ethan Bowyer |1 | |04/07/2011 |

|Chad Sloan |1 | |04/07/2011 |

|Stephanie Shaver |1 | |04/07/2011 |

Contents

1 Contents ii

2 Introduction 1

2.1 System Overview 1

2.2 Supporting Materials 1

2.3 Definitions and Acronyms 1

3 Functional Requirements Mapping Overview 2

4 High Level Design 4

4.1 Conceptual View (Architectural Context Model) 4

5 Low Level Design 5

5.1 Process Model 5

6 User Interface Design 6

6.1 Application Control 6

6.2 Screen 1..n 6

7 Final Schedule 15

8 Final Budget 16

Introduction

1 System Overview

We will develop a content management system for the Sports Club Council that can be accessed via the World Wide Web. Certain individuals (referred to as users) in the Sports Club Council will be able to use their Radford user name and password to log into the system. Users will be able to use an interactive calendar to post the dates of upcoming sports events. They may also post articles about sporting events that first be submitted to the administrator; with the approval of the administrator the article will then be shown publicly. The main page will also allow users to post short messages about recent news, such as the score of a recently finished game. Users may also submit pictures which will be grouped with their respective sports.

The system will also include a list of the clubs that are in the Sports Club Council, along with links to each individual clubs respective web sites. It will also include the names and contact information of all officers within the Sports Club Council, as well as the names and contact information of each of the officers in the various clubs that make up the Sports Club Council. Various forms used by the Sports Club Council will also be stored in the content management system, such as the Sports Club Handbook and the Fundraiser forms.

2 Supporting Materials

Microsoft Visio

Microsoft Project

3 Definitions and Acronyms

Joomla! - Content Management System that we are using to develop the website for our client.

JEvents – Joomla! Plugin / Component that manages calendar events.

Phoca Gallery – Joomla! Plugin / Component that manages pictures and picture albums.

Functional Requirements Mapping Overview

|Functional Requirement |Design Artifact |

|1: User Login : The user shall be able to login into the |(Figure 6.2.1) |

|system. |Login section on the main page |

|2: Administrator Backend Login: The Administrator shall be |(Figure 6.2.2) |

|able to login to the system from the backend. |Joomla! Administration Page |

|3: Club Registration: An Administrator shall be able to |(Figure 6.2.6) |

|register a club with the system. |Joomla! Backend , User Registration |

|4: Password Recovery: The system shall be able to give a user |(Figure 6.2.3) |

|their password when requested by that user. |Login section on the main page |

|5: User Logout: The user shall be able to logout of the system|(Figure 6.2.4) |

| |Login section on the main page |

|6: Delete Clubs: The administrator shall be able to delete |(Figure 6.2.6) |

|clubs from the system. |Joomla! backend, User Registration |

|7: Create Album: All users shall be able to create an album to|(Figure 6.2.16) |

|store pictures in. |Joomla! Backend, Components, Phoca Gallery, Categories |

|8: Create Calendar Event: The user shall be able to create |(Figure 6.2.7) |

|events in the calendar. |JEvents Calendar, JEvents Calendar |

|9: Add Photo: The user shall be able to add photos to a |(Figure 6.2.19) |

|specified album. |Photo Gallery, Albums |

|10: Delete Photo: The administrator shall be able to delete |(Figure 6.2.20) |

|photos from an album. |Photo Gallery, Albums |

|11: Add Post: A user shall be able to add a post about what is|(Figure 6.2.10) |

|currently going on at an event for all other users to see. |Add Post on the main page |

| | |

|12: Delete Post: An administrator shall be able to delete a |(Figure 6.2.12) |

|post that has been added to the news feed. |Joomla! Backend, Article Manager, |

|13: Add Article: A user shall be able to add an article to the|(Figure6.2.13) |

|website after logging in. |Main Page, Add Article |

|14: Delete Article: An administrator shall be able to remove |(Figure 6.2.15) |

|an article they have uploaded. |Joomla! Backend, Article Manager |

|15: Administrator Backend Logout: The Administrator shall be |(Figure 6.2.5) |

|able to logout of the backend of the system. |Joomla! Backend |

|16: Modify Article: A user shall be able to modify their |(Figure 6.2.14) |

|uploaded article. |Joomla! Backend, Article Manager |

|17: Modify Post: A user shall be able to modify a post that |(Figure 6.2.11) |

|they have added to the news feed. |Edit Post on the main page |

|18: Delete Calendar Event: The administrator shall be able to |(Figure 6.2.9) |

|delete events from the calendar. |Joomla! Backend, Components, JEvents, Manage Events |

|19: Modify Calendar Event: The user shall be able to modify |(Figure 6.2.8) |

|events in the calendar. |Edit Event on the JEvents Calendar Page |

|20: Modify Album: All users shall be able to modify an album |(Figure 6.2.17) |

|to store pictures in. |Joomla! Backend, Components, Phoca Gallery, Categories |

|21: Delete Album: The administrator shall be able to delete an|(Figure 6.2.18) |

|album to store pictures in. |Joomla! Backend, Components, Phoca Gallery, Categories |

High Level Design

1 Conceptual View (Architectural Context Model)

[pic]

Low Level Design

1 Process Model

[pic]

User Interface Design

1 Application Control

There will be a navigation bar at the top center of every page as well as a main menu bar on the left side of the page. In addition, there will be links to the photo gallery and the calendar below the main menu. Finally, once the user has logged in there will be a user menu on every page containing personal details and logout. We are also implementing the Radford University color scheme (primarily red and white).

2 Screen 1..n

Figure 6.2.1: User Login

[pic]

Figure 6.2.2: Administrator Backend Login

[pic]

Figure 6.2.3 (Password Recovery)

[pic]

Figure 6.2.4 (User Logout)

[pic]

Figure 6.2.5 (Administrator Backend Logout)

[pic]

Figure 6.2.6 (Add and Delete Clubs)

[pic]

Figure 6.2.7 (Add Event)

[pic]

Figure 6.2.8 (Edit Event)

[pic]

Figure 6.2.9 (Delete Event)

[pic]

Figure 6.2.10 (Add a post)

[pic]

Figure 6.2.11 (Edit a post)

[pic]

Figure 6.2.12 (Delete a post)

[pic]

Figure 6.2.13(Add an Article)

[pic]

Figure 6.2.14 (Modify an Article)

[pic]

Figure 6.2.15 (Delete an Article)

[pic]

Figure 6.2.16 (Create an Album)

[pic]

Figure 6.2.17 (Modify an Album)

[pic]

Figure 6.2.18 (Delete an Album)

[pic]

Figure 6.2.19 (Add Picture)

[pic]

Figure 6.2.20 (Delete Picture)

[pic]

Final Schedule

[pic]

Final Budget

[pic]

................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download