MS-DOS Batch and Linux Shellscript Programs

Program Prompting Users for Input and Outputting Result

Write an MS-DOS batch or Linux shellscript program:

1. Which prompts the user to enter a numeric expression and outputs the result to the screen.

2. Which take one parameter on the command line which is the name of a directory. If the user does not enter any parameters on the command line it should prompt the user for it.

If the directory does not exist then it creates it or if the directory exists it tells the user the directory already exists.

3. Helps maintain a log file. It should present the user with a menu with two options, option one prompts the user for a comment (it does not matter what) then adds a line to the end of a log file called “log.txt” (in the current directory) which contains the comment. It should preserve the previous contents of the file (if it exists).

Note – for full marks you will be expected to hand in ALL the things listed below for each exercise. Failure to do so will result in lower marks even if your programs fully meet the above functional specifications. Marks will also be deducted for poor presentation and poor programming practice. Just handing in a disk with no printed report or a printed report and no disk will result in a low (possibly fail) mark.

By the deadline above, you must hand in a word report containing:

• Fully commented single spaced listings of your solutions to the three exercises. Minimally or uncommented and/or poorly laid out code is likely to score very low marks. Take care to check that Word does not mess up your code formatting (for example wrapping round code lines).

• Screen shots showing your programs running. Your screen shots should be annotated (indicating clearly what the screen shot demonstrates) and show that the programs work exactly as described above.

• Think carefully what screen shots you show, they should be selected to show the various aspects and routes through the program all work correctly, random screenshots with little or no evidence of thought about the above or excessive screen shots where most or all  do not aid proving the code works correctly are also likely to score poorly. Remember the user is always right J…. It is no good implementing something other than what is asked for (including extra unnecessary features) and they trying to argue your way is better!

What the customer wants, the customer gets even if you disagree with them...

• A bibliography list if you used any sources to help you develop your code cross referenced where needed to your report (including references in the research questions). If you are unclear how to reference properly there is a guide to how on the ARU Library website. It is not essential you use a specific style but you should use a recognised referencing style such as Harvard. If you directly used code from another source then this should also be stated in the comments in your programs.

• A zip file containing the program files (as text NOT Word files) and your Word report, as detailed above. Please name your text files so that it is obvious what they are, such as ex1.bat or ex1.sh etc.

• Keep an electronic backup of all submitted work in case your script or disk goes missing!

• Make sure your zip file contains all the required files and is readable (please check this!). Do not encrypt it! If we cannot open your zip file (for example it is corrupted) we will be unable to test your code and/or check your Word document we will give you zero for that aspect