The following are many applications: • A composite SOA application composed of a set of reusable services and a user interface that leverages those services.
There are at least two applications here (the user interface and one or more service components).
Each service is not counted as an application. • A legacy client-server app that writes to a database to store data and an Excel spreadsheet that uses macros to read data from the database to present a report.
There are TWO apps in this example.
The database clearly belongs to the legacy app because it was developed with it, delivered with it, and is tightly coupled to it.
This is true even if the legacy system uses the same stored procedures as the Excel spreadsheet. References  HBR Prod. #: 74104-PDF-ENG  “The State Of Global Enterprise IT Budgets: 2009 To 2010”, Forrester Research, (http:/ / www.forrester.com/ rb/ Research/ state_of_global_enterprise_it_budgets_2009/ q/ id/ 53332/ t/ 2)  Definition of an Application, Inside Architecture Blog (http:/ / blogs.
Msdn.com/ nickmalik/ archive/ 2006/ 08/ 11/ third-attempt-definition-of-an-application-in-a-soa-environment.
Aspx), Nick Malik Application Services Library 27 Application Services Library ASL is a methodology used in the IT industry.
The Application Services Library (ASL) is a public domain standard, which describes a standard for processes within Application Management (the discipline of producing and maintaining information systems and applications).
The term “library” is used because the ASL standard is based on the descriptions of best practices from the industry.
This standard was developed in the late nineties in the Netherlands, originally as the proprietary R2C model, which evolved into ASL in 2000.
In 2001 it was donated by the IT Service Provider PinkRoccade to the ASL Foundation, now the ASL BiSL Foundation.
ASL is closely related to ITIL, BiSL and CMM.
It is described in several books and articles (most of them only available in Dutch), as well as on the official website of the ASL BiSL Foundation.
The standard was developed because of the inability to structure the way of working within the Application Management departments by only using the ITIL framework, an older library embraced by the IT infrastructure departments for structuring their way of working.
At the time of development, ITIL was very useful for infrastructure management but lacked specific guidance for application design, development, maintenance and support.
Newer ITIL versions, particularly V3, have increasingly addressed the Application Development and Application Management domains.
A reference to a white paper comparing ITIL V3 and ASL is included.
ASL was defined in order to fill this gap for Application Management.
A similar development has led to the definition of the BiSL-standard for Information Management / Functional Management. Purpose The ASL is intended to support Application Management by providing tools.
Two main categories of aids are defined: • Descriptions of the processes for Application Management.
Plus the use of best-practises • Standard terminology, avoiding the pitfall of talking about different topics while using the same words.
The goal of ASL is to assist in the professionalisation of Application Management. Structure of ASL Application Services Library 28 ASL contains six clusters of processes, three on the operational level, one on the tactical level and two on the strategic level. Operational level Service organisation There are five processes within the cluster Service Organisation.
The processes in the Service Organisation cluster support the daily use of the information systems.
The processes in this cluster are: • • • • • incident management continuity management capacity management availability management configuration management
Read more about ITIL Versions : Newer ITIL versions particularly V3 have increasingly addressed the Application….: