Presentation is loading. Please wait.

Presentation is loading. Please wait.

SUBMITTED TO: DR. LAWRENCE CHUNG ASSOCIATE PROFESSOR, DEPARTMENT OF COMPUTER SCIENCE, THE UNIVERSITY OF TEXAS AT DALLAS, RICHARDSON, TX- 75080 SUBMITTED.

Similar presentations


Presentation on theme: "SUBMITTED TO: DR. LAWRENCE CHUNG ASSOCIATE PROFESSOR, DEPARTMENT OF COMPUTER SCIENCE, THE UNIVERSITY OF TEXAS AT DALLAS, RICHARDSON, TX- 75080 SUBMITTED."— Presentation transcript:

1 SUBMITTED TO: DR. LAWRENCE CHUNG ASSOCIATE PROFESSOR, DEPARTMENT OF COMPUTER SCIENCE, THE UNIVERSITY OF TEXAS AT DALLAS, RICHARDSON, TX SUBMITTED BY: STEVEN FORD GILBERT ISLAS PAUL WASILEWSKI OBI OGBANUFE MICHAEL MURPHY TEAM WEBSITE: Schedule360

2 Agenda Problem Definition Scenario Goal Vision Statement Project Specification Budget / Scope Creep Process Specification Requirements and WRS refinement Traceability Test Cases Mock-up

3 Problem Statement The problem of multiple schedules without a source to consolidate into a single form of media affects Business Professionals with lives outside of work. The impact of which is an unawareness of all appointments and various other commitments.

4 Scenario Steven is the Sales Director of a startup of 20 employees and a devoted husband and father of 2. Steven has important meeting with a possible customer that is rescheduled after he has already left for the day. Steven did not receive the reschedule notification due to family commitments outside of work. Steven is late to the meeting the next morning and misses out on a big opportunity for new business. The startup’s success is now in jeopardy due to the missed opportunity.

5 Goal Consolidate all schedules into one location and allow user to modify them at their convenience.

6 Project Specification The project spec for the creation of Schedule360 Using  NFR Framework  SIG (Softgoal Interdependency Graph) – Star UML  FR Framework  UML – Visual Paradigm for UML

7 Project Specification (NFR)

8 Project Specification (FR)

9 Schedule / Budget Identified roles for each of the 5 team members and based their hourly rates on industry standards Multiplied that rate at 5 days/wk 8 hrs/day over course of semester leaving slack in schedule Core budget came out to be $150,000

10 Slack Time / Scope Creep Measured budget needed to continue project to the end of semester Given the schedule for the project the maximum allowable amount of scope creep was measured to 17%

11 Process Specification The process for the creation of Schedule360 Using  NFR Framework  SIG (Softgoal Interdependency Graph)  FR Framework  IDEFO  Class Diagram

12 Process Specification (NFR)

13 Process Specification (FR)

14

15 Requirement (FR) The application shall allow the user to create appointments The application shall allow users to synchronize information between the application and all other existing electronic calendars (personal, work, etc.).

16 WRS Requirement Refinement (FR) Functional Refinement  There is no definition of what fields need to be in the appointment.  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.  Revised functional requirement  The appointment shall allow the creator to specify the subject of the appointment, location, start time, end time, etc.

17 Requirement (NFR) The software shall be compatible with the following calendars: Outlook, Google, Yahoo, and Lotus Notes. The software shall be compatible as an application on the Apple iPhone version 3GS and newer.

18 WRS Requirement Refinement (NFR) Non-Functional Refinement  The software shall be available for download from a database containing the Schedule 360 smartphone application.  Issue description: How can availability be defined better to ensure users have easy access to the application.  Options: Keep or modify the current requirement.  Decision and Rationale: Need to be specific on the term “available for download” or describe where it is available.  Revised non-functional requirement  The software shall be available for download from the iPhone App Store.

19 Traceability

20 Functional Example Non-Functional Example Test Cases

21 Synchronizing the Device Select ‘Synchronize Devices’ to Sync. Home Calendar Settings Help More Synchronize Devices

22 Viewing Calendar Select ‘Calendar’ Home Calendar Settings Help More Synchronize Devices

23 Editing Appointments Select the appointment you would like to edit from your calendar. Select which fields to edit. Select ‘Delete Event’ to remove it from the calendar. Select ‘Cancel’ to return to the calendar.

24 Vision Document Consolidated overall plan for developing Schedule 360 application in one document.  Product Positioning  Stakeholder and User Descriptions  Product Overview  Functional/Non-Functional Requirements  Product Features and Constraints  Quality Ranges  Precedence and Priorities  Product Requirements  Documentation Requirements

25 Summary Project Development Defined a Problem  Illustrated using a scenario  Developed a goal of solving the problem Created a Vision of how to achieve goal Refined vision into project and process specification  Defined scope of what project plans to achieve (Project Spec)  Developed & organized process to solve the problem (Process Spec) Defined requirements and refined them  Tracked and Tested these requirements Used information to develop application and achieved goal


Download ppt "SUBMITTED TO: DR. LAWRENCE CHUNG ASSOCIATE PROFESSOR, DEPARTMENT OF COMPUTER SCIENCE, THE UNIVERSITY OF TEXAS AT DALLAS, RICHARDSON, TX- 75080 SUBMITTED."

Similar presentations


Ads by Google