Business Analysis and Requirements

Our business analysis approach may include:

• Identifying requirements based on using IT as an enabler to improve your business process
• Preparing feasibility analysis and business cases
• Facilitating workshops
• Identifying requirements and use cases for information technology
• Developing data models and “To Be” business process models (includes how the manual and automated parts of the process fit together)
• Transitioning requirements & “To Be” business processes into test plans & training
• Managing organizational/people change
• Ensuring sustainability

Data requirements

During facilitated business process sessions, we are capturing data requirements. We capture data at an entity (table) level, then may provide more detail (attribute/field level) especially in areas of major change.

Functional requirements

During facilitated sessions, we are capturing how the system should behave and what tasks it should perform within the business process. We also identify the different possible scenarios (to develop use cases).

Business rule requirements

Systems implementation often fail because critical business rules were not identified. Kogawa is an early proponent of business rules and has proven guidelines for capturing business rules.

Security and access requirements

When new ways of performing the business process are identified, there may be new security and access implications.

Volume requirements

The volumes (e.g. number of traffic tickets) are identified to understand storage requirements and what tests are required.