SlideShare ist ein Scribd-Unternehmen logo
1 von 12
Downloaden Sie, um offline zu lesen
Requirement Excellence
     Framework™
RequirementPro™ Architecture

      www.enfocussolutions.com
Enterprise Knowledgebases

Knowledgebases are used to store information that is used between projects. Optimally,
enterprise libraries should be maintained by business unit; however they may also be
maintained by business analyst as they define project requirements. The four enterprise
libraries are explained below.

                   A business rule is a compact statement about some aspect of the business          •   Business Rules
    Business       that serves as a constraint of what must or must not be done. Rules are
                   organized in rule books and expressed using simple, clear language. They
     Rules         should be accessible by all interested parties such as business process
                   owners, business analysts, technical architects and so on.
                   A business process is the set of steps a business performs to create value for    • Business Process
   Business        customers. A process consists of three components: inputs, activities, and
   Processes       outputs.


                   Stakeholder profiles are used to describe categories of individuals involved in   • Stakeholder
                   project such as the sponsor, customers, end-users, business subject matter          Profile
  Stakeholder      experts, and people involved in the design, development, implementation
    Profiles       and support of the solution.

                   Products are used to document the products and services that the                  • Product or Service
                   organization delivers to the customer. This category can also be used for ITIL      Description
    Products       V3 Service Descriptions. In this case, the product and all of its projects with   • Product Feature
                   associated requirements become a Service Design Package.                            Roadmap
                                                                                                                        1
Three Level of Requirements
                                         (Generally recognized)


               Represent the high level objectives of the       •   Business Objectives
               organization. Business requirements describe     •   Project Vision and Scope
  Business     why the system is being developed,               •   Project Constraints
               measurable business benefits that align with     •   Business Process Design
Requirements   the organization’s vision, and any constraints   •   Business Rules
               that have been imposed on the project.


               User requirements describe what the users        •   Stakeholder Needs
               need to perform their tasks. They bridge the     •   Needs from Document Review
               gap between business requirements and            •   Business Rule Constraints
    User       what the developers will build (system           •   Use Cases
Requirements   requirements).                                   •   User Stories
                                                                •   Scenario


               System requirements describe how the             •   Functional requirements
               business processes will be automated             •   Supplemental requirements
               (functional requirements) and the attributes     •   Test Cases
   System      and constraints of the environment where         •   Requirement Bundles
Requirements   the system will operate (supplemental
               requirements).




                                                                                                 2
Requirements Overview


            Business Requirements (Objectives and Constraints)



     Business
Process Analysis and                    User Requirements (Needs)
      Design


                                                       Organizational Change
                                  Software
                                                            & Training
                                Requirements
                                                           Requirements


                                                        Organizational Design
                             Systems Analysis and
                                                            and Change
                                   Design
                                                           Management


                                                                                3
Avoiding Confusion

Many people seem to confuse the three because the work requirement is used in all three. Ee use
the following terms in the Requirements Excellence Framework:
Business Objectives and Constraints
     Business Objective - Reduce delinquent accounts to 10% or less, within three months.
     Project Constraint - The software must be delivered by March 31st, 2012.
     Technical Constraint – The system must utilize the Oracle Database to comply with our
     standards.
Needs
     User Need – As an accounting clerk, I need the ability to cancel transactions.
Requirements
     Functional Requirement - System shall permit users to cancel transactions with an audit trail.
     Supplemental Requirement –-The system must be available 24 hours a day from Monday to
     Saturday.

A statement about “how” the solution will work as opposed to “what” it is intended to do should
be captured in the Design Document. The statement below is not a requirement.
   “The Location shall be selected from a drop-down list”
                                                                                                  4
Business Rules

                                                                Project

                                                                Feature
                                                                Impact

            Process Category           Rule Book                Scope
                                                              Statement
Business rules are maintained
separate from requirements. They                        Functional        Supplemental
                                                       Requirement        Requirement
are organized by rule book for
various functional topics such
vacation and holiday leave, travel,
customer service, etc.). Each rule    Business Rule              Related Rules
book has a rule book owner. Rule
books are ideally maintained by the
business. Rules may be linked to
requirements.

                                                                                   5
Business Processes

        Process Category                                                                Feature
                                                    Project
                                                                                        Impact
          Process Group
                                                                                        Scope
                                              Business Process                        Statement
              Process
                                                   Impact

              Activity                                                   Functional            Supplemental
                                                                        Requirement            Requirement

The process structure is organized using      During Process Analysis, impacts on   Since software is used to
APQC’s Process Classification Structure       existing business processes are       provide automated support
(PCF). The PCF was developed by APQC          identified and documented .           for a business process, it is
and its member organizations as an open       Depending on the size of the          essential to understand how
standard to facilitate improvement            project, AS IS and TO BE business     the process is going to work
through process management and                process models may be created or      before defining software
benchmarking, regardless of industry, size,   updated. The business process         requirements.
or geography. The PCF organizes operating     impacts are later used in the
and management processes into 12              Project Scope Activity to define
enterprise-level categories, including        scope statements which are used
process groups and over 1,000 processes       to elicit needs from Stakeholders                                6
and associated activities.                    and specify requirements.
Stakeholders

                                         Stakeholder                    Stakeholder               Project
                                            Profile                       Contact                 Contact
      Product


                      Product                                      Project
                    Stakeholder                                  Stakeholder
                                                                                                  Project

