Development Strategies

Slides:



Advertisements
Similar presentations
System Analysis and Design
Advertisements

Systems Analysis and Design 8th Edition
System Analysis and Design
Data and Process Modeling
Copyright © 2014 Pearson Education, Inc. 1 Managers from across organizations are involved in developing and acquiring information systems Chapter 5 -
Data and Process Modeling
Acquiring Information Systems and Applications
MSIS 110: Introduction to Computers; Instructor: S. Mathiyalakan1 Systems Design, Implementation, Maintenance, and Review Chapter 13.
Systems Analysis and Design 9th Edition
Chapter 5.
Fundamentals of Information Systems, Second Edition
Development Strategies
MSIS 110: Introduction to Computers; Instructor: S. Mathiyalakan1 Systems Investigation and Analysis Chapter 12.
PowerPoint Presentation by Charlie Cook Copyright © 2004 South-Western. All rights reserved. Chapter 7 System Design and Implementation System Design and.
Introduction to Systems Analysis and Design
Acquiring Information Systems and Applications
Acquiring Information Systems and Applications
PHASE 3: SYSTEMS DESIGN Chapter 8 System Architecture.
Chapter Objectives Describe software trends, including the concept of software as a service Explain software acquisition alternatives, including traditional.
Chapter 5 DEVELOPMENT STRATEGIES
Chapter 6 Home Page – Welcome! To navigate the slide presentation, use the navigation bar on the left OR use your right and left arrow keys. Move your.
1 Building and Maintaining Information Systems. 2 Opening Case: Yahoo! Store Allows small businesses to create their own online store – No programming.
SYS364 Evaluating Alternatives. Objectives of the Systems Analysis Phase determine, analyze, organize and document the requirements of a new information.
Prof. Mohammad Moizuddin
Moving into Design SYSTEMS ANALYSIS AND DESIGN, 6 TH EDITION DENNIS, WIXOM, AND ROTH © 2015 JOHN WILEY & SONS. ALL RIGHTS RESERVED. 1 Roberta M. Roth.
Systems Analysis & Design 7 th Edition Chapter 6.
11.1 © 2007 by Prentice Hall 11 Chapter Building Information Systems.
Information Systems Technology Ross Malaga "Part III - Building and Managing Information Systems" III 11 Copyright © 2005 Prentice Hall, Inc MANAGING.
Principles of Information Systems, Sixth Edition Systems Design, Implementation, Maintenance, and Review Chapter 13.
Acquiring Information Systems and Applications
Systems Analysis & Design (Sixth Edition) 1 Chapter 5 Development Strategies PHASE 2: SYSTEMS ANALYSIS.
Systems Analysis and Design 8 th Edition Chapter 7 Development Strategies.
SYSTEMS ANALYSIS AND DESIGN 8 TH EDITION Chapter 7 Development Strategies.
Accounting Information System By Rizwan Waheed M.Com 710.
CHAPTER 13 Acquiring Information Systems and Applications.
1 Chapter 1 Introduction to Accounting Information Systems Chapter 17 System Selection and System Design.
Systems Analysis and Design 10th Edition
Chapter 2 The Origins of Software Modern Systems Analysis and Design Fifth Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich.
Principles of Information Systems, Sixth Edition 1 Systems Design, Implementation, Maintenance, and Review Chapter 13.
Topic 5 Development Strategies.  Describe the concept of Software as a Service  Define Web 2.0 and cloud computing  Explain software acquisition alternatives,
1 BTEC HNC Systems Support Castle College 2007/8 Systems Analysis Lecture 8 Moving from Analysis to Design Design Strategies.
ITEC 275 Computer Networks – Switching, Routing, and WANs
Chapter 2 The Origins of Software
Systems Analysis and Design in a Changing World, Fifth Edition
Development Strategies
Chapter 8 Environments, Alternatives, and Decisions.
Building Information Systems
Dinesh Mirchandani University of Missouri – St. Louis
Fundamentals of Information Systems, Sixth Edition
Systems Analysis – ITEC 3155 Evaluating Alternatives for Requirements, Environment, and Implementation.
Building Information Systems
Chapter 2 The Sources of Software
Chapter 2 The Origins of Software
Systems analysis and design, 6th edition Dennis, wixom, and roth
Chapter 2 The Origins of Software
Chapter 2 The Origins of Software
Systems analysis and design, 6th edition Dennis, wixom, and roth
Modern Systems Analysis and Design Third Edition
Information Systems, Ninth Edition
Introduction to Systems Analysis and Design Stefano Moshi Memorial University College System Analysis & Design BIT
Purchasing a Solution Chapter 9.
MANAGING THE DEVELOPMENT AND PURCHASE OF INFORMATION SYSTEMS
Modern Systems Analysis and Design Third Edition
Chapter 11 Selecting the Best Alternative Design Strategy
Chapter 2 The Origins of Software
Modern Systems Analysis and Design Third Edition
Chapter 11 Selecting the Best Alternative Design Strategy
Modern Systems Analysis and Design Third Edition
Presentation transcript:

