Quality - |
(Software Engineering) the degree to which a product conforms to both explicit and implicit requirements |
Refactoring - |
(Software Engineering) changing software in a way that improves its internal structure but does not change it external behavior; often conducted iteratively as design evolves into code. |
Resources - |
(Software Engineering) anything that is required to get the project done, people, hardware, materials, information, etc. |
Reusability - |
(Software Engineering) the ability to reuse an already-existing program component in another application |
Reverse engineering - |
(Software Engineering) trying to develop design models or an understanding of design using program code as a starting point |
Risk - |
(Software Engineering) a potential problem or occurrence that put a project in jeopardy |
Scheduling - |
(Software Engineering) the activity that lays out a timeline for work to be conducted on a project |
Security testing - |
(Software Engineering) testing tasks that probe the vulnerability of both client-side and server-side software |
Selective testing - |
(Software Engineering) testing only a selected set of program paths and data inputs |
Smoke testing - |
(Software Engineering) an integration testing approach that constructs and tests software on a daily basis |