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
299 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

Surbhi Mahnot
Surbhi Mahnot
Requirements define the needs of the project to provide best of its utility and benefits. If they aren’t clear or analysis is not done properly, it might lead to failure of the project no matter how good the concept and design is. Just as a system is composed of various functionalities, requirements too are identified in various forms. This ...
0 Responses
Sanjay Yadav
Sanjay Yadav
 Challenges in Implementation:     I’m a strong believer of putting finishing touch to any initiative. Project Initiation is always tough and complex and need lots of research but if BA is unable to give the finishing touch then he is not done yet. So, I thought to put few of my views, challenges and observations during...
1 Responses
Surbhi Mahnot
Surbhi Mahnot
All professionals talk about identifying business needs, identifying requirements to create tools so that they can help businesses take better decisions. In your career as an IT professional, I am sure at some point you must have heard terms such as “Requirements”, “Business Requirements”, “Software Requirements”...
2 Responses




Featured Digital Library Resources 
Copyright 2006-2015 by Modern Analyst Media LLC