CSUN Information Systems dn58412/IS312/IS312_SP15.htm IS312 Information Systems for Business Lecture...

CSUN Information CSUN Information SystemsSystems

http://www.csun.edu/~dn58412/IS312/IS312_SP15.htm

IS312 Information Systems for IS312 Information Systems for BusinessBusiness

Lecture 8Lecture 8Information Systems DevelopmentInformation Systems Development

(Ch. 9)(Ch. 9)

IS 312 : Lecture 8

2

LEARNING OBJECTIVES Systems Development Life Cycle

Application Development Methodologies

Project Management

Systems Acquisition

Development Phases in a Structured Process

IS 312 : Lecture 8

3

APPLICATION DEVELOPMENT Application that is built correctly can transform

as the organization and its business transforms

Application that effectively meets employee needs will help an organization become more productive and enhance decision making

Application that does not meet employee needs may have a damaging effect on productivity and can even cause a business to fail

IS 312 : Lecture 8

4

APPLICATION DEVELOPMENT . . .

As organizations’ reliance on application software grows, so do the business-related consequences of application software successes and failures including:

• Increase or decrease revenue

• Repair or damage to brand reputation

• Prevent or incur liabilities

• Increase or decrease productivity

IS 312 : Lecture 8

5

The Need for Structured Systems Development

Process The process of defining requirements,

designing, building, and maintaining information systems• Standardized development methods

Best practices to follow Consistent quality

• Software engineering

IS 312 : Lecture 8

6

THE SYSTEMS DEVELOPMENT LIFE CYCLE (SDLC) Systems

development life cycle (SDLC) – The overall process for developing information systems from planning and analysis through implementation and maintenance

IS 312 : Lecture 8

7

The Systems Development Life Cycle

1. Planning phase – Establishes a high-level plan of the intended project and determines project goals

2. Analysis phase – Involves analyzing end-user business requirements and refining project goals into defined functions and operations of the intended system (WHAT)

• Business requirements – Specific business requests the system must meet to be successful

IS 312 : Lecture 8

8

The Systems Development Life Cycle . . .

3. Design phase – Establishes descriptions of the desired features and operations of the system including screen layouts, business rules, process diagrams, pseudo code, and other documentation (HOW)

4. Development phase – Involves taking all of the detailed design documents from the design phase and transforming them into the actual system

IS 312 : Lecture 8

9


5. Testing phase – Involves bringing all the project pieces together into a special testing environment to eliminate errors and bugs, and verify that the system meets all of the business requirements defined in the analysis phase

6. Implementation phase – Involves placing the system into production so users can begin to perform actual business operations with it

IS 312 : Lecture 8

10


7. Maintenance phase – Involves performing changes, corrections, additions, and upgrades to ensure the system continues to meet its business goals

IS 312 : Lecture 8

11

APPLICATION DEVELOPMENT METHODOLOGIES

Waterfall (Structured Process) Agile Rapid application development (RAD) Extreme programming Rational unified process (RUP) SCRUM

IS 312 : Lecture 8

12

Waterfall Methodology

Waterfall methodology – A structured sequence of phases in which the output of each phase becomes the input for the next

IS 312 : Lecture 8

13

Agile Methodology

Iterative development – Consists of a series of tiny projects

Agile methodology – Aims for customer satisfaction through early and continuous delivery of useful application software components developed by an iterative process using the bare minimum requirements

IS 312 : Lecture 8

14

Rapid Application Development

(RAD) Methodology Rapid application development methodology– Emphasizes extensive user involvement in the rapid and evolutionary construction of working prototypes of a system to accelerate the systems development process

Prototype – A smaller-scale representation or working model of the users’ requirements or a proposed design for an information system

The prototype is an essential part of the analysis phase when using a RAD methodology

IS 312 : Lecture 8

15

Extreme Programming Methodology

Extreme programming (XP) methodology – Breaks a project into tiny phases, and developers cannot continue on to the next phase until the first phase is complete

IS 312 : Lecture 8

16

