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. Test cases made -> code compiles -> make code pass
Analysis...
long parameter list
Test- driven development
Dijkstra's law
2. Recognizable indicator that something may be wrong with code
Elicitation
code smell
statement
Performance testing
3. 1st step of requirements gathering
Elicitation
Maturity
Programming syntax
WSDL
4. Semantic- oriented programming. A programming paradigm in which the programmer formulizes the logic of a domain by means of semantic structures
inappropriate intimacy
Test- driven development
Usability testing
SOP
5. Testing the whole system for functionality
Functional Requirements
system testing
Database normalization
Quality metrics
6. Formal testing against end user specifications
Recovery testing
path
Acceptance testing
Design pattern
7. Degree to which the system meets the specified requirements and development standards
software quality
code smell
long parameter list
Design pattern
8. A powerful motivator for change
use case
Dijkstra's law
conflict
Performance testing
9. Representational State Transfer.
long method
Feasibility
Maturity
REST
10. A way to automatically grade code based on heuristics
Programming syntax
Quality metrics
Elicitation
model- driven development
11. (smell) A class whose only purpose is to hold data
First- class citizen
Fully- dressed use case
Law of demeter
Data classes
12. (smell) method has too many statements - loops or variables
a refactoring
Capacity testing
long method
Liskov substitution principle
13. The rights governing the ownership and disposition of technology
Versioning
intellectual property
Use case diagram
Parser
14. Delaying the creation of an object - calculation of a value or another expensive process until first needed.
Phase
unit testing
Lazy initialization or Lazy loading (Design pattern)
brief use case
15. Force software to fail in order to see how it recovers
Software Quality
Large class
Recovery testing
brief use case
16. Each team member given set of features to work on
Design patterns
Elicitation
feature- driven development
Stakeholders
17. Evaluates upper limits of operational parameters
Capacity testing
Feasibility
message chain
Programming syntax
18. Tasks that a system must be able to perform
statement
code smell
Programming syntax
Functional Requirements
19. Web Services Description Language. Used to create the XML document that describes the tasks performed by various web services.
WSDL
duplicated code
Lambda
feature- driven development
20. Test the run - time performance of the system
Semantic Web
Acceptance testing
Dijkstra's law
Performance testing
21. JQuery is a lightweight JavaScript library that emphasizes interaction between JavaScript and HTML.
Design patterns
Law of demeter
regression testing
jquery
22. How developed code is (testing - documentation etc)
Stakeholders
Feasibility
Maturity level
intellectual property
23. The things a system must do
Design Patterns
Code Quality
comments
Requirements
24. 3rd step of requirements gathering
unit testing
intellectual property
conflict
Specification
25. A subjective set of rules or guidelines used when writing source code. Example: The use of whitespace to consistently group and space out statements.
Stakeholders
Recovery testing
Programming style
OOP
26. 2nd step of requirements gathering
Data classes
Analysis...
long parameter list
Scrum (Agile software development)
27. Each line of code is covered once
comments
brief use case
statement
white box testing
28. Word - logo or symbol used to distinguish one organization's wares and services from another's
Dijkstra's law
Large class
use case
trademark
29. Constraints on the design due to external factors
Constructor
white box testing
Design Patterns
Non - functional Requirements
30. A movement that promotes common formats for data.
Maturity level
Semantic Web
Analysis...
Fully- dressed use case
31. Formal document outlining a task that needs to be performed on a system
Fully- dressed use case
sequence diagram
Acceptance testing
WSDL
32. Approach to team management that splits management up into two people with separate tasks
Lexer
Design patterns
Software Quality
technical managerial approach
33. 4th step of requirements gathering
unit testing
Association
Validation
Security testing
34. Object oriented programming; using objects to solve problems.
Casual use case
Large class
OOP
Test- driven development
35. Each possible path through the code is covered
Code Quality
Decorator pattern
path
Database normalization
36. AKA: Function Constant or Function Literal A function defined - and possibly called - without being bound to an identifier.
Integration testing
Erich Gamma - Richard Helm - Ralph Johnson - John Vlissides
Anonymous function
Delegation
37. Executes system in a manner that demands abnormal amounts of resources
Large class
Stress testing
Algorithm
Fully- dressed use case
38. Testing designed to uncover regressions (where stuff that used to work doesn't work anymore)
Data classes
Design pattern
patent
regression testing
39. Protecting the embodiment of an idea
Stakeholders
Test- driven development
SOP
copyright
40. Diagram used to show how information flows around the system
sequence diagram
code smell
Liskov substitution principle
Maturity level
41. Reusable - abstract 'blocks' of design
Design Patterns
Erich Gamma - Richard Helm - Ralph Johnson - John Vlissides
Validation
long method
42. 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
Large class
Lambda
Closure
OOP
43. Each condition is covered twice (true - false)
Closure
copyright
path
branch
44. The degree to which code is free of defects
code quality
Versioning
black box testing
Lexer
45. (smell) Making one change requires changes in multiple places
Scrum (Agile software development)
shotgun surgery
Data classes
Non - functional Requirements
46. A relationship between objects.
system testing
patent
Constructor
Association
47. People who care about the outcome
message chain
Stakeholders
Cowboy coding
code smell
48. How well your fulfil your requirements
REST
Software Quality
regression testing
Design
49. Iterative - incremental framework for project management.
Scrum (Agile software development)
Design pattern
branch
Closure
50. (smell) If a set of variables are used together in multiple places
data clumps
message chain
First- class citizen
Elicitation