SRS document

[fmentis]

Greetings from Greece

My name is Mentis Fotios, I 'm a 25-year-old pre-graduate student in the Computer Science Department in the Aristotle University of Thessaloniki.

I am really interested in composing an SRS document for the GolenDict project if you need it either in Greek or in English.
I am looking forward to your answer.

With Regards,
Mentis Fotis

[ikm]

Well, you're the second student from the same University to contact me about taking part in an open source project. The answer is: we're open to contributions! But if by SRS you mean 'Software Requirements Specification', isn't that a little bit late for that? I mean, the software is already there... So please be more specific. Also, in my opinion you should be cooperating with other students so you don't happen to duplicate efforts.

[alleo]

I know one more meaning of SRS - Spaced Repetition System.

[fmentis]

With SRS I meant the software requirements specification.

This is mostly a document that can be used as a manual of the program. It is a template that is composed to show a user what the program requires to work and how it works, something like a manual for the program. So it is written at the last stage of the program where everything works as it should. It is not a document where someone says what he requires from the program, that would be a software requirement planner.

Furthermore I am aware of the fact that I am the second one on this project so it won't be a problem after all.

[C2BlEv]

My understanding was also that SRS would be a blueprint for software before it is implemented. But I guess it can also be written based on the existing software.

Anyway, as the author ikm said, everybody would be happy if you contribute. There is a lot of info in this forum (some of it is in Russian, ask if you need a translation of something specific), the source code is at https://github.com/goldendict/goldendict . Use the GD (most recent builds are at https://github.com/goldendict/goldendic ... or-Windows ), ask questions.
GD would benefit from a user manual. Note that some attempts have been made to make a user manual at GD wiki: http://goldendict.org/wiki/index.php/Main_Page

Don't forget that GD runs on multiple platforms (Win, Linux, now Mac, in the future Android).

Part of the manual could be the description of how people could help with the project (translation/localization, ports, programming, releasing dictionaries that are not under copyright, etc.)

[ikm]

I would also add that language-wise the project would benefit most from docs in English, since that's the language everyone more-or-less understands.

[fmentis]

I could start by writing that document in my native language (Greek). In that way it would be much easier to simply translate it in English later since the basic info would be there already.

The "hard" part would be collecting the info after all