Project Stakeholders and Project Stakeholder contacts are
identified during Stakeholder Analysis.                                                                     Feature
 Stakeholder Needs are identified during Elicitation through a                                              Impact
 variety of elicitation techniques such as web forms,                          Stakeholder Need
 interviews, observations and group discussion. They are
 captured using patterns and organized by Product
 Stakeholder and cope Statement.
                                                                                                              Scope
 User Stories are a special type of need often used on Agile                      User Story
                                                                                                            Statement
 projects. They are normally in the form of As…, I want to… so
 that I can ….. Stakeholders are linked to user stories via the As
 a … clause of the user story.
                                                                                   Use Case
 Use Cases are developed by the analyst during Analysis to
 gain a better understanding of the sequence of events and                                                            7
 user involvement.
Products


                                  Project

      Product


                                 Feature                        Scope
      Feature
                                 Impact                       Statement

                                                     Functional       Supplemental
                                                    Requirement       Requirement

Products may be implemented many ways depending on the needs of the organization.
For example, products could be applications, ITIL Services, or products or services sold
to external customers. A project can impact one or many products. Defining scope
statements depends on having feature (Product) and Process impacts identified and
documented.

                                                                                           8
Projects

                                             The Project, the Project Vision and Project Constraints
Stakeholders that                            are defined during the Project Vision activity.
are impacted by the
project are                                                                            Project Vision
identified during                Project
the Stakeholder                Stakeholder
                                                        Project
Analysis activity
                                                                                    Project Constraints
Impact on the
product portfolio.                                   Feature Impact
These are identified
during the Project
                                                                                    Business Objectives
Scope activity                                                                 SMART business objectives are
                                                        Scope                  documented during the Business
                           Process Impact
Business process                                      Statement                Objectives activity.
impact that are
identified and
documented during
Process Analysis.                                                                         Requirement
                                              Functional          Supplemental
                                             Requirement          Requirement           Management. Plan
         Functional requirements,
         supplemental requirements and
                                                                             The Requirement Management Plan
         related business rules are
                                                       Related Rules         defines the approach and set of
         developed during the
                                                                             tasks to complete Requirements
         Specification activity,                                             Development and Management
                                                                             activities.
                                                                                                             9
Requirements Development
                     Scope Statements are defined in the Project Scope activity and                      Process Impacts are
                     used to elicit needs and specify requirements.                                      identified during Process
                                                                                        Process          Analysis and used to
                                                                                        Impact           define scope statements.
Project Stakeholders are identified                    Scope
during Stakeholder Analysis                                                                              Impacts on products and
and used to define stakeholder                       Statement                         Feature           services are identified during
needs and user stories. Project                                                        Impact            Project Scope and are used to
stakeholders are also used as actors                                                                     create scope statements.
in Use Cases.
                                                                                 Supplemental            Supplemental Requirements
                                Stakeholder Need
                                                                                 Requirement             are created during
                                                                                                         Specification.
  Project
                                    User Story
Stakeholder                                                                        Functional            Functional Requirements
                                                                                                         are created during
                                                                                  Requirement
                                       Use Case                                                          Specification.

Stakeholder Needs are          User Stories are a special type   Use Cases are
                                                                                                           Related Rules
identified during Elicitation of need which are created          developed by the analyst
through a variety of           during Elicitation.               during Analysis to gain a               Related Rules are identified
elicitation techniques such as                                   better understanding of                 during Specification and
web forms, interviews,                                           the sequence of events                  linked to a requirement.
observations and group                                           and user involvement.
discussion.

   Note that Requirements Development is an iterative and incremental activity. Generally Elicitation,
                      Analysis, Specification, and Validation go on concurrently.                                                10
Requirement Management
                                                                                   Functional and Supplemental
          Stakeholder Need           User Story                 Use Case           Requirements are grouped into
                                                                                   bundles. Associated User Stories, Use
                                                                                   Cases Stakeholder Needs, and Related
      Related Rules                                                                Business Rules are included by
                                   Functional              Supplemental            reference.
                                  Requirement              Requirement             Lifecycle Events are identified based on
                                                                                   the type of requirements in the bundle.
                                                                                   Lifecycle Events include such things as
                                                                                   Validation, Design Reviews, User
                                                  Bundles                          Acceptance Testing, Code Inspections,
                                                                                   Sprint Plans, etc.


                                             Lifecycle Event
Change Requests                                                                                     Defects

After a bundle has       Participants          Test Scenarios           Validations                  Requirement defects
been baselined, all                                                                                  are recorded and
changes, additions,   Project Stakeholders                           Validations are performed       tracked to ensure they
and deletions are     participate in              Test Cases         to confirm such things as:      are resolved.
controlled and        lifecycle events to                            • needs are addressed,
tracked.              perform tests and      User Acceptance Tests • developers understand
                      validations of the     are defined to ensure      the requirements, and
                      requirements.          that the solution meets • there is sufficient budget
                                             the defined                to build the solution.
                                             requirements.
                                                                                                                        11

