Information System

Module 1: Lesson 1

AIS01-18 – IS Analysis and Design

 INFORMATION SYSTEM

A system is a group of elements that work together to accomplish an objective.

The information system is a computer-based systems that capture, store, and retrieve data associated with process
activities. In addition, they organize these data into meaningful information that organizations use to support and
assess these activities.

FUNCTIONAL
ENTERPRISE SYSTEMS
INFORMATION SYSTEM

Systems which evolved Systems which support the entire

independently of one another. process rather than parts of the
process.

AIS01-18 – IS Analysis and Design Module 1: Lesson 1 – Information System

 INFORMATION SYSTEM

ENTERPRISE SYSTEMS

FUNCTIONAL
INFORMATION SYSTEM

AIS01-18 – IS Analysis and Design Module 1: Lesson 1 – Information System

 ROLE OF INFORMATION SYSTEM

EXECUTE THE CAPTURE AND STORE MONITOR PROCESS

PROCESS PROCESS DATA PERFORMANCE

INFORMATION SYSTEM COMPONENTS INFORMATION SYSTEM FUNCTIONS

PEOPLE
INFORMATION
INPUT PROCESS OUTPUT STORAGE CONTROL
SOFTWARE
HARDWARE
DATA
PROCESS
AIS01-18 – IS Analysis and Design Module 1: Lesson 1 – Information System
 KNOWLEDGE CHECK!

Which is not an IS Component?

A. Data
B. Information
C. Framework
D. Human

What IS activity involves maintaining and organizing records i.e. details related to customers, etc.?
A. Input
B. Storage
C. Process
D. Output

AIS01-18 – IS Analysis and Design Module 1: Lesson 1 – Information System

 Systems Development Life Cycle
Module 1: Lesson 2

AIS01-18 – IS Analysis and Design

 SYSTEMS DEVELOPMENT LIFE CYCLE (SDLC)

SDLC is a multistage procedure which is generally treated as “best practices” for Systems Development.

Generally, it has four (4) phases, each phase is itself composed of a series of steps, which rely upon
techniques that produce deliverables (specific documents and files that provide understanding about the
project).

PARTICIPANTS IN SYSTEM DEVELOPMENT:

• Systems Professionals
• End-users
• Stakeholders
• Accountants/Auditors

AIS01-18 – IS Analysis and Design Module 1: Lesson 2 – Systems Development Life Cycle
 INFORMATION SYSTEM ACQUISTIION
IN-HOUSE
DEVELOPMENT
• For companies with unique
operations or activities
• Software is not readily
available in the market or is
very costly.
• Requires maintaining a full-
time systems staff of analysts
and programmers.
AIS01-18 – IS Analysis and Design
COMMERCIAL
SYSTEMS
• Systems that are purchased
from software vendors.
TURNKEY SYSTEMS BACKBONE SYSTEMS
GENERAL ACCOUNTING SYSTEMS SPECIAL PURPOSE SYSTEMS
OFFICE AUTOMATION SYSTEMS
VENDOR SUPPORTED SYSTEMS
Module 1: Lesson 2 – Systems Development Life Cycle
 SYSTEMS DEVELOPMENT LIFE CYCLE (SDLC)

PLANNING is the fundamental process of

understanding why an information system should
PLANNING be built and determining how the project team
will go about building it.

ANALYSIS • Project Initiation

IMPLEMENTATION • Project Management

ANALYSIS answers the questions of who will use

the system, what the system will do, and where
DESIGN
and when it will be used. During this phase, the
project team investigates any current system(s),
identifies improvement opportunities, and
develops a concept for the new system.

AIS01-18 – IS Analysis and Design Module 1: Lesson 2 – Systems Development Life Cycle
 SYSTEMS DEVELOPMENT LIFE CYCLE (SDLC)

DESIGN PHASE decides how the system will

operate in terms of the hardware, software, and
PLANNING network infrastructure that will be in place; the
user interface, forms, and reports that will be
used; and the specific programs, databases, and
ANALYSIS files that will be needed.
IMPLEMENTATION
IMPLEMENTATION is the final phase during which
the system is built (or purchased and installed if
the design calls for a prewritten software
DESIGN
package).

