Help
Options
Didn't know it?
click below
click below
Knew it?
click below
click below
Don't Know
Remaining cards (0)
Know
retry
shuffle
restart
0:00
Embed Code - If you would like this activity on your web page, copy the script below and paste it into your web page.
Normal Size Small Size show me how
Normal Size Small Size show me how
MIS 1-5
| Question | Answer |
|---|---|
| planning | The first phase of the SDLC , in which an organization's total information system needs are identified, analyzed, prioritized, and arranged |
| analysis | The second phase of the SDLC, in which system requirements are studied and structured. |
| design | The third phase of the SDLC, in which the description of the recommended solution is converted into logical and then physical system specifications |
| implementation | The fourth phase of the SDLC, in which the information system is coded, tested, installed, and supported in the organization. |
| maintenance | The final phase of the SDLC, in which an information system is systematically repaired and improved |
| application software | Computer software designed to support organizational functions or processes. |
| information systems analysis and design | The complex organizational process whereby computer-based information systems are developed and maintained |
| logical design | The part of the design phase of the SDLC in which all functional features of the system chosen for development in analysis are described independently of any computer platform. |
| logical design | The part of the design phase of the SDLC in which all functional features of the system chosen for development in analysis are described independently of any computer platform. |
| Physical design | The part of the design phase of the SDLC in which the logical specifications of the system from logical design are transformed into technology-specific details from which all programming and system construction can be accomplished. |
| systems analyst | The organizational role most responsible for the analysis and design of information systems. |
| systems development life cycle | (SDLC) The traditional methodology used to develop, maintain, and replace information systems. |
| systems development methodology | A standard process followed in an organization to conduct all the steps necessary to analyze, design, implement, and maintain information systems. |
| cloud computing | The provision of computing resources, including applications, over the Internet so customers do not have to invest in the computing infrastructure needed to run and maintain the resources. |
| enterprise resource planning systems | (ERP) A system that integrates individual traditional business functions into a series of modules so that a single transaction occurs seamlessly within a single information system rather than several separate systems. |
| outsourcing | The practice of turning over responsibility for some or all of an organization's information systems applications and operations to an outside firm. |
| request for proposal | (RFP) A document provided to vendors that asks them to propose hardware and system software that will meet the requirements of a new system. |
| COCOMO | The Constructive Cost Model (COCOMO) is an automated software estimation model that uses historical project data and current as well as future project characteristics to estimate project costs. |
| critical path | The shortest time in which a project can be completed. |
| critical path scheduling | A scheduling technique whose order and duration of a sequence of task activities directly affect the completion date of a project. |
| deliverable | An end product of an SDLC phase. |
| feasibility study | A study that determines if the proposed information system makes sense for the organization from an economic and operational standpoint. |
| gantt chart | A graphical representation of a project that shows each task as a horizontal bar whose length is proportional to its time for completion |
| network diagram | A diagram that depicts project tasks and their interrelationships. |
| PERT | (Program Evaluation Review Technique) A technique that uses optimistic, pessimistic, and realistic time estimates to calculate the expected time for a particular task. |
| project charter | A short document prepared for the customer during project initiation that describes what the project will deliver and outlines generally at a high level all work required to complete the project |
| project closedown | The final phase of the project management process that focuses on bringing a project to an end. |
| project execution | The third phase of the project management process in which the plans created in the prior phases (project initiation and planning) are put into action. |
| project initiation | The first phase of the project management process in which activities are performed to assess the size, scope, and complexity of the project and to establish procedures to support later project activities. |
| project management | A controlled process of initiating, planning, executing, and closing down a project |
| project manager | A systems analyst with a diverse set of skills-management, leadership, technical, conflict management, and customer relationship-who is responsible for initiating, planning, executing, and closing down a project |
| project planning | The second phase of the project management process that focuses on defining clear, discrete activities and the work needed to complete each activity within a single project. |
| project workbook | An online repository for all project-related documents that is used for performing project audits, orienting new team members, communicating with management and customers, identifying future projects, and performing post-project reviews. |
| project | A planned undertaking of related activities to reach an objective that has a beginning and an end. |
| resources | Any person, group of people, piece of equipment, or material used in accomplishing an activity. |
| slack time | The amount of time that an activity can be delayed without delaying the project. |
| work breakdown structure | The process of dividing the project into manageable tasks and logically ordering them to ensure a smooth evolution between tasks. |
| affinity clustering | The process of arranging planning matrix information so that clusters of information with a predetermined level or type of affinity are placed next to each other on a matrix report. |
| bottom-up planning | A generic information systems planning methodology that identifies and defines IS development projects based upon solving operational business problems or taking advantage of some business opportunities. |
| competitive strategy | The method by which an organization attempts to achieve its mission and objectives. |
| corporate strategic planning | An ongoing process that defines the mission, objectives, and strategies of an organization. |
| data dictionary | A centralized repository of information about data such as meaning, relationships to other data, origin, usage, and format. |
| electronic commerce | (EC) Internet-based communication to support day-to-day government, business, and consumer activities. |
| incremental commitment | A strategy in systems analysis and design in which the project is reviewed after each phase and continuation of the project is rejustified. |
| information systems planning | (ISP) An orderly means of assessing the information needs of an organization and defining the systems, databases, and technologies that will best satisfy those needs. |
| internet-of-Things | (IOT) A broad class of physical objects that feature an Internet address and connectivity that communicate between these objects and other Internet-enabled devices and systems. |
| internet | A large, worldwide network of networks that use a common protocol to communicate with each other. |
| mission statement | A statement that makes it clear what business a company is in. |
| objective statements | A series of statements that express an organization's qualitative and quantitative goals for reaching a desired future position |
| top-down planning | A generic ISP methodology that attempts to gain a broad understanding of the information systems needs of the entire organization. |
| value chain analysis | Analyzing an organization's activities to determine where value is added to products and/or services and the costs incurred for doing so, it usually also includes a comparison with the activities, added value, and costs of other organizations the purpose |
| baseline Project Plan | (BPP) A major outcome and deliverable from the project initiation and planning phase that contains the best estimate of a project's scope, benefits, costs, risks, and resource requirements. |
| break-even analysis | A type of cost-benefit analysis to identify at what point (if ever) benefits equal costs. |
| business case | The justification for an information system, presented in terms of the tangible and intangible economic benefits and costs and the technical and organizational feasibility of the proposed system. |
| discount rate | The rate of return used to compute the present value of future cash flows. |
| economic feasibility | A process of identifying the financial benefits and costs associated with a development project. |
| intangible benefits | A benefit derived from the creation of an information system that cannot be easily measured in dollars or with certainty. |
| intangible costs | A cost associated with an information system that cannot be easily measured in terms of dollars or with certainty. |
| legal and contractual feasibility | The process of assessing potential legal and contractual ramifications due to the construction of a system. |
| one-time costs | A cost associated with project start-up and development or system start-up. |
| operational feasibility | The process of assessing the degree to which a proposed system solves business problems or takes advantage of business opportunities. |
| political feasibility | The process of evaluating how key stakeholders within the organization view the proposed system. |
| present value | The current value of a future cash flow. |
| project Scope Statement | (PSS) A document prepared for the customer that describes what the project will deliver and outlines generally at a high level all work required to complete the project |
| recurring costs | A cost resulting from the ongoing evolution and use of a system. |
| schedule feasibility | The process of assessing the degree to which the potential time frame and completion dates for all major activities within a project meet organizational deadlines and constraints for affecting change |
| tangible benefits | A benefit derived from the creation of an information system that can be measured in dollars and with certainty. |
| tangible costs | A cost associated with an information system that can be measured in dollars and with certainty. |
| technical feasibility | A process of assessing the development organization's ability to construct a proposed system. |
| time value of money | (TVM) The concept that money available today is worth more than the same amount tomorrow. |
| total cost of ownership | (TCO) The cost of owning and operating a system, including the total cost of acquisition, as well as all costs associated with its ongoing use and maintenance. |
| walk-throughs | A peer group review of any product created during the systems development process; also called a structured walk-through. |
Created by:
user-1978467
Popular Business sets