bua 3305 final p

bua3305_final_project.pdf

Home >Business & Finance homework help >bua 3305 final p

BUA 3305: Final Project Guidelines and Grading Guide

Overview For your final project in this course, you will choose a small business or organization for which you will complete a management information system analysis and design project report. You will apply the skills and knowledge you have gained throughout the course to clearly identify a business problem that an information system could address (within the scope of the semester). The purpose of this final project is to assume the role of a systems analyst, whose primary task is to assist an organization or business in finding ways to align appropriate technologies with its needs in a way that delivers improved service and value while streamlining processes and reducing expenses. A system analysis and design report formally documents a prioritized assessment of business problems based on perceived value with a proposed information system-based solution that benefits the business and its customers. The project is divided into five milestones, which will be submitted at various points throughout the course to scaffold learning and ensure quality final project submissions. These milestones will be submitted in Modules 1, 2, 3, 4, and 5. In this assignment, you will demonstrate your mastery of the following course outcomes:

● CO2: Apply critical thinking (knowledge, comprehension, application, analysis, synthesis, and evaluation) to solve problems related to computer information systems

● CO3: Demonstrate effective written communication skills ● CO5: Analyze the needs of various types of users within an organization in order to ensure that functional area concepts are appropriately

applied in an information system

Prompt Specifically, your report must include the critical elements in the following sections and subsections:

I. Executive Summary and Background Information

This section should be a succinctly written management summary, about one page in length or less, that summarizes the project proposal in such a way that readers can rapidly become acquainted with a large body of material without having to read it all. NOTE: Even though this section is at the beginning, it is usually written last. This section must address the following critical elements of the project:

A. Problems and/or Needs: Identify the problems and/or needs of the small business or organization that are of the highest priority.

B. Project Scope: Describe what the project will include and exclude. C. Data Collection: Identify specific resources from which you will collect any data you need in order to complete the project (e.g.,

forms, reports, industry and journal articles, etc.). D. Statement of Business Requirements: Clearly identify (without using technology jargon) the requirements that the system

you recommend will need to have in a Statement of Business Requirements. Examples of what these requirements might look like are as follows: “The system shall generate a real-time report that includes…” “The system’s reports shall be accessible online.” “The system shall update inventory items in real time.” These requirements can be in a bulleted list void of technical requirements.

II. The Information Architecture This goal of this section is to arrange the system information in such a way that it is understandable and useful to the various stakeholders within the organization. To do this, a systems analyst must first determine the business goals and objectives of the company, which will drive the strategy. Secondly, the relevant business areas and the specific information needed to support the critical success factors for the business must be identified. This section of your report should include the following critical elements:

A. Business Goals and Objectives: Describe the company’s goals for the next 3 to 5 years and any associated intermediate milestones or objectives that will serve as status checkpoints.

B. Business Strategy: Explain how the company plans to achieve its goals, meet customer expectations, and sustain a competitive advantage. Be sure to refer to Porter’s Model.

C. Critical Success Factors: Assess what factors must be addressed for the company to stay financially solvent. D. Business Areas and Descriptions: Describe the organizational structure within the business and what various departments

do for the company (e.g., accounting, marketing, production, HR).

III. System Analysis

This section should be written after conducting the client interview, essentially providing a high-level overview of the existing system and its perceived problems from the client’s vantage point. This section of your report should include the following critical elements:

A. Overview of Existing System: Briefly describe the current system’s technology architecture or manual system. B. Definition of User Needs: Define how various user groups (within the various business areas) will use the system and what

they need it to do so that you can ensure the recommended system will address the needs of all affected departments and their particular requirements.

C. Problem and Opportunity: Identify a problem that, if exploited, provides an opportunity for the organization (based on a SWOT analysis).

D. Technique Used While Gathering Study Facts: Assess what strategies you will use to get the information needed for analyzing the system (e.g., interviews, questionnaires, observations).

E. Statement of Alternative Solutions: Identify at least three possible solutions, listing the pros and cons of each, and explain how they would address problems that the current system does not.

F. Recommendation: Based on the alternative solutions suggested above, and the data collected and analyzed, recommend which solution is preferred and explain why. Then justify whether the project is worth pursuing for the company.

