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. Models ->code work is done to keep models in sync with code
model- driven development
black box testing
Integration testing
Requirements
2. A movement that promotes common formats for data.
Algorithm
Fully- dressed use case
First- class citizen
Semantic Web
3. (smell) Classes using things that should be private in other classes
Liskov substitution principle
Maturity
Recovery testing
inappropriate intimacy
4. Description of possible sequences of interactions between a user and the system.
branch
Analysis...
use case
shotgun surgery
5. Testing the whole system for functionality
Refactoring
Stakeholders
system testing
Non - functional Requirements
6. Iterative - incremental framework for project management.
inappropriate intimacy
duplicated code
a refactoring
Scrum (Agile software development)
7. Diagram outlining the tasks that are going to be performed by the user
Use case diagram
path
patent
REST
8. Part of compiler reads the sequence of characters and outputs a sequence of lexemes.
SOAP
Decorator pattern
Lexer
Semantic Web
9. 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
10. Representational State Transfer.
REST
Algorithm
Capacity testing
Programming syntax
11. One or two paragraphs of text outlining a use case
Large class
duplicated code
SOAP
Casual use case
12. A method that initializes a newly instantiated object
Test- driven development
Constructor
message chain
Functional Requirements
13. (smell) many parameters are being passed into a method
Specification
long parameter list
Constructor
shotgun surgery
14. Test the run - time performance of the system
Anonymous function
Feasibility
system testing
Performance testing
15. Improve the internal design and implementation of code without affecting external behavior
Refactoring
intellectual property
branch
Functional Requirements
16. Testing tactic that looks at all ways that data can flow through the code
Refactoring
architectural design
Lazy initialization or Lazy loading (Design pattern)
white box testing
17. Evaluates upper limits of operational parameters
Large class
Refactoring
Performance testing
Capacity testing
18. Developing a plan for a product - system or component. 'how' a system should perform a task
Lexer
Design
Specification
Erich Gamma - Richard Helm - Ralph Johnson - John Vlissides
19. (smell) One class delegates all of its requests to another class
Scrum (Agile software development)
Elicitation
Capacity testing
middle man
20. Testing that verifies that individual units of source code are working
unit testing
Refactoring
patent
Liskov substitution principle
21. Degree to which the system meets the specified requirements and development standards
Delegation
software quality
regression testing
Stress testing
22. Tasks that a system must be able to perform
Algorithm
software quality
Functional Requirements
Design Patterns
23. (smell) A class whose only purpose is to hold data
Cowboy coding
Data classes
a refactoring
Functional Requirements
24. How well your fulfil your requirements
shotgun surgery
duplicated code
brief use case
Software Quality
25. 4th step of requirements gathering
Lazy initialization or Lazy loading (Design pattern)
Parser
Validation
Constructor
26. (smell) client needs to use one object to get another and then use that one to get another
message chain
Integration testing
feature- driven development
Design
27. Derived methods should not assume more or deliver less
Denormalization
Liskov substitution principle
software quality
Parser
28. Reusable - abstract 'blocks' of design
intellectual property
Design Patterns
Use case diagram
message chain
29. Each line of code is covered once
jquery
SRS Documentation
statement
Elicitation
30. The rights governing the ownership and disposition of technology
intellectual property
Recovery testing
Specification
Casual use case
31. Diagram used to show how information flows around the system
Phase
comments
sequence diagram
Requirements
32. Each condition is covered twice (true - false)
Test- driven development
Design pattern
branch
Association
33. 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.
Acceptance testing
Feasibility
Design
Phase
34. (smell) Smell deodorant
Usability testing
comments
First- class citizen
model- driven development
35. (smell) Making one change requires changes in multiple places
Test- driven development
statement
Anonymous function
shotgun surgery
36. 3rd step of requirements gathering
Programming style
architectural design
Specification
Non - functional Requirements
37. Single step in a lifecycle
Use case diagram
Phase
Capacity testing
Elicitation
38. People who care about the outcome
Casual use case
sequence diagram
Stakeholders
long parameter list
39. Each team member given set of features to work on
Lambda
feature- driven development
middle man
Dijkstra's law
40. (smell) method has too many statements - loops or variables
long method
REST
trademark
Performance testing
41. A few sentences summarizing a use case
Association
a refactoring
Erich Gamma - Richard Helm - Ralph Johnson - John Vlissides
brief use case
42. Reusable - abstract 'blocks' of design
trademark
Design pattern
code quality
intellectual property
43. Techniques for composing objects to form larger structures
Design patterns
middle man
Lambda
Design
44. Semantic- oriented programming. A programming paradigm in which the programmer formulizes the logic of a domain by means of semantic structures
Specification
a refactoring
software quality
SOP
45. Formal testing against end user specifications
use case
Acceptance testing
Stress testing
SOAP
46. Web Services Description Language. Used to create the XML document that describes the tasks performed by various web services.
Test- driven development
conflict
Code Quality
WSDL
47. (smell)class with too many instance variables or too much code
Large class
Software Quality
Validation
Data classes
48. Ways to express the system's subsystems and their relationship
architectural design
statement
Decorator pattern
Database normalization
49. Protecting the embodiment of an idea
copyright
Closure
Liskov substitution principle
patent
50. (smell) If a set of variables are used together in multiple places
long parameter list
data clumps
Integration testing
Elicitation