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. Diagram outlining the tasks that are going to be performed by the user
Feasibility
Stakeholders
Use case diagram
conflict
2. (smell) many parameters are being passed into a method
SOAP
long parameter list
architectural design
Anonymous function
3. Degree to which the system meets the specified requirements and development standards
feature- driven development
Semantic Web
software quality
Decorator pattern
4. (smell) A method using another class more than its own
feature- driven development
feature envy
Acceptance testing
Requirements
5. Each line of code is covered once
Design patterns
Semantic Web
Maturity
statement
6. Diagram used to show how information flows around the system
a refactoring
sequence diagram
code smell
branch
7. Approach to team management that splits management up into two people with separate tasks
REST
Capacity testing
Liskov substitution principle
technical managerial approach
8. (smell) method has too many statements - loops or variables
Anonymous function
technical managerial approach
Closure
long method
9. JQuery is a lightweight JavaScript library that emphasizes interaction between JavaScript and HTML.
Design Patterns
Lazy initialization or Lazy loading (Design pattern)
jquery
Law of demeter
10. Part of compiler reads the sequence of characters and outputs a sequence of lexemes.
Lexer
feature envy
white box testing
Constructor
11. Test the run - time performance of the system
intellectual property
Performance testing
Elicitation
statement
12. How developed code is (testing - documentation etc)
Liskov substitution principle
jquery
Stress testing
Maturity level
13. Reusable - abstract 'blocks' of design
SOP
inappropriate intimacy
SRS Documentation
Design Patterns
14. A few sentences summarizing a use case
Fully- dressed use case
Quality metrics
Algorithm
brief use case
15. 'single dot rule'
brief use case
Anonymous function
Law of demeter
long method
16. 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
17. Improve the internal design and implementation of code without affecting external behavior
Database normalization
copyright
jquery
Refactoring
18. 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.
WSDL
First- class citizen
REST
software quality
19. 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.
Elicitation
white box testing
Feasibility
Maturity
20. The process of eliminating data redundancy by ensuring that tables in a database pertain to a single topic
Specification
Database normalization
Acceptance testing
black box testing
21. A method that initializes a newly instantiated object
Performance testing
Functional Requirements
Constructor
Stakeholders
22. Verifies that system is protected against improper penetration
software quality
Specification
Security testing
REST
23. A way to automatically grade code based on heuristics
Quality metrics
Lambda
feature envy
Capacity testing
24. Freezing the state of the source code at a particular point
Versioning
OOP
Design Patterns
Software Quality
25. Testing designed to uncover regressions (where stuff that used to work doesn't work anymore)
patent
Erich Gamma - Richard Helm - Ralph Johnson - John Vlissides
regression testing
Acceptance testing
26. Simple Object Access Protocol. Specification for exchanging structured information. Uses XML. Usually relies on other Application Layer protocols (HTTP - SMTP)
Database normalization
Programming syntax
SOAP
code smell
27. Delaying the creation of an object - calculation of a value or another expensive process until first needed.
shotgun surgery
Test- driven development
Lazy initialization or Lazy loading (Design pattern)
code smell
28. (smell) If a set of variables are used together in multiple places
Specification
data clumps
a refactoring
Versioning
29. Techniques for composing objects to form larger structures
statement
Design patterns
Erich Gamma - Richard Helm - Ralph Johnson - John Vlissides
Constructor
30. Lack of errors in code - readability etc
Code Quality
Lambda
Stress testing
Stakeholders
31. The process of attempting to optimise the read performance of a database by adding redundant data or by grouping data
sequence diagram
use case
Fully- dressed use case
Denormalization
32. Wrote the book Design Patterns: Elements of Reusable Object-Oriented Software.
Quality metrics
Erich Gamma - Richard Helm - Ralph Johnson - John Vlissides
unit testing
Design Patterns
33. A computer program that divides code up into functional components
Fully- dressed use case
Validation
Parser
Lexer
34. 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.
branch
Refactoring
Programming syntax
SRS Documentation
35. 1st step of requirements gathering
Programming style
software quality
Elicitation
Security testing
36. Formal document outlining a task that needs to be performed on a system
Maturity
Fully- dressed use case
Programming style
Performance testing
37. (smell) code is repeated in multiple places
duplicated code
comments
code quality
Stakeholders
38. Single step in a lifecycle
Phase
Maturity level
Lifecycle
Liskov substitution principle
39. An effective method expressed as a finite list of well- defined instructions for solving a problem.
Design Patterns
code quality
OOP
Algorithm
40. Absence of lifecycle
Code Quality
long method
Cowboy coding
message chain
41. Protecting the embodiment of an idea
copyright
Liskov substitution principle
Scrum (Agile software development)
WSDL
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
First- class citizen
Casual use case
Closure
Algorithm
43. Ways to express the system's subsystems and their relationship
architectural design
system testing
regression testing
Scrum (Agile software development)
44. (smell)class with too many instance variables or too much code
a refactoring
Analysis...
Large class
Elicitation
45. (smell) Classes using things that should be private in other classes
Elicitation
Stakeholders
inappropriate intimacy
message chain
46. Testing the whole system for functionality
jquery
inappropriate intimacy
regression testing
system testing
47. Test cases made -> code compiles -> make code pass
Usability testing
Feasibility
Test- driven development
unit testing
48. Testing that verifies that individual units of source code are working
middle man
Design patterns
unit testing
Use case diagram
49. Semantic- oriented programming. A programming paradigm in which the programmer formulizes the logic of a domain by means of semantic structures
copyright
SOP
white box testing
Requirements
50. Reusable - abstract 'blocks' of design
Usability testing
sequence diagram
Code Quality
Design pattern