Weitere ähnliche Inhalte

Was ist angesagt?

Methods To Leverage SAP Workflow
Methods To Leverage SAP WorkflowMethods To Leverage SAP Workflow
Methods To Leverage SAP WorkflowEric Stajda
 
BABOK - Tasks, Input and Outputs
BABOK - Tasks, Input and OutputsBABOK - Tasks, Input and Outputs
BABOK - Tasks, Input and OutputsCBAP Master
 
Methodology framework
Methodology framework   Methodology framework
Methodology framework IndigoCube
 
Science Modernisation Strategy v1 0
Science  Modernisation  Strategy v1 0Science  Modernisation  Strategy v1 0
Science Modernisation Strategy v1 0Salim Sheikh
 
ITIL v3 Foundation Presentation
ITIL v3 Foundation PresentationITIL v3 Foundation Presentation
ITIL v3 Foundation PresentationWajahat Rajab
 
6 rpt oracle_plugin-anitha_krishnamurthy
6 rpt oracle_plugin-anitha_krishnamurthy6 rpt oracle_plugin-anitha_krishnamurthy
6 rpt oracle_plugin-anitha_krishnamurthyIBM
 
Methodology Framework
Methodology FrameworkMethodology Framework
Methodology FrameworkBob Sanders
 
Introduction to the BPM Lifecycle
Introduction to the BPM LifecycleIntroduction to the BPM Lifecycle
Introduction to the BPM LifecycleMichael zur Muehlen
 
Dallas Salesforce User Group - January 2012 Meeting: Release Management
Dallas Salesforce User Group - January 2012 Meeting: Release ManagementDallas Salesforce User Group - January 2012 Meeting: Release Management
Dallas Salesforce User Group - January 2012 Meeting: Release ManagementKevin Richardson
 
Business Service Management for Life Sciences
Business Service Management for Life SciencesBusiness Service Management for Life Sciences
Business Service Management for Life SciencesNiamh Cahill
 
Business Process Management - From Market Consolidation to Process Innovation
Business Process Management - From Market Consolidation to Process InnovationBusiness Process Management - From Market Consolidation to Process Innovation
Business Process Management - From Market Consolidation to Process InnovationMichael zur Muehlen
 
SEC Presentation V2
SEC Presentation V2SEC Presentation V2
SEC Presentation V2Salim Sheikh
 
LeverX - A Comprehensive Guide to SAP PLM 7.01
LeverX - A Comprehensive Guide to SAP PLM 7.01LeverX - A Comprehensive Guide to SAP PLM 7.01
LeverX - A Comprehensive Guide to SAP PLM 7.01LeverX
 
Erp Implementation Methodology Wkshp 2.0 120611
Erp Implementation Methodology Wkshp 2.0 120611Erp Implementation Methodology Wkshp 2.0 120611
Erp Implementation Methodology Wkshp 2.0 120611John Paulson
 
Aufait Technologies - Introduction to BPM
Aufait Technologies - Introduction to BPMAufait Technologies - Introduction to BPM
Aufait Technologies - Introduction to BPMDinesh Kumar P
 
Functional decomposition
Functional decompositionFunctional decomposition
Functional decompositionCOEPD HR
 

Was ist angesagt? (20)

Methods To Leverage SAP Workflow
Methods To Leverage SAP WorkflowMethods To Leverage SAP Workflow
Methods To Leverage SAP Workflow
 
BABOK - Tasks, Input and Outputs
BABOK - Tasks, Input and OutputsBABOK - Tasks, Input and Outputs
BABOK - Tasks, Input and Outputs
 
Methodology framework
Methodology framework   Methodology framework
Methodology framework
 
Science Modernisation Strategy v1 0
Science  Modernisation  Strategy v1 0Science  Modernisation  Strategy v1 0
Science Modernisation Strategy v1 0
 
ITIL v3 Foundation Presentation
ITIL v3 Foundation PresentationITIL v3 Foundation Presentation
ITIL v3 Foundation Presentation
 
6 rpt oracle_plugin-anitha_krishnamurthy
6 rpt oracle_plugin-anitha_krishnamurthy6 rpt oracle_plugin-anitha_krishnamurthy
6 rpt oracle_plugin-anitha_krishnamurthy
 
Methodology Framework
Methodology FrameworkMethodology Framework
Methodology Framework
 
Killing the Myth: Agile & CMMI
Killing the Myth: Agile & CMMIKilling the Myth: Agile & CMMI
Killing the Myth: Agile & CMMI
 
Introduction to the BPM Lifecycle
Introduction to the BPM LifecycleIntroduction to the BPM Lifecycle
Introduction to the BPM Lifecycle
 
Dallas Salesforce User Group - January 2012 Meeting: Release Management
Dallas Salesforce User Group - January 2012 Meeting: Release ManagementDallas Salesforce User Group - January 2012 Meeting: Release Management
Dallas Salesforce User Group - January 2012 Meeting: Release Management
 
PLM-ERP Integration
PLM-ERP IntegrationPLM-ERP Integration
PLM-ERP Integration
 
