Reusing Requirements. April 19, 2012

Transcription

1 Reusing Requirements April 19, 2012

2 Changing Change. Develop the Professional. Develop the Profession. International Institute of Business Analysis 2

3 Vision and 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. 3 I n t e r n a t i o n a l I n s t i t u t e o f B u s i n e s s A n a l y s i s

4 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 ) I n t e r n a t i o n a l I n s t i t u t e o f B u s i n e s s A n a l y s i s 4

5 Outline Introductions and Housekeeping 12:00 Vendor Presentations 12:05 TechnoSolutions 12:05 Jama Software 12:20 Sparx Systems 12:35 Questions and Answers 12:50 Close 12:59 Extended Q&A 1:00 5 I n t e r n a t i o n a l I n s t i t u t e o f B u s i n e s s A n a l y s i s

6 4.3 Maintain Requirements for Re-use What do we do? Identify requirements that are candidates for long-term usage by the enterprise Performance or compliance Reuse in other projects or analysis Enterprise, Portfolio, Program, [ Project?] Reference Organizational Process Assets Standards on how and when requirements should be maintained for reuse 6 I n t e r n a t i o n a l I n s t i t u t e o f B u s i n e s s A n a l y s i s

7 4.3 Maintain Requirements for Re-use Why do we do it? Performance monitoring and compliance Facilitate in impact analysis Reduce elicitation and analysis effort Assist in maintenance of existing solutions Use in training and documentation Corporate governance Consistency across enterprise 7 I n t e r n a t i o n a l I n s t i t u t e o f B u s i n e s s A n a l y s i s

8 4.3 Maintain Requirements for Re-use When do we do it? Following requirements implementation Tough to get time allocated for this Types of reusable requirements Ongoing (approved) Compliance, quality, SLA, current state Business rules (administered by business) 8 I n t e r n a t i o n a l I n s t i t u t e o f B u s i n e s s A n a l y s i s

9 4.3 Maintain Requirements for Re-use Types of reusable requirements Satisfied (approved) Project complete, but still needed by stakeholders System, project Deferred (unapproved) Not approved for a project, but worth keeping around for future projects or new product versions 9 I n t e r n a t i o n a l I n s t i t u t e o f B u s i n e s s A n a l y s i s

10 4.3 Maintain Requirements for Re-use Stakeholders Business Analyst Different BAs Reuse satisfied requirements on a new project Reuse ongoing requirements for compliance Domain SME Reference ongoing requirements regularly for adherence to them in day-to-day work I n t e r n a t i o n a l I n s t i t u t e o f B u s i n e s s A n a l y s i s 10

11 4.3 Maintain Requirements for Re-use Stakeholders Implementation SME Access satisfied requirements for regression testing, impact analysis, and maintenance Management Current state, business rules for governance, compliance Business case for ROI analysis 11 I n t e r n a t i o n a l I n s t i t u t e o f B u s i n e s s A n a l y s i s

12 4.3 Maintain Requirements for Re-use Output Suitable for long-term usage across enterprise key factors: Packaging, classifying, tracing Stored in a common repository Easily available; easy to find and access Clearly named and described 12 I n t e r n a t i o n a l I n s t i t u t e o f B u s i n e s s A n a l y s i s

13 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! Ashu Pontis Derwyn Harris IIBA Host Tom Karasmanis Ramsay Millar 13 I n t e r n a t i o n a l I n s t i t u t e o f B u s i n e s s A n a l y s i s

14 Reusing Requirements 4.3 in IIBA BABOK Ashu Potnis

15 TopTeam implementation of Requirements Reuse Program 1 Requirement A Requirement A System C Requirement A Define, Validate, Test once System D Requirement A Project X reuse same artifact multiple times Requirement A

16 Requirements Reuse in TopTeam Repository Explorer Defined Reused

17 Multiple Levels of Requirements Reuse Global Organization / Corporate level Program Program / System Level Project Project Level

18 Benefits of Requirements Reuse Requirements need not be re-validated with stakeholders repeatedly Ensure Consistency of Requirements & Business Rules within organization or Program Test Cases/Test Coverage is already available and can be reused Reduce Requirements work for subsequent uses

