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. 4th step of requirements gathering
duplicated code
Design Patterns
Validation
long method
2. Each condition is covered twice (true - false)
branch
inappropriate intimacy
data clumps
brief use case
3. Test cases made -> code compiles -> make code pass
Liskov substitution principle
Versioning
Test- driven development
branch
4. Protecting the embodiment of an idea
SRS Documentation
copyright
Stakeholders
use case
5. A movement that promotes common formats for data.
long method
model- driven development
Semantic Web
statement
6. (smell) method has too many statements - loops or variables
brief use case
Acceptance testing
duplicated code
long method
7. The things a system must do
Recovery testing
Requirements
brief use case
code smell
8. 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.
long parameter list
SOAP
First- class citizen
Security testing
9. Testing the whole system for functionality
brief use case
long parameter list
Non - functional Requirements
system testing
10. The rights governing the ownership and disposition of technology
Law of demeter
intellectual property
Lazy initialization or Lazy loading (Design pattern)
Code Quality
11. Approach to team management that splits management up into two people with separate tasks
Specification
Recovery testing
Versioning
technical managerial approach
12. Techniques for composing objects to form larger structures
Acceptance testing
Design patterns
comments
Recovery testing
13. (smell) A method using another class more than its own
trademark
Programming style
Analysis...
feature envy
14. Force software to fail in order to see how it recovers
Capacity testing
Recovery testing
Software Quality
Maturity
15. 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
Delegation
Specification
code quality
intellectual property
16. A method that initializes a newly instantiated object
Constructor
Refactoring
Specification
Non - functional Requirements
17. Each line of code is covered once
OOP
Test- driven development
Design pattern
statement
18. People who care about the outcome
Maturity
system testing
Stakeholders
branch
19. (smell) code is repeated in multiple places
comments
regression testing
duplicated code
Requirements
20. Reusable - abstract 'blocks' of design
Design pattern
a refactoring
Liskov substitution principle
Constructor
21. Iterative - incremental framework for project management.
OOP
Usability testing
Scrum (Agile software development)
data clumps
22. Ways to express the system's subsystems and their relationship
architectural design
shotgun surgery
Functional Requirements
Design pattern
23. Derived methods should not assume more or deliver less
Liskov substitution principle
duplicated code
Parser
Requirements
24. Models ->code work is done to keep models in sync with code
inappropriate intimacy
Non - functional Requirements
model- driven development
Association
25. (smell) client needs to use one object to get another and then use that one to get another
data clumps
Law of demeter
Use case diagram
message chain
26. 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
Large class
brief use case
Recovery testing
27. Test the run - time performance of the system
branch
inappropriate intimacy
Performance testing
Parser
28. Recognizable indicator that something may be wrong with code
SOP
OOP
software quality
code smell
29. Testing where modules are combined and tested as a group
Analysis...
Integration testing
technical managerial approach
intellectual property
30. Tasks that a system must be able to perform
Maturity
Liskov substitution principle
inappropriate intimacy
Functional Requirements
31. (smell) many parameters are being passed into a method
long parameter list
First- class citizen
technical managerial approach
long method
32. Absence of lifecycle
long method
Code Quality
Design pattern
Cowboy coding
33. Diagram used to show how information flows around the system
patent
Database normalization
sequence diagram
Maturity
34. Testing that verifies that individual units of source code are working
unit testing
Programming syntax
code smell
patent
35. The process of eliminating data redundancy by ensuring that tables in a database pertain to a single topic
duplicated code
OOP
Database normalization
Feasibility
36. Test whether or not tasks can be accomplished efficiently by all levels of users
Usability testing
white box testing
OOP
SRS Documentation
37. How developed code is (testing - documentation etc)
Maturity level
Feasibility
comments
Maturity
38. The degree to which code is free of defects
Erich Gamma - Richard Helm - Ralph Johnson - John Vlissides
code quality
Test- driven development
Closure
39. 3rd step of requirements gathering
Specification
trademark
Feasibility
data clumps
40. Representational State Transfer.
Stakeholders
architectural design
REST
unit testing
41. Comprehensive description of software's intended purpose
Association
SOAP
SRS Documentation
Fully- dressed use case
42. JQuery is a lightweight JavaScript library that emphasizes interaction between JavaScript and HTML.
Design Patterns
Algorithm
a refactoring
jquery
43. Delaying the creation of an object - calculation of a value or another expensive process until first needed.
Validation
software quality
Programming syntax
Lazy initialization or Lazy loading (Design pattern)
44. 'single dot rule'
Cowboy coding
architectural design
Casual use case
Law of demeter
45. Each possible path through the code is covered
path
shotgun surgery
Stakeholders
Quality metrics
46. Degree to which the system meets the specified requirements and development standards
Use case diagram
statement
Versioning
software quality
47. A way to automatically grade code based on heuristics
sequence diagram
Quality metrics
Database normalization
Refactoring
48. Object oriented programming; using objects to solve problems.
Code Quality
OOP
branch
Quality metrics
49. Small - behaviour- preserving - source- to- source transformation
Feasibility
use case
a refactoring
Acceptance testing
50. Description of possible sequences of interactions between a user and the system.
Erich Gamma - Richard Helm - Ralph Johnson - John Vlissides
Stress testing
Requirements
use case