Software Design Document
Andrew Doyle
Chad Sloan
Stephanie Shaver
Ethan Bowyer
Software Engineering I
April 07, 2011
[] [ Code Walkers ]Software Design Specification
Revisions
Version / Primary Author(s) / Description of Version / Date CompletedFinal Draft #1 / Andrew Doyle
Ethan Bowyer
Chad Sloan
Stephanie Shaver / Completed all the sections / 04/06/2011
Review & Approval
Requirements Document Approval History
Approving Party / Version Approved / Signature / DateAndrew Doyle / 1 / 04/07/2011
Dr. T. L. Lewis
Requirements Document Review History
Reviewer / Version Reviewed / Signature / DateEthan Bowyer / 1 / 04/07/2011
Chad Sloan / 1 / 04/07/2011
Stephanie Shaver / 1 / 04/07/2011
1Contents
1 Contents
2 Introduction
2.1 System Overview
2.2 Supporting Materials
2.3 Definitions and Acronyms
3 Functional Requirements Mapping Overview
4 High Level Design
4.1 Conceptual View (Architectural Context Model)
5 Low Level Design
5.1 Process Model
6 User Interface Design
6.1 Application Control
6.2 Screen 1..n
7 Final Schedule
8 Final Budget
Page 1
[] [ Code Walkers ][ Project ] - Software Design Specification
2Introduction
2.1System 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.2Supporting Materials
Microsoft Visio
Microsoft Project
2.3Definitions 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.
3Functional Requirements Mapping Overview
Functional Requirement / Design Artifact1: User Login : The user shall be able to login into the system. / (Figure 6.2.1)
Login section on the main page
2: Administrator Backend Login: The Administrator shall be able to login to the system from the backend. / (Figure 6.2.2)
Joomla! Administration Page
3: Club Registration: An Administrator shall be able to register a club with the system. / (Figure 6.2.6)
Joomla! Backend , User Registration
4: Password Recovery: The system shall be able to give a user their password when requested by that user. / (Figure 6.2.3)
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 clubs from the system. / (Figure 6.2.6)
Joomla! backend, User Registration
7: Create Album: All users shall be able to create an album to store pictures in. / (Figure 6.2.16)
Joomla! Backend, Components, Phoca Gallery, Categories
8: Create Calendar Event: The user shall be able to create events in the calendar. / (Figure 6.2.7)
JEvents Calendar, JEvents Calendar
9: Add Photo: The user shall be able to add photos to a specified album. / (Figure 6.2.19)
Photo Gallery, Albums
10: Delete Photo: The administrator shall be able to delete photos from an album. / (Figure 6.2.20)
Photo Gallery, Albums
11: Add Post: A user shall be able to add a post about what is currently going on at an event for all other users to see. / (Figure 6.2.10)
Add Post on the main page
12: Delete Post: An administrator shall be able to delete a post that has been added to the news feed. / (Figure 6.2.12)
Joomla! Backend, Article Manager,
13: Add Article: A user shall be able to add an article to the website after logging in. / (Figure6.2.13)
Main Page, Add Article
14: Delete Article: An administrator shall be able to remove an article they have uploaded. / (Figure 6.2.15)
Joomla! Backend, Article Manager
15: Administrator Backend Logout: The Administrator shall be able to logout of the backend of the system. / (Figure 6.2.5)
Joomla! Backend
16: Modify Article: A user shall be able to modify their uploaded article. / (Figure 6.2.14)
Joomla! Backend, Article Manager
17: Modify Post: A user shall be able to modify a post that they have added to the news feed. / (Figure 6.2.11)
Edit Post on the main page
18: Delete Calendar Event: The administrator shall be able to delete events from the calendar. / (Figure 6.2.9)
Joomla! Backend, Components, JEvents, Manage Events
19: Modify Calendar Event: The user shall be able to modify events in the calendar. / (Figure 6.2.8)
Edit Event on the JEvents Calendar Page
20: Modify Album: All users shall be able to modify an album to store pictures in. / (Figure 6.2.17)
Joomla! Backend, Components, Phoca Gallery, Categories
21: Delete Album: The administrator shall be able to delete an album to store pictures in. / (Figure 6.2.18)
Joomla! Backend, Components, Phoca Gallery, Categories
4High Level Design
4.1Conceptual View (Architectural Context Model)
5Low Level Design
5.1Process Model
6User Interface Design
6.1Application 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).
6.2Screen 1..n
Figure 6.2.1: User Login
Figure 6.2.2: Administrator Backend Login
Figure 6.2.3 (Password Recovery)
Figure 6.2.4 (User Logout)
Figure 6.2.5 (Administrator Backend Logout)
Figure 6.2.6 (Add and Delete Clubs)
Figure 6.2.7 (Add Event)
Figure 6.2.8 (Edit Event)
Figure 6.2.9 (Delete Event)
Figure 6.2.10 (Add a post)
Figure 6.2.11 (Edit a post)
Figure 6.2.12 (Delete a post)
Figure 6.2.13(Add an Article)
Figure 6.2.14 (Modify an Article)
Figure 6.2.15 (Delete an Article)
Figure 6.2.16 (Create an Album)
Figure 6.2.17 (Modify an Album)
Figure 6.2.18 (Delete an Album)
Figure 6.2.19 (Add Picture)
Figure 6.2.20 (Delete Picture)
7Final Schedule
8Final Budget
Page 1