计算机专业中英文文献翻译 联系客服

发布时间 : 星期一 文章计算机专业中英文文献翻译更新完毕开始阅读

计算机专业中英文文献翻译

computerized video recording, storage, and playback devices, including CD-ROMS.

Document Management

Networks have made it next to impossible to find the document you want when you want it. Files are often scattered across myriad computers, storage devices, applications, directories, and file formats on the corporate LAN and WAN.

The rapid development of the World Wide Web has exacerbated the problem of maintaining, managing, indexing, and finding important business documents under the guise of home pages - by allowing users to publish and distribute HTML-formatted files far and wide across the Internet and corporate intranets. The development of powerful search engine software (such as Alta Vista) was in inevitable consequence of this trend, enabling users to tap into basic document-management functions text indexing, search, and retrieval - in order to harness the unruly but infinitely rich information resources of this new world.

Workflow capabilities are a natural extension of document management systems and are supported in many of today's commercial products. Users can check out files from server-based virtual libraries, route them to others for review and revision, track who has the file at any time reconcile and merge multiple comments and version into a final draft, and then check the resultant files back into the library, either overwriting the original or saving the final version to a different filename.

Multiplitform transparency, distributed search tools, and standard application programming interfaces are inherent to the Web. Unlike the hierarchically organized file management systems bundled with most operating systems, the Web is a purely decentralized virtual library. Embedded cross-reference can be established from any Web page to any other local or remote Internet resource. Services such as Yahoo allow users to search the world for Web-resident information with as little as a single query. Authoring new Web applications is facilitated by near-ubiquitous implementation of HTML document formatting/ hyper linking and Java application-development standards.

Database Management

Database management systems have long been the principal platform for development of mission-critical corporate applications. Databases are at the heart of more workflow applications. One database contains the process model, which specifies the routes, roles, and rules for

计算机专业中英文文献翻译

document routing. Another database may contain information on the current location and status of documents in process. Others may

contain the information input by users in on-screen electronic forms.

What chiefly distinguishes database management form document management systems is the format of the information they manage. Document management systems can handle the vast majority of information used in any organization, whether it's semi structured and unstructured information, such as the running text in word-processing file, or e-mail message. Database management systems, by contrast, work principally with alphanumeric character text that can be organized into a highly structured set of files, records, and fields. This

information can be linked, indexed, sorted, and filtered in countless ways, which makes databases well suited

to supporting complex, custom-built, function-specific applications. Many databases provide a common pool of information accessible to multiple applications.

计算机专业中英文文献翻译

3

Systems development is always difficult. Most projects that are deemed failures rather cost too much or did not produce useful systems. Large projects are especially difficult. To deal with these difficulties and provide some control over the process, a systems development life cycle has been developed, This system analysis technique breaks projects into manageable pieces. Software tools display interrelationships and integrate modules. Modules have inputs, processing steps, controls, outputs. The prototyping approach is iterative, as opposed to the rigidity of the SDLC method, and provides an early version of the system.

Another way to build systems is to ask end users to develop their own systems using more user-friendly fourth-generation tools such as database management systems (DBMS) or spreadsheets. This last approach carries the risk of lack of testing, incompatibilities, and duplication.

All of the methods mentioned have the name five basic stages: feasibility and planning, systems analysis, design, implementation, and maintenance. Systems designers need to remember that working systems must be maintained and modified as business needs arise. Systems Development Life Cycle The SDLC is one of the most formalized techniques used to develop computer systems. There are difficult versions of this technique, but all have the goal to build computer systems by analyzing the process it should replicate and breaking the process into smaller, more manageable, pieces. This approach avoids problems such as duplicated efforts, incompatible portions of programs, and runaway costs due to situations such as programmer turnover and shifting direction.

A feasibility study is a quick examination of the benefits, goals, cost, and problems of the proposed system solution. The objective of this stage is to decide whether a system is the right procedure to solve the situation.

Planning consists of developing a schedule for the project, appointing team leaders, and laying out a plan.

System analysis determines present system procedures and problems and breaks the current system into pieces. It uses diagrams, such as a visual table of contents, which shows the relationship between the modules of a system.

Systems design describes the new system on paper , including a detailed description of its

计算机专业中英文文献翻译

modules and interrelationships, It then translates this description into workable code.

Systems implementation is the most difficult step. It consists of installing the new system, training and users, making adjustments, and converting from the old system. An important element of this stage is final testing. The final testing and quality control of the new system before it is presented to the end users can uncover problems that can be resolved before multiple end users replicate the problem in production.

Involving end users in the design, education and training is important because it programs system flexibility, recognizes the impact of the new system on the business, and reduces the resistance to change from the end users to the new system.

Maintenance, provides a method to address changing hardware and soft requirements, problems not found during testing, end users who request additional features from the software, and changes to the program that may come from changes in the industry.

Evaluation, the last phase, is important for future projects. The effectiveness of the new system, with regard to reliability, speed, ease of use, and cost, are all important criteria with which to judge the new system.

Prototyping. Prototyping is a systems-building technique that uses more advanced building blocks. The main objective is to construct a working version as quickly as possible, even if the initial working system does not have all of the necessary details. This technique work s best when the necessary system are not too complex and the number of users are limited. Advantages include users which have more flexible, and a working version of the system that is much faster than using SDLC methodology. Rapid application develops the program using advanced development effort is potentially expensive and hard to implement. Tow trends causing this technique to become more popular are the backlog of projects and maintenance in most companies’ IT departments, and the proliferation of powerful and user-friendly software tools. Pseudocode This method was an early technique to help programmers outline the system.. Pseudocode describes the logic of a program. It provides an overview of the program written in “plain” English, without the computer syntax.

Top-Down Design Using this approach, the design of a new computer system begins by looking at the big picture, or the company as a whole. A bottom-up design starts with building computer systems as the need arises and responding quickly to management demands.