Rational Unified Process (RUP) Methodology

Rational Unified Process (RUP) – Provides a framework for breaking down the development of software into four gates

• Gate One: Inception

• Gate Two: Elaboration

• Gate Three: Construction

• Gate Four: Transition

IS 312 : Lecture 8

17

SCRUM Methodology SCRUM – Uses small teams to produce small

pieces of deliverable software using sprints, or 30-day intervals, to achieve an appointed goal

Under this methodology, each day ends or begins with a stand-up meeting to monitor and control the development effort

IS 312 : Lecture 8

18

DEVELOPING SUCCESSFUL APPLICATION

Primary reasons for project failure• Unclear or missing business requirements

• Skipping SDLC phases

• Failure to manage project scope Scope creep Feature creep

• Failure to manage project plan

• Changing technology

IS 312 : Lecture 8

19

Developing Successful Application . . .

The later in the SDLC an error is found the more expensive it is to fix!

IS 312 : Lecture 8

20

MANAGING SOFTWARE DEVELOPMENT PROJECTS

Analysts predict investment in MIS projects worldwide is over $1 trillion

70 percent will be lost due to failed projects The consequences of failed projects include

•Damaged brand

•Lost goodwill

•Dissolution of partnerships

•Lost investment opportunities

•Low morale

IS 312 : Lecture 8

21

Managing Software Development Projects

Project – Temporary activities undertaken to create a unique product or service

Project management – The application of knowledge, skills, tools, and techniques to project activities to meet project requirements

Project manager – An individual who is an expert in project planning and management, defines and develops the project plan, and tracks the plan to ensure the project is completed on time and on budget

IS 312 : Lecture 8

22

Managing Software Development Projects . . .

Project deliverable – Any measurable, tangible, verifiable outcome, result, or item that is produced to complete a project or part of a project

Project milestone – Represents key dates when a certain group of activities must be performed

Project management office (PMO) – An internal department that oversees all organizational projects

IS 312 : Lecture 8

23

PROJECT CONSTRAINTS

IS 312 : Lecture 8

24

The Triple Constraint Benjamin Franklin’s timeless advice - by failing to

prepare, you prepare to fail - applies to software development projects

The Hackett Group analyzed 2,000 companies and discovered

• Three in 10 major IT projects fail

• 21 percent of the companies state that they cannot adjust rapidly to market changes

• One in four validates a business case for IT projects after completion

IS 312 : Lecture 8

25

PROJECT PARTICIPANTS Project stakeholders - Individuals and organizations

actively involved in the project or whose interests might be affected as a result of project execution or project completion

• Owner (What information system can provide)

• User (What tasks to be done)

• Designer (What to do to build system, How IT do it)

• Developer (Build system according to specs)

Executive sponsor - The person or group who provides the financial resources for the project

IS 312 : Lecture 8

26

User Requirement Discovery: What the system should do to assist users

User Participation: Develop “system ownership”: the system is theirs

User Acceptance: The system does what users need effectively, efficiently

User Satisfaction: The success of a system !!!

Role of Users in Systems Development Process

IS 312 : Lecture 8

27

Project Management Role

IS 312 : Lecture 8

28

CHOOSING STRATEGIC PROJECTS

Three common techniques for selecting projects

1. Focus on organizational goals (vision, strategy)

2. Categorize projects (visibility, urgency, benefit)

3. Perform a financial analysis (cost/benefit)

IS 312 : Lecture 8

29

Understanding Project Planning

After selecting strategic projects and identifying a project manager the next critical component is the project plan

Building a project plan involves two key components

• Project charter

• Project plan

IS 312 : Lecture 8

30

Understanding Project Planning . . .

Project charter - A document issued by the project initiator or sponsor that formally authorizes the existence of a project and provides the project manager with the authority to apply organizational resources to project activities and includes• Project scope statement

• Project objectives

• Project constraints

• Projects assumptions

IS 312 : Lecture 8

31


SMART criteria are useful reminders on how to ensure that the project has created understandable and measurable objectives

IS 312 : Lecture 8

