cost-benefit analysis (5 facts) - The process of deciding whether to do something by evaluating the costs of doing it and the benefits of doing it, and then choosing to do it if the benefits sufficiently exceed the costs
domain analysis (11 facts) - The process by which a software engineer learns enough background information so that he or she can understand the problem and make good decisions during requirements analysis and other stages of the software engineering process
impact analysis (3 facts) - The process of exploring and documenting all possible effects of a change
object oriented analysis (6 facts) (OOA) - The process of deciding which classes will be important to the users, and working out the structure, relationships and behaviour of these classes
post-mortem analysis (3 facts) - The process of looking back at a completed project's design and its development process, in order to identify those aspects where improvements can be made in future projects
requirements analysis (13 facts) - The process of deciding on the requirements of a software system
root cause analysis (4 facts) - The process of determining the ultimate reason why a software engineer made the error introduced a defect
task analysis (3 facts) - The process of determining the detailed steps needed to perform a task effectively and efficiently
use case analysis (14 facts) - The process of dividing up the functionality of the system into use cases, and determining the relationships among those use cases