SUBJECTS
|
BROWSE
|
CAREER CENTER
|
POPULAR
|
JOIN
|
LOGIN
Business Skills
|
Soft Skills
|
Basic Literacy
|
Certifications
About
|
Help
|
Privacy
|
Terms
|
Email
Search
Test your basic knowledge |
Software Engineering Vocab
Start Test
Study First
Subjects
:
engineering
,
it-skills
Instructions:
Answer 50 questions in 15 minutes.
If you are not ready to take this test, you can
study here
.
Match each statement with the correct term.
Don't refresh. All questions and answers are randomly picked and ordered every time you load a test.
This is a study tool. The 3 wrong answers for each question are randomly chosen from answers to other questions. So, you might find at times the answers obvious, but you will see it re-enforces your understanding as you take the test each time.
1. 1st step of requirements gathering
Refactoring
Elicitation
SRS Documentation
Programming syntax
2. Each possible path through the code is covered
path
copyright
jquery
Specification
3. The process of attempting to optimise the read performance of a database by adding redundant data or by grouping data
Large class
Denormalization
Dijkstra's law
conflict
4. Simple Object Access Protocol. Specification for exchanging structured information. Uses XML. Usually relies on other Application Layer protocols (HTTP - SMTP)
Usability testing
SOAP
Feasibility
conflict
5. (smell) method has too many statements - loops or variables
Large class
long method
Elicitation
Liskov substitution principle
6. 2nd step of requirements gathering
Casual use case
architectural design
Phase
Analysis...
7. (smell) many parameters are being passed into a method
Security testing
unit testing
long method
long parameter list
8. Reusable - abstract 'blocks' of design
Scrum (Agile software development)
Feasibility
Design pattern
code smell
9. Test whether or not tasks can be accomplished efficiently by all levels of users
Code Quality
Non - functional Requirements
Usability testing
Analysis...
10. 3rd step of requirements gathering
Specification
Design pattern
Parser
white box testing
11. Delaying the creation of an object - calculation of a value or another expensive process until first needed.
Database normalization
First- class citizen
Lazy initialization or Lazy loading (Design pattern)
SOP
12. The rights governing the ownership and disposition of technology
Association
use case
intellectual property
Parser
13. Lack of errors in code - readability etc
a refactoring
Design Patterns
Code Quality
code smell
14. (smell) One class delegates all of its requests to another class
Erich Gamma - Richard Helm - Ralph Johnson - John Vlissides
middle man
Delegation
software quality
15. Each team member given set of features to work on
feature- driven development
Anonymous function
Performance testing
WSDL
16. Executes system in a manner that demands abnormal amounts of resources
Stress testing
Parser
code quality
Data classes
17. (smell) A class whose only purpose is to hold data
Code Quality
Security testing
Data classes
Specification
18. Wrote the book Design Patterns: Elements of Reusable Object-Oriented Software.
Erich Gamma - Richard Helm - Ralph Johnson - John Vlissides
Stakeholders
Software Quality
Delegation
19. Testing tactic based on whether inputs and outputs match up for required functionality
Analysis...
black box testing
comments
Feasibility
20. Contract between inventor - assignee and state giving a time and geographically limited monopoly
patent
shotgun surgery
Validation
Association
21. The process of eliminating data redundancy by ensuring that tables in a database pertain to a single topic
Database normalization
system testing
regression testing
Programming style
22. (smell) code is repeated in multiple places
duplicated code
Lambda
conflict
patent
23. Part of compiler reads the sequence of characters and outputs a sequence of lexemes.
Design patterns
Lexer
Closure
First- class citizen
24. Comprehensive description of software's intended purpose
Specification
OOP
SRS Documentation
model- driven development
25. The rigorousness of the tests that are able to be placed on the code
Law of demeter
Maturity
Stakeholders
Lifecycle
26. People who care about the outcome
Stakeholders
path
conflict
Constructor
27. Formal document outlining a task that needs to be performed on a system
Refactoring
Software Quality
Fully- dressed use case
long method
28. Reusable - abstract 'blocks' of design
Delegation
Design Patterns
SRS Documentation
Requirements
29. Techniques for composing objects to form larger structures
Design patterns
system testing
Maturity
Feasibility
30. A relationship between objects.
Quality metrics
comments
Dijkstra's law
Association
31. Test cases made -> code compiles -> make code pass
Database normalization
long method
Test- driven development
Design pattern
32. A set of rules that define the combinations of symbols that are considered to be correctly structured in a specific programming language. Example: In many programming languages - statements are terminated by a semicolon.
Programming syntax
Quality metrics
code smell
conflict
33. Testing can show the presence but not absence of errors
Warning
: Invalid argument supplied for foreach() in
/var/www/html/basicversity.com/show_quiz.php
on line
183
34. AKA: Lexical Closure or Function Closure - A function together with a referencing environment for the non - local variables of that function. The key aspect of a ______ is variables from outside the function retain there value from the time the closu
SOP
Closure
message chain
Decorator pattern
35. AKA: Function Constant or Function Literal A function defined - and possibly called - without being bound to an identifier.
REST
branch
WSDL
Anonymous function
36. Each line of code is covered once
Specification
statement
Parser
Capacity testing
37. Ways to express the system's subsystems and their relationship
Non - functional Requirements
Maturity level
architectural design
a refactoring
38. AKA: Object - Entity - or Value - An entity that can be constructed at run - time - passed as a parameter - returned from a subroutine - or assigned into a variable.
First- class citizen
Usability testing
Association
brief use case
39. 4th step of requirements gathering
Maturity level
Test- driven development
Validation
WSDL
40. A design pattern that allows behaviour to be added to an existing object dynamically.
SRS Documentation
Versioning
Performance testing
Decorator pattern
41. Series of phases through which software is developed
Test- driven development
Data classes
feature- driven development
Lifecycle
42. Tasks that a system must be able to perform
Versioning
Security testing
Functional Requirements
architectural design
43. (smell)class with too many instance variables or too much code
long parameter list
Large class
feature envy
model- driven development
44. Description of possible sequences of interactions between a user and the system.
use case
middle man
Programming syntax
feature envy
45. Single step in a lifecycle
path
Quality metrics
Phase
Design
46. Models ->code work is done to keep models in sync with code
Stress testing
model- driven development
Test- driven development
Phase
47. A way to automatically grade code based on heuristics
Quality metrics
statement
technical managerial approach
Data classes
48. Test the run - time performance of the system
Cowboy coding
Performance testing
WSDL
Algorithm
49. The degree to which code is free of defects
Parser
Functional Requirements
code quality
Anonymous function
50. Testing the whole system for functionality
Requirements
Lexer
system testing
feature- driven development