AIS01-18 – IS Analysis and Design Module 1: Lesson 2 – Systems Development Life Cycle
 KNOWLEDGE CHECK!

Which of the following individuals would likely be SDLC participants EXCEPT

A. Accountants
B. Shareholders
C. Management
D. Programmers

What should be the basis of the management’s decision to buy available software or to build a custom software
application?
A. Cost savings by switching to recognized best-in-class application used by others in the industry.
B. Converting from existing internal custom processes to the method new software operates in
order to save money by avoiding the cost of customization
C. Competitive advantage of using the same software as everyone else
D. Data from the feasibility study and business specifications
AIS01-18 – IS Analysis and Design Module 1: Lesson 2 – Systems Development Life Cycle
 System Analyst
Module 2: Lesson 1

AIS01-18 – IS Analysis and Design

 THE SYSTEM ANALYST
A System analyst plays a key role in the SDLC:
• Analyzing the business situation
• Identifying opportunities for improvements
• Designing an information system to implement the improvements

SYSTEM ANALYST

CHANGE MANAGEMENT ANALYST

REQUIREMENTS ANALYST
INFRASTRUCTURE ANALYST

PROJECT MANAGER

BUSINESS ANALYST

AIS01-18 – IS Analysis and Design Module 2: Lesson 1 –Systems Analyst

 THE SYSTEM ANALYST

CHANGE AGENTS

✓ Technical
✓ Analytical
✓ Interpersonal

✓ Business

✓ Ethical
✓ Management

AIS01-18 – IS Analysis and Design Module 2: Lesson 1 –Systems Analyst

KNOWLEDGE CHECK!

James is a system analyst on a new account management system for BPI. At a recent
meeting with the project sponsor, James learned about some new ideas for the system that
were not part of the original project scope. Specifically, the bank’s marketing director has
asked that some of the data that will be collected by the new system from customers who
open a new checking and savings accounts also be used as the basis of a marketing
campaign for various loan products the bank offers. James is uncomfortable with the
request. He is not sure the bank has the right to use a person’s data for purposes other
than the original intent.
KNOWLEDGE CHECK!

1. Who “owns” this data, the bank that collected it as a part of a customer opening an
account, or the customer who the data describes?

2. Should James insist that the customers give authorization to use “their” data in this way?
Or should he say nothing and ignore the issue?

3. Is it necessary (or appropriate) for a systems analyst to be an ethical watchdog in a

systems development project? Why or why not?
 Systems Development Methodologies
Module 2: Lesson 2

AIS01-18 – IS Analysis and Design

 METHODOLOGIES
A methodology is a formalized approach to implementing SDLC.

STRUCTURED DESIGN RAPID APPLICATION DEVELOPMENT AGILE DEVELOPMENT

Structured design methodologies adopt a formal step-by-step approach to SDLC that moves logically from
one phase to the next.

1. Waterfall Development

• Original structured design methodology

• Moves forward from one phase in the same manner as the waterfall.
• Requirements are typically very long.

AIS01-18 – IS Analysis and Design Module 2: Lesson 2 – Systems Development Methodologies

 METHODOLOGIES

Advantage/s:
• Identifies system requirements
long before programming
begins
• Minimizes changes to the
requirements as the project
proceeds.

Disadvantage/s:
• The design must be completely
specified before programming
begins.
• A long time elapses between
the completion of the system
proposal in the analysis phase
and the delivery of the system.

AIS01-18 – IS Analysis and Design Module 2: Lesson 2 – Systems Development Methodologies

 METHODOLOGIES
2. Parallel Development

• Performs a general design for the whole system and then divides the project into a series of distinct
subprojects that can be designed and implemented in parallel.

Advantage/s
• Reduce the time to deliver a
system

Disadvantage/s:
• The end of the project can
require significant integration
eff orts.

