Requirements specification
I) Initial sources:
1. Source codes http://downloads.sourceforge.net/psi/psi-0.12.1.tar.bz2 / http://psi-im.org/development/
II) Results:
1. EXE-file of PSI distributive. It should instal PSI version that satisfies all the items of the requirements specification.
2. Sources codes that can be built easily to get: a) New Psi; b) Distributive exe for new Psi.
3. Patch for http://downloads.sourceforge.net/psi/psi-0.12.1.tar.bz2 that makes version from subparagraph II.1.
4. Source codes must also compile and work under Linux, so the distributive does.
III) Changes that must be done to the standard version of PSI:
1. In CHAT mode:
1.1 If the own messages OR/AND the messages of interlocutor AREN’T beeing crypted, the list of messages must be shown with RED frame.
1.2 If the own messages AND the messages of interlocutor ARE beeing crypted, the list of messages must be shown with GREEN frame.
1.3 If an interlocutor doesn’t have a PGP-key, its tab must be shown with red background.
1.4 Functionality of subparagraphes III.1.1-3 must turn on/off in “Settings” dialog of PSI.
1.5 The state of “Lock” button (pressed/released) must be stored forever, i.e. if it’s pressed, it should stay pressed and the crypting must work next time PSI is run whatever happens: PSI is closed, system reboots, system halts unexpectedly etc.
1.6 Crypting can be turned off only by pressing out (releasing) “Lock” button by user. Just so and by no other means.
1.7 The mode of message delivery confirmation must be realized. The messages which are sent and for which the confirmation hanen’t gotten must be shown in gray color. When the confirmation is gotten the color must be changed to standard one (look at the settings of color scheme of PSI).
1.8 If the password for PGP-keys has been inputed incorrectly two more attempts should be allowed (now a single attempt is allowed, then user must press “ok” -> go to offline mode -> go to online mode -> retype password).
2. General:
2.1 PSI must reread key list each time the menu “Choose PGP-key” is opened so that reloading of PSI won’t be required in order to refresh PGP-key list.
IV) Acceptance of work and testing:
1. Testing of work when different sides of PSI messaging doesn’t have PGP-keys.
2. After process of jabber on one side has been killed, the other one jabber sends messages.
3. Testing of 4096bit PGP-keys support.
4. Incorrect password is typed N times.
5. After new key has been added to keyring, it should be shown in the key list of PSI without restarting of it.
Categories: C/C++ Tags: and the, codes, color, confirmation, distributive, has been, http downloads sourceforge, interlocutor, key, key list, keys, list, messages, mode, Modification, New, password, pgp, pgp key, pgp keys, pressed, psi, psi modification, shown, shown with, Testing, the messages, version, work
Requirements specification
I) Initial sources:
1. Source codes http://downloads.sourceforge.net/psi/psi-0.12.1.tar.bz2 / http://psi-im.org/development/
II) Results:
1. EXE-file of PSI distributive. It should instal PSI version that satisfies all the items of the requirements specification.
2. Sources codes that can be built easily to get: a) New Psi; b) Distributive exe for new Psi.
3. Patch for http://downloads.sourceforge.net/psi/psi-0.12.1.tar.bz2 that makes version from subparagraph II.1.
4. Source codes must also compile and work under Linux, so the distributive does.
III) Changes that must be done to the standard version of PSI:
1. In CHAT mode:
1.1 If the own messages OR/AND the messages of interlocutor AREN’T beeing crypted, the list of messages must be shown with RED frame.
1.2 If the own messages AND the messages of interlocutor ARE beeing crypted, the list of messages must be shown with GREEN frame.
1.3 If an interlocutor doesn’t have a PGP-key, its tab must be shown with red background.
1.4 Functionality of subparagraphes III.1.1-3 must turn on/off in “Settings” dialog of PSI.
1.5 The state of “Lock” button (pressed/released) must be stored forever, i.e. if it’s pressed, it should stay pressed and the crypting must work next time PSI is run whatever happens: PSI is closed, system reboots, system halts unexpectedly etc.
1.6 Crypting can be turned off only by pressing out (releasing) “Lock” button by user. Just so and by no other means.
1.7 The mode of message delivery confirmation must be realized. The messages which are sent and for which the confirmation hanen’t gotten must be shown in gray color. When the confirmation is gotten the color must be changed to standard one (look at the settings of color scheme of PSI).
1.8 If the password for PGP-keys has been inputed incorrectly two more attempts should be allowed (now a single attempt is allowed, then user must press “ok” -> go to offline mode -> go to online mode -> retype password).
2. General:
2.1 PSI must reread key list each time the menu “Choose PGP-key” is opened so that reloading of PSI won’t be required in order to refresh PGP-key list.
IV) Acceptance of work and testing:
1. Testing of work when different sides of PSI messaging doesn’t have PGP-keys.
2. After process of jabber on one side has been killed, the other one jabber sends messages.
3. Testing of 4096bit PGP-keys support.
4. Incorrect password is typed N times.
5. After new key has been added to keyring, it should be shown in the key list of PSI without restarting of it.
Categories: C/C++ Tags: and the, codes, color, confirmation, distributive, has been, http downloads sourceforge, interlocutor, key, key list, keys, list, messages, mode, New, password, patch, pgp, pgp key, pgp keys, pressed, psi, psi patch, shown, shown with, Testing, the messages, version, work
