Forums for the Business Analyst

 
  Modern Analyst Forums  Business and Sy...  Requirements  Migration User Requirements
Previous Previous
 
Next Next
New Post 1/23/2015 10:46 AM
User is offline Davie
1 posts
No Ranking


Migration User Requirements 

Hi I am on a short term contract to come up with a solution for a data catch up between the migration phase and the go live phase of a migration program.  I have to document the user requirements for this and I am currently analyzing the data fields and sources for each.  I have this in a good place in the requirements catalogue but I am unsure how to transfer this into the user requirements document.  Is there a standard way this is documented?

I am thinking of recommending a SQL database for the comparison of migrated data to new/changes to the data entered in the legacy system but I do not have template or previous example for the functional specifications for this .  Can someone point me in the direction of one or both of these.

Apologies for the short explanation.  Any help greatly appreciated.

 

Davie.

 

 
New Post 1/23/2015 7:02 PM
User is offline NitWitNick
243 posts
6th Level Poster


Re: Migration User Requirements 

I'm probably reading your problem wrong ... but ...

Data Catch-Up ? What are you catching up ? Are you migrating and mapping data from some source-to-target (another system) ? Is there a table with data somewhere waiting to update the current database (ie: LockBox - a collection payments, orders, etc. that needs processing).

What could the user requirements be on a data migration ? ... "The Data Must Be Migrated Correctly And Available For Use By Monday Morning" ? Other user requirements could be identifying, processing, running reports on the migrated data differently ... which could be programming / user interface changes.

Don't you have a test database somewhere to initially load the migrated data in, unit test it and run current applications against it to test the successful mapping of migrated data ?

Now that things look OK, you will move the data into the production database and test again for success ... 

"a solution for a data catch up (between the migration phase and the go live phase of a migration program)." ... isn't that the QA part of the migrated data with end-users, test scripts and scenarios to verify that the new data was mapped correctly for your current system applications ?

Make sure none of the migrated will overlay any of the current system data ... wiping out current stuff with older stuff.

Do you have a Roll-Back plan in case something goes wrong on the production system ?


Like I said ... I probably read it all wrong and am missing some computer term ... but I'm not familiar with a "Data Catch Up".

 

 
New Post 9/15/2015 6:14 AM
User is offline Ndome
1 posts
No Ranking


Re: Migration User Requirements 
Modified By Chris Adams  on 9/15/2015 10:15:48 AM)

Hi NitwickNick,

Hope this finds you well. Your response above tells me you know your way around data migration undertakings. I am hoping you can help clarify or give me some pointers to help me fuflil my role in such a project. I am a 2 year BA but this is my first Data Migration project. My general feeling is that the role of a BA is not full in such projects. I am currently looking at Migration Principles/Rules/Requirements & Data Mapping. Some tips and guidance on best practice on these would really help. Also, could you please give me an idea of which areas to really take ownership for apart from the above?

Many thanks

Ndome

 
New Post 9/26/2015 5:46 PM
User is offline NitWitNick
243 posts
6th Level Poster


Re: Migration User Requirements 

Depending on technical you are, I would take a look at the databases you are using for migration ... check the data you have and where to put them in the new database (data mapping) ... data might be the same but field names might be different or one field might now hold the concatenation or calculations of other fields, etc.

Data mapping always took the longest for me because I was not familiar with the other system ... I usually worked with some tech person from the new database ... once that was done, then I could write the specs so it is know what goes where, what does not, needed database changes, etc. I usually set up an As-Is / To-Be database table images and showed the data migration in pictorial form.

What data is needed (all or just the last 5 years), what could be eliminated or stored in some data warehouse so it could be accessed if needed.

 

 
Previous Previous
 
Next Next
  Modern Analyst Forums  Business and Sy...  Requirements  Migration User Requirements

Community Blog - Latest Posts

Bert Wagner
Bert Wagner
It’s 4:30 pm on Friday and Mr. Manager comes along to tell you that he needs you to run some important ad-hoc analysis for him. Previously this meant having to stay late at the office, writing cumbersome queries to extract business information from transactional data. Lucky for you, you’ve recently started using Temporal Tables in SQL...
1 Responses
Ronak Sanghavi
Ronak Sanghavi
Current State For many years now, the most commonly used metaphor on Business Analysis has been the “Bridge”. However, in recent past, some in the BA community have started revisiting the metaphor resulting in a debate on how relevant it is. Of course, the value business analysis can provide for an organization does not depend on how i...
4 Responses
SarikaA
SarikaA
Pega systems(Software Company) is the leading provider of business process management (BPM) and customer relationship management (CRM) software solutions. Pega systems motto is “Build For Change” and their goal is to “eliminate software coding” and “automate manual work”. Pega systems has bee...
1 Responses




Latest Articles

Agile User Interface Design
Sep 24, 2017
0 Comments
The role of design still puzzles many agile teams I work with. When should the design activities take place? Who should carry them out? How are design...
Featured Digital Library Resources 
Copyright 2006-2015 by Modern Analyst Media LLC