Business Service Management for Life Sciences
Business Service Management for Life SciencesBusiness Service Management for Life Sciences
Business Service Management for Life Sciences
 
Oracle Aim Methodology
Oracle Aim MethodologyOracle Aim Methodology
Oracle Aim Methodology
 
Business Process Management - From Market Consolidation to Process Innovation
Business Process Management - From Market Consolidation to Process InnovationBusiness Process Management - From Market Consolidation to Process Innovation
Business Process Management - From Market Consolidation to Process Innovation
 
SEC Presentation V2
SEC Presentation V2SEC Presentation V2
SEC Presentation V2
 
LeverX - A Comprehensive Guide to SAP PLM 7.01
LeverX - A Comprehensive Guide to SAP PLM 7.01LeverX - A Comprehensive Guide to SAP PLM 7.01
LeverX - A Comprehensive Guide to SAP PLM 7.01
 
Business Process Management Training 1
Business Process Management Training 1Business Process Management Training 1
Business Process Management Training 1
 
Erp Implementation Methodology Wkshp 2.0 120611
Erp Implementation Methodology Wkshp 2.0 120611Erp Implementation Methodology Wkshp 2.0 120611
Erp Implementation Methodology Wkshp 2.0 120611
 
Aufait Technologies - Introduction to BPM
Aufait Technologies - Introduction to BPMAufait Technologies - Introduction to BPM
Aufait Technologies - Introduction to BPM
 
Functional decomposition
Functional decompositionFunctional decomposition
Functional decomposition
 

Ähnlich wie RequirementPro™ Architecture

40411923 business-analyst
40411923 business-analyst40411923 business-analyst
40411923 business-analystHar Da
 
Aim PPT For Oracle HRMS
Aim PPT For Oracle HRMSAim PPT For Oracle HRMS
Aim PPT For Oracle HRMSRajiv reddy
 
Business analysis and project changes
Business analysis and project changesBusiness analysis and project changes
Business analysis and project changesIIBA Romania Chapter
 
Business Analyst Job Profile coepd
Business Analyst Job Profile   coepdBusiness Analyst Job Profile   coepd
Business Analyst Job Profile coepdCOEPD HR
 
SAP Netweaver BPM #SITANK 2011
SAP Netweaver BPM #SITANK 2011SAP Netweaver BPM #SITANK 2011
SAP Netweaver BPM #SITANK 2011Abdulbasit Gulsen
 
Gathering And Documenting Your Bi Business Requirements
Gathering And Documenting Your Bi Business RequirementsGathering And Documenting Your Bi Business Requirements
Gathering And Documenting Your Bi Business RequirementsWynyard Group
 
Business Requirements development
Business Requirements development Business Requirements development
Business Requirements development Mark Opanasiuk
 
Agile & Business Analysis: A Successful Combination
Agile & Business Analysis: A Successful CombinationAgile & Business Analysis: A Successful Combination
Agile & Business Analysis: A Successful CombinationLuiz C. Parzianello
 
Run sap methodology how to implement end to-end solution operations
Run sap methodology  how to implement end to-end solution operations  Run sap methodology  how to implement end to-end solution operations
Run sap methodology how to implement end to-end solution operations ricardopabloasensio
 
Requirements Manager Center of Excellence: “Achieving Goals Without Formaliz...
Requirements Manager Center of Excellence:  “Achieving Goals Without Formaliz...Requirements Manager Center of Excellence:  “Achieving Goals Without Formaliz...
Requirements Manager Center of Excellence: “Achieving Goals Without Formaliz...IIBA Rochester NY
 
Pm for application development
Pm for application developmentPm for application development
Pm for application developmentAbdelrahman Serag
 
Operational Model Design
Operational Model DesignOperational Model Design
Operational Model DesignFlexera
 

Ähnlich wie RequirementPro™ Architecture (20)

Biz Req Checklist1
Biz Req Checklist1Biz Req Checklist1
Biz Req Checklist1
 
Scor model
Scor modelScor model
Scor model
 
Aim crisp handout
Aim crisp handoutAim crisp handout
Aim crisp handout
 
SRE_Lecture_1,2,3,4.pptx
SRE_Lecture_1,2,3,4.pptxSRE_Lecture_1,2,3,4.pptx
SRE_Lecture_1,2,3,4.pptx
 
40411923 business-analyst
40411923 business-analyst40411923 business-analyst
40411923 business-analyst
 
Aim PPT For Oracle HRMS
Aim PPT For Oracle HRMSAim PPT For Oracle HRMS
Aim PPT For Oracle HRMS
 
Business analysis and project changes
Business analysis and project changesBusiness analysis and project changes
Business analysis and project changes
 
Business Analyst Job Profile coepd
Business Analyst Job Profile   coepdBusiness Analyst Job Profile   coepd
Business Analyst Job Profile coepd
 
Enfoucs Requirement Suite™
Enfoucs Requirement Suite™Enfoucs Requirement Suite™
Enfoucs Requirement Suite™
 
Entitlement and Access Manegement
Entitlement and Access ManegementEntitlement and Access Manegement
Entitlement and Access Manegement
 
SAP Netweaver BPM #SITANK 2011
SAP Netweaver BPM #SITANK 2011SAP Netweaver BPM #SITANK 2011
SAP Netweaver BPM #SITANK 2011
 
