Non-Functional Requirements Analysis

Transcription

1 Non-Functional Requirements Analysis December 12, 2013

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

3 Tom Karasmanis IIBA Product Manager Tom Karasm anis is a Senior Consult ant w it h 25 y ears' experience in I nf orm at ion Technology, including roles as a Business Archit ect, Business/ Sy st em s Analy st, Project Leader, Technical Archit ect, and Sof t w are Engineer. He has w orked in f inancial serv ices, publishing, healt hcare, public sect or and t elecom m unicat ions. Tom serv ed as Chief Archit ect of t he I I BA f rom 2009 t o He is current ly I I BA Product M anager of Bei ng a BA: Techni cal Excel l ence and Vendor Showcase. Tom is a m anagem ent consult ant in business archit ect ure and business analy sis, assist ing organizat ions t o build or im prov e t heir BA pract ices. He speaks regularly at int ernat ional conf erences. Tom holds a Bachelor of Applied Science in Chem ical Engineering f rom t he Univ ersit y of Toront o and is act iv e in t he business analy sis and business archit ect ure com m unit ies. 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 Outline Introductions and Housekeeping 12:00 Vendor Presentations 12:05 TopTeam Analyst 12:05 Blueprint 12:25 Questions and Answers 12:42 Close 12:59 4 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

5 Question and Answer How to Ask Questions Use the Question box to ask questions. Selected questions w ill be answ ered at the end, but you can ask at any time. Include the vendor s name if you w ant a specific vendor to respond. Shor t, specif ic questions, please! IIBA Host Tom Karasmanis Ashu Potnis Tony Higgins 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 So it s not working? ( Fr om BABOK Guide v2.0, section 9.17) NON-FUNCTIONAL REQUIREMENTS ANALYSIS 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 What Are Non-Functional Requirements? Requirements structure (From BABOK Guide v2.0) Business Requirements Stakeholder Requirements Solution Requirements Functional Requirements Non-functional Requirements *** Transition Requirements 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 What Are Non-Functional Requirements? Capture conditions that do not directly relate to the behavior or functionality of the solution Instead, they describe environmental conditions under which the solution must remain effective or qualities that the systems must have Quality or supplementary requirements 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 What Are Non-Functional Requirements? Can include requirements related to: Capacity Speed (Response time, Throughput) Security Availability Scalability and more 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 What Is Requirements Analysis? Describes how business analysts prioritize and progressively elaborate stakeholder and solution requirements in order to enable the project team to implement a solution that will meet the needs of the sponsoring organization and stakeholders Includes non-functional requirements 10 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

11 What Is Requirements Analysis? Involves analyzing stakeholder needs to define solutions that meet those needs, assessing the current state of the business to identify and recommend improvements, and the verification and validation of the resulting requirements Includes non-functional requirements 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 11

12 What Is Non-functional Requirements Analysis? BABOK Guide v2.0, section 9.17 The purpose of non-functional requirements is to describe the required qualities of a system, such as its usability and performance characteristics. These supplement the documentation of functional requirements, which describe the behavior of the system. 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

13 What Is Non-functional Requirements Analysis? BABOK Guide v2.0, section 9.17 Categories (ISO 9126) Reliability Performance Efficiency Operability Security Compatibility Maintainability Transferability 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

14 What Is Non-functional Requirements Analysis? BABOK Guide v2.0, section 9.17 Measurement Include one or more measures of success How do we know we met the requirement Requires to adequately test requirement Documentation The system shall SMART 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

15 Importance Why Bother? Essentially describe the target quality of the system, so Missing non-functional requirements (missing quality) impacts every functional requirement Could affect adoption Could be compliance issues Careful! Too much could impact time and cost Often require technical expertise Could be done by System Analysts 15 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

16 Question and Answer How to Ask Questions Use the Question box to ask questions. Selected questions w ill be answ ered at the end, but you can ask at any time. Include the vendor s name if you w ant a specific vendor to respond. Shor t, specif ic questions, please! IIBA Host Tom Karasmanis Ashu Potnis Tony Higgins 16 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

17 Non-Functional Requirements Security Reliability Performance Non- Functional Scalability Accessibility

18 Requirements Functional Non- Functional Business Rules

19 Functional + Non-Functional = Complete Requirements Functional Requirements Non-Functional Requirements What the system should do Constrain Under what constraints it should do

20 TopTeam Analyst Functional Requirements Artifacts Textual User Stories Functional Requirements What the system should do Use Cases Application Prototypes custom Req. Types

21 TopTeam Analyst Non-Functional Requirements Artifacts Performance Security Non-Functional Requirements The parameters/constraints under which it should perform its functions Usability Scalability custom Req. Types

22 Requirements for a Business Application Authentication The system shall use 256 bit RSA encryption for authentication handshake The system shall authenticate users before allowing access to customer data The system shall perform authentication within 3 seconds Functional The system shall not allow login from mobile web browsers Constrain Non Functional

