This week, we have been working to complete the final draft of our Software Requirements Specification document, This has involved finalizing our requirements and quality attributes, writing and modelling use cases and determining any remaining uncertainties. Our SRS is currently about 90% complete, as there are only a few uncertainties remaining and we have completed all sections of our SRS template. However, we have not yet had our SRS reviewed by the project stakeholders, which needs to occur before we submit it.
Project Plan:
10/1: finish first draft of SRS
10/11: finish final draft of SRS
Defects List:
- Are the customer satisfaction surveys associated with the patient who completed them or are they anonymous?
- What protocols shall our application use to communicate with the back-end servers? Is there an API it should use?
- Our requirements list could be higher level and less detailed, but then they would match our vision and scope document.
Risks:
- We still do not know the structure and design of the remote server’s api.
- We do not know whether the customer satisfaction survey is considered “sensitive” information or not.
- Our SRS document has not been reviewed yet.
- We will not have time for an in person review, so our feedback may not be as robust as it could be.
- The due date for the Final SRS document is approaching and our sponsor, Brian, may not get back to us before we have to submit.
No comments:
Post a Comment