Gathering And Documenting Your Bi Business Requirements
Gathering And Documenting Your Bi Business RequirementsGathering And Documenting Your Bi Business Requirements
Gathering And Documenting Your Bi Business Requirements
 
Business Requirements development
Business Requirements development Business Requirements development
Business Requirements development
 
Agile & Business Analysis: A Successful Combination
Agile & Business Analysis: A Successful CombinationAgile & Business Analysis: A Successful Combination
Agile & Business Analysis: A Successful Combination
 
Bpabro
BpabroBpabro
Bpabro
 
Run sap methodology how to implement end to-end solution operations
Run sap methodology  how to implement end to-end solution operations  Run sap methodology  how to implement end to-end solution operations
Run sap methodology how to implement end to-end solution operations
 
Requirements Manager Center of Excellence: “Achieving Goals Without Formaliz...
Requirements Manager Center of Excellence:  “Achieving Goals Without Formaliz...Requirements Manager Center of Excellence:  “Achieving Goals Without Formaliz...
Requirements Manager Center of Excellence: “Achieving Goals Without Formaliz...
 
Pm for application development
Pm for application developmentPm for application development
Pm for application development
 
Operational Model Design
Operational Model DesignOperational Model Design
Operational Model Design
 
Cisco Data Sheet SORM
Cisco Data Sheet SORM Cisco Data Sheet SORM
Cisco Data Sheet SORM
 

Kürzlich hochgeladen

UiPath Community: AI for UiPath Automation Developers
UiPath Community: AI for UiPath Automation DevelopersUiPath Community: AI for UiPath Automation Developers
UiPath Community: AI for UiPath Automation DevelopersUiPathCommunity
 
Meet the new FSP 3000 M-Flex800™
Meet the new FSP 3000 M-Flex800™Meet the new FSP 3000 M-Flex800™
Meet the new FSP 3000 M-Flex800™Adtran
 
AI Fame Rush Review – Virtual Influencer Creation In Just Minutes
AI Fame Rush Review – Virtual Influencer Creation In Just MinutesAI Fame Rush Review – Virtual Influencer Creation In Just Minutes
AI Fame Rush Review – Virtual Influencer Creation In Just MinutesMd Hossain Ali
 
Using IESVE for Loads, Sizing and Heat Pump Modeling to Achieve Decarbonization
Using IESVE for Loads, Sizing and Heat Pump Modeling to Achieve DecarbonizationUsing IESVE for Loads, Sizing and Heat Pump Modeling to Achieve Decarbonization
Using IESVE for Loads, Sizing and Heat Pump Modeling to Achieve DecarbonizationIES VE
 
Apres-Cyber - The Data Dilemma: Bridging Offensive Operations and Machine Lea...
Apres-Cyber - The Data Dilemma: Bridging Offensive Operations and Machine Lea...Apres-Cyber - The Data Dilemma: Bridging Offensive Operations and Machine Lea...
Apres-Cyber - The Data Dilemma: Bridging Offensive Operations and Machine Lea...Will Schroeder
 
activity_diagram_combine_v4_20190827.pdfactivity_diagram_combine_v4_20190827.pdf
activity_diagram_combine_v4_20190827.pdfactivity_diagram_combine_v4_20190827.pdfactivity_diagram_combine_v4_20190827.pdfactivity_diagram_combine_v4_20190827.pdf
activity_diagram_combine_v4_20190827.pdfactivity_diagram_combine_v4_20190827.pdfJamie (Taka) Wang
 
UiPath Studio Web workshop series - Day 7
UiPath Studio Web workshop series - Day 7UiPath Studio Web workshop series - Day 7
UiPath Studio Web workshop series - Day 7DianaGray10
 
COMPUTER 10 Lesson 8 - Building a Website
COMPUTER 10 Lesson 8 - Building a WebsiteCOMPUTER 10 Lesson 8 - Building a Website
COMPUTER 10 Lesson 8 - Building a Websitedgelyza
 
Artificial Intelligence & SEO Trends for 2024
Artificial Intelligence & SEO Trends for 2024Artificial Intelligence & SEO Trends for 2024
Artificial Intelligence & SEO Trends for 2024D Cloud Solutions
 
COMPUTER 10: Lesson 7 - File Storage and Online Collaboration
COMPUTER 10: Lesson 7 - File Storage and Online CollaborationCOMPUTER 10: Lesson 7 - File Storage and Online Collaboration
COMPUTER 10: Lesson 7 - File Storage and Online Collaborationbruanjhuli
 
UiPath Platform: The Backend Engine Powering Your Automation - Session 1
UiPath Platform: The Backend Engine Powering Your Automation - Session 1UiPath Platform: The Backend Engine Powering Your Automation - Session 1
UiPath Platform: The Backend Engine Powering Your Automation - Session 1DianaGray10
 
VoIP Service and Marketing using Odoo and Asterisk PBX
VoIP Service and Marketing using Odoo and Asterisk PBXVoIP Service and Marketing using Odoo and Asterisk PBX
VoIP Service and Marketing using Odoo and Asterisk PBXTarek Kalaji
 
Igniting Next Level Productivity with AI-Infused Data Integration Workflows
Igniting Next Level Productivity with AI-Infused Data Integration WorkflowsIgniting Next Level Productivity with AI-Infused Data Integration Workflows
Igniting Next Level Productivity with AI-Infused Data Integration WorkflowsSafe Software
 
Linked Data in Production: Moving Beyond Ontologies
Linked Data in Production: Moving Beyond OntologiesLinked Data in Production: Moving Beyond Ontologies
Linked Data in Production: Moving Beyond OntologiesDavid Newbury
 
Videogame localization & technology_ how to enhance the power of translation.pdf
Videogame localization & technology_ how to enhance the power of translation.pdfVideogame localization & technology_ how to enhance the power of translation.pdf
Videogame localization & technology_ how to enhance the power of translation.pdfinfogdgmi
 
UiPath Solutions Management Preview - Northern CA Chapter - March 22.pdf
UiPath Solutions Management Preview - Northern CA Chapter - March 22.pdfUiPath Solutions Management Preview - Northern CA Chapter - March 22.pdf
UiPath Solutions Management Preview - Northern CA Chapter - March 22.pdfDianaGray10
 
Salesforce Miami User Group Event - 1st Quarter 2024
Salesforce Miami User Group Event - 1st Quarter 2024Salesforce Miami User Group Event - 1st Quarter 2024
Salesforce Miami User Group Event - 1st Quarter 2024SkyPlanner
 
UiPath Studio Web workshop series - Day 6
UiPath Studio Web workshop series - Day 6UiPath Studio Web workshop series - Day 6
UiPath Studio Web workshop series - Day 6DianaGray10
 
IESVE Software for Florida Code Compliance Using ASHRAE 90.1-2019
IESVE Software for Florida Code Compliance Using ASHRAE 90.1-2019IESVE Software for Florida Code Compliance Using ASHRAE 90.1-2019
IESVE Software for Florida Code Compliance Using ASHRAE 90.1-2019IES VE
 

Kürzlich hochgeladen (20)

UiPath Community: AI for UiPath Automation Developers
UiPath Community: AI for UiPath Automation DevelopersUiPath Community: AI for UiPath Automation Developers
UiPath Community: AI for UiPath Automation Developers
 
201610817 - edge part1
201610817 - edge part1201610817 - edge part1
201610817 - edge part1
 
Meet the new FSP 3000 M-Flex800™
Meet the new FSP 3000 M-Flex800™Meet the new FSP 3000 M-Flex800™
Meet the new FSP 3000 M-Flex800™
 
AI Fame Rush Review – Virtual Influencer Creation In Just Minutes
AI Fame Rush Review – Virtual Influencer Creation In Just MinutesAI Fame Rush Review – Virtual Influencer Creation In Just Minutes
AI Fame Rush Review – Virtual Influencer Creation In Just Minutes
 
Using IESVE for Loads, Sizing and Heat Pump Modeling to Achieve Decarbonization
Using IESVE for Loads, Sizing and Heat Pump Modeling to Achieve DecarbonizationUsing IESVE for Loads, Sizing and Heat Pump Modeling to Achieve Decarbonization
Using IESVE for Loads, Sizing and Heat Pump Modeling to Achieve Decarbonization
 
Apres-Cyber - The Data Dilemma: Bridging Offensive Operations and Machine Lea...
Apres-Cyber - The Data Dilemma: Bridging Offensive Operations and Machine Lea...Apres-Cyber - The Data Dilemma: Bridging Offensive Operations and Machine Lea...
Apres-Cyber - The Data Dilemma: Bridging Offensive Operations and Machine Lea...
 
activity_diagram_combine_v4_20190827.pdfactivity_diagram_combine_v4_20190827.pdf
activity_diagram_combine_v4_20190827.pdfactivity_diagram_combine_v4_20190827.pdfactivity_diagram_combine_v4_20190827.pdfactivity_diagram_combine_v4_20190827.pdf
activity_diagram_combine_v4_20190827.pdfactivity_diagram_combine_v4_20190827.pdf
 
UiPath Studio Web workshop series - Day 7
UiPath Studio Web workshop series - Day 7UiPath Studio Web workshop series - Day 7
UiPath Studio Web workshop series - Day 7
 
COMPUTER 10 Lesson 8 - Building a Website
COMPUTER 10 Lesson 8 - Building a WebsiteCOMPUTER 10 Lesson 8 - Building a Website
COMPUTER 10 Lesson 8 - Building a Website
 
Artificial Intelligence & SEO Trends for 2024
Artificial Intelligence & SEO Trends for 2024Artificial Intelligence & SEO Trends for 2024
Artificial Intelligence & SEO Trends for 2024
 
COMPUTER 10: Lesson 7 - File Storage and Online Collaboration
COMPUTER 10: Lesson 7 - File Storage and Online CollaborationCOMPUTER 10: Lesson 7 - File Storage and Online Collaboration
COMPUTER 10: Lesson 7 - File Storage and Online Collaboration
 
