1. Development Processes
Chapter 10
Development Processes

2. Copyright © 2015 Pearson Education, Inc.
“We Need to Support Other Watches and Mobile Devices, and at Least Android Phones.”
Three doctors are partners and sole owners of Austin Cardiac Surgery.
Meeting to determine what to do next.
Need to define and document business procedures, train staff, involve other partners.
Make system more available on more devices.
Strategic implication: Spin off PRIDE as separate business?
GOALS
Use the PRIDE System to:
Illustrate the difference between application development and systems development.
Motivate the need for the SDLC and other development process.
Illustrate some of the difficulties in creating and managing an inter-enterprise system.
Copyright © 2015 Pearson Education, Inc.

3. Copyright © 2015 Pearson Education, Inc.
Bottom Line
Know the difference between an application program and a system.
PRIDE needs an IS, not just an application. Both business and systems analysts have a role.
When developing inter-enterprise systems, anticipate. procedural and usage problems and understand there will be differences in interest, motivation, and rewards for using new system.
Copyright © 2015 Pearson Education, Inc.

4. Copyright © 2015 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: 2024?
Copyright © 2015 Pearson Education, Inc.

5. Q1: How Are Business Processes, IS, and Applications Developed?
Application: combination of hardware, software, and data components that accomplishes a set of requirements.
Answer to Q1 clarifies what we’re developing and introducing three different development processes. Steps taken to process an order are as follows:
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 © 2015 Pearson Education, Inc.

6. Relationship of Business Processes and Information Systems
Every information system has at least one application because every IS includes a software component.
Copyright © 2015 Pearson Education, Inc.

7. Copyright © 2015 Pearson Education, Inc.
How Do Business Processes, Information Systems, and Applications Differ and Relate?
1. Business processes, information systems, and applications have different characteristics and components.
2. Relationship of business processes to information systems is many-to-many, or N:M.
A 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.
Copyright © 2015 Pearson Education, Inc.

8. Which Development Processes Are Used for Which?
This chapter investigates three ways to develop applications: Business Process Management (BPM), systems development life cycle (SDLC), and scrum. A fourth way to develop applications is to steal them.
Copyright © 2015 Pearson Education, Inc.

9. Role of Development Personnel
Copyright © 2015 Pearson Education, Inc.

10. Q2: How Do Organizations Use Business Process Management (BPM)?
Business process - a network of activities, repositories, roles, resources, and flows that interact to accomplish a business function.
Activities - a collections of related tasks that receive inputs and produce outputs.
Repository - a collection of something.
Inventory - a physical repository.
Database - a data repository.
Theses are defined in Ch. 3.
Copyright © 2015 Pearson Education, Inc.

11. Copyright © 2015 Pearson Education, Inc.
New Terms
Roles - a collections of activities.
Resources - are people or computer applications assigned to roles.
Flow
Control flow - directs the order of activities.
Data flow - movement of data among activities and repositories.
Copyright © 2015 Pearson Education, Inc.

12. Why Do Processes Need Management?
Processes are dynamic and often need to be changed
Why does this process need to be managed?
Fundamentally, there are three reasons: to improve process quality, to adapt to changes in technology, and to adapt to changes in business fundamentals.
Copyright © 2015 Pearson Education, Inc.

