הנדסת תוכנה - מעודכן

Explain why change is inevitable in complex systems and give examples (apart from prototyping and incremental delivery) of software process activities that help predict changes and make the software being developed more resilient to change. Below is a list of correct/incorrect examples of software process activities that help predict changes and make the software being developer more resilient to change. 1. Recording of requirements rational so that the reason why a requirement is included is known. This helps future change. 2. Requirements traceability that shows dependencies between requirements and between the requirements and the design/code of the system. 3. Design modeling where the design model documents the structure of the software. 4. Code refactoring that improves code quality and so makes it more amenable to change.

	Test (a) is intended for string 1; Test (b) is intended for stings 3 and 4; Test (c) is intended for strings 5, 6, 7 and 8
	Test (a) is intended for string 1, 3 and 7; Test (b) is intended for stings 2, 3 and 4; Test (c) is intended for strings 5, 6, and 8
	Test (a) is intended for string 1; Test (b) is intended for stings 2, 3 and 4; Test (c) is intended for strings 5, 6, 7 and 8
	Test (a) is intended for string 1; Test (b) is intended for stings 2 and 4; Test (c) is intended for strings 5, 6, 7 and 8
	None of the above listed answers is correct

	Right order of the above-mentioned activities is 3->2->5->1->4
	Right order of the above-mentioned activities is 5->2->1->3->4
	Right order of the above-mentioned activities is 3->2->1->5->4
	Right order of the above-mentioned activities is 1->3->2->4->5
	None of the above answers is correct