BSA375 (Version 13) – Week 5- Learning Team-Final Project – Service Request SR-kf-013 Paper
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.
Grading for this weeks team assignment will based on completion only and will not be graded in detail. The purpose of turning this in for completion only credit is to keep the learning teams on track for completion of the final paper due at the end of Week 5.
Draft the first 4- to 6-page section of the Service Request SR-kf-013 Paper, due in Week Five. Include the following:
- Statement of Scope and Goals: Specify which functions will be included in the project. Identify the goals and 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.
- Summary of project feasibility: Include specific operational, technical, and economic feasibility analyses. Operational and technical issues should specify how each issue will be addressed. The economic analysis must include quantified specific benefit and cost areas.
- Current business process summary: Provide a flowchart and a separate high-level logical data flow diagram of the current process.
Proposed system requirement list: List specific individual requirement needs in measurable and objective terms.
Draft the next 4- to 6-page section of the Service Request SR-kf-013 Paper, due in Week Five. Include the following:
- 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 milestone 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.
Draft the next 4- to 6-page section of the paper, due in Week Five. Include the following:
- 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.
Draft the final 4- to 6-page section of the paper. Include the following:
- Testing process summary: Define a test plan or script that identifies major software functionality and hardware to be tested 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 discusses the effects of project constraints, such as time and conversion method, and include a description of the recommended training plan.
- Documentation plan summary: Specify and explain each type of documentation required for ongoing technical and user support for the proposed system.
- Support and maintenance plan summary: Provide a plan that outlines responsibilities and related resources— software, hardware, and networks—necessary to support and maintain the proposed system.
Finalize and submit the paper.