close

Вход

Забыли?

вход по аккаунту

код для вставкиСкачать
Team07
Tucker Lein, Justin Price, Cody Robinson, and Jennifer Gay
1
ITEC 370 – Software Engineering I
Client: R-SPaCE – Amanda Sorenson
Team Project : R-SPaCE Entertainment App
and Centralized Website for Distributing
Information
Six Week Update Presentation
2
Objectives Overview
 Who/What is R-SPaCE?
 Current issues our client is facing
 Our Project: Solution to client’s needs
 Project Overview
 Backend Overview
 Development Plan Overview
 Conclusion
3
What does R-SPaCE stand for?
Radford Student Programming and
Campus Events
R-SPaCE is an organization, through
Student Affairs, which works with
other organizations on campus to
bring Radford students entertaining
events. Movies, concerts, Build-ABear workshops, etc.
4
Problem: People forget about RSPaCE Events
What Was I Supposed To Remember?
5
Solution…
 R-SPaCE Entertainment App
 Lists current and upcoming
events
 Provide mobile access to event
information
 Manage customizable alerts for
specific events
6
Problem: Updating
multiple websites to post
information
There must be an
easier way *sigh*
Before Tesseract Design
Came to R-SPaCE’s rescue
7
Each website had to be updated manually for every event
8
R-SPaCE Entertainment App User
Interface Preview – Home Page
9
R-SPaCE Entertainment App User
Interface Preview Cont’d – All Page
10
R-SPaCE Entertainment App User Interface
Preview Cont’d – Event Detail Page
11
Event Management Website
Overview
 Login with RU username and
password
 Post events with web form
 Server script:
 Updates Events Database
 Posts event information to
other online media websites
that R-SPaCE uses
 Alerts Android devices about
updated Events Database
12
Android App Overview
 App will communicate with
Events server using AJAX
 New event information will
be sent to the client as a JSON
string
 Client will store new event
information in a local
database for offline storage
13
Development Plan
 Break development into 4 sections:
 Development of the app
 Front-end of Event Management Website
 Client-server communication
 Event server-side processing
 Assign each of these sections to one of our developers
to work on parallel to each other
14
Development Plan
 Other plans for development:
 Testing small components of functionality during
Requirements phase



Push notifications
AJAX communication
Facebook/Twitter APIs
15
Conclusion
16
1/--страниц
Пожаловаться на содержимое документа