Anonymous, bureaucrat, administrator
7,528
edits
Changes
m
# The contact list is loaded with whatever data is available into a new form. (The green form image in the diagram)
# The form is refined to make it usable for contact operations
# A data cleaning exercise is performed to remove dud records e.g. no name, test records, etc.
→Person-centric build approach
[[File:Personcentric-002.png]]
== Data Loading ==
If a company has been in existence for a while, then they will have amassed customer data and it is probably in various places. Operational systems, accounting systems, Excel spreadsheets and older systems.
# The data is loaded with whatever data is available into the new person form.
# The form is refined to make it usable for contact operations
# A data cleaning exercise is performed to remove dud records e.g. no name, test records, etc.
== Form Design ==
# The fields in the new form are aligned with the fields available in the Person database.
# A further cleaning exercise is performed which allows information in the central Person database to filter into the form, especially regarding contact permissions.
With a central repository of existing customers all marketing campaigns will be required to keep this repository up to date. This could cause an excess of update management and systems communications issues. By centralising all updates from the Person table systems such as a data warehouse can be updated from the central person record which has been fed by all marketing campaigns.
= Project Outline Steps =