New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
iNNvestigate 2.0 planning #221
Comments
Hi @leanderweber @enryH @rachtibat here is a first draft. Cheers, |
Hi @albermax , thanks for the draft! For now I would suggest the following additions/changes: Stakeholder requirements:
Software requirements:
|
Hi Max, Thank you for writing everything out! Best |
since come comments indicate activity towards a 2.0 version (I cannot wait :-) ) I have two questions: is there some approx. ETA for tf2 compatible innvestigate 2.0 that you could share with us (users)? and if there is some branch that already works in some cases it would be quite interesting to know where to find (at least I could not figure out the most recent code version) |
Hi Moritz, We are aiming for a first release before August. |
Hello, |
@adrhill it would be great, if you give an update on the release schedule or point us to information about it. in particular I am strongly interested when pattern attribution is available for tf2 |
Hi Moritz, |
Hi @moritzaugustin, this took longer than anticipated, but iNNvestigate 2.0 is now released! |
I suggest we approach the planning in the following way:
I know many things are "trivial", but IMHO it is good to have them listed and in mind when making decisions.
Also compared to coding the whole package, planning it takes not that much time. :-)
Also, those requirements change over time. The idea is to then update accordingly the derived requirements/architecture/interfaces/implementations.
Stakeholder requirements
Stakeholder is someone how will interact with this package in some way. Such requirements give a broad direction to the planning and are use case oriented. Mind stakeholders are more of a role than real persons - one person can have several roles.
Software requirements
SW requirements are software oriented and typically derive from stakeholder requirements.
Architecture & interfaces
fit
/analyze
pattern?Open questions:
Todos:
The text was updated successfully, but these errors were encountered: