Module 4 Quiz

Use Case

A business process that begins with an actor, ends with the actor, and accomplishes a business task for the actor.

Actor

A business role played by a set of business entities or stakeholders, which initiates use cases.

Requirements

Capabilities that the system must deliver and constraints that restrict the solution space.

Domain Modeling

A process to help the team understand the application domain and establish a common understanding.

Functional Requirements

Statements of information processing capabilities that the software system must possess.

Non-functional Requirements

Requirements that specify criteria that can be used to judge the operation of a system, rather than specific behaviors.

Traceability Matrix

A matrix that links requirements to their origins, showing where they come from and how they relate to use cases.

Feasibility Study

An assessment of the practicality of a proposed project or system, focused on technology, timing, cost, and constraints.

High Level Use Case

Describes when and where a use case begins and ends, such as TUCBW (Thing Understanding Caller Begin With) and TUCEW (Thing Understanding Caller Ends With).

Expanded Use Case

A detailed description that outlines step-by-step how the actor interacts with the system to carry out a business process.

System Engineering

The multidisciplinary approach of defining system requirements, allocating them to subsystems, and integrating these components.

Agile Principles

Approaches in project management focusing on iterative development, collaboration with users, and prioritization of tasks.

Use Case Diagram

A visual representation of the actors and use cases within a system, showing their interactions.

Actor-System Interaction Modeling

Modeling and design of how the system interacts with actors to carry out use cases.

Abstract Use Case

A use case defined by a verb-noun phrase, capturing the essence of a business process.

Key Takeaway Points

Summarized insights that capture the essential information from a lecture or chapter.

Behavior Modeling

The process of describing the behaviors of actors and systems during use case interactions.

Requirements Elicitation

The process of identifying and documenting the requirements for a system.

Iterative Phase

The phase where activities occur during each iteration of development.

System Boundary

The delimitations that define the scope of the system, distinguishing between those within the system and those outside.

Domain Model

A model that defines application domain concepts in terms of classes, attributes, and relationships.

UML Class Diagram

A structural diagram that shows the classes, their attributes and operations, and relationships between classes.

Polymorphism

The ability of different classes to respond to the same method call in different ways.

Encapsulation

The bundling of data and methods that operate on that data within one unit, usually a class.

Information Hiding

The principle of restricting access to the details of a program's implementation.

Inheritance

A mechanism where one class can inherit attributes and methods from another class.

Aggregation Relationship

A relationship that expresses one object being part of another object.

Association Relationship

A general relationship between two classes other than inheritance or aggregation.

Multiplicity in UML

Defines how many instances of a class can be related to instances of another class.

Use Case Specification

Describes the requirements and behavior of a use case in detail.

System Integration Testing

The phase where individual software modules are combined and tested as a group.

Customer Collaboration

Involving the customer in the development process to uncover and refine requirements.

Acceptance Testing

Testing that verifies if a system meets the acceptance criteria defined for it.

High Priority Use Cases

Use cases identified as critical for early testing and implementation due to their importance.

Requirements Specification (SRS)

A document that outlines the requirements for a software system.

Use Case Iteration Allocation Matrix

A tool that helps organize which use cases will be developed in each iteration.

Control Flow

The order in which individual statements, instructions, or function calls are executed in a program.

Data Flow

The path that data takes from input to output within a system.

Actor-System Interaction Table

A table used to describe the interactions between actors and the system.

Safety Requirements

Requirements ensuring that the system operates without causing harm to users.

Quality Requirements

Criteria defining acceptable quality levels for system outputs.

Performance Requirements

Specifications detailing how well the system should perform under specific conditions.

Security Requirements

Requirements that focus on protecting the system from unauthorized access or harm.

SRS Document Structure

The organization and key contents of a Software Requirements Specification document.

Feedback Loop

The process of using customer feedback to inform and improve ongoing development.

Interactive Models

Models that allow for user interaction during requirements gathering to clarify and explore needs.

Business Rules

Guidelines or constraints that govern how business operations are conducted.

Continuous Integration

The practice of merging code changes frequently to detect problems early.

Deployment

The process of delivering the completed software system to the client or users for use.

Maintenance Phase