32


Project plan – A formal, approved document that manages and controls project execution

A well-defined project plan should be

• Easy to understand and read

• Communicated to all key participants

• Appropriate to the project’s size, complexity, and criticality

• Prepared by the team, rather than by the individual project manager

IS 312 : Lecture 8

33

MANAGING PROJECTS

Managing a project includes

• Identifying requirements

• Establishing clear and achievable objectives.

• Balancing the competing demands of quality, scope, time, and cost

• Adapting the specifications, plans, and approach to the different concerns and expectations of the various stakeholders

IS 312 : Lecture 8

34

In-Sourcing Vs. Outsourcing Projects

In-sourcing (in-house-development) –Uses the professional expertise within an organization to develop and maintain its information technology systems

Outsourcing – An arrangement by which one organization provides a service or services for another organization that chooses not to perform them in-house

IS 312 : Lecture 8

35

Outsourcing Projects Factors driving outsourcing growth include

• Core competencies

• Financial savings

• Rapid growth

• The Internet and globalization

IS 312 : Lecture 8

36

Outsourcing Projects

Onshore outsourcing

Nearshore outsourcing

Offshore outsourcing

IS 312 : Lecture 8

37

Outsourcing Benefits Outsourcing benefits include

• Increased quality and efficiency of business processes

• Reduced operating expenses for head count and exposure to risk for large capital investments

• Access to outsourcing service provider’s expertise, economies of scale, best practices, and advanced technologies

• Increased flexibility for faster response to market changes and less time to market for new products or services

IS 312 : Lecture 8

38

Outsourcing Challenges Outsourcing challenges include

• Length of contract

1. Difficulties in getting out of a contract

2. Problems in foreseeing future needs

3. Problems in reforming an internal IT department after the contract is finished

• Threat to competitive advantage

• Loss of confidentiality

IS 312 : Lecture 8

39

Project Management Failure

Lack of sufficient planning Problems with technology compatibility Lack of commitment by management

providing necessary resources Poorly defined project scope Lack of sufficient time to complete the

project

IS 312 : Lecture 8

40

Planning for and Justifying Applications

Organizations must analyze the need for the IT application.

Each IT application must be justified in terms of costs and benefits.

The application portfolio

IS 312 : Lecture 8

41

Information Systems Planning Process

IS 312 : Lecture 8

42

SYSTEMS DEVELOPMENT LIFE CYCLE

(SDLC)Overview

( IS 312, IS 431 , IS 531, IS 630 , IS 655 )

IS 312 : Lecture 8

43

Where Do Systems Development Projects Come From?

Problem – an actual undesirable situation that prevents the organization from fully achieving its purpose, goals, and/or objectives.

Opportunity – a chance to improve the organization even in the absence of an identified problem.

Directive - a new requirement that is imposed by management, government, or some external influence/parties.

IS 312 : Lecture 8

44

System Analysis & Design Approaches in a Nutshell

DEVELOPMENT

•Modeling

•Prototyping (RAD)

IMPLEMENTATION

•Build (In-house)

•Buy (COTS)

IS 312 : Lecture 8

45

1. Identify an IT problem to solve

2. Break the large problem into several smaller, more manageable units

3. Translate each unit (small problem) into computer programs

4. Piece together each program into an overall comprehensive IS that solves the problem

System Construction Process

IS 312 : Lecture 8

46

System Construction Process…

IS 312 : Lecture 8

47

Strategies for Acquiring IT Applications

Buy the applications (off-the-shelf approach)

Lease the applications Software-as-a-Service (Cloud Computing) Use Open-Source Software Outsourcing Developing the applications in-house

IS 312 : Lecture 8

48

1. System Identification, Selection, and Planning

2. System Analysis3. System Design4. System Implementation5. System Maintenance

SYSTEMS DEVELOPMENT PROCESS

IS 312 : Lecture 8

49

Systems Development Process Scope Definition Phase

• What Business Problem Analysis Phase

• What System Issues (Info / Data, Processes, Communications / Interfaces),

