1. Development Processes
Chapter 12
Development Processes

2. "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
GOALS
Use the PRIDE System to:
Demonstrate a typical software development meeting in a small startup.
Show the wide range in development costs that can exist.
Illustrate the use of a prototype for reducing risk.
Provide a setting for a discussion of scrum.
Copyright © 2016 Pearson Education, Inc.

3. Copyright © 2016 Pearson Education, Inc.
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
Copyright © 2016 Pearson Education, Inc.

4. Copyright © 2016 Pearson Education, Inc.
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 processes? Q4: What are the phases in the systems development life cycle (SDLC)? Q5: What are the keys for successful SDLC projects? Q6: How can scrum overcome the problems of the SDLC? Q7: 2025
Remind students that as a business professional, they will be involved in the development of new technology applications their business, and may take the lead in in developing an application.
Copyright © 2016 Pearson Education, Inc.

5. Q1: How Are Business Processes, IS, and Applications Developed?
Application: combination of hardware, software, data components that accomplish a set of requirements
Three different development processes--Steps in Processing an Order
Ensure operations department verifies product is available and can be delivered on requested schedule.
Check with Accounting to verify credit required to process the order.
Check with your boss, a sales manager, to approve any special terms the customer might request (discounts, free shipping, extended return policy, and so forth).
Copyright © 2016 Pearson Education, Inc.

6. Relationship of Business Processes and Information Systems
Every information system has at least one application
Copyright © 2016 Pearson Education, Inc.

7. Copyright © 2016 Pearson Education, Inc.
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.
People confuse these terms. They’ll quickly switch back and forth among processes, systems, and applications without knowing they’ve changed terms and contexts.
With these understandings, you can add value to your team simply by clarifying these differences.
Copyright © 2016 Pearson Education, Inc.

8. Which Development Processes Are Used for Which?
Three ways to develop applications: BPM, SDLC, scrum, steal them.
Copyright © 2016 Pearson Education, Inc.

9. Role of Development Personnel
Business analyst is well versed in Porter’s models, organization strategies, and focuses on ensuring business processes and information systems meet organization’s competitive strategies.
Copyright © 2016 Pearson Education, Inc.

10. Q2: How Do Organizations Use Business Process Management (BPM)?
Activities
Repository
Inventory
Database
These terms are defined in Ch. 3.
Copyright © 2016 Pearson Education, Inc.

11. Copyright © 2016 Pearson Education, Inc.
New Terms
Roles -
Collections of activities
Resources -
People or computer applications assigned to roles
Flow
Control flow - directs order of activities
Data flow - movement of data among activities & repositories
Copyright © 2016 Pearson Education, Inc.

12. Why Do Processes Need Management?
Processes are dynamic and often need to be changed
Three fundamental reasons:
Improve process quality
Change in technology
Change in business fundamentals
Monitor process quality and adjust process design, as appropriate.
Copyright © 2016 Pearson Education, Inc.

13. Examples of Change in Business Fundamentals
Market (new customer category, change in customer characteristics)
Product lines
Supply chain
Company policy
Company organization (merger, acquisition)
Internationalization
Business environment (new priority on credit checking)
Business environment could involve adapt change
Copyright © 2016 Pearson Education, Inc.

14. Copyright © 2016 Pearson Education, Inc.
Four Stages of BPM
Stages in BPM Cycle
BPM is a cyclical process for systematically creating, assessing, and altering business processes.
Cycle begins by creating models of business processes.
Build an as-is model that documents the current situation.
See for more information.
COBIT (Control Objectives for Information and related Technology)
Copyright © 2016 Pearson Education, Inc.

15. Copyright © 2016 Pearson Education, Inc.
Q3: How Is Business Process Modeling Notation (BPMN) Used to Model Processes?
Copyright © 2016 Pearson Education, Inc.

16. Existing Order Process
Note: role named CRM in this subprocess. This role is performed entirely by an information system, although we cannot determine that from this diagram.
Copyright © 2016 Pearson Education, Inc.

17. Check Customer Credit Process
Copyright © 2016 Pearson Education, Inc.

18. Q4: What Are the Phases in the Systems Development Life Cycle (SDLC)?
Copyright © 2016 Pearson Education, Inc.

19. Copyright © 2016 Pearson Education, Inc.
SDLC Definition Phase
At the start, cost and schedule feasibility are only an approximation or back-of-the-envelope analysis.
Eliminate any obviously infeasible ideas as soon as possible.
Copyright © 2016 Pearson Education, Inc.

20. Copyright © 2016 Pearson Education, Inc.
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
Expense is often justified not only for greater clarity and completeness of requirements, and because parts of prototype can be reused in operational system
Copyright © 2016 Pearson Education, Inc.

21. SDLC Requirements Analysis Phase
Most important phase in the systems development process. If requirements are wrong, the system will be wrong. If requirements are determined completely and correctly, then design and implementation will be easier and more likely to result in success.
Copyright © 2016 Pearson Education, Inc.

22. SDLC Component Design Phase
Team determines specifications for the hardware that they want to acquire.
Program design depends on the source of the programs. For off-the-shelf software, team must determine candidate products and evaluate them against the requirements. For off-the-shelf with alteration programs, team identifies products to be acquired off-the-shelf, then determines alterations required. For custom-developed programs, team produces design documentation for writing program code.
Copyright © 2016 Pearson Education, Inc.

