1 / 47

Pertemuan – 17-18

Pertemuan – 17-18. Matakuliah : M0304/Corporate Information System Management Tahun : 2008. M ETODOLOGI P ENGEMBANGAN S OFTWARE M ANDIRI. S YSTEMS D EVELOPMENT L IFE C YCLE M ETHODOLOGY.

kasi
Download Presentation

Pertemuan – 17-18

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Pertemuan – 17-18 Matakuliah : M0304/Corporate Information System Management Tahun : 2008

  2. METODOLOGI PENGEMBANGAN SOFTWARE MANDIRI

  3. SYSTEMS DEVELOPMENT LIFE CYCLE METHODOLOGY Systems development life cycle (SDLC) – a highly structured approach for development of new customized software applications

  4. SYSTEMS DEVELOPMENT LIFE CYCLE METHODOLOGY The SDLC Steps Key characteristic is extensive formal reviews required at end of each major step Figure 17.1 The Systems Development Life Cycle

  5. SYSTEMS DEVELOPMENT LIFE CYCLE METHODOLOGY The SDLC Steps Hallmark of SDLC approach: extensive up-front time spent determining requirements to avoid expensive changes later Figure 17.2 Cost Breakdown for $1 Million SDLC Project

  6. SYSTEMS DEVELOPMENT LIFE CYCLE METHODOLOGY The SDLC Steps SDLC: • Most often requires a lot of documentation • Outputs from one step inputs to next • Often referred to as the “waterfall” model

  7. SYSTEMS DEVELOPMENT LIFE CYCLE METHODOLOGY Definition Phase – Requirements Definition • Focuses on logical design: processes, data flows, and data interrelationships – not specific physical implementation • Deliverable – system requirements document: • Detailed descriptions of inputs and outputs, processes used to convert input data to outputs • Formal diagrams and output layouts • Revised cost/benefit analysis • Revised plan for remainder of project

  8. SYSTEMS DEVELOPMENT LIFE CYCLE METHODOLOGY Construction Phase • System Design • System Building • System Testing Documentation is a major mechanism of communication during development process Figure 17.3 Characteristics of High Quality Systems

  9. SYSTEMS DEVELOPMENT LIFE CYCLE METHODOLOGY Implementation Phase • Installation • Operations • Maintenance

  10. Implementation Phase – Installation Parallel Strategy Parallel Strategy Parallel Strategy Parallel Strategy Figure 17.4 Implementation Strategies

  11. Implementation Phase – Maintenance Figure 17.5 Percent of Development Resources Devoted to Maintenance

  12. Implementation Phase – Maintenance Figure 17.6 The Widening Gap Between Organization’s Needs and System’s Performance

  13. SYSTEMS DEVELOPMENT LIFE CYCLE METHODOLOGY The SDLC Project Team • Usually temporary • Includes personnel from IS and business units • Has a project manager • Traditionally from IS • Can be from business unit • May be one from each • Responsible for success of project – delivering quality system on time and within budget

  14. SYSTEMS DEVELOPMENT LIFE CYCLE METHODOLOGY The SDLC Project Team • Includes systems analysts • Have critical roles • Work closely with business managers and end users • Have problem-solving skills, knowledge of IT capabilities, strong business understanding • Has a business sponsor and a champion

  15. SYSTEMS DEVELOPMENT LIFE CYCLE METHODOLOGY Managing an SDLC Project • Characteristics critical for success: • Manageable project size • Accurate requirements definition • Executive sponsorship

  16. SYSTEMS DEVELOPMENT LIFE CYCLE METHODOLOGY Managing an SDLC Project (Adapted from Boehm, 1976) Figure 17.7 Costs of Error Correction by SDLC Step

  17. SYSTEMS DEVELOPMENT LIFE CYCLE METHODOLOGY SDLC Advantages and Disadvantages Figure 17.8 Advantages and Disadvantages of Traditional SDLC Approach

  18. PROTOTYPING METHODOLOGY • Prototyping approach: • Takes advantage of availability of fourth generation procedural languages and relational database management systems • Enables creation of system (or part of system) more quickly, then revise after users have tried it • Is a type of evolutionarydevelopment process

  19. PROTOTYPING METHODOLOGY • Prototyping examples: • Input and output screens developed for users to test as part of requirements definition • “First-of-a-series” – a completely operational prototype used as a pilot • “Selected features” – only some essential features included in prototype, more added later • Prototyping used as a completealternative to traditional SDLC methodology

  20. PROTOTYPING METHODOLOGY • Prototyping used as a completealternative to traditional SDLC methodology: • Good when requirements hard to define • Good when system needed quickly • Impractical for large, complex applications

  21. The Prototyping Steps Figure 17.9 The Prototyping Life Cycle

  22. PROTOTYPING METHODOLOGY The Prototyping Project Team • Representatives from IS and user management necessary • Need team members who can quickly build systems using advanced tools • Requires dedicated business user roles

  23. PROTOTYPING METHODOLOGY Prototyping Advantages and Disadvantages • Advantages: • Only basic requirements needed at front end • Used to develop systems that radically change how work is done, so users can evaluate • Allows firms to explore use of new technology • Working system available for testing more quickly • Less strong top-down commitment needed at front end • Costs and benefits can be derived after experience with initial prototype • Initial user acceptance likely higher

  24. PROTOTYPING METHODOLOGY Prototyping Advantages and Disadvantages • Disadvantages: • End prototype often lacks security and control features • May not undergo as rigorous testing • Final documentation may be less complete • More difficult to manage user expectations

  25. PROTOTYPING METHODOLOGY Prototyping within an SDLC Process Figure 17.10 SDLC with Prototyping to Define Requirements

  26. PROTOTYPING METHODOLOGY Prototyping within an SDLC Process Figure 17.11 Prototyping/Piloting Replaces SDLC Definition Phase

  27. NEWER APPROACHES Rapid Application Development (RAD) • Hybrid methodology – aspects of SDLC and prototyping • Goal is to produce a system in less than a year Figure 17.12 Four-Step RAD Cycle

  28. NEWER APPROACHES Rapid Application Development (RAD) Joint application design (JAD) – a technique in which a team of users and IS specialists engage in an intense and structured process in order to minimize the total time required for gathering information from multiple participants

  29. NEWER APPROACHES Rapid Application Development (RAD) Joint application design (JAD) – a technique in which a team of users and IS specialists engage in an intense and structured process in order to minimize the total time required for gathering information from multiple participants Computer-aided software engineering (CASE) – any software tool used to automate one or more steps of a software development methodology

  30. NEWER APPROACHES Rapid Application Development (RAD) (Adapted from Valacich, George, and Hoffer, 2001) Figure 17.13 Types of CASE Tools

  31. NEWER APPROACHES Rapid Application Development (RAD) Figure 17.14 RAD Advantages and Disadvantages

  32. NEWER APPROACHES Agile Software Development Discipline • Alternative methodology for smaller projects • Based on four key values: • Simplicity • Communication • Feedback • Courage • One type: Extreme Programming (XP) • Programmers write code in pairs • Use simple design and frequent testing

  33. MANAGING SOFTWARE PROJECTS USING OUTSOURCED STAFF • Advantages: • Helps keep software development costs down • Uses technical expertise not available in-house • Can often complete projects more quickly • Off-site outsourcing: • Onshore – within same country or region • Offshore – not within same country or region

  34. MANAGING SOFTWARE PROJECTS USING OUTSOURCED STAFF • Offshore alternative good option when: • System requirements well-defined and remain stable • Time is of essence and 7x24 hour availability of resources a good idea • Cost of project important

  35. MANAGING SOFTWARE PROJECTS USING OUTSOURCED STAFF • Guidelines for managing offsite outsourcer: • Manage expectations, not staff • Take explicit actions to integrate the offsite workers • Communicate frequently • Abandoning informal ways may result in increased rigor

  36. Prosedure Outsource • Reff-Haag

  37. OUTSOURCING • Developing strategic partnerships • Outsourcing - the delegation of specific work to a third party for a specified length of time, at a specified cost, and at a specified level of service

  38. Developing Strategic Partnerships

  39. Developing Strategic Partnerships • IT outsourcing takes on 1 of 4 forms: • Purchasing existing software • Purchasing existing software and pay the publisher to make certain modifications • Purchasing existing software and pay the publisher for the right to make modifications yourself • Outsourcing the development of an entirely new and unique system for which no software exists

  40. The Outsourcing Process

  41. The Outsourcing Process • Steps of the outsourcing process • Planning • Define project scope • Select a target system • Establish logical requirements

  42. The Outsourcing Process • Develop a request for proposal • Request for proposal (RFP) - a formal document that describes in detail your logical requirements for a proposed system and invites outsourcing organizations to submit bids for its development • Evaluate request for proposal returns and choose a vendor • Test and accept solution • Monitor and reevaluate

  43. The Outsourcing Process – an RFP

  44. Offshore Outsourcing • Offshore outsourcing - using organizations from other countries to write code and develop systems

  45. The Advantages of Outsourcing • Focus on unique core competencies • Exploit the intellect of another organization • Better predict future costs • Acquire leading-edge technology • Reduce costs • Improve performance accountability

  46. The Disadvantages of Outsourcing • Reduces technical know-how for future innovation • Reduces degree of control • Increases vulnerability of strategic information • Increases dependency on other organizations

More Related