Development Strategies Chapter 7 Development Strategies

Introduction Chapter 7 describes the remaining activities in the systems analysis phase The chapter also describes the transition to systems design, prototyping, and systems design guidelines 4

Development Strategies Overview Selecting the best development path is an important decision that requires companies to consider three key topics The impact of the Internet Software outsourcing options In-house software development alternatives

The Impact of the Internet The Internet has triggered enormous changes in business methods and operations, and software acquisition is no exception This section examines a trend that views software as a service, the changing market-place for software, and how Web-based development compares to traditional methods

The Impact of the Internet Software as a Service The Software and Information Industry Association (SIIA) is an industry group that focuses on the digital economy SIIA believes that the concept of software as a service is redefining the way that companies develop and deploy their information systems Cloud computing would be an ultimate form of SaaS Web 2.0 Enable people to collaborate, interact, and share information more easily

The Impact of the Internet The Changing Software Marketplace In the traditional model, software vendors develop and sell application packages to customers In addition to traditional vendors, the marketplace now includes many forms of outsourcing, including application service providers and firms that offer Internet business services

The Impact of the Internet The Impact of the Internet on Systems Development Developers will focus on Web-based application development, where the Web becomes an integral part of the application rather than just a communication channel

The Impact of the Internet The Impact of the Internet on Systems Development Traditional development Systems design is influenced by compatibility issues Systems are designed to run on local and wide-area company networks Web-based features are treated as enhancements rather than core elements of the design

The Impact of the Internet The Impact of the Internet on Systems Development Web-based development Internet-based development treats the Web as the platform, rather than just a communication channel Easily scalable and hardware independent Treat software as a service, not a commodity Web-based software usually requires additional layers, called middleware, to communicate with existing software and legacy system

Salesforce.com: What is Cloud Computing? http://www.youtube.com/watch?v=ae_DKNwK_ms&feature=related

Outsourcing Can refer to relatively minor programming tasks, the rental of software from a service provider, the outsourcing of a basic business process (often called business process outsourcing, or BPO), or the handling of a company’s entire IT function

Outsourcing The Growth of Outsourcing Traditionally, firms outsourced IT tasks as a way of controlling costs and dealing with rapid technological change Outsourcing has become part of an overall IT strategy for many organizations

Outsourcing Outsourcing Fees A fixed fee model uses a set fee based on a specified level of service and user support A subscription model has a variable fee based on the number of users or workstations that have access to the application A usage model or transaction model charges a variable fee based on the volume of transactions or operations performed by the application

Outsourcing Outsourcing Issues and Concerns Mission-critical IT systems should be out-sourced only if the result is a cost-attractive, reliable, business solution that fits the company’s long-term business strategy Outsourcing can be especially attractive to a company whose volume fluctuates widely, Ex. 處理全國考試業務

Outsourcing Offshore Outsourcing Offshore outsourcing – global outsourcing Many firms are sending IT work overseas at an increasing rate Gartner, a leading IT research and consulting firm, predicts that by 2005 one in 10 IT jobs at U.S. IT companies and one in 20 at non-IT companies will move offshore Read “The World Is Flat”

In-House Software Development Options A company can choose to develop its own systems, or purchase, possibly customize, and implement a software package The most important consideration is total cost of ownership (TCO) Companies also develop user applications designed around commercial software packages, e.g. Excel, Word

