Career Forums

Modern Analyst Forums Business and Sy... Business Proces... gap analysis, the definition and areas of application

6/24/2009 9:13 PM

	KJ
243 posts

Re: gap analysis, the definition and areas of application

Tony,

The “as-is” essential model contains the “what” without the detailed “how”.

(Green analysts get confused with the “HOW” of things, especially when dealing with knowledgeable SMEs. They tell the Analyst “HOW” they “pay an invoice” rather than “WHAT” they do. )

The essential DFDs are then enhanced; that is, functionality (the gap) is added to the “as-is” essential model resulting in the “to-be” model. Automation boundaries and implementations may differ between the “to-be” and previous models.

[Digression: someone asked recently when do we use declarative requirements of the type “the system shall ..”. Well, the essential “to-be” model is a good starting point from which to list these declarative requirements. Eg. The system shall/must be able to “pay an invoice”]

The vertical axis in my drawing above identifies parts of the NON-Functional Requirements.

Warm regards,