AIS01-18 – IS Analysis and Design Module 2: Lesson 2 – Systems Development Methodologies

 METHODOLOGIES
A methodology is a formalized approach to implementing SDLC.

STRUCTURED DESIGN RAPID APPLICATION DEVELOPMENT AGILE DEVELOPMENT

Rapid Application Development (RAD) use special techniques and computer tools to speed up the
analysis, design, and implementation phases.

1. Phased Development

• Breaks an overall system into a series of versions that are developed sequentially.
• Have the advantage of quickly getting a useful system into the hands of the users.
• Users begin to work with systems that are intentionally incomplete.

AIS01-18 – IS Analysis and Design Module 2: Lesson 2 – Systems Development Methodologies

 RAD METHODOLOGIES

AIS01-18 – IS Analysis and Design Module 2: Lesson 2 – Systems Development Methodologies

 RAD METHODOLOGIES

2. Prototyping

• Performs the analysis, design, and implementation phases concurrently, and all three phases
are performed repeatedly in a cycle until the system is completed.
• Work immediately begins on a system prototype, a quick-and-dirty program that provides a
minimal amount of features.

Advantages:
• It very quickly provides a system with which the users can interact, even if it is not
ready for widespread organizational use at first.
• Reassures the users that the project team is working on the system (there are no long
delays in which the users see little progress).
• Helps to more quickly refine real requirements.

AIS01-18 – IS Analysis and Design Module 2: Lesson 2 – Systems Development Methodologies

 RAD METHODOLOGIES

Disadvantage/s:
• Its fast-paced system releases challenge attempts to conduct careful, methodical analysis.

AIS01-18 – IS Analysis and Design Module 2: Lesson 2 – Systems Development Methodologies

 RAD METHODOLOGIES

3. Throwaway Prototyping

• Have a relatively thorough analysis phase that is used to gather information and to develop
ideas for the system concept.
• Involves designing and building a “design” prototype which is not a working system.
• Relies on several design prototypes during the analysis and design phases.

Advantages:
• Produces more stable and reliable systems.

Disadvantage/s:
• Take longer to deliver the final system as compared to prototyping-based
methodologies

AIS01-18 – IS Analysis and Design Module 2: Lesson 2 – Systems Development Methodologies

 RAD METHODOLOGIES

AIS01-18 – IS Analysis and Design Module 2: Lesson 2 – Systems Development Methodologies

 METHODOLOGIES
A methodology is a formalized approach to implementing SDLC.

STRUCTURED DESIGN RAPID APPLICATION DEVELOPMENT AGILE DEVELOPMENT

Agile Development focus on streamlining the system-development process by eliminating much

of the modeling and documentation overhead and the time spent on those tasks.

Simple Cycle

AIS01-18 – IS Analysis and Design Module 2: Lesson 2 – Systems Development Methodologies

 AGILE METHODOLOGIES

1. Extreme Programming (XP)

• Founded on four core values: communication, simplicity, feedback, and courage.

• Three of the key principles that XP uses to create successful systems are continuous
testing, simple coding performed by pairs of developers, and close interactions with end
users to build systems very quickly.
• Recommended only for small groups of developers—no more than ten developers—and it is
not advised for large mission-critical applications.
• Needs a lot of on-site user input

AIS01-18 – IS Analysis and Design Module 2: Lesson 2 – Systems Development Methodologies

 AGILE METHODOLOGIES

2. Scrum

• Scrum means to restart a game.

• Most chaotic.
• Teams are self-organized and self-directed (no team leader).
• Once a sprint has begun, Scrum teams do not consider any additional requirements. Any new
requirements that are uncovered are placed on a back-log of requirements that still need to
be addressed.

AIS01-18 – IS Analysis and Design Module 2: Lesson 2 – Systems Development Methodologies

 CRITERIA FOR SELECTING A METHODOLOGY

• Clarity of user requirements

• Familiarity with technology
• System Complexity
• System Reliability
• Short Time Schedules
• Schedule Visibility

AIS01-18 – IS Analysis and Design Module 2: Lesson 2 – Systems Development Methodologies