IV. System Evaluation A system evaluation is a feasibility study analysis on the viability of the proposed system solution. The feasibility study should focus on answering whether the proposed solution is viable economically, technically, operationally, legally, etc. The goal of a feasibility study is to underscore potential problems that could ensue if the project is undertaken, given an analysis of the various outlined factors, to determine if the project is worth pursuing. This section of your report should include the following critical elements:

A. Economic Analysis: Justify the financial investment (ROI, IRR, NPV, etc.) of the system you are recommending for the company.

B. Technical Analysis: Explain whether the needed technology exists and if it is stable. C. Operational Analysis: Assess whether the organization has the capabilities to operate, use, or maintain the proposed

technology. D. Schedule Analysis: Estimate how long the development effort will take and identify whether that amount of time is consistent

with the client’s timeline. E. Legal and Contractual Analysis: Explain any legal or contractual considerations.

F. Political Analysis: Explain any political considerations that could hamper the development effort.

V. System Design

A system design lays out the system design architecture for each of the elements of the proposed information system, such as the type of computer system, CPU, memory, secondary storage, operating system, application programs, network, database management system, etc. In this section, you will identify the model or version, quantity, speed, cost, etc. for each element of the recommended system listed below. Any items from the list below that are not applicable should be addressed with “N/A” in your report.

A. Hardware Design: Identify relevant computer type CPU, RAM memory, HD storage, quantity, speed, cost, etc. B. Software Design: Specify version, features, OS, cloud-based, cost, etc. as applicable. C. Personnel Design: Specify any particular IT skill set required of the personnel who will be working with the system. D. Network Design: List requirements for internet, intranet, Wi-Fi, personal hotspot, etc. E. Database Design: Identify relevant version, features, cloud-based, cost, etc. as applicable.

VI. System Implementation

This section translates the various system planning activities into operational actions necessary to bring the information system to fruition so it can accomplish the strategic goals and objectives of the business. This section of your report should include the following critical elements:

A. Facility Planning: Describe the venue and specific accommodations (e.g., electrical, lighting, cooling) B. Conversion Plan: Outline the transition plan from the older system to the new system (e.g., direct cutover, pilot) C. Training: Determine whether any new training is recommended or needed based on the existing skill sets of staff. D. Testing: Recommend the level of testing needed (e.g., unit, system, volume). E. Documentation: Identify what, if any, system documentation is recommended (user manuals, user guide, quick setup guide,

etc.).

VII. Appendices In this section, you will include any ancillary material used for the project. It does not count toward the required minimum of five pages for the final report. See the list below for examples of appendices you might include in your report, but note that you are not limited to this list:

● Questionnaire 4

● Forms ● Reports

Milestones Milestone 1: Final Project Review and Topic Exploration In Module 1, you will identify three prospective small business or organization clients that you are considering focusing on for your final project topic, and contact your first choice to inquire whether they will agree to work with you. This milestone is graded with the Milestone 1 Rubric. Milestone 2: Industry Analysis Report, Interview Questionnaire, and Meeting Agenda In Module 2, you will narrow your focus and confirm a specific small business or organization client for your management information system analysis and design project report. To gather some of the information needed to complete this project, you will perform some industry research and then interview a contact from your small business or organization client. This milestone is graded with the Milestone 2 Rubric. Milestone 3: Interview Debrief Report In Module 3, you will write an interview debrief report and start organizing the background information section of your final project. This milestone is graded with the Milestone 3 Rubric. Milestone 4: SWOT Analysis and Systems Analysis In Module 4, you will conduct a SWOT analysis and organize the information required for the system design section of your final paper in order to determine what type of information system you will recommend as a solution for the business problem. This milestone is graded with the Milestone 4 Rubric. Milestone 5: System Design In Module 5, you will organize the information required for the system design section of your final paper. You will identify the exact specifications for construction of a technical, computer-based solution for the business requirements you identified in Milestone 4: System Analysis. This milestone is graded with the Milestone 5 Rubric.

Final Submission: Your final submission will be a five-page management information system analysis and design project report.

Deliverable Milestones

Milestone Deliverables Module Due

Grading

1 Final Project Review and Topic Exploration

1 Graded separately; Module 1 Rubric

2 Industry Analysis Report, Interview Questionnaire, and Meeting Agenda

2 Graded separately; Module 2 Rubric

3 Interview Debrief Report 3 Graded separately; Module 3 Rubric 4 SWOT Analysis and Systems

Analysis 4 Graded separately; Module 4 Rubric

5 System Design 5 Graded separately; Module 5 Rubric

