Assessment 5 Instructions: Capital BudgetingPRINTPerform calculations and answer questions related to capital budgeting.In this assessment, you will explore capital budgeting, which is the process of evaluating the feasibility and selection of investment projects. You will examine basic capital budgeting techniques, such as payback, discounted payback, net present value (NPV), internal rate of return (IRR), profitability index (PI), and modified internal rate of return (MIRR).IntroductionThis assessment focuses on capital budgeting calculations.InstructionsComplete and submit the Assessment 5 Template [XLSX].Competencies MeasuredBy successfully completing this assessment, you will demonstrate your proficiency in the course competencies through the following assessment scoring guide criteria:Competency 1: Analyze financial environments and concepts.Explain which capital budgeting method is superior—NPV, IRR, or MIRR.Competency 2: Apply financial computations and processes.Calculate five capital budgeting problems correctly.Competency 3: Communicate effectively and professionally.Convey clear meaning through appropriate word choice and usage.

PART 1  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 topic of interest) can determine if the proposed solution is feasible and will address the needs or gaps in the current operating environment. A. Problem Statement: Craft a clear, accurate problem statement that highlights the information technology-related aspects of the challenges that you are facing. B. 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. C. 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.). D. Deliverables: Propose your overall solution, highlighting the key deliverables that you will create to solve the problem or challenge the statement. E. 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. F. 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? Prompt II: Project Plan and System Design Your project plan and system design will be submitted together in Module Seven, and should communicate a problem to be solved by your proposed information technology solution. These deliverables will be used to direct the implementation effort in your next course, IT 420. Specifically, the following critical elements must be addressed: I. Project Plan: The project plan will be drafted early in the course but further refined as you develop the system design. This way, the work breakdown structure and tasks identified in the design in need of development are added to the project plan. A. 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. B. 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.) C. Dependencies: Clearly communicate any dependencies between tasks or resources for ensuring successful communication of needs. D. Use of Tools: Professionally document project plan using Microsoft Project or Excel.  II. 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. B. 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. C. Constraints: Determine the constraints of the system design and any assumptions made in terms of the problem being solved. D. Resources: Identify necessary resources—hardware, software, servers, virtual desktop resources, and so on—that are required to complete the project, based on analysis of the problem being solved. E. System Overview: Describe the overall design in terms of the integration of tools and technology for successfully constructing your solution. 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. F. Documented Detailed Design: Your detailed design should illustrate and annotate all important details to be developed of the system and its components, interfaces, subsystems, and more. 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. PART 2: Specifically, the following critical elements must be addressed: I. Project Plan: The project plan will be drafted early in the course but further refined as you develop the system design. This way, the work breakdown structure and tasks identified in the design in need of development are added to the project plan. A. 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. B. 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.) C. Dependencies: Clearly communicate any dependencies between tasks or resources for ensuring successful communication of needs. D. Use of Tools: Professionally document project plan using Microsoft Project or Excel.  II. 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. B. 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. C. Constraints: Determine the constraints of the system design and any assumptions made in terms of the problem being solved. D. Resources: Identify necessary resources—hardware, software, servers, virtual desktop resources, and so on—that are required to complete the project, based on analysis of the problem being solved. E. System Overview: Describe the overall design in terms of the integration of tools and technology for successfully constructing your solution. 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. F. Documented Detailed Design: Your detailed design should illustrate and annotate all important details to be developed of the system and its components, interfaces, subsystems, and more. 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.