Upgrade to remove ads
Only ₩37,125/year
- Science
- Computer Science
- Software Engineering
-
Flashcards
-
Learn
-
Test
-
Match
-
Flashcards
-
Learn
-
Test
-
Match
Terms in this set (45)
acceptance
When an organization decides to accept a risk because the cost of avoiding the risk outweighs the potential loss of the risk. A decision to accept a risk can be extremely difficult and controversial when dealing with safety-critical systems because making that determination involves forming personal judgments about the value of human life, assessing potential liability in case of an accident, evaluating the potential impact on the surrounding natural environment, and estimating the system's costs and benefits.
agile development
A software development methodology in which a system is developed in
iterations lasting from one to four weeks. Unlike the waterfall system development model,
agile
development accepts the fact that system requirements are evolving and cannot be fully
understood or defined at the start of the project.
annualized loss expectancy (ALE)
The estimated loss from a potential risk event over the course of a year. The following equation is used to calculate the annual loss expectancy: ARO ×
SLE = ALE. Where ARO is the annualized rate of occurrence, an estimate of the
probability that this event will occur over the course of a year and SLE is the single loss expectancy, the estimated loss that would be incurred if the event happens.
annualized rate of occurrence (ARO)
An estimate of the probability that a risk event will occur over the course of a year.
avoidance
The elimination of a vulnerability that gives rise to a particular risk in order to avoid the risk altogether. This is the most effective solution, but often not possible due to organizational requirements and factors beyond an organization's control.
best practice
A method or technique that has consistently shown results superior to those
achieved with other means, and that is used as a benchmark within a particular
industry.
black-box testing
A type of dynamic testing that involves viewing the software unit as a device
that has expected input and output behaviors but whose internal workings are unknown (a black
box).
breach of warranty
When a product fails to meet the terms of its warranty.
business information system
A set of interrelated components—including hardware, software,
databases, networks, people, and procedures—that collects and processes data and disseminates
the output.
Capability Maturity Model Integration (CMMI) models
A collection of best practices that help organizations improve their processes
CMMI-Development (CMMI-DEV)
A specific application of CMMI frequently used to assess and improve software development practices.
contributory negligence
When the plaintiffs' own actions contributed to their injuries.
decision support system (DSS)
A type of business information system used to improve decision making in a variety of industries.
deliverable
Products developed during various stages of the development process, including statements of requirements, flowcharts, and user documentation.
dynamic testing
A QA process that tests the code for a completed unit of software by actually
entering test data and comparing the
results to the expected results.
failure mode
A description of how a product or process could fail to perform the desired
functions described by the customer.
failure mode and effects analysis (FMEA)
An important technique used to develop ISO 9000-
compliant quality systems by both evaluating reliability and determining
the effects of system
and equipment failures.
hazard log
A logging and monitoring system used by safety engineers to track hazards from a project's start to its finish.
high-quality software system
Systems that are easy to learn and use because they perform quickly and efficiently; they meet their users' needs; and they operate safely and reliably so that system downtime is kept to a minimum
integration testing
Software testing done after successful unit testing, where the software units
are combined into an integrated subsystem that undergoes rigorous testing to ensure that the linkages among the various subsystems work successfully
ISO 9001 family of standards
A set of standards written to be served as a guide to quality products, services, and management. It provides a set of standardized requirements for a quality management system.
mitigation
The reduction in either the likelihood or the impact of the occurrence of a risk
N-version programming
An approach to minimizing the impact of software errors by independently implementing the same set of user requirements N times (where N could be 2, 3, 4 or more); the N-versions of software are run in parallel; and, if a difference is found, a "voting algorithm" is executed to determine which result to use.
product liability
The liability of manufacturers, sellers, lessors, and others for injuries caused by defective products.
quality assurance (QA)
Methods within the development process that are designed to guarantee reliable operation of a product.
quality management
The defining, measuring, and refining of the quality of the development
process and the products developed during its various stages. The objective of
quality
management is to help developers deliver high-quality systems that meet the needs of their users.
redundancy
The provision of multiple interchangeable components to perform a single function in order to cope with failures and errors.
reliability
A measure of the rate of failure in a system that would render it unusable over its expected lifetime
risk
The potential of gaining or losing something of value. Risk can be quantified by three elements: a risk event, the probability of the event happening, and the impact (positive or
negative) on the business outcome if the risk does actually occur.
risk management
The process of
identifying, monitoring, and limiting risks to a level that an
organization is willing to accept.
safety-critical system
A system whose failure may cause human injury or death.
single loss expectancy (SLE)
The estimated loss that would be incurred if a risk event occurs.
software defect
Any error that, if not removed, could cause a software system to fail to meet its users' needs.
software development methodology
A standard, proven work process that enables systems analysts, programmers, project managers, and others to make controlled and orderly progress in
developing high-quality software.
software quality
The degree to which a software product meets the needs of its users.
static testing
A software-testing technique in which software is tested without actually executing the code. It consists of two steps—review and static analysis.
strict liability
A situation in which the defendant is held responsible for injuring another person, regardless of negligence or intent.
system safety engineer
Someone who has explicit responsibility for the system's safety
system testing
Software testing done after successful integration testing, where the various
subsystems are combined to test the entire system as a complete
entity.
transference
A risk management strategy in which the risk, should it happen, does not rest solely on one individual or organization. For example, a common way to accomplish risk
transference is for an individual or an organization to purchase insurance, such as auto or
business liability insurance. Another way to transfer risk is to outsource the risk by contracting with a third party to manage the
risk.
unit testing
A software-testing technique that involves testing individual components of code
(subroutines, modules, and programs) to verify that each unit performs as intended.
user acceptance testing
Software testing done independently by trained end users to ensure the
system operates as expected.
warranty
Assures buyers or lessees that a product meets certain standards of quality.
waterfall system development model
A software development methodology that involves a sequential, multistage system development process in which development of the next stage of the system cannot begin until the results of the current stage are approved or modified as necessary.
white-box testing
A type of dynamic testing that treats the software unit as a device that has
expected input and output behaviors but whose internal workings, unlike the unit in black-box
testing, are known.
Ethics and tech - ch 7
30 terms
Vrs3136
Ethics In Information Technology - Chapter 7
36 terms
Blyzzards12
CH 7
33 terms
BrittSchultz
Comp Ethics Ch 7
32 terms
zloty
Other sets by this creatorLaw 201 Exam 1
35 terms
winsunita
Final Exam Vocab
109 terms
winsunita
Expresiones problemáticas Final Exam
58 terms
winsunita
Expresiones problemáticas (set 1)
34 terms
winsunita
Verified questions
COMPUTER SCIENCE
A painting company has determined that for every 112 square feet of wall space, one gallon of paint and eight hours of labor will be required. The company charges $35.00 per hour for labor. Write a program that asks the user to enter the square feet of wall space to be painted and the price of the paint per gallon. The program should display the following data:$ $$ \begin{matrix} \text{• The number of gallons of paint required}\\ \text{• The hours of labor required}\\ \text{• The cost of the paint}\\ \text{• The labor charges}\\ \text{• The total cost of the paint job}\\ \end{matrix} $$ $
Verified answer
COMPUTER SCIENCE
The ______ library function returns the exponential function of a number.
Verified answer
COMPUTER SCIENCE
T F The do-while loop is a pretest loop.
Verified answer
COMPUTER SCIENCE
Modify the Dice Poker program, include any or all of the following features: (a) Splash Screen. When the program first fires up, have it print a short introductory message about the program and buttons for "Lets Play" and "Exit". The main interface shouldn't appear unless the user selects "Lets Play." (b) Add a help button that pops up another window displaying the rules of the game (the payoffs table is the most important part). (c) Add a high score feature. The program should keep track of the 10 best scores. When a user quits with a good enough score, he/she is invited to type in a name for the list. The list should be printed in the splash screen when the program first runs. The high-scores list will have to be stored in a file so that it persists between program invocations.
Verified answer
Recommended textbook solutionsEngineering Electromagnetics
8th EditionJohn Buck, William Hayt
483 solutions
Introduction to the Theory of Computation
3rd EditionMichael Sipser
389 solutions
Computer Organization and Design MIPS Edition: The Hardware/Software Interface
5th EditionDavid A. Patterson, John L. Hennessy
220 solutions
Python for Everyone
2nd EditionCay S. Horstmann, Rance D. Necaise
730 solutions
Other Quizlet setsHealth exam 1st quarter
20 terms
brynnkelso23PLUS
Erik Hinson - Create Vectors 1 Quizlet
12 terms
ewh05
KIN 310 Test 1
122 terms
robnagelyPLUS
Ch. 7
27 terms
dorygh
Related questionsQUESTION
(FQ6) A structured technique for identifying risks which requires participants to rank and prioritize ideas in round-robin fashion is most closely associated with:
3 answers
QUESTION
Which UML diagram is designed to show a system's layout, showing which pieces of software run on what pieces of hardware?
5 answers
QUESTION
For implementing ERP systems, the first task is to create a model of current business procedures and practices, which is called the as-is model. T/F
2 answers
QUESTION
2. Name two important factors to consider for the business to see success( Principle 1)
5 answers