[ Organization Name ] Software Design Specification

Software Engineering Software Design Document

Nick AntzoulatosRoger Kidd

Chad GuevremontScott Wenkstern

Andrew Polhamus

Dot Com Millionaires

https://www.radford.edu/~softeng17/index.html

11/16/11

Page i

[ Organization Name ] Software Design Specification

Revisions

Version Primary Author(s)

Description of Version Date Completed

1 Dot Com Mil-lionaires

Final Draft. 11/17/11

Review & Approval

Requirements Document Approval History

Approving Party Version Approved

Signature Date

Scott Wenkstern 1

Dr. T. L. Lewis

Requirements Document Review History

Reviewer Version Reviewed

Signature Date

Chad Guevremont 1

Andrew Polhamus 1

Nick Antzoulatos 1

Roger Kidd 1

Page ii

[ Organization Name ] Software Design Specification

1 Contents

1 CONTENTS.................................................................................................................III

2 INTRODUCTION...........................................................................................................1

2.1 SYSTEM OVERVIEW..................................................................................................1

3 FUNCTIONAL REQUIREMENTS MAPPING OVERVIEW..............................................2

4 HIGH LEVEL DESIGN.................................................................................................6

4.1 CONCEPTUAL VIEW (ARCHITECTURAL CONTEXT MODEL).....................................6

5 LOW LEVEL DESIGN..................................................................................................7

5.1 DATA FLOW DIAGRAM MODEL................................................................................75.2 DATA FLOW DIAGRAM MODEL................................................................................8

6 USER INTERFACE DESIGN.........................................................................................9

6.1 APPLICATION CONTROL...........................................................................................96.2 SCREENS.................................................................................................................10HOME SCREEN..............................................................................................................10

7 FINAL SCHEDULE.....................................................................................................15

8 Final Budget..............................................................................................................17

Page iii

[ Organization Name ] [ Project ] - Software Design Specification

2 Introduction

2.1 System OverviewOur goal is to create an interactive application for the new Radford University transit system. We plan to include a map with active icons of all of the pick-up/drop off points, which will allow you to view the hours of operation, times of every stop, and other detailed information about each stop. Ideally, we would like to incorporate real-time GPS into the map that would tell the user where the closest bus stop is rela-tive to their location. We will also provide a link to the main website & interactive buttons to auto contact the transit or emergency services. We will include a ‘Trip Planner’ function that will allow the user to choose a route, destination, and time from drop-down menus and have the application calculate and output route details.

Supporting Materials

Programs:

-Microsoft Project

-Microsoft Visio

-Microsoft Word

-WireframeSketcher Pro

-Adobe Photoshop

Web:

-Appinventor Tutorials

-www.w3schools.com

Meetings:

Meetings 6-10

Page 1

[ Organization Name ] [ Project ] - Software Design Specification

3 Functional Requirements Mapping Overview

Functional Require-ment Design Artifact

1: Select a Route

Page 2

[ Organization Name ] [ Project ] - Software Design Specification

2: Pick a Map

Page 3

[ Organization Name ] [ Project ] - Software Design Specification

3: Plan a Trip

Page 4

[ Organization Name ] [ Project ] - Software Design Specification

4:Interact with the Map

5: User Hits the Back Button Returns to Splash Screen. Then Loads main menu.

Page 5

[ Organization Name ] [ Project ] - Software Design Specification

4 High Level Design

4.1 Conceptual View (Architectural Context Model)

Page 6

[ Organization Name ] [ Project ] - Software Design Specification

5 Low Level Design

5.1 Data Flow Diagram Model

High-Level Data flow for broad application use.

Page 7

[ Organization Name ] [ Project ] - Software Design Specification

5.2 Data Flow Diagram Model

Low-level data flow for trip planner.

Page 8

[ Organization Name ] [ Project ] - Software Design Specification

6 User Interface Design

6.1 Application Control

Each screen for the application will have a similar look and feel and transition smoothly. Upon loading, the application will briefly display a splash screen, then it will proceed to display the home screen. The home screen will have four buttons that may be pressed. Upon pressing these buttons, the application will proceed to the next screen. The schedule screen will have tables of data providing information on route times. The Trip Planner screens will have drop down menus that will be detailed in the next section. The Maps screen will have interactive images of maps through which the user will be able to scroll, zoom, and rotate. Each screen will maintain a similar look and feel. Screenshots and further detail will be provided in the next sec-tion.

Page 9

[ Organization Name ] [ Project ] - Software Design Specification

6.2 Screens

Home Screen

The home screen will have four buttons: Maps, Schedule, Trip Planner, and About.

When clicked, these buttons will take the user to the corresponding screen.

Page 10

[ Organization Name ] [ Project ] - Software Design Specification

Trip Planner Screen

The trip planner screen will function as illustrated. The user will select a route, time, and des-tination from drop down menus. When the “Go” button is pressed, it will proceed to the next screen, the map screen. The map screen is used to select a destination. When the destination is selected, the user will again press “Go” then be taken to the confirmation screen. At the confirmation screen, the user will either press “Yes” to confirm the route or “Change Loca-tion” to be taken to the previous screen. The final screen before the route information is pro-vided is the waiting screen, with a loading bar and a notice to “please wait.”

Page 11

[ Organization Name ] [ Project ] - Software Design Specification

This is the map selection screen. The user will push the button corresponding with the desired map. The number and the map will both be clickable.

Page 12

[ Organization Name ] [ Project ] - Software Design Specification

This is the route selection screen. The user will select the desired route. The number and text will be clickable.

Page 13

[ Organization Name ] [ Project ] - Software Design Specification

This is the trip planner selection screen. Here the user will select from the menus their day, route, and destination

Page 14

[ Organization Name ] [ Project ] - Software Design Specification

7 Final Schedule

PERT Chart for RU Transit Development

Page 15

[ Organization Name ] [ Project ] - Software Design Specification

Page 16

[ Organization Name ] [ Project ] - Software Design Specification

8 Final Budget

Page 17