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. (smell)class with too many instance variables or too much code
Stakeholders
Use case diagram
Lazy initialization or Lazy loading (Design pattern)
Large class
2. Testing that verifies that individual units of source code are working
Lifecycle
unit testing
Phase
Refactoring
3. 1st step of requirements gathering
Elicitation
jquery
Programming style
Lexer
4. (smell) method has too many statements - loops or variables
long method
Usability testing
SOP
Elicitation
5. Each condition is covered twice (true - false)
Stakeholders
branch
Analysis...
SRS Documentation
6. (smell) code is repeated in multiple places
model- driven development
Code Quality
code smell
duplicated code
7. Diagram outlining the tasks that are going to be performed by the user
regression testing
branch
Versioning
Use case diagram
8. Comprehensive description of software's intended purpose
Specification
Functional Requirements
Design
SRS Documentation
9. Absence of lifecycle
Software Quality
Large class
OOP
Cowboy coding
10. 2nd step of requirements gathering
Analysis...
SOAP
Lambda
Constructor
11. Techniques for composing objects to form larger structures
Constructor
Versioning
Law of demeter
Design patterns
12. Reusable - abstract 'blocks' of design
Design pattern
sequence diagram
Erich Gamma - Richard Helm - Ralph Johnson - John Vlissides
WSDL
13. Formal document outlining a task that needs to be performed on a system
Recovery testing
Fully- dressed use case
Functional Requirements
branch
14. (smell) A method using another class more than its own
feature envy
Specification
data clumps
Code Quality
15. (smell) One class delegates all of its requests to another class
Maturity level
middle man
Quality metrics
Design pattern
16. (smell) If a set of variables are used together in multiple places
system testing
Denormalization
data clumps
Large class
17. A design pattern that allows behaviour to be added to an existing object dynamically.
Decorator pattern
Scrum (Agile software development)
Algorithm
Programming style
18. One or two paragraphs of text outlining a use case
Data classes
Casual use case
Refactoring
Specification
19. (smell) client needs to use one object to get another and then use that one to get another
message chain
comments
Use case diagram
Feasibility
20. Each possible path through the code is covered
path
sequence diagram
Design
Security testing
21. Constraints on the design due to external factors
Non - functional Requirements
regression testing
Analysis...
Stress testing
22. 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
23. (smell) Making one change requires changes in multiple places
feature envy
comments
Programming syntax
shotgun surgery
24. A guess of the ability to complete a task or solve a problem. Typically the possible benefits and risks are considered. Some factors would be benefit of completion - risks of incompletion and costs to approach completion.
Feasibility
Analysis...
sequence diagram
SOP
25. AKA: Function Constant or Function Literal A function defined - and possibly called - without being bound to an identifier.
Dijkstra's law
sequence diagram
Recovery testing
Anonymous function
26. A few sentences summarizing a use case
Parser
Delegation
brief use case
Data classes
27. Testing tactic that looks at all ways that data can flow through the code
SOAP
white box testing
Design Patterns
Parser
28. 1. A language feature that supports prototype- based programming. 2. Originally: One object relying upon another to provide a specified set of functionalities. 3. In .NET: A way of telling which method to call when an event is triggered
brief use case
Delegation
feature envy
Anonymous function
29. Iterative - incremental framework for project management.
First- class citizen
middle man
Scrum (Agile software development)
black box testing
30. A way to automatically grade code based on heuristics
Design pattern
Quality metrics
jquery
unit testing
31. Small - behaviour- preserving - source- to- source transformation
Software Quality
Design
statement
a refactoring
32. Web Services Description Language. Used to create the XML document that describes the tasks performed by various web services.
Casual use case
use case
Decorator pattern
WSDL
33. Each line of code is covered once
technical managerial approach
long parameter list
statement
branch
34. Representational State Transfer.
Large class
patent
REST
Fully- dressed use case
35. A method that initializes a newly instantiated object
Design
Constructor
long parameter list
regression testing
36. Object oriented programming; using objects to solve problems.
Refactoring
OOP
Specification
Validation
37. 3rd step of requirements gathering
technical managerial approach
Integration testing
code quality
Specification
38. 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
39. Recognizable indicator that something may be wrong with code
WSDL
Delegation
Closure
code smell
40. Each team member given set of features to work on
architectural design
WSDL
intellectual property
feature- driven development
41. An effective method expressed as a finite list of well- defined instructions for solving a problem.
Design
Algorithm
Denormalization
long method
42. A subjective set of rules or guidelines used when writing source code. Example: The use of whitespace to consistently group and space out statements.
Programming style
black box testing
comments
Validation
43. Figuring out what the requirements are
Elicitation
Erich Gamma - Richard Helm - Ralph Johnson - John Vlissides
Parser
Requirements
44. The degree to which code is free of defects
REST
Lifecycle
code quality
Security testing
45. Testing designed to uncover regressions (where stuff that used to work doesn't work anymore)
technical managerial approach
regression testing
model- driven development
Elicitation
46. JQuery is a lightweight JavaScript library that emphasizes interaction between JavaScript and HTML.
jquery
Dijkstra's law
feature- driven development
conflict
47. 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
Maturity
duplicated code
Design Patterns
48. People who care about the outcome
jquery
Non - functional Requirements
Stress testing
Stakeholders
49. Simple Object Access Protocol. Specification for exchanging structured information. Uses XML. Usually relies on other Application Layer protocols (HTTP - SMTP)
Decorator pattern
Association
duplicated code
SOAP
50. Tasks that a system must be able to perform
long parameter list
Elicitation
Elicitation
Functional Requirements