This week we learned about SRS and started to incorporate it into our project. SRS help us to stick to our processes and goals by defining requirements that cover different areas during development.
For this, we chose to jot down documents in our Azure DevOps project wiki. It allows us to maintain a wiki for each repository or just the whole project. This is super awesome in our case because we don’t need to leave our primary development environment, Azure DevOps that is, for various different tasks.
In addition to that, we also created a use case diagram fully powered by the power of markdown and mermaid’s syntax. You should definitely check it out.
Please refer to our wiki page for an up-to-date version of our SRS. We’d love to know what you think of it.
Cheers,
Gino
3 replies on “A first look into our Software Requirements Specification”
Hey Guys,
I really like the structure and clarity of your SRS, good job on that. Also nice idea on using markdown for the use case diagram.
The use case diagram looks decent, however it isn’t quick clear to me how your scope is organized.
Do you want to implement all the use cases in one semester or am I missing something?
Cheers,
Lukas@KeyCloud
Hi Lucas, thank you for your feedback. You’re right, we actually haven’t thought about it before. We added rough deadlines to the individual functionalities in our SRS and will determine the exact deadlines later on. If you have further suggestions, please let us know.
Thanks,
Gino
Hello everyone,
Thank you for the hint of checking out Azure DevOps, I will definitely look into it. Like KeyCloud already said it’s a nice idea to use markdown for the use case diagram.
It would be better if you choose different colors in your Use Case Diagram that we can check which features are optional or in schedule for the next semester.
Cheers,
Niclas