23 Authoring Requirements in TopTeam Analyst with Word processor-like Editor Non Functional Unique Requirements Identifiers and Trace Indicators

24 Trace links between Functional and Non-Functional Requirements Trace Report Graphical Trace Editor

25 Non-Functional Requirements can be linked with (traced to) Use Case Scenarios Linked/Traced Non-Functional Requirements Activity Diagram is automatically generated from text

26 Requirements for a Device/System Noise Cancelling Headphone The device battery shall last 12 hours of continuous use The device shall reduce background noise by 24 decibels The device shall be powered by ordinarily available AAA batteries Functional The device shall weigh less than 10 oz/284 grams Constrain Non Functional

27 Microsoft Word-like Full-Rich-Text editor for Requirements Embed images, tables, bullets, etc. Embed Excel Spreadsheet / Visio Diagrams etc. (OLE Embedding)

28 Requirements Versioning, Baselines and diff comparison View Precise differences between versions Inserted Text

29 Requirements for a Business Application Billing History Report The system shall generate report in Adobe Reader (PDF) format The system shall produce a billing history report every quarter for each account The report shall be formatted to fit a Letter size paper in a portrait orientation Functional The system shall produce the report in less than 30 seconds for each account Constrain Non Functional

30 Non-Functional Requirement Types also called ilities Availability Extensibility Interoperability Maintainability Portability Scalability Supportability Accessibility

31 Adapt TopTeam Analyst by configuring Non-Functional Requirements types that you need Requirement Type Configuration Create Non-Functional Requirement Types as per your needs

32 Non-Function Requirements vs User Stories Trace Configuration Define Trace Schema/Rules

33 Link Non-Functional Requirements with User Stories User Story Linked/Traced Non-Functional Requirements

34 Trace links between User Story and Non-Functional Requirements Trace Report Graphical Trace Editor

35 Conduct Visual Application Walkthroughs with stakeholders Non-Functional Requirements can be reviewed in the context of system behavior

36 Author and Manage Test Coverage for Non-Functional Requirements Test Cases

37 Users Conduct Online Reviews & Approvals of Requirements via their Web Browsers Get rapid iterative Requirements refinement

38 A No-Compromise, end-to-end Solution for VisualRequirements Definition and Requirements Management Mature -launched 2005, now in seventh major release Used by more than 500 organizations in 55 countries

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

40 Learn more or try it yourself TopTeamAnalyst.com For more information "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

42 Blueprint Blueprint develops requirements definition and management (RDM) software purpose-built to solve the many errors and inefficiencies encountered in RDM today. Using Blueprint results in better requirements and reduced rework, leading to successful projects and better applications. 5/1/13 Copyright 2013 Blueprint Software Systems Inc. All Rights Reserved. 42

43 Blueprint Requirements Definition & Management Platform Business Process Diagram Author Textual Requirement Validate Simulation Online Review/Approve Document Generation Collaborate Inline Discussions Use Case Diagrams Use Cases Traceability Version/Baseline Notifications Generic Diagram Glossaries Manage Reuse Visual Differencing Requirements Sharing Storyboards User Interface Mockups Coverage Cost / Status Actors Domain Diagram Monitor Progress Consolidated Dashboard Personal Activity Center Integrate Test Generation Excel, Visio Import/Export Word Conversion ALM Integrations Copyright 2013 Blueprint Software Systems Inc. All Rights Reserved. 43

46 Classification Schemes / Taxonomy McCall 1980 Keller 1990 Deutsch 1988 ISO/IEC 9126; 1991 Sommerville 1992 Availability x x Correctness x x x Efficiency x x x x x x x Expandability x x x Flexibility x x x x x Integrity x x x x x Interoperability x x x x x x Maintainability x x x x x x Portability x x x x x x Reliability x x x x x x x Reusability x x x x Safety x x Security x x Survivability x x x Testability x x Usability x x x x x x x Verifiability x x x Gilb 2005 Miller 2009 The Quest for Software Requirements, Roxanne Miller Copyright 2013 Blueprint Software Systems Inc. All Rights Reserved. 46

47 Requirements Taxonomy Blueprint for Enteprise Agile Feature Theme Provides Context or Elaboration At any level Bus iness Process Information Model Non-Functional Non-Functional Requirement Requirement constrain Feature Epic problem analysis solution analysis / specification Non-Functional Requirement Non-Functional Requirement constrain Feature Use Case UI UI Mockups Storyboa rd Non-Functional Requirement Non-Functional Requirement constrain Feature Epic User Feature Story Si mulation Other Forms Feature Epic Feature Tasks Copyright 2013 Blueprint Software Systems Inc. All Rights Reserved. 47

61 Contact Information Register for more webinars on the Learning and Development page of our website under Webinars. Ashu Potnis TopTeam Analyst Tony Higgins Blueprint International Institute of Business Analysis 61