PROGRAMMING METHODS AND TESTING Flashcards

SKILLS

1
Q

NAME TYPES OF PROGRAMMING METHODS

A

AGILE
WATERFALL

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

THIS PROGRAMING METHOD INCLUDES “SPRINTS” QUICKLY RESPONDS TO EMERGING NEEDS
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.

A

AGILE

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

THIS PROGRAMING METHOD IS SYSTEM DEVELOPMENT SEQUENTIAL. NEXT STAGE NOT STARTED UNTIL CURRENT STAGE COMPLETE
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.

A

WATERFALL

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

METHOD WITHIN DEVELOPMENT PROCESS GUARENTEE RELIABLE OPERATION OF PRODUCT

A

QUALITY ASSURANCE

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

NAME TYPES OF SOFTWARE TESTING

A

DYNAMIC WHICH INCLUEDS BLACK-BOX AND WHITE BOX
STATIC
UNIT TESTING
INTEGRATION TESTING
SYSTEM TESTING
USER ACCEPTANCE

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

INPUT/OUTPUT TYPE OF DYNAMIC TESTING INTERNAL WORKINGS UNKNOWN

A

BLACK-BOX TESTING

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

INPUT/OUTPUT TYPE OF DYNAMIC TESTING INTERNAL WORKINGS KNOWN

A

WHITE-BOX TESTING

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

SOFTWARE TESTED WITHOUT EXECUTING CODE REVIEW AND STATIC ANALYSIS

A

STATIC TESTING

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

SOFTWARE TESTING USING INDIVIDUAL COMPONETS OF CODE

A

UNIT TESTING

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

THIS STAGE OF SOFTWARE TESTING MAY ONLY BE DONE AFTER UNIT TESTING IS COMPLETE IT COMBINES UNITS INTO INTEGRATED SUBSYSTEMS

A

INTEGRATION TESTING

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

THIS STAGE OF SOFTWARE TESTING MAY ONLY BE DONE AFTER INTEGRATION TESTING IS COMPLETE SUBSYSTEMS ARE COMBINED TO TEST ENTIRE SYSTEM

A

SYSTEM TESTING

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

THIS STAGE OF SOFTWARE TESTING INVOLVED TRAINED USERS CONDUCTING INDEPENDENT TESTING

A

USER ACCEPTANCE

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

COMPONENTS OF HIGH QUALITY SOFTWARE SYSTEMS

A

EASY TO LEARN
PERFORM QUICKLY
MEET USER NEEDS
OPERATES SAFELY
RELIABLE

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

ERROR IN SOFTWARE THAT IF NOT REMOVED COULD CAUSE SYSTEM TO FAIL

A

SOFTWARE DEFECT

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

The degree to which a software product meets the needs of its users.

A

SOFTWARE QUALITY

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

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.

A

SOFTWARE DEVELOPMENT METHODOGLY

17
Q

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.

A

QUALITY MANAGEMENT

18
Q

A set of interrelated components—including hardware, software, databases, networks, people, and procedures—that collects and processes data and disseminates the output.

A

BUSINESS INFORMATION SYSTEMS

19
Q

A type of business information system used to improve decision making in a variety of industries.

A

DSS DECISION SUPPORT SYSTEM

20
Q

The liability of manufacturers, sellers, lessors, and others for injuries caused by defective products.

A

PRODUCT LIABILITY

21
Q

NAME TYPES OF SOFTWARE PRODUCT LIABILITY CLAIMS

A

STRICT LIABILITY
NEGLIGENCE
CONTRIBUTORY NEGLIGENCE
WARRANTY
BREACH OF WARRANTY

22
Q

A situation in which the defendant is held responsible for injuring another person, regardless of negligence or intent.

A

STRICT LIABILITY

23
Q

HARMFUL DEFECTS THAT COULD HAVE BEEN DETECTED AND CORRECTED THROUGOH “REASONABLE” SOFTWARE DEVELOPMENT PRACTICES

A

NEGLIGENCE

24
Q

When the plaintiffs’ own actions contributed to their injuries.

A

CONTRIBUTORY NEGLIGENCE

25
Q

Assures buyers or lessees that a product meets certain standards of quality.

26
Q

When a product fails to meet the terms of its warranty.

A

BREACH OF WARRANTY

27
Q

Collection of best practices that help organizations improve their processes.

A

CMMI - CAPABILITY MATURITY MODEL INTEGRATION

28
Q

A specific application of CMMI frequently used to assess and improve software development practices.

29
Q

A system whose failure may cause human injury or death.

A

SAFETY CRITICAL SYSTEMS

30
Q

Someone who has explicit responsibility for ensuring that a system will operate in a safe and reliable manner while meeting its users’ needs.

A

SYSTEM SAFETY ENGINEER

31
Q

A logging and monitoring system used by safety engineers to track hazards from a project’s start to its finish.

A

HAZARD LOG