Successfully reported this slideshow.

Improve Your Requirements With Visual Models

1,460 views

Published on

This presentation discussed the value of visual requirements models, providing a few impactful models that you can use immediately on any project to improve your requirements.

Published in: Technology, Business
  • Be the first to comment

Improve Your Requirements With Visual Models

  1. 1. Immediately Improve Your Software Requirements with Visual Models © Seilevel, Inc. All rights reserved
  2. 2. Joy Beatty, VP Seilevel joy.beatty@seilevel.com & Tony Higgins, VP Blueprint tony.higgins@blueprintsys.com © Seilevel, Inc. All rights reserved
  3. 3. Model business processes to identify requirements Model UI screen display and behavior requirements Map requirements to processes to identify missing requirements © Seilevel, Inc. All rights reserved
  4. 4. Meet Blue © Seilevel, Inc. All rights reserved
  5. 5. Why do we need to model information? 7±2 © Seilevel, Inc. All rights reserved
  6. 6. We developed a language of requirements models (RML®) that are easy to create and consume Business Objectives Model Business Data Diagram Roles & Permissions Matrix State Table Org Chart Objective Chain Key Performance Indicator Model Use Case Data Dictionary Process Flow Data Flow Diagram System Flow Feature Tree © Seilevel, Inc. All rights reserved DAR Model Requirements Mapping Matrix Decision Tree UI Flow System Interface Table Decision Table State Diagram Report Table Ecosystem Map
  7. 7. The RML models are categorized to help you figure out when to use them Objective Models describe the business value of the system People models show who uses the system and how System models detail the interaction between systems © Seilevel, Inc. All rights reserved Data models focus on the information in the system and how its modified
  8. 8. There are 22 RML models so we are going to focus on a “quick start” set of models you can use immediately Objectives People Business Objectives Model Org Chart Objective Chain Key Performance Indicator Model Feature Tree © Seilevel, Inc. All rights reserved Requirements Mapping Matrix Process Flow Use Case Roles & Permissions Matrix Systems Ecosystem Map Display Action Response Model System Flow UI Flow System Interface Table Decision Tree Decision Table Data Business Data Diagram Data Flow Diagram Data Dictionary State Table State Diagram Report Table
  9. 9. This is an approach that most projects can implement at any stage for immediate improvement © Seilevel, Inc. All rights reserved
  10. 10. Blueprint Requirements Definition & Management Platform Simulation Author Business Process Diagram Document Generation Validate Textual Requirement Use Case Diagrams Online Review/Approve Collaborate Use Cases Inline Discussions Traceability Version/Baseline Notifications Generic Diagram Manage Glossaries Reuse Visual Differencing Requirements Sharing Storyboards User Interface Mockups Actors Domain Diagram Test Generation Coverage Monitor Visio Import/Export Cost / Status Progress Consolidated Dashboard Excel Import/Export Personal Activity Center Word Import/Export HP ALM/Quality Center Integrate © Seilevel, Inc. All rights reserved Central System of Record Administer Highly Configurable Role-Based Security Microsoft TFS
  11. 11. Introduction to Blueprint © Seilevel, Inc. All rights reserved
  12. 12. Create Process Flows for all your critical business processes © Seilevel, Inc. All rights reserved
  13. 13. One Example Process Flow: Add to Cart © Seilevel, Inc. All rights reserved
  14. 14. Create a Requirements Mapping Matrix (RMM) to map process steps to requirements 1. Add your steps to the matrix 2. Add your requirements to the matrix © Seilevel, Inc. All rights reserved
  15. 15. Create Display-Action-Response (DAR) models instead of a typical screen shot and long list of UI requirements © Seilevel, Inc. All rights reserved Requirements Document • System shall have fields for first name, middle initial and last name. • System shall display a name if there is one in the stored profile. • System shall require name is completed. • System shall have a field for position or title. • System shall require title is completed. • System shall display a position or title if there is one in the stored profile. • System shall have fields for email and alternate email addresses. • System shall display an email address if there is one in the stored in the profile. • System shall require email and alternate email addresses are completed. • System shall have a field for a daytime phone number. • System shall display a phone number if there is one in the stored profile. • System shall require phone number is completed. • System shall validate the phone number is all digits when user exits the field. • System shall display an error message if phone number is not all digits. • System shall have a field for a fax number. • System shall require fax is completed. • System shall display a fax number if there is one in the stored profile. • System shall validate the fax number is all digits when user exits the field. • System shall display an error message if the fax number field is not all digits. • System shall have two fields for a street address. • System shall require the first street address field is completed. • System shall display an address if there is one in the stored profile. • System shall have a field for city. • System shall require the city field is completed. • System shall display a city if there is one in the stored profile. • System shall have a field for state. • System shall display a state if there is one in the stored profile. • System shall require the state field is completed. • System shall have a field for zip code. • System shall display a zip code if there is one in the stored profile. • System shall require the zip code field is completed. • System shall look up zip code in the list of zip codes that span counties and display a county selection if it does span counties. • System shall have a submit option. • System shall save contact information updates to the order when the submit option is selected. • System shall validate required fields are completed when the submit is selected.
  16. 16. DARs have screens and element tables to describe display and behavior requirements © Seilevel, Inc. All rights reserved
  17. 17. Add to Cart DAR © Seilevel, Inc. All rights reserved
  18. 18. Add the DAR models to the RMM to ensure that processes can be completed within the screens You can add additional models to further organize your requirements © Seilevel, Inc. All rights reserved
  19. 19.    Model business processes to identify requirements Model UI screen display and behavior requirements Map requirements to processes to identify missing requirements © Seilevel, Inc. All rights reserved
  20. 20. Demonstration of Blueprint © Seilevel, Inc. All rights reserved
  21. 21. Suggested Reading © Seilevel, Inc. All rights reserved http://amzn.to/OxgGsC http://www.seilevel.com/blog BOOK BLOG http://bit.ly/1dIicEs http://www.blueprintsys.com/blog
  22. 22. Take Away © Seilevel, Inc. All rights reserved RML® Quick Reference RFP Template http://bit.ly/1hKg1CV www.blueprintsys.com/rfp
  23. 23. Upcoming Events © Seilevel, Inc. All rights reserved
  24. 24. Questions ? info@seilevel.com info@blueprintsys.com © Seilevel, Inc. All rights reserved Twitter: #improverqmnts
  25. 25. Contact Us Call us and speak with a Business Development Specialist. +1-866-979-2583 (BLUE) / info@blueprintsys.com Video Product Overview Watch the informative video demonstration of Blueprint in action. Watch Product Demo © Seilevel, Inc. All rights reserved Register Live Demo Request a complimentary consultation with a Blueprint representative. Live Demo Request

×