1 / 7

Life Cycle Objectives

Life Cycle Objectives. By James Lee and Matt Higgins Project Name: Task Scheduler. Operational Concepts. Cell phones have poor input and output capabilities compared to a normal PC This project uses the benefits of a PC with the mobile benefits of a cell phone

nehru-calhoun
Download Presentation

Life Cycle Objectives

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Life Cycle Objectives • By James Lee and Matt Higgins • Project Name: Task Scheduler

  2. Operational Concepts • Cell phones have poor input and output capabilities compared to a normal PC • This project uses the benefits of a PC with the mobile benefits of a cell phone • The Task Scheduler allows users to create a schedule on a PC, which will then execute tasks on their cell phone

  3. System Requirements • A server interface with 3 ways of designing a schedule • Create a schedule by days of the week • Parse a student’s class schedule to create a weekly schedule • Add tasks for specific dates and times • The tasks include the following: • Ringer on/off • Alarm clock • Text reminders • The phone will have menus to view upcoming tasks and to disable the Task Scheduler.

  4. System and software architecture • The servlet provides the interface for the user, and stores individual’s schedules in a database. It will send commands to the phone to perform. • The midlet will respond to servlet requests, and execute the specified tasks. The user has the option of turning off the Task Scheduler.

  5. System and software architecture Client Midlets HTTP (Wireless Web) Task Servlet Database User Servlet Home PC

  6. Lifecycle Plan • Objective: Give users a quick way to create a schedule that they will use for months. • Schedule: Completed by June 5th. • Resources: Database, 4-6 students • The servlet will need the most work, and will require more than half the group. • New tasks can be added with later versions

  7. Feasibility Rationale • Implementation of the schedule interface seems feasible • Different phones may not have the capability to respond to all of the desired tasks • The time it takes for the user to design a schedule must be worth it for the time that they may save • The servlet’s access to a student’s schedule requires for them to be logged onto MYUW

More Related