IT 215

1
IT 215

• Analysis and Design Techniques

2
Chapter 5 Development Strategies

• Overview
• Web-Based Software Trends
• Outsourcing
• In-House
• Role of Analyst
• Software Acquisition

• Completion of Analysis Tasks
• Transition to Design
• Design Guidelines
• Prototyping
• Codes During Design

3
Overview

• Choices Today vs. Yesterday
• Packages vs. Custom
• In-House vs. Outsource
• On-Shore vs. Off-Shore
• Other

4
Web-Based Software Trends

• Software as Service
• Changing Marketplace
• Internet Impact

5
Outsourcing

• Growth
• Fees
• Issues
• Concerns

6
In-House

• Make vs. Buy
• In-House Development
• Package Purchase
• Customization
• User Applications

7
(No Transcript)
8
(No Transcript)
9
Role of Analyst

• Company Decisions
• Make/Buy
• In/Out
• Package/Custom
• Mix

10
Software Acquisition

• Evaluate Requirements
• Identify Options
• Evaluate Alternatives
• Cost/Benefit Analysis
• Recommendation
• Implement

11
Financial Analysis Tools

• Payback Analysis
• Return on Investment
• Net Present Value

12
Cost-Benefit Analysis

• Cost-Benefit Analysis Checklist
• List each development strategy being considered
• Identify all costs and benefits for each
  alternative. Be sure to indicate when costs will
  be incurred and benefits realized
• Consider future growth and the need for
  scalability
• Include support costs for hardware and software

13
Cost-Benefit Analysis

• Cost-Benefit Analysis Checklist
• Analyze various software licensing options,
  including fixed fees and formulas based on the
  number of users or transactions
• Apply the financial analysis tools to each
  alternative
• Study the results and prepare a report to
  management

14
A Software Acquisition Example

• Step 1 Evaluate the Information System
  Requirements
• Identify key features
• Consider network and web-related issues
• Estimate volume and future growth
• Specify hardware, software, or personnel
  constraints

15
A Software Acquisition Example

• Step 1 Evaluate the Information System
  Requirements
• Prepare a request for proposal or quotation
• Request for proposal (RFP)
• Evaluation model
• Request for quotation (RFQ)

16
(No Transcript)
17
(No Transcript)
18
A Software Acquisition Example

• 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
  systems that contains thousands of forums, called
  newsgroups

19
A Software Acquisition Example

• Step 3 Evaluate the Alternatives
• Existing users
• Application testing
• Benchmarks
• Match each package against the RFP features and
  rank the choices

20
A Software Acquisition Example

• 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
  maintenance agreement

21
A Software Acquisition Example

• Step 5 Prepare a Recommendation
• You should prepare a recommendation that contains
  your recommendation and lists 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

22
A Software Acquisition Example

• 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 systems format

23
Completion of Analysis Tasks

• Requirements document
• Presentation

24
Transition to Design

• Preparation
• Logical vs. Physical Design

25
Design Guidelines

• Objectives
• Trade-Offs

26
(No Transcript)
27
(No Transcript)
28
Prototyping

• Methods
• Tools
• Limitations
• Other Modeling Tools

29
(No Transcript)
30
(No Transcript)
31
(No Transcript)
32
(No Transcript)
33
(No Transcript)
34
Codes During Design

• Overview
• Types
• Development

35
(No Transcript)
36
Using Codes During System Design

• Overview of Codes
• Because codes often are used to represent data,
  you encounter them constantly in your everyday
  life
• They save storage space and costs, reduce
  transmission time, and decrease data entry time
• Can reduce data input errors

37
Using Codes During System Design

• Types of Codes
• Sequence codes
• Block sequence codes
• Alphabetic codes
• Category codes
• Abbreviation codes

38
Using Codes During System Design

• Types of codes
• Significant digit codes
• Derivation codes
• Cipher codes
• Action codes
• Self-checking codes

39
Using Codes During System Design

• Developing a Code
• Keep codes concise
• Allow for expansion
• Keep codes stable
• Make codes unique
• Use sortable codes
• Avoid confusing codes

40
Using Codes During System Design

• Developing a Code
• Make codes meaningful
• Use a code for a single purpose
• Keep codes consistent