19 Good Candidates for Reuse Business Rules FDA CFR 11 / HIPAA Regulatory Glossary Terms Entity Attribute Definitions SOX / Other Compliance Reqs.

20 Reusing Requirements via Record Sharing

21 Reusing Business Rules via Record Sharing Business Rules defined in a global Project available in another Project when shared

22 Reusing Entity-Attribute (Data Model) via Record Sharing Entity Customer defined in a global Project Shared into another Project

23 Reusing Glossary Terms via Record Sharing Terms defined in a global Project appear in another Project when shared

24 Reusing Requirements via the <<include>> relationship of Use Case Scenarios

25 Reuse Use Case Scenarios via <<include>> in a Use Case Step <<include>> common scenarios for reuse included common scenario

26 TopTeam automatically converts scenario text into diagram and displays reused Use Case Scenario included scenario is shown on the flow diagram

27 Reuse Use Case Scenarios via <<include>> Common functionality is reused over and over again

28 Reusable Use Cases can be easily identified Reusable Use Case Scenarios can be placed in Common folder at Project, Program or Global level

29 Reusing Requirements via Trace Links

30 Reuse Requirements via Traceability Common Requirements Business Rule 1 Use Case 1 Requirement 1 Use Case 2 FDA CFR 11 Screen 1

31 Link to same Requirement in multiple Use Case Scenarios Link same Requirement into multiple Scenarios

32 Same Requirement can be traced to multiple artifacts including across Projects Reuse of Requirements via Traceability

33 Multi-level Impact Analysis/Trace Report shows reuse of Requirement via Trace

34 Reusing Requirements via OLE Embedding of existing Spreadsheets and Visio Diagrams

35 Outside artifacts such as Visio Diagrams/Excel Spreadsheets can be reused in your Projects via OLE embedding Reuse of artifacts via OLE Embedding

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

37 Anytime Anywhere Access Across the Cubicle or Across the Continents San Francisco New York London Sydney

38 components Rich Windows Desktop App Web Access and Collaboration Offline Desktop App TopTeam Open API

39 integrations Quality Center Team System (TFS) Microsoft Word Microsoft Excel TopTeam Open API (Integrate anything)

40 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

41 Contour and Requirements Re-use

42

43 Re-use

44 Attributes

45 The Requirement: The system must do something Who is working on it?! What is the priority? Who is notified of changes? Collaboration, approvals, reviews? Release scheduling

46 Same vs Synchronized

47 Same Change is global Ownership confusing Change notification can be confusing

48 Synchronized More Control Local Ownership Local Workflows Upstream Change

49 Branching

50

51 Determine attributes

52 Re-use requirements

53 Compare changes

54 Synchronize Pull changes Compare Push changes Branch

55

56 Leverage your collective genius.

57 IIBA Vendor Series BABOK Maintain Requirements for Re-use Presented by Ramsay Millar, Practice Leader & Mentor Business Analysis, Business Architecture

58 Re-Use Requirements What s wrong with the status quo? Thousands of pages of lost facts Documents die once the project is over Documents are inconsistent Documents are NOT traceable Documents cannot provide impact analysis Documents are impossible to search and Re-use across the Enterprise Business Analysis is very costly in time and resources Documents are impossible to manage the growing complexity of business and technology 58

59 Insanity - is doing the same thing over and over again and expecting different results. Albert Einstein 59

60 Be the master of thinking tools to address business complexity Ross & Lam The Strategic BA works To improve Business Capabilities To improve Business Agility To model and document Business Complexity To Re-use knowledge in an increasing knowledge intensive world To dramatically improve Requirements Management To Align Business and IT outcomes 60

61 Re-use Requirements must be clearly named and defined - BABOK Requirements Management Short Description Long Description Requirements number Status Difficulty Priority Author Requirement Types Phase Version Date created and updated Files and hyperlinks 61