In-House Software Development Options Make or Buy Decision (Fig. 7-10, p. 291) The choice between developing versus purchasing software often is called a make or buy, or build or buy decision Companies that develop software for sale are called software vendors Value-added reseller (VAR): add custom features on a commercial package

In-House Software Development Options Reasons for Developing Software In-House Satisfy unique business requirements Minimize changes in business procedures and policies Meet constraints of existing systems Meet constraints of existing technology Develop internal resources and capabilities

In-House Software Development Options Reasons for Purchasing a Software Package Lower costs Requires less time to implement Proven reliability and performance benchmarks Requires less technical development staff Future upgrades provided by the vendor Input from other companies

In-House Software Development Options Customizing a Software Package You can purchase a basic package that vendors will customize to suit your needs You can negotiate directly with the software vendor to make enhancements to meet your needs by paying for the changes You can purchase the package and make your own modifications, if this is permissible under the terms of the software license

Role of the Systems Analyst When selecting hardware and software, systems analysts often work as an evaluation and selection team The primary objective of the evaluation and selection team is to eliminate system alternatives that will not work, rank the system alternatives that will work, and present the viable alternatives to management for a final decision

The Software Acquisition Process Step 1: Evaluate the Information System Requirements Prepare a request for proposal or quotation Request for proposal (RFP) 系統建議邀約, P. 301 Evaluation model, P. 302 Request for quotation (RFQ) 報價書邀約:已知要買的東西, p. 303

The Software Acquisition Process Step 2: Identify Potential Vendors or Outsourcing Options The Internet is a primary marketplace Another approach is to work with a consulting firm Another resource is the Internet bulletin board system that contains thousands of forums, called newsgroups

The Software Acquisition Process Step 3: Evaluate the Alternatives Existing users Application testing Benchmarking – benchmark testing: ex. Testing the time needed to post 1,000 sales transactions Match each package against the RFP features and rank the choices

The Software Acquisition Process Step 4: Perform Cost-Benefit Analysis Identify and calculate TCO for each option you are considering When you purchase software, what you are buying is a software license If you purchase a software package, consider a supplemental maintenance agreement

The Software Acquisition Process Step 5: Prepare a Recommendation You should prepare a recommendation that evaluates and describes the alternatives, together with the costs, benefits, advantages, and disadvantages of each option At this point, you may be required to submit a formal system requirements document and deliver a presentation

The Software Acquisition Process Step 6: Implement the Solution Implementation tasks will depend on the solution selected Before the new software becomes operational, you must complete all implementation steps, including loading, configuring, and testing the software; training users; and converting data files to the new system’s format

Completion of Systems Analysis Tasks System Requirements Document The system requirements document, or software requirements specification, contains the requirements for the new system, describes the alternatives that were considered, and makes a specific recommendation to management Like a contract Format and organize it so it is easy to read and use

Completion of Systems Analysis Tasks Presentation to Management Begin your presentation with a brief overview of the purpose and primary objectives of the system project, the objectives of this presentation, and what decisions need to made Summarize the primary viable alternatives. For each alternative, describe the costs, advantages, and disadvantages

Completion of Systems Analysis Tasks Presentation to Management Explain why the evaluation and selection team chose the recommended alternative Allow time for discussion and for questions and answers Obtain a final decision from management or agree on a timetable for the next step in the process

Completion of Systems Analysis Tasks Presentation to Management Based on their decision, your next task will be one of the following Implement an outsourcing alternative Develop an in-house system Purchase or customize a software package Perform additional systems analysis work Stop all further work

The Transition to Systems Design If management decides to develop the system in-house, then the transition to the systems design phase begins Preparing for Systems Design Tasks It is essential to have an accurate and understandable system requirements document

The Transition to Systems Design The Relationship between Logical and Physical Design The logical design defines the functions and features of the system and the relationships among its components The physical design of an information system is a plan for the actual implementation of the system

Systems Design Guidelines The systems analyst must understand the logical design of the system before beginning the physical design of any one component Data design User interface Systems design specification

Systems Design Guidelines Systems Design Objectives The goal of systems design is to build a system that is effective, reliable, and maintainable Some considerations examples