Hello, i'm interested in writing a requirements specification document for Geany (definition for this type of technical document on http://en.wikipedia.org/wiki/Requirements_specification) I hope that this will be OK with the developers of Geany. Any help (if needed) would be appreciable. Thanks !
On Fri, 04 Dec 2009 23:01:41 +0200, Panagiotis wrote:
Hello, i'm interested in writing a requirements specification document for Geany (definition for this type of technical document on http://en.wikipedia.org/wiki/Requirements_specification) I hope that this will be OK with the developers of Geany. Any help (if
Why shouldn't this be not ok with us? :D
Even though usually SRS are written *before* a software is developed :).
The question which came first to my mind: why? I always hated to write SRS and I still do (not that much anymore but still :D). No doubt about that it's important and very useful but IMO just no fun at all.
Regards, Enrico
?????? ?????? ??? Enrico Troger enrico.troeger@uvena.de:
On Fri, 04 Dec 2009 23:01:41 +0200, Panagiotis wrote:
Hello, i'm interested in writing a requirements specification document for Geany (definition for this type of technical document on http://en.wikipedia.org/wiki/Requirements_specification) I hope that this will be OK with the developers of Geany. Any help (if
Why shouldn't this be not ok with us? :D
Even though usually SRS are written *before* a software is developed :).
The question which came first to my mind: why? I always hated to write SRS and I still do (not that much anymore but still :D). No doubt about that it's important and very useful but IMO just no fun at all.
Regards, Enrico
-- Get my GPG key from http://www.uvena.de/pub.asc
First of all, thanks for answering my post :-D
I'm aware of the fact that a requirements document is written before the software developement stage.
This SRS comes within the scope of a software engineering project for the corresponding course in the university i study.
I would like to contribute in another way (technical documents aren't my favorites too) but i'm not an advanced C user in order to write code or fix bugs(if any). So i decided to work on a SRS.
On Tue, 08 Dec 2009 23:24:05 +0200, Panagiotis wrote:
?????? ?????? ??? Enrico Troger enrico.troeger@uvena.de:
On Fri, 04 Dec 2009 23:01:41 +0200, Panagiotis wrote:
Hello, i'm interested in writing a requirements specification document for Geany (definition for this type of technical document on http://en.wikipedia.org/wiki/Requirements_specification) I hope that this will be OK with the developers of Geany. Any help (if
Why shouldn't this be not ok with us? :D
Even though usually SRS are written *before* a software is developed :).
The question which came first to my mind: why? I always hated to write SRS and I still do (not that much anymore but still :D). No doubt about that it's important and very useful but IMO just no fun at all.
First of all, thanks for answering my post :-D
I'm aware of the fact that a requirements document is written before the software developement stage.
This SRS comes within the scope of a software engineering project for the corresponding course in the university i study.
Haha, I could have guessed it :).
I would like to contribute in another way (technical documents aren't my favorites too) but i'm not an advanced C user in order to write code or fix bugs(if any). So i decided to work on a SRS.
Ok, cool. Just ask if you have any questions and once you get any results!
Regards, Enrico