In this week we worked on the Software Requirements Specification and Use Case Diagram for our project. Keep in mind that those are work in progress and several details will change in the following weeks.
You can view our SRS in Google Docs and the Overall Use Case Diagram in Google Drive
The react Project 
Hey there!
As I understood it, the use cases should be roles played by the actors (e.g. saving the file) while the actors are individuals using the system (e.g. a developer using MS Word). That would mean that your overall use case diagram should not contain actors like “server” and use cases like “manage capture information”.
A lot of points your software requirements specification contains are “to be determined”. What is holding you back?
I think some of the requirements you specified are hard to realize (99% availability, 20mins downtime etc.).
Best regards,
Thomas
LikeLike
Hi,
your criticsm is welcomed. We are going to work on the SRS and UCD and update it. We are thinking about additional functions and elements.
Best Regards
Team react
LikeLike
Hey Team react!
I like your SRS, because it’s well structured.
But maybe you could add a little more content and go more into detail.
I also like your use case diagram. The differentiation between the different parts is easy to understand and the whole diagram is very good readable.
I only miss that you haven’t colored the use cases you plan to realize this semester. Maybe you could add that.
Best regards
Team Mix-It!
LikeLike
Hey.
Thanks for your comment. We are planning to realize them in this semester. But you’re right, we should add the colors.
Best regards
Team react
LikeLike