The stage following development in which the system is updated and improved based on user needs.

User Interface Prototyping

Creating preliminary versions of user interfaces to gather feedback before implementation.

Use Case Context

The environment or scenario in which a use case takes place.

Class Hierarchy

A structure that represents relationships among classes in terms of generalization and specialization.

User Interaction Flows

The paths through which users engage with a system in various scenarios.

Input Data Validation

The process of ensuring that data entered into a system is correct and useful.

Documentation

Records and descriptions throughout the development lifecycle that help explain the system's requirements and functions.

Summary Representation

A concise description of a large process or requirement set to facilitate communication and understanding.

Customer Priorities

The ordering of needs based on customer input, emphasizing what is most important to enhance satisfaction.

Exploratory Testing

A testing methodology where testers actively explore the software to identify defects without predefined test cases.

Iterative Development

An approach that builds software in small, manageable increments.

Problem Statement

A concise description of the issues a project aims to address.

Use Case Analysis

Examination and breakdown of use cases to ensure they capture the necessary requirements.

Operational Environment

The context in which a system will operate, including hardware and software conditions.

User Acceptance,

The process of validating if the proposed system meets user expectations and requirements.

Quality Assurance Process

A systematic process to ensure the quality of the software during its development lifecycle.

Stakeholder Involvement

Engagement of individuals or groups interested in the outcome of a project.

Iterative Feedback

Collecting responses or evaluations from users at different stages of development for enhancement.

Scenario Planning

A method used to create hypothetical scenarios for future developments to assess risk and strategy.

Requirements Review

A process of examining requirements documents to ensure correctness, completeness, and clarity.

Validation vs Verification

Validation checks if the product meets customer requirements, while verification checks if it meets specifications.

Test Plan Document

A formal document detailing the testing strategy and framework for verifying system functionality.

Use Case Detail

An in-depth description of a use case, including its purpose, steps, and outcomes.

Functional Decomposition

Breaking down of complex processes into simpler, more manageable parts.

Component-Based Development

An approach to software engineering focusing on the reuse of software components.

Prototype Development

Creating early models of software systems to explore concepts and gather requirements.

Process Improvement

Ongoing efforts to improve services, products, or processes.

Maintenance Strategy

Plans and procedures put in place to maintain and enhance the system after deployment.

Workflow Diagrams

A visual representation of activities or processes to illustrate how tasks are supposed to flow.

Requirements Gathering Techniques

Methods and strategies used to collect user needs and expectations.

User Stories

Short, simple descriptions of a feature told from the perspective of the person who desires the new capability.

Change Management Process

Systematic approach to dealing with change, both from the perspective of an organization and the individual.

Task Automation

Using technology to perform tasks without human intervention.

Iterative Refinement

Gradually improving upon an idea or product through successive iterations.

Customer Feedback Mechanism

Methods in place to collect user feedback on the product’s performance and usability.

Testing Procedure,

Steps that define how testing will be executed for the software application.

Solution Architecture

The high-level structure of a software solution, which includes its components and their interrelations.

Requirements Lifecycle

The process of managing requirements from initial concept through to acceptance and deployment.

Quality Control Checks

Procedures to ensure the software meets quality standards and requirements.

Defect Tracking System

A system used to log, track, and manage defects in the development process.

Performance Metrics

Measurements used to evaluate the efficiency and effectiveness of a system.

Risk Management Practices

Methods to identify, assess, and mitigate risks in a project.

Collaborative Tools,

Software applications that enable teamwork and collaboration among members.

Resource Allocation Plan

A plan detailing how resources (human, financial, material) will be distributed in a project.

Project Charter

A document that outlines the objectives, scope, and participants in a project.

Design Specifications

Detailed descriptions of how a system should be built, including architecture and interface designs.

System Maintenance Practices

Methods and procedures for preserving a system's functionality over time.

Development Roadmap

A strategic plan that outlines the development process, milestones, and timelines.

Code Review Procedures

Processes for checking and evaluating code to maintain quality and standards.

Error Handling Mechanism

Strategies employed to manage errors in a program effectively.

Business Goals

Objective statements that outline the desired outcomes of a business or project.