SR-kf-013
Service Request SR-kf-013 Paper (Preparation)
BSA/375
Outline
1. Project scope
a. “What problem or opportunity does the project address?
b. What are the quantifiable results to be achieved?
c. What needs to be done?
d. How will success be measured?
e. How will we know when we are finished?” (Valacich, Joseph. 2012. P. 53)
2. Goals
a. Develop a working system.
b. Gather data that can be used when the system is develop.
c. Maintain system performance.
3. Functions
a. Collect data from the three Kudler stores.
b. Maintaining the data stores.
c. Producing as well as developing data from various sinks.
4. Accomplishments
a. When a system is developed that is operational.
b. When data has been gathered from the three Kudler stores.
c. When the system successfully performs the tasks it was designed to.
5. Measures
a. Prototype – The prototype can be used as a way to measure the success of the system that was developed. The prototype will also help identify any issues the system currently has.
b. Complete Data Collection – The data collection process will be complete when the system developers have successful collected information from all three Kudler stores. This information will be relevant and will help further the development of the system.
c. Monitoring System Performance – The system will need to be monitored to see if the performance of the system is consistent. When the system shows constant high performance then the system has been successfully developed.
6. Project feasibility
a. Operational – The operational analysis will show if the system can solve problems as well as meet the opportunities present in the project scope. The modified database and programming do not require increased levels of computer knowledge for employees or managers. One issue operational issue is the system not optimizing the opportunities available. The way this issue will be addressed is by looking over the opportunities available and
BSA/375
Outline
1. Project scope
a. “What problem or opportunity does the project address?
b. What are the quantifiable results to be achieved?
c. What needs to be done?
d. How will success be measured?
e. How will we know when we are finished?” (Valacich, Joseph. 2012. P. 53)
2. Goals
a. Develop a working system.
b. Gather data that can be used when the system is develop.
c. Maintain system performance.
3. Functions
a. Collect data from the three Kudler stores.
b. Maintaining the data stores.
c. Producing as well as developing data from various sinks.
4. Accomplishments
a. When a system is developed that is operational.
b. When data has been gathered from the three Kudler stores.
c. When the system successfully performs the tasks it was designed to.
5. Measures
a. Prototype – The prototype can be used as a way to measure the success of the system that was developed. The prototype will also help identify any issues the system currently has.
b. Complete Data Collection – The data collection process will be complete when the system developers have successful collected information from all three Kudler stores. This information will be relevant and will help further the development of the system.
c. Monitoring System Performance – The system will need to be monitored to see if the performance of the system is consistent. When the system shows constant high performance then the system has been successfully developed.
6. Project feasibility
a. Operational – The operational analysis will show if the system can solve problems as well as meet the opportunities present in the project scope. The modified database and programming do not require increased levels of computer knowledge for employees or managers. One issue operational issue is the system not optimizing the opportunities available. The way this issue will be addressed is by looking over the opportunities available and