While collecting some views of Application Architectures, I came across yet another way of defining an application. I liked it, as it aligns with my reasoning that an application is simply the automation of a business function using technology.
An analyst named Tom Richards wrote the following in an Enterprise Application Integration paper:
“A business process is not just a systems topic; it is also a business management
and human performance topic. It is a series of activities,
grouped into three areas, that convert business inputs into outputs:
• Inputs – data, outputs from another linked process, and/or an event
(sometimes referred to as a stimulus) that initiates the process and/
or provides the information needed to perform a task;
• Work – rules and workflow that process the inputs, including skill
sets, knowledge, motivation, feedback, performance standards and
• Outputs – the result of the process, which may include data or a
response or a link to another dependent process.
Automation performs a vital supporting role in assuring the desired outcomes
of these activities. Automating a business process allows the consistent
execution of the process; consistent application of business logic,
policy and rules; and increased, scalable capacity.”