UiPath Platform: The Backend Engine Powering Your Automation - Session 1
UiPath Platform: The Backend Engine Powering Your Automation - Session 1UiPath Platform: The Backend Engine Powering Your Automation - Session 1
UiPath Platform: The Backend Engine Powering Your Automation - Session 1
 
VoIP Service and Marketing using Odoo and Asterisk PBX
VoIP Service and Marketing using Odoo and Asterisk PBXVoIP Service and Marketing using Odoo and Asterisk PBX
VoIP Service and Marketing using Odoo and Asterisk PBX
 
Igniting Next Level Productivity with AI-Infused Data Integration Workflows
Igniting Next Level Productivity with AI-Infused Data Integration WorkflowsIgniting Next Level Productivity with AI-Infused Data Integration Workflows
Igniting Next Level Productivity with AI-Infused Data Integration Workflows
 
Linked Data in Production: Moving Beyond Ontologies
Linked Data in Production: Moving Beyond OntologiesLinked Data in Production: Moving Beyond Ontologies
Linked Data in Production: Moving Beyond Ontologies
 
Videogame localization & technology_ how to enhance the power of translation.pdf
Videogame localization & technology_ how to enhance the power of translation.pdfVideogame localization & technology_ how to enhance the power of translation.pdf
Videogame localization & technology_ how to enhance the power of translation.pdf
 
UiPath Solutions Management Preview - Northern CA Chapter - March 22.pdf
UiPath Solutions Management Preview - Northern CA Chapter - March 22.pdfUiPath Solutions Management Preview - Northern CA Chapter - March 22.pdf
UiPath Solutions Management Preview - Northern CA Chapter - March 22.pdf
 
Salesforce Miami User Group Event - 1st Quarter 2024
Salesforce Miami User Group Event - 1st Quarter 2024Salesforce Miami User Group Event - 1st Quarter 2024
Salesforce Miami User Group Event - 1st Quarter 2024
 
UiPath Studio Web workshop series - Day 6
UiPath Studio Web workshop series - Day 6UiPath Studio Web workshop series - Day 6
UiPath Studio Web workshop series - Day 6
 
IESVE Software for Florida Code Compliance Using ASHRAE 90.1-2019
IESVE Software for Florida Code Compliance Using ASHRAE 90.1-2019IESVE Software for Florida Code Compliance Using ASHRAE 90.1-2019
IESVE Software for Florida Code Compliance Using ASHRAE 90.1-2019
 

