This week we started creating and specifing 2 Usecases. We also setup the first hello world page on our client and server. You can find the latest version on Github.
UC1: Send Message
https://github.com/Haus4/NeCo/blob/master/docs/UC1_SendMessage.md
UC2: Receive Message
https://github.com/Haus4/NeCo/blob/master/docs/UC2_ReceiveMessage.md
NeCo 
Hey there,
I think your Use Case Specification is well thought out and I like your activity diagram.
But shouldn’t you include the Server side in the diagram, because it is communicating with the application?
Best Regards
Team react
LikeLike
We tried to combine server and the application core into a single component to have a layer of abstraction to simplify the readability of the use case and to make it clear what requires user interaction and what is done in the background the user doesn’t have to care about.
If it’s not that clear, we can split it up into the separate components.
Greetings,
The NeCo Team
LikeLike
Hi team necoproject,
we like your first design of the mockups and the use case specifications. But both of the use cases are nearly the same. It would be nice if you would have the possibility to show another use case with the corresponding mockup, so we can see better how your app will work. Also look in your document for the grammar and spelling.
Greetings,
Team SuperWoman
LikeLike
We have chosen the two most important use cases for out app, but you are right, they are very similar.
We will add further use cases in the future and we will of course check the grammar and spelling again.
Greetings,
The NeCo Team
LikeLike
[…] 1: Vision Week 2: Team Roles & Technologies Week 3: SRS & OUCD Week 4: Use Cases 1 & 2 Week 5: Scrum & Prototype Week 6: Gherkin .feature files Week 7: Class Diagram Week […]
LikeLike