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

Slides:



Advertisements
Similar presentations
Synergy Distributed Meeting Scheduler(SDMS) TEAM:4 Rutvij Mehta Shruti Mehta Shveta Mupparapu Meghna Swetha Raguraman Rakesh Sanapala Venkata Jaganadh.
Advertisements

Copyright The Info-Tech Research Group Inc. All Rights Reserved. D1-1 by James M. Dutcher Strategic IT Planning & Governance Creation H I G H.
MICHAEL MARINO CSC 101 Whats New in Office Office Live Workspace 3 new things about Office Live Workspace are: Anywhere Access Store Microsoft.
Object-Oriented Analysis and Design LECTURE 3: REQUIREMENTS DISCIPLINE.
Requirements Specification Presented By: Code Shark Solutions 11/3/10.
IT Requirements Capture Process. Motivation for this seminar Discovering system requirements is hard. Formally testing use case conformance is hard. We.
Page - 1 Functional Overview: Users / Groups / Roles / Permissions Groups, Roles and Permissions will be established to match State Purchasing organization.
Systems Analysis and Design 9th Edition
Chapter 2.
Major Exam II Reschedule 5:30 – 7:30 pm in Tue Dec 5 th.
Analyzing the Business Case
Configuration Management
Lesson 10: IT Project and Program Management. Lesson 10 Objectives  Identify resources for technical data  Identify project management fundamentals.
Professor Michael J. Losacco CIS 1150 – Introduction to Computer Information Systems Application Software Chapter 3.
Change Request Management
Chapter 7: The Object-Oriented Approach to Requirements
Problems in handling NFR Term Paper (as-is) problem statement BY AJAYKUMAR ASWATHAPPA CS/SE 6361 EXECUTIVE.
Nary Subramanian Firmware Engineer Applied Technology Division Anritsu Company Richardson, TX. Lawrence Chung.
Phase II Instructor: Dr. Lawrence Chung Rachel Bock, Ruben Cavazos, Chih-Lin Cheng, Victor Isbell, Swathi Kandimalla, Nikhil Mishra, Amy Polcari, Ramon.
Team Crutch. Vision Statement Team crutch aims to develop portable, inexpensive, user-friendly software for the Android platform that mitigates communication.
RUP Requirements RUP Artifacts and Deliverables
1 SYS366 Week 3 Lecture 1 Introduction to Requirements Gathering: Part 1.
® IBM Software Group © 2006 IBM Corporation Rational Software France Object-Oriented Analysis and Design with UML2 and Rational Software Modeler 06. Requirements.
MSF Requirements Envisioning Phase Planning Phase.
Copyright 2002 Prentice-Hall, Inc. Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 6 Initiating.
Business Case Justification System Planning
Virtual OSGi Framework and Telecommunications Sam Supakkul Yotta Networks Digital Pockets, LLC Dallas, Texas Lawrence Chung Dept.
Chapter 10 Information Systems Analysis and Design
Software Engineering Management Lecture 1 The Software Process.
Requirements Specification for Lab3 COP4331 and EEL4884 OO Processes for Software Development © Dr. David A. Workman School of Computer Science University.
Software Requirements (Advanced Topics) “Walking on water and developing software from a specification are easy if both are frozen.” --Edward V Berard.
ISYS 562 Microcomputer Business Applications David Chao.
DEV234 Project Management For.NET Developers Marc Gusmano Director of Emerging Technologies The Information Management Group.
Ch 4 - Learning Objectives Scope Management You should be able to: n Discuss the relationship between scope and project failure n Describe how strategic.
Synergy Meeting Scheduler System T-squared, S-cubed TJ Andrews Thriveni Movva Sadequa Azam Sama Malik Scott Denson.
Systems Analysis and Design 8 th Edition Chapter 2 Analyzing the Business Case.
1 Final Status Report Sonali PagadeNibha Dhagat David Ziman Reginald Bradshaw II Sebastian Schagerer Janet Xu Phan Marvel Electronics & Home Entertainment.
R.O.S.E.S. Preliminary Design Presented By: Code Shark Solutions 12/8/10.
Software Production ( ) First Semester 2011/2012 Dr. Samer Odeh Hanna (PhD)
1 Software Requirements l Specifying system functionality and constraints l Chapters 5 and 6 ++
TieFlow Process Editor CAPSTONE TEAM # 2 03/04/2009CSCI Spring 2009.
CT1404 Lecture 2 Requirement Engineering 1 1. Today's Lecture Definition of a Software Requirement Definition of Software Requirements Management Characteristics.
Software Requirements: A More Rigorous Look 1. Features and Use Cases at a High Level of Abstraction  Helps to better understand the main characteristics.
COTS-Aware Requirements Engineering and Software Architecting
Introduction to Project Management.  Explain what a project is?  Describe project management.  Understand project management framework.  Discuss the.
1 Project Planner Michael Adcock & KFTF Research Team 1/24/06.
 SAP AG 2007, SAP CSUN 2007 Conference Presentation / 1 Presented by Team “Call of Duty” 29 th April 2010 CS 6361, University of Texas At Dallas.
