Ridoran Outline
Ridoran MRP Outline
Team A
December 9, 2011
BSA/375
Deborah Marshall
1) Introduction
2) Statement of scope and goals
a) Specify what functions are included in the project.
3) Supporting measures for success
a) Specify tangible measures for determining the relative degree of success of the completed project. Measures must correlate with goals specified in the first section.
4) Summary of project feasibility
a) Include specific operational, technical, and economic feasibility analysis. Operational and technical issues must specify how each issue is addressed. The economic analysis must include specific benefit and cost areas.
5) Determination of requirements
a) Identify specific analysis methods, used to determine user needs.
6) List of confirmed requirements
a) Categorize each system requirement identified for last week’s assignment as mandatory or optional.
7) Proposed system process view
a) Provide a flowchart of the proposed process.
8) Functional allocation modeling
a) Specify how each proposed system function would be allocated in terms of required hardware, software, and Human-Computer Interface (HCI).
9) Logical system model
a) Provide a high-level logical data flow diagram of the proposed system.
10) Preliminary design model
a) Provide a diagram illustrating the overall logical information architecture.
11) Design trade-off approach
a) Specify tradeoffs between cost, schedule, and performance. A fast and inexpensive solution may not adequately address performance requirements.
12) Detailed design process and specifications
a) Specify separate recommended decisions for software design, hardware, and networks. Include a resolution of HCI considerations.
13) Physical system model
a) Illustrate recommended decisions in information architecture diagrams.
14) Testing process summary
a) Define a test plan or script identifying major software functionality and
Team A
December 9, 2011
BSA/375
Deborah Marshall
1) Introduction
2) Statement of scope and goals
a) Specify what functions are included in the project.
3) Supporting measures for success
a) Specify tangible measures for determining the relative degree of success of the completed project. Measures must correlate with goals specified in the first section.
4) Summary of project feasibility
a) Include specific operational, technical, and economic feasibility analysis. Operational and technical issues must specify how each issue is addressed. The economic analysis must include specific benefit and cost areas.
5) Determination of requirements
a) Identify specific analysis methods, used to determine user needs.
6) List of confirmed requirements
a) Categorize each system requirement identified for last week’s assignment as mandatory or optional.
7) Proposed system process view
a) Provide a flowchart of the proposed process.
8) Functional allocation modeling
a) Specify how each proposed system function would be allocated in terms of required hardware, software, and Human-Computer Interface (HCI).
9) Logical system model
a) Provide a high-level logical data flow diagram of the proposed system.
10) Preliminary design model
a) Provide a diagram illustrating the overall logical information architecture.
11) Design trade-off approach
a) Specify tradeoffs between cost, schedule, and performance. A fast and inexpensive solution may not adequately address performance requirements.
12) Detailed design process and specifications
a) Specify separate recommended decisions for software design, hardware, and networks. Include a resolution of HCI considerations.
13) Physical system model
a) Illustrate recommended decisions in information architecture diagrams.
14) Testing process summary
a) Define a test plan or script identifying major software functionality and