1/48
Flashcards of key terms and concepts from the lecture notes about Agile, Full-Stack Development, DevOps, Databases, Frontend Frameworks and .NET.
Name | Mastery | Learn | Test | Matching | Spaced |
---|
No study sessions yet.
Agile
A flexible way of building software in small, iterative chunks with feedback each cycle
Waterfall
Traditional step-by-step process where everything is done once in order
Scrum
An Agile framework with roles, events, and artifacts to structure teamwork
Sprint
A short time-boxed period (1–4 weeks) where a team builds a set of features
Daily Standup
Quick daily team check-in
Sprint Planning
Plan what to build in the next sprint
Sprint Review
Show what was built
Sprint Retrospective
Reflect on what went well or could improve
Scrum Master
Facilitator who ensures Scrum is followed
Product Owner
Manages the backlog and decides what to build
Backlog
A prioritized list of tasks/stories/features
End-to-End Functionality
Building every layer: UI, middleware, backend
User Interface (UI)
The part of the app users see and interact with
Backend
Handles logic, data processing, and database connections
Middleware
Code that connects frontend to backend; handles logging, auth, etc.
API
The interface through which different parts of the app or different apps communicate
Unit Test
A small automated test for one part of your code
Application Lifecycle
The process from planning to maintaining software
CI/CD Pipeline
Automated steps for testing, building, and deploying code
Continuous Integration
Code is tested and merged regularly
Continuous Deployment
Code is automatically released after passing tests
Agile Storyboard
A task board (e.g., Trello, Jira) showing To Do → In Progress → Done
Git Repository
A version-controlled folder that stores your project history
GitHub / GitLab
Platforms for hosting Git repos
Database Components
Tables, relationships, indexes, views, etc.
SQL Query
A request to get or change data in a database
Primary Key
Uniquely identifies a row in a table
Foreign Key
Connects rows across tables
ORM (Object-Relational Mapping)
A tool that lets you work with databases using code instead of raw SQL
Entity Framework, Hibernate, SQLAlchemy
Examples of ORMs
User Story
A simple feature description from a user's point of view. Format: 'As a [user], I want [feature] so that [benefit]'
Acceptance Criteria
Conditions that define when a story is complete
Estimating
Deciding how much effort a story will take (story points, T-shirt sizes)
Troubleshooting
Finding and fixing bugs or issues
Researching
Looking up info to solve problems (docs, forums, etc.)
Analysis
Understanding system behavior, logs, or data to inform action
Test Case
Step-by-step test instructions for a feature
Test Automation
Writing code/scripts that test features automatically
Knowledgebase
A collection of helpful guides, FAQs, and how-tos
Technical Documentation
Explains how the code or system works
User Manual
Explains how to use the product
API Docs
Describes how to use your web service or API
Modern JavaScript Frameworks
React, Vue, Angular, Svelte
SPA (Single Page Application)
Loads one page and updates dynamically
Angular
A TypeScript-based frontend framework for building SPAs
.NET Core
A Microsoft framework for building fast, cross-platform apps (now just .NET)
ASP.NET Core
Used for building web APIs and web apps in .NET
Web Service
A backend system that provides data/functions over the internet (usually via an API)
Securing a Web Service
Using authentication, authorization, HTTPS, rate limiting, etc.