CPSC-3720 Final

0.0(0)
studied byStudied by 0 people
learnLearn
examPractice Test
spaced repetitionSpaced Repetition
heart puzzleMatch
flashcardsFlashcards
Card Sorting

1/53

encourage image

There's no tags or description

Looks like no tags are added yet.

Study Analytics
Name
Mastery
Learn
Test
Matching
Spaced

No study sessions yet.

54 Terms

1
New cards

Scrum Master

A facilitator who helps the team follow Scrum practices and removes obstacles.

2
New cards

Product Owner

Defines the product vision, manages the backlog, and prioritizes features.

3
New cards

Sprint Planning

A Scrum ceremony where the team plans what work will be completed during the sprint.

4
New cards

Daily Scrum

A short, daily meeting where team members share progress and blockers.

5
New cards

Sprint Review

Meeting at the end of a sprint to demo work and gather feedback.

6
New cards

Sprint Retrospective

A reflection meeting to improve team processes for future sprints.

7
New cards

Product Backlog

A prioritized list of all features, bug fixes, and technical tasks for a product.

8
New cards

Sprint Backlog

A subset of the product backlog selected for completion during a sprint.

9
New cards

Increment

The sum of all completed backlog items at the end of a sprint that meet the Definition of Done.

10
New cards

INVEST Acronym

Independent, Negotiable, Valuable, Estimable, Small, Testable — qualities of a good user story.

11
New cards

User Story

A short description of a feature from the user's point of view using the format: As a…, I can…, so that…

12
New cards

Epic

A large user story that can be broken down into smaller stories.

13
New cards

Story Points

A relative measure of complexity and effort to complete a user story.

14
New cards

Velocity

The average number of story points a team completes in a sprint.

15
New cards

REST API

A software architecture style for designing scalable web services using HTTP methods.

16
New cards

HTTP GET

Retrieves data from a specified resource.

17
New cards

HTTP POST

Creates a new resource.

18
New cards

HTTP PATCH

Updates part of an existing resource.

19
New cards

HTTP DELETE

Removes a resource.

20
New cards

Endpoint

A specific URL that represents an API resource (e.g., /orders).

21
New cards

OpenAPI Specification

A machine-readable format used to describe RESTful APIs (formerly Swagger).

22
New cards

OpenAPI Info Section

Contains API metadata like title, version, and description.

23
New cards

OpenAPI Paths Section

Defines the available endpoints and their operations.

24
New cards

OpenAPI Components Section

Defines reusable schemas, parameters, and responses.

25
New cards

Mock Server

A simulated API endpoint used for testing before the real backend is built.

26
New cards

Postman

A tool for testing APIs, creating mocks, examples, and automated test collections.

27
New cards

Postman Collection

A group of saved API requests organized for testing or documentation.

28
New cards

Postman Environment

A set of variable values (like base URLs) used to configure API requests.

29
New cards

Functional Testing

Testing that verifies if a system behaves according to requirements.

30
New cards

Non-Functional Testing

Testing how the system performs under conditions like load, stress, and usability.

31
New cards

CI/CD

Pipeline of Continuous Integration and Continuous Delivery/Deployment to automate testing and releases.

32
New cards

DynamoDB

A serverless NoSQL database used in AWS Lambda applications.

33
New cards

Lambda Function

A serverless compute service that runs backend code in response to events.

34
New cards

API Gateway

An AWS service that exposes REST endpoints and routes to Lambda functions.

35
New cards

CloudWatch

A logging and monitoring service for AWS Lambda and other AWS resources.

36
New cards

The First Way (DevOps)

Emphasizes fast flow of work from development to operations using practices like CI/CD.

37
New cards

The Second Way (DevOps)

Focuses on continuous feedback to catch and resolve issues early.

38
New cards

The Third Way (DevOps)

Encourages continuous learning, experimentation, and improvement.

39
New cards

Brooks’s Law

Adding people to a late software project makes it later.

40
New cards

Build One to Throw Away

The first version of a system will likely be flawed, so plan to rebuild.

41
New cards

Conceptual Integrity

Good software is designed with a consistent and unified vision.

42
New cards

Microservices

Independent, loosely-coupled services that focus on a specific business capability.

43
New cards

Accounts Service

Handles user data like login, registration, and preferences.

44
New cards

Notifications Service

Sends messages based on events like password changes or order updates.

45
New cards

Order Service

Manages the creation, update, and status tracking of food orders in TigerChow.

46
New cards

Valuation Service

Estimates the value of a used car based on input details.

47
New cards

Search & Filter Service

Allows users to filter or sort listings based on specific criteria.

48
New cards

Kanban Board

A visual project tracking tool used in Agile to move tasks across columns like To Do → Doing → Done.

49
New cards

Definition of Done

A team’s shared understanding of what it means for a story to be complete.

50
New cards

Acceptance Criteria

Specific conditions a story must meet to be considered done and testable.

51
New cards

TigerChow Sprint 1

Focused on creating API specs and examples for Accounts and Notifications.

52
New cards

TigerChow Sprint 2

Added Lambda + DynamoDB implementations and testing.

53
New cards

TigerChow Sprint 3

Implemented the Orders service with notifications and status updates.

54
New cards