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 used to show how information flows around the system
Non - functional Requirements
Design patterns
Lexer
sequence diagram
2. 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
OOP
code smell
architectural design
3. Techniques for composing objects to form larger structures
statement
Analysis...
code smell
Design patterns
4. 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
Closure
Non - functional Requirements
Specification
system testing
5. Approach to team management that splits management up into two people with separate tasks
Anonymous function
Usability testing
technical managerial approach
Software Quality
6. One or two paragraphs of text outlining a use case
Casual use case
Performance testing
Stakeholders
Programming syntax
7. Verifies that system is protected against improper penetration
Security testing
unit testing
First- class citizen
copyright
8. A few sentences summarizing a use case
Algorithm
Dijkstra's law
Analysis...
brief use case
9. Testing where modules are combined and tested as a group
Integration testing
Design patterns
duplicated code
Programming style
10. The process of eliminating data redundancy by ensuring that tables in a database pertain to a single topic
Functional Requirements
branch
Database normalization
Cowboy coding
11. Formal document outlining a task that needs to be performed on a system
Parser
feature- driven development
Fully- dressed use case
intellectual property
12. A way to automatically grade code based on heuristics
Quality metrics
Capacity testing
Performance testing
code smell
13. A design pattern that allows behaviour to be added to an existing object dynamically.
Quality metrics
Non - functional Requirements
Decorator pattern
patent
14. Testing that verifies that individual units of source code are working
Validation
Design pattern
Anonymous function
unit testing
15. Test the run - time performance of the system
branch
Performance testing
Specification
Closure
16. An operator used to denote anonymous functions or closures.
Stress testing
Database normalization
Lambda
long parameter list
17. Testing the whole system for functionality
sequence diagram
branch
system testing
Elicitation
18. 1st step of requirements gathering
Use case diagram
Versioning
Elicitation
Database normalization
19. Diagram outlining the tasks that are going to be performed by the user
feature- driven development
Design patterns
Use case diagram
Design Patterns
20. 3rd step of requirements gathering
Dijkstra's law
Functional Requirements
REST
Specification
21. 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
22. Reusable - abstract 'blocks' of design
feature envy
Design Patterns
First- class citizen
Acceptance testing
23. Formal testing against end user specifications
Acceptance testing
Law of demeter
feature envy
data clumps
24. The things a system must do
Algorithm
Law of demeter
Requirements
Closure
25. Freezing the state of the source code at a particular point
Versioning
Closure
Casual use case
OOP
26. Simple Object Access Protocol. Specification for exchanging structured information. Uses XML. Usually relies on other Application Layer protocols (HTTP - SMTP)
SOAP
Fully- dressed use case
Refactoring
Integration testing
27. Object oriented programming; using objects to solve problems.
duplicated code
inappropriate intimacy
OOP
Versioning
28. (smell)class with too many instance variables or too much code
Large class
Use case diagram
patent
Design patterns
29. How developed code is (testing - documentation etc)
Maturity level
Versioning
comments
Scrum (Agile software development)
30. Tasks that a system must be able to perform
Functional Requirements
Law of demeter
Quality metrics
model- driven development
31. Absence of lifecycle
Cowboy coding
Recovery testing
Validation
feature envy
32. JQuery is a lightweight JavaScript library that emphasizes interaction between JavaScript and HTML.
statement
Design
long parameter list
jquery
33. How well your fulfil your requirements
SOAP
Validation
Software Quality
Maturity
34. The rights governing the ownership and disposition of technology
conflict
Performance testing
REST
intellectual property
35. (smell) If a set of variables are used together in multiple places
data clumps
Constructor
technical managerial approach
brief use case
36. Small - behaviour- preserving - source- to- source transformation
regression testing
a refactoring
patent
Acceptance testing
37. Each condition is covered twice (true - false)
branch
OOP
Feasibility
Denormalization
38. The process of attempting to optimise the read performance of a database by adding redundant data or by grouping data
conflict
Denormalization
SOP
black box testing
39. Single step in a lifecycle
code quality
copyright
brief use case
Phase
40. (smell) Smell deodorant
comments
Validation
Analysis...
REST
41. (smell) many parameters are being passed into a method
Quality metrics
SOAP
long parameter list
Lambda
42. Wrote the book Design Patterns: Elements of Reusable Object-Oriented Software.
Erich Gamma - Richard Helm - Ralph Johnson - John Vlissides
Software Quality
Usability testing
Refactoring
43. 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.
Recovery testing
REST
Feasibility
Closure
44. Each possible path through the code is covered
Performance testing
Lazy initialization or Lazy loading (Design pattern)
intellectual property
path
45. Comprehensive description of software's intended purpose
Acceptance testing
Phase
SRS Documentation
Stakeholders
46. (smell) code is repeated in multiple places
duplicated code
Scrum (Agile software development)
Validation
Algorithm
47. Each team member given set of features to work on
Requirements
comments
copyright
feature- driven development
48. Part of compiler reads the sequence of characters and outputs a sequence of lexemes.
Quality metrics
Lexer
Integration testing
Maturity
49. Force software to fail in order to see how it recovers
Requirements
Use case diagram
Database normalization
Recovery testing
50. Semantic- oriented programming. A programming paradigm in which the programmer formulizes the logic of a domain by means of semantic structures
Functional Requirements
Data classes
shotgun surgery
SOP