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 9: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 10:15 AM
User is offline Chris Adams
307 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

Limor Wainstein
Limor Wainstein
Business analysts typically gather and interpret data from many areas within an organization, finding solutions to business problems and improving business processes with all that data. A business analyst may measure and improve on such disparate things as warehouse efficiency and cloud software implementation. A marketing analyst, on the other...
0 Responses
EA Learning
EA Learning
My current, favourite question for Executives and Architects is “How do you see Architecture operating in an Agile environment.” This question usually elicits a wry smile and a response along the lines of “I will need to get back to you on that!” Many people are wondering how Architecture will fair in the world of Agile. My ...
0 Responses
Limor Wainstein
Limor Wainstein
The age of cloud computing is now so firmly established that research firm Gartner predicted by 2020, a corporate "no-cloud" policy will be as rare as a "no-internet" policy is today. In the same press release, Gartner went on to predict that spending on compute power sold by cloud providers will exceed that of compute power sold and deployed into ...
0 Responses


Upcoming Live Webinars



Latest Articles

Intelligent Business Requirements
Jan 21, 2018
0 Comments
Intelligent Business Requirements are business needs and objectives that were designed to add business value and promote scalability and innovation. ...
Featured Digital Library Resources 
Copyright 2006-2015 by Modern Analyst Media LLC