I'm looking for some reassurance on my interpretation of the following requirement/s.
The instructions state that standalone mode � �is selected using the single command line argument that is permitted� and also say later that the application must ��accept an indication that a local database is to be used, in which case, the networking must be bypassed entirely�.
Is it safe to assume that both statements actually refer to a single requirement, restated in two different ways, or are the instructions stipulating that, having selected networked mode via the setting of the correct command line parameter, the user should still be able to select standalone mode while entering the initialisation details.
I�m currently leaning toward the former interpretation (i.e. network mode is specified via the command line and nowhere else) because I can�t see the value in allowing the user to choose �standalone� mode immediately after they have specified �network� mode at the command line.
I agree with your view. However, I would state that in my choices.txt.
Imagine if your program is used on the market. Wouldn't it be annoying to click on the mode you want to run every time you start the software? I would much prefer to have a short cut link to run the command with specified mode. Double click and voila!
I also have doubts about this, I interpret ti like : "In either case, the program must allow the user to specify the location of the database" - I must be able to specified the db file location.
"it must also accept an indication that a local database is to be used, in which case, the networking must be bypassed entire" -> I must be able to swith th e modes and in the local mode I have no network. The "indication" in this case is the command line parameter.
Quoted by Stuart Graig ---------------------------------- I�m currently leaning toward the former interpretation (i.e. network mode is specified via the command line and nowhere else) because I can�t see the value in allowing the user to choose �standalone� mode immediately after they have specified �network� mode at the command line. --------------------------------
I have opted for your former interpretation ( one the user has selected the mode, the network form will not allow switch the mode). I have noticed this when I read the spec again chasing the word "must". Any way, preferably to document this in the choices.txt
If "alone" mode (local)there will be a database input field which says something like that "please locate your data base on your local machine since you are running a local mode".
If it "network" mode ( client newtwork mode) then you will not see any indication to locate a database; hence, there is no indication to any local mode
In summary, I've interpreted the requirements thus (I've stated my reasons in previous posts):
The user may select network mode by specifying the appropriate commmand line parameter.
In "standalone" and "network server" modes the user is prompted to enter the details of the database file. The user will have the option of free typing the file specification or using a file manager dialogue to choose the database file (this last part is not strictly required, but creates a better user experience in my opinion).
In addition, in "network server" mode the user is prompted to enter the details (e.g. port number) of the remote accessible service which will support database access for the "network clients".
In "network client" mode the user is prompted to enter the connection details (e.g. IP address, port number etc.) for the "network server" which will accept and process database access requests. The user will not have the opportunity to enter a database file specification in this mode, since all access is proxied through the "network server".
You showed up just in time for the waffles! And this tiny ad:
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koop