Uploaded on

 

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
135
On Slideshare
0
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
2
Comments
0
Likes
0

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. ISM 4113 Chapter 8 Analysis to Design
  • 2. From What to How Physical Physical Logical Logical Current System New System “ What” “ How” 1 2 3 4 5 We are here
  • 3. The Geometric Truth Cheap Now Right Emphasizing quality generally diminishes the likelihood of cost minimization and fast delivery. Emphasizing cost minimization or delivery time generally diminishes the quality. Emphasizing quality and delivery generally diminishes the likelihood of significant cost minimization.
  • 4. Where are we in SDLC
    • Physical Design
      • Don’t get confused we are not here yet in NOMAS
    • Deliverables:
      • Detailed Spec of new system
      • Formal feasibility analysis
  • 5. Transition From Logical to Physical Design Prepare a detailed development plan for the physical design Identify a physical design which meets the requirements Document the physical design in detail Assess the feasibility of the physical design across all dimensions Recommend based on the outcome of the feasibility assessment
  • 6. Selecting a Design Strategy
    • Alternative Solutions
      • Do Nothing!
      • Non-Automated Solution
      • Buy vs. Make
        • Commercial off the shelf (COTS)
        • Develop system from scratch
        • Outsource IS solution
      • Don’t forget about Hardware
  • 7. Evaluating a COTS Solution Evaluation Criteria Characteristics   Application Efficiency
    • Acceptable response times under actual conditions
    • Efficient use of a wide variety of data storage solutions
    • Efficient use of backup and recovery mechanisms
    •  
      Application Effectiveness
    • Meets all stated requirements for the present process needs
    • Expandable & scalable to expected future needs & platform requirements
    • Logical organization of menus and data capture screens
    • Capacity for current and expected future user load
    •  
      Usability
    • Functional and logical user interface
    • Context-sensitive online help system
    • Appropriate user feedback with regard to application processes and user error
    • Non-destructive error recovery from command or menu selection errors
    •  
      Documentation
    • Well-organized and comprehensive written user documentation
    • Complete duplication of all documentation in online form
    • Comprehensive user tutorials for all application functions
    •  
      Vendor Support
    • Telephone technical support with direct access to technicians
    • Web-based support site with downloadable updates
    • Searchable web-based technical support knowledge base for first line solutions
    •  
  • 8. Evaluating Outsourcing     Terms of reference document that sets out the objectives, scope and approach of the evaluation Strategic business plan (where does the organization want to be?) Analysis of how outsourcing integrates with the purchaser's strategic plan Business analysis and feasibility study (the high level requirements and how the process would work) Human resources impact assessment (may require the assistance of employment law specialists at an early stage) Request for information (RFI) (seeking suitable services and indicative costs) Cost-benefit analysis (what are the economics?) Risk analysis and business impact (what are the risks?) Business case and recommendation to management Specification of requirements (detailed statement of services and service levels required) Call for proposals from suppliers known as a request for proposal (RFP) Evaluation of proposals  
  • 9. Remember Bounded Rationality
    • The Feasible Solution
      • For every problem there are many solutions
      • Some are good
      • Only one is BEST
        • Best = Feasible?
    • Feasible Defined:
      • A solution that solves the identified problem or maximizes the … opportunity without causing any problems that were not in existence before its implementation.
  • 10. 3 Ways to Make a Business Case Facts Faith Fear
    • “ The system will have a net present value of $753,000.”
    • “ The system will yield a minimum reduction in operating cost of $193,000 annually.”
    • “ The estimated increase in market share is 14.7%.” within the first 24 months of operation.”
    • “ IT is part of the infrastructure, we can’t cost justify it like a new fleet of trucks.”
    • “ It seems reasonable to assume that this new system will reduce our costs of servicing this market sector.”
    • “ Trust me. This is why you hired me as the IT Director.”
    • “ Our competitors are doing this even as we speak.”
    • “ Our shareholders will view us as technologically behind if we don’t do this now.”
    • “ We have a small window of opportunity here and we are wasting precious time trying to decide.”
  • 11. Feasibility Dimensions
    • Technical
    • Operational
    • Human Factors
    • Legal & Political
    • Economic
  • 12. Technical
    • Technology must be sufficient for proposed solution
      • Is the technology necessary for the proposed solution practical to obtain?
      • Do we currently possess the technology necessary to implement the proposed solution?
      • Is the technology necessary to implement the proposed solution available now and has it been tested and proved?
  • 13. Vaporware, Beware!
  • 14. Operational
    • Solution must “fit” within the organization and be accepted by end-users
      • Does the solution fit with the organizations IS Plan?
      • How does the implementation schedule fit with the other organization projects?
      • Are the necessary resources available to complete the proposed solution?
      • What impact can we expect if we adopt this proposed solution?
  • 15. Human Factors
    • Usability
      • Ease of use
        • How easy is the system within the context of your day-to-day activities
      • Perceived usefulness
        • Does the system conform to the needs of your job
      • Overall satisfaction
        • Are you pleased with the system in general
    • End-user training
      • When should this start?
      • Too early and …
      • Too late and ...
  • 16. Legal & Political
    • Legal
      • Will the solution violate any law’s, treaties, etc.
    • Political
      • Change and reallocation of information (info=power) will cause people to resist change
      • Who might resist and what measures are in place to overcome this?
  • 17. Economic
    • Benefits > Cost (period!)
  • 18. Typical Tangible Benefits Benefit Category Common Examples   Cost Reduction     Reduction in labor or headcount Less paperwork Reduction or elimination of overtime Efficiencies in distribution Consolidation of jobs or employee roles Less need for travel Reduction in supply usage Less maintenance Smaller inventory needs or carrying costs Lower costs of hardware and/or software Increase in product/process quality Improved production throughput or costs Reduction in overall cost of funds Efficient use of utilities Improved subcontractor or external vendor control Reduction in or improved effectiveness of training     Revenue Increase     Introduction of new products Improved product quality Increased efficiency in sales processes Product enhancements Improved advertising support and target marketing Development of, or access to, new markets Decreased time to market Effective bidding tools  
  • 19. Typical Intangible Benefits
    • Improved employee morale
    • Improved corporate image
    • Increase in perceived quality of products or services
    • Perceived decrease in time to market by customers
    • Improved decision making
    • More timely information
    • Increased organizational flexibility
    • Improved resource allocation and control
    • Increased strategic or competitive advantage
    • Improved public and community relations
    • Improvements in addressing environmental concerns
    • Reduced employee turnover
    • Increased quality of work for employees
    • Proactive attention to ethical issues
    • Proactive addressing of legal issues
    • Increased workplace and/or community safety
  • 20. Typical System Costs Cost Category Common Examples   Tangible Development   Development personnel Data conversion costs Analysis and design consulting fees Pre-development training Vendor installation and consulting Materials and supplies Hiring costs for new operating personnel Hardware and software acquisition or development Physical plant acquisition and/or conversion     Tangible Operating     Maintenance and upgrades (hardware and software) End-user training Annual or renewable software licenses Operational personnel Repairs (hardware and software) Depreciation of system assets Connectivity and communication charges Materials and supplies Equipment lease payments       Intangible     Potential disruption to existing productivity and environment Loss of customer goodwill Reduction in employee morale Diversion of attention to daily responsibilities  
  • 21. Types of Economic Analysis
    • Net Present Value (NPV)
    • Internal Rate of Return (IRR)
      • Discount Rate that equates the PV of future cash flows to the Initial Cost
        • Discount Rate > Cost of Funds = Surplus for Project
        • Discount Rate < Cost of Funds = Deficit for Project
    • Return on Investment (ROI)
      • Net Cash Flow / Total Cost
    • Break-even Analysis
      • (Break-even year Cash flow – BE year cumulative Cash flow) / Break-even year Cash flow
  • 22. Breakeven Analysis
  • 23. Categories of Risk Category of Risk Examples of Risk   Project Size  
    •  
    • length of development schedule
    • number of members of development team
    • span of involvement across organizational business units
    • span of involvement across unrelated organizations
    • size of project as measured in number of applications or lines of code
    •  
      Project Structure  
    •  
    • degree to which development effort is new and/or innovative
    • extent of organizational or structural change required
    • overall managerial commitment to project
      Analysts  
    •  
    • familiarity with business environment
    • familiarity with proposed technologies
    • familiarity with similar project scopes and complexities
    •  
      End-users  
    •  
    • perception of end-users to necessity or relevance of new system
    • familiarity with system development process and change
    • familiarity with proposed system application environment
    •  
  • 24. Next Class UGH#4
    • Prepare a Cost Benefit Analysis using the following assumptions:
      • Net Benefit in Year 1 = 50,000
        • Benefit increases by $5000 each year.
      • One Time cost = 90,000
      • Recurring Costs = 25,000 each year
      • Discount rate = 10%
    • Determine the Following:
      • NPV
      • ROI
      • Break-Even Point
  • 25. For Next Class
    • Read Glass Article