JAY MARK F.

ARENDAIN, MIS
Subject Instructor
 LEARNING OUTCOMES
At the end of the lesson, the students should be able
to;
1. Discuss the business process concepts;
2. Discuss and explain the planning Business of Information
Systems;
3. Discuss the building processes of BIS;
4. Review and discuss the system development process;
5. Identify the needed tools in the design and building of
information systems.

2
What is a Business Process?
A business process is a set of tasks that together
accomplish a goal or produce something of value for
the benefit of the organization.
❑ Business processes can be supported by manual as well as
automated activities, and by paper-based as well as digital
information.
❑ An information system aims to make business processes
more effective or efficient, and a detailed process analysis is
the starting point to define what the information system is
supposed to do.
3
EXAMPLE: A BUSINESS PROCESS (Manual/Physical)

4
 BUSINESS PROCESS REDESIGN (Electronic/IS)

Business process reengineering - is the act of recreating a core business process with the goal of improving
product output, quality, or reducing costs. Typically, it involves the analysis of business workflows,
finding processes that are sub-par or inefficient, and figuring out ways to get rid of them or change them.
5
Planning a Business Information Systems Project

STEP 1: Identify problems and opportunities

➢ Business information system is the combination of
people and IT elements that supports the operations,
management, and evidence based decision-making.

➢ Think about which problems in your chosen business

process could be solved if you or other workers had
better (more accurate, complete, timely, or relevant)
information.

6
First things first? What to do?
❑ What are important thing to be considered before
designing and building a business information
system?

1. Identify the organizations involved in the business

processes
2. Identify the needs and responsibilities of your chosen
business firm or organization.
3. Identify the processes, inputs and outputs of each process.
4. Identify the procedural steps for implementing the proposed
system.
7
Planning a Business Information Systems Project

➢ Setting and respecting boundaries will be a key

success factor for your project.
You can achieve this by clearly establishing and agreeing on the
scope—that is, defining what is and is not included in your
project—in terms of its functional, programmatic, and
geographic dimensions.

8
Planning a Business Information Systems Project

1. Functional
➢ The functional scope of the system refers to what it does. Will
it support product records, customer’s information, stock
management, and logistics? Advocacy and outreach? Finance
and accounting? Human resource management?

2. Programmatic
➢ The programmatic scope refers to the business related
programs that will be using the system. Is it going to be made
specifically for one program or will it be integrated?

9
Planning a Business Information Systems Project
❑ To answer this question, it is worth thinking about the end users
of the system. Will they end up needing several systems to do
their job? In that case, their development needs should be
coordinated.

3. Geographic
➢ The geographic scope of the system refers to where it will be
used, and by whom. Is it meant for nationwide deployment?
At what levels of the business system? In local area? wide
area? metropolitan area?

10
Planning a Business Information Systems Project

STEP 2: Form Your Team

By taking this step you should be able to answer…

➢ What resources and skills do I need for each of the

three phases (develop, scale, and sustain)?
➢ How can I assess what skills are already available in
the business, other departments, or business
partners?

11
Planning a Business Information Systems Project

STEP 2: Form Your Team

➢ There is more to IT projects than developing software; in fact, an
information system is always a combination of people and
technology. At the start of your project, you should form a
multidisciplinary team that can manage every project function,
not only the development, deployment, and operations
functions, but also the management and governance functions.

12
Planning a Business Information Systems Project

❑ Project Management – is organizing and directing

people to achieve a planned result within budget and on
schedule

➢ The project needs to be planned, managed, monitored, and

evaluated by a project manager and support staff. This
management group should also include administrative
functions such as procurement. Often, more than one project
manager oversees a project.

13
Planning a Business Information Systems Project

❑ Nine (9) Project Management Body of

Knowledge
1. Scope Management
➢ Control functions included in system
➢ Control scope of work done by team

2. Time Management
➢ Build detailed schedule of all project tasks
➢ Monitor progress of project against milestones

14
Planning a Business Information Systems Project
3. Human resource management
➢ Recruit and hire project team members
➢ Train, motivate, team build

4. Cost Management
➢ Calculate initial cost/benefit analysis
➢ Monitor expenses

5. Communication Management
➢ Identify stakeholders and their communications
➢ Establish team communications
15
Planning a Business Information Systems Project
6. Risk Management
➢ Identify and review risks for failure
➢ Develop plans to reduce these risks

7. Procurement Management
➢ Develop requests for proposals (RFPs)
➢ Evaluate bids, write contracts, monitor performance

