Create a Change Management document to capture the changes. Mock up a prototype by including screenshots to reflect the changes. The mock up can be completed with any drawing tool or verbose written description.

The requirements definition process is one of the most important aspects of the systems development life cycle. The effective elicitation of requirements increases the probability of system adoption. One way to improve the requirements elicitation process is through the use of a Requirements Traceability Matrix (RTM). It is also important to note that requirements evolve and even change. The customer may fully understand what is required initially, but there may be laws that change, new policies introduced or budget limitations that result in changed requirements.

Think of a scenario where the customer wants to meet with you to share new requirement for a system that two of you have been working on. The customer indicates that there are 5 new requirements, 2 requirements changes and the removal of requirement in their health care patient management system. The customer also hides the fact that their management would like to delete a total 2 requirements, but has purposely omitted that information.

Create a Change Management document to capture the changes. Mock up a prototype by including screenshots to reflect the changes. The mock up can be completed with any drawing tool or verbose written description.
Include the ethical considerations required to address the ethical dilemma presented via the omission of the deleted requirements.
Create an RTM to ensure that the system functionality maps to all requirements.

You may use the context of a health care patient management system or a system of your choosing.

Submit a Change Management Document using MS Word and an RTM using MS Excel.