Verified Document

Design Methods Enterprise Level Business Systems Term Paper

Enterprise-Level Business Information Systems In terms of workplace productivity and efficiency, one key aspect to when developing an effective information system for an enterprise is how to select a system that is simple enough to understand for the vast majority of its users, but technologically forward enough so that it has adequate backup for the data stored within the system's various components. Ideally as well, the system should be able to consolidate all data so that it may be shared at various levels within the business' structure, yet still have adequate passwords and security controls. "Experts say about 65% of all companies have lost control of the management or planning of a computer project at some stage," thus the creation of a system with adequate backup and maximum efficacy cannot be underestimated, not simply from a technical point-of-view, but also the point-of-view of the business as a whole. ("The Computer that Ate the Company, Financial World, 1992). Time may be money in business, but technological comprehensiveness and a future-forward perspective is, as well.

Of course, the needs of such a system will fluctuate with the specific requirements of the enterprise. A sales-based enterprise will necessitate sharing data through the advertising, warehousing, and managerial levels of its structure, while a purely supply-oriented company may require data to be easily accessed only by warehousing and management staff in its early stages. (EIS, 2004). But effective data access is critical to almost all modern enterprises, as well as increased communication between its staff through the use of effective information technology and comfort with accessing the enterprise's data and information.

II. Design Methods

A. Describe which design methods you prefer for developing an enterprise-level information system

Thus, enterprise-level...

The system should be able to consolidate the data needed to run the business effectively so that it may be shared at various levels within the business' structure, yet still have adequate passwords and security controls. Conceptually, one way to reckon such as system would be that of "a data warehouse." (EIS, 2004).
In such a design model, individual data files are stored in a central corporate database. "Once inside the corporate database, those disparate sets of data are used to create consolidated reports, which can be distributed for viewing in a variety of ways." (EIS, 2004). One such example is a database engine from Microsoft, SQL, which can receive transactional data from a variety of sources, such as, for example, sales, purchasing, inventory, and transfer transaction level information to the necessary concerned staff members. (Microsoft, 2004). The Microsoft system effectively deploys the architecture of data warehousing because all data is equally accessible to all whom have the correct password or key. All one needs to have is the necessary software capability to enter the 'warehouse' and to know the correct labels or categories of the data one is looking for. The architecture of data warehousing is simple in its conception. It employs the 'real world' metaphor that, once one is in the warehouse, one can access all information equally quickly.

The ideal computer model, although it would require too much memory for current systems in existence at this time, has been described as "a 3-D computer model" ... that would be the mother of all business tools -- a real-time simulation of what's happening everywhere. Say, for example,…

Sources used in this document:
A. Discuss which business process mapping tools you recommend in documenting the design.

Firstly, the business must map out, what sorts of improvements or future successes, it desires to achieve with the new database design. If improvement of information sharing to increase sales is one goal, for instance, it must quantify the percentile increase it hopes to achieve. The overall success of the business in question must be quantified according to certain overall goals, as well as risks taken into consideration of not pursuing the new design. In documenting this design, firstly, the goals should be defined in terms of increased information sharing and data collection, coupled with the implementation of security procedures. After implementation, an audit of time saved by company members, questionnaires posited to company members regarding the system's ease and safety of usage, as well as an overall tabulation of increased productivity and sales must be taken into consideration. (Jacka & Keller, 2001)

In this area, it is important to remember that when new updates and projects go "astray, about 80% of the problem is management-oriented, not technical. You can hire lots of technicians to solve your problems, but most technicians
Cite this Document:
Copy Bibliography Citation

Related Documents

Enterprise Level Business System
Words: 814 Length: 2 Document Type: Term Paper

Enterprise-Level Business System For this startup company to make maximum use of informational technology, it must create a website that is not used merely for informational purposes, but is designed to handle customer inquiries as well as vendor proposals. Currently this spin-off startup company is not using its informational technology to full capacity. Although each operating group has its own database, enterprise infrastructure has not kept pace with internal needs nor

Enterprise Level Business System
Words: 572 Length: 2 Document Type: Term Paper

Enterprise-Level Business System Determination of Requirements -- Main Objectives Create interactive website for consumers and vendors, rather than simply a visually interesting but non-useful website Create functional internal system of Internet communication and a shared database for all staff at the company. Given company's limited numbers, this is feasible Identify which specific analysis methods needed to accomplish this Interviews with lead staff members to determine company needs and computer literacy Submit questionnaires to current 800 phone

Enterprise Level Business System
Words: 516 Length: 2 Document Type: Term Paper

Enterprise-Level Business System Design and Modeling Specifics Preliminary Design Model Design Trade-Off Approach Specify trade-offs among cost, schedule, and performance to be used in final design choice for hardware, software and human interface. Also include a discussion of the rationale for making these designs choices and any impact known to achieving the confirmed requirements as previously specified. Oracle Systems Pros: Grid system allows the coordinated use of servers and storage. One computer" approach for a whole organization will

Delimitations Today, Modern Business Systems
Words: 20751 Length: 75 Document Type: Research Proposal

A favorite target for conspiracists today as well as in the past, a group of European intellectuals created the Order of the Illuminati in May 1776, in Bavaria, Germany, under the leadership of Adam Weishaupt (Atkins, 2002). In this regard, Stewart (2002) reports that, "The 'great' conspiracy organized in the last half of the eighteenth century through the efforts of a number of secret societies that were striving for

Successful Implementation of Enterprise Resource Planning Systems
Words: 1505 Length: 6 Document Type: Essay

Successful Implementation of Enterprise Resource Planning Systems in Public Settings: A Synthesis of Current Literature As organizations both private and public continue to grow in complexity and sheer size, enterprise resource planning (ERP) has become an increasingly important function in order to effectively and efficiently carry out operations an ensure stability and longevity. The use of information technologies and a variety of different theoretical frameworks has been applied to ERP problems

System Development Life Cycle SDLC
Words: 1611 Length: 5 Document Type: Term Paper

However, the company did feel it should develop its own Database infrastructure that would work with the new underlying database management system and would mesh with existing organizational skills and the selected enterprise software solution. Because the company followed a standardized implementation process, they were able to successfully reengineer their existing business structure. The objective of the System Development Life Cycle is to help organizations define what an appropriate system

Sign Up for Unlimited Study Help

Our semester plans gives you unlimited, unrestricted access to our entire library of resources —writing tools, guides, example essays, tutorials, class notes, and more.

Get Started Now