PRESENTATION TITLE SpeechTEK 2007 Session: Communication Strategies for Speech Projects (B105) Monday, August 20 2007, 4:15-5:00 p.m. August Does your.

Slides:



Advertisements
Similar presentations
Systems Development Environment
Advertisements

Multimedia Specification Design and Production 2013 / Semester 1 / week 7 Lecturer: Dr. Nikos Gazepidis
1 Information Systems Development (ISD) Systems Development Life Cycle Overview of Analysis Phase Overview of Design Phase CP2236: Information Systems.
Information Resources Management January 23, 2001.
CHAPTER TWO Object Oriented System Analysis and Design 1.
Sharif University of Technology Session # 3.  Contents  Systems Analysis and Design Sharif University of Technology MIS (Management Information System),
<<replace with Customer Logo>>
Software Modeling SWE5441 Lecture 3 Eng. Mohammed Timraz
1 The Database Application Development Process The Database Application Development Process.
GAI Proprietary Information
4.1 Blended approaches: Information Engineering IMS Information Systems Development Practices.
Introduction To System Analysis and Design
Ch 4 The Process page 1CS 368 Building Software is Difficult often delivered late often over budget always with errors must be a custom solution complexity.
Development Processes UML just is a modeling technique, yet for using it we need to know: »what do we model in an analysis model? »what do we model in.
© Prentice Hall CHAPTER 9 Application Development by Information Systems Professionals.
SYSTEMS DEVELOPMENT Phases, Tools, and Techniques
1 IS 4420 Database Fundamentals Chapter 2: Database Development Process Leon Chen.
Chapter 1 The Systems Development Environment 1.1 Modern Systems Analysis and Design Third Edition.
9 1 Chapter 9 Database Design Database Systems: Design, Implementation, and Management, Seventh Edition, Rob and Coronel.
The database development process
Systems Development (SD) Presentation Michael Webb IT Director for Medicaid Utah Department of Health UDOH Informatics Brownbag August.
Agile software development is a group of software development methodologies based on iterative and incremental development, where requirements and solutions.
Handouts Software Testing and Quality Assurance Theory and Practice Chapter 11 System Test Design
> Blueprint Kickoff >. Introductions Customer Vision & Success Criteria Apigee Accelerator Overview Blueprint Schedule Roles & Responsibilities Communications.
1 A Practical Rollout & Tuning Strategy Phil Shinn 08/06.
Complete and Integrated Lifecycle Management. Challenges 1.
Introduction To System Analysis and design
The Database Development Process
CIS 321—IS Analysis & Design
Appendix 2 Automated Tools for Systems Development © 2006 ITT Educational Services Inc. SE350 System Analysis for Software Engineers: Unit 2 Slide 1.
1COM6030 Systems Analysis and Design © University of Sheffield 2005 COM 6030 Software Analysis and Design Lecture 4 - System modelling Dr Richard Clayton.
Pertemuan 5 Pengembangan Teknologi Informasi Matakuliah: H0402/PENGELOLAAN SISTEM KOMPUTER Tahun: 2005 Versi: 1/0.
Chapter 2 The process Process, Methods, and Tools
Managing the development and purchase of information systems (Part 1)
Chapter 1: The Object-Oriented Systems Development Environment Object-Oriented Systems Analysis and Design Joey F. George, Dinesh Batra, Joseph S. Valacich,
المحاضرة الثالثة. Software Requirements Topics covered Functional and non-functional requirements User requirements System requirements Interface specification.
Demystifying the Business Analysis Body of Knowledge Central Iowa IIBA Chapter December 7, 2005.
1-1 © Prentice Hall, 2007 Chapter 1: The Object-Oriented Systems Development Environment Object-Oriented Systems Analysis and Design Joey F. George, Dinesh.
MD Digital Government Summit, June 26, Maryland Project Management Oversight & System Development Life Cycle (SDLC) Robert Krauss MD Digital Government.
Systems Design Approaches The Waterfall vs. Iterative Methodologies.
Software Requirements Engineering: What, Why, Who, When, and How
1 Introduction to Software Engineering Lecture 1.
Information Systems Engineering. Lecture Outline Information Systems Architecture Information System Architecture components Information Engineering Phases.
Notes of Rational Related cyt. 2 Outline 3 Capturing business requirements using use cases Practical principles  Find the right boundaries for your.
Review of Software Process Models Review Class 1 Software Process Models CEN 4021 Class 2 – 01/12.
Software Engineering Prof. Ing. Ivo Vondrak, CSc. Dept. of Computer Science Technical University of Ostrava
ECE450 - Software Engineering II1 ECE450 – Software Engineering II Today: Introduction to Software Architecture.
Software Maintenance Speaker: Jerry Gao Ph.D. San Jose State University URL: Sept., 2001.
Business Analysis. Business Analysis Concepts Enterprise Analysis ► Identify business opportunities ► Understand the business strategy ► Identify Business.
Connecting with Computer Science2 Objectives Learn how software engineering is used to create applications Learn some of the different software engineering.
The principles of an object oriented software development process Week 04 1.
Software Engineering Lecture # 1.
Software Development Life Cycle (SDLC)
Introduction to Software Engineering 1. Software Engineering Failures – Complexity – Change 2. What is Software Engineering? – Using engineering approaches.
Public Management Information Systems System Analysis & Design Saturday, June 11, 2016 Hun Myoung Park, Ph.D. Public Management & Policy Analysis Program.
Configuration Control (Aliases: change control, change management )
Chapter 2- Software Development Process  Product Components  Software Project Staff  Software Development Lifecycle Models.
SOFTWARE DEVELOPMENT Presented By : Emporiumtech This presentation is brought you by
Methodologies and Algorithms
Chapter 1: Introduction to Systems Analysis and Design
Chapter 1: Introduction to Systems Analysis and Design
Topic for Presentaion-2
Software Life Cycle Models
Software Development Life Cycle
Engineering Processes
Proposed Software Development Process
Delivery of Solutions Information Management
Rapid Application Development (JAD)
Chapter 1: Introduction to Systems Analysis and Design
OU BATTLECARD: Oracle SOA Training & Certification
Presentation transcript:

