chapter 2 of BPM... "Evolution of enterprise systems architecture"

1. 2/14/2013
Business Process Methodology
Chapter 2
Evolution of Enterprise Systems
Software Architecture
Architectures “A structure that organizes the software
elements and the resources of a software
system. “
• Software elements and resources are
Prepared by:
Rao Majid Shamshad represented by subsystems.
University of Education, Lahore • In a given software architecture, these
email: majidrao111@gmail.com
http://www.bpm-ue.blogspot.com subsystems have specific responsibilities and
relationships to other subsystems.
2.1 Traditional Application 2.2 Enterprise Applications and their
Development Integration
• In the early stages of enterprise computing,
mainframe solutions were developed that hosted
monolithic applications, typically developed in
assembler programming language.
• These monolithic applications managed all tasks
with a single huge program, including the textual
user interface, the application logic, and the data.
• Data was mostly stored in files, and the applications
accessed data files through the operating system.
1

2. 2/14/2013
1980’s………. 1980’s…………………. continued
• With the advent of database systems, an internal • More application systems were developed.
structuring of the system was achieved: data was • One software system for human resources
managed by a database management system. management, one for purchase order
• However, the application code and the user management and one for production planning.
interface code were not separated from each • One logical data object, such as a customer
other. address, was stored in different data stores
• The user interface provides the desired managed by different application systems.
functionality through textual, forms-based
interfaces.
2.2.1 Enterprise Resource Planning
Systems
• Provide an integrated database that spans large
parts of an organization.
• An ERP system stores its data in one centralized
database
2

3. 2/14/2013
Year 2000 and later………..
• The demand for additional functionality arose,
and new types of software systems entered the
market.
• Examples of ERPS
▫ supply chain management systems, or SCM
systems,
▫ customer relationship management systems, or
CRM systems.
2.2.2 Enterprise Application
Siloed Applications
“meaning that data is stored redundantly Integration
in different systems” 1. Point-to-Point Integration
3

4. 2/14/2013
2. Hub-and-Spoke Integration 2.4 Workflow Management
“Workflow is the automation of a business
process, in whole or in part, during which
documents, information, or tasks are passed
from one participant to another for action,
according to a set of procedural rules.”
Workflow Management System Single-application workflow v/s
“A workflow management system is a software
multiple-application workflows
system that defines, creates, and manages the
execution of workflows through the use of “A single-application workflow consists of
software, running on one or more workflow activities and their causal and temporal
engines, which is able to interpret the process ordering that are realized by one common
definition, interact with workflow participants, application system. Multiple-application
and, where required, invoke the use of IT tools workflows contain activities that are realized
and applications.” by multiple application systems, providing an
integration of these systems.”
4

5. 2/14/2013
System Workflows Human Interaction Workflows
A system workflow consists of activities that are implemented Workflows in which humans are actively involved and interact with
by software systems without any user involvement information systems are called human interaction workflows.
Challenges for Workflow Management
• Lack of Adequate Support for Knowledge
Workers
▫ Users acceptance issues
• Technical Integration Challenges
• Process Support Without Workflow Systems
5