• What User Needs,

• What to Do - Conceptual Model

• What Solution Design Phase

• How to Do - Physical Model Implementation / MaintenancePhase

• Do it, use it, keep it good

IS 312 : Lecture 8

50

Systems Development Life Cycle …

IS 312 : Lecture 8

51

Systems Development Life Cycle in Practice

IS 312 : Lecture 8

52

Phase 1: System Identification, Selection, and Planning

IS 312 : Lecture 8

53

• Undertake only those projects critical to mission, goals, and objectives

• Select a development project from all possible projects that could be performed

• Different evaluation criteria used to rank potential projects

Phase 1: System Identification, Selection, and Planning

IS 312 : Lecture 8

54

Evaluation criteriaStrategic alignmentPotential benefitsPotential costs and resource

availabilityProject size / durationTechnical difficulty / risks

Phase 1: System Identification, Selection, and Planning . . .

IS 312 : Lecture 8

55

Evaluation Criteria

IS 312 : Lecture 8

56

Phase 2: Systems Analysis

IS 312 : Lecture 8

57

Requirements collection

• Interviews

• Questionnaires

• Observations

• Document analysisCritical Success Factors (CSF)Joint Application Design (JAD)

Phase 2: System Analysis . . .

IS 312 : Lecture 8

58

Pros & Cons of CSF

IS 312 : Lecture 8

59

Pros & Cons of JAD

IS 312 : Lecture 8

60

Modeling Organizational Data

• Entity Relationship Diagram (ERD) Modeling Organizational Processes

and Logic

• Data Flow Diagram (DFD)

• Processing Logic

Phase 2: System Analysis . . .

IS 312 : Lecture 8

61

A Process Model

IS 312 : Lecture 8

62

A Data Model

IS 312 : Lecture 8

63

Phase 3: System Design

IS 312 : Lecture 8

64

Designing forms and reports

Designing interfaces and dialogues Designing databases and files Designing processing and logic

Phase 3: System Design . . .

IS 312 : Lecture 8

65

Phase 4: System Implementation

IS 312 : Lecture 8

66

Software programming Software testing

• Developmental (check program logic)

• Alpha testing (simulated data)

• Beta testing (real data)

Phase 4: System Implementation . . .

IS 312 : Lecture 8

67

System Testing

IS 312 : Lecture 8

68

System conversion• Parallel• Direct / Cut-off• Phased• Pilot

System documentation, training, and support• User and reference guides• Training and tutorials• Installation procedures and troubleshooting

guides

Phase 4: System Implementation . . .

IS 312 : Lecture 8

69

System Conversion

IS 312 : Lecture 8

70

Conversion Strategies

Risk

Cost

DirectConversion

LocationConversion

PhasedConversion

ParallelConversion

IS 312 : Lecture 8

71

User Training

IS 312 : Lecture 8

72

Maintenance process steps:1. Obtain maintenance request

2. Transform requests into changes

3. Design changes

4. Implement changes

Phase 5: System Maintenance . . .

IS 312 : Lecture 8

73


IS 312 : Lecture 8

74

Maintenance types:1. Corrective maintenance

2. Adaptive maintenance

3. Perfective maintenance

4. Preventive maintenance


IS 312 : Lecture 8

75

Software Maintenance

IS 312 : Lecture 8

76

1. Limited IS staff

2. IS staff has limited skill set

3. IS staff is overworked

4. Problems with performance of IS staff

5. Reinvent the wheel (Common business functions)

Need for Alternatives to In-house Development

IS 312 : Lecture 8

77

Commercial Off-the-Shelf Software Advantages

• Fast implementation of new system (many functions are similar across businesses, no need to build them from scratch.)

• No need for expertise and staff for in-house development

• Low development costs (but expensive to customize and implement !!!)

• Vendors are responsible for software improvements and error corrections

IS 312 : Lecture 8

78

Disadvantages

• Dependent on the vendors

• Future upgrade/customization is expensive

• A COTS rarely reflects ideal solution developed in-house