13. Why Do Process Need Management? (cont'd)
Three fundamental reasons
Improve process quality.
Change in technology.
Change in business fundamentals.
Need to monitor process quality and adjust process design, as appropriate.
Copyright © 2015 Pearson Education, Inc.

14. Examples of Change in Business Fundamentals
Market (e.g., new customer category, change in customer characteristics)
Product lines
Supply chain
Company policy
Company organization (e.g., merger, acquisition)
Internationalization
Business environment
Copyright © 2015 Pearson Education, Inc.

15. Q2: What Are the Business Process Management (BPM)?
Stages in the BPM Cycle
BPM is a cyclical process for systematically creating, assessing, and altering business processes.
Cycle begins by creating models of business processes.
Usually teams build an as-is model that documents the current situation.
See for more information.
Copyright © 2015 Pearson Education, Inc.

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

17. Documenting As-Is Business Order Process: Existing Order Process
Note the role named CRM in this subprocess. In fact, this role is performed entirely by an information system, although we cannot determine that from this diagram.
Copyright © 2015 Pearson Education, Inc.

18. Check Customer Credit Process
Copyright © 2015 Pearson Education, Inc.

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

20. SDLC: Definition Phase
SDLC: System definition phase.
At the start, cost and schedule feasibility are only an approximation or back-of-the-envelope analysis. The purpose is to eliminate any obviously infeasible ideas as soon as possible.
Copyright © 2015 Pearson Education, Inc.

21. Copyright © 2015 Pearson Education, Inc.
Role of a Prototype
Provides user direct experience.
Can be expensive to create.
Parts often reused
PRIDE code that generates smartphone display can be reused in the operational system.
Cost occurs early, sometimes before full project funding available.
Copyright © 2015 Pearson Education, Inc.

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

23. SDLC: Component Design Phase
For hardware, the 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, the team must determine candidate products and evaluate them against the requirements. For off-the-shelf with alteration programs, the team identifies products to be acquired off-the-shelf, then determines the alterations required. For custom-developed programs, the team produces design documentation for writing program code.
Copyright © 2015 Pearson Education, Inc.

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

25. SDLC: System Maintenance Phase
There 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 description of the failure or enhancement, and records who reported the problem, who will make the fix or enhancement, the status of that work, and whether the fix or enhancement has been tested and verified by the originator.
Copyright © 2015 Pearson Education, Inc.

26. Ethics Guide: Estimation Ethics
Estimating just “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 © 2015 Pearson Education, Inc.

27. Ethics Guide: Estimation Ethics
Contractor agrees to produce system for less than what really costs
Time and materials contract
Fixed-cost contract
In-house projects often started with buy-ins
Projects often 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 © 2015 Pearson Education, Inc.

28. Q5: What Are the Keys for Successful SDLC Projects?
Create a work-breakdown structure.
Estimate time and costs.
Create a project plan.
Adjust plan via trade-offs.
Manage development challenges.
Copyright © 2015 Pearson Education, Inc.

29. Work Breakdown Structure (WBS)
Copyright © 2015 Pearson Education, Inc.

30. Gantt Chart of the WBS for the Definition Phase of a Project
Copyright © 2015 Pearson Education, Inc.

31. Gantt Chart with Resources (People) Assigned
Copyright © 2015 Pearson Education, Inc.

32. Primary Drivers of Systems Development
Inherent in trade offs is risk.
Copyright © 2015 Pearson Education, Inc.

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

34. Copyright © 2015 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.
Example of Brooks Law - “Nine women cannot make a baby in one month.”
Copyright © 2015 Pearson Education, Inc.

35. Using MIS InClass 7: Improving the Process of Making Paper Airplanes
Purpose of this exercise is to demonstrate process concepts. Create one or more groups with four students in a group. Each student will perform in one work center (WC) activity. Assembly line processes transform raw material (a stack of plain paper) into folded paper airplanes as finished goods. See Figure 7-15 (p. 231) for details for the work center tasks.
See textbook for exercise instructions.
Copyright © 2015 Pearson Education, Inc.

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

37. Principles of Agile (Scrum) Development
Copyright © 2015 Pearson Education, Inc.

38. Copyright © 2015 Pearson Education, Inc.
Scrum Essentials
Copyright © 2015 Pearson Education, Inc.

39. Copyright © 2015 Pearson Education, Inc.
Scrum Process
Copyright © 2015 Pearson Education, Inc.

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

41. How Do Requirements Drive the Scrum Process?
Copyright © 2015 Pearson Education, Inc.

42. Summary of Scrum Estimation Techniques
Copyright © 2015 Pearson Education, Inc.

43. Copyright © 2015 Pearson Education, Inc.
Q7: 2024
Continuing focus on aligning business processes and information systems with business strategy, goals, and objectives.
Computer systems will be more easily changed and adapted.
The cloud will lead to substantially more innovation.
Emergence of new software vendor business models.
Copyright © 2015 Pearson Education, Inc.

44. 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 that had a firewall set up on port 24 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 the possibility of industrial espionage.
Set up need for IS management (next chapter).
Give yet another example of why strong passwords are necessary.
Copyright © 2015 Pearson Education, Inc.

45. Guide: The Real Estimation Process
Software developers are optimists.
People can’t work all the time.
Apply a factor like 0.6 to compute number of effective labor hours for each employee.
Be aware of consequences of negotiating a schedule.
GOALS
Sensitize students to challenges of software scheduling.
Alert students to possible consequences when negotiating a schedule.
Some important takeaways for students:
Software developers are optimists.
Be aware of the consequences of negotiating a schedule.
Large projects are much harder to schedule than small ones. Also, if the project lasts longer than a year, watch out! Longer projects mean more chance for technology change, requirements change, and employee turnover. All these factors increase the likelihood of schedule delays.
Copyright © 2015 Pearson Education, Inc.

46. Copyright © 2015 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: 2024?
Copyright © 2015 Pearson Education, Inc.

47. Case Study 10: Cost of PRIDE
Typical example of a new software venture.
So focused on technology and making it work, they neglect to consider what will happen, in the long term.
Some problem solutions involve staff training and procedures.
Flores and his partners need a longer term direction.
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 © 2015 Pearson Education, Inc.

48. Copyright © 2015 Pearson Education, Inc.
Sources of PRIDE Costs
Copyright © 2015 Pearson Education, Inc.