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.
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.
brought to you by enabling practitioners & organizations to achieve their goals using:
Advertising Opportunities | Contact Us