SCHEDULE 360 SOFTWARETeam Alpha

Submitted To:

Dr. Lawrence ChungAssociate Professor,

Department of Computer Science,The University of Texas at Dallas,

Richardson, TX- 75080

Submitted By:

Steven FordGilbert Islas

Paul WasilewskiObi Ogbanufe

Michael Murphy 

Team Website: http://www.indigomark.com/alpha/

Steve’s Scheduling

Steve is a Director of Sales for Alpha Communications, a startup with 20 employees

Steven Has Numerous Commitments

Steve Coach’s kids

Steve has a wife

Steve has two young children

Presentation is at 9AMSteve is presenting to the board of a large corporation on the upcoming availability of a

new product on Wednesday

Tuesday Afternoon

•Steve Confirms Conference Room - Alpha

Steve Confirms Meeting Time - 9AM

Steve Finalizes Presentation

At 4:30pm a meeting notice change comes up moving the conference room from Alpha to Bravo and the meeting time from 9am to

8am

At 4:30pm Steve leaves early for Dentist Appointment

Tuesday Afternoon

Tuesday Night

Prepares for next morning

Dinner with Wife

Puts kids to bed

Wednesday Morning

STEVEN WAKES UP AND GETS READY.

Steven gets the kids up and ready.

Steven takes the kids to day care at 7:30 am.

Steven drops the wife off at work (her car is in the shop).

Wednesday Morning

STEVEN ARRIVES AT CONFERENCE ROOM AT 8:30 AM, CONFERENCE ROOM IS EMPTY.

Steven is flustered.

Steven calls his boss.

Steven’s boss informs him that the meeting time and room had changed per change notification sent out at 4:30 yesterday.

Wednesday Morning

STEVEN RUSHES INTO CONFERENCE ROOM BRAVO 40 MINUTES LATE.

Customers are unhappily leaving.

Any potential for deal with customer is lost.

Does this scenario sound familiar???

Schedule 360 Cloud SoftwareThe Average young tech savvy professional

interfaces with as many as six computing devices during a normal day

Each device has its own calendar or schedule application

The majority of the different platforms are not able to synchronize with other devices/programs

Additionally, any given program or system is at risk of failure causing the permanent loss of critical information.

Schedule 360 Stakeholders• An individual who utilizes multiple computing

devices and maintains a schedule either professionally, personally or both.

• A small company which does not benefit from a packaged email system which can synchronize both company email/schedule and company mobile devices.

Schedule 360 Domain• Phone & Tablet Manufacturers:

• At first offering the software will function on Apple products as this gives the company the best opportunity to gain a foothold in the market

• Email:• The application will be compatible with the most widely

used emails

Schedule 360 WRS ProcessWRS

◦ W Problem Goal Improved understanding of the Domain, Stakeholders,

Functional and Non-Functional Objectives

◦ RS Functional RS – Improved understanding of Software System

Requirements: FRs Non-functional RS -Improved understanding of Software

System Requirements: NFRs

Schedule 360 Functional Requirements• Requirement: The application shall be compatible

with all existing electronic calendars.• Issue description: A problem exists creating an

application that is compatible with all possible electronic calendars in existence

• Options: One option to reduce this problem is to identify the calendars that are widely used and limit the compatibility to these popular calendars

• Decision and Rationale: The application will now be compatible with the following calendars: Outlook, Google, Yahoo, and Lotus Notes. The rationale is that these are the most widely used calendars.

Schedule 360 Functional RequirementsRequirement: The application shall allow the user

to create appointments◦ Issue description: A problem exists creating the

appointments because there are currently no functional requirements defining what fields are required for an appointment

◦ Options: An option is to define the common fields required when creating the appointment

◦ Decision and Rationale: Create additional functional requirements to clearly define the field required

Schedule 360 Non-Functional Requirements

• The software shall be compatible on smartphones with wireless internet connectivity.• Issue description: What defines compatibility?

• Options: Use better definition of compatibility.

• Decision and Rationale: The software designers will need a definition of compatibility in order to ensure it can be downloaded on desired devices.

Schedule 360 Non-Functional Requirements

• The software shall perform greater than 95% of its computations in the cloud.• Issue description: Why is there a percentage metric for

computation? It would be more relevant to use power consumption as the metric.

• Options: Convert the percentage computation to a power consumption requirement.

• Decision and Rationale: The percentage requirement is arbitrary. Limiting the power consumption in terms of watts per hour is a better requirement.

Schedule 360 WRS ResultsThe requirements have been improved to include:

◦ Specific Phone and Tablet Manufacturers are specified

◦ Phone service providers are specified

◦ 10 Functional Requirements have been refined

◦ 15 Non-Functional Requirements have been refined

Refinement is an on-going process…

Questions?