Systems Development Life Cycle Quiz

A conceptual model that outlines the stages involved in developing an information system project.

The first phase of the SDLC, where project goals are defined, needs are assessed, and a feasibility study is conducted.

The second phase of the SDLC, where the project's feasibility is determined by evaluating its technical, operational, and economic aspects.

The third phase of the SDLC, where high-level plans and goals are transformed into actionable ideas and development steps.

The fourth phase of the SDLC, where the actual software is built based on the design specifications.

The process of gathering information about a system's current state, user needs, and business goals, and using this information to create a detailed plan for the new system.

The process of analyzing and evaluating the collected requirements, ensuring they are complete, consistent, and feasible.

A formal document that outlines the software's specifications, including its functionalities, features, and user interface.

The stage where the system's architecture and design are created, outlining the system's structure, components, and how they will interact.

The process of testing the developed software to ensure it meets the defined requirements and performs as expected.

The stage where the software is deployed to its intended environment, made available to users, and user training may be provided.

The ongoing process of monitoring the software's performance, addressing issues, and making necessary updates and improvements.

The initial step in the SDLC, where the project's scope, goals, and feasibility are clearly defined. This phase sets the foundation for the entire project.

A technique used for gathering requirements through direct conversations with stakeholders. This allows for detailed understanding and clarification.

A method of collecting information from a large group of stakeholders using questionnaires or online surveys. This enables broad data gathering.

Directly observing how users interact with the current system to identify areas for improvement. This provides a realistic view of system usage.

Analyzing existing documents, such as process flows or user manuals, to understand the system. This helps in understanding the current system's structure.

A method of involving key stakeholders in the development process. This allows for collaborative decision-making and ensuring user needs are met.

Creating a prototype or working model of the system. This allows for early testing and feedback from users.

The process of creating an interface that is visually appealing, easy to use, and accessible to all users.

Designing a system that provides users with clear feedback on their actions, helping them understand the system's state and make decisions.

Creating a consistent design for a system's elements, such as buttons, menus, and icons, to ensure a uniform and predictable user experience.

The goal of making a system easy to understand and use, minimizing learning curves and effort for users.

The ability to create a system that is usable by people with disabilities.

Developing software that is efficient and performs well, using resources effectively and minimizing user wait times.

Creating a system that helps users prevent errors by providing clear instructions, warnings, and guidance.

The practice of building, testing, and deploying a new information system, involving developing software components, conducting testing phases, and training end-users.

A structured approach that uses graphical diagrams to represent system specifications, emphasizing a hierarchical and logical breakdown.

A graphical representation of a system's data flow, using specific symbols to depict processes, data stores, and external entities.

A method used for developing systems that focuses on a top-down approach, breaking down a system into smaller, manageable modules.

In Structured Analysis, breaking a system down into self-contained modules that perform specific functions, making development and maintenance easier.

The use of visual representations like diagrams and charts to communicate system specifications effectively and clearly to all stakeholders.

A way to represent the logical relationships between different components of a system, showing how information flows and is processed.

The ability of AI and machine learning systems to enhance system capabilities, improve decision-making, and automate repetitive tasks.

Systems designed with a focus on mobile device compatibility, prioritizing user experience on smaller screens and touch interfaces.

A flowchart that shows relationships between entities (people, objects, concepts) in a system. It's used in designing and debugging relational databases in software, business, education, and research.

Key activities of corrective maintenance include monitoring system performance, fixing bugs and addressing issues, and implementing system updates and enhancements. This maintenance focuses on resolving immediate problems and improving the system's functionality.

Adaptive maintenance aims to adapt the system to changes in the environment, user needs, or business goals. It involves modifying the system to handle new requirements, integrate with new technologies, or improve user experience.

Perfective maintenance focuses on improving the system's performance, reliability, and maintainability. This involves optimizing code, enhancing performance, and simplifying the system for easier maintenance. It's about making the system better and more efficient without adding new features.

Preventive maintenance aims to prevent future issues by anticipating potential problems and taking steps to address them. It involves regular system checks, identifying potential vulnerabilities, and implementing preventive measures to avoid system failures.

A standard notation for object-oriented analysis and design. It provides a set of symbols and diagrams to represent system structure and behavior.

Pseudocode uses structural rules of a normal programming language but is written for human interpretation instead of machine interpretation. It's a simplified representation of code, making it easier to understand and communicate the logic of a program.

A visual representation of system functionality from the user's perspective. It shows actors (users) interacting with the system and how they use different features.