What comes first…Gap Analysis or Use Case development?

What comes first…Gap Analysis or Use Case development?

It’s a good question and one we often get asked, but like most things in an imperfect World, the answer is “it depends!”

If we look at the OUM Method Pack and examine the dependencies for the Gap Analysis Tasks, then we see that one of the key pre-requisites are Use Case Specifications.

So that means we have to write a Use Case before doing any Gap Analysis…..right?.....well, it depends!!!

Consider the following two examples:

Let’s say you are implementing one of Oracle’s COTS applications, for example, eBS, Fusion or PeopleSoft etc. We might begin by capturing functional requirements by iteratively developing a Future Process Model. During that process you discover that the client has some requirements that cannot be met using the standard features of the application. If those requirements are reasonably well understood, then you would most likely drop into the OUM Gap Analysis “Process”. If the result of that process is a decision to go down a custom development path in order to close the “Gap” then one or more Use Cases could be created in order to fully describe the functional solution to the Gap.

Now consider this scenario. Your client is designing a solution that includes Single Sign-On, Business Intelligence and some components of Content Management. In this type of environment, it’s especially important to ask ourselves “what is the best way to capture functional requirements?” Why you may ask?............well, for projects that are process centric (e.g. Order-to-Cash, Procure-to-Pay) one would tend to favor the development of a Future Process model in order to define functional requirements. However, for projects that are not centered around traditional business processes, then we might want to consider leading with a Use Case approach in order to capture the client’s functional requirements.

In this second example, we probably won’t discover any Gaps until we go through the first iteration of Use Case development. But if we do uncover any Gaps, then our Use Cases will be an ideal direct input into the Gap Analysis process.

So what comes first Gap Analysis or Use Case Development?…..well just like the Chicken-and-Egg story, it all depends!!

Comments:

Hi Dave,
very interesting indeed. As an apps oriented guy I did not realize the second possibility.
Kind regards
Francis

Posted by Francis Moeris on February 23, 2012 at 09:44 PM GMT+05:00 #

This article really helps ! Thanks for the sharing ! If you want another reference, you can visit our site now !

Posted by Katie on May 25, 2012 at 03:25 AM GMT+05:00 #

Post a Comment:
  • HTML Syntax: NOT allowed
About

OUM Logo
The Oracle® Unified Method (OUM) is Oracle’s standards-based method that enables the entire Enterprise Information Technology (IT) lifecycle.

Read:

· Brief

· White Paper

· Customer Program Data Sheet

Connect:

· OUM on Twitter

· OUM on LinkedIn

Search

Archives
« April 2014
SunMonTueWedThuFriSat
  
1
2
3
4
5
6
7
8
9
10
11
12
13
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today
Feeds