IT 415 Southern New Hampshire

For the HBR course pack I choose the GasBuddy Study case: GasBuddy: Fueling Its Digital Platform for Agility and Growth GasBuddy is an established app-led company in the travel app industry. They are facing competitive pressure that has led a new management team to make changes across areas of culture, digital platform, and product line; these changes are tested during the events of Hurricanes Harvey and Irma

Using the HBR coursepack case study you selected in Module One, you will develop three deliverables for your final submission. Milestone One, the executive proposal, is the first deliverable. In Milestone Two, your project plan and system design will be submitted together. These deliverables will be used to direct the implementation effort in your next course, IT 420. If the scope of your planned project is not fully implementable due to constraints on time and resources, you will need to prepare to deliver at the end of the next course a prototype, simulation of the information system vision, or a detailed projection of what the fully implemented system would look like. This projection of a fully implemented system is expected to be much more detailed than a system design.

Specifically, the following critical elements must be addressed:

I. Project Proposal. The project proposal should contain enough detail so that relevant stakeholders (who will vary depending on your selected case study) can determine if the proposed solution is feasible and will address the needs or gaps in the current operating environment. The following sections should be included:

  1. Problem Statement: Craft a clear, accurate problem statement that highlights the information technology-related aspects of the challenges you are facing.
  2. Significance: Analyze the significance of this problem and what a solution could mean to you, the company or group, and the discipline or area of interest within information technology. In other words, describe the significance that this project has to your discipline or area of interest within information technology and your development as a practitioner. This will be your chance to sell this project idea so that it is exciting for your imaginary stakeholder audience, and also for your real-world instructor, peers, and potential employers.
  3. Objectives: Describe the scope, goals, and objectives of your project. If you are addressing only a part of the overarching problem, state this in this section. Make sure that your objectives are reasonable (i.e., could be accomplished without exorbitant resource usage, an irrational timeline, etc.).
  4. Deliverables: Propose your overall solution, highlighting the key deliverables that you will create to solve the problem or challenge the statement.
  5. Methodology: Establish the methodology and techniques that you intend to use throughout the design phase of your project, with support as to how each is appropriate for the situation.
  6. Risks: Analyze the problem and your own solution proposal to highlight any risks that may prevent successful completion of your solution design. Include risks that result from the project not fulfilling the objective to solve the information technology problem. In other words, what risks are present and how would they impact the potential for a successful information technology solution?

Place this order or similar order and get an amazing discount. USE Discount code “GET20” for 20% discount

Posted in Uncategorized

IT 415 Southern New Hampshire

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. 

 

Place this order or similar order and get an amazing discount. USE Discount code “GET20” for 20% discount

Posted in Uncategorized

IT 415 Southern New Hampshire

I’m working on a information technology multi-part question and need an explanation to help me understand better.

IT 415 Milestone Two Guidelines and Rubric

You will develop three deliverables for your final submission. You have already submitted the proposal in Module Three, and now you will submit a draft of the last two deliverables: the project plan and system design. The final versions of the project plan and system design will be submitted together at the end of the course. These deliverables will be used to direct the implementation effort in your next course, IT 420. If the scope of your planned project is not fully implementable due to constraints on time and resources, you will need to prepare to deliver at the end of the next course a prototype, simulation of the information system vision, or a detailed projection of what the fully implemented system would look like. This projection of a fully implemented system is expected to be much more detailed than a system design.

Specifically, the following critical elements must be addressed:

  1. Project Plan: The project plan will be drafted early in the course but further refined as you develop the system design. This way, the workbreakdown structure and tasks identified in the design in need of development are added to the project plan.
    1. Work Breakdown Structure: Clearly communicate a logical work breakdown structure for stakeholders to ensure successful completion of the project. Identify all tasks and artifacts to be developed.
    2. Timeline: Illustrate the overall project timeline, identifying start and finish dates, major milestones, and any other relevant data points during the design and implementation of the project/solution. (Implementation should happen in IT 420, the implementation course.)
    3. Dependencies: Clearly communicate any dependencies between tasks or resources for ensuring successful communication of needs.
    4. Use of Tools: Professionally document project plan using Microsoft Project or Excel.
  2. System Design Document: Although you will individually develop your recommended information technology project, the project design should contain enough detail to support another skilled information technology practitioner in implementing the solution. Determine a reasonable scope for your project so that it can be implemented within the timeframe of the IT 420 course. The following sections should be included:

A. Introduction: Articulate the overall purpose and scope of the system design in terms of addressing the problem or challenges identified in your proposal.

  1. Requirements: Determine all relevant and necessary system requirements based on analysis of the problem faced. The requirements should be written as “system shall” statements that are testable and include functional, design, security, safety, and performance requirements.
  2. Constraints: Determine the constraints of the system design and any assumptions made in terms of the problem being solved.
  3. Resources: Identify necessary resources—hardware, software, servers, virtual desktop resources, and so on—that are required tocomplete the project, based on analysis of the problem being solved.
  4. System Overview: Describe the overall design in terms of the integration of tools and technology for successfully constructing yoursolution. In this section, you should describe the high-level design and architecture, making sure that details are congruent with the type of project you are working on. For example, use of case and class diagrams would need to be included if your project focused on a software application, website wireframe, screen mock-ups for a web application, and so on.
  5. Documented Detailed Design: Your detailed design should illustrate and annotate all important details to be developed of the system and its components, interfaces, subsystems. It further breaks down the high-level design into small enough chunks to be properly implemented. The detailed design should align with the work breakdown structure in the product plan. The detailed design should inform the tasks identified and included in the project plan.

Guidelines for Submission: Submit assignment as a Word document with double spacing, 12-point Times New Roman font, and one-inch margins.

My project is about GasBuddy;

  • GasBuddy: Fueling Its Digital Platform for Agility and Growth GasBuddy is an established app-led company in the travel app industry. They are facing competitive pressure that has led a new management team to make changes across areas of culture, digital platform, and product line; these changes are tested during the events of Hurricanes Harvey and Irma.

Place this order or similar order and get an amazing discount. USE Discount code “GET20” for 20% discount

Posted in Uncategorized