BSA 375 Something Great /uophelp.com BSA 375 Something Great /uophelp.com | Page 15

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