ISTM 210 Key Terms

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

1/81

flashcard set

Earn XP

Description and Tags

Chapter Review QUIZZES

82 Terms

1
New cards

Systems Development Life Cycle (SDLC)

End-to-end process for developing an information system, from planning through maintenance; includes hardware, people, and processes.

2
New cards

Seven SDLC Phases

Planning, Analysis, Design, Development, Testing, Implementation, Maintenance.

3
New cards

Planning Phase Output

Formal management approval to proceed and a high-level requirements matrix.

4
New cards

Analysis Phase Output

Requirements definition document.

5
New cards

Design Phase Output

Detailed models and specifications.

6
New cards

Development Phase Output

Working prototype.

7
New cards

As-Is Process

How a process actually works today, including hidden steps and workarounds.

8
New cards

To-Be Process

How a process should work after the change.

9
New cards

Why Document As-Is Before To-Be?

To understand the real current process and identify gaps that become requirements.

10
New cards

Waterfall Development

Runs phases once in strict order with heavy upfront planning; best suited to stable, fixed-scope requirements.

11
New cards

Agile Development

Repeats work in short sprints with continuous feedback; adapts to changing requirements.

12
New cards

Choosing a Development Method

Ask how stable the requirements are and how expensive a late change would be.

13
New cards

Agile Trade-Off

Flexibility and less discarded work, but recurring planning, demos, client involvement, backlog decisions, and possible rework.

14
New cards

Testable Requirement

A requirement with measurable conditions that allow a test to determine whether it is satisfied.

15
New cards

Functional Requirement

Specifies what the system does, such as calculating sales tax.

16
New cards

Non-Functional Requirement

Specifies how well the system performs, such as response time, capacity, or uptime.

17
New cards

User Story Format

As a [role], I want [capability], so that [benefit].

18
New cards

Acceptance Criteria

Specific, checkable conditions that determine whether a user story is satisfied.

19
New cards

Say-Do Gap

The difference between how people describe their work and how they actually perform it.

20
New cards

MoSCoW Prioritization

Must have, Should have, Could have, Won't have this time.

21
New cards

Traceability

Links each requirement to its source or process gap and the future test that verifies it.

22
New cards

Packet Switching

Breaks messages into independently routed packets carrying destination addresses and sequence numbers; packets are reassembled at the destination.

23
New cards

Advantages of Packet Switching

Shares network capacity across conversations and allows packets to route around failures.

24
New cards

TCP

Provides reliable delivery by numbering and acknowledging packets, retransmitting missing ones, and reassembling data.

25
New cards

DNS Lookup

Translates a domain name into the address needed to reach its destination through a chain of queries.

26
New cards

DNS Caching

Stores DNS answers temporarily, so old and new records may coexist for hours after a change.

27
New cards

Network Troubleshooting Questions

Do other devices work? Can anything connect? Does the router report an upstream outage? Do all sites fail?

28
New cards

HTTPS

Encrypts content in transit but does not hide all connection metadata or guarantee a website is trustworthy.

29
New cards

Facebook Outage

Routing announcements were withdrawn, making Facebook's networks and DNS servers unreachable even though its servers were still running.

30
New cards

Dynamic Website Request Path

DNS → internet routing → optional firewall/gateway → web application → optional database.

31
New cards

Actual Domain Owner in paypal.com.secure-billing.net

secure-billing.net; the registrable domain identifies the actual domain owner.

32
New cards

HTTP GET

Requests a representation and is intended to be safe.

33
New cards

HTTP POST

Submits data for processing.

34
New cards

HTTP 2xx

Status codes indicating success.

35
New cards

HTTP 3xx

Status codes indicating redirection.

36
New cards

HTTP 4xx

Status codes indicating the request was rejected or could not be fulfilled.

37
New cards

HTTP 5xx

Status codes indicating a server failure while handling an apparently valid request.

38
New cards

HTTP Statelessness

HTTP does not automatically retain request context between separate exchanges.

39
New cards

Cookie and Session

The browser stores a session identifier in a cookie; the server uses it to recognize later requests.

40
New cards

Infrastructure as a Service (IaaS)

Rent virtual machines and storage; the customer manages the operating system and higher layers.

