Running Head: Business Application System Proposal
Business Application System Proposal
Lindsey King
BSA/411
May 25, 2014
Karen Miles
1
Running Head: Business Application System Proposal
2
Incorrect spacing
Business Application System Proposal
This paper will give a summary level description of a proposed tracking system
for supplies to be used by a drilling company.
Constraints for the implementation
of this new tracking system would include manpower. Employees are used to the manual
system, and fears using an automated system that involves new hardware and software.
Budget is another constraint. Most of the budget is allocated to the cost of
purchasing the new system, which not only includes the software, but also a new
computer to run the advanced program, plus the cost of the license per user.. Employee
training is also a constraint. Only selected employees can be trained to use the new
system. Hence, part of the training includes the development of a user’s manual that will
document step-by-step procedures on how to use the system. The last possible constraint
is the schedule for the transitioning to the new system. In order to facilitate a smooth
transition, most software companies suggest letting the old and the new system overlap
for a time, called a transition period, until it is certain the new system is efficiently
working as intended.
.
In addition to the survey, information regarding the company’s processes must be
gathered. This information includes the business requirements for purchasing and
maximum capacity of the storage area. The success and speed of the implementation
depends, in part, on the thoroughness of the information-gathering step (Curran, & Ladd,
Running Head: Business Application System Proposal
3
2000). When sufficient information is gathered, the developers build a prototype tracking
system, which is customized to the specific business requirements of the company. The
new system will undergo a test run. The company will upload real information into the
system to test its real time tracking capabilities for several weeks. System operators will
do multiple data verification to check the efficiency of the system. During the test run,
the system developers will also train selected company employees to operate and become
proficient in running the system.
topologies and the way in which network peripherals connect to one another.
Errors in the system can be easily identified and isolated by following the model closely.
Each peripheral can be tested separately to determine if, and where, the system failed to
communicate, and transport data to the other peripheral units. The system’s physical
design, therefore, allows for easy troubleshooting and faster recovery (Majewski, 2005).
Once the final and modified version of the software is ready, it is loaded onto a
server, where it can be retrieved and installed on individual computers for different users.
Each user can retrieve and work on a specific module of the software, then restore it on
the server. However, the data will only reside on the server for real time update and
tracking. During the transitioning phase, automated real time tracking and manual
tracking will be done for a couple of weeks. The parallel tracking systems will be
compared and the performance of the new system will be evaluated against the old
system. Once the new system is fully integrated and proven to work efficiently, the old
system will be phased out in compliance with regulations. According to GAAP mandate,
whenever there is a new accounting system, the old data must be kept within the facility
Running Head: Business Application System Proposal
4
and made available upon request. Another backup data should also be stored outside the
company, usually in a safety deposit box.
Although it rarely happen, it is not impossible that a complete transitioning will
occur once the new software is implemented. In this instance, the old system is
immediately phased out once the new system is in place. This usually occurs when the
old system can no longer cope with the current business requirements of the company, or
when the company cannot afford to purchase new hardware and the existing one cannot
run both systems. This choice is allowed if there are hard copies of the old system’s
records that can be filed and easily retrieved upon request (Stockley, 2010). The company
usually assigns an in-house team, which receives intensive training from the software
developers, to manage slight internal modifications to the software to cope with the
changing business demands of the company. However, the software developers should do
serious changes, such as the creation of new modules.
In conclusion, the implementation of the new tracking system will boost the
company’s competitive edge and efficiency. Problems arising from late delivery of
supplies, which causes delay in job completion and customer dissatisfaction, are no
longer an issue with an automated and real time tracking system that monitors expected
delivery dates of supplies.
Running Head: Business Application System Proposal
5
References:
Blaha, M., & Rumbaugh, J. (2005). Object-Oriented Modeling and Design with UML
(2nd ed.). Prentice Hall. Retrieved from
http://www.cs.toronto.edu/~jm/2507S/Notes04/OOA.pd
Curran, T., & Ladd, A. (2000). SAP R/3 Business Blueprint: Understanding Enterprise
Supply Chain Management. Prentice Hall. Retrieved from
http://sappdf.blogspot.com/2010/08/sap-r3-business-blueprint-understanding.html
Heba. (2007). Rational Unified Process (RPU). Retrieved from
http://searchsoftwarequality.techtarget.com/definition/Rational-Unified-Process
Majewski , S. (2005). Designing Enterprise-Level Business Systems. Retrieved from
http://blogs.dotnetnerds.com/steve/articles/298.aspx.
Stockley, D. (2010). Implementing new business systems successfully. Retrieved from
http://derekstockley.com.au/lgpro.html
Running Head: Business Application System Proposal
6
Organization (20%) – 0 – 3 points for 15 point paper.
The introduction provides a sufficient background
on the topic and previews major points.
1. Purpose/Objective of the paper is presented
and is immediately clear.
2. Sections support the objective and cover the
topics.
3. Approach of subject matter is presented in a
logical flow.
4. Conclusion/recommendations follow logically
from the body of the paper
2.0 – points received. All papers require an introduction. An
introduction states the subject to be discussed within the paper.
For this week, the subject was selecting a business system
application that would address a business issue or opportunity.
Secondly, the introduction must state the 3 most important points
within the reading assignment and relate how these barriers are
encountered during business analysis.
Content/Development/Analysis (60%) – 0 – 9 points
for a 10 point paper.
Covers and addresses the required components
including all the requirements for the paper in terms of
subject.
1. Includes additional areas that support the
required topic.
2. Provides insight throughout the paper.
3. Provides justification on pros and cons
4. Sufficient research to cover the topics and
components.
5. Provides justification on points and issues.
6. Shows understanding and application of
information technology from an overall
perspective.
7. Explored, understands and presented key areas
7.0 – points received – The paper contained some very good
information. However, the paper does not meet the requirements
for this week. It appears to be providing a summary discussion of
points for collecting requirements. The paper did not select an
actual system to discuss and map to barriers. It does appear there is
a lot of information that is not concisely presented as it is loaded
with generalizations without insight in several areas. Students
must have a good comprehension of the software, the modules and
be able to explain from a user perspective.
Mechanics/Clarity (20%) – 0 – 3 points for
15 point paper
1. APA Format (Abstract not required). Margins,
references format correct, quotes, citation;
running head and page numbers correct; font
size is 12-point.
2. Grammar, punctuation, sentence structure
(PLEASE TURN ON YOUR SPELL
CHECKER).
3. Define out of the ordinary terms and analogies.
4. All content is relevant to the topic/subject;
sentences add value to the paper.
5. Words used are precise and unambiguous.
6. Transitions between sentences/
paragraphs/sections help maintain the flow of
thought.
7. Does not exceed the word count. Title papers
and References are not counted as part of the
word count. There must be at least 2
references are required for all written
2.0 – points received. Overall, good job on meeting the APA
requirements. There needs to be a running head label on the cover
page. Please review the paper requirements each week.
Running Head: Business Application System Proposal
assignments.
Paper Grade: 11(The paper was late. There is a 20% deduction for late papers. I
will only deduct 1 point this week. All future late papers will received 20%
deduction) FINAL GRADE: 10
7
Purchase answer to see full
attachment