BSA 375 Week 5 Learning Team Assignment



Product Description

BSA 375 Week 5 Learning Team Assignment

BSA 375 Week 5 Learning Team Assignment


BSA 375 Week 5 Learning Team Assignment Service Request SR-kf-013 Paper and Presentation

Learning Team Assignment: Service Request SR-kf-013 (Due Week Five)

1. Create a Learning Team Charter

Complete Service Request SR-kf-013.

Develop Requirements for Kudler Fine Foods Frequent Shopper Program.

Prepare a 12-16 page paper and a PowerPoint® presentation of the project, due in Week Five. Assume that the paper and the presentation are to be delivered to an executive management committee. At a minimum, the paper should include the following:

Business objectives with supporting measures of success for the project

Description of the current business process or system with identification of the scope or boundaries of the project

Project constraints: finances, time, resources, and organizational policies or culture

Business functional requirements

Description of the new business process or system—use the process objectives model and the system objectives model

Design requirements: input or output design, interface design, data model, and network model

Cost-benefit analysis

2. Learning Team Assignment: Service Request SR-kf-013 (Due Week Five)

Review the Service Request SR-kf-013 for Kudler Fine Foods.

Define the scope and stakeholders associated with the project.

Identify the preliminary assignments and tasks for each group member.

Create a detailed outline for each section of the paper.

Draft the first 4-6 page section of the due in Week Five. Include the following:

Statement of Scope and Goals: Specify what functions will be included in the project. Identify the goals—include accomplishments, not a solution.

Supporting Measures for Success: Specify tangible measures for determining the relative degree of success of the completed project. The measures must correlate with the goals specified in the first section of this deliverable.

3. Learning Team Assignment: Service Request SR-kf-013 (Due Week Five)

Draft the next 4-6 page section of the due in Week Five. This should include:

Determination of Requirements: Identify specific analysis methods used to determine user needs.

List of Confirmed Requirements: Categorize each system requirement identified for the Week Two deliverable as mandatory or optional.

Proposed System Process View: Provide a flowchart of the proposed process.

Functional Allocation Modeling: Specify how each proposed system function would be allocated in terms of the required hardware, software, and Human-Computer Interface (HCI).

Logical Model of the System: Provide a high-level logical data flow diagram of the proposed system.

4. Learning Team Assignment: Service Request SR-kf-013 (Due Week Five)

Draft the next 4-6 page section of due in Week Five. This must include:

Preliminary Design Model: Provide a diagram that illustrates the overall logical information architecture.

Design Trade-off Approach: Specify the tradeoffs among cost, schedule, and performance. For example, a fast, inexpensive solution may not address performance requirements adequately.

Detailed Design Process and Design Specifications: Specify separate recommended decisions for software design, hardware, and networks. Include resolution of HCI considerations.

Physical Model of the System: Illustrate the recommended decisions in information architecture diagrams.

Begin work on the PowerPoint presentation.

5. Learning Team Assignment: Service Request SR-kf-013

Draft the final 4-6 page section of the paper. This should include:

Testing Process Summary: Define a test plan or script that identifies major software functionality and hardware to be tested along with the required outcomes.

Installation Process and Training Plan Summary: Provide a time line that identifies the specific steps—including training—and related resources required to implement the recommended system. Include a narrative explanation that includes a discussion on the effects of project constraints, such as time, conversion method, etc. and a description of the recommended training plan.

Documentation Plan Summary: Specify and explain each type of documentation required for ongoing support—technical and user—of the proposed system.

Support and Maintenance Plan Summary: Provide a plan that outlines responsibilities and related resources necessary to support and maintain the proposed system—software, hardware, and networks.

Finalize the paper.

Finalize the PowerPoint presentation.