Final Project: Management Information System Analysis and Design Project Report

7 Graded separately; Final Product Rubric

Final Product Rubric

Requirements of Submission: Your report must be submitted as at least a five-page Microsoft Word document (not including appendices), with double spacing, 12-point Times New Roman font, and 1-inch margins. The sections above must be clearly labeled, and any sections or subsections that are not relevant for any reason should still be addressed but noted with “N/A.” You must reference at least three sources, cited in APA format. It should be a complete, polished artifact containing all of the critical elements of the final product. It should incorporate of feedback gained throughout the course. Instructor Feedback: Students can find their feedback in the Grade Center. Rubric Note: Any category that does not apply should still be addressed and noted with “N/A” to receive full points for that category.

Critical Elements Exemplary (100%) Proficient (85%) Needs Improvement (55%) Not Evident (0%) Value Executive Summary and Background Information: Problems and/or Needs

Demonstrates a sophisticated knowledge of management information system analysis and design through the identification of problems and/or needs of the small business or organization with the highest priority.

Identifies the problems and/or needs of the small business or organization with the highest priority.

Identifies the problems and/or needs of the small business or organization with the highest priority, but lacks in detail or clarity.

Does not identify the problems and/or needs of the small business or organization with the highest priority.

Executive Summary and Background

Demonstrates a sophisticated knowledge of management information system analysis and design through the description of

Describes what the project will include and exclude.

Describes what the project will include and exclude, but lacks in detail or clarity.

Does not describe what the project will include and exclude.

Information: Project Scope

what the project will include and exclude.

Executive Summary and Background Information: Data Collection

Demonstrates a sophisticated knowledge of management information system analysis and design through the identification of specific resources for collecting data needed to complete the project

Identifies specific resources for collecting data needed to complete the project.

Identifies specific resources for collecting data needed to complete the project, but lacks in detail or clarity.

Does not identify specific resources for collecting data.

Executive Summary and Background Information: Statement of Business Requirements

Demonstrates a sophisticated knowledge of management information system analysis and design through the identification of requirements needed of the recommended system.

Identifies requirements needed of the recommended system.

Identifies requirements needed of the recommended system, but lacks in detail or clarity..

Does not identify requirements needed of the recommended system.

Information Architecture: Business Goals and Objectives

Demonstrates a sophisticated knowledge of management information system analysis and design through the description of the company’s goals for the next three to five years and any associated intermediate milestones or objectives that will serve as status checkpoints.

Describes the company’s goals for the next three to five years and any associated intermediate milestones or objectives that will serve as status checkpoints.

Describes the company’s goals for the next three to five years and any associated intermediate milestones or objectives that will serve as status checkpoints, but lacks in detail or clarity.

Does not describe the company’s goals for the next three to five years and any associated intermediate milestones or objectives that will serve as status checkpoints.

Information Architecture: Business Strategy

Demonstrates a sophisticated knowledge of management information system analysis and design through the explanation of how the company plans to achieve its goals, meet customer

Explains how the company plans to achieve its goals, meet customer expectations, and sustain a competitive advantage; and refers to Porter’s Model.

Explains how the company plans to achieve its goals, meet customer expectations, and sustain a competitive advantage; but might not refer to Porter’s

Does not explain how the company plans to achieve its goals, meet customer expectations, and sustain a

expectations, and sustain a competitive advantage; and refers to Porter’s Model.

Model, or lacks in detail or clarity.

competitive advantage; and does not refer to Porter’s Model.

Information Architecture: Critical Success Factors

Demonstrates a sophisticated knowledge of management information system analysis and design through the assessment of what factors must be addressed for the company to stay financially solvent.

Assesses what factors must be addressed for the company to stay financially solvent.

Assesses what factors must be addressed for the company to stay financially solvent, but lacks in detail or clarity.

Does not assess what factors must be addressed for the company to stay financially solvent.

Information Architecture: Business Areas and Descriptions

Demonstrates a sophisticated knowledge of management information system analysis and design through the description of the organizational structure within the business and what various departments do for the company.

Describes the organizational structure within the business and what various departments do for the company.

Describes the organizational structure within the business and what various departments do for the company, but lacks in detail or clarity.

Does not describe the organizational structure within the business and what various departments do for the company.

System Analysis: Overview of Existing System

Demonstrates a sophisticated knowledge of management information system analysis and design through the description of the current system’s technology architecture or manual system.

