Requirements Matrix
Form Identification
Date:
Document Version:	Draft
Last Saved:	4/20/21
Customer Name:	See Contract
Customer Contact:	Instructor Name
Project Manager:	Student Name
Technical Lead:	N/A
Project Name:	See contract summary
Project Phase:	Scope and Requirements
Change Log
Version	Date	Modified by	Notes
Draft	1/29/16	add PM name	Add notes for updates made for this version

Case# 2 Requirements Matrix template (3) Q- Search Sheet Home Insert Page Layout Formulas Data Review View LI A TT. Pictures Shapes Add-ins Recommended B Sparklines Slicer Hyperlink New Comment Text Header & Header & 9 Box Footer Charts PivotTable Recommended Table Pivot Tables F16 fx A D E F 1 J Requirements Matrix: Complete the document by describing the contract requirements. The requirements should be more specific with regards to what will be delivered. Add assumptions, contraints and risks. Insert a sub requirements line if nee example, you can add a 1.1 sub requirement of 1.0 Contract Requirements Requirement Statement Key Assumptions Constraints Risks 1 2 Req ID 3 1.0 4 2.0 5 3.0 4.0 Category Functional Functional Data Knowledge Transfer/Training System Architecture Operational Functional Functional add category add category add category add category add category add category add category add category 7 5.0 8 6.0 9 7.0 10 8.0 11 9.0 12 0.0 131.0 14 12.0 15 12.0 16 14.0 17 15.0 18 16.0 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 Overview Project Requirements + Ready + 85% 4553494 X + learn-us-east-1-prod-fleet02-xythos.content.blackboardcdn.com/5ddc079f9352b/4553494?X-Blackboard-Expiration=161897400... Q Update 4553494 1 / 1 92% + Case# 2 - Requirements meeting minutes Meeting Purpose Location Date & Time Facilitator Next Meeting Customer Requirement Meeting WebEx January 12, 2021; 1- 2:00 PM Tony Stark 1 Agenda Items & Meeting Summary The Eagles Nest core business leaders conducted an internal meeting to discuss the key requirements that would be needed for the overall project to be a success. Eagles Nest discussed the urgency of getting the system online by October 2021. The customer confirmed that the system is required to launch their new fan-based marketing strategies. The team begin discussing the Ul solution requirements for the system. The Ul must have the ability to conduct an inventory search to determine the amount of product on hand. The screen should be able display 25 records on the screen by default to allow an easy review. The UI should also allow the screen to scroll up to 50 records before having to load a new page. The primary key for conducting a product look up should allow the use of the product- key and date added. The UI should also provide a drill down on the product-key and display a picture of the product with full 360 view. The system should also integration API which will allow it to connect to key suppliers' systems. The system should also provide the ability to drill down to provide detail inventory on hand and forecast of available supply based on historical usage numbers. The UI will also provide a pricing index score for each product listed. After clicking the "index score", the UI will display a graph listing the pricing model score to market price for days, months, and year to date. The UI can also sort the product from the highest to the lowest index score. The higher the score defines how well the model is performing. The Ul system will also generate reports of the product pricing scores. The system will have an SFTP connection that will allow the customer's partner to send secure data files containing product information. The solution will require an ETL script to intake the data and prepare for loading into the system. The process should be setup to run weekly and an alert should be sent if the job fails. The team will need to conduct 3 iterations of the pricing model development and testing before deploying the solution to production. The solution will connect to an Oracle database with the capacity of 1 Terabyte of storage. The team will need to generate a prototype of the solution to demonstrate capabilities. Case# 2 Requirements Matrix template (3) Q- Search Sheet Home Insert Page Layout Formulas Data Review View LI A TT. Pictures Shapes Add-ins Recommended B Sparklines Slicer Hyperlink New Comment Text Header & Header & 9 Box Footer Charts PivotTable Recommended Table Pivot Tables F16 fx A D E F 1 J Requirements Matrix: Complete the document by describing the contract requirements. The requirements should be more specific with regards to what will be delivered. Add assumptions, contraints and risks. Insert a sub requirements line if nee example, you can add a 1.1 sub requirement of 1.0 Contract Requirements Requirement Statement Key Assumptions Constraints Risks 1 2 Req ID 3 1.0 4 2.0 5 3.0 4.0 Category Functional Functional Data Knowledge Transfer/Training System Architecture Operational Functional Functional add category add category add category add category add category add category add category add category 7 5.0 8 6.0 9 7.0 10 8.0 11 9.0 12 0.0 131.0 14 12.0 15 12.0 16 14.0 17 15.0 18 16.0 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 Overview Project Requirements + Ready + 85% 4553494 X + learn-us-east-1-prod-fleet02-xythos.content.blackboardcdn.com/5ddc079f9352b/4553494?X-Blackboard-Expiration=161897400... Q Update 4553494 1 / 1 92% + Case# 2 - Requirements meeting minutes Meeting Purpose Location Date & Time Facilitator Next Meeting Customer Requirement Meeting WebEx January 12, 2021; 1- 2:00 PM Tony Stark 1 Agenda Items & Meeting Summary The Eagles Nest core business leaders conducted an internal meeting to discuss the key requirements that would be needed for the overall project to be a success. Eagles Nest discussed the urgency of getting the system online by October 2021. The customer confirmed that the system is required to launch their new fan-based marketing strategies. The team begin discussing the Ul solution requirements for the system. The Ul must have the ability to conduct an inventory search to determine the amount of product on hand. The screen should be able display 25 records on the screen by default to allow an easy review. The UI should also allow the screen to scroll up to 50 records before having to load a new page. The primary key for conducting a product look up should allow the use of the product- key and date added. The UI should also provide a drill down on the product-key and display a picture of the product with full 360 view. The system should also integration API which will allow it to connect to key suppliers' systems. The system should also provide the ability to drill down to provide detail inventory on hand and forecast of available supply based on historical usage numbers. The UI will also provide a pricing index score for each product listed. After clicking the "index score", the UI will display a graph listing the pricing model score to market price for days, months, and year to date. The UI can also sort the product from the highest to the lowest index score. The higher the score defines how well the model is performing. The Ul system will also generate reports of the product pricing scores. The system will have an SFTP connection that will allow the customer's partner to send secure data files containing product information. The solution will require an ETL script to intake the data and prepare for loading into the system. The process should be setup to run weekly and an alert should be sent if the job fails. The team will need to conduct 3 iterations of the pricing model development and testing before deploying the solution to production. The solution will connect to an Oracle database with the capacity of 1 Terabyte of storage. The team will need to generate a prototype of the solution to demonstrate capabilities