flickssilikon.blogg.se

Uml logicworks
Uml logicworks





uml logicworks

Interestingly, some of these vendors make it easy to let traditional information-worker end users "browse" the repository data others see IT staffers as their ultimate end users. Ted proprietary database applications to store and manage that data. Historically, data-warehousing-tool vendors have crea

uml logicworks

Repository technology makes sense in data warehousing, because you need to store information about a data warehouse's (or OLAP server's) source data and about the extraction, cleansing, and aggregation rules that are associated with building and maintaining it. This has happened largely because of their role in the exploding field of data warehousing and on-line analytical processing (OLAP) applications. It will let itself be interrogated through open, standard, and well-defined interfaces. It will also be largely self-managing and will interoperate with metadata sets coming from different sources and represented using different standards.

uml logicworks

Metadata is extensively used in systems and applications to gain efficiency when accessing, transferring, sharing, or processing large amounts of data.Īn ideal repository will be distributed, open, and extensible. Re tools to help manage computer systems and networks. But the need to share information across enterprises and government entities has led to a variety of domain-specific proposals for metadata repositories, including Federal Geographic Data Committee (FGDC) for geographic information systems, the Warwick Framework and Dublin Core for digital libraries, and industry standards such as Common Data Interchange Format (CDIF), a standard devised by CASE-tool vendors for modeling tools. Some repositories, usually from tool vendors, have been designed to store information related to the software-development process: source code, version history, project management information, and so on. CASE repositories have focused on storing design information, often about database schemata. For example, they have often been associated with CASE and data-modeling tools. That's the vision of the repository, so it shouldn't be surprising that repositories have been called data dictionaries - even encyclopedias - and that their contents are often referred to collectively as metadata, or data about data.ĭata repositories aren't new. Imagine that kind of library for an entire organization's resources. In a sense, a repository's role is similar to that of a library's card catalog - an exhaustive and cross-indexed list of resources.Ĭhances are that most programmers will recognize the notion of a repository as the library or component manager associated with many of today's developer tools. Tabase design information, business rules, and corporate naming standards, for example. System information? In the context of repositories, system information refers to information about an organization's IT assets - everything from C++ header files, component definitions, and COBOL copy books to information about on-line corporate knowledge-base assets. More accurately, they're database applications for system information. Their appeal is simply as an enabling technology, something that's supposed to make programmers' and information technology (IT) enterprise architects's livesĪt their simplest level, repositories are basically databases. We might add that no one wants to pay for them, either. The problem with repositories, notes Michael Barnes, an analyst with the Hurwitz Group consultancy, is that no one wants to deal with them directly. More than databases, repositories should hold the corporate IS jewels. May 1998 / Reseller / The Road to a Universal Repository BYTE Magazine - May 1998 / Reseller / The Road to a Universal Repository The Road to a Universal Repository







Uml logicworks