Chapter 5
Upcoming SlideShare
Loading in...5
×
 

Chapter 5

on

  • 417 views

 

Statistics

Views

Total Views
417
Views on SlideShare
417
Embed Views
0

Actions

Likes
0
Downloads
1
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Chapter 5 Chapter 5 Presentation Transcript

    • IT 215 Analysis and Design Techniques
    • 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
    • Overview
      • Choices Today vs. Yesterday
      • Packages vs. Custom
      • In-House vs. Outsource
      • On-Shore vs. Off-Shore
      • Other
    • Web-Based Software Trends
      • Software as Service
      • Changing Marketplace
      • Internet Impact
    • Outsourcing
      • Growth
      • Fees
      • Issues
      • Concerns
    • In-House
      • Make vs. Buy
      • In-House Development
      • Package Purchase
      • Customization
      • User Applications
    •  
    •  
    • Role of Analyst
      • Company Decisions
      • Make/Buy
      • In/Out
      • Package/Custom
      • Mix
    • Software Acquisition
      • Evaluate Requirements
      • Identify Options
      • Evaluate Alternatives
      • Cost/Benefit Analysis
      • Recommendation
      • Implement
    • Financial Analysis Tools
      • Payback Analysis
      • Return on Investment
      • Net Present Value
    • 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
    • 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
    • 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
    • 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)
    •  
    •  
    • 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
    • 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
    • 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
    • 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
    • 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 system’s format
    • Completion of Analysis Tasks
      • Requirements document
      • Presentation
    • Transition to Design
      • Preparation
      • Logical vs. Physical Design
    • Design Guidelines
      • Objectives
      • Trade-Offs
    •  
    •  
    • Prototyping
      • Methods
      • Tools
      • Limitations
      • Other Modeling Tools
    •  
    •  
    •  
    •  
    •  
    • Codes During Design
      • Overview
      • Types
      • Development
    •  
    • 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
    • Using Codes During System Design
      • Types of Codes
        • Sequence codes
        • Block sequence codes
        • Alphabetic codes
          • Category codes
          • Abbreviation codes
    • Using Codes During System Design
      • Types of codes
        • Significant digit codes
        • Derivation codes
        • Cipher codes
        • Action codes
        • Self-checking codes
    • 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
    • Using Codes During System Design
      • Developing a Code
        • Make codes meaningful
        • Use a code for a single purpose
        • Keep codes consistent