Describes the current system’s technology architecture or manual system.

Describes the current system’s technology architecture or manual system, but lacks in detail or clarity.

Does not describe the current system’s technology architecture or manual system.

System Analysis: Definition of User Needs

Demonstrates a sophisticated knowledge of management information system analysis and design through the definition of how various user groups will use

Defines how various user groups will use the system and what they need it to do.

Defines how various user groups will use the system and what they need it to do, but lacks in detail or clarity.

Does not define how various user groups will use the system and what they need it to do.

the system and what they need it to do.

System Analysis: Problem and Opportunity

Demonstrates a sophisticated knowledge of management information system analysis and design through the identification of a problem that if exploited, provides an opportunity for the organization.

Identifies a problem that if exploited, provides an opportunity for the organization.

Identifies a problem that if exploited, provides an opportunity for the organization, but lacks in detail or clarity.

Does not identify a problem that if exploited, provides an opportunity for the organization.

System Analysis: Technique Used While Gathering Study Facts

Demonstrates a sophisticated knowledge of management information system analysis and design through the assessment of strategies for obtaining information needed for analyzing the system.

Assesses strategies for obtaining information needed for analyzing the system.

Assesses strategies for obtaining information needed for analyzing the system, but lacks in detail or clarity.

Does not assess strategies for obtaining information needed for analyzing the system.

System Analysis: Statement of Alternative Solutions

Demonstrates a sophisticated knowledge of management information system analysis and design through the identification of at least three possible solutions listing the pros/cons of each, and explain how they would address problems that the current system does not.

Identifies at least three possible solutions listing the pros/cons of each, and explain how they would address problems that the current system does not.

Identifies at least three possible solutions listing the pros/cons of each, and explain how they would address problems that the current system does not, but lacks in detail or clarity.

Does not identify at least three possible solutions listing the pros/cons of each, and explain how they would address problems that the current system does not.

System Analysis: Recommendation

Demonstrates a sophisticated knowledge of management information system analysis and design through the recommendation of a preferred solution; explains why; and

Recommends a preferred solution; explains why; and justifies whether the project is worth pursuing for the company.

Recommends a preferred solution; explains why; and justifies whether the project is worth pursuing for the company, but lacks in detail or clarity.

Does not recommend a preferred solution; explains why; and justifies whether the project is worth pursuing for the company.

justifies whether the project is worth pursuing for the company.

System Evaluation: Economic Analysis

Demonstrates a sophisticated knowledge of management information system analysis and design through the justification of the financial investment of the recommended system for the company.

Justifies the financial investment of the recommended system for the company.

Justifies the financial investment of the recommended system for the company, but lacks in detail or clarity.

Does not justify the financial investment of the recommended system for the company.

System Evaluation: Technical Analysis

Demonstrates a sophisticated knowledge of management information system analysis and design through the explanation of whether the needed technology exists and if it is stable.

Explains whether the needed technology exists and if it is stable.

Explains whether the needed technology exists and if it is stable, but lacks in detail or clarity.

Does not explain whether the needed technology exists and if it is stable.

System Evaluation: Operational Analysis

Demonstrates a sophisticated knowledge of management information system analysis and design through the assessment of whether the organization has the capabilities to operate, use, or maintain the proposed technology.

Assesses whether the organization has the capabilities to operate, use, or maintain the proposed technology.

Assesses whether the organization has the capabilities to operate, use, or maintain the proposed technology, but lacks in detail or clarity.

Does not assess whether the organization has the capabilities to operate, use, or maintain the proposed technology.

System Evaluation: Schedule Analysis

Demonstrates a sophisticated knowledge of management information system analysis and design through the estimation of how long the development effort will take and identifies whether

Estimates how long the development effort will take and identifies whether that amount of time is consistent with the client’s timeline.

Estimates how long the development effort will take and identifies whether that amount of time is consistent with the client’s timeline, but lacks in detail or clarity.

Does not explain estimate how long the development effort will take and identifies whether that amount of time is consistent with the client’s timeline.

that amount of time is consistent with the client’s timeline.

System Evaluation: Legal and Contractual Analysis

Demonstrates a sophisticated knowledge of management information system analysis and design through the explanation of any legal or contractual considerations.

Explains any legal or contractual considerations.

Explains any legal or contractual considerations, but lacks in detail or clarity.

Does not explain any legal or contractual considerations.

