Faculty Enablement Program- Day1

Education & Research

2011 Infosys Ltd. This document contains valuable confidential and proprietary information of Infosys. Such confidential and proprietary information includes, amongst others, proprietary intellectual property which can be legally protected and
commercialized. Such information is furnished herein for training purposes only. Except with the express prior written permission of Infosys, this document and the information contained herein may not be published, disclosed, or used for any
other purpose.

What is an Enterprise Application

The enterprise applications are the software applications that are the DNA of
organizations and imbibe the business functionalities of the enterprises to
catalyze their growth.

The enterprise applications typically imbibes complex business logic, expected to

be high on performance, fortified from vulnerabilities and attack vectors, expected
to handle large volumes of data and concurrent users and is scalable on need
basis, easily maintainable and extendable, and is able to orchestrate with the
overall enterprise application landscape of the organization.

Enterprise applications not only enhance the efficiency and productivity of the
organization but also help in ensuring business continuity.

Categorization of Enterprise Applications

Visibility to end user

Industry domain specific application

Type of processing supported

Custom built or readymade application

Categorization of Enterprise
Applications(Contd.)

Visibility to end user:

Customers facing enterprise applications or front-end systems of an organization are
referred to as Upstream enterprise applications. For example, an order capture
application which captures online orders of customers is an upstream enterprise
application.

The back-end enterprise applications which work behind the scenes in an organization
to fulfill the customers or end users needs are called Downstream enterprise
applications. For example, an order provisioning application can be considered as a
downstream application as it helps in fulfilling and provisioning the online orders
captured through the order capture upstream enterprise application.

There is a third category of applications in an organization, which fulfills the general
organizational needs, and can be referred to as Business Enabler enterprise
applications e.g. payroll and human resource management applications.

Categorization of Enterprise
Applications(Contd.)

A typical enterprise application landscape (partial) in Financial domain

5

Challenges in Building Enterprise

Applications
With changing market dynamics, customer needs and
technology, Enterprise applications face many challenges to
stand out from the crowd. Below are the key challenges:

Business Process Automation :

Data Harmonization

Application Integration

Application Security

Transaction Management

Quality of Service (QoS)

Rich User Experience

Internationalization

Technology Selection
6

Software Engineering methodologies

Iterative methodologies

IBM RUP: RUP has assembled the iterations in four phases: inception,
elaboration, construction and transition.

Agile software development: an extension to the iterative approach to build

applications in a nimble fashion with a light weight process.

Waterfall methodology

Traditional approach of software development that typically comprises of a

sequence of phases requirements, analysis, design, build and testing
wherein each phase output acts as input to the next phase.

Life Cycle of Building an Enterprise

Application
Development of an enterprise application follows a life
cycle with the following stages:

Incepting

Typically starts as a result of enterprise analysis and business modeling

activities.

Requirements engineering is the key activity.

Concludes with casting the plan and project estimation.

Architecting and Designing

Takes key inputs from the enterprise architecture initiatives of an organization.

Life Cycle of Building an Enterprise

Application (contd)
Application architecture and software designing are the key
activities.

Constructing

starts with building the application framework components;

followed by construction of application components;

Unit testing and code review and analysis are also carried out

Concludes with component integration

Testing

includes integration testing, system testing and user acceptance testing

Rolling out

successful user acceptance test leads to application rollout.

Building enterprise applications

10

Skill requirements to Build an Enterprise

Application
Following are the key skill sets required to develop an
enterprise application:

Knowledge of organizational dynamics: understand the organizational business

and business needs of end users.

Domain knowledge: comes handy especially during inception, architecting and

design and testing phase of applications.

Business analysis skills: conglomeration of domain knowledge, technical

knowledge, use of business analysis related tools and practice of soft skills.

11

Skill requirements to raise an Enterprise

Application (contd)

Program management skills: includes planning, estimation, budgeting, talent

management, change management, positive communication and many more

Architecting and designing skills: includes the knowledge of architecture views

and view points, architectural patterns, design patterns, design paradigms like
object orientation, aspect orientation and service orientation, usage of design tools,
architectural and design best practices, technical frameworks, knowledge of
modeling languages like Unified Modeling Language, etc.

12

Skill requirements to raise an Enterprise

Application (contd)

Programming skills: includes knowledge of a programming language ,knowledge of

the underlying platform, knowledge of an Integrated Development Environment (IDE)
tool, programming best practices, code review skills, knowledge of unit testing tools,
configuration management and build tools, static code analysis tools and dynamic code
analysis tools etc.

Testing skills: includes skills for performing integration testing, performance testing,
load testing, stress testing, application security testing, interface testing and user
acceptance testing.

Knowledge of tools

13

Ingredients of Enterprise Application

14

Measuring the success of Enterprise

Applications

Once we are done with raising an enterprise application , we need to measure its
success based on different parameters.

Measuring the business process automation gain and the gain in terms of the ease
with which end user can carry out the same process.

Quality of application in terms of non functional requirements.

Time to production - faster the time to market , better for the organization

Adherence to budget and timeliness.

Cost effectiveness of application.

Productivity of development teams

15

Introduction to Loan Order

Management(LOMS) case study

EM Bank (Easy Money Bank) is a leading global bank headquartered in Europe with
presence in more than 50 countries across continents. EM Bank offers services in core
banking, investment banking, mortgage, foreign exchange and wealth management.

The core banking segment of EM Bank has been offering loans to its retail customers
through its branches, since 1970. In order to keep up with the competition and current
business trends, the bank management decided to expand the loan offerings to a wider
customer base using multiple channels to reach the prospective and existing
customers.

16

LOMS (Contd.)

17

LOMS(Contd.)

18

Documenting the TO-BE process

Documenting the
TO-BE process

19

Enterprise analysis

Business continuity and sustained growth are of paramount

importance to any enterprise.

Enterprise Analysis deals with questions such as

Why a given system is needed?

Why a given system needs change?

Why it is important to invest at this time?

20

The Enterprise Triangle and Business

Patterns

If we look at an enterprise from 10000 feet, it is

Business

represented by co-existence and interaction of Users,

Business applications and Data.
In any enterprise end users uses business
applications to access the data. These 3 constituents
of an enterprise interact differently in different business
scenarios.
These business scenarios can be categorized in
commonly occurring patterns, called as business
patterns.

21

Enterprise

User

Data

Types of business patterns

1/2

Self Service:
The business pattern where users directly interact with the business using the applications over internet or
intranet. For example a customer using an online ordering system, a typical web site, to order a product or
services and tracking it until its delivery.

Information Aggregation:
The business pattern where users can fetch useful information from applications consisting of large volume of
data, text and images. For example, business intelligence applications, web crawlers and knowledge
management applications are representative applications of information aggregation business pattern.

Collaboration:
The business pattern where applications support collaborative work between users via internet or intranet.
Email, chat, e-community are some of the representative applications of collaboration business pattern.

Extended Enterprise:
The business pattern where two or more enterprises business processes get connected via applications to
fetch mutual business benefits is called as an extended enterprise business pattern. For example, the suppliers
and partners business processes and in turn their enterprise applications get linked with the primary enterprise
applications for mutual benefit and transparency. Supply chain management and Electronic Data Interchange
(EDI) are a few representative applications of extended enterprise business pattern

22

The Enterprise constituents and Business

Patterns
Business Patterns

Enterprise
Constituents

Representative Apps

Self Service

User to Business

Web applications

Information
Aggregation

User to Data

Business Intelligence,
Knowledge Management,
Web Crawlers

Collaboration

User to User

Email, Chat, eCommunity

Extended Enterprise

Business to Business

EDI, supply chain

management

23

Activities-Enterprise analysis

As part of Enterprise Analysis, a business analyst performs the following activities:

Identifies the business opportunities and business changes

Identifies stakeholders across business units

Collects and prioritizes the business requirements

Defines the business roadmap with scope and exclusions

Determines the high level investment needed for the enterprise

Conducts feasibility study for any changes proposed

Conducts risk analysis and competitive analysis

Decides on Build-or-Buy strategy

Creates Return on Investment business cases with proper justifications

Gets the necessary approvals from the sponsors
24

Thank You