Muhammad Ghiffari Faza

18/429426/EK/22035
CHAPTER 13 – BUILDING INFORMATION SYSTEM

Four changes enabled by IT:

1. Automation  Assisting employees with performing their tasks more efficiently and effectively.
2. Rationalization  Streamlining of standard operating procedures; usually found in TQM.
3. Business Process Redesign  Business process analyzed, simplified, and redesigned.
4. Paradigm Shifts  Rethinking the nature of business.

Business process management (BPM)  Provides variety of tools and methodologies to anlyze existing processes, design new
processes, and optimize processes. Steps includes:

1. Identify processes for change  what business processes needs improvement, how to do it with little time, and little
impact in overall performance.
2. Analyze existing processes  modeled and documented to identify inefficiencies.
3. Design new processes  modeled and documented for comparison to the old one.
4. Implement the new process  translated into a new set of procedures and work rules. As it was applied, problems are
uncovered and addressed.
5. Continuous measurement  because processes may deteriorate over time as employees fall back to old methods.

System Development  Activities that go into producing an information system solution to an organizational problem or
opportunity.

1. System Analysis  Analysis of a problem that a firm tries to solve with an information system. Process: Defining the
problem, identifying its causes, specifying the solution, and identifying the information requirements that must be met
by a system solution. Also includes feasibility studi to determine whether the solution is feasible, or achievable, from a
financial, technical, and organizational standpoint. Establishing information requirement: identifying who needs what
information, where, when, and how.
2. System Design  Shows how the system will fulfill the objective drive by the information requirements. Users must
have sufficient control over the design process to ensure that the system refleccts their business priorities and information
needs.
3. Completing:
a. Programming  System specifications that were prepared during the design stage are translated into the software
program code.
b. Testing  Must be conducted to ascertain whether the system produces the right results. Kinds: System Testing
(function of information system as a whole), Acceptance testing (inal certification that the system us ready to use),
Test Plan (all preparations for the series of test).
c. Conversion  Process of changing from the old system to new system. Kinds: Parallel Strategy (old and new run
together until assure that the new one fits), Direct cutover strategy (replace old system entirely on appointed day),
Pilot study strategy (introduce new systen only in limited area of organization), Phased approach study (introduce
new system in stages; by functions or organizational units)
d. Production (after new system installed and conversion complete) & Maintenance (changes in hardware, software,
documentation, or procedures to a production system to correct errors, meet new requirements, or improve
processing efficiency).

Structured Methodologies  Steps using:

1. Data Flow Diagram (DFD), which offers logical graphic model of information flow.
2. Data Dictionary, contains info about individual pieces of data and groupings within system. Process specifications
describe transformation occurring within the lowest level of data flow diagrams.
3. Structure Chart, a top-down chart, showing each level of design, its relationship to other levels, and its place in the
overall design structure.

Alternative:

1. Traditional System Life Cycle  Oldest Method

2. Prototyping  Building experimental system rapidly and inexpensively for end users.
3. End User Development  Object-oriented development uses the subject as the basic unit of sytems analysis & design.
4. App Software Packages and Service.

New Approaches:

Rapid App Development (RAD); Joint App Design (JAD); Agile Development; DevOps; Component based
development; Mobile App.