1/65
Comprehensive vocabulary flashcards covering SDLC, requirement engineering, delivery models, Scrum, internet networking, cloud computing, HTML semantics, and web architecture based on ISTM 210 lecture notes.
Systems Development Life Cycle (SDLC)
The end-to-end framework for building an information system, consisting of seven sequential phases: Planning, Analysis, Design, Development, Testing, Implementation, and Maintenance.
Feasibility Analysis
An evaluation conducted during the SDLC Planning phase to determine if a project is viable across economic, technical, operational, legal, and schedule dimensions.
Error Amplification
The principle that mistakes made in early SDLC phases carry over into every subsequent phase, becoming increasingly expensive and difficult to fix at each handoff.
Unit Testing
The first level of software testing that checks an individual, isolated piece of code to ensure it functions as specified.
Integration Testing
Testing level that verifies whether separate software modules or components operate correctly when combined together.
System Testing
Testing the entire integrated software system against all functional and non-functional requirements, including load, capacity, and security testing.
User Acceptance Testing (UAT)
The final testing phase where real end users perform authentic tasks to confirm the system meets business requirements prior to sign-off.
Direct Implementation (Big-Bang)
A rollout strategy where all users switch to the new system at once; it is the fastest transition method, but a single system failure impacts everyone immediately.
Parallel Implementation
A rollout strategy where the legacy system and the new system operate side by side simultaneously, allowing outputs to be compared and offering a fallback at the cost of doubled work.
Pilot Implementation
A rollout approach where the complete system is released to a single site or department first, containing failures and gathering live user feedback before broader rollout.
Phased Implementation
A gradual deployment approach where subsystems or features are introduced in stages over time, requiring old and new systems to coexist.
Say-Do Gap
The difference between how workers verbally describe their work and what they actually do, often caused by automated habits, omitted workarounds, and unrecorded offline steps.
As-Is vs. To-Be Analysis
Documenting how a business process functions today (the as-is) before designing the future process (the to-be); the difference between them defines requirements, training needs, and technical changes.
Business Analyst
The intermediary between business stakeholders and technical developers who interviews users, converts needs into testable requirements, and translates technical constraints into business language.
Functional Requirement
A specification defining what a system does, including an action, feature, or calculation (e.g., emailing an order receipt).
Non-Functional Requirement
A quality attribute defining how well a system performs under specified conditions, covering criteria such as response time, uptime, security, and usability.
Traceability
The practice of linking each requirement backward to its business origin and forward to the corresponding design documents, code files, and test cases that verify delivery.
User Story
An agile requirement expressed as: 'As a [role], I want [capability], so that [benefit],' supplemented with acceptance criteria while omitting technical design choices.
MoSCoW Prioritization
A requirement prioritization technique dividing features into Must (mandatory for release), Should (important with workarounds), Could (desirable; cut first), and Won't this time.
Waterfall Delivery
A linear, plan-driven delivery model where phases execute sequentially once; ideal when requirements are thoroughly understood and late modifications would be costly, hazardous, or legally restricted.
Agile Delivery
An iterative delivery methodology suited for emerging requirements, delivering small working software increments in short cycles with continuous testing and customer feedback.
Agile Theater
A situation where a software team adopts agile terminology and meetings (such as daily standups and Kanban boards) but fails to ship working software or alter its backlog based on feedback.
Minimum Viable Product (MVP)
The smallest functional release of a system capable of performing core tasks, built to validate assumptions and gather user feedback with minimal effort.
Product Owner
The Scrum role responsible for managing and ordering the product backlog, deciding what the team builds without dictating technical execution.
Scrum Master
A servant-leader who facilitates Scrum practices, removes blockers, and protects team focus without managing personnel or assigning daily tasks.
Sprint Review
An end-of-sprint event where the Scrum team demonstrates the newly built increment to stakeholders to gather feedback that alters the product backlog.
Sprint Retrospective
An internal Scrum meeting where the team reflects on team dynamics, processes, and tools to identify actionable improvements for the next sprint.
Definition of Done
A shared, formal checklist of quality standards and technical criteria that an increment must satisfy before being considered complete.
Sourcing (Make vs. Build vs. Buy)
The strategic selection of who produces a solution: internal staff creating custom software (Make), an external contractor building to specification (Build), or purchasing a commercial software package (Buy).
Packet
A unit of data formatted for network transmission, consisting of a header (containing source and destination IP addresses) and a payload (the actual data).
Transmission Control Protocol (TCP)
A transport layer protocol that sequences packets, detects dropped packets, requests retransmissions, and reassembles them in order at the destination.
Internet Protocol (IP)
The network protocol that handles addressing and routing individual packets across interconnected networks from source to destination.
Packet Switching
A network transmission paradigm where packets traverse shared infrastructure independently along dynamic paths rather than over a dedicated physical circuit.
Domain Name System (DNS)
The internet's distributed lookup service that translates human-readable domain names into numerical IP addresses.
Latency
The time required for a packet to make a round trip across a network, measured in milliseconds.
Bandwidth
The maximum volume of data that can pass through a network connection per unit of time, typically expressed in megabits per second (Mbps).
Ping
A command-line diagnostic tool that measures round-trip time in milliseconds to confirm if a remote host is reachable across the network.
Registered Domain
The authoritative domain name identifying the site owner, situated directly before the public top-level domain suffix (e.g., 'example.com' in 'store.example.com').
Query String
The portion of a URL following a question mark containing key-value pairs (e.g., '?color=red') sent to the web server; visible in browser history and server logs.
GET Request
An HTTP method used to retrieve resources from a server without modifying state; request data is sent within the URL.
POST Request
An HTTP method that transmits data in the request body to modify server data or execute state-changing actions such as transactions.
HTTP Status Codes
Three-digit numeric server response categories indicating the outcome of a request: 2xx (Success), 3xx (Redirection), 4xx (Client Error), and 5xx (Server Error).
Cookie
A small string of data including a session identifier saved by the browser to preserve user state and session tracking across stateless HTTP connections.
Content Delivery Network (CDN)
A geographically distributed network of proxy servers caching static files near users to accelerate load times and reduce origin server load.
HTTPS
An encrypted communication protocol combining HTTP with TLS/SSL encryption to secure data in transit and authenticate the remote server using a digital certificate.
Infrastructure as a Service (IaaS)
A cloud service model where the customer rents virtual machines and manages the operating system, middleware, and application stack.
Platform as a Service (PaaS)
A cloud computing tier where the vendor manages hardware, operating systems, and server infrastructure while the customer focuses solely on deploying application code.
Software as a Service (SaaS)
A cloud delivery model where complete, vendor-managed business applications are consumed over the internet (e.g., cloud email or web office suites).
Shared Responsibility Model
The cloud security framework establishing that while the vendor manages infrastructure security, the customer always retains responsibility for credentials, data protection, and user permissions.
Service Level Agreement (SLA)
A contract specifying a cloud provider's measurable commitments (such as uptime percentage) and contractual remedies, typically provided via service credits.
Virtualization
The partitioning of a single physical server into multiple isolated virtual machines (VMs) running independent operating systems using a hypervisor.
Correlated Failure
A major risk in virtualized environments where a single hardware malfunction causes every virtual machine residing on that physical host to fail simultaneously.
Recovery Time Objective (RTO)
The maximum acceptable duration of system downtime that an organization can tolerate following an unplanned service disruption.
Recovery Point Objective (RPO)
The maximum acceptable volume of recent data loss, expressed in time backward from an incident, that an organization is prepared to lose.
3-2-1 Backup Rule
A data continuity rule mandating three separate copies of data stored on two distinct media types, with at least one copy stored off-site.
HTML Element
A document component composed of an opening tag, wrapped content, and a closing tag (e.g., '
Hello
').Empty (Void) Element
An HTML tag containing no closing tag and no enclosed content (e.g., '
', '
HTML Attribute
Key-value configuration data declared inside the opening HTML tag (e.g., 'name="value"') to modify element behavior or provide metadata.
Nesting Rule
The HTML syntactic requirement that elements opened inside other elements must be closed in reverse order of opening before closing the parent element.
'
' is an invisible container for page metadata and titles placed before '', whereas 'Relative Path
A file address written in relation to the current directory of the document containing the link (e.g., 'images/latte.jpg' or '../about.html').
Root-Relative Path
A file path starting with a forward slash ('/') that locates files from the website's root folder regardless of the current document's directory location.
alt Attribute
An attribute of the '' element providing text equivalents for screen readers and search engines; leaving it empty ('alt=""') identifies an image as purely decorative.
Form Action and Method
Attributes of the '
Application Programming Interface (API)
A defined interface of documented functions and request formats (typically over HTTP returning JSON) allowing software applications to interact with external services programmatically.
Client-Side vs. Server-Side Validation
The security boundary where browser-based validation checks provide fast user feedback but can be bypassed, requiring the web server to independently validate and sanitize all submitted data.