Forums for the Business Analyst

 
  Modern Analyst Forums  Business and Sy...  Requirements  Transitional Requirements - showing process statuses between legacy and future system
Previous Previous
 
Next Next
New Post 2/23/2016 8:23 PM
User is offline transitioned
13 posts
10th Level Poster


Transitional Requirements - showing process statuses between legacy and future system 

Hi All

We re creating a licensing system.  There are 2 main functional groups: licensing and compliance.  In phase 1 we're delivering for Compliance - i.e. they will be the only group using the system.

The high level value chain is:

Application --> Licence --> Licence Conditions --> Inspection --> Enforcement Action

Licensing and Compliance pass information back and forth about licensees.

The question is should we just replicate the old licence statuses in the new system. 

One principle I've used is that Compliance only deal with licenses that are in effect.  So any status where the licence is still an application shouldn't be shown in the new system - because the licence doesn't exist yet.

Another is that some records have statuses that don't exist in the legacy system anymore, therefore those statuses should be mapped NOT replicated.

My issue is more deciding to map or just replicate the statuses that still are valid in the old system and do relate to final licences that have been granted.

But for other statuses should I just replicate the status in the new system?  E.g. in source system we've got a status of 'withdrawn'  currently we're mapping that to 'inactive'.  And there's other statuses that are mapping to inactive - so we're consolidating a list of source statuses to a smaller list of target statuses.

 

 

 
New Post 3/10/2016 9:15 AM
User is offline Chris Adams
323 posts
5th Level Poster






Re: Transitional Requirements - showing process statuses between legacy and future system 

Without understanding a lot more detail about your project and systems it's hard to give a definite answer.

However, I can give you this advice.  If certain statuses make no sense for a user of a particular system, why would you show them at all?  Therefore, it sounds like you would either show a subset of statuses that DO apply, or maybe there is a reason to map certain statuses to another status.


Chris Adams
Core Member – ModernAnalyst.com
LinkedIn Profile
 
Previous Previous
 
Next Next
  Modern Analyst Forums  Business and Sy...  Requirements  Transitional Requirements - showing process statuses between legacy and future system

Community Blog - Latest Posts

In today's dynamic business environment, mastering effective business analysis techniques is crucial for organizations aiming to achieve sustainable growth and competitive advantage. Business analysis involves the systematic evaluation of business processes, requirements, and strategies to uncover insights that drive informed decision-making. T...
For many years now, a lot of people have found it difficult to identify the difference between Sankey diagrams and parallel sets. The two have made headlines, given that most people find it challenging to note what makes them different from each other. What remains to be undeniable is the fact that the Sankey diagram is among the top data visualiza...
Hosted by Deirdre Caren on Agora Insight's Blueprints for Success - Business Architecture and AI In our recent conversation with Joseph Edward, we explored the transformative power of business architecture (BA) and technology as tools for uplifting communities. Joseph, with his rich background spanning from education to IT leadership, shared...

 






 

Copyright 2006-2024 by Modern Analyst Media LLC