62 Re-use Requirements must be clearly named and defined - BABOK Requirement types Business Rules Business Needs Business Concerns Functional Requirements User Interface Requirements Data Requirements Reporting Requirements Compliance Legal Regulatory QoS Requirements (non-functional) Others? 62

63 Re-use Requirements must be clearly named and defined - BABOK Requirement Tagged Values Stakeholder Responsible Stakeholder Accountable Stakeholder Consulted Stakeholder Informed Date of Next Review Date QA Tested Date Retired Disposition [Maintained, Reuseable] Work Estimate in hours Requested by Risk, Value Others? 63

64 Re-use Requirements must be easily available to other analysts BABOK Build Custom Re-use Requirements Find Maintained Requirements Find Reusable Requirements Find Requirements by Stakeholder types Responsible Accountable Consulted Informed Any stakeholder, actor or role Any type of Requirement 64

65 Re-use Requirements must be easily available to other analysts BABOK Requirements Reports Requirements sorted by Stakeholder Requirements sorted by Stakeholder influence Requirements sorted by priority and value Requirements sorted by Disposition [maintained, reusable] 65

66 These requirements may be stored in a repository BABOK 2.42 Fully traceable across the life cycle Store knowledge and re-useable facts Manage business complexity Effective stakeholder collaborations Re-use saves labor and reduces time to market Avoid documentation inconsistencies Rapid searching using relational database Re-use promotes continual quality Re-use avoids rework 66

67 A person should be identified to manage the repository BABOK The Model Guardian Manage Standards Manage Security Work Package Locking Diagram Locking Manage Re-use 67

68 Re-use facilitates impact analysis for business changes BABOK

69 Re-use facilitates impact analysis for business changes BABOK Assess Impacts across the Business Landscape Trace all Stakeholders to Requirements Trace from requirements to product delivery and beyond for Re-use Business Capabilities Business Needs Business Processes Business Rules Use Cases User Interfaces Data Models Software Code QA and Testing 69

70 Requirements may be maintained for re-use beyond the lifetime of a project - BABOK Maintain requirements for Re-use Business Architecture Governance, Risk, and Compliance Standard Operating Policy (SOP) Business Rules Decision Tables Functional Requirements User Interface Requirements Data Requirements Quality of Service (QoS) or non-functional 70

71 Requirements may be maintained for re-use beyond the lifetime of a project - BABOK Rapidly Drag and drop Re-use Requirements Enterprise Business Architecture Models Business Process Activities (BPMN 2) Use Cases User Interfaces Data Models Others? 71

72 Re-use Requirements Requirements to Stakeholder R Responsible A Accountable C Consulted I - Informed 72

73 Re-use Requirements Generate Re-use documentation from repository User stories Use Cases RACI Acceptance tests Requirements matrices Websites Custom documents 73

74 A good Business Analysis thinking tool MUST Support all BABOK 2 techniques Avoid rework using Re-use features Accelerate sharing and collaboration Trace Requirements to delivery and beyond Manage changes across many roles Support Open Standard Frameworks Generate many documentation types Be highly scalable for large teams Easy to use and customize Be a thinking tool limited by your imagination Be Affordable and increase Productivity 74

75 Unified and Comprehensive Business and Software Modeling Requirements Management Business Process Management Business Rules Management Portfolio and Project Management Strategic Business Modeling Business Architecture Enterprise Architecture Software Product Engineering Quality Assurance and Testing 75

76 Need to learn more? Please drop by the Sparx Systems booth in October You are invited to join our User group on LinkedIn Register for our Sparx EA for BAs online training sessions Led by Ramsay Millar, Practice Leader & Mentor Business Analysis, Business Architecture 76

77 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! Ashu Pontis Derwyn Harris IIBA Host Tom Karasmanis Ramsay Millar 77 I n t e r n a t i o n a l I n s t i t u t e o f B u s i n e s s A n a l y s i s

78 Contact Information Register for more webinars on the Professional Development page of our website under Webinars. IIBA.org/PD community.iiba.org Ashu Potnis Technosolutions Derwyn Harris Jama Software Ramsay Miller Sparyx Solutions International Institute of Business Analysis 78