Ünite 3: Information System Development And Management — Doğru/Yanlış

Gösterilen tanım o kavrama ait mi? 23 soru var.

1 / 230 doğru

Functional Requirements

The specific capabilities, features, and data processing tasks that the new information system must offer to its users. For example, a ••• requirement for an e-commerce system is the ability to securely collect and store customer credit card details during checkout.

Functional Requirements — The specific capabilities, features, and data processing tasks that the new information system must offer to its users. For example, a functional requirement for an e-commerce system is the ability to securely collect and store customer credit card details during checkout.

Alfa Test — The process of testing a complete information system using simulated or sample data within a controlled development environment. For example, the internal testing team runs sample transactions through the new billing software to detect and debug initial coding errors.

Perfective Maintenance — The process of improving system efficiency, reliability, maintainability, and documentation to respond to evolving user needs and organizational growth. For example, a system administrator optimizes database queries to speed up the generation of weekly sales reports.

Work Statement — A formal contract or agreement that outlines the definition, content, general timing, and resource budget for developing an information system. For example, the project manager and system owner sign this document to officially initiate the development of a new inventory database.

Human Resource Information System (HRIS) — A computer-based system designed to acquire, store, manipulate, analyze, retrieve, and distribute information regarding an organization's human resources. For example, an HRIS is used by managers to track employee performance, manage talent pools, and plan succession strategies.

Pilot Transition Strategy — A transition approach where the new system is deployed and operated in only one branch or department before being rolled out to the rest of the business. For example, a retail chain installs a new point-of-sale system in its Izmir branch first to resolve any errors before nationwide deployment.

Phased Transition Strategy — An incremental transition method where the new system is put into practice in separate modules or pieces over time. For example, a company first deploys the recruitment module of its HR system, followed by the payroll module, and finally the performance management module.

Adaptive Maintenance — The process of modifying or adding system functions to ensure the information system conforms to changing business activities, industry standards, or legal regulations. For example, a developer updates the payroll system to comply with a newly enacted government tax rate change.

Feasibility Study — An investigation conducted during the planning phase to assess the technical, operational, scheduling, economic, and legal likelihood of a project's success. For example, a team conducts this study to determine if the business has the budget and technology to build a new customer relationship management system.

System Development Life Cycle (SDLC) — A systematic, phase-by-phase approach to information system development that includes scope and planning, requirements analysis, design, realization and test, setup and distribution, and operation and maintenance. For example, a business uses SDLC to ensure a new payroll system meets all user requirements and is delivered on budget.

HR Metrics — Quantitative indicators used to track, measure, and demonstrate the performance and effectiveness of human resource activities. For example, a company tracks 'time till promotion' and 'revenue per employee' to evaluate the success of its talent development programs.

Data Dictionary — A centralized document created during the design phase that defines the data types, structures, and characteristics of all data elements in the system. For example, an analyst uses a data dictionary to map old database fields to the new database structure during data transformation.

Parallel Transition Strategy — A system transition method where both the old and new systems are operated simultaneously until the new system is proven to work perfectly. For example, a bank runs its old and new transaction systems together for a month to ensure zero downtime and compare output accuracy.

Joint Application Design (JAD) — A collaborative, group-based requirement gathering technique where system analysts, managers, and users participate in intensive, structured meetings to define system goals. For example, a company conducts a three-day JAD session to collectively design the workflow of a new supply chain system.

CASE Repository — A central database at the heart of CASE tools that stores and shares all project models, diagrams, descriptions, and documentation among developers. For example, when an analyst updates a system flowchart, the change is automatically saved in the repository for the programmers to access.

System Analyst — A specialized professional who understands both business needs and computing technologies, acting as a bridge to identify and validate business problems for system owners and users. For example, the analyst conducts interviews with managers to translate their operational needs into technical system specifications.

Discovery Prototyping — An iterative process of building a quick, simplified model of a system to help users and developers understand and define highly uncertain requirements. For example, a developer builds a basic screen mockup of a new mobile app so the client can evaluate and refine the user interface.

Preventive Maintenance — Proactive activities designed to lengthen the service life of the system and reduce the likelihood of future failures, adding high long-term value. For example, an IT team performs regular server disk cleanups and updates security protocols to prevent future system crashes.

Nonfunctional Requirements — The performance, reliability, security, and usability characteristics that define how well the information system must operate. For example, a nonfunctional requirement specifies that the banking system must be available 24/7 and have a response time of less than two seconds.

Direct Transition Strategy (Big-Bang) — A high-risk transition approach where the old system is instantly shut down and replaced by the new system in the shortest possible time. For example, a small business completely replaces its old accounting spreadsheet with a new software package over a single weekend.

Electronic Human Resource Management (e-HRM) — The application of information technology to enable networking and support shared HR activities among employees, managers, and HR staff. For example, e-HRM allows employees to log into an online portal to submit vacation requests and view their retirement benefits.

Corrective Maintenance — The reactive process of fixing software bugs, errors, and failures that are discovered by users during live system operations. For example, a developer writes and applies a software patch to fix a calculation error in the monthly tax reporting module of an accounting system.

Beta Test — The process of testing an information system in a real production environment using real data before the system is officially delivered to all users. For example, a selected group of end-users operates the new software in their daily tasks to identify any remaining operational issues.