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

Fabricio Laguna talks Business Analysis and AI
I recently connected with Fabricio Laguna, aka The Brazilian BA. Fabricio is a passionate and pioneering business analyst from Brazil. During our conversation, we had a thought-provoking discussion on how artificial intelligence stands to shape the field of business analysis in the years ahead. While AI promises to transform many aspects of busines...
Business Architecture, Ontology and More with Terry Roach
It's been a privilege meeting Terry Roach, a visionary in the field of enterprise architecture and business architecture. Terry's insights into the evolution of business models, the importance of ontology in architecture, and the potential of AI to shape our future were not only thought-provoking but also a reflection of his extensive exper...
Today I had the pleasure of chatting to Jignesh Jamnadas, Chief Operations Officer at Mosaic, about his Blueprints for Success. As a Senior Finance and Operations Executive, Jigs (as he is known to many) has a holistic understanding of all facets of business and a flair for managing both people and processes. Having worked with Jigs, I was struc...

 



Upcoming Live Webinars




 

Copyright 2006-2024 by Modern Analyst Media LLC