• Changing current business processes to fit the COTS

Commercial Off-the-Shelf Software . . .

IS 312 : Lecture 8

79

System Proposal & Project Management

Feasibility Analysis Alternative (Candidate) System

Solutions. Cost-benefit Analysis System Proposal Reports Project Management

IS 312 : Lecture 8

80

Feasibility Analysis

• Feasibility is the measure of how beneficial or practical the development of an information system will be to an organization. • Creeping Commitment : feasibility should be measured throughout the life cycle as project scope expands over times.

IS 312 : Lecture 8

81

Feasibility Analysis …

Technical feasibility is a measure of the practicality of a specific technical solution and the availability of technical resources and expertise.

Operational feasibility is a measure of how well the solution will work in the organization. It is also a measure of how people feel about the system/project.

Economic feasibility is a measure of the cost-effectiveness of a project or solution.

Schedule feasibility is a measure of how reasonable the project timetable is.

IS 312 : Lecture 8

82

Cost-Benefit AnalysisCosts: Development costs are one time costs that will not recur after

the project has been completed. Operating costs are costs that tend to recur throughout the

lifetime of the system. Such costs can be classified as:

• Fixed costs — occur at regular intervals but at relatively fixed rates.

• Variable costs — occur in proportion to some usage factor.

Benefits: Tangible benefits are those that can be easily quantified. Intangible benefits are those benefits believed to be difficult or

impossible to quantify.

IS 312 : Lecture 8

83

Costs for a Proposed Systems Solution

IS 312 : Lecture 8

84

Economic Feasibility Payback Analysis

• Payback analysis is to determine if and when an investment will pay for itself.

• Payback period is the period of time that will lapse before accrued benefits overtake accrued and continuing costs.

Net Present Value• a dollar today is worth more than a dollar one

year from now• Discount rate – a percentage that the business

earns on investing money in other projects or investments: opportunity cost

IS 312 : Lecture 8

85

Economic Feasibility … Return-on-Investment (ROI) Analysis – a

technique that compares the lifetime profitability of alternative solutions.• ROI for a solution or project is a percentage rate

that measures the relationship between the amount the business gets back from an investment and the amount invested.

• Lifetime ROI = (estimated lifetime benefits – estimated lifetime costs) / estimated lifetime costs

• Annual ROI = lifetime ROI / lifetime of the system

IS 312 : Lecture 8

86

Candidate Systems Matrix Characteristics

Portion of System ComputerizedBrief description of that portion of the system that would be computerized in this candidate.

BenefitsBrief description of the business benefits that would be realized for this candidate.

Servers and WorkstationsA description of the servers and workstations needed to support this candidate.

Software Tools NeededSoftware tools needed to design and build the candidate (e.g., database management system, emulators, operating systems, languages, etc.). Not generally applicable if applications software packages are to be purchased.

Candidate 1

COTS package from Software Solutions would be purchased and customized to satisfy required functionality.

This solution can be implemented quickly because it’s a purchased solution.

Technically architecture dictates Pentium III, MS Windows 2000 class servers and workstations (clients).

MS Visual C++ and MS Access for customization of package to provide report writing and integration.

Candidate 2

Member Services and warehouse operations in relation to order fulfillment.

Fully supports user required business processes for more efficient interaction with member accounts.

Same as candidate 1.

MS Visual Basic 5.0System Architect 2001Internet Explorer

Candidate 3




MS Visual Basic 5.0System Architect 2001Internet Explorer

IS 312 : Lecture 8

87

Candidate Systems Matrix …Characteristics

Application SoftwareA description of the software to be purchased, built, accessed, or some combination of these techniques.Method of Data ProcessingGenerally some combination of: on-line, batch, deferred batch, remote batch, and real-time.

Output Devices and ImplicationsA description of output devices that would be used, special output requirements, (e.g., network, preprinted forms, etc.), and output considerations (e.g., timing constratints)

Candidate 1

Package solution

Client/Server

(2) HP4MV department laser printers(2) HP5SI LAN laser printers

Candidate 2

