JDP FINAL REPORT An android app by Jonh Fernandes, David Diez Perez, and Peter Fitzpatrick.
42
JDP FINAL REPORT An android app by Jonh Fernandes, David Diez Perez, and Peter Fitzpatrick
-
Upload
tamsin-spencer -
Category
Documents
-
view
214 -
download
0
Transcript of JDP FINAL REPORT An android app by Jonh Fernandes, David Diez Perez, and Peter Fitzpatrick.
JDP FINAL REPORTAn android app by Jonh Fernandes, David Diez Perez, and Peter Fitzpatrick
Company Mission:
To always innovate and provide practical and simple software solutions via cutting-edge applications for mobile phones.
Proposed Goal:
Develop a bran new mobile application for Android phones and tablets.
Idea:
College Students’ JDP – Just Delightful Planner
Specific Goal:
The goal of JDP is to become a college student’s most handy planner app.
OUR COMPANY
WHAT IT DOES
-A calendar/planner app centered around college courses
-Allows users to order events based off of courses they are enrolled in
-Allows users to dynamically add, edit and remove said events
-Set reminders to keep you on track
February 2014Original Project Proposal
March 20141st week | Domain Analysis Stage2nd week |Project Requirements Analysis3rd week |Project Requirements Analysis4th week | Design Stage
April 2014Development Stage
May 2014Testing and Validating
Project Delivery Date
May 6th 2014
PROJECT SCHEDULE
February 2014Original Project Proposal
March 20141st week | Domain Analysis Stage2nd week |Project Requirements Analysis3rd week |Project Requirements Analysis4th week | Design Stage
April 2014Development Stage
May 2014Testing and Validating
Project Delivery Date
May 6th 2014
PROJECT SCHEDULE
USE-CASE SCENARIOS
ADD EVENT
SYSTEM: display home screen
USER: select “ADD EVENT”
SYSTEM: show a calendar view
USER: select a date
SYSTEM: show a row of time for selection
USER: select a specific time
SYSTEM: show a dialog box to describe the event of this time/date
USER: Input the description and submit.
SYSTEM: save the information
SYSTEM: display home screen
USE-CASE SCENARIOS
ADD EVENT
SYSTEM: display home screen
USER: select “ADD EVENT”
SYSTEM: show a calendar view
USER: select a date
SYSTEM: show a row of time for selection
USER: select a specific time
SYSTEM: show a dialog box to describe the event of this time/date
USER: Input the description and submit.
SYSTEM: save the information
SYSTEM: display home screen
USE-CASE SCENARIOS
DELETE EVENTSYSTEM: display home screen
USER: select “DELETE EVENT”
SYSTEM: display calendar view
USER: select specific date
SYSTEM: display that date’s events
USER: select desired event
SYSTEM: show a dialogue box confirming deletion
USER: select answer
SYSTEM: display home screen
USE-CASE SCENARIOS
ADD COURSE
SYSTEM: display home screen
USER: select “add”
SYSTEM: display “Add screen”
USER: select “course”
SYSTEM: ask for course name and info
USER: input all the requested info
SYSTEM: show inputted info, save?
USER: select save or not
SYSTEM: save event or discard input
SYSTEM: show results
USE-CASE SCENARIOS
ADD COURSE
SYSTEM: display home screen
USER: select “add”
SYSTEM: display “Add screen”
USER: select “course”
SYSTEM: ask for course name and info
USER: input all the requested info
SYSTEM: show inputted info, save?
USER: select save or not
SYSTEM: save event or discard input
SYSTEM: show results
USE-CASE SCENARIOS
EDIT EVENT
SYSTEM: display home screen
USER: select “show events”
SYSTEM: list events
USER: select one
SYSTEM: show a dialog box with previous information
USER: change the previous information and confirm
SYSTEM: alter the previous information, confirm the alteration and back to home screen
February 2014Original Project Proposal
March 20141st week | Domain Analysis Stage2nd week |Project Requirements Analysis3rd week |Project Requirements Analysis4th week | Design Stage
April 2014Development Stage
May 2014Testing and Validating
Project Delivery Date
May 6th 2014
PROJECT SCHEDULE
Four Categoriesa. Functional Requirementsb. Quality Requirementsc. Platform Requirementsd. Process Requirements
REQUIREMENTS
First Categorya. Functional Requirementsb. Quality Requirementsc. Platform Requirementsd. Process Requirements
REQUIREMENTS
FUNCTIONAL REQUIREMENTS
F1. The application should allow the following functionalities for Events:
F1.1 Add
F1.2 Delete
F1.3 Edit
OBS: Events can be homework, community service, class meeting, etc.
F2. The application should allow the following functionalities for Courses
F2.1 Create
F2.2 Delete
F2.3 Assign Event
FUNCTIONAL REQUIREMENTS
F3. Set reminders for Events
F4. Display reminders on Android’s main notification bar
F5. Display upcoming events and enrolled courses on an organized home screen
Second Categorya. Functional Requirementsb. Quality Requirementsc. Platform Requirementsd. Process Requirements
REQUIREMENTS
QUALITY REQUIREMENTS:
This application should take no more than five seconds when processing input from the user.
RESPONSE TIME
QUALITY REQUIREMENTS:
The maximum amount of memory that this application should consume is no more than 30MB.
RESOURCE USAGE
QUALITY REQUIREMENTS:
We aim for this program to have a maximum of one failure in a week long period of continuous usage.
RELIABILITY
QUALITY REQUIREMENTS:
At any given down time, the program should not be functionless for more than one minute.
AVAILABILITY
QUALITY REQUIREMENTS:
Should the application crash, the program will be rebooted by android and the data will remain intact.
RECOVERY FROM FAILURE
QUALITY REQUIREMENTS:
This program should allow for future enhancements such as cloud storage so that the application can send and receive data on multiple devices
MAINTENANCE
QUALITY REQUIREMENTS:
This application should be very intuitive. Any person that know to use Android systems can use it.
USABILITY
QUALITY REQUIREMENTS:
About 40% of the code used to create this application should be specifically designed so that it can be re used.
REUSABILITY
QUALITY REQUIREMENTS:
As a local application, this program should have personal control about data.
SECURITY
Third Categorya. Functional Requirementsb. Quality Requirementsc. Platform Requirementsd. Process Requirements
REQUIREMENTS
PLATFORM REQUIREMENTS1. Android powered smartphon
es.2. 2.35” by 4.18” or smaller siz
ed, Android devices.3. Android devices running And
roid 4.0 or later.
Fourth Categorya. Functional Requirementsb. Quality Requirementsc. Platform Requirementsd. Process Requirements
REQUIREMENTS
PROCESS REQUIREMENTS
1. Entire application will be written in the bundled Eclipse with the Android Software Development Kit
2. All source code must be commented sufficiently
3. All source code must be reviewed by all members of the team
4. Cost: this project proudly takes full advantage of the free, open source software available to us from the good folks at the Open Source Initiative (www.opensource.org)
5. Delivery Date: first week of May, 2014.
February 2014Original Project Proposal
March 20141st week | Domain Analysis Stage2nd week |Project Requirements Analysis3rd week |Project Requirements Analysis4th week | Design Stage
April 2014Development Stage
May 2014Testing and Validating
Project Delivery Date
May 6th 2014
PROJECT SCHEDULE
UML DIAGRAM
February 2014Original Project Proposal
March 20141st week | Domain Analysis Stage2nd week |Project Requirements Analysis3rd week |Project Requirements Analysis4th week | Design Stage
April 2014Development Stage
May 2014Testing and Validating
Project Delivery Date
May 6th 2014
PROJECT SCHEDULE
PROPOSED GANTT CHART
REFORMED GANTT CHART
February 2014Original Project ProposalMarch 20141st week | Domain Analysis Stage2nd week |Project Requirements Analysis3rd week |Project Requirements Analysis4th week | Design StageApril 2014Development StageMay 2014Testing and Validating
Project Delivery Date
May 6th 2014
PROJECT SCHEDULE
SCREEN SHOTS
SCREEN SHOTS
SCREEN SHOTS
APP INFO
THE JUST DELIGHTFUL PLANNER
LIVE DEMO ..
We will now do a live demonstration of our fabulous android app..
THE JUST DELIGHTFUL PLANNER
THANKS !
Hope you enjoyed this presentation..