RequirementPro™ Architecture

  • 1. Requirement Excellence Framework™ RequirementPro™ Architecture www.enfocussolutions.com
  • 2. Enterprise Knowledgebases Knowledgebases are used to store information that is used between projects. Optimally, enterprise libraries should be maintained by business unit; however they may also be maintained by business analyst as they define project requirements. The four enterprise libraries are explained below. A business rule is a compact statement about some aspect of the business • Business Rules Business that serves as a constraint of what must or must not be done. Rules are organized in rule books and expressed using simple, clear language. They Rules should be accessible by all interested parties such as business process owners, business analysts, technical architects and so on. A business process is the set of steps a business performs to create value for • Business Process Business customers. A process consists of three components: inputs, activities, and Processes outputs. Stakeholder profiles are used to describe categories of individuals involved in • Stakeholder project such as the sponsor, customers, end-users, business subject matter Profile Stakeholder experts, and people involved in the design, development, implementation Profiles and support of the solution. Products are used to document the products and services that the • Product or Service organization delivers to the customer. This category can also be used for ITIL Description Products V3 Service Descriptions. In this case, the product and all of its projects with • Product Feature associated requirements become a Service Design Package. Roadmap 1
  • 3. Three Level of Requirements (Generally recognized) Represent the high level objectives of the • Business Objectives organization. Business requirements describe • Project Vision and Scope Business why the system is being developed, • Project Constraints measurable business benefits that align with • Business Process Design Requirements the organization’s vision, and any constraints • Business Rules that have been imposed on the project. User requirements describe what the users • Stakeholder Needs need to perform their tasks. They bridge the • Needs from Document Review gap between business requirements and • Business Rule Constraints User what the developers will build (system • Use Cases Requirements requirements). • User Stories • Scenario System requirements describe how the • Functional requirements business processes will be automated • Supplemental requirements (functional requirements) and the attributes • Test Cases System and constraints of the environment where • Requirement Bundles Requirements the system will operate (supplemental requirements). 2
  • 4. Requirements Overview Business Requirements (Objectives and Constraints) Business Process Analysis and User Requirements (Needs) Design Organizational Change Software & Training Requirements Requirements Organizational Design Systems Analysis and and Change Design Management 3
  • 5. Avoiding Confusion Many people seem to confuse the three because the work requirement is used in all three. Ee use the following terms in the Requirements Excellence Framework: Business Objectives and Constraints Business Objective - Reduce delinquent accounts to 10% or less, within three months. Project Constraint - The software must be delivered by March 31st, 2012. Technical Constraint – The system must utilize the Oracle Database to comply with our standards. Needs User Need – As an accounting clerk, I need the ability to cancel transactions. Requirements Functional Requirement - System shall permit users to cancel transactions with an audit trail. Supplemental Requirement –-The system must be available 24 hours a day from Monday to Saturday. A statement about “how” the solution will work as opposed to “what” it is intended to do should be captured in the Design Document. The statement below is not a requirement. “The Location shall be selected from a drop-down list” 4
  • 6. Business Rules Project Feature Impact Process Category Rule Book Scope Statement Business rules are maintained separate from requirements. They Functional Supplemental Requirement Requirement are organized by rule book for various functional topics such vacation and holiday leave, travel, customer service, etc.). Each rule Business Rule Related Rules book has a rule book owner. Rule books are ideally maintained by the business. Rules may be linked to requirements. 5
  • 7. Business Processes Process Category Feature Project Impact Process Group Scope Business Process Statement Process Impact Activity Functional Supplemental Requirement Requirement The process structure is organized using During Process Analysis, impacts on Since software is used to APQC’s Process Classification Structure existing business processes are provide automated support (PCF). The PCF was developed by APQC identified and documented . for a business process, it is and its member organizations as an open Depending on the size of the essential to understand how standard to facilitate improvement project, AS IS and TO BE business the process is going to work through process management and process models may be created or before defining software benchmarking, regardless of industry, size, updated. The business process requirements. or geography. The PCF organizes operating impacts are later used in the and management processes into 12 Project Scope Activity to define enterprise-level categories, including scope statements which are used process groups and over 1,000 processes to elicit needs from Stakeholders 6 and associated activities. and specify requirements.
  • 8. Stakeholders Stakeholder Stakeholder Project Profile Contact Contact Product Product Project Stakeholder Stakeholder Project Project Stakeholders and Project Stakeholder contacts are identified during Stakeholder Analysis. Feature Stakeholder Needs are identified during Elicitation through a Impact variety of elicitation techniques such as web forms, Stakeholder Need interviews, observations and group discussion. They are captured using patterns and organized by Product Stakeholder and cope Statement. Scope User Stories are a special type of need often used on Agile User Story Statement projects. They are normally in the form of As…, I want to… so that I can ….. Stakeholders are linked to user stories via the As a … clause of the user story. Use Case Use Cases are developed by the analyst during Analysis to gain a better understanding of the sequence of events and 7 user involvement.
  • 9. Products Project Product Feature Scope Feature Impact Statement Functional Supplemental Requirement Requirement Products may be implemented many ways depending on the needs of the organization. For example, products could be applications, ITIL Services, or products or services sold to external customers. A project can impact one or many products. Defining scope statements depends on having feature (Product) and Process impacts identified and documented. 8
  • 10. Projects The Project, the Project Vision and Project Constraints Stakeholders that are defined during the Project Vision activity. are impacted by the project are Project Vision identified during Project the Stakeholder Stakeholder Project Analysis activity Project Constraints Impact on the product portfolio. Feature Impact These are identified during the Project Business Objectives Scope activity SMART business objectives are Scope documented during the Business Process Impact Business process Statement Objectives activity. impact that are identified and documented during Process Analysis. Requirement Functional Supplemental Requirement Requirement Management. Plan Functional requirements, supplemental requirements and The Requirement Management Plan related business rules are Related Rules defines the approach and set of developed during the tasks to complete Requirements Specification activity, Development and Management activities. 9
  • 11. Requirements Development Scope Statements are defined in the Project Scope activity and Process Impacts are used to elicit needs and specify requirements. identified during Process Process Analysis and used to Impact define scope statements. Project Stakeholders are identified Scope during Stakeholder Analysis Impacts on products and and used to define stakeholder Statement Feature services are identified during needs and user stories. Project Impact Project Scope and are used to stakeholders are also used as actors create scope statements. in Use Cases. Supplemental Supplemental Requirements Stakeholder Need Requirement are created during Specification. Project User Story Stakeholder Functional Functional Requirements are created during Requirement Use Case Specification. Stakeholder Needs are User Stories are a special type Use Cases are Related Rules identified during Elicitation of need which are created developed by the analyst through a variety of during Elicitation. during Analysis to gain a Related Rules are identified elicitation techniques such as better understanding of during Specification and web forms, interviews, the sequence of events linked to a requirement. observations and group and user involvement. discussion. Note that Requirements Development is an iterative and incremental activity. Generally Elicitation, Analysis, Specification, and Validation go on concurrently. 10
  • 12. Requirement Management Functional and Supplemental Stakeholder Need User Story Use Case Requirements are grouped into bundles. Associated User Stories, Use Cases Stakeholder Needs, and Related Related Rules Business Rules are included by Functional Supplemental reference. Requirement Requirement Lifecycle Events are identified based on the type of requirements in the bundle. Lifecycle Events include such things as Validation, Design Reviews, User Bundles Acceptance Testing, Code Inspections, Sprint Plans, etc. Lifecycle Event Change Requests Defects After a bundle has Participants Test Scenarios Validations Requirement defects been baselined, all are recorded and changes, additions, Project Stakeholders Validations are performed tracked to ensure they and deletions are participate in Test Cases to confirm such things as: are resolved. controlled and lifecycle events to • needs are addressed, tracked. perform tests and User Acceptance Tests • developers understand validations of the are defined to ensure the requirements, and requirements. that the solution meets • there is sufficient budget the defined to build the solution. requirements. 11