1. Is it ever possible to have the requirements definition document be the same as the requirements specifications? What are the pros and cons of having two documents? 2. Sometimes a customer requests a requirement you know is impossible to implement. Should you agree to put the requirement in the definition and specification documents anyways, thinking you may come up with a novel way to meet it or there may be a possibility the customer will drop the requirement? Discuss the ethical implications of promising what you know you cannot deliver