Experiencing MIS 8th by m kronenke chapter 12

Study QuestionsQ1: How are business processes, IS, and applications developed?. Q3: How is business process modeling notation BPMN used to model... Q1: How Are Business Processes, IS, an

Development Processes

Chapter 12

"We Think We Can Open the Doors to an Entirely New Market"

• Example of decision making in small company

– Zev owner and source of investment funds – Team presents idea, he listens and makes a decision

• Team doesn’t really know what’s involved

• Building a prototype a good, low cost way to learn

• Situation similar with a professional IS department

Bottom Line

• Startups can be fun and interesting places to work

• Time and budgets limited

• Decisions usually made more quickly, but risky if not well managed

• Prototypes used to reduce front-end risk

• Scrum ideal development process for creating prototypes

Study Questions

Q1: How are business processes, IS, and applications developed?

Q2: How do organizations use business process management (BPM)?

Q3: How is business process modeling notation (BPMN) used to model

Q1: How Are Business Processes, IS, and

Applications Developed?

Application: combination of

hardware, software, data

components that accomplish a

set of requirements

Relationship of Business Processes and

Information Systems

Every information system has at least one application

How Do Business Processes, Information

Systems, and Applications Differ and Relate?

1 Business processes, information systems, applications have

different characteristics and components.

2 Relationship of business processes to information systems is

many-to-many, or N:M

 Business process need not relate to any information system, but

an information system relates to at least one business process.

3 Every IS has at least one application because every IS has a

software component

Which Development Processes Are Used for

Which?

Role of Development Personnel

Q2: How Do Organizations Use Business Process

Why Do Processes Need Management?

Processes are dynamic and often need to be changed

Three fundamental reasons:

1 Improve process quality

2 Change in technology

3 Change in business fundamentals

Examples of Change in Business Fundamentals

• Market (new customer category, change in customer

Four Stages of BPM

COBIT (Control Objectives for Information and related Technology)

Stages in BPM Cycle

Q3: How Is Business Process Modeling Notation

(BPMN) Used to Model Processes?

Existing Order

Process

Check

Customer

Credit

Process

Q4: What Are the Phases in the Systems

Development Life Cycle (SDLC)?

SDLC Definition Phase

Role of a Prototype

• Provides direct experience for user

• Can be expensive to create

• Parts often reused

– PRIDE code generates Xbox may be reused

in operational system

• Cost occurs early, sometimes before full project funding available

SDLC Requirements Analysis Phase

SDLC Component Design Phase

SDLC System Maintenance Phase

Design and Implementation for the Five

Components

SDLC System Maintenance Phase

Ethics Guide: Estimation Ethics

• Estimating just a “theory”

– Average of many people’s guesses

Ethics Guide: Estimation Ethics (cont'd)

• Contractor agrees to produce system for less than what really costs

– Time and materials contract – Fixed-cost contract

• In-house projects often start with buy-ins

– Start with hopes of more money later – Team members disagree about costs Do you report it?

– Not all costs included in initial estimates Report it?

• Do you buy-in on project schedule if you know you can’t make

that schedule?

Ethics Guide: Estimation Ethics (cont'd)

• Be aware buy-ins occur and some vendors make

a practice of bidding projects with them

– Carefully scrutinize unbelievably low bids

• There is no substitute for experience

– Hire expertise to evaluate bids

• Consider your own position on buy-ins

– When can you ever justify one? If so, when?

Q5: What Are the Keys for Successful SDLC

Projects?

• Create a work-breakdown structure (WBS)

• Estimate time and costs

• Create a project plan

• Adjust plan via trade-offs

• Manage development challenges

Work

Breakdown

Structure

(WBS)

Partial Gantt Chart for Definition Phase of Project

Partial Gantt Chart with Resources (People)

Assigned

Primary Drivers of Systems Development

Manage Development Challenges

Diseconomies of Scale

Brooks’ Law

• “Adding more people to a late project makes

the project later.”

• New staff must be trained by productive members who lose productivity while training

• Schedules can be compressed only so far

• Once a project is late and over budget, no good choice exists

So What? Systems Development?

• You have great idea for an application system

What do you do with it?

• Idea better be consistent with your organization’s competitive strategy.

• Apply your knowledge of the SDLC to produce a proposal for a new system to enhance its chances

of being approved and developed.

Q6: How Can Scrum Overcome the Problems of

– Others

Principles of Agile (Scrum) Development

Scrum

Essentials

Scrum Process

When Are We Done?

• Customer is satisfied with product created and accepts it

• Project runs out of time

• Project runs out of money

How Do Requirements Drive the Scrum Process?

Summary of Scrum Estimation Techniques

Q7: 2025?

1 Continuing focus on aligning business processes and

information systems with business strategy, goals, objectives

2 Applications built faster, more easily changed and adapted

– Applications develop other applications (singularity)

3 The cloud lead to substantially more innovation

– Very small hardware budgets

4 Emergence of new software vendor business models

Security Guide: Psst There’s Another Way, You

Know

• Do you think servers in China were actually shut down?

• Large organizations with good IS departments with port

24 set to only allow traffic to go to IP address of ISP did

not lose any designs.

• What about smaller organizations with minimal IS

Department, or supported by small, unsophisticated

VAR?

Guide: Final, Final Word

• Learn to find, create, and manage innovative applications of IS technology

• Two important takeaways:

– Software developers are optimists – Be aware of consequences of negotiating a schedule – Large projects much harder to schedule than small ones

 If project lasts longer than a year, watch out!

o Longer projects mean more chance for technology

change, requirements change, employee turnover

Guide: The Final, Final Word (cont'd )

• Use what you’ve learned in this class to obtain the job you really want!

• Do the exercises at the end of this guide, and use the answers in your job interviews!

Active Review

Q1: How are business processes, IS, and applications developed?

Q2: How do organizations use business process management (BPM)?

Q3: How is business process modeling notation (BPMN) used to model

Case Study 12: When Will We Learn?

• 1974 - Number one reason for failure was a lack of user

involvement in creating and managing system

requirements.

• Access CT project (2013) successful

– If schedule is fixed, and funding nearly fixed, what factor

can be traded-off to reduce project difficulty and risk?

– Requirements Reduce to bare minimum and get

system running Then, after some success, add to it

Case Study 12: When Will We Learn? (cont'd)

• State of Oregon wasted more than $248 million attempting to

develop an information system to support its healthcare exchange

• Very early in project, Maximus Company, consulting firm hired to

provide quality assurance, warned that requirements were vague,

changing, and inconsistent.

• Those warnings made no difference Why?

• Software and systems are made of pure thought-stuff

– Easy to imagine a glorious future of amazing capability, but

subject to human frailties.