

Study with the several resources on Docsity
Earn points by helping other students or get them with a premium plan
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
Community
Ask the community for help and clear up your study doubts
Discover the best universities in your country according to Docsity users
Free resources
Download our free guides on studying techniques, anxiety management strategies, and thesis advice from Docsity tutors
A list of key terms related to information systems development, including asking directly, computer-aided software engineering, data analysis, data-flow diagram, design report, and many more. These terms are essential for understanding the systems development process.
Typology: Study notes
1 / 2
This page cannot be seen from the preview
Don't miss anything!
Fundamentals of Information Systems, Fifth Edition 8- 1
Asking directly —an approach to gather data that asks users, stakeholders, and other managers about what they want and expect from the new or modified system. Computer-aided software engineering (CASE) —tools that automate many of the tasks required in a systems development effort and encourage adherence to the SDLC. Data analysis —manipulation of the collected data so that the development team members who are participating in systems analysis can use the data. Data preparation, or data conversion —ensuring all files and databases are ready to be used with new computer software and systems. Data-flow diagram (DFD) —a model of objects, associations, and activities that describes how data can flow between and around various objects. Design report —the primary result of systems design, reflecting the decisions made and preparing the way for systems implementation. Direct conversion (also called plunge or direct cutover) —stopping the old system and starting the new system on a given date. Direct observation —watching the existing system in action by one or more members of the analysis team. Economic feasibility —determination of whether the project makes financial sense and whether predicted benefits offset the cost and time needed to obtain them. End-user systems development —any systems development project in which the primary effort is undertaken by a combination of business managers and users. Feasibility analysis —assessment of the technical, economic, legal, operational, and schedule feasibility of a project. Information systems planning —translating strategic and organizational goals into systems development initiatives. Installation —the process of physically placing the computer equipment on the site and making it operational. Joint application development (JAD) —process for data collection and requirements analysis in which users, stakeholders, and IS professionals work together to analyze existing systems, propose possible solutions, and define the requirements of a new or modified system. Legal feasibility —determination of whether laws or regulations may prevent or limit a systems development project. Logical design —a description of the functional requirements of a system. Make-or-buy decision— the decision regarding whether to obtain the necessary software from internal or external sources. Object-oriented systems development (OOSD) —approach to systems development that combines the logic of the systems development life cycle with the power of object-oriented modeling and programming. Operational feasibility —measure of whether the project can be put into action or operation. Parallel start-up— running both the old and new systems for a period of time and comparing the output of the new system closely with the output of the old system; any differences are reconciled. When users are comfortable that the new system is working correctly, the old system is eliminated. Phase-in approach, or piecemeal approach —slowly replacing components of the old system with those of the new one. This process is repeated for each application until the new system is running every application and performing as expected. Physical design —the specification of the characteristics of the system components necessary to put the logical design into action. Pilot start-up —running the new system for one group of users rather than for all users. Programmer —specialist responsible for modifying or developing programs to satisfy user requirements.
Fundamentals of Information Systems, Fifth Edition 8- 2 Questionnaires —a method of gathering data when the data sources are spread over a wide geographic area. Rapid application development (RAD) —a systems development approach that employs tools, techniques, and methodologies designed to speed application development. Request for proposal (RFP) —a document that specifies in detail required resources such as hardware and software. Requirements analysis —determination of user, stakeholder, and organizational needs. Schedule feasibility —determination of whether the project can be completed in a reasonable amount of time. Site preparation —preparation of the location of a new system. Stakeholders —people who, either themselves or through the organization they represent, ultimately benefit from the systems development project. Start-up —the process of making the final tested information system fully operational. Steering committee —an advisory group consisting of senior management and users from the IS department and other functional areas. Structured interview —an interview where the questions are written in advance. Systems analysis —the systems development phase involving the study of existing systems and work processes to identify strengths, weaknesses, and opportunities for improvement. Systems analyst —professional who specializes in analyzing and designing business systems. Systems design —the systems development phase that answers the question, “How will the information system solve a problem?” Systems implementation —the systems development phase involving the creation or acquiring of various system components detailed in the systems design, assembling them, and placing the new or modified system into operation. Systems investigation —the systems development phase during which problems and opportunities are identified and considered in light of the goals of the business. Systems investigation report —summary of the results of the systems investigation and the process of feasibility analysis and recommendation of a course of action. Systems maintenance and review —the systems development phase that ensures the system operates as intended and modifies the system so that it continues to meet changing business needs. Systems maintenance —a stage of systems development that involves checking, changing, and enhancing the system to make it more useful in achieving user and organizational goals. Systems operation —use of a new or modified system. Systems request form —document filled out by someone who wants the IS department to initiate systems investigation. Systems review —the final step of systems development, involving the analysis of systems to make sure that they are operating as intended. Technical feasibility —assessment of whether the hardware, software, and other system components can be acquired or developed to solve the problem. Unstructured interview —an interview where the questions are not written in advance. User acceptance document —a formal agreement signed by the user that states that a phase of the installation or the complete system is approved. User preparation —the process of readying managers, decision makers, employees, other users, and stakeholders for new systems. Users —people who will interact with the system regularly.