Advertisement
Guest User

Untitled

a guest
Feb 26th, 2020
235
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 3.21 KB | None | 0 0
  1. The problem was:
  2.  
  3. There was no easy way to perform multiple specific tasks without taking the time to input each command into the terminal individually. The user wanted a single command way to perform each required function
  4.  
  5. The solution is:
  6.  
  7. To create a script that can be run on any terminal that allows streamlined function of multiple processes without having to manually input each command into the terminal to perform operations
  8.  
  9. The requirements of the task were:
  10.  
  11. Create an Executable Script
  12.  
  13. This script must be able to find contents of selected directories
  14.  
  15. Find file path and contents of selected files
  16.  
  17. Each output must be preceded with a descriptive heading
  18.  
  19.  
  20.  
  21. Methodology:
  22.  
  23. The methodology I used for this task was the Software Prototyping Model. I used this model because it allows me to follow through easily with changing and testing the software without reverting to earlier stages which were already complete as they met requirements. This model was ideal because the brunt of the work I had performed was adjusting the code and testing it to iron out issues and potential problems that the user would encounter.
  24.  
  25. I was acting as the end user in this example however, as it was easier to use the scripts acting as the user and see if the user would encounter errors which I could then iterate on those potential issues.
  26.  
  27.  
  28.  
  29. Process:
  30.  
  31. Tools:
  32.  
  33. The tools I used to create and test this script included Atom text editor, which I used to create the actual script. I used Firefox Browser to browse the internet for possible solutions to problems I was encountering when writing or operating the code. I also used the Ubuntu Operating system and Terminal, which utilized the BASH language to test the script as well as run the other tools such as Atom and Firefox.
  34.  
  35.  
  36.  
  37. Development process:
  38.  
  39. During development, text was added in order to give the user instruction about how to operate the script if they are unaware. Grammar had to be adjusted as the requirements had been changed to host multiple directories. This change was hard to accommodate at first but was managed by modifying the way that the script handles user input.
  40.  
  41. The text was spaced, and short delays placed on certain strings. This was done so the user has time to read the text
  42.  
  43.  
  44.  
  45. W
  46.  
  47. W
  48.  
  49. W
  50.  
  51. w
  52.  
  53.  
  54.  
  55. Stage of development:
  56.  
  57. The script is currently mostly finished. Fixes need to be made such as to the explanations, capital letter sensitivity, and the general usability and streamline. some other improvements can be made such as possible formatting or visuals such as colours and bolding & italicizing some text. These improvements are not prioritized however as they are not vital to the operation of the script.
  58.  
  59.  
  60.  
  61. Recommendations:
  62.  
  63. Further development can be taken if needed, however this is not vital to the operation and usability of the script. This could be things such as visual design as stated earlier. The script should carry no maintenance or risks and would just need placing in a common place on machines running it, such as the home folder of the device. It is suited for Ubuntu terminals at the current stage and has not been tested on any other operating system or runtime environment.
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement