GoConqr has a new look! Let us know what you think.

Sign up free

Flashcards

Chapter 11

aleaguirre IS FINAL EXAM English 53 cards

Cards in this deck (53)

  1. 1Structure Chart (Structured Methodologies/Tools)a top-down chart showing each level of design, its relationship to other levels, and its place in the overall design structure
  2. 2Change Control Board (CCB)responsible for approving or rejecting all change requests
  3. 3Traditional Systems Development Lifecycle (SDLC)-Original/traditional method for building information systems
    -Phased approach with formal stages
    -“Waterfall approach”
    -Formal division of labor between end-users and IT
  4. 4PrototypePreliminary model built rapidly and inexpensively; a small scale version of the system
  5. 5Four Step Process of Prototyping1.Identify the user’s basic requirements
    2.Develop an initial prototype
    3.Use the prototype
    4.Revise and enhance the prototype
  6. 6End User Development-End users create simple information systems with little or no assistance from technical specialists
    -Use fourth-generation languages, graphics languages, and PC software tools to access data, create reports, and develop information systems
  7. 7Purchasing Solutions-Purchase a software package from a commercial vendor
    -Generalized systems for universal functions with standard processes
    -Customization
  8. 8onshore outsourcingengaging another company within the same country for services
  9. 9nearshore outsourcingcontracting an outsourcing arrangement with a company in a nearby country
  10. 10offshore outsourcingusing organizations from developing (or far-shore) countries to write code and develop systems
  11. 11Rapid Application Development (RAD)-Creating workable systems in a very short period of time
    -Utilize prototyping, visual programming techniques, reusable standardized SW components, and JAD techniques
  12. 12JAD – Joint application designEnd users and information systems specialists working together on design
  13. 13Data Flow Diagram (Structured Methodologies/Tools)represents the processes of a system and the flow of data between them
  14. 14Process Specification (Structured methodologies/tools)describe the transformation occurring within the lowest level of the data flow diagrams, showing the logic for each process
  15. 15Change Management Systema collection of procedures to document a change request and define the steps necessary to consider the change based on the expected impact of the change
  16. 16Object- Oriented DevelopmentUses the concept of an “object” as the basic unit of analysis and design – an object combines the data and the specific processes that operate on that data
  17. 17Component-based development and Web servicesa way to develop SW by using SW components for common functions to quickly develop system
  18. 18Computer-Aided Software Engineering (CASE)-Provides software tools to automate some steps in the previously described methodologies
    -Reduces repetitive work in systems development
  19. 19CASE tools facilitate-clear documentation
    -coordination of team development efforts
    -modest productivity benefits if tools are used correctly
  20. 20Projecta planned series of related activities for achieving a specific business objective
  21. 21Project Managementapplication of knowledge, skills, tools, and techniques to achieve targets within specified budget and time constraints
  22. 22Project Management Variables-Scope
    -Time
    -Cost
    -Quality
    -Risk
  23. 23Project Selection-must select the projects to pursue evaluate and compare the choices
    -Determine project costs and benefits
    Tangible benefits
    Intangible benefits
    Capital budgeting methods – ROI, NPV, IRR
  24. 24Level of project risk is affected by-Project size
    -Project structure
    -Required level of technical expertise
  25. 25Overcoming user resistance-Promote user participation
    -Pay attention to user interfaces and ergonomic issues
    -Conduct an Organizational Impact analysis
  26. 26Gantt Chartlists project activities along with their start and completion dates – visually represents the timing and duration of different tasks
  27. 27PERT Chartgraphically depicts the project tasks and their interrelationships/dependencies
  28. 28Change Managementa set of techniques that aid in evolution, composition, and policy management of the design and implementation of a system
  29. 29Preventative Maintenancechanges to reduce the chance of system failure
  30. 30Perfective Maintenanceenhancements or improvements; desired but not necessarily required features
  31. 31Adaptive Maintenanceincrease system functionality to meet new business requirements
  32. 32Corrective Maintenancerepair defects or flaws in the design, coding or implementation
  33. 33Maintenance (Step 4)- changes required to correct or enhance a system
    - different types of maintenance
  34. 34Production (Step 4)-the actual use of the system in the real world setting
    - ongoing review of the system to determine how well it is meeting the Information Requirements and objectives to determine if any modifications are needed
  35. 35Phased Conversion (Step 4)implement new system in phases or pieces
  36. 36Pilot Conversion (Step 4)implement new system in one department or location only until it is evident that the new system works
  37. 37Plunge (direct cutover) conversion (Step 4)discard old system completely and start using new system
  38. 38Parallel Conversion (Step 4)using both old and new systems until it is evident that the new system performs correctly
  39. 39System DevelopmentSoftware that is built correctly can transform as the organization and its business transform
  40. 40Causes of System Development project failure-Missed deadlines
    -Going over budget
    -Unclear or missing business requirements
    -Users’ needs that weren’t met
    -Dissatisfied customers
    -Lack of support from top management
  41. 41Four Steps to Building an Information System1.Define and understand the problem
    2.Develop alternative solutions
    3.Choose a solution
    4.Implement the solution
  42. 42Step 1: Defining and Understanding the ProblemWhat caused the problem?
    Why does it persist?
    Why hasn’t it been solved?
    What are the objectives of a solution?
  43. 43Information Requirementsthe detailed set of business requests that the system must meet in order to be successful and meet objectives
  44. 44Step 2: Developing Alternative SolutionsDevelop alternative solutions to achieve the objectives and Information Requirements that were identified
  45. 45Step 3: Evaluating and Choosing SolutionsConduct a Feasibility Study to determine whether each alternative is feasible and achievable
  46. 46Step 4: Implementing the SolutionSystem design is the detailed design, model or blueprint for the system solution
  47. 47Testingsystem is thoroughly tested to determine it produces the right results/output
  48. 48Unit Testingdetailed testing of individual computer programs or modules
  49. 49System Testingtests the performance of the information system as a whole
  50. 50Acceptance testingtests that the system is ready to be used in a production or “real” setting
  51. 51Training (Step 4)-For successful implementation to occur, users will require training so they will be able to use the new system
    -Different types of training are available: on-line, face-to-face, built-in “help” features, etc.
  52. 52Documentation (Step 4)-Shows how the system works from both a technical and end-user perspective
    -User manuals and reference guides
    -Installation procedures
    -Troubleshooting guides and procedures
  53. 53Conversion (Step 4)the process of changing from the old system to the new system

Information

Description
IS FINAL EXAM Flashcards on Chapter 11, created by aleaguirre on 03/05/2013.
Created by
aleaguirre
Views
94
Rating

Feedback

What is it about?

What do you think of the new look?

How do you like it?