Upload
samson-walsh
View
218
Download
0
Tags:
Embed Size (px)
Citation preview
Overview of Project
Introduction Purpose of the projectProject PlanUsecase DiagramUsecase SpecificationsBreakdown of individual usecasesDiscuss Sequence DiagramsFunctional TestShow Screen Shots of Application
Overview of Project (Continued)
Discuss ER and Class DiagramData DictionaryDiscuss Dataflow DiagramEvolutionClosing Remarks
Introduction(About us)
Gassie Orr- A fourth year CIS major who graduates in the Spring.
Jabare Mitchell-
Introduction
While in the system class, we the class, came up with a system design that we believe would be beneficial to Florida Agricultural and Mechanical University.
A GPS application for the campus
It will give directions to various buildings, parking lots, and bus routes according to where they are located on the campus.
Introduction
Will also include a variety of special features to go along with this application such as a special events section, which will describe the different types of events going on around the campus.
Another key feature that will be included on our system will be the alerts section. will include our They Towing alert system
application that allows users to be educated about the campus of Florida A&M and also for efficiency when trying to get around on the campus.
Purpose
The purpose of this system is to provide a Navigation system specifically for Florida A&M University.
We also would like for our system to pr0vide a more efficient way of getting around our campus.
….. And of course for an “A” grade!!!
Project Plan
Our project plan consist of 8 steps….1. Start Project2. Project Specifications Finalized3. Android Phone Acquired4. Android App Developer Software Downloaded5. Best GPS and Mapping Systems Chosen6. Application programming Completed7. GPS and Mapping Interface Completed8. Project Completion
Diagram on next slide…
Use case Diagram
From a list of stakeholders we narrowed it down to 3 actors.
This diagram shows what the actors are capable of doing, but not limiting them to the things that are around them, because some of the actors can do things other actors can do.
A way of reducing redundancy
Use Case Specifications
Our use case specifications come from the “can do’s” in the Use Case Diagram.
A total of 12 basic features that we believe are vital to our systems success.
Over time new features will be included.For better understanding we will show you the
Use Case Specification each with… Sequence diagram- includes all classes that go along
with the Use case. Function Test Case- an example in words of the use case Screenshots w/ appropriate data.
ER Diagram
The ER Diagram shows the relationship between entities along with the attributes that go along with each of them.
Data Dictionary
The Data Dictionary is a list of all the Entities we believe that we will need that explain the attributes, the types, the key, and a description.
These are also found on the ER diagram.
Dataflow Diagram
The Dataflow Diagram shows the flow of how all the use cases are carried out, it does not show any relationships it just explains the flow of the system.
Evolution
Like we stated previously there would be new features that we would like to include on the system.
Here is a list of a couple features we would like to have in design by the time the first system comes out.