PART 1: Big data is a popular term used to describe the exponential growth and availability of data, both structured and unstructured. In this assignment, you will research big data. Describe the impact big data has had on today’s business operations. Identify the communication issues and infrastructure issues associated with big data. Explain why big data is expected to become a key factor for competition, business growth, and innovation.
PART 2: In IT 415, you described the considerations you would take during the design phase to protect the information that your system will be processing. What considerations did/will you now take during implementation? Read the National Institute of Standards and Technology’s Security Considerations in the System Development Life Cycle publication on information security, ( https://learn.snhu.edu/d2l/lor/viewer/view.d2l?ou=…) which discusses security considerations that can be integrated throughout the phases of the system development life cycle (SDLC).
Write a short paper describing how your system was designed and implemented with information security in mind. Provide an overview of the security considerations you took during implementation, discuss how your system will be tested to ensure information security, and describe how the security considerations you implemented or planned for will mitigate security-related risks to the implemented system and the organization and the data it processes
Specifically, the following critical elements must be addressed:
? Security Considerations: Explain the security considerations that were incorporated into the SDLC phases to ensure information security.
? Information Security Risk Mitigation: Describe how the security considerations you implemented will mitigate information security risks for the organization. Guidelines for Submission:
PART 3; In this milestone, you will submit a draft of Section I (introduction) and Section II (verification plan) to include all critical elements. The introduction provides an overview of the IT problem you are addressing. When completed, it should provide sufficient context to facilitate quality feedback from the reviewing audience. Your draft Introduction will largely consist of the information from the system proposal and should continue to be updated as required. The verification plan (Section II) will describe how to verify that the system meets original design specifications, for example, by performing various tests that demonstrate functionality and performance. It should include a detailed feedback plan and comment adjudication guidelines.
Prompt: Specifically, the following critical elements must be addressed:
I. Introduction: Present an overview of the problem that the project addressed, the significance this project has, and objectives that the project should have met. Much of this can be taken from the project proposal submitted in IT 415 but including any necessary alterations or adjustments you made during this course. The aim of this section is to provide context to the rest of the project closure document so that the audience can critically evaluate the completed project and provide feedback.
II. Verification Plan: A verification plan will provide an organized way to conduct verification of the system, which can be done through execution of formal test cases that exercise the functionality and performance of the system. It can also include obtaining verbal feedback through focus groups, usability testing of prototypes, and other means.
The following sections should be included:
a) Feedback Plan: Construct a comprehensive plan for showcasing your system and collecting feedback from stakeholders. Explain what you will present as regular artifacts of the system to your stakeholders so you can obtain feedback. The stakeholders from whom you must collect feedback will vary depending on your IT issues.
b) Criteria: Establish the criteria you will use to determine whether or not the feedback received is relevant and actionable.
c) Test Cases: In this section, you will describe how you will (or would) test the implemented project to ensure it fulfilled all requirements and that the promised objectives/functionality were met. You will be required to fully test your system and supply the test results as part of the appendix of your project closure document, if implementation of your project is possible.
0 comments