23. SDLC System Maintenance Phase
Needs to be a means for tracking both failures and requests for enhancements to meet new requirements. Many organizations find it necessary to develop a tracking database. This database contains a descriptions of failures and enhancements , who reported them, who will make the fix or enhancement, status of that work, and whether the fix or enhancement has been tested and verified by the originator.
Copyright © 2016 Pearson Education, Inc.

24. Design and Implementation for the Five Components
This table summarizes the tasks for five IS components during the design and implementation phases.
Copyright © 2016 Pearson Education, Inc.

25. SDLC System Maintenance Phase
Copyright © 2016 Pearson Education, Inc.

26. Ethics Guide: Estimation Ethics
Estimating just a “theory”
Average of many people’s guesses
Buy-in game
Projects start with overly optimistic schedules and cost estimates
When is a buy-in within accepted boundaries of conduct?
GOALS
Introduce concept of buy-in as it pertains to information systems.
Assess ethics of buy-ins in different settings.
Copyright © 2016 Pearson Education, Inc.

27. 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?
One major goal is to see how buy-ins apply to information systems projects. Future managers need to know this to guard against, or at least consider, possibility of a buy-in.
Future managers need to consider their own values and principles.
Copyright © 2016 Pearson Education, Inc.

28. 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?
One major goal is to see how buy-ins apply to information systems projects. Future managers need to know this to guard against, or at least consider, possibility of a buy-in.
Future managers need to consider their own values and principles.
Copyright © 2016 Pearson Education, Inc.

29. 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
Copyright © 2016 Pearson Education, Inc.

30. Work Breakdown Structure (WBS)
Copyright © 2016 Pearson Education, Inc.

31. Partial Gantt Chart for Definition Phase of Project
Critical path is red. Note, start date-stop dates of activities, dependencies of activities.
Copyright © 2016 Pearson Education, Inc.

32. Partial Gantt Chart with Resources (People) Assigned
Adds resources to chart.
Copyright © 2016 Pearson Education, Inc.

33. Primary Drivers of Systems Development
Inherent in trade offs involve risks.
Copyright © 2016 Pearson Education, Inc.

34. Manage Development Challenges
1. Coordination
2. Diseconomies of scale
Brook's Law
3. Configuration control
4. Unexpected events
Copyright © 2016 Pearson Education, Inc.

35. Copyright © 2016 Pearson Education, Inc.
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
“Nine women cannot make a baby in one month.”
Copyright © 2016 Pearson Education, Inc.

36. 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.
Copyright © 2016 Pearson Education, Inc.

37. Q6: How Can Scrum Overcome the Problems of the SDL
Alternatives to SDLC
Rapid application development
Unified process
Extreme programming
Scrum
Others
Principles of Agile (Scrum) Development
Copyright © 2016 Pearson Education, Inc.

38. Principles of Agile (Scrum) Development
Copyright © 2016 Pearson Education, Inc.

39. Copyright © 2016 Pearson Education, Inc.
Scrum Essentials
Copyright © 2016 Pearson Education, Inc.

40. Copyright © 2016 Pearson Education, Inc.
Scrum Process
Copyright © 2016 Pearson Education, Inc.

41. Copyright © 2016 Pearson Education, Inc.
When Are We Done?
Customer is satisfied with product created and accepts it
Project runs out of time
Project runs out of money
Copyright © 2016 Pearson Education, Inc.

42. How Do Requirements Drive the Scrum Process?
Copyright © 2016 Pearson Education, Inc.

43. Summary of Scrum Estimation Techniques
Copyright © 2016 Pearson Education, Inc.

44. Copyright © 2016 Pearson Education, Inc.
Q7: 2025?
Continuing focus on aligning business processes and information systems with business strategy, goals, objectives
Applications built faster, more easily changed and adapted
Applications develop other applications (singularity)
The cloud lead to substantially more innovation
Very small hardware budgets
Emergence of new software vendor business models
Copyright © 2016 Pearson Education, Inc.

45. 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?
GOALS
Sensitize students to possibility of industrial espionage.
Set up need for IS management (next chapter).
Give yet another example of why strong passwords are necessary.
Copyright © 2016 Pearson Education, Inc.

46. 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!
Longer projects mean more chance for technology change, requirements change, employee turnover
GOALS
Inspire students to use what they have learned to find, create, and manage innovative applications of IS technology.
Copyright © 2016 Pearson Education, Inc.

47. 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!
GOAL
Inspire students to use their learning from this class to find, create, and manage innovative applications of information systems and technology.
WRAP UP
The best is yet to come!
What that best is, what happens next, will be in large measure up to you!
We started this book with a firing and we’re ending it, we hope, with a hiring… yours!
Copyright © 2016 Pearson Education, Inc.

48. Copyright © 2016 Pearson Education, Inc.
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 processes? Q4: What are the phases in the systems development life cycle (SDLC)? Q5: What are the keys for successful SDLC projects? Q6: How can scrum overcome the problems of the SDLC? Q7: 2025
Copyright © 2016 Pearson Education, Inc.

49. Case Study 12: When Will We Learn?
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.
GOALS
Illustrate difference between application development and systems development.
Motivate need for the SDLC or other development process.
Illustrate some difficulties in creating and managing an inter-enterprise system.
Copyright © 2016 Pearson Education, Inc.

50. 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.
Copyright © 2016 Pearson Education, Inc.

51. Copyright © 2016 Pearson Education, Inc.