41
New cards

Platform as a Service (PaaS)

The provider manages infrastructure and runtime, letting the customer focus on application code.

42
New cards

Software as a Service (SaaS)

The provider runs and delivers a complete application.

43
New cards

Public Cloud

Cloud infrastructure shared across customers; useful for workloads such as spiky ticket sales.

44
New cards

Private Cloud or Isolated Deployment

Dedicated or isolated infrastructure suited to requirements such as sensitive hospital records.

45
New cards

Hybrid Cloud

Combines environments, such as a legacy factory system with a new mobile application.

46
New cards

Reserved Cloud Capacity

Capacity planned for predictable, year-round baseline demand.

47
New cards

On-Demand Cloud Capacity

Flexible capacity used to handle demand spikes.

48
New cards

Spot Cloud Capacity

Discounted, interruptible capacity suited to work that can tolerate interruptions.

49
New cards

Cloud Computing Benefits

Faster provisioning, elasticity, and global reach.

50
New cards

Cloud Computing Trade-Offs

Recurring costs, less control over incident timing, and concentration risk.

51
New cards

Recovery Time Objective (RTO)

How long the business can afford to be down.

52
New cards

Recovery Point Objective (RPO)

How much recent data the business can afford to lose.

53
New cards
HTML Structure
HTML declares what each piece of content is, not how it looks.
54
New cards
Structural HTML Elements
h1 = heading; p = paragraph; ul/li = list and list items; header/main = page regions.
55
New cards
Semantic Heading
A heading marked in HTML that contributes to the page outline, not just text that looks large.
56
New cards
HTML Validation
Checks HTML for syntax errors, mis-nested or unclosed tags, and missing required attributes.
57
New cards
href Attribute
Specifies a link destination, such as an absolute URL, relative path, or on-page anchor.
58
New cards
Absolute URL
A complete address pointing to a destination on another site.
59
New cards
Relative Path
A path to a file or page based on the current file's folder.
60
New cards
On-Page Anchor (#id)
A link to an element with a matching ID on the same page.
61
New cards

Descriptive Link Text

Text that clearly communicates where a link leads, helpful for screen readers; better than vague text like "click here."

62
New cards
alt Attribute
Text read in place of an image by screen readers and used by search engines to interpret the image.
63
New cards
Relative Path: about.html
Refers to a file in the same folder as the current file.
64
New cards
Relative Path: ../
Goes up one folder to a parent directory.
65
New cards
Relative Path: images/logo.png
Goes down into the images subfolder to locate logo.png.
66
New cards
Why Relative Paths Matter
Incorrect paths can create dead links or broken images.
67
New cards

Connecting a Label to a Field

Match the label's for attribute to the field's id attribute.

68
New cards
HTML Input Type
Specifies the kind of data a field accepts, such as email, number, or date.
69
New cards
Form Field name Attribute
Provides the key in the name/value pair submitted with the form.
70
New cards
select Element
Provides a control for choosing from constrained, predefined options.
71
New cards
textarea Element
Provides a control for entering free-form or longer text.
72
New cards
HTML Table
Uses elements such as table, tr, th, and td to organize related data into rows and columns.
73
New cards
Why Avoid Tables for Page Layout?
Layout tables can confuse screen readers and break on small screens.
74
New cards
HTML Element h1
Marks a top-level heading in the document structure.
75
New cards
HTML Element p
Marks a paragraph of text.
76
New cards
HTML Element ul
Defines an unordered list containing list items.
77
New cards

HTML Element li

Defines an individual list item; <ul> and <ol> must only directly contain <li>

78
New cards
Browser, Screen Reader, Crawler, Script
Four types of tools that benefit from correct HTML structure and nesting.
79
New cards
HTML Accessibility: Links
Link text should explain the destination because screen reader users may hear links without surrounding context.
80
New cards
HTML Accessibility: Images
Alt text should explain an image's meaning in context; decorative images should use empty alt text.
81
New cards
Form Control Selection
Use an appropriate input type for the data, select for fixed choices, and textarea for free text.
82
New cards
HTML Table Elements
table = table; tr = row; th = header cell; td = data cell.