Protyotyping. November 10, 2011

Transcription

1 Protyotyping November 10, 2011

2 Vision and Mission Vision Mission The world's leading association for Business Analysis professionals Develop and maintain standards for the practice of business analysis and for the certification of its practitioners IIBA is an international not-for-profit professional association for business analysts. (C) International Institute of Business Analysis

3 Tom Karasmanis IIBA Product Manager Tom Karasmanis is a Senior Consultant with 25 years' experience in Information Technology, including roles as a Business Architect, Business/Systems Analyst, Project Leader, Technical Architect, and Software Engineer. He has worked in publishing, healthcare, public sector, banking, financial services, insurance, supply chain, telecommunications, and retail. Tom served as Chief Architect of the IIBA from 2009 to He is currently IIBA Product Manager of Being a BA: Technical Excellence and Vendor Showcase. Tom is a management consultant in business architecture and business analysis, assisting organizations to build or improve their BA practices. He speaks regularly at international conferences. Tom holds a Bachelor of Applied Science in Chemical Engineering from the University of Toronto and is active in the business analysis and business architecture communities. (C) International Institute of Business Analysis 3

4 Outline Introductions and Housekeeping 12:00 Vendor Presentations 12:05 edev Technologies 12:05 irise 12:20 TechnoSolutions 12:35 Questions and Answers 12:50 Close 12:59 Extended Q&A 1:00 International Institute of Business Analysis 4

5 Question and Answer How to Ask Questions Use the Question box to ask questions. Selected questions will be answered at the end, but you can ask at any time. Include the vendor s name if you want a specific vendor to respond. Short, specific questions, please! Asif Sharif IIBA Host Tom Karasmanis Eniola Alabi International Institute of Business Analysis Ashu Potnis 5

6 Every building is a prototype. No two are alike. PROTOTYPING -- Helmut Jahn (C) International Institute of Business Analysis 6

7 General Characteristics Early Partial functionality / simplified view Purpose To test a concept or improve understanding (C) International Institute of Business Analysis 7

8 Purpose (9.22.1) Details user interface requirements and integrates them with other requirements such as use cases, scenarios, data and business rules Stakeholders often find prototyping to be a concrete means of identifying, describing and validating their interface needs (C) International Institute of Business Analysis 8

9 Some Synonyms BABOK v2 Storyboarding Navigation Flow Paper Prototyping Screen Flows Industry Wireframes Visual Model Screen Shots (C) International Institute of Business Analysis 9

10 Categories (9.22.2) 1. Functional Scope A horizontal prototype models a shallow, and possibly wide view of the system s functionality Typically no business logic running behind the visualization A vertical prototype models a deep, and usually narrow slice of the entire system s functionality (C) International Institute of Business Analysis 10

11 Categories (9.22.2) 2. Usage Throughout SDLC A Throw-away prototype seeks to quickly uncover and clarify interface requirements Usually discarded when the final system has been developed Focus is on functionality not easily elicited by other techniques or is difficult to understand (C) International Institute of Business Analysis 11

12 Categories (9.22.2) 2. Usage Throughout SDLC An Evolutionary or Functional prototype extends initial interface requirements into a fully functioning system and requires a specialized prototyping tool or language This prototype is the foundation for a working software application (C) International Institute of Business Analysis 12

13 Prepare for Prototyping ( ) 1. Determine the prototyping approach Know the purpose of the prototype! Throw-away / Evolutionary / Functional Vertical / Horizontal 2. Identify functionality to model (C) International Institute of Business Analysis 13

14 Prototype ( ) Iterative process The initial efforts outline the high-level views Subsequent iterations can add detail Initial focus is an end-to-end understanding of the interface flow Add details as appropriate to the work (C) International Institute of Business Analysis 14

15 Evaluate the Prototype ( ) Trace prototype elements to user requirements such as use cases, processes, data and business rules Validate that the prototype represents the user s needs Review with users scenarios Match to requirements such as use cases, data, business rules (C) International Institute of Business Analysis 15

16 Advantages ( ) Visual, concrete, closer to reality than traditional requirements Early user interaction and feedback Inexpensive Test feasibility (C) International Institute of Business Analysis 16

17 Disadvantages ( ) Can get bogged down in details and design Unrealistic expectations Performance Delivery date May shift focus from requirements to design (C) International Institute of Business Analysis 17

18 REQUIREMENTS Lifecycle Managment Best Tools Award Seilevel Consulting Austin Texas PROJECT SUCCESS CONTACT Information LOWER COSTS Copyright edev Technologies 2011

19 REQUIREMENTS Lifecycle Managment Continuous Process Improvement promotes Greater Project Success Elicitation Gather requirements of a system from stakeholders Collaboration Work together to review, enhance and approve requirements Definition Finding, documenting, organizing, and tracking requirements Validation Seek out and correct ommissions, errors, vague language Management Ensure that the latest version is used, and relationships are defined.

20 COLLABORATIVE RLM Ecosystem

21 REQUIREMENTS Validation Know Its Right Challenges Excessive Rework Getting Buy-in Ambiguous Requirements Partial & Orphan Requirements Stakeholder Unavailability &-or Unwillingness to read documents Get it Right the First Time High Fidelity Simulation Bring it all Together Mock up Automated Validation Specification Checker Test Case Automation

22 DEMO Requirements Validation Lifecycle Define Requirements Publish/Share & Collect Feedback Define User Scenario Fine Tune Simulation Generate Simulation