System Evaluation: Political Analysis

Demonstrates a sophisticated knowledge of management information system analysis and design through the explanation of any political considerations that could hamper the development effort.

Explains any political considerations that could hamper the development effort.

Explains any political considerations that could hamper the development effort, but lacks in detail or clarity.

Does not explain any political considerations that could hamper the development effort.

System Design: Hardware Design

Demonstrates a sophisticated knowledge of management information system analysis and design through the identification of hardware specifications needed for implementing the recommended system.

Identifies hardware specifications needed for implementing the recommended system.

Identifies hardware specifications needed for implementing the recommended system, but lacks in detail or clarity.

Does not identify hardware specifications needed for implementing the recommended system.

System Design: Software Design

Demonstrates a sophisticated knowledge of management information system analysis and design through the identification of software specifications needed for implementing the recommended system.

Identifies software specifications needed for implementing the recommended system.

Identifies software specifications needed for implementing the recommended system, but lacks in detail or clarity.

Does not identify software specifications needed for implementing the recommended system.

System Design: Personnel Design

Demonstrates a sophisticated knowledge of management information system analysis and design through the identification of personnel needed for operating the recommended system.

Identifies personnel needed for operating the recommended system.

Identifies personnel needed for operating the recommended system, but lacks in detail or clarity.

Does not identify personnel needed for operating the recommended system.

System Design: Network Communication Design

Demonstrates a sophisticated knowledge of management information system analysis and design through the identification of network communication specifications needed for implementing the recommended system.

Identifies network communication specifications needed for implementing the recommended system.

Identifies network communication specifications needed for implementing the recommended system, but lacks in detail or clarity.

Does not identify network communication specifications needed for implementing the recommended system.

System Design: Database Design

Demonstrates a sophisticated knowledge of management information system analysis and design through the identification of database specifications for implementing the recommended system.

Identifies database specifications for implementing the recommended system.

Identifies database specifications for implementing the recommended system, but lacks in detail or clarity.

Does not identify database specifications for implementing the recommended system.

System Implementation: Facility Planning

Demonstrates a sophisticated knowledge of management information system analysis and design through the description of the venue and specific accommodations.

Describes the venue and specific accommodations.

Describes the venue and specific accommodations, but lacks in detail or clarity.

Does not describe the venue and specific accommodations.

System Implementation: Conversion Plan

Demonstrates a sophisticated knowledge of management information system analysis and design through the by outlining the transition plan from the older system to the new system.

Outlines the transition plan from the older system to the new system.

Outlines the transition plan from the older system to the new system, but lacks in detail or clarity.

Does not outline the transition plan from the older system to the new system.

System Implementation: Training

Demonstrates a sophisticated knowledge of management information system analysis and design through the determination of whether any new training is recommended or needed based on the existing skill sets of staff.

Determines whether any new training is recommended or needed based on the existing skill sets of staff.

Determines whether any new training is recommended or needed based on the existing skill sets of staff, but lacks in detail or clarity.

Does not determine whether any new training is recommended or needed based on the existing skill sets of staff.

System Implementation: Testing

Demonstrates a sophisticated knowledge of management information system analysis and design through the recommendation of the level of testing needed.

Recommends the level of testing needed.

Recommends the level of testing needed, but lacks in detail or clarity.

Does not recommend the level of testing needed.

System Implementation: Documentation

Demonstrates a sophisticated knowledge of management information system analysis and design through the identification of what, if any, system documentation is recommended.

Identifies what, if any, system documentation is recommended.

Identifies what, if any, system documentation is recommended, but lacks in detail or clarity.

Does not identify what, if any, system documentation is recommended.

Appendices Includes any ancillary material used for the project.

N/A

Does not include any ancillary material used for the project.

Articulation of Response

Submission is free of errors related to citations, grammar, spelling, syntax, and organization and is presented in a professional and easy to read format. All sources used are cited using APA Style, 6th ed.

Submission has no major errors related to citations, grammar, spelling, syntax, or organization and/or errors made in citing sources using APA Style, 6th ed.

Submission has major errors related to citations, grammar, spelling, syntax, or organization that negatively impact readability and articulation of main ideas, or sources used are not cited using APA Style, 6th ed.

Submission has critical errors related to citations, grammar, spelling, syntax, or organization that prevent understanding of ideas, or no sources are cited.

Earned Total Comments

100 %