Design of an Enterprise-level
Design of an Enterprise-level Business SystemThere are a number of information gathering methods that can be used to determine the requirements for an enterprise-level business system. The information needed in order to do an analysis of a business can be obtained using these different methods. One method is a simple survey or questionnaire, but when using this method careful consideration must be taken when developing questions for the survey to get the desired information. You must be extremely careful about how the questions are worded. The wrong wording or a complicated question can return a false result. Cooperation of the people in the corporation is required in order to have the survey completed and even returned. On average about 30 percent of the sent surveys are returned, this is still considered a valid survey, if less than 30 percent is returned the survey will be invalidated. Another method for business information-gathering is interviews with everyone or just with key people such as department heads in a corporation. The one large problem doing this method is time. This is a very time consuming process and cooperation is not always there. Some employees will not tell you everything you need to know, or they can in
The method I have chosen to use in the future is a simple straight forward survey without open ended questions, followed up by interviewing key people in the corporation, and then going over the operating procedures of the corporation, conducting a walk through on any that are not clear. There are websites that rate and compare them based on usability and function. Depending on which article you read or which expert you talk to you will be told one tool is better then another tool. In business process mapping there are several tools that can be used to convey the information gathered in the information gathering stage. It has many temples and packaged icons that relate to my needs. Also the analyst can use a GUI environment to prototype the enterprise-level business system and get the corporation to sign off on the prototype. This is information gathered is fact, not opinion. When this happens the analyst will have to make a choice either to train his programmers or to out-source the modifications to a company. By using a GUI environment an analyst can get the corporation to sign off on the end users windows. Requirements can be functionally allocated to human interface by using a simple program. The third is observation, or walking through the actual processing associated with the system. What the listed tools and methods allow the analyst to do is get an idea of the required process and environment the corporation expects the users of the enterprise-level business system to have and use. The best tool would be the tool that the user is most comfortable with. Some of the tools are; Microsoft Visio, BPwin, ERwin, Smartdraw, entity relationship diagram (ERD), object oriented diagram (OOD), flow charts, and Hieratical process flow diagram.
Common topics in this essay:
Business System,
BPwin ERwin,
Microsoft Visio,
JAVA GUI,
ERwin Smartdraw,
enterprise-level business system,
business system,
enterprise-level business,
design trade-off,
Visual Basic,
flow charts,
microsoft visio,
information gathered,
gui environment,
system information,
Microsoft C-sharp,
oriented diagram ood,
tools microsoft,
charts hieratical process,
relationship diagram,
diagram ood flow,
ood flow charts,
|
Acceptance Essays
