Development plan (information technology)

from Wikipedia, the free encyclopedia

Similar to the development plan for urban development documents the current land use and determines the future land use, are in an IT development plan current and future be employed IT infrastructure and application software of a company to support its business processes documented and defined (see.) .

Overview

A development plan is a central guideline for the people and organizational units involved in the construction and maintenance of the IT architecture . He ensures that the development of the application software and the IT infrastructure is based on the needs of the users and customers of a company. A development plan is an important tool for the management of enterprise architecture (Enterprise Architecture Management).

The basis for an IT development plan is an actual record of the business processes, the business objects, the application landscape and the IT infrastructure of a company and their relationships with one another. Based on the actual development plan, a target development plan is developed taking into account strategic requirements. Measures and projects are derived from the delta between the actual and target development plan, which are necessary to achieve the desired target state.

Once collected, the actual development plan is i. d. Usually kept up to date. The planning horizon for the target development plan extends over approx. 5 years (medium-term planning). The target development plan is revised once or several times a year in a rolling process, so that increasingly more precise statements can be made for the immediately following years.

The measures and projects derived from the development planning, including their dependencies, are brought into a chronological sequence. The resulting roadmap is in turn input for the company's project portfolio management.

Visualization

Schematic development plan (excerpt)

IT development plans to illustrate the corporate architecture represent the entire application software of a company or part of a company in relation to business processes, business objects or organizational units. The classic visualization shows a matrix that assigns all applications to the business processes on the one hand and to the organizational units on the other (see picture) .

To document which business objects are processed by which applications, information flow diagrams are used for visualization.

To visualize the IT infrastructure, it is often visualized which applications use which IT infrastructure.

The graphic representation of the IT development plans is supported by tools for managing the corporate architecture . However, many companies also use conventional graphics tools to draw IT development plans.

See also

literature

  • BITKOM (Ed.) (2011): Enterprise Architecture Management - a new discipline for holistic corporate development. Federal Association for Information Technology, Telecommunications and New Media e. V.
  • Hanschke, Inge (2011): Enterprise Architecture Management - simple and effective. Carl Hanser Verlag , ISBN 978-3-446-42694-8
  • Hanschke, Inge (2013): Strategic Management of the IT Landscape. Carl Hanser Verlag , 3rd edition, ISBN 978-3-446-43509-4
  • Keller, Wolfgang (2012): IT enterprise architecture: From business strategy to optimal IT support. dpunkt.verlag, 2nd edition, ISBN 978-3-898-64768-7

swell

  1. BITKOM (ed.) (2011), p. 22