1 / 47

Chapter 15 Systems Development

Chapter 15 Systems Development. Learning Objectives. Describe the systems development life cycle, which is the traditional approach to systems development List and explain the pros and cons of prototyping Describe how software tools facilitate monitoring and controlling systems development.

uyen
Télécharger la présentation

Chapter 15 Systems Development

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Chapter 15Systems Development Management Information Systems, 4th Edition

  2. Learning Objectives • Describe the systems development life cycle, which is the traditional approach to systems development • List and explain the pros and cons of prototyping • Describe how software tools facilitate monitoring and controlling systems development Management Information Systems, 4th Edition

  3. Learning Objectives (Cont.) • Explain the difficulties involved in systems development • List the advantages and disadvantages of different system conversion strategies • Explain the concept of systems integration Management Information Systems, 4th Edition

  4. Why Develop an IS? • An opportunity (proactive) • Potential increase in revenue • Reduction of costs • Gain in competitive advantage • A problem (reactive) • Undesired situation • A directive • An order to take action Management Information Systems, 4th Edition

  5. The Systems DevelopmentLife Cycle (Cont.) Management Information Systems, 4th Edition

  6. The Systems DevelopmentLife Cycle (Cont.) Management Information Systems, 4th Edition

  7. Analysis • Investigation • Developers interview managers and perspective users to determine business needs • Three feasibility studies performed Management Information Systems, 4th Edition

  8. Analysis (Cont.) • Technical Feasibility Study • Ensures hardware and software exist to build the system • Economic Feasibility Study • Determines resources needed for implementation • Determines if benefits outweigh the costs Management Information Systems, 4th Edition

  9. The Systems DevelopmentLife Cycle (Cont.) Management Information Systems, 4th Edition

  10. Analysis (Cont.) • Operational Feasibility Study • Determines if system will be used as intended at its full capacity • Requirements Definition • Specific features and interface requirements of the system defined Management Information Systems, 4th Edition

  11. The Systems DevelopmentLife Cycle Management Information Systems, 4th Edition

  12. Design • Translation of user requirements into detailed functions of the system • Input files • Procedures • Output files • User Dialog • Interfaces Management Information Systems, 4th Edition

  13. Design (Cont.) Management Information Systems, 4th Edition

  14. Design (Cont.) • Software development tools • Flowcharts • Graphical symbols illustrating system • Logical and physical elements • Over 30 symbols for events, hardware, processes and more Management Information Systems, 4th Edition

  15. Design (Cont.) Management Information Systems, 4th Edition

  16. Design (Cont.) • Software development tools • Data flow diagram • Describe flow of data in system with only four symbols: • External entities • Processes • Data stores • Data direction Management Information Systems, 4th Edition

  17. The Systems DevelopmentLife Cycle (Cont.) Management Information Systems, 4th Edition

  18. The Systems DevelopmentLife Cycle (Cont.) Management Information Systems, 4th Edition

  19. Design (Cont.) • Software development tools • Unified Modeling Language • Graphical standard for visualizing, specifying, and documenting software • Independent of programming language • Describe types of software • Use case, class, interaction, state, activity, and physical components Management Information Systems, 4th Edition

  20. The Systems DevelopmentLife Cycle (Cont.) Management Information Systems, 4th Edition

  21. Design (Cont.) • Construction • Programming • Systems Testing • Checked against system requirements • Attempts to make system fail Management Information Systems, 4th Edition

  22. Implementation • Training • Conversion • Parallel Conversion • Phased Conversion • Cut Over Conversion • Pilot Conversion Management Information Systems, 4th Edition

  23. Implementation (Cont.) Management Information Systems, 4th Edition

  24. Support Management Information Systems, 4th Edition

  25. Prototyping • Systems developed using an iterative process • Purpose is to develop a working model as quickly as possible, which can be tweaked and revised • Significantly shortens systems development backlog • Can increase risk of incompatibility and other unforeseen mishaps Management Information Systems, 4th Edition

  26. Prototyping (Cont.) Management Information Systems, 4th Edition

  27. Prototyping (Cont.) Management Information Systems, 4th Edition

  28. Agile Methods • Alternatives to SDLC • Able to adapt to vague or rapidly changing user requirements • Adaptive Software Development (ASD) • Extreme Programming (XP) • Lean Development (LD) • Rational Unified Process (RUP) • Feature Driven Development (FDD) • Dynamic Systems Development Method (DSDM) • Scrum • Crystal Management Information Systems, 4th Edition

  29. Project Management • Project Management Tools • Project Evaluation and Review Technique (PERT) • PERT chart shows events, required activities, and relationships • Advantage: Communication of interdependencies among activities • Gantt Chart • Represents activities and start and completion times, but not the relationships among activities • Advantage: Simple and linear Management Information Systems, 4th Edition

  30. Project Management (Cont.) Management Information Systems, 4th Edition

  31. Project Management (Cont.) • Project Management Goals • Complete the project on time • Complete the project within budget • Meet requirements • Meet expectations Management Information Systems, 4th Edition

  32. Project Management (Cont.) Management Information Systems, 4th Edition

  33. Project Management • Project Management Functions • Communication Management • Schedule Management • Quality Management • Financial Management • Resource Management Management Information Systems, 4th Edition

  34. Project Management Functions and Tools • Communication management • Ensure information gets to team members • Schedule management • Ensure milestones are met on time • Uses Gantt, PERT and other tools • Quality management • Tests and retests Management Information Systems, 4th Edition

  35. Project Management Functions and Tools (Cont.) • Financial management • Recording and tracking expenses • Resource management • Allocate personnel, hardware, software • Recruiting Management Information Systems, 4th Edition

  36. The Project Management Office • Enforce standard processes • Control budgets • Oversee several projects at one time • Two thirds of North American corporation had PMOs in 2003 • Not a substitute for direct involvement of senior managers Management Information Systems, 4th Edition

  37. JAD: Systems DevelopmentLed by End Users • Joint Application Development (JAD) • Uses six-step process • Plan • Customize • Workshop • Wrap-up • Design • Customize • Workshop • Wrap-up Management Information Systems, 4th Edition

  38. JAD: Systems DevelopmentLed by End Users (Cont.) Management Information Systems, 4th Edition

  39. JAD Critical Success Factors • All participants must be committed to the JAD process • The customers and IS people must agree on the project’s scope • The sponsor must be supportive and involved • JAD team members must be empowered decision makers Management Information Systems, 4th Edition

  40. JAD Critical Success Factors (Cont.) • Business objectives must be clearly defined • Business processes must be understood • Team members must be able to meet two or more days per week • Members must be committed to the team Management Information Systems, 4th Edition

  41. Benefits of the JAD Method • Speeds up development process: • Time required to gather requirements and resolve business issues is shortened • Increases customer commitment, confidence, and involvement while improving communication and design quality Management Information Systems, 4th Edition

  42. Benefits of the JAD Method (Cont.) • Increased commitment to the process: • IS unit and customers are partners, each with a vested interest in the project • Resulting system costs less than one developed in a traditional SDLC Management Information Systems, 4th Edition

  43. Systems Integration • Takes a look at the information needs of an entire organization (or a major division) • Analysts integrate existing systems so that: • Data can flow more easily among business units • Users can access different types of data via a single interface Management Information Systems, 4th Edition

  44. Systems Integration (Cont.) Management Information Systems, 4th Edition

  45. Ethical and Societal IssuesShould IS Professionals Be Certified? • Malfunctioning ISs • Faulty systems may wreak havoc, causing financial damage or even death • Should IS professionals be certified based on the high investment and risk involved in their work? Management Information Systems, 4th Edition

  46. Ethical and Societal IssuesShould IS Professionals Be Certified? • Certification Pros • Protect potential employers • Protect clients of consultants • Fewer software-related failures • Certification Cons • Difficult to measure software competence • May create a “closed shop:” decreased competition, decreased incentive to improve skills Management Information Systems, 4th Edition

  47. Summary • The SDLC is the traditional approach to systems development • There are pros and cons to prototyping • Software tools facilitate monitoring and controlling system development • There are advantages and disadvantages to different system conversion methods Management Information Systems, 4th Edition

More Related