slide1 n.
Skip this Video
Loading SlideShow in 5 Seconds..
Developing e-Business Solutions PowerPoint Presentation
Download Presentation
Developing e-Business Solutions

Developing e-Business Solutions

1 Vues Download Presentation
Télécharger la présentation

Developing e-Business Solutions

- - - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript

  1. 10 Developinge-BusinessSolutions

  2. Chapter 10 • Development Methods • Project Management • Change Management

  3. Chapter Objectives • Use the systems development process to simple business problems. • Identify the activities involved in the implementation of new information systems. • Identify several change management solutions for end user resistance to the implementation of new e-business applications.

  4. Key Terms • Project Management • On Demand or Self-service • Value on Investment

  5. Project Definition “Temporary undertaking to create a unique product or service with a defined start and end point and specific objectives that, when attained, signify completion.” Project Management Terms, J. Leroy Ward, ESI International, Arlington Virginia, 2000

  6. 3 Approaches • Systems Approach • Prototyping (RAD) • End User Development

  7. Define the Problem Develop Alternative Solutions Monitor and Evaluate Results Select the Solution Design the Solution Implement the Solution Systems Approach to Problem Solving

  8. Systems Investigation Product: Feasibility Study Understand the Business Problem or Opportunity Systems Analysis Product: Functional Requirements Develop an Information System Solution Systems Design Product: System Specifications Systems Implementation Product: Operational System Implement the Information System Solution Systems Maintenance Product: Improved System Traditional Systems Development Life Cycle

  9. Identify an End User's Information Requirements Develop Information System Prototypes Prototyping Cycle Revise the Prototypes to Better Meet End User Requirements Maintenance Cycle Use and Maintain the Accepted System Prototyping Process

  10. Controls What controls are needed? Processing What operations on the input is required? Input What data is required? Output What information is needed? Storage Will the application need to store data? End User Development

  11. Projects • Typically address a significant change in business requirements or in system architecture • Address a new business need, or needs which have changed significantly • Typically result in the purchase or development of new hardware and/or software, and may involve replacement of existing systems • Require more than 40 business hours to perform • May require separate funding and resource scheduling

  12. PROJECT or CHANGE REQUEST? New Business Need ? Budget $$$ Required ? Y Y Start N N Change ? >40 ManHours? PROJECT Y Y “Decision Tree” N Multi-Discipline Support ? CHANGE REQUEST N Y

  13. Project Phases • Project Initiation • Requirements (Functional) • Logical Design (Technical) • Physical Design (Technical) • Build (Development) • Test (Quality Assurance) • Implement • Post-Implementation

  14. Start N N Project Initiation Approved? Project Kick-Off Mtg Reqmnts Clear Approved Single Solution Approved Develop Y Y Y Y Y Y A N N N N Require- ments Logical Design Purchase/ Config/ Test Install B B Physical Design Approved Build & Test Approved Acceptance Test Approved Implemen- tation Approved Y Y Y Y A C N N N N Recovery Procedure Post Implemen- tation Determine Action C End Legend: Cust&IMT IMT Sponsor & IMT Cabinet Customer Project Responsibilities

  15. I - Project Initiation • Submit Project Request • Log Request • Accept/Reject Request • Prioritize Project • Assign Project • Perform Cost Estimate • Start Project Schedule • Request “Go-Forward” Approval from IMT Cabinet & Executive Sponsor LSV

  16. II - Requirements • Conduct “Kick-Off” Meeting • Capture Requirements • Define Business Terms • Assemble Project Team • Estimate Phase-on-Deck • Provide Project Estimate at Completion (EAC) • Revise Project Schedule • Request “Go-Forward” Approval from IMT Cabinet & Executive Sponsor LSV

  17. Organizational Key Areas of Systems Analysis Present System Functional Requirements Systems Analysis

  18. III – Logical Design • Review Requirements with Team • Establish Technical Parameters • Conduct “Existing” Systems Architecture Impact Analysis • Conduct “Future” Systems Architecture Impact Analysis (Capacity Planning) • Prepare Solution Options • State Solution Recommendation • Review/Adjust Team Membership • Estimate Phase-on-Deck • Adjust Estimate At Completion (EAC) • Revise Project Schedule • Request “Go-Forward” Approval From IMT Cabinet & Executive Sponsor LSV

  19. Organizational Feasibility Is it a good fit? Economic Feasibility Can we afford it? Operational Feasibility Will it be accepted? Technical Feasibility Does the capability exist? Systems Investigation

  20. IV – Physical Design • Prepare Technical Specifications • Create Test Plan • Begin Implementation Plan • Review/Adjust Team Membership • Estimate Phase-on-Deck • Adjust Estimate At Completion (EAC) • Revise Project Schedule • Request “Go-Forward” Approval from IMT Cabinet & Executive Sponsor LSV

  21. Guiding Principles • Information Architect - Interoperability • Stewardship • View solution offerings as an opportunity to converge data and/or technologies • Commitment to Open Standards • Web browser based end user interface • Cross platform support

  22. Hardware Evaluation Factors Performance Cost Reliability Compatibility Technology Ergonomics Connectivity Scalability Software Support Software Evaluation Factors Quality Efficiency Flexibility Security Connectivity Language Documentation Hardware Efficiency Evaluating Hardware and Software

  23. IS Evaluation Factors Performance Systems Development Maintenance Conversion Training Backup Accessibility Business Position Hardware Software Evaluating IS Services

  24. V – Build & Test • Build Solution • Test Solution • Identify Customer Acceptance Test Team • Estimate Phase-on-Deck • Adjust Estimate At Completion (EAC) • Revise Project Schedule • Request “Go-Forward” Approval From IMT Cabinet & Executive Sponsor LSV

  25. Implementation Activities Acquisition Development and Modification System Testing End User Training System Docu- mentation Conversion The Implementation Process

  26. Implementation Activities Acquisition Software Development Training Testing Documentation Conversion Implementing New Systems

  27. Old System Parallel New System Old System New System Pilot Old System New System Phased Old System New System Plunge Installation Conversion Methods

  28. VI – Customer Acceptance Test • Conduct Customer Acceptance Test • Estimate Phase-on-Deck • Adjust Estimate At Completion (EAC) • Revise Project Schedule • Request “Go-Forward” Approval From IMT Cabinet & Executive Sponsor LSV

  29. VII - Implementation • Finalize Implementation Plan • Create End-User Documentation • Formalize System Documentation • Train Support Group(s) • Train Customer(s) • Communicate, Communicate, Communicate… • Deploy Solution/System • Notify Customers of System Availability LSV

  30. VIII - Post-Implementation • Perform any “clean-up” necessary • The Project Lead will conduct meetings with the requestor & team to discuss/document areas of future opportunity and to highlight those things that went well • Close Project • Sponsorship sign-off • Close Project Account • Prepare Project Summary • Lessons Learned • Measurable and can be Implemented • Project Costs LSV

  31. Organizational Design Change Management Measurement and Rewards Core Competencies Development Managing Organizational Change Executive Vision Organization Mission and Role Work Redesign

  32. Objectives • Coordination Of Change Management Activities • Communication Of Planned Changes • Notification Of Scheduled/Failed Changes • Use Of Standardized Methods And Procedures • Auditing Mechanisms And Processes For Reviewing Changes After They Have Taken Place • Management Reporting

  33. Change Request - Definition • A written submission from an IMTclient, or staff member, to alter a “Production” IMT system/service… • Enterprise Resource Planning system (i.e. IFAS) • Including any functionality integrated with ERP • Network Systems • Servers • Telecom Systems • Etceteras • Usually performed by a single IMT work group • Estimated effort less than 40 hours • AOP Budget Dollars Approved

  34. Chapter Summary • Business professionals and IS specialists use a systems approach to help them develop information system solutions to meet e-business needs. • The application development capabilities built into many end user software packages have made it easier for end users to develop their own e-business applications. • Business professionals should know how to evaluate IT products for acquisition. IT vendor proposals should be based on specifications developed during the design phase.