8. Quality Management
➢ Establish quality plan and control activities for each project
phase
9. Integration Management 16
Planning a Business Information Systems Project

STEP 3: Define what your system needs to do

(Process – Objectives - Input – Process – Output)

By taking this step you should be able to answer…

➢ How does the design of my business information

system enable to maintain it? Is it possible to design
an information system so that training is minimized?
➢ How will newly computerized processes link to
retained manual and paper-based processes?
17
THE INFORMATION SYSTEM DEVELOPMENT PROCESS

Building a system can be broken down into six core activities. 18

THE SYSTEM DEVELOPMENT PROCESS

❑ Systems analysis is the analysis of a problem that a

firm tries to solve with an information system. It consists
of defining the problem, identifying its causes, specifying
the solution, and identifying the information requirements
that must be met by a system solution.

❑ The systems analysis also includes a feasibility study to

determine whether that solution is feasible, or
achievable, from a financial, technical, and organizational
standpoint.
19
THE SYSTEM DEVELOPMENT PROCESS

❑ Information requirements of a new system involve

identifying who needs what information, where, when,
and how.
❑ The most challenging task of the systems analyst is to
define the specific information requirements that must
be met by the chosen system solution.

20
THE SYSTEM DEVELOPMENT PROCESS

PROCESS 1: SYSTEM ANALYSIS describes what a system

should do to meet information requirements, and systems design
shows how the system will fulfill this objective.

PROCESS 2: SYSTEM DESIGN: The design of an information

system is the overall plan or model for that system. Like the
blueprint of a building or house, it consists of all the specifications
that give the system its form and structure.
❑ Proposed system requirements specifications including a
conceptual data model, system design prototype, modified
DFDs, and Metadata (data about data).
21
SYSTEM DESIGN ACTIVITIES

22
COMPLETING THE SYSTEMS DEVELOPMENT PROCESS
These concluding steps consist of programming, testing,
conversion, production, and maintenance.

PROCESS 3: PROGRAMMING/SYSTEM DEVELOPMENT

In this stage, system specifications that were prepared during the
design stage are translated into software program code.
❑ Today, many organizations no longer do their own
programming for new systems. Instead, they purchase the
software that meets the requirements for a new system from
external sources such as:

23
 SYSTEM DESIGNING, PROGRAMMING/DEVELOPMENT

CRUD FUNCTIONS

STORE DATA

DATABASE
SELECT DATA

END-USER’S INTERFACE
Example: USER INTERFACE
- ADMINISTRATOR/OWNER
Example:
- ACCOUNTANT
- CASHIER - Customer 24
- SUPPLIER - Consumer
COMPLETING THE SYSTEMS DEVELOPMENT PROCESS

➢ software packages from a commercial software vendor

➢ software services from an application service provider, or
➢ outsourcing firms that develop custom application
software for their clients

❑ PROCESS 4: SYSTEM TESTING - tests the functioning

of the information system as a whole.
❑ Acceptance testing provides the final certification that
the system is ready to be used in a production setting.

25
COMPLETING THE SYSTEMS DEVELOPMENT PROCESS

PROCESS 5: CONVERSION - is the process of changing

from the old system to the new system.

PROCESS 6: PRODUCTION AND MAINTENANCE

❑ After the new system is installed and conversion is
complete, the system is said to be in production.
❑ In this stage, the system will be reviewed by both
users and technical specialists to determine how well it
has met its original objectives and to decide whether
any revisions or modifications are in order.
26
COMPLETING THE SYSTEMS DEVELOPMENT PROCESS

❑ Maintenance – changes in hardware, software,

documentation, or procedures to a production system to
correct errors, meet new requirements, or improve
processing efficiency.

27
Needed Tools in the Design and Building of BIS

❑ Software Requirements
❑ Programming Language
❑ Database Software
❑ Designing Tools
❑ Etc.

❑ Hardware Specifications
❑ Computer/Laptop
❑ Internet Connectivity
❑ Etc.
28
Needed Tools in the Design and Building of BIS

❑ Project Schedule/Gantt Chart (Use MS Project)

❑ Charts/Diagramming (Use MS Visio);
❑ examples:
❑ System Prototyping
❑ Organizational Chart
❑ Use Case Description
❑ Use Case Diagram
❑ Activity Diagram
❑ Class Diagram
❑ Entity-Relationship Diagram
29
JAY MARK F. ARENDAIN, MIS
Subject Instructor