ecba-L1.6. Key Terms and Definitions

Per l’esame ECBA è necessario conoscere i termini chiave, le classificazioni dei requisiti, le definizioni degli stakeholder e la differenza tra requisito e design facendo riferimento al capitolo 2 del BABOK Guide V3.

Studiate Requirement Classification Schema; Business Requirements; Stakeholder Requirements; Solution Requirements: Functional Requirements – Non-Functional Requirements; Transition Requirements. Fate riferimento alla tecnica 10.30 Non-Functional Requirements (BABOK Guide V3) per le definizioni che incontrerete.  Dovete essere in grado di riconoscere i tipi di requisiti che vi vengono presentati.

Inoltre, prestate particolare attenzione ai ruoli associati agli Stakeholder e alle definizioni, dovrete saperli riconoscere nel contesto delle domande.  

Dovete saper riconoscere i Requirements e i Design nel contesto delle domande.

Studiate i Key Terms per acquisire il linguaggio che viene utilizzato nella disciplina della Business Analysis.

Key Terms

Il BABOK Guide V3 include una sezione sui “Key Terms” nel Capitolo 2. Dovete comprendere le terminologie di riferimento.

Qui riportiamo alcuni termini chiave importanti da ricordare:

• Business analysis information: Any kind of information at any level of detail used as input or output of business analysis work. This extends beyond just “requirements” to include elicitation results, designs, solution options, scope, and change strategy.

• Business analysis package: A collection of text, matrices, diagrams, and models that represent business analysis information.

• Business analyst: Any person who performs business analysis, regardless of their job title or organizational role.

• Verification (business analysis): The process of confirming that a deliverable or artifact meets an acceptable quality standard.

• Validation (business analysis): the process of checking that a deliverable is suitable for its intended use.

• Requirements validation: work done to evaluate requirements to ensure they support the delivery of the expected benefits and are within the scope of the solutions.

Requirements Classification Schema

Le categorie dei Requisiti consentono di iniziare da subito ad avere un approccio di analisi strutturato che permette di tracciare i requisiti e favorire l’allineamento continuo ai reali bisogni (needs) e al valore.

The Business Analysis Standard lists four main requirement types: business requirements, stakeholder requirements, solution requirements (which include functional and non-functional requirements), and transition requirements. Categorizing requirements helps ensure full understanding, completeness, and appropriate traceability.

Business Requirements: Statements of goals, objectives, and outcomes describing why a change has been initiated. They can apply to the whole of an enterprise, a business area, or a specific initiative – Subject is the Enterprise and refers to the Strategy.

Stakeholder Requirements: Describe the needs of stakeholders that must be met to achieve business requirements. They serve as a bridge between business and solution requirements. The subjects are the people.

Solution Requirements: Describe the capabilities and qualities of a solution that meets the stakeholder’s requirements. They provide an appropriate level of detail to allow for development and implementation. They refer to the Solution. They are divided into 2 categories: Function requirements – capabilities a solution must have in terms of the behaviour and information that the solution will manage; Non-functional requirements – describe conditions under which a solution must remain effective or qualities that a solution must have. Studiate la Tecnica 10.30 Non-Functional Requirements Analysis: dovete conoscere le 15 categorie comuni: Availability; Compatibility; Functionality; Maintainability; Performance Efficiency; Portability; Reliability; Scalability; Security; Usability; Certificaton; Compliance; Localization; Service Level Agreements; Extensibility.

Transition Requirements: Describe the temporary capabilities a solution must have to facilitate transition from current to future state. They include: data conversion, training and business continuity.

Di seguito trovate Esempi di Requirements per Type.

Stakeholder

Attenzione agli Stakeholder. Dovete conoscere le definizioni delle categorie di Stakeholder identificate nel BABOK Guide V3 – Chapter 2. Dovete saper riconoscere gli stakeholder e i loro ruoli nel contesto delle domande. Dovete saper usare le tecniche10.43  Stakeholder List, Map, Personas, RACI (BABOK Guide V3) fondamentali per identificare, gestire e ingaggiare gli stakeholder. La collaborazione e la comunicazione con gli stakeholder sono fondamentali per il successo dell’analisi: ottenere il valore per l’organizzazione.

Understanding who the stakeholders are, how proposed changes impact them, and their potential influence on the change is vital.

Collaboration is defined as two or more people working together towards a common goal. Effective collaboration requires stakeholders to feel heard and valued, and involves regular, frequent, two-way communication.

Requirements and Designs

Dovete saper distinguere tra Requirements e Design (BABOK Guide V3 – Chapter 2.5).

Eliciting, analyzing, validating, and managing requirements are consistently recognized as key business analysis activities. Business analysts are also responsible for defining design, at some level. The level of responsibility for design varies based on the perspective.

A design is a usable representation of a solution, focusing on how value might be realized.

The primary difference between requirements and design lies in how they are used and by whom. One person’s design can be another’s requirement .

Business analysis transforms a request or proposed solution into a requirement or design by asking “why?” it is needed to provide value and support objectives

Modeling needs, requirements, designs, and solutions is instrumental for thorough analysis and communication.

Verified requirements are of sufficient quality for further work.

Validated requirements ensure they provide value and support organizational objectives.

In sintesi, il Dominio 1 si concentra sulla comprensione fondamentale di ciò che è la business analysis, i concetti fondamentali che ne sono alla base (BACCM), come questi concetti vengono utilizzati nella pratica e perché la disciplina è cruciale per il successo organizzativo e la fornitura di valore.