Business Application System

Topics: System software, Application software, Computer software Pages: 5 (1618 words) Published: August 21, 2011
Business Application System
University of Phoenix
BSA 411, Systems Analysis Methodologies
September 6, 2010

There are many different business problems or business opportunities in today’s business world that need to be corrected. I have been a part of a few project teams that were responsible for correcting a few of these business problems at some of the different companies I have worked for. In this paper I will discuss the one that I feel was the biggest success due to how it helped the company. Business Application System

Many years ago I worked for the hydraulic parts division of Dana Corporation particularly in the machining area. During this time there arose the need for a better business system to track what parts we had on hand and what parts we needed to make to fill the incoming orders. Being that I had a lot of experience in my department I was asked to be a part of the project team to create the system. The new business system would need to be able to track, in real time, what parts were needed to fill customer orders, what parts we currently had on hand in storage, and what parts were currently in the process of being machined. In order to make this business system happen there were several barriers we would have to overcome. Some of the barriers included assessing the current business situation and the business systems needs, designing the new business system that would be used to replace the old system and fix the business problem, and implementation of the new business system with as little interruption to the company output as possible. Assessing the Business System

There are several different methods that can be used to gather information for analyzing requirements, some of which are more effective than others. One of those methods of information gathering for analyzing requirements is to survey to all of the employees that you can within the company. The major drawback to the survey method is that you must be very careful about the question you ask so that you get back the most useful information. Another drawback with the survey method is that many people that receive a survey might not fill it out and send it back to you. Another method of information gathering for analyzing requirements is to interview people and departments about their daily activities and needs. The biggest drawback to this method is the time that it can take to conduct all these interviews. Also some people may not want to talk in groups and some people may only feel comfortable talking when they are in a group setting. A third method of information gathering is to go around to the different areas in a corporation and get as much information about their processes as you can and then look at the standard operating procedures for the process the corporation has. This can be one of the better methods to use because you will not have to worry about people telling one thing and the company procedures saying to do it another. When you look at the company’s standard procedures you will find the approved method of doing business within company. A very good way to gather information in this third method is to go around a company and watch people and make as many notes as possible on how business is done on a day to day basis. In the end there is no one correct or incorrect method for gathering the required information. In fact the best method for gathering information for analyzing requirements is a combination of the multiple methods. The one thing to keep in mind is that the method used should be the one that is best suited for the type of information you are trying to gather. Once the information is gathered you will then move into designing the business system. Designing the Business System

In the past most of the software development cycles followed a waterfall type technique. In this type of technique every step was dependant on the one before it and one step could not occur without...

References: Blaha, M. & Rumbaugh, J. (2005). Object-Oriented Modeling and Design with UML (2nd ed.). Prentice Hall.
Curran, T. & Ladd, A. (2000). SAP R/3 Business Blueprint: Understanding Enterprise Supply Chain Management. Prentice Hall.
Stockley, D. (1996-2010). Implementing new business systems successfully. Retrieved September 5, 2010, from
Continue Reading

Please join StudyMode to read the full document

You May Also Find These Documents Helpful

  • Essay about Business
  • business information system Essay
  • Business Information Systems Essay
  • Business Systems Analysis Essay
  • Management Information System and Business Strategy Essay
  • Introduction to business information systems review Essay
  • IBM 320 – Business Application Essay
  • Monitoring System Essay

Become a StudyMode Member

Sign Up - It's Free