Thats a unique idea.You should consider the following idea to enhance your idea so that it would impact uniquely: Requirements changes during software development pose a risk to cost, schedule and quality while at the same time providing an opportunity to add value. Provision of a generic change source taxonomy which makes the distinction beten factors contributing to requirements uncertainty and events that trigger change will support requirements change risk visibility, and also facilitate richer recording of change data.   present a collaborative study to investigate and support the management of software requirements volatility within the development lifecycle. Previously published change ‘causes’ are elicited from the literature, consolidated using expert knowledge and classified using card sorting. The resulting change trigger taxonomy constructs re initially validated using a small set of requirements change data, and deemed sufficient and practical as a means to collect common requirements change source statistics across multiple projects.
['Sharon McGee', 'Desmond Greer']
I am writing a research paper on a idea A Software Requirements Change Source Taxonomy
[{"from": "human", "value": "I am writing a research paper on a idea A Software Requirements Change Source Taxonomy"}, {"from": "gpt", "value": "Thats a unique idea.You should consider the following idea to enhance your idea so that it would impact uniquely: Requirements changes during software development pose a risk to cost, schedule and quality while at the same time providing an opportunity to add value. Provision of a generic change source taxonomy which makes the distinction beten factors contributing to requirements uncertainty and events that trigger change will support requirements change risk visibility, and also facilitate richer recording of change data.   present a collaborative study to investigate and support the management of software requirements volatility within the development lifecycle. Previously published change \u2018causes\u2019 are elicited from the literature, consolidated using expert knowledge and classified using card sorting. The resulting change trigger taxonomy constructs re initially validated using a small set of requirements change data, and deemed sufficient and practical as a means to collect common requirements change source statistics across multiple projects."}]