Information Technology

Applications

Sumeet Sharma
Assistant Professor
Indian Institute of Management Raipur
 I am Sumeet Sharma….
Assistant Professor,
IIM Rohtak

B.Tech Software Developer

PhD Assistant Professor,
Computer Sciene & Engg Dassault Systems,
Information Systems Bennett University,
NIT Raipur Pune
IIM Raipur Greater Noida

2009- 201 2014- 201 201 2023- 2024-

2013 2017 2024 2025 Now
3 7 8

Senior Associate, 2, of Stats & Info Mgmt, Product Manager

Software Developer –Dept
Genpact India, Teradata India, Jarvis Consulting
Reserve Bank of India (RBI),
Gurugram Hyderabad New Delhi
Mumbai
2
Agenda
• Course Outline

• Why IT Applications in business?

• Module: ERP and CRM Systems (Enterprise Systems)

3
Modules
• Module I: Artificial Intelligence

• Module II: ERP & CRM Systems

• Module III: Cloud Computing

• Module IV: Blockchain and Decentralization Technologies

4
Why IT Applications in business?
• In today’s digital economy, IT drives efficiency, decision-making, and
competitiveness.
• For business school students, understanding the role of IT in
business is crucial for future leadership and management roles.

• Key Benefits
• Enhancing Operational Efficiency
• Data-Driven Decision Making
• Improving Communication & Collaboration
• Enhancing Customer Experience
• Enabling E-commerce & Digital Transformation
• Cost Reduction & Process Optimization
• Ensuring Security & Compliance
• Gaining Competitive Advantage
5
 Module
ERP and CRM Systems

6
Content
• System Development Life Cycle (SDLC)

• Types of SDLC

• Customer Relationship Management

• Supply Chain Management

• Enterprise Resource Planning

• Decision Support Systems

7
System Development Life Cycle(SDLC)
• Reasons for systems failure:
• Missed deadline
• Users’ needs were not met
• Poor customer experience
• Lack of support from top management
• Poor financial management
• Poor planning of system development

8
System Development Life Cycle(SDLC)
• SDLC is a framework that describe various stages involved
in the development of an Information Systems or
projects.
• The SDLC consists of the 5 key phases:
1. Planning
2. Requirement Gathering & Analysis
3. Design
4. Implementation
5. Maintenance
• Types of SDLC
• Waterfall
• Agile
• SOA
9
System Development Life Cycle(SDLC)
• Pre-requisite to SDLC

Problem Identification or Objective

• Why is the information system being developed?
• Who are the system’s current and future users?
• Is the system new, or is it an upgrade or extension?
• Which functional areas (departments) will be using the
system?

10
 SDLC: Overview of phases

Image Source:
Hossein Bidgoli
MIS, 11th Edition 11
SDLC: Phase 1- Planning
• System designer must define the problem statement or
challenges faced by organization
• Identification of the problem
• Problems can be internal or external
• Internal problem
• Management voicing concern about the organization’s lack of
competitive edge in the marketplace
• External problem
• Supplier noting inefficiency in the inventory control procedure

12
SDLC: Phase 1- Planning
• After identifying the problem, assess the current and
future need of the organization:
• Examine the organization’s goal
• Which factors are critical for the success of the proposed
systems
• Establishing evaluation criteria to measure system
performance

13
SDLC: Phase 1- Planning
• Ensure the comprehension of 4 Ws:
• Why – Why is the information system being developed?
• Who – Who is going to use the system? Is it going to be used by
one decision makers or group of decision makers? For example,
will the marketing dept be using the system? Will the
manufacturing dept be using the same system?
• When – When will the system be operational? In what stage
system will be used?
• What – What kind of capabilities will the system provide? How
these capabilities will be used?

14
SDLC: Phase 1- Planning (Use case)
• An organization, namely, ABC Furniture is planning for an
IS to solve the problem of inaccurate inventory
forecast.
• 4 Ws:
• Why – Why is the information system being developed?
• Who – Who is going to use the system? Is it going to be used by
one decision makers or group of decision makers? For example,
will the marketing dept be using the system? Will the
manufacturing dept be using the same system?
• When – When will the system be operational? In what stage
system will be used?
• What – What kind of capabilities will the system provide? How
these capabilities will be used?
15
SDLC: Phase 1- Planning (Use case)
• Why – Why is the information system being developed?
• To track inventory
• Generate a more accurate forecast of product demand
• Track wood requirement
• High availability of products
• Improve ABC’s reputation

