BY: GASSIE ORR JABARE MITCHELL TYSHUN JONES Information Systems (Android Application)

Slides:



Advertisements
Similar presentations
Project Analysis Course ( ) Final Project Report Overview.
Advertisements

OOAD – Dr. A. Alghamdi Mastering Object-Oriented Analysis and Design with UML Module 3: Requirements Overview Module 3 - Requirements Overview.
Deliverable #8: Detailed Design - Overview due: Wednesday, 7 March All Deliverable materials are to be posted into Team Concert. Your to.
Write Your Project Title Here VU Logo Here Group Members Introduction Write your group members introduction here with names and VU Id.
Write Your Project Title Here VU Logo Here Group Members Introduction Write your group members introduction here with names and VU Id.
INFO 425 Week 31 INFO 425 Design Problem I Week 3 – SDS Improvements Glenn Booker.
Automatic Annotation of Urban Environments to Support POL Behavior Automatic Annotation of Urban Environments to Support Pattern of Life Behavior Daniel.
Information Systems (Android Application)
Chapter 6 Methodology Conceptual Databases Design Transparencies © Pearson Education Limited 1995, 2005.
Requirements of the user interface: Use-case story board (1) The use-case storyboard –Complements use-cases by user-interface issues –Takes the use-cases‘
Methodology Conceptual Database Design
Setting up IC to use a 4 Point Scale Created by North High School 2013.
RUP Requirements RUP Artifacts and Deliverables
Lesson 7 Guide for Software Design Description (SDD)
UML REVIEW –PART1 1. Introduction What is UML visual modelling language UML is a language not a methodology? Q: why is this distinction important? UML.
® IBM Software Group © 2006 IBM Corporation Rational Software France Object-Oriented Analysis and Design with UML2 and Rational Software Modeler 06. Requirements.
Chapter 5 Analysis Model. Analysis model (AM) The first step in describing how the system will implement the requirements specification The first step.
ANALYSIS REQUIREMENT ANALYSIS DESIGN IMPLEMENTATION TEST.
1 Requirements Analysis and Design Engineering Southern Methodist University CSE 7313.
Uploading Image Files. Introduction – Click on Control Panel Button Typically, most instructors will post the majority of their images under the “Course.
Team ELL System Requirements Ladakeysha Thomas Elizabeth Waldo LaWanda Warren Brandon Williams.
Methodology - Conceptual Database Design Transparencies
Software School of Hunan University Database Systems Design Part III Section 5 Design Methodology.
Methodology Conceptual Databases Design
1 Chapter 15 Methodology Conceptual Databases Design Transparencies Last Updated: April 2011 By M. Arief
Prepared by Afra`a Sayah. Introduction. Weekly Tasks. Plane Phase. Analysis Phase. Design Phase. Report Rules. Conclusion. 2.
Team ELL Team Members: Ladekeysha Thomas Elizabeth Waldo LaWanda Warren.
Generalizable Element Namespace Model Element name visibility isSpecification Classifier isRoot Constraint Body Use Cases CS/SWE 421 Introduction to Software.
Requirements Specification for Lab3 COP4331 and EEL4884 OO Processes for Software Development © Dr. David A. Workman School of Computer Science University.
Software Engineering Chapter 7 Fall Capturing the Requirements as Use Cases Capturing the Requirements as Use Cases By using use cases analysts.
Requirements Artifacts Precursor to A & D. Objectives: Requirements Overview  Understand the basic Requirements concepts and how they affect Analysis.
FAMU CMRP Database By: Jabare Mitchell Tyshun Jones Gassie Orr.
COMP106 Assignment 2 Proposal 1. Interface Tasks My new interface design for the University library catalogue will incorporate all of the existing features,
Methodology - Conceptual Database Design. 2 Design Methodology u Structured approach that uses procedures, techniques, tools, and documentation aids to.
Information Systems in Organizations 2
Requirements as Usecases Capturing the REQUIREMENT ANALYSIS DESIGN IMPLEMENTATION TEST.
Template for Applet Design stage. General Instructions: The template shown is an example. Please add more slides wherever required. Include look of the.
Methodology - Conceptual Database Design
R.O.S.E.S. Preliminary Design Presented By: Code Shark Solutions 12/8/10.
® IBM Software Group © 2006 IBM Corporation Writing Good Use Cases Module 1: Introduction to Use-Case Modeling.
ANALYSIS - II REQUIREMENT ANALYSIS DESIGN IMPLEMENTATION TEST.
Shanghai Jiao Tong University 上海交通大学软件工程中心 Object Oriented Analysis and Design Requirements Overview.
CPSC 203. Use Case Diagram  A description of a system’s behavior as it responds to a request that originates from outside of that system. Specifies the.
Analysis Modeling CpSc 372: Introduction to Software Engineering
Use Cases CS 6961 – Lecture 4 Nathan Dykman. Neumont UniversityCS Lecture 102 Administration Homework 1 is due –Still reviewing the proposal, but.
SWEN 5231 FORMAL METHODS Slide 1 System models u Abstract presentations of systems whose requirements are being analyzed.
Conceptual Databases Design Step 1 © Pearson Education Limited 1995, 2005.
These materials are prepared only for the students enrolled in the course Distributed Software Development (DSD) at the Department of Computer.
CIS 4910 Information Systems Development Project Project Documentation.
Generalizable Element Namespace Model Element name visibility isSpecification Classifier isRoot Constraint Body Use Cases CS/SWE 421 Introduction to Software.
Analysis Yaodong Bi. Introduction to Analysis Purposes of Analysis – Resolve issues related to interference, concurrency, and conflicts among use cases.
Use Case Model Use case description.
Object Oriented Analysis and Design Introduction to Rational Rose.
Your Interactive Guide to the Digital World Discovering Computers 2012 Chapter 12 Exploring Information System Development.
Use Case, Component and Deployment Diagrams University of Sunderland.
INFORMATION X INFO415: Systems Analysis.
CS 8532: Adv. Software Eng. – Spring 2009 Dr. Hisham Haddad , Monday Class will start momentarily. Please Stand By … CS 8532: Advanced Software.
LOGO Supervisor: Mr.Huỳnh Anh Dũng Students: Nguyễn Công Tuyến Nguyễn Cảnh Phương Phạm Thị Hằng Bùi Thị Huệ Trần Đức Bình Nguyễn.
OOAD Using the UML - Use-Case Analysis, v 4.2 Copyright  Rational Software, all rights reserved 1 Use Case Analysis – Part 4 Analysis Mechanisms.
Methodology Conceptual Databases Design
Methodology Conceptual Database Design
Student name Student ID Degree program Area of specialization
Software Engineering Summarized Slides.
Student name Student ID Degree program Area of specialization
Write Your Project Title Here VU Logo Here
Software Design Lecture : 15.
Methodology Conceptual Databases Design
Student name Student ID Degree program Area of specialization
Presentation transcript:

BY: GASSIE ORR JABARE MITCHELL TYSHUN JONES Information Systems (Android Application)

Overview of Project Introduction Purpose of the project Project Plan Usecase Diagram Usecase Specifications Breakdown of individual usecases Discuss Sequence Diagrams Functional Test Show Screen Shots of Application

Overview of Project (Continued) Discuss ER and Class Diagram Data Dictionary Discuss Dataflow Diagram Evolution Closing Remarks

Introduction The students in Prof. Nowicki’s Information Systems Design and Development class came up with a system design that we believe would be beneficial to Florida Agricultural and Mechanical University. A GPS application based on FAMU’s campus area, usable by Faculty, Students and campus police. 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. An example of one of the features 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 Project 2. Project Specifications Finalized 3. Android Phone Acquired 4. Android App Developer Software Downloaded 5. Best GPS and Mapping Systems Chosen 6. Application programming Completed 7. GPS and Mapping Interface Completed 8. Project Completion Diagram on next slide…

Project Plan (PERT Chart)

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 Diagram (Diagram)

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.

Use Case Specification (Find a Parking Spot)

Sequence Diagram (Find a Parking Spot)

Function Test Case (Find a Parking Space)

Screen Shot (Find A Parking Spot) General Step 1 (Of all cases) Step 2

Screen Shot (Find A Parking Spot) Step 3

Screen Shot (Take Me to Next Class) Step 1 Step 2

Take Me to Next Class (Alternate Flow) Step 1 Step 2

Use Case Specification (Get Safety Alert)

Sequence Diagram (Get Safety Alert)

Screen Shot (Get Safety Alert)

Use Case Specification (Get they Towing Alerts)

Screen Shot (Get they Towing Alerts)

Sequence Diagram (Save Location)

Function Test Case (Save Location)

Screen Shot (Save Location) Bragg Stadium Entered in TextBox Saved Location In Blue

Use Case Specification (Post Safety Alerts)

Sequence Diagram (Post Safety Alerts)

Function Test Case (Post Safety Alerts)

Screen Shot (Post Safety Alerts)

Use Case Specification (Post they Towing Alerts)

Sequence Diagram (Post they Towing Alerts)

Function Test Case (Post they Towing Alerts)

Sequence Diagram Edit Class Schedule(Remove)

Sequence Diagram Edit Class Schedule(Add)

Screen Shot Edit Class Schedule (Add) Step 1 Step 2

Screen Shot Edit Class Schedule (Add) Step 3

Screen Shot Edit Class Schedule (Remove) Step 1 Step 2

Screen Shot Edit Class Schedule (Add) Step 3

ER Diagram The ER Diagram shows the relationship between entities along with the attributes that go along with each of them.

ER Diagram

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.

Data Dictionary Instructor

Data Dictionary Student

Data Dictionary (User)

Data Dictionary (Parking Lot)

Data Dictionary (location)

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.

Dataflow (diagram)

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.

Evolution

Closing Remarks 1This completes our system design. Like previously stated the goal is to make getting around the campus more efficient and effective. Possible specifications to leave out or alter: Bus Route Feature