Diese Präsentation wurde erfolgreich gemeldet.
Wir verwenden Ihre LinkedIn Profilangaben und Informationen zu Ihren Aktivitäten, um Anzeigen zu personalisieren und Ihnen relevantere Inhalte anzuzeigen. Sie können Ihre Anzeigeneinstellungen jederzeit ändern.

Sample - Data Warehouse Requirements

43.402 Aufrufe

Veröffentlicht am

Example requirements docuemntation for data warehousing

Veröffentlicht in: Technologie, Business
  • DOWNLOAD THIS BOOKS INTO AVAILABLE FORMAT (2019 Update) ......................................................................................................................... ......................................................................................................................... Download Full PDF EBOOK here { https://soo.gd/irt2 } ......................................................................................................................... Download Full EPUB Ebook here { https://soo.gd/irt2 } ......................................................................................................................... Download Full doc Ebook here { https://soo.gd/irt2 } ......................................................................................................................... Download PDF EBOOK here { https://soo.gd/irt2 } ......................................................................................................................... Download EPUB Ebook here { https://soo.gd/irt2 } ......................................................................................................................... Download doc Ebook here { https://soo.gd/irt2 } ......................................................................................................................... ......................................................................................................................... ................................................................................................................................... eBook is an electronic version of a traditional print book THIS can be read by using a personal computer or by using an eBook reader. (An eBook reader can be a software application for use on a computer such as Microsoft's free Reader application, or a book-sized computer THIS is used solely as a reading device such as Nuvomedia's Rocket eBook.) Users can purchase an eBook on diskette or CD, but the most popular method of getting an eBook is to purchase a downloadable file of the eBook (or other reading material) from a Web site (such as Barnes and Noble) to be read from the user's computer or reading device. Generally, an eBook can be downloaded in five minutes or less ......................................................................................................................... .............. Browse by Genre Available eBooks .............................................................................................................................. Art, Biography, Business, Chick Lit, Children's, Christian, Classics, Comics, Contemporary, Cookbooks, Manga, Memoir, Music, Mystery, Non Fiction, Paranormal, Philosophy, Poetry, Psychology, Religion, Romance, Science, Science Fiction, Self Help, Suspense, Spirituality, Sports, Thriller, Travel, Young Adult, Crime, Ebooks, Fantasy, Fiction, Graphic Novels, Historical Fiction, History, Horror, Humor And Comedy, ......................................................................................................................... ......................................................................................................................... .....BEST SELLER FOR EBOOK RECOMMEND............................................................. ......................................................................................................................... Blowout: Corrupted Democracy, Rogue State Russia, and the Richest, Most Destructive Industry on Earth,-- The Ride of a Lifetime: Lessons Learned from 15 Years as CEO of the Walt Disney Company,-- Call Sign Chaos: Learning to Lead,-- StrengthsFinder 2.0,-- Stillness Is the Key,-- She Said: Breaking the Sexual Harassment Story THIS Helped Ignite a Movement,-- Atomic Habits: An Easy & Proven Way to Build Good Habits & Break Bad Ones,-- Everything Is Figureoutable,-- What It Takes: Lessons in the Pursuit of Excellence,-- Rich Dad Poor Dad: What the Rich Teach Their Kids About Money THIS the Poor and Middle Class Do Not!,-- The Total Money Makeover: Classic Edition: A Proven Plan for Financial Fitness,-- Shut Up and Listen!: Hard Business Truths THIS Will Help You Succeed, ......................................................................................................................... .........................................................................................................................
       Antworten 
    Sind Sie sicher, dass Sie …  Ja  Nein
    Ihre Nachricht erscheint hier
  • DOWNLOAD THIS BOOKS INTO AVAILABLE FORMAT (2019 Update) ......................................................................................................................... ......................................................................................................................... Download Full PDF EBOOK here { https://soo.gd/irt2 } ......................................................................................................................... Download Full EPUB Ebook here { https://soo.gd/irt2 } ......................................................................................................................... Download Full doc Ebook here { https://soo.gd/irt2 } ......................................................................................................................... Download PDF EBOOK here { https://soo.gd/irt2 } ......................................................................................................................... Download EPUB Ebook here { https://soo.gd/irt2 } ......................................................................................................................... Download doc Ebook here { https://soo.gd/irt2 } ......................................................................................................................... ......................................................................................................................... ................................................................................................................................... eBook is an electronic version of a traditional print book THIS can be read by using a personal computer or by using an eBook reader. (An eBook reader can be a software application for use on a computer such as Microsoft's free Reader application, or a book-sized computer THIS is used solely as a reading device such as Nuvomedia's Rocket eBook.) Users can purchase an eBook on diskette or CD, but the most popular method of getting an eBook is to purchase a downloadable file of the eBook (or other reading material) from a Web site (such as Barnes and Noble) to be read from the user's computer or reading device. Generally, an eBook can be downloaded in five minutes or less ......................................................................................................................... .............. Browse by Genre Available eBooks .............................................................................................................................. Art, Biography, Business, Chick Lit, Children's, Christian, Classics, Comics, Contemporary, Cookbooks, Manga, Memoir, Music, Mystery, Non Fiction, Paranormal, Philosophy, Poetry, Psychology, Religion, Romance, Science, Science Fiction, Self Help, Suspense, Spirituality, Sports, Thriller, Travel, Young Adult, Crime, Ebooks, Fantasy, Fiction, Graphic Novels, Historical Fiction, History, Horror, Humor And Comedy, ......................................................................................................................... ......................................................................................................................... .....BEST SELLER FOR EBOOK RECOMMEND............................................................. ......................................................................................................................... Blowout: Corrupted Democracy, Rogue State Russia, and the Richest, Most Destructive Industry on Earth,-- The Ride of a Lifetime: Lessons Learned from 15 Years as CEO of the Walt Disney Company,-- Call Sign Chaos: Learning to Lead,-- StrengthsFinder 2.0,-- Stillness Is the Key,-- She Said: Breaking the Sexual Harassment Story THIS Helped Ignite a Movement,-- Atomic Habits: An Easy & Proven Way to Build Good Habits & Break Bad Ones,-- Everything Is Figureoutable,-- What It Takes: Lessons in the Pursuit of Excellence,-- Rich Dad Poor Dad: What the Rich Teach Their Kids About Money THIS the Poor and Middle Class Do Not!,-- The Total Money Makeover: Classic Edition: A Proven Plan for Financial Fitness,-- Shut Up and Listen!: Hard Business Truths THIS Will Help You Succeed, ......................................................................................................................... .........................................................................................................................
       Antworten 
    Sind Sie sicher, dass Sie …  Ja  Nein
    Ihre Nachricht erscheint hier
  • Follow the link, new dating source: ❶❶❶ http://bit.ly/2u6xbL5 ❶❶❶
       Antworten 
    Sind Sie sicher, dass Sie …  Ja  Nein
    Ihre Nachricht erscheint hier
  • Dating for everyone is here: ♥♥♥ http://bit.ly/2u6xbL5 ♥♥♥
       Antworten 
    Sind Sie sicher, dass Sie …  Ja  Nein
    Ihre Nachricht erscheint hier
  • Positions Available Now! We currently have several openings for writing workers. ■■■ http://ishbv.com/easywriter/pdf
       Antworten 
    Sind Sie sicher, dass Sie …  Ja  Nein
    Ihre Nachricht erscheint hier

Sample - Data Warehouse Requirements

  1. 1. Data Management & Warehousing SAMPLE Requirements Examples DAVID M WALKER Version: 0.1 Date: 01/01/2006 Data Management & Warehousing 138 Finchampstead Road, Wokingham, Berkshire, RG41 2NU, United Kingdom http://www.datamgmt.com
  2. 2. Sample - Requirements ExamplesTable of ContentsTable of Contents ...................................................................................................................... 2Synopsis .................................................................................................................................... 3Intended Audience .................................................................................................................... 3About Data Management & Warehousing ................................................................................. 3Business Requirements ............................................................................................................ 4Data Requirements ................................................................................................................... 9 Dimensions ........................................................................................................................... 9 Performance Measures ....................................................................................................... 11Query Requirements ............................................................................................................... 15Interface Requirements ........................................................................................................... 16Copyright ................................................................................................................................. 17 © 2006 Data Management & Warehousing Page 2
  3. 3. Sample - Requirements ExamplesSynopsisThis document has a number of samples of completed sections from the four sets ofrequirements (Business, Data, Query and Interface) to aid analysts in completing their owntemplates. The requirements are a merger of actual requirements taken from Telcos aroundthe world. They are not consistent nor should anything be read into any requirements ascoming from any particular operator. There are no examples from the TechnicalRequirements as they do not have the same form of template table.Intended AudienceReader Recommended ReadingExecutive Synopsis through to BackgroundBusiness Users Synopsis through to BackgroundIT Management Entire DocumentIT Strategy Entire DocumentIT Project Management Entire DocumentIT Developers Entire DocumentAbout Data Management & WarehousingData Management & Warehousing is a specialist consultancy in data warehousing, based inWokingham, Berkshire in the United Kingdom. Founded in 1995 by David M Walker, ourconsultants have worked for major corporations around the world including the US, Europe,Africa and the Middle East. Our clients are invariably large organisations with a pressing needfor business intelligence. We have worked in many industry sectors but have specialists inTelco’s, manufacturing, retail, financial and transport as well as technical expertise in many ofthe leading technologies.For further information visit our website at: http://www.datamgmt.com © 2006 Data Management & Warehousing Page 3
  4. 4. Sample - Requirements ExamplesBusiness Requirements BUSINESS REQUIREMENTBusiness Requirement Number 1Business Requirement Name Organisations & Individuals (Customers)Priority HighCurrently available in the Data Warehouse YesDescriptionThere is a requirement to hold details and build a history of customers’ activities with Telco,tracking them through their Telco relationship ‘life cycle’, from initial marketing prospect,through sales, service provisioning, billing, etc.Organisations and individuals include customers and prospects for Telco products andservices and all others for which information can be obtained. Organisations may also beOLO (Other Licensed Operators) network customers, third-party dealers, the customers ofthird-party dealers, and other organisations such as Telco own business units, OFTEL,contractors, suppliers, etc.Note: prospects details are only required for prospects that have become customers orprospects that form part of the Target Account List.The information held for organisations and individuals must include name, address,postcode, etc. and a standardised version the customer name into a common searchformat.For organisations, other details should include: • Basic company information - business and trading names, company registration number. • A detail of all organisations sites e.g. addresses and service locations of installed equipment. • Parent company, subsidiaries, international ownership and partners • An indication of serviced customer or third party customer.The relationships between organisations and individuals must be maintained, e.g. multiplecontacts for customer organisations. This should include the individual’s full contact detailsand what they do, such as influencers, decision makers, finance/procurement contact, ITdirector or contact, telephony contact, billing contact, data network contact, marketingcontact, etc.These is also a need to hold enhanced profile information about organisations such as: • Turnover, numbers of sites and number of employees per site. • Telecomm profile - Comms spend (not just with Telco), telecomm products/services used, equipment used, other suppliers used (and products), PBX supplier. • OFTEL information on licensed operators.There is a need to maintain a history of the relationship between a customer and otherassociated information. This information includes contracts, orders, products and services,accounts, usage, non-usage, billing, payments, contacts, faults, sites, telephone numbers,sales channels, sales account manager, market segmentation, etc. © 2006 Data Management & Warehousing Page 4
  5. 5. Sample - Requirements ExamplesIt is required to be able to record and analyse organisations by a number of differentorganisational hierarchies. These hierarchies will change over time and customers mayalso be in multiple hierarchies at any one time. For example : • Customer defined hierarchies e.g. business and trading names of an organisation and all its subsidiaries and parent companies. This is how the customer sees himself or herself - this might be for revenue reporting purposes. • Legal hierarchies, e.g. as the government or tax authorities see a customer organisation - i.e. the official company structure. • Dun and Bradstreet method of customer hierarchies. • Wholesale customers may be made up of intermediary organisations that actually deal with Telco end user customers - where possible details of these levels should be held, i.e. from wholesaler to end user. • Telco defined hierarchies or groupings, such as: o Holding Company, Group Customer, Customer Account, Customer Site and Customer Line Identity. o Sales channel related hierarchies, i.e. how sales view their customers. o ‘Forced hierarchies’, e.g. car dealerships with different names. o Limited grouping of customers by customer name. o Marketing sectors, segments, geography.Over time, as history information is accumulated, these hierarchies will allow detailedanalysis of behaviour to be performed by relating the revenue, product, account, orders etc.together for an organisational structure.There is a requirement to have the ability to monitor and analyse - • Customer profitability. Initially this will only include interconnect in-payments / out- payments against products and services delivered. When available, sources of actual cost information should be included. • Product mix by revenue within customer. • Customer details, e.g. monthly numbers and revenue, by customer life cycle status, customer hierarchy level, SOV (Sales Order Value), product, price package, discount plan, actual and potential comms spend, installed equipment, geography, campaign response or marketing activity, market segment, sector. • Customer churn by product, reason, location, market segment, sector, sales channel, campaign code, etc. This will enable the proactive identification of revenue drop and provide customer churn KPI. • Number and names of customers lost, their worth and billing trends. • Other patterns in the customer base, e.g. customer lifecycle, customer historic trends, customer buying cycle, customer revenue, cost profiles, profitable/non- profitable, customer site moves, etc. • The dealer and reseller relationship, including revenue and payments, by call type, © 2006 Data Management & Warehousing Page 5
  6. 6. Sample - Requirements Examples national, mobile, international, etc. Also, aggregate third party customers into their respective dealers / suppliers. • Existing resellers and dealers to identify potential reseller and dealer companies. • OLO customer revenue (in-payments and out-payments) and usage patterns and trends, by routes/points of interconnect, tail costs, time of day, inbound, outbound, etc.Definition of Key Terms • Customer: An organisation or individual of interest to Telco in the provision of Telco products and services. Multiple views of a customer hierarchy may exist e.g. the customer own view of their organisation, Telco sales view, the billing systems view etc. • Prospect: A prospect is a customer that Telco intends to attempt to sell Telco products and services to. ‘Prospect’ is usually treated as a status of the customer as a whole, or of the customer for particular products, services or campaigns. • Organisation: An organisation is a grouping of one or more individuals, or of one or more companies, or other business activities, or for some other reason are required to be known about. An organisation may be a legal entity or just some recognised group. Examples of organisations include customers and prospects of Telco products and services, network customers, third-party dealers, the customers of third-party dealers, OLO (Other Licensed Operators), competitors, contractors, suppliers, government bodies, Telco own business units, etc. • Individual: An individual is a person for which information can be obtained. An individual may be associated with an organisation, for example as a contact for an organisation (e.g. influencers, decision makers, finance/procurement contact, IT director or contact, telephony contact, billing contact, data network contact, marketing contact, etc.). An individual may also be a customer or prospect for Telco products and services or the customer of a third-party dealer. • OLO (Other Licensed Operators): An organisation that is licensed by OFTEL to provide telecomm network services. • Customer Churn: Customer Churn is defined as the number of customers leaving Telco from a given level of the customer hierarchy as a proportion of the total customer base at that level (presented either as a number or a percentage and calculated at monthly, quarterly and yearly intervals) - churn is also calculated by the value of the customer leaving Telco as a proportion of overall revenue. • Dealer: A dealer is a third party organisation that has an existing business base through which it can sell standard Telco Branded Products. Telco owns the customer and consequently the Customer benefits from 24hr customer care and management reports etc. In return for acquiring customers on Telco’s behalf the dealer receives an ongoing revenue share’ this is a proportion the customers billing. • Reseller: The Reseller purchases Telco products at wholesale rates and resells them under their own brand. The contractual relationship is between the reseller and the customer, not Telco. The reseller sets his own retail pricing, bills the customer, arranges premise routing and provides customer care. Telco will provide the reseller with a monthly wholesale bill and provide customer care for bill queries and network faults to the reseller only, contact is not made between Telco and the resellers customer. The reseller can be further subdivided into two groups: those who aggregate carrier © 2006 Data Management & Warehousing Page 6
  7. 7. Sample - Requirements Examples minutes (an Aggregator) and those who merely resell (Direct Reseller) from one or two carriers. • Aggregator: By using smart MLU technology e.g. black box or via sophisticated PBX software, customer premise routing is made over a number of carriers according to price. Aggregators are able to maximise their buying power to secure the best possible rate for each route. Aggregators approach customers as an independent telecomm provider. The offer is to remove the purchase and pricing decision from the customer by pooling rates from all carriers and therefore always offering the best possible combination of rates. Effectively they will manage a customer’s telephony needs.Description of limitations of current data warehouse • The solution should not support lead tracking, contact management - Not all the information that the sales force will require is likely to be held in the warehouse as this will not be a suitable repository. • Prospect and Customer hierarchies - will need to be given as manual or automated input details of group customer s and holding companies. • Customer profitability - Initially this will only include interconnect payments/out- payments against products and services delivered. Sources of actual cost information to be investigated and reported on when available. • No payment information will be available until increment 4 Data OverviewPerformance Measures Dimensionality / Ordered By / Described By • Turnover • Customer (organisation, individual, • Number of sites TAL customer, OLO, supplier, • Number of employees dealers, resellers, aggregators etc.) • Telco spend (actual and potential) • Customer ‘life cycle’ status • Account measures • Organisation structure/hierarchy level • Revenue • Geography • Payment amount • Contract • Term • Orders • Number of accounts • Product • Customer measures • Account (status, date, etc.) • Profitability • Billing • Worth • Payment • Churn • Fault • Number of customers • Telephone number • SOV (Sales order value) • Call Distance • Network event measures (usage) • Network • Network tail cost • Sales channel hierarchy • Price, charge, discount (usage, • Market segment and sector non-usage) • Installed equipment • Campaign (response, activity) • Churn reason • TimeTechnical Assessment © 2006 Data Management & Warehousing Page 7
  8. 8. Sample - Requirements ExamplesData Retention RequirementsOther Comments © 2006 Data Management & Warehousing Page 8
  9. 9. Sample - Requirements ExamplesData Requirements Dimensions DIMENSION Dimension Number 1 Dimension Name Party Description The Party dimension represents individuals, their parent organisations and the higher-level organisation structure. Hierarchy Structure Holding Company Customer Reporting Customer Hierarchy Group Customer Account Customer Site Customer Line Identity Additional Descriptive Information This dimension is intended to represent individuals and organisations of interest to Telco – so, for instance, this may represent organisations with which Telco have a customer, supplier or interconnect relationship. The diagram above depicts one of the specific hierarchies that is required – the customer reporting hierarchy. Other requirements for the representation of organisation hierarchies may include : • Business and trading names of an organisation and all its subsidiaries and parent companies. • Legal hierarchies, e.g. as the government or tax authorities see a customer organisation - i.e. the official company structure. • Dun and Bradstreet method of customer hierarchies. • Wholesale customers may be made up of intermediary organisations that actually deal with Telco end user customers - where possible details of these levels should be held, i.e. from wholesaler to end user. © 2006 Data Management & Warehousing Page 9
  10. 10. Sample - Requirements Examples • Telco defined hierarchies or groupings, such as: o Sales channel related hierarchies, i.e. how sales view their customers. o ‘Forced hierarchies’, e.g. car dealerships with different names. o Marketing sectors, segments, geography. o TAL method of grouping customers for a sales account manager. o Customer hierarchies defined on an ad-hoc basis for Telco internal reporting. Organisations also include third-party dealers, the customers of third-party dealers, OFTEL, contractors and suppliers. No hierarchical structure within any of these is required. Data Steward Status Changes (Slowly Changing Dimensions) The customer reporting hierarchy is likely to change at a rate between quarterly and annually. The Telco sales organisation is likely to change at a rate between monthly for small changes and annually for large changes. Currently available in the Data Warehouse Yes Limitations of current availability Description of Known Data Quality Problems Data Retention Requirements This information would be required indefinitely. Data Refresh Requirements It is important that this information stays as up to date as possible for those organisations with which Telco carries out transactions. For other organisations, such as prospects, the data refresh requirement is more lenient. Implementation Notes Customers are the holders of (active or deactivated) billing system accounts.© 2006 Data Management & Warehousing Page 10
  11. 11. Sample - Requirements ExamplesPerformance Measures PERFORMANCE MEASUREPerformance Measure Number 1Performance Measure Name Vanilla Rated Call Revenue AmountMeasure Type BasicDefinitionThe Vanilla Rated Call Revenue is the amount of revenue generated by a call, and is attached toa Call Detail Record (CDR) by the first pass of the rating engine.Additional CommentaryAs such, this Vanilla Rated Call Revenue Amount is the basic revenue value attachedto the call record, and includes factors such as the time of day the call was made, theday of the week, the message source code, the charge band and the specific ratinggroup.It excludes any subsequent rating changes that are applied by the billing system, whichturn Vanilla Rated Call Revenue into the Re-Rated Call Revenue.The Vanilla Rated Call Revenue Amount could also loosely be referred to as unbilledusage revenue, and should therefore have a revenue status type of unbilled usagerevenue.Data StewardDimensionality / Ordered By / Described By • Party – Customer Organization • Account • Customer Site (Service Location) • Product / Service • Product / Service Instance (Product / Service + Customer Site) • Message Source Code • Time – charge time (at the individual charge level) and billed time. • Telephone Number and its Geography (where applicable) • Account Address and its Geography • Sales Channel • Market Segment • Campaign • Distance Band • Time Band • Revenue Status Type • Scheme • Volume Band • Duration BandCurrently available in the Data Warehouse YesLimitations of current availabilityFor unbilled usage: Vanilla Rated Call Revenue Amount will be accumulated alongsidethe Call Duration on a daily basis by telephone number per bill cycle, and will be zeroedat the start of each bill production run for that telephone number. A later incrementmay load individual unbilled usage revenue at the CDR level for both Vanilla Rated CallRevenue and Call Duration.© 2006 Data Management & Warehousing Page 11
  12. 12. Sample - Requirements ExamplesFor billed usage: Vanilla Rated Call Revenue Amount will be stored at the individualCDR level alongside the Call Duration and the Re-Rated Call Revenue Amount.Description of Known Data Quality ProblemsData Retention RequirementsIndividual Call Detail Records are required for a rolling three months, which therefore implies thatVanilla Rated Call Revenue Amounts will be available for a rolling three months.Data Refresh RequirementsSee above comments in Limitations in Increment 1.The cumulative unbilled usage (Vanilla Rated Call Revenue Amount and Call Duration)by telephone number by bill cycle will be a daily feed into the system.This should be replaced, in a later increment, by a daily feed of individual unbilledusage CDR records.At the billed usage level, this information should be loaded into the system once per billproduction run. That is, there are currently estimated to be six bill production runs permonth.Implementation Notes© 2006 Data Management & Warehousing Page 12
  13. 13. Sample - Requirements Examples PERFORMANCE MEASUREPerformance Measure Number 2Performance Measure Name Number of ServicesMeasure Type CountDefinitionThe Number of Services is an aggregated performance measure that is a simple countof the number of occurrences of at least one instance of a product/service code at aparticular chosen level of interrogationAdditional CommentaryFor example – we may wish to know the number of different service codes and theirdescriptions by account number and service location, in order to explore service mix.Data StewardDimensionality / Ordered By / Described By • Party – Customer Organization • Account • Customer Site (Service Location) • Product / Service • Product / Service Instance (Product / Service + Customer Site) • Account Address and its Geography • Market Segment • SchemeCurrently available in the Data Warehouse YesLimitations of current availabilityDescription of Known Data Quality ProblemsData Retention RequirementsData Refresh RequirementsImplementation Notes© 2006 Data Management & Warehousing Page 13
  14. 14. Sample - Requirements Examples PERFORMANCE MEASUREPerformance Measure Number 3Performance Measure Name Bill Balance Brought Forward AmountMeasure Type DerivedDefinitionThe Bill Balance Brought Forward Amount is the balance brought forward from theprevious bill cycles billAdditional CommentaryThe Bill Balance Brought Forward Amount should be the same as the previous billcycle’s Bill Balance Carried Forward Amount.The Bill Balance Brought Forward Amount will be sourced directly from the sourcebilling systems.Data StewardDimensionality / Ordered By / Described By • Party – Customer Organization • Account • Account Address and its Geography • Time – billed time • Sales Channel • Market Segment • CampaignCurrently available in the Data Warehouse YesLimitations of current availabilityThe speed of response will depend on the available level of pre-calculated aggregates.This information could be made available from the source systems should the SystemsRoadmap point to this being an area of high priority.Description of Known Data Quality ProblemsData Retention RequirementsData Refresh RequirementsImplementation Notes© 2006 Data Management & Warehousing Page 14
  15. 15. Sample - Requirements ExamplesQuery Requirements Query RequirementQuery Requirement Number 1Query Requirement Name Credit/aged reportDescriptionA report that show the outstanding debt by account and credit groupDefinition of Key TermsCurrently available in data warehouse YESDescription of limitations within current implementationRequested byData OverviewDebts by account and how long that debt has been outstandingPerformance Measures Dimensionality / Ordered By / Described By • credit limit • credit class • current balance • account number • balance 30 days • bill cycle/run • balance 60 days • balance 90 days • balance 120+ daysTechnical AssessmentData Retention RequirementsOther CommentsFrequency WeeklyType Regular © 2006 Data Management & Warehousing Page 15
  16. 16. Sample - Requirements ExamplesInterface Requirements InterfaceInterface Number 1Interface Name Customer Segmentation GroupsTarget System Name CRM SystemOutput Type FileOutput Location /BI/ftp/outgoing/CRMOutput File Name csg.csvOutput File Type CSVOutput Format ASCIIOutput Character Set US-ASCIIOutput Frequency DailyCSV SpecificsField Separator Comma (,)Record Separator Carriage Return – Line FeedQuoting Character Double Quote (“)Escaping Character Double Quote (“)XML SpecificsValidationValidation LocationDescription/Purpose of FileThis file is used to update the CRM system with the current market segment group andscore informationData DefinitionField Name Source Field Name Mandatory?Customer_id Customer.customer_id YesMarket_Segment MarSeg.segment_name YesSegment_Score Custom_MarSeg_History.score Yes Yes / No Yes / No Yes / No Yes / No Yes / No Yes / No Yes / NoCurrently available from the Data Warehouse YesLimitations of current availabilityDescription of Known Data Quality ProblemsImplementation Notes © 2006 Data Management & Warehousing Page 16
  17. 17. Sample - Requirements ExamplesCopyright© 2006 Data Management & Warehousing. All rights reserved. Reproduction not permittedwithout written authorisation. References to other companies and their products usetrademarks owned by the respective companies and are for reference purposes only. © 2006 Data Management & Warehousing Page 17

×