1 / 26

Using MIS 2e Chapter 10: Managing Development David Kroenke

Study Questions. Q1

xiujuan
Download Presentation

Using MIS 2e Chapter 10: Managing Development David Kroenke

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. Using MIS 2e Chapter 10: Managing Development David Kroenke

    2. Study Questions Q1 What is systems development? Q2 Why is systems development difficult and risky? Q3 How do businesses use the systems development life cycle (SDLC) process? Q4 How do businesses use the rapid application development (RAD) process? Q5 What are the trade-offs among requirements, schedule, and cost? 10-2 Chapter 10: Managing Development

    3. Q1 What is System Development? 10-3 Chapter 10: Managing Development

    4. Many projects are never finished; others finish 200 percent over budget. Some projects finish on schedule and within budget but do not meet their goals. Q2 Why is systems development difficult and risky? 10-4 Chapter 10: Managing Development

    5. Q2 Why is systems development difficult and risky? Determine Requirements What features do you really want? Do you really need them? What controls do you need? What data do you have? What information do you want provided? Changes in Requirements Development aims at moving target; Bigger the system and longer the project, the more requirements change When requirements change, what should the development team do? Stop work and rebuild system in accordance with new requirements? If they do that, system will develop in fits and starts and might never be completed. Or, should the team finish the system, knowing that it will be unsatisfactory the day it is implemented and will therefore need immediate maintenance? 10-5 Chapter 10: Managing Development

    6. Q2 Why is systems development difficult and risky? Scheduling and Budgeting How long to build? How long to test? How long for training? How much will it cost for labor? What are the costs and benefits? Whats the rate of return? Changing Technology Do you want to stop your development to switch to the new technology? Would it be better to finish developing according to the existing plan? Diseconomies of Scale As people are added, the average contribution per worker decreases (The Mythical Man Month by Fred Brooks) When new staff are brought in, they must be trained by productive members who lose productivity while theyre training new members. Some tasks simply cant be speeded up. 10-6 Chapter 10: Managing Development

    7. Q2 Why is systems development difficult and risky (Methodologies)? Is systems development really so bleak? The answer is yes and no. These are two system development processes that help make projects more likely to succeed. Systems development life cycle (SDLC) Traditional method for system development but replaced by newer techniques Rapid application development (RAD) Makes extensive use of Joint Application Development, Prototyping, CASE tools, and object-oriented programming Each development method offers advantages based on the scope and complexity of the system being built. No single process works for all projects. 10-7 Chapter 10: Managing Development

    8. Q3 How do businesses use the systems development life cycle (SDLC) process? 10-8 Chapter 10: Managing Development

    9. Q3 How do businesses use the systems development life cycle (SDLC) process? 10-9 Chapter 10: Managing Development

    10. Q3 How do businesses use the systems development life cycle (SDLC) process? 10-10 Chapter 10: Managing Development

    11. Q3 How do businesses use the systems development life cycle (SDLC) process? 10-11 Chapter 10: Managing Development

    12. Q3 How do businesses use the systems development life cycle (SDLC) process? 10-12 Chapter 10: Managing Development

    13. Q3 How do businesses use the systems development life cycle (SDLC) process? 10-13 Chapter 10: Managing Development

    14. Q3 How do businesses use the systems development life cycle (SDLC) process? 10-14 Chapter 10: Managing Development

    15. Q3 How do businesses use the systems development life cycle (SDLC) process? The SDLC is not without its problems: Systems development seldom goes so smoothly. There is sometimes a need to crawl back up the waterfall. It is difficult to document the requirements in a usable way. Scheduling and budgeting is difficult especially for large projects Rapid Application Development (RAD) is an alternate methodology 10-15 Chapter 10: Managing Development

    16. Q4 How do businesses use the rapid application development (RAD) process? 10-16 Chapter 10: Managing Development

    17. Version 0 (Technical Design) Identify entities and relationships Identify fields and properties Relationship Diagram Version 1 (Visual Design) Confirmation of Technical Design Approval of Visual Design One-level Switchboard Version 2 (Navigation) Two-level switchboard shows complete navigation via Prototype macro Working form (from template) Working report (from template) Version 2.5 . . (Intermediate versions) Version 3 (Implementation) Finished system is developed in stages by substituting completed forms and reports for the various prototype entries Version 4 (Maintenance/Enhancement) Q4 How do businesses use the RAD process (Prototyping)? 10-17 Chapter 10: Managing Development

    18. The use of prototyping enables continual testing and avoids the last minute panic in traditional systems. Q4 How do businesses use the RAD process (Prototyping)? 10-18 Chapter 10: Managing Development

    19. Joint Application Design (JAD )is key element of RAD to help teams of users and developers conduct design activities. JAD came about because development wanted to incorporate feedback and testing earlier in the development process. A JAD session is a design meeting of short duration, perhaps an afternoon or a day or two at most. The goal is to keep the scope of the component small enough that the design can be completed in a short period. Q4 How do businesses use the RAD process (Joint Application Design)? 10-19 Chapter 10: Managing Development

    20. Q4 How do businesses use the RAD process (Joint Application Design)? 10-20 Chapter 10: Managing Development

    21. Q4 How do businesses use the RAD process (CASE tools)? 10-21 Chapter 10: Managing Development

    22. Object-Oriented Programming (OOP) is a discipline for designing and writing programs. Programmer defines the data and the operations (functions or methods) that can be applied to the data; thus the data structure is an object that includes both data and functions. Programmers can create relationships between objects so that one object inherits characteristics from other objects. A traditional program is executed sequentially, beginning with the first line of code and continuing through the program; it is the program and not the user that drives the system An object oriented program is driven by the user; i.e., he or she determines the events that take place which in turn trigger system actions Q4 How do businesses use the RAD process (Object Oriented Programming)? 10-22 Chapter 10: Managing Development

    23. Q4 How do businesses use the RAD process (Object Oriented Programming)? 10-23 Chapter 10: Managing Development

    24. There is a constant trade-off between requirements, cost, and time; i.e., more elaborate requirements increase cost and/or time, or conversely a shorter schedule requires lesser requirements and/or more cost Q5: What are trade-offs between requirements, schedule and cost? 10-24 Chapter 10: Managing Development

    25. Summary Systems development is the process of creating and maintaining information systems and are tailor-made. Major challenges of systems development include: Determining requirements Changes in requirements Difficulties in scheduling and budgeting Changing technology Diseconomies of scale (Mythical Man Month) Two systems development methodologies are: Systems Development Life Cycle (SDLC); traditional development methodology Rapid Application Development (RAD) uses prototyping, joint application development, and object-oriented programming 10-25 Chapter 10: Managing Development

    26. Review: Select the appropriate term for each item A mockup of one aspect of a new system Prototype Methodology that uses prototyping and object oriented programming Rapid Application Development The classical process that is used to develop information systems System Development Life Cycle Classic book that described diseconomies of scale in a large project Mythical Man Month Allows future users of the system to try out the new system on their own Beta testing Users and developers working in conjunction with each other to develop a system Joint Application Design A object oriented tool to facilitate development of computer programs or systems CASE tool 10-26 Chapter 10: Managing Development

More Related