PRESENTATION TITLE SpeechTEK 2007 Session: Communication Strategies for Speech Projects (B105) Monday, August , 4:15-5:00 p.m. August Does your customer know what they are signing off? Maria Aretoulaki (PhD) Head of Speech Design

2 Does your customer know what they are signing off? Maria Aretoulaki (PhD) #1 PROBLEM “Difficult” customers! Worried customers! #2 PROBLEM People with different skill sets People with different interpretations

3 Does your customer know what they are signing off? Maria Aretoulaki (PhD) #1 PROBLEM “Difficult” customers!  Never-ending Change Requests  Constant changes to the scope  Costing time and money  Accusations of non-compliance to original design  Marring the credibility of the service provider  Losing trust  losing business Worried customers!  ‘Will I get what I paid for?’  Anxious about the unknown

4 Does your customer know what they are signing off? Maria Aretoulaki (PhD) #2 PROBLEM People with different skill sets  Non-technical people  Customer-side: Project managers, Business unit managers, call centre managers  Provider-side: (pre-)sales engineers, account managers, Project managers  Technical people  Customer-side: IT managers, database specialists  Provider-side: VUI designers, architecture specialists, application developers People with different interpretations Requirements  Design A for Non-techies  Design B for Techies

5 Does your customer know what they are signing off? Maria Aretoulaki (PhD) GOAL Manage customer expectations  Specify what should be delivered unambiguously  Ensure customer reviews and consensus on system functionality early on Intertwine design with development  Make transition smoother from Spec and rough design to Implemented Call-flow  Speed up both the design & the development processes

6 Does your customer know what they are signing off? Maria Aretoulaki (PhD) SOLUTION Standardise customer documentation –Different level of detail for different audiences: pre-sales pitch or spec for Java developers? –Document templates Standardise Project communication –Involve the customer early on in the design –Intertwine VUI design with implementation Standardise Translation from Specs to Design

7 Does your customer know what they are signing off? Maria Aretoulaki (PhD) METHODOLOGY Combine two extremes: 1.Top-down approach (standard) –high-level diagram of functionality AND 2.Bottom-up approach –collect example dialogues together with the Customer at a Discovery Workshop   Infer + Specify functionality

