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. Verifies that system is protected against improper penetration
Security testing
Stress testing
Large class
long parameter list
2. (smell) A class whose only purpose is to hold data
Scrum (Agile software development)
Lambda
OOP
Data classes
3. Semantic- oriented programming. A programming paradigm in which the programmer formulizes the logic of a domain by means of semantic structures
architectural design
Association
SOP
Data classes
4. Absence of lifecycle
Cowboy coding
Refactoring
conflict
Maturity level
5. How developed code is (testing - documentation etc)
Maturity level
use case
data clumps
patent
6. Each condition is covered twice (true - false)
Recovery testing
brief use case
branch
Law of demeter
7. 1st step of requirements gathering
code quality
Programming style
Elicitation
Denormalization
8. How well your fulfil your requirements
Decorator pattern
Software Quality
Maturity level
model- driven development
9. The rigorousness of the tests that are able to be placed on the code
Parser
message chain
middle man
Maturity
10. (smell) code is repeated in multiple places
Semantic Web
duplicated code
WSDL
Maturity
11. (smell) many parameters are being passed into a method
Elicitation
long parameter list
Design Patterns
regression testing
12. (smell) method has too many statements - loops or variables
Dijkstra's law
Versioning
use case
long method
13. A movement that promotes common formats for data.
SRS Documentation
regression testing
Semantic Web
software quality
14. Description of possible sequences of interactions between a user and the system.
Design
use case
Dijkstra's law
Use case diagram
15. Web Services Description Language. Used to create the XML document that describes the tasks performed by various web services.
WSDL
Acceptance testing
sequence diagram
Law of demeter
16. Object oriented programming; using objects to solve problems.
Design
Parser
OOP
Capacity testing
17. 'single dot rule'
long method
Law of demeter
Liskov substitution principle
Feasibility
18. Reusable - abstract 'blocks' of design
Law of demeter
Requirements
Design Patterns
Denormalization
19. (smell) client needs to use one object to get another and then use that one to get another
Stress testing
Versioning
message chain
Refactoring
20. (smell) Making one change requires changes in multiple places
regression testing
sequence diagram
Requirements
shotgun surgery
21. Each possible path through the code is covered
Recovery testing
path
Decorator pattern
sequence diagram
22. Test cases made -> code compiles -> make code pass
software quality
Test- driven development
Algorithm
Casual use case
23. Word - logo or symbol used to distinguish one organization's wares and services from another's
trademark
Constructor
branch
a refactoring
24. Evaluates upper limits of operational parameters
Requirements
Elicitation
Lambda
Capacity testing
25. An operator used to denote anonymous functions or closures.
Lambda
Semantic Web
Erich Gamma - Richard Helm - Ralph Johnson - John Vlissides
Versioning
26. Lack of errors in code - readability etc
Code Quality
Phase
Usability testing
technical managerial approach
27. People who care about the outcome
Stress testing
Stakeholders
Parser
regression testing
28. Testing where modules are combined and tested as a group
Parser
code smell
Integration testing
Stress testing
29. 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
jquery
Closure
SOAP
30. Representational State Transfer.
Performance testing
Closure
regression testing
REST
31. Diagram outlining the tasks that are going to be performed by the user
Closure
SOP
long method
Use case diagram
32. (smell)class with too many instance variables or too much code
REST
Law of demeter
Functional Requirements
Large class
33. Tasks that a system must be able to perform
Law of demeter
WSDL
Functional Requirements
comments
34. A way to automatically grade code based on heuristics
middle man
Quality metrics
Anonymous function
Decorator pattern
35. Freezing the state of the source code at a particular point
Versioning
inappropriate intimacy
sequence diagram
copyright
36. Diagram used to show how information flows around the system
Feasibility
Delegation
architectural design
sequence diagram
37. Testing tactic that looks at all ways that data can flow through the code
Law of demeter
Data classes
Elicitation
white box testing
38. The process of eliminating data redundancy by ensuring that tables in a database pertain to a single topic
software quality
sequence diagram
Feasibility
Database normalization
39. Ways to express the system's subsystems and their relationship
architectural design
Recovery testing
Phase
a refactoring
40. A method that initializes a newly instantiated object
Lambda
OOP
Constructor
Quality metrics
41. AKA: Function Constant or Function Literal A function defined - and possibly called - without being bound to an identifier.
Software Quality
branch
Acceptance testing
Anonymous function
42. Techniques for composing objects to form larger structures
conflict
white box testing
Design patterns
Test- driven development
43. 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
brief use case
SOP
inappropriate intimacy
Closure
44. Degree to which the system meets the specified requirements and development standards
software quality
Data classes
Maturity level
SOP
45. Figuring out what the requirements are
unit testing
Elicitation
use case
Non - functional Requirements
46. 3rd step of requirements gathering
Stakeholders
Specification
Fully- dressed use case
Design
47. Wrote the book Design Patterns: Elements of Reusable Object-Oriented Software.
long method
Feasibility
Elicitation
Erich Gamma - Richard Helm - Ralph Johnson - John Vlissides
48. The process of attempting to optimise the read performance of a database by adding redundant data or by grouping data
Lifecycle
Closure
Stakeholders
Denormalization
49. A powerful motivator for change
Validation
conflict
Semantic Web
code smell
50. 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