16
SDLC: Phase 1- Planning (Use case)
• Who – Who is going to use the system? Is it going to be
used by one decision makers or group of decision makers?
For example, will the marketing dept be using the system?
Will the manufacturing dept be using the same system?
• Procurement team – places new orders
• Manufacturing team – tracking inventory & managing demand
• Sales personnel – receive order from distributors/retailers

17
SDLC: Phase 1- Planning (Use case)
• When – When will the system be operational? In what
stage system will be used?
• Set a timeline to operationalize IS
• For example: festival seasons, govt regulations, gain competitive edge
• Plan must include
• Procurement time
• Manufacturing time
• Shipping time

18
SDLC: Phase 1- Planning (Use case)
• What – What kind of capabilities will the system provide?
How these capabilities will be used?
• On the inbound side
• Track pending and received deliveries, and quantity of raw materials
• Status of placed orders
• Raw material levels from all suppliers
• Operations side
• Inventory level for all products
• Work-in-progress at each stages of manufacturing
• Quality of intermediate and finished goods
• Stats on rejected/accepted goods (efficiency)
• Outbound side
• Delivery status of finished goods
• Order history for distributors
19
SDLC: Phase 1- Planning
• Formation of the task force
• Representatives like IT experts, business analysts, top-
management team
• Collect feedback (generally for system upgradation) from users
• Two types of users:
• Internal - Employees
• External - customers, suppliers, contractors, vendors
• Task force explains the detailed functionality, and systems
specifications
• Task force ensures that collected requirements are not very
limited and focused on a specific functional aspect

20
 SDLC: Overview of phases

Image Source:
Hossein Bidgoli
MIS, 11th Edition 21
SDLC: Phase 2- Requirement Gathering & Analysis

• In this phase, analyst understand the requirements for the system,

analyzes these requirements to determine the main problem with
the current system, and seek alternative ways to resolve it.
• Gathering requirements:
• What users do?
• How they do it?
• What users expect from the system?
• Where data comes from?
• How data should be presented?
• What tools are needed to examine data for the decision that user make?

• Define the project scope

• Including what a system should have and what should not
• Prepare a document called as “system specifications”
22
SDLC: Phase 2- Requirement Gathering & Analysis

• Tools to analysis and design:

Modelling Tool Process Analysis & Purpose
Design
Data Flow Process analysis & Breaks complex process into simpler and
Diagram (DFD) design manageable process; also helps define
the system’s scope
Flowchart Process analysis Logical steps in a process, does not show data
elements; how a process works
Context diagram Process analysis & Level-wise process
design

23
 Phase 2- Requirement Gathering & Analysis
SDLC:

Use Case – Data Flow Diagram ABC Furniture

Distributor
Invoice & PO Invoice &
Raw material Shipment Details Shipment Raw material
Purchase orders
suppliers Distributor suppliers
Supplier Order
Raw Paymen
Payment
Material t
Purchase Approved Approva Payments
orders Invento Amount l
ry Manage For PO Manage
Levels Create Purchase
inbound Order outbound
Finished
order order
Raw Material Raw Material
goods
Shipment Shipment inventory
Quantities Invoice levels
Distributor
Inventory Details Order Details

Inventory data Inventory Shipment

Update Manage Notificati
on
Distributor order
Inventory inventory
Details Order
Quantities
Inventory Levels
Market Demand
Manufacturing Marketing
Inventory Demand Data
24
 Phase 2- Requirement Gathering & Analysis
SDLC:

Use Case – Data Flow Diagram ABC Furniture

Distributor
Invoice & PO Invoice &
Raw material Shipment Details Shipment Raw material
Purchase orders
suppliers Distributor suppliers
Supplier Order
Raw Paymen
Payment
Material t
Purchase Approved Approva Payments
orders Invento Amount l
ry Manage For PO Manage
Levels Create Purchase
inbound Order outbound
Finished
order order
Raw Material Raw Material
goods
Shipment Shipment inventory
Quantities Invoice levels
Distributor
Inventory Details Order Details

Inventory data Inventory Shipment

