role of managing the technology infrastructure | Good Grade Guarantee!
How do I do this?You have assumed the role of managing the technology infrastructure at a zoo. You will develop a working program (either an authentication system or a monitoring system) for the zoo designed to follow the specifications outlined in the overview. You will also provide detailed documentation describing your development process. Select from one of the following options as the basis of your program. Option 1: Authentication System For security-minded professionals, it is important that only the appropriate people gain access to data in a computer system. This is called authentication. Once users gain entry, it is also important that they only see data related to their role in a computer system. This is called authorization. For the zoo, you will develop an authentication system that manages both authentication and authorization. You have been given a credentials file that contains credential information for authorized users. You have also been given three files, one for each role: zookeeper, veterinarian, and admin. Each role file describes the data the particular role should be authorized to access. Create an authentication system that does all of the following: ? Asks the user for a username ? Asks the user for a password ? Converts the password using a message digest five (MD5) hash o It is not required that you write the MD5 from scratch. Use the code located in this document and follow the comments in it to perform this operation. ? Checks the credentials against the valid credentials provided in the credentialsfile o Use the hashed passwordsin the second column; the third column contains the actual passwords for testing and the fourth row contains the role of each user. ? Limits failed attempts to three before notifying the user and exiting theprogram ? Gives authenticated users access to the correct role file after successfulauthentication o The system information stored in the role file should be displayed. For example, if a zookeeper’s credentials is successfully authenticated, then the contents from the zookeeper file will be displayed. If an admin’s credentials is successfully authenticated, then the contents from the admin file will be displayed. ? Allows a user to log out ? Stays on the credential screen until either a successful attempt has been made, three unsuccessful attempts have been made, or a user chooses to exit You are allowed to add extra roles if you would like to see another type of user added to the system, but you may not remove any of the existing roles. Option 2: Monitoring System As a zookeeper, it is important to know the activities of the animals in your care and to monitor their living habitats. Create a monitoring system that does all of the following: ? Asks a user if they want to monitor an animal, monitor a habitat, orexit Displays a list of animal/habitat options (based on the previous selection) as read from either the animals or habitats file o Asks the user to enter one of theoptions ? Displays the monitoring information by finding the appropriate section in thefile ? Separates sections by the category and selection (such as “Animal – Lion” or “Habitat -Penguin”) ? Uses a dialog box to alert the zookeeper if the monitor detects something out of the normal range (These will be denoted in the files by a new line starting with *****. Do not display the asterisks in thedialog.) ? Allows a user to return to the originaloptions You are allowed to add extra animals, habitats, or alerts, but you may not remove the existing ones. Specifically, the following critical elements must be addressed: I. Process Documentation: Create process documentation to accompany your program that addresses all of the followingelements: A. Problem Statement/Scenario: Identify the program you plan to develop and analyze the scenario to determine necessary consideration for building your program. B. Overall Process: Provide a short narrative that shows your progression from problem statement to breakdown to implementation strategies. In other words, describe the process you took to work from problem statement (your starting point) to the final product. Your process description should align to your end resulting program and include sufficient detail to show the step-by-step progress from your problem statement analysis. C. Pseudocode: Break down the problem statement into programming terms through creation of pseudocode. The pseudocode should demonstrate your breakdown of the program from the problem statement into programming terms. Explain whether the pseudocode differs from the submitted program and document any differences and the reason forchanges. D. Methods and Classes: Your pseudocode reflects distinct methods and classes that will be called within the final program. If the pseudocode differs from the submitted program, document the differences and reason forchanges. E. Error Documentation: Accurately document major errors that you encountered while developing yourprogram. F. Solution Documentation: Document how you solved the errors and what you learned fromthem. AI. Program: Your working program should include all of the specified requirements. The comments within your program will count toward the assessment of the documentation aspects of yoursubmission. A. Functionality 1. Input/Output: Your program reads input from the user and uses systemoutput. 2. Control Structures: Your program utilizes appropriate control structures for programlogic. 3. Libraries: Your program utilizes standard libraries to pull in predefinedfunctionality. 4. Classes Breakdown: Your program is broken down into at least two appropriateclasses. 5. Methods: Your program utilizes all included methods correctly within the classes. 6. Error Free: Your program has been debugged to minimize errors in the final product. (Your program will be run to determine functionality.) B. Best Practices: These best practices should be evident within your working program and processdocumentation. 1. Formatting Best Practices: Provide program code that is easy to read and follows formatting best practices as defined by the industry, such as with indentation. 2. Documentation Best Practices: Include comments where needed within the program in appropriate detail for communicating purpose, function, and necessary information to other information technology (IT) professionals. 3. Coding Best Practices: Ensure your program supports clean code through descriptive variablenames. Milestone One: Discussion Peer Review: Final ProjectPlanning Milestones In Module Five, you will create and submit the pseudocode for the final project problem statement. This milestone will be graded with the Milestone One Rubric. Final Submission: Authentication or Monitoring System In Module Seven, you will submit your final project. It should be a complete, polished artifact containing all of the critical elements of the final project. It should reflect the incorporation of feedback gained throughout the course. This submission will be graded with the Final Project Rubric. Final Project Rubric Guidelines for Submission: Your process documentation should be approximately 2 to 4 pages double-spaced and in 12-point Times New Roman font. Any resource citations should adhere to the most current guidelines for APA formatting. You will submit the code for your working program in a separate file from your process documentation, though the two will be graded together by your instructor. Submit all files as a ZIP file to brightspace for grading. Critical Elements Exemplary Proficient Needs Improvement Not Evident Value Process Meets “Proficient” criteria and Identifies the program to be Identifies the program to be Does not identify the program to 4.75 Documentation: determination demonstrates a developed and analyzes the developed and analyzes the be developed or analyze the Problem thorough understanding of scenario to determine scenario to determine scenario to determin
QUALITY: 100% ORIGINAL – NO PLAGIARISM.
- **REMEMBER TO PRECISE PAGE NUMBER**
- Hit The Order Button To Order A **Custom Paper**