Software Development Life Cycle (SDLC) Quiz

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.