ISTM 210 Midterm Review: Systems Development, Networking, Cloud, HTML, and Web Architecture

0.0(0)
Studied by 0 people
call kaiCall Kai
learnLearn
examPractice Test
spaced repetitionSpaced Repetition
heart puzzleMatch
flashcardsFlashcards
GameKnowt Play
full-widthPodcast
1
Card Sorting

1/65

flashcard set

Earn XP

Description and Tags

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.

66 Terms

1
New cards

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.

2
New cards

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.

3
New cards

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.

4
New cards

Unit Testing

The first level of software testing that checks an individual, isolated piece of code to ensure it functions as specified.

5
New cards

Integration Testing

Testing level that verifies whether separate software modules or components operate correctly when combined together.

6
New cards

System Testing

Testing the entire integrated software system against all functional and non-functional requirements, including load, capacity, and security testing.

7
New cards

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.

8
New cards

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.

9
New cards

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.

10
New cards

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.

11
New cards

Phased Implementation

A gradual deployment approach where subsystems or features are introduced in stages over time, requiring old and new systems to coexist.

12
New cards

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.

13
New cards

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.

14
New cards

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.

15
New cards

Functional Requirement

A specification defining what a system does, including an action, feature, or calculation (e.g., emailing an order receipt).

16
New cards

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.

17
New cards

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.

18
New cards

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.

19
New cards

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.

20
New cards

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.

21
New cards

Agile Delivery

An iterative delivery methodology suited for emerging requirements, delivering small working software increments in short cycles with continuous testing and customer feedback.

22
New cards

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.

23
New cards

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.

24
New cards

Product Owner

The Scrum role responsible for managing and ordering the product backlog, deciding what the team builds without dictating technical execution.

25
New cards

Scrum Master

A servant-leader who facilitates Scrum practices, removes blockers, and protects team focus without managing personnel or assigning daily tasks.

26
New cards

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.

27
New cards

Sprint Retrospective

An internal Scrum meeting where the team reflects on team dynamics, processes, and tools to identify actionable improvements for the next sprint.

28
New cards

Definition of Done

A shared, formal checklist of quality standards and technical criteria that an increment must satisfy before being considered complete.

29
New cards

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).

30
New cards

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).

31
New cards

Transmission Control Protocol (TCP)

A transport layer protocol that sequences packets, detects dropped packets, requests retransmissions, and reassembles them in order at the destination.

32
New cards

Internet Protocol (IP)

The network protocol that handles addressing and routing individual packets across interconnected networks from source to destination.

33
New cards

Packet Switching

A network transmission paradigm where packets traverse shared infrastructure independently along dynamic paths rather than over a dedicated physical circuit.

34
New cards

Domain Name System (DNS)

The internet's distributed lookup service that translates human-readable domain names into numerical IP addresses.

35
New cards

Latency

The time required for a packet to make a round trip across a network, measured in milliseconds.

36
New cards

Bandwidth

The maximum volume of data that can pass through a network connection per unit of time, typically expressed in megabits per second (Mbps).

37
New cards

Ping

A command-line diagnostic tool that measures round-trip time in milliseconds to confirm if a remote host is reachable across the network.

38
New cards

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').

39
New cards

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.

40
New cards

GET Request

An HTTP method used to retrieve resources from a server without modifying state; request data is sent within the URL.

41
New cards

POST Request

An HTTP method that transmits data in the request body to modify server data or execute state-changing actions such as transactions.

42
New cards

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).

43
New cards

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.

44
New cards

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.

45
New cards

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.

46
New cards

Infrastructure as a Service (IaaS)

A cloud service model where the customer rents virtual machines and manages the operating system, middleware, and application stack.

47
New cards

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.

48
New cards

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).

49
New cards

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.

50
New cards

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.

51
New cards

Virtualization

The partitioning of a single physical server into multiple isolated virtual machines (VMs) running independent operating systems using a hypervisor.

52
New cards

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.

53
New cards

Recovery Time Objective (RTO)

The maximum acceptable duration of system downtime that an organization can tolerate following an unplanned service disruption.

54
New cards

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.

55
New cards

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.

56
New cards

HTML Element

A document component composed of an opening tag, wrapped content, and a closing tag (e.g., '

Hello

').


57
New cards

Empty (Void) Element

An HTML tag containing no closing tag and no enclosed content (e.g., '
', '


', '').

58
New cards

HTML Attribute

Key-value configuration data declared inside the opening HTML tag (e.g., 'name="value"') to modify element behavior or provide metadata.

59
New cards

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.

60
New cards
vs.

'' is an invisible container for page metadata and titles placed before '', whereas '

' is a visible introductory region contained within ''.

61
New cards

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').

62
New cards

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.

63
New cards

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.

64
New cards

Form Action and Method

Attributes of the '

' element where 'action' specifies the destination server URL that processes input data and 'method' determines whether data is submitted via 'GET' or 'POST'.

65
New cards

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.

66
New cards

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.