Things to Consider Existing Meta Data Repository Do we already have a meta data repository? Do we have to expand it? Do we have to add more meta data components ? Or expand the functionality? Who is keeping the meta data repository up-to-date? Who is using it? How are they using it? What parts of the meta data repository are they using? Do they like it? Are there any complaints? If we do not have a meta data repository, how are we coping without one? Why do we not have one? Lack of budget? Lack of resources? Lack of understanding? Meta Data Repository Products Are there meta data repository products that will satisfy our meta data requirements? Or do we have to build a meta data repository from scratch? How many of our meta data requirements cannot be satisfied by the meta data repository products on the market? How important are those meta data requirements? Can the meta data repository products be enhanced to meet those specific meta data requirements? Which meta data repository products have import and export capabilities? Interfaces How will we automate the interfaces from the meta data repository to other tools that have their own meta data dictionaries, for example, computer-aided software engineering (CASE), extract/transform/load (ETL), and online analytical processing (OLAP) tools? Will we have to buy additional middleware? Do the other tools from which we have to extract meta data have import and export capabilities? Are those tools XML-enabled? How will we deliver the meta data to the business people? Through reports ? Through a help function? Through a Web interface? Will it be hard for the business people to learn how to use the meta data repository interfaces? What training do we have to develop? Staffing Will we need more staff to install, enhance, and maintain a licensed meta data repository product? Will we need more staff to design, build, and maintain our own custom-built meta data repository? |