PerryM123 / BluePrintAlarmClock

Software Developer project

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

BluePrintAlarmClock

Software Engineering class project

Android Application made with Java Programming Language

Project length: 2 months

Software Engineering Ideologies and Patterns:

Agile Programming:

-Weekly Meetings

-Set short term goals

SCRUM (4 members)

-SCRUM team consisted of SCRUM MASTER, Development team, and Product Owner -1 week sprints

-Before each sprint, team members set and explains goals for the sprint -At the end of the sprint, we conduct a code review Model-View-Controller Pattern(MVC)

-Focused on utilizing MVC pattern

Goal

At the time of being a university student, I noticed many students had a lot of difficulties with waking up early for class. Many students rely on cell phone alarm systems, but the major flaw for this lies in the "Shut off alarm". After a normal cell phone alarm rings, many students are successful awakened but on the other hand, countless students make the mistake of shutting off the alarm and falling back to sleep. As a result, the student misses class.

This is where we come in. The BluePrintAlarmClock will function like a normal alarm clock but with one catch. In order to stop our users from falling back to sleep after turning off the alarm, we have set up a challenge where the user would be forced to solve an easy simple or difficult mathematical problem and spelling puzzles to shut off the alarm.

The idea is:

we want to force the user to wake up and use brain power to shut off the alarm. With the help of a difficult math problem, the user will be unable to solve the problem quickly and will be forced to find a pen and paper to solve the math problem. After the user uses brain power and successfully shuts off the alarm, the user will be FULLY awakened and be unable to fall back asleep.

Screenshots

alt tag alt tag alt tag alt tag alt tag

Regrets/Things we wished improved on/Lessons learned

-Unfortunately, due to time constraints, our final sprint was incredibly hectic. We made a lot of desperate fixes and ugly ugly ugly design decisions to push our product out for the user.

Evidence of this is in:

-AlarmSetting.java

-GlobalVariables.java

-Main.java

-NormalAlarmReceiver

-MathProblems

-Also, due to time constraints, we were forced to remove the Word problem and Word Spelling Problems for the project leaving the application only with a Math Problem Alarm.

-A very big lack of proper documentation:

Because the deadline was closing in very fast, we disregarded using JavaDoc or any sort of documentation. This ended up hurting us in the long run. It made our code unreadable and difficult to follow. Running into this problem made me realize how incredibly important it is to properly document work for future works.

Contributors

AlarmSetting.java - worked on by Perry and Travis

GlobalVariables.java - Nick, Rameet

Main - Perry, Nick, Travis, Rameet

MathProblem - Perry

MathScreen - Perry

NormalAlarmReceiver - Perry, Nick, Travis, Rameet

SnoozeDismiss - Perry and Travis

SoundService - Travis

WordProbWorker - Perry

generateWords - Perry

About Us/ Authors

A team of programmers working on the same goal during our school semester

Author:

Perry Miranda

About

Software Developer project


Languages

Language:Java 100.0%