8 Does your customer know what they are signing off? Maria Aretoulaki (PhD) STANDARDISE Documentation! Represent system functionality, business logic and call-flows : –Incrementally, showing different level of detail –depending on target audience (Pre)-sales / Customer Business Unit managers / PMs Customer IT dept, Call Centre Leaders Application developers, database experts –In a modular fashion Use Document Templates –well-specified and fixed –Start from the abstract and go to the more specific

9 Does your customer know what they are signing off? Maria Aretoulaki (PhD) 3-tier modular & incremental representation High-Level call flow Abstract General functionality, business logic, basic tasks Business, Sales Project managers Macro- call flow Detailed Processes, interactions among modules, Interactions with DB IT managers, Call Centre Managers Micro- call flow Very detailed System prompts, Error handling, Grammar design, References to connecting modules Application Developers, VUI designers, DB specialists TOP-DOWN approach

10 Does your customer know what they are signing off? Maria Aretoulaki (PhD) High-level call flow (abstract)

11 Does your customer know what they are signing off? Maria Aretoulaki (PhD) Macro-call flow (detailed)

12 Does your customer know what they are signing off? Maria Aretoulaki (PhD) Micro-call flow (very detailed!) Start FinishedOrStartAgain SubDialog Start Again Return Timeout/Error 3610_Finished Or Start Again 2950_ Check_No. Of Failures <2 > 1 Finished 1310_OK Hope you ring again

13 Does your customer know what they are signing off? Maria Aretoulaki (PhD)

14 Does your customer know what they are signing off? Maria Aretoulaki (PhD) STANDARDISE Project Communication! Involve the customer early on in the design –Design Workshops –Example dialogues showing all case scenarios  BOTTOM-UP approach Intertwine VUI design with implementation –Proof of concept –Design and test

15 Does your customer know what they are signing off? Maria Aretoulaki (PhD) Standard SPEECH PROJECT CYCLE Request for Proposal (Customer) -> SOW (Pre-sales) Discovery Workshop (Pre-Sales+PS+Customer) -> Requirements Specification (PS) After review, VUI Design & Persona Proposal (VUI Designer) After approval, Functional Design Specification (VUI Designer, Architect) Official Sign-off (Customer) Prototype Development (VUI Designer, System Architect, Application Developer) WOZ testing / Usability Testing (VUI Designer, Customer) Detailed Application Design (VUI Designer, System Architect) Official Sign-off (Customer) Implementation (Application Developer) FAT testing (Testers) Installation CAT testing (Customer) / UAT testing (End-Customer) Tuning (VUI Designer, System Architect, Application Developer)

16 Does your customer know what they are signing off? Maria Aretoulaki (PhD) DesignTest&TuneImplement Sign Off

17 Does your customer know what they are signing off? Maria Aretoulaki (PhD) STANDARDISE Project Communication! Involve the customer early on in the design –Design Workshops –Example dialogues showing all case scenarios  BOTTOM-UP approach Intertwine VUI design with implementation –Proof of concept –Design and test STANDARDISE Translation from Specs to Design!

18 DesignTest&TuneImplement Sign Off Does your customer know what they are signing off? Maria Aretoulaki (PhD) DesignTest&TuneImplement Sign Off Test& Tune

19 Does your customer know what they are signing off? Maria Aretoulaki (PhD) Dialogue Capture Requirements Capture Customer Review Back into Dialogue Capture Call Flow Standardise Translation from Specs to Design

20 Does your customer know what they are signing off? Maria Aretoulaki (PhD) The way forward: Collaborative Design! rather than insular and cryptic design Design and Test together with the customer (Proof-of-concept)  Clarity, lack of ambiguity  confidence, consent  Fewer misunderstandings  Any drastic changes limited to –BEFORE full-length official and signed-off documentation –BEFORE prototype deployment  minimisation of change requests hindering project sign-off  No accusations that what was delivered is not what was signed- off  SHORTER SPEECH PROJECT LIFECYCLES!!

21 Does your customer know what they are signing off? Maria Aretoulaki (PhD) New School: VUI DESIGN-cum-IMPLEMENTATION! –Design and Implement concurrently  Better Coverage of functionality  Smooth transition from Specs to design to development  Congruence between call flow in spec and in SDK  Incremental and iterative System testing from the start  Automatic generation of test cases -- Document different level of detail for different people  Better code maintenance and adaptation post-project  Re-usability of design concepts and code  SHORTER SPEECH PROJECT LIFECYCLES!!