|Stable release||3.4 / October 2014|
|Operating system||platform independent|
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.
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.
- Interfaces define the dependencies of information systems, whereby mostly the information flow is modeled.
- 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 timeframe, 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 modeled. 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 Excel or the XMI export function of iteraplan data can be processed to further programs and be edited there.
In addition to the free community edition, there is also a paid enterprise edition available with several additional features.
- While the community edition only supports HSQLDB databases, the enterprise edition can also be run with MySQL or Oracle databases.
- The use of different users, roles and permissions is possible in the enterprise edition.
- The enterprise edition can be integrated with an existing LDAP-Server.
- Over an data import interface initial gathering of existing data is facilitated.
- To enable the migration to a new iteraplan release, migration scripts for the enterprise edition are available. With their help, existing data will easily be migrated into the new version.
- The enterprise edition is available in combination with maintenance, support and introduction support through iteratec.
The first version of the tool was developed in 2004 and used with customers of iteratec GmbH. The versions 1.0 up to 1.8 (mid of 2007) were only available as closed source.
At the beginning of 2008 iteraplan (now version 2.0) became the first open source EAM tool by providing a completely revised source code on SourceForge. It was released under the open source licence AGPL. Since then, iteraplan has received increasing attention, e.g. from companies like HUK-COBURG, Otto, VKB-Bank but also public authorities like Hamburg Port Authority.
In May 2008 the version 2.1 with fixed bugs and numerous new functions was released. In February 2009 the version 2.2 including many Refactorings was published. In May 2009 version 2.3 added plenty of comfort functions.
The next major update to version 3.0 in April 2012 introduced a clearer user interface based on Twitter Bootstrap. Moreover the responsive web design enabled usage of iteraplan on smartphones and tablets. The version 3.1 (July 2013) brought new functionality for life cycle management and roadmap planning as well as usability improvements. The version 3.2 from October 2013 introduces a REST-Interface and improves the dashboard functionality and the visualizations. Version 3.3 was developed with a focus on integration and ease of use. In the current version 3.4, the integration and especially the import and export has been improved and accelerated. From version 3.4 on the iteraplan source code is no longer available under AGPL-license.
For the next years updates are scheduled for April and October. The company iteratec employs all active developers of this project and offers consulting, training and support, among other things.
|CPU||1 GHz Dual Core||more is better|
|RAM||2 GB (with large models: more needed)||4 GB and more|
|HDD (excluding DB and OS)||250 MB||1 GB of free space|
|Operating System||any OS supported by Java 6 or 7 (32 Bit or 64 Bit) especially Windows, Linux and MacOS X
Note: Windows 8 is currently not supported
|Windows 7, Server 2003/2008/2012 or newer
Linux (Suse's SLES, Red Hat's RHEL)
|Runtime Environment||Java SE Runtime Environment 6 Update 26 or 7 Update 25 by Oracle/SUN
Note: Java 8 is currently not supported
|latest Update of Java SE 7 or 6 by Oracle/SUN (http://www.java.com)|
|Application Server||Apache Tomcat 6.0.35 or 7.0.37||latest Apache Tomcat 7.0.x or 6.0.x|
|Database System||MySQL 5.x, Oracle 10/11/12 or MS SQL Server 2012
(latter with additional contract package)
|Database Storage||10 MB (with large models: more needed)||100-200 MB|
|Browser||standard web browser||latest Mozilla Firefox
Microsoft Internet Explorer 9 or 10
- Inge Hanschke: Strategisches Management der IT Landschaft. Ein praktischer Leitfaden für das Enterprise Architecture Management, Hanser Fachbuch, München 2013, ISBN 978-3-446-43509-4
- Inge Hanschke: Strategic IT Management: A Toolkit for Enterprise Architecture Management, Springer, München 2010, ISBN 3-642-05033-6
iteraplan in the press
- Forrester Research: Are Open Source And Low-Priced Solutions Available For Tooling EA?
- The Gartner Enterprise Architecture Summit 2010 – English
- The Gartner Enterprise Architecture Summit 2010 – German