|
iteraplan is a simple effective tool to manage Enterprise architecture with focus on the IT landscape. The aim of iteraplan is to quickly introduce EAM into an organisation, enable tool support for managing the enterprise architecture and facilitate collaboration between different EA relevant stakeholders, such as enterprise architects, project managers, IT staff. == Features == With iteraplan different fields of enterprise architecture can be analysed. The focus not only lies on IT relevant parts, but the whole company is considered, like business architecture, information system architecture and technical architecture. The best practice meta-model is structured as follows. * Business domains are structural elements that serve to group associated elements in the business landscape. * Business processes are sequences of logically connected activities or sub-processes that contribute in some way to the enterprise‘s value added. Each process has a defined start and end, is expressed in terms of performing some action for customers. * Business function is a distinct, cohesive set of business functionality such as “customer relationship management”. The enterprise’s capabilities are expressed in terms of the business functions it carries out. * A product is the outcome or deliverable of an enterprise’s service process. Products can be either material (e.g. goods such as cars or computers) or immaterial (services). * Business units are logical or structural units of the enterprise, such as departments, sites and plants, also logical user groups such as field sales team or internal administration. * A Business object represents a real-world entity – abstract or concrete – which encapsulates some part of the business activity of an enterprise (customers, for example, products or orders). Business objects can be associated with one another by relationships and are used by business processes. * An information system domain combines information systems based on one or more criteria. It is used to categorize information systems based on the application landscape or on the responsibility. * An information system is software or a software package, which supports business functions. * Using IT-Services you can model you IT-services catalogue. * Interfaces define the dependencies of information systems, whereby mostly the information flow is modelled. * Architecture domains are structures of the blueprint, the standardization catalogue of technical components. *A Technical Component provides information on technical implementations or interfaces. Technical components are standardized by technical standardization processes. The result is a catalogue (named technical blueprint) of standardised technical building blocks. As well as the standardised components, it might be necessary in documenting the as-is landscape to include non-standardised technical components as well. * Infrastructure Elements are infrastructure units such as hardware or networks on which applications run (e.g. client, server, database). * A project is essentially a one-off activity overall, e.g. in terms of objectives, restricted time frame, funding, personnel and other parameters, and is clear demarcation from other projects. In addition it will also have a separate organisation. After capturing the as-is state of the architecture, the desired to-be situation can be modelled. It is possible to develop different (e.g. sequential) to-be states. Furthermore, different graphical reports can be derived from iteraplan. For example a portfolio- or information flow diagram, allocation tables or lists. All graphical reports can be configured to your needs and saved. With the Excel or XMI import & export function data can be processed by other programs. A REST interface is available as well. 抄文引用元・出典: フリー百科事典『 ウィキペディア（Wikipedia）』 ■ウィキペディアで「iteraplan」の詳細全文を読む スポンサード リンク
|