Software Development Life Cycle (SDLC) Quiz

<p>Triggered by internal system changes (C)</p> Signup and view all the answers

<p>Ignoring logins and backup functions (B)</p> Signup and view all the answers

<p>Actors (B)</p> Signup and view all the answers

<p>To tailor system responses to user needs (B)</p> Signup and view all the answers

<p>Problem solving (A)</p> Signup and view all the answers

<p>System Development Life Cycle (D)</p> Signup and view all the answers

<p>Market the product (D)</p> Signup and view all the answers

<p>SDLC includes monitoring and business aspects (A)</p> Signup and view all the answers

<p>Waterfall model (B)</p> Signup and view all the answers

<p>Strict adherence to planning (B)</p> Signup and view all the answers

<p>System developed in repeated cycles (B)</p> Signup and view all the answers

<p>Market the system (A)</p> Signup and view all the answers

<p>Planning, Analysis, Design, Implementation, Maintenance (A)</p> Signup and view all the answers

<p>A document outlining system capabilities and business needs (C)</p> Signup and view all the answers

<p>A visual representation of project tasks showing dependencies and critical path (C)</p> Signup and view all the answers

<p>Prioritize essential entities and relationships (C)</p> Signup and view all the answers

<p>Random selection (A)</p> Signup and view all the answers

<p>To visually represent project tasks over time, including schedules but not dependencies (A)</p> Signup and view all the answers

<p>Systematic questioning (C)</p> Signup and view all the answers

<p>Including irrelevant nouns (C)</p> Signup and view all the answers

<p>Organizational &amp; Cultural Feasibility (D)</p> Signup and view all the answers

<p>Technological Feasibility (D)</p> Signup and view all the answers

<p>Is it a synonym for an existing class? (B)</p> Signup and view all the answers

<p>Arises from an immediate business need (D)</p> Signup and view all the answers

<p>As descriptive characteristics of a class (B)</p> Signup and view all the answers

<p>An attribute (B)</p> Signup and view all the answers

<p>Specific events or incidents (C)</p> Signup and view all the answers

<p>If they are synonyms for related concepts (D)</p> Signup and view all the answers

<p>To simplify complex systems and facilitate communication. (C)</p> Signup and view all the answers

<p>Algorithmic (A)</p> Signup and view all the answers

<p>Low-Level Abstraction (D)</p> Signup and view all the answers

<p>To describe other models. (C)</p> Signup and view all the answers

<p>Abstraction (D)</p> Signup and view all the answers

<p>Models can not capture all aspects of the real-world domain. (B)</p> Signup and view all the answers

<p>Models always provide a complete and accurate representation of the domain. (A)</p> Signup and view all the answers

<p>Textual descriptions of system requirements (A)</p> Signup and view all the answers

<p>To clarify requirements and enhance quality (B)</p> Signup and view all the answers

<p>An abstract representation of a concept or entity (D)</p> Signup and view all the answers

<p>Reducing project costs (A)</p> Signup and view all the answers

<p>By guiding the database structure and architecture (D)</p> Signup and view all the answers

<p>Iterate and refine the models (D)</p> Signup and view all the answers

<p>It breaks down domains into manageable parts (A)</p> Signup and view all the answers

<p>Data entities (C)</p> Signup and view all the answers

<p>Early identification of potential misunderstandings (B)</p> Signup and view all the answers

A method involving identifying users, classifying roles, interviewing, and compiling use cases.

A technique to identify external, temporal, and state events that trigger system responses.

Events initiated by an outside actor, like a customer purchase.

Events that occur based on time, such as generating monthly reports.

Events triggered by internal system changes, like reaching a reorder point.

Actors, use cases, and relationships that describe interactions in a system.

A relationship where one use case is executed as part of another use case.

A relationship where an additional use case is executed conditionally based on another use case.

A representation of some aspect of a system.

Models help deal with complexity, communicate, and provide solutions.

A broad overview of the system.

Focus on detailed components of the system.

A model that describes other models.

Include graphical, descriptive, and mathematical.

Facilitate modification, reuse, and abstraction.

Uses diagrams (e.g., UML) for representation.

Three essential skills for a Systems Analyst: Problem Solving, IT Knowledge, Communication.

SDLC stands for System Development Life Cycle, a process for developing and managing information systems.

The six core phases of SDLC are: 1. Identify the Plan 2. Plan and Monitor the Project 3. Discover and Understand Details 4. Design the System 5. Build and Test 6. Complete System Tests and Deploy.

SDLC covers planning, monitoring, and business aspects, while Software Development mainly focuses on coding and testing software applications.

A linear approach where development phases are completed one at a time, in a sequence.

A flexible development methodology that uses iterative cycles and adapts to changes.

A system is developed in repeated cycles, allowing for refinement after each cycle.

A professional who gathers, analyzes, and defines system requirements for projects.

The specific area or context in which a problem exists, including relevant entities.

Components in Object-Oriented (OO) systems representing entities in the problem domain.

Creating a conceptual model of information for a specific problem area to clarify requirements.

It clarifies requirements, improves communication, supports design, reduces complexity, and enhances quality.

Domain modelling aligns stakeholder understanding of needs and specifications.

Establishes a common language among stakeholders through shared understanding.

Guides system architecture and database structure based on the domain model.

Including iterating and refining models as more information becomes available over time.

Key components and connections that define a system.

Engaging stakeholders to ensure data correctness.

Systematic questioning to identify tangible elements in a system.

Identifying nouns in descriptions to classify domain classes.

Challenges include irrelevant nouns and not recognizing attributes.

A characteristic that describes a domain class (e.g., Customer’s data).

A unique attribute that identifies an instance of a class (e.g., Customer ID).

Questions that help narrow down relevant nouns used as classes.

The five core phases of the Software Development Life Cycle: Planning, Analysis, Design, Implementation, and Maintenance.

Three ways projects can be initiated: Top-down, Bottom-up, and External forces.

A project initiation strategy that is part of a long-term strategic plan.

A project initiation strategy reacting to an immediate business need.

A document that outlines the high-level overview of system capabilities and business needs.

A visual representation of project tasks showing dependencies and the critical path.

A bar chart that visually represents project tasks over time, showing schedules but not dependencies.

Five types of feasibility studies: Economic, Organizational & Cultural, Technological, and additionally, Legal and Operational may exist.