Custom solution


(2) HP4MV department laser printers.(2) HP5SI LAN laser printers(1) PRINTRONIX bar-code printer (includes software & drivers)

Web pages must be designed to VGA resolution. All internal screens will be designed for SVGA resolution.

Candidate 3




IS 312 : Lecture 8

88

Candidate Systems Matrix …

Characteristics

Input devices and ImplicationsA description of input methods to be used, input devices (e.g., keyboard, mouse, etc.), special input requirements (e.g., new or revised forms from which data would be input), and input considerations (e.g., timing of actual inputs).

Storage Devices and ImplicationsBrief description of what data would be stored, what data would be accessed from existing stores, what storage media would be used, how much storage capacity would be needed, and how data would be organized.

Candidate 1

Keyboard & mouse.

MS SQL Server DBMS with 1000GB arrayed capability.

Candidate 2

Apple “Quick Take” digital camera and software(15) PSC Quickscan laser bar-code scanners(1) HP Scanjet 4C Flatbed ScannerKeyboard and mouse


Candidate 3



IS 312 : Lecture 8

89

Feasibility Matrix

IS 312 : Lecture 8

90

Scheduling Strategies

Forward Scheduling – a project scheduling approach that establishes a project start date and then schedules forward from that date.

Reverse Scheduling – a project scheduling strategy that establishes a project deadline and then schedules backward from that date.

IS 312 : Lecture 8

91

PERT Chart

5-3-2001 5-12-2001

5-3-2001 5-11-2001

Preliminary Investigation

5-12-2001 6-12-2001

5-12-2001 6-14-2001

Problem Analysis

5-28-2001 7-15-2001

5-30-2001 7-18-2001

Requirements Analysis

6-13-2001 7-30-2001

6-13-2001 8-3-2001

Decision Analysis

9-10-2001 12-14-2001

TBD TBD

Implementation

7-19-2001 11-13-2001

7-20-2001 In Progress

Construction

7-3-2001 9-25-2001

7-5-2001 10-9-2001

Design

5-3-2001 N/A

5-3-2001 N/A

Project Initiation

ScheduledStart

ScheduledFinish

Actual Start ActualFinish

Task

ScheduledStart

ScheduledFinish

Actual Start ActualFinish

Task

intertaskdependency

Legend

IS 312 : Lecture 8

92

Critical Path

The critical path is highlighted in red

TASK C

Fri 2/9/01 2 days

Fri 2/9/01 0 days

TASK D

Tue 2/20/01 7 days

Tue 2/20/01 0 days

TASK I

Tue 2/27/01 5 days

Tue 2/27/01 0 days

TASK E

Mon 2/19/01 6 days

Tue 2/20/01 1 day

TASK B

Wed 2/7/01 2 days

Wed 2/7/01 0 days

TASK A

Mon 2/5/01 3 days

Mon 2/5/01 0 days

TASK H

Thu 2/15/01 1 day

Tue 2/20/01 3 days

TASK F

Wed 2/14/01 3 days

Fri 2/16/01 2 days

TASK G

Fri 2/16/01 2 days

Tue 2/20/01 2 days

Duration

Slack Time

IS 312 : Lecture 8

93

Gantt Chart

Incomplete Task

Complete Task

Legend

ID

1

2

3

4

5

6

7

Preliminary investigation

Problem analysis

Requirements analysis

Decision analysis

Design

Construction

Implementation

May Jun Jul Aug Sep Oct Nov Dec

2001Task Name

Today

IS 312 : Lecture 8

94

Measures of Project Success

• The resulting information system is acceptable to the customer.

• The system was delivered “on time.”

• The system was delivered “within budget.”

• The system development process had a minimal impact on ongoing business operations.

IS 312 : Lecture 8

95

System Proposal

CSUN Information Systems dn58412/IS312/IS312_SP15.htm IS312 Information Systems for Business Lecture...

Documents

Transcript of CSUN Information Systems dn58412/IS312/IS312_SP15.htm IS312 Information Systems for Business Lecture...