Technical Business Analysis

Definition:

In A Guide to the Business Analysis Body of Knowledge®BABOK®Guide) published by International Institute of Business Analysis (IIBA) business process is defined as “…a set of defined ad-hoc or sequenced collaborative activities performed in a repeatable fashion by an organization.”
version 3 goes on to state: “Business analysis is the practice of enabling change in an enterprise by defining needs and recommending solutions that deliver value to stakeholders.”
Technical Business Analysis is to approach analysis from an existing systems point of view, reverse engineering existing systems rather than eliciting all the requirements from the business users.

Wikipedia: https://en.wikipedia.org/wiki/Business_analysis
IIBA link: http://www.iiba.org/ quotes are attributable as fair use
Requirements: https://en.wikipedia.org/wiki/Requirements_analysis
Functional Specifications: https://en.wikipedia.org/wiki/Functional_specification
Software Engineering Body of Knowledge (SWEBOK) is an international standard ISO/IEC TR 19759:2005: https://en.wikipedia.org/wiki/Software_Engineering_Body_of_Knowledge

Goals:

·         Process improvement or documentation

·         Software Development fit for purpose to cater for the business processes

Products: (the following may be produced by either waterfall or agile methods and iterations.)

·          Gap Analysis document (functional Gap between existing processes and new methods particularly when adopting new Software, primarily used as a guide for re-training users)

·          Functional Specifications (Use Cases for Process improvement & Software Development, our equivalent of Requirements document)

·          Technical specifications (For Software Development, sketch-ups and how to instructions)

·          Entity relationship maps (for Process improvement & Software Data Development)