23 Define Application Usage Scenario Helps keep simulation in sync with use case, test case and diagrams

24 Invoke Simulation Wizard Rapidly define interactive mockups Updates in simulation wizard will update the usage scenarios Context Sensitive Help Auto Generated Mock up Reuse data Definition from the Domain Model Define Navigation Annotate Mock up Take URL Snapshot & Annotate

25 CONTEXT Sensitive Help Autogenerated help with all related information Screen Summary Screen thumbnail Navigation Data info on the screen Related Requirements and Business Rules

26 SIMULATION DESIGNER High Fidelity Simulation Common Controls Layout Controls Drawing Controls Preview in browser Simulation Files Properties Panel Design Panel

27 SIMULATION DESIGNER Reuse Predefined Screen Templates

28 SIMULATION Player Provide Feedback to the Analyst

29 IMPLEMENTING integreat Product Options InteGREAT Professional Strategy/Risk, Glossary and Requirements/Rule Management Web Access for Collaboration (available) Team Foundation Server and Quality Center Integration integreat Premium Use case, Domain and Process Model Development Test Case Automation Automated Simulation integreat Ultimate Simulation Designer Decision Model Custom Data Extractor Cocomo II -Function Point Estimation

30 CONTACT Info Asif Sharif Chief Technologist Copyright edev Technologies 2011

31 irise Visualization November 10, 2011 Prepared for: Prepared by: Eniola Alabi Solutions Consultant irise 31 Company Confidential 2010 All rights reserved. irise Company Confidential 2010 All rights reserved

32 But the Way That Software is Defined Hasn t Changed in Over 30 Years! But the Way That Software is Defined Hasn t Changed in Over 30 Years!

33 Issue #1: Business Users Don t Know What They Want Until They See & Interact With It

34 Issue #2: Business Users Can t Interpret Text Specs., Use Cases, Screen Shots, etc.

35 The Impact is Dramatic Long cycle times Late stage rework Poor adoption Risky global sourcing Blown business plans Strained relationships

36 The Solution: Visualization

37 Visualization is the First Step Visualizations assembled at light speed by BAs as a first step No coding drag & drop Visualizations look, act & behave just like final software Business stakeholders get to test drive the application Use your current process Business acceptance done BEFORE coding Change management starts on day one of the project

38 What Can Be Visualized? Web 2.0 & Rich Internet Applications Desktop Apps & Enhancements Mobile Applications Packaged Applications

39 Value Delivered From the Start Get to market twice as fast with 30% less cost Global sourcing that really works Dramatically improved customer experience Accelerated business agility

40 10 Years of Market Leadership 500+ customers Broadest portfolio of industries World s first patents awarded for application simulation (2007, 2008, 2010) Most documented customer successes Global community of 10,000+ visualization authors & 25,000+ reviewers 3,000 successful projects Backed by Morgan Stanley Venture Partners & Deutsche Bank

41 Customer Success

43 irise Challenge for IIBA members Do you have a project in distress? Let the irise team build out a simulation for your stakeholders We will complete 1 free simulation based on your requirements What you need to do? Be the first 10 IIBA members who send us their requirements your project outline with your requirements to ealabi@irise.com What we will do for you? Return your first simulation within 24 hours of reviewing the specifications We will also give you a 1 hour mentoring session

45 Prototyping 9.22 in IIBA BABOK

46 Requirements docs can get too big and difficult to understand!

47 Can t get good feedback if your users are not engaged

48

49 Surprise!

50 Prototyping & Simulation

51

52 How can help you with Prototyping and Simulation?

53 Use Cases Business Rules Requirements Trace Links Business Process Diagrams Screen Mockups Open Source

54 Collaborate across cubicles or across continents San Francisco New York London Sydney Windows Desktop Client Web Access and Collaboration Offline Client

55 Requirements User Stories Use Case Scenarios Entity-Attributes Business Process Modeling End-to-End Traceability Test Cases Online Reviews and Approvals And more

56 Prototype Screen Flows

57 Use widgets to build Sketch Style Screen Mockups

58 Sketch Style Preview

59 Define Entities and Attributes

60 Place Data Fields on Screen Mockups

61 Use Styles to standardize look and feel

62 View Screen Mockups in Web Browser

63 Users can add review comments

64 Users can add review comments

65 Users can simulate applications in their Web Browsers and give high quality feedback

66 Track & Visualize End-to-End Traceability All the way to Screen Mockups

67 Screen Prototype Data Attributes Look & Feel Use Case Scenarios Requirement s Screen Mockup Application Navigation Business Rules System Behavior

68 Integrations Quality Center Team System (TFS) TopTeam Open API

69 Learn more or try it yourself TopTeamAnalyst.com "I am enjoying using TopTeam. It allows me more creative time, instead of document formatting time, so my analysis is better and more detailed." Carl Knowlan Senior Analyst & Product Manager Houston, Texas

70 Contact Information Register for more webinars on the Professional Development page of our website under Webinars. IIBA.org/PD community.theiiba.org Asif Sharif edev Technologies Eniola Alabi irise Ashu Potnis TechnoSolutions International Institute of Business Analysis 70

71 Contact Information Register for more webinars on the Professional Development page of our website under Webinars. IIBA.org/PD community.theiiba.org Asif Sharif edev Technologies Eniola Alabi irise Ashu Potnis TechnoSolutions International Institute of Business Analysis 71