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. 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.
jquery
technical managerial approach
Association
First- class citizen
2. The process of eliminating data redundancy by ensuring that tables in a database pertain to a single topic
Database normalization
Law of demeter
Decorator pattern
shotgun surgery
3. Testing tactic based on whether inputs and outputs match up for required functionality
black box testing
duplicated code
Use case diagram
Fully- dressed use case
4. (smell) code is repeated in multiple places
Use case diagram
Specification
feature envy
duplicated code
5. A movement that promotes common formats for data.
Semantic Web
brief use case
Use case diagram
Stakeholders
6. Absence of lifecycle
copyright
Cowboy coding
feature- driven development
Constructor
7. Iterative - incremental framework for project management.
Constructor
Phase
Design patterns
Scrum (Agile software development)
8. Testing where modules are combined and tested as a group
white box testing
data clumps
WSDL
Integration testing
9. Representational State Transfer.
Dijkstra's law
long parameter list
Requirements
REST
10. Formal document outlining a task that needs to be performed on a system
SOAP
Fully- dressed use case
system testing
unit testing
11. Derived methods should not assume more or deliver less
unit testing
Delegation
Liskov substitution principle
Dijkstra's law
12. 3rd step of requirements gathering
Use case diagram
Specification
Stakeholders
Design
13. A relationship between objects.
Association
Capacity testing
Maturity level
comments
14. Protecting the embodiment of an idea
Cowboy coding
model- driven development
copyright
Design
15. A design pattern that allows behaviour to be added to an existing object dynamically.
Decorator pattern
REST
middle man
path
16. Each team member given set of features to work on
Programming style
software quality
feature- driven development
Use case diagram
17. JQuery is a lightweight JavaScript library that emphasizes interaction between JavaScript and HTML.
Validation
Stress testing
jquery
intellectual property
18. 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
Validation
Lifecycle
Design Patterns
19. 4th step of requirements gathering
system testing
long parameter list
Validation
Design Patterns
20. The degree to which code is free of defects
jquery
code quality
Functional Requirements
code smell
21. Developing a plan for a product - system or component. 'how' a system should perform a task
data clumps
Performance testing
Design
Casual use case
22. The things a system must do
Denormalization
Requirements
Phase
feature- driven development
23. People who care about the outcome
WSDL
copyright
Code Quality
Stakeholders
24. Web Services Description Language. Used to create the XML document that describes the tasks performed by various web services.
WSDL
SOAP
Anonymous function
Quality metrics
25. (smell) client needs to use one object to get another and then use that one to get another
message chain
Quality metrics
Dijkstra's law
Use case diagram
26. Recognizable indicator that something may be wrong with code
comments
code smell
Law of demeter
Requirements
27. A method that initializes a newly instantiated object
WSDL
patent
Lifecycle
Constructor
28. An effective method expressed as a finite list of well- defined instructions for solving a problem.
Quality metrics
Association
Algorithm
Usability testing
29. 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
30. (smell) A method using another class more than its own
architectural design
Integration testing
WSDL
feature envy
31. Verifies that system is protected against improper penetration
Law of demeter
Security testing
Specification
SOP
32. 'single dot rule'
duplicated code
Performance testing
Erich Gamma - Richard Helm - Ralph Johnson - John Vlissides
Law of demeter
33. Models ->code work is done to keep models in sync with code
Feasibility
Maturity
Large class
model- driven development
34. Comprehensive description of software's intended purpose
Maturity
Requirements
SRS Documentation
Maturity level
35. How developed code is (testing - documentation etc)
sequence diagram
Performance testing
Test- driven development
Maturity level
36. Test whether or not tasks can be accomplished efficiently by all levels of users
Design Patterns
Usability testing
Analysis...
branch
37. 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
Stress testing
Closure
Algorithm
WSDL
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. How well your fulfil your requirements
Database normalization
inappropriate intimacy
Software Quality
WSDL
40. The rigorousness of the tests that are able to be placed on the code
Decorator pattern
Elicitation
Maturity
data clumps
41. Reusable - abstract 'blocks' of design
Decorator pattern
Design Patterns
Analysis...
Elicitation
42. A way to automatically grade code based on heuristics
Law of demeter
code quality
Quality metrics
patent
43. Formal testing against end user specifications
Acceptance testing
Scrum (Agile software development)
message chain
code smell
44. Constraints on the design due to external factors
Non - functional Requirements
Liskov substitution principle
Erich Gamma - Richard Helm - Ralph Johnson - John Vlissides
Large class
45. A computer program that divides code up into functional components
Lambda
Dijkstra's law
Parser
code quality
46. 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.
jquery
statement
Denormalization
Programming syntax
47. (smell) One class delegates all of its requests to another class
Fully- dressed use case
middle man
Algorithm
Phase
48. A powerful motivator for change
Casual use case
Database normalization
Large class
conflict
49. (smell)class with too many instance variables or too much code
Large class
Liskov substitution principle
regression testing
Requirements
50. Testing the whole system for functionality
regression testing
system testing
Programming style
Integration testing