Information Architecture Sample Clauses

Information Architecture describes the structure of an organization's logical and physical data assets and data management resources. (TOGAF 9.1)
Information Architecture. The pages of the website are structured in four parts: 1. Header: it hosts the main menu bar containing the menu buttons. The menu buttons that are content-related are located on the left part of the menu bar, the “contact” button is located on the right side of the bar. The header remains the same throughout the website.
Information Architecture. When studying information architecture (IA) models, there was no clear choice. A company, Compact, explained that “the choice of the best data management model is dependent on multiple influencing factors: data dimension, the level of automation and available expertise.” In choosing a model, we identified the data dimensions that need to be maintained. We thought about which level of automation was required and for what processes. Lastly, we considered what level of expertise existed within the business related to data management and if they could maintain the quality of data at a decentral level.
Information Architecture. In order to support the five mentioned objectives, the information architecture is developed alongside these elements, which shall be accessible directly from the homepage. In addition, core information about the background of the Community Building Platform is provided on the project home page. Therefore, the following information architecture will be utilized for the website: About Us + Contact Catalogue + Repository News & Events MCS Projects Innovation Roadmap Home The areas that provide interactive services are highlighted in the above services. This is in line with the content strategy described above (chapter 3.2). For each of these areas, a further information architecture has been conceived. They are explained in the coming sub-chapters.
Information Architecture. The competitive benchmarking activity will determine what is desirable in a CNM offering. The information architecture activity will determine what is possible. Genuity's CNM offering for private line and ATM services will make information that is stored in GNI's OSS's available to customers via a web interface. For all of this information to be published, we need to know - Which OSS manages the information to be published? - What support does the OSS have for partitioning information by customer and circuit, and limiting access to information by customer? - What is the Web interface to the OSS? There are a number of Genuity initiatives that deal with the information and OSS's that will be involved with the CNM offering, including: - CIA/Data Mart/Data Warehouse/EAI projects - the Web-based interface to TBS PSR project - the BS OE/Sales Bundling of Services projects - the CSO infrastructure enhancements project We will examine the OSS's that store the information to be published, as well as related systems and initiatives, to design an overall information architecture for the CNM offering. This includes the overall flow of information from OSS's to customers via the CNM web site how the facilities of each OSS are used to partition information by customer how the web interfaces of the OSS's are used, and what new web interfaces are needed to integrate the information.