FRINK Linked Data Fragments server

Matches in SemOpenAlex for { <https://semopenalex.org/work/W79999240> ?p ?o ?g. }

• W79999240 startingPage "67" @default.
• W79999240 abstract "HOW TO INTEGRATE SOFTWARE WITHOUT A HITCH In today's complex business world, accountants increasingly are called on to help plan and install computerized business systems. In this article, Ira R. Weiss, CPA, PhD, dean of the Madrid Business School, Madrid, Spain, and Durairaj Asaithambi, CPA, an accounting systems project supervisor at Houston Lighting & Power Co., Houston, out-line guidelines for a successful installation. The authors acknowledge the contribution of Thomas J. Farfell, manager, Houston Lighting & Power Co., to this article. Most businesses rely heavily on computer software to handle accounting, purchasing, inventory and other operations. But often they are not satisfied with stand-alone software because they want to integrate it with other, complementary programs to do more complex jobs. For example, if the accounting department's software could talk to purchasing's and the sales department's software, much data-entry duplication could be eliminated. In addition, with such a link, data on materials ordered by purchasing instantly could be incorporated into accounting's computer to produce up-to-the-minute information on cash flow and other financial and inventory information. Linking discrete and diverse programs so they work seamlessly--that is, as if there is no apparent separation between them--takes considerable planning. But once the integration is accomplished, the resuiting software system is cost-effective and should pay for itself within one to six years. GUIDELINES FOR SUCCESS Following are practical guidelines for senior management, project teams and accountants involved in the design and implementation of integrated systems: 1. Management commitment. An organizational change as major as this one requires the full support of senior management. If management fails to communicate the importance of the project to the staff, chances are it will fail no matter how well it is planned. 2. Project team. Many integrated software projects fail, or are only no better than marginally successful, because key people are left out of the development loop and the responsibility for designing the system is given exclusively to management information systems professionals. These technical experts may know software integration and management techniques, but probably not the detailed needs of the users and the environment in which the system will operate. As a result, the project team should include representatives of the user groups. In addition, a steering committee comprising the managers of each user department and chaired by the highest-ranking manager should oversee the project. It should consider cost-benefit priorities, staffing, changes the system will require in the work environment, as well as changes in the business environment affected by the system. It also should be able to resolve interdepartmental problems that cannot be solved by the project team. 3. Evaluation of platforms, tools and methods. A complex project requires careful evaluation of more than just the specific software under consideration. The team also must look at the choice of computers, the operating system and the network to be sure they can accommodate the jobs envisioned for them. …" @default.
• W79999240 created "2016-06-24" @default.
• W79999240 creator A5021849688 @default.
• W79999240 creator A5024749958 @default.
• W79999240 creator A5079511747 @default.
• W79999240 date "1993-04-01" @default.
• W79999240 modified "2023-09-28" @default.
• W79999240 title "How to Integrate Software without a Hitch" @default.
• W79999240 hasPublicationYear "1993" @default.
• W79999240 type Work @default.
• W79999240 sameAs 79999240 @default.
• W79999240 citedByCount "0" @default.
• W79999240 crossrefType "journal-article" @default.
• W79999240 hasAuthorship W79999240A5021849688 @default.
• W79999240 hasAuthorship W79999240A5024749958 @default.
• W79999240 hasAuthorship W79999240A5079511747 @default.
• W79999240 hasConcept C110354214 @default.
• W79999240 hasConcept C111919701 @default.
• W79999240 hasConcept C121955636 @default.
• W79999240 hasConcept C127413603 @default.
• W79999240 hasConcept C144133560 @default.
• W79999240 hasConcept C162324750 @default.
• W79999240 hasConcept C162853370 @default.
• W79999240 hasConcept C163867264 @default.
• W79999240 hasConcept C187736073 @default.
• W79999240 hasConcept C195094911 @default.
• W79999240 hasConcept C2777904410 @default.
• W79999240 hasConcept C2778813691 @default.
• W79999240 hasConcept C2779110517 @default.
• W79999240 hasConcept C41008148 @default.
• W79999240 hasConceptScore W79999240C110354214 @default.
• W79999240 hasConceptScore W79999240C111919701 @default.
• W79999240 hasConceptScore W79999240C121955636 @default.
• W79999240 hasConceptScore W79999240C127413603 @default.
• W79999240 hasConceptScore W79999240C144133560 @default.
• W79999240 hasConceptScore W79999240C162324750 @default.
• W79999240 hasConceptScore W79999240C162853370 @default.
• W79999240 hasConceptScore W79999240C163867264 @default.
• W79999240 hasConceptScore W79999240C187736073 @default.
• W79999240 hasConceptScore W79999240C195094911 @default.
• W79999240 hasConceptScore W79999240C2777904410 @default.
• W79999240 hasConceptScore W79999240C2778813691 @default.
• W79999240 hasConceptScore W79999240C2779110517 @default.
• W79999240 hasConceptScore W79999240C41008148 @default.
• W79999240 hasIssue "4" @default.
• W79999240 hasLocation W799992401 @default.
• W79999240 hasOpenAccess W79999240 @default.
• W79999240 hasPrimaryLocation W799992401 @default.
• W79999240 hasRelatedWork W1568028048 @default.
• W79999240 hasRelatedWork W1569570251 @default.
• W79999240 hasRelatedWork W1573324307 @default.
• W79999240 hasRelatedWork W1621431408 @default.
• W79999240 hasRelatedWork W223104605 @default.
• W79999240 hasRelatedWork W2368537399 @default.
• W79999240 hasRelatedWork W239537077 @default.
• W79999240 hasRelatedWork W2404790183 @default.
• W79999240 hasRelatedWork W2406552621 @default.
• W79999240 hasRelatedWork W2414364223 @default.
• W79999240 hasRelatedWork W2414759045 @default.
• W79999240 hasRelatedWork W2414917069 @default.
• W79999240 hasRelatedWork W2482792428 @default.
• W79999240 hasRelatedWork W2502055603 @default.
• W79999240 hasRelatedWork W2768086743 @default.
• W79999240 hasRelatedWork W2798876427 @default.
• W79999240 hasRelatedWork W610913664 @default.
• W79999240 hasRelatedWork W64944389 @default.
• W79999240 hasRelatedWork W973577425 @default.
• W79999240 hasRelatedWork W2262409974 @default.
• W79999240 hasVolume "175" @default.
• W79999240 isParatext "false" @default.
• W79999240 isRetracted "false" @default.
• W79999240 magId "79999240" @default.
• W79999240 workType "article" @default.