Below are the types of governance processes BAs should know about:
- Business Analysis Governance
- Change Governance
- Data Governance
- IT Governance
- Project Governance
- Organizational Governance
Below are the types of data migration:
- Application Migration - Moving an application program from one environment to another.
- Business Process Migration - Moving business process applications, data, and metrics to a new environment.
- Cloud Migration - Moving data, application, or other business elements from either an on-premises data center to a cloud or from one cloud to another.
- Database Migration - Moving from one database management system (DBMS) to another or upgrading from the current version of a DBMS to the latest version of the same DBMS.
- Storage Migration - Moving data off existing storage structures into better-performing ones that enable other systems to access it.
Below are considerations for prioritizing and ordering a product backlog:
Prioritization Considerations:
- Benefit (tangible and intangible value)
- Penalty
- Cost (tangible and intangible)
- Project Dependencies
- Product Risk
- Time Sensitivity
- Requirement Stability
- Regulation or Compliance
Ordering Consideration
- PBI Dependency (necessity and effort)
- Implementation Risk
- Delivery Team Capacity
- Implementation Complexity
- Implementation Cost
Below are the characteristics of each entity-relationship diagram stage:
Conceptual ERD
- Least amount of detail
- Communicates overall scope of a system
- Includes entities and their relationships
- Easy for the business to understand
- Easy to update
- Often created on paper or a whiteboard
Logical ERD
- More detail than a conceptual ERD
- Communicates operations, transactions, and business rules
- Introduces the attributes and relationship cardinality
- Database agnostic
- Easy for the business and technical team to understand
- Takes more effort to update
- Best represented with a diagramming tool
Physical ERD
- The most amount of detail
- Communicates physical structure of a database
- Introduces database-specific data types
- Entities become tables
- Attributes become columns
- Difficult for the business to understand
- Requires the most effort to update
- Best represented with a data modeling software
Below are some tools and techniques to facilitate functional coverage from the BA perspective according to BABOK.
- Document Analysis - When documents are up to date, identifying and consulting all potential requirements sources will result in improved requirements coverage.
- Functional Decomposition - Breaks functions down into smaller pieces to allow for analysis of the detailed processes to ensure coverage of all processes that are relevant to a potential solution.
- Interface Analysis - Early identification of interfaces allows the business analyst to provide the context for eliciting more detailed stakeholder requirements, thus determining adequate functional coverage.
- Roles and Responsibility Matrix - Used to ensure coverage of activities and functions by indicating responsibility to identify roles and discover missing roles.
- Traceability Matrix - Ensures requirements and design coverage by identifying clearly defined requirement relationships.