Foundations of Geospatial System Development Todd S. Bacastow Professor of Practice for Geospatial Intelligence John A. Dutton e-Education Institute The.
Requirement engineering & Requirement tasks/Management. 1Prepared By:Jay A.Dave.
ANALYSIS PHASE OF BUSINESS SYSTEM DEVELOPMENT METHODOLOGY.
Integrating FRs and NFRs: A Use Case and Goal Driven Approach Sam Supakkul Network Surveillance Systems MCI Lawrence Chung Dept. of.
SynergySoft™ Distributed Meeting Scheduler Requirements Review Yasaman Haghpanah Ravindra Rudraraju Sowjanya Sakruti Jim Whitaker.
Requirements Specification for Lab1 COP4331 and EEL4884 OO Processes for Software Development © Dr. David A. Workman School of Computer Science University.
HighImpact Soft Final Presentation Dare Famodimu Eric Deshazer Sergio Loza Scott Willock.
HighImpactSoft 2010 Organizing a Better Future. Agenda Specify Goals ScopeDefinitions Process Model Preliminary Requirements Issues and solutions TraceabilityPrototype.
SUPERVISOR CONSULTATION Consult 1: 30 September 2015 Team Bonté to be kind enough to, to be good enough to.
Waste Management Inspection Tracking System (WMITS)
NAVSEA Liaison Scott Huseth Faculty Advisor Dr. Jiang Guo Team Members Areg Abcarians David Ballardo Niteen Borge Daniel Flores Constance Jiang June 3,
Systems Analysis & Design 7 th Edition Chapter 2.
CS 160 and CMPE/SE 131 Software Engineering May 3 Class Meeting Department of Computer Science Department of Computer Engineering San José State University.
Page 1 An Overview of The COTS-Aware Requirements Engineering and Software Architecting Project (CARE/SA) The University of Texas at Dallas Department.
SharePoint 101 – An Overview of SharePoint 2010, 2013 and Office 365
Change Request Management
Software Engineering Management
Chapter 4 – Requirements Engineering
Requirement Engineering
Advanced features iNaturalist
An easy-to-use memory management smartphone application
This presentation has been prepared by Vault Intelligence Limited (“Vault") and is intended for off line demonstration, presentation and educational purposes.
CS/SE ADVANCED SOFTWARE ARCHITECTURE AND DESIGN FALL 2015
Presentation transcript:

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

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

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.

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.

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

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

Project Specification (NFR)

Project Specification (FR)

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

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%

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

Process Specification (NFR)

Process Specification (FR)

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.).

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.

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.

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.

Traceability

Functional Example Non-Functional Example Test Cases

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

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

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.

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

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