On Sep 12, 2012, at 6:54 AM, Simon Pietro Romano <[email protected]> wrote:
> As a general comment, I personally think that the document mixes technical > and non-technical requirements for the RPS and I find this a bit confusing. > Technical requirements are those directly coupled to the functionality that > the RPS will have to make available and would be easily described (or mapped) > with a formal modeling approach like UML, in much the same way as with any > other software requirements specification. Non-technical requirements are > most of the times related to 'policies', which, as I have often claimed on > IETF mailing list discussions, are always orthogonal to (and hence > independent from) technical details of a system. The document definitely mixes those. I like your description of non-technical requirements as "policies". > My personal preference would be to have a clear distinction between the above > classes of requirements. Why is that clear distinction important? Someone reading the document can make the distinction themselves. In the case where a requirement straddles both classes, the reader can say "this seems like both. > I think this would also make it easier, in the future, to edit a formal > software requirements specification for potential bidders. The IAOC might or might not want to do that, but that's up to them. The requirements of both categories came from the IETF community; the IAOC can decide how they want to deal with those requirements. > This said, I also found a third category of requirements which in my view > fall in a specific class which I would call something like "Requirements for > the seamless integration of the future RPS system with the current IETF tools > and meeting materials portal". That is a good example of things that can be technical or policies. I am not sure who would benefit from calling that out in this document. --Paul Hoffman _______________________________________________ NOTE WELL: This list operates according to http://mipassoc.org/dkim/ietf-list-rules.html. https://www.ietf.org/mailman/listinfo/vmeet