Update Manage Notificati
on
Distributor order
Inventory inventory
Details Order
Quantities
Inventory Levels
Market Demand
Manufacturing Marketing
Inventory Demand Data
25
SDLC: Phase 3 - Designing
• Select the realistic and highest payoff solution for the
organization
• Details of the proposed solutions

• Output – Exact specifications for implementing the

system, including files and database, networking
components, documentation (manual), processes,
and system specifications (hardware & software).

• Output – Developing prototype

26
SDLC: Phase 3 - Designing
• Prototype
• A small version of actual system that allow users to asses the
potential challenges and limitations.
• Proof-of-concept (PoC) prototype
• If a system appears to be technically unfeasible, a prototype
exhibit how the particular task can be accomplished.
• Selling prototype
• A prototype used to sell a proposed system to users or
management by showing some of its features

27
SDLC: Phase 3 - Designing
• Advantage of Prototype
• Feasibility of proposed solutions
• Early detection of system’s limitations
• Reduce costs
• Easy to modify prototype & complete system
• Improve communication with decision-making team

• Disadvantage of Prototype
• Require more support and assistance from top-management team
• May be misleading, if prototype is not reflecting the actual system

28
SDLC: Phase 4 - Implementation
• Procurement and installation of the system in the
organization
• Task includes:
• Acquiring new equipment
• Hiring new employees
• Training employees
• Coding
• Testing
• Designing security measures & safeguards
• Creating a disaster recovery plan

• Pilot project -> Actual implementation

29
SDLC: Phase 5 - Maintenance
• The information system is operating, enhancements, and
modification to the system have been developed and
tested
• Hardware & software components have been added or
replaced
• Collect performance data, and evaluating KPIs
• Creating support team

30
Feasibility
• To measure how beneficial or practical an IS will be to an
organization

• Feasibility study has 5 major dimensions:

• Economic
• Technical
• Operational
• Scheduling
• Legal

31
Economic Feasibility
Assessment of costs and benefits of a system
• Costs:
• Hardware & software
• Software lease or licenses
• Maintenance cost
• Personnel cost – Salaries of IT resource person
• Training cost
• Opportunity costs
• Measure what you would miss by not having a system or
feature.
• For example, if your competitor has a website and you don’t, what is
the cost of not having a website, event if you do not need one? What
market share are you likely to lose if you do not have a website?
32
Economic Feasibility
Benefits:
• Tangible benefits
• Quantified in terms of monthly/annual savings
• Intangible benefits
• Difficult to quantify in monetary value
• Example:
• Improved morale of employees
• Customer satisfaction
• Flexibility in operations

• Calculate cost-effectiveness
• For example: ROI, Break-even point
33
Technical Feasibility
• Assessment of technology that will be used in the system
• For example:
• For ABC, does full-featured autonomous delivery truck feasible?
• Lack of readiness
• Organization lacking the expertise, time, or personnel to
implement a new system
• Solutions?
• Employee training
• Hiring experts
• Collaboration with other companies

34
Operational Feasibility
• Assessment of how well the proposed solution will work in
the organization, and how internal and external customers
will react to it.

• In other words, whether the information system is

worth implementing or not?

35
Operational Feasibility
• Should address the following questions:
• Is system doing what it is suppose to do?
• For example: for ABC, will system reduce orders for raw material by
tracking inventory?
• Will the system be used?
• Will there be resistance from users?
• Will system positively affects the users (internal & external)?

36
Scheduling Feasibility
• Assessing whether the new system can be completed on
time.
• Setting milestones for the project or system deliverables
• Access the impact of missing deadlines:
• Business revenue
• Losing customer

37
Legal Feasibility
• Assessment of legal issues
• Addresses questions such as the following:
• Will the system create any legal issues in the country (where it
will be used)?
• Are there any political repercussion of using the system?
• Is there any conflict between proposed system and legal
requirement?
• For example: does system take care of privacy?

38
 SDLC: Overview of phases

Image Source:
Hossein Bidgoli
MIS, 11th Edition 39
Type of SDLC
• Waterfall model
• Agile Methodology
• Low-Code or No-code development
• Service-Oriented Architecture (optional)
• Rapid Action Development (optional)

40
Waterfall model

41
Agile Methodology

42
Low-code or No-Code Development

43