Hi,I'm a QA/QC Analyst for a software company. We are currently doing a project that requires an ERP solution for it's requirements. The approved proposal was to use Microsoft's Great Plains solution. Great Plains covers almost all of the requirements plus other excess fields that is not required by the process. Since the Great Plains is a package solution, we can not do musch about these excess fields. The other requirements alredy have solutions. We know that System Design Specifications (SDS) are made for developing systems from the ground-up. But in this case, Great Plains is a system that already exists. What our requirements team are doing right now is coming up with a System Design Specifications (SDS) for Great Plains, specifically for the process and functionality. Now, here are my questions:-I'd like to know if we should still create an SDS for Great Plains? If yes, what should the scope of the SDS be?- In this case that the system is already existing, what should we really be tesing?We are having a "rough" time with our requirements team since in their opinion, we shouldn't be giving them problems with the SDS creation. We (QA/QC team) are treating the Great Plains as a system that made from the ground-up. Are we doing the right thing here?Kindly help us here. I'd really appreciate it.Thanks and best regards,Jazzer