Less costly. Some prototype systems can be developed for 10% to 20% of the cost of traditional systems. For example, one utility company claimed a 13 - to - 1 improvement in development time over traditional methods when prototyping was used to develop 10 major applications.
Disadvantages of Prototyping
Prototyping has the following disadvantages:
Significant user time. Prototyping requires users to devote significant time to working with the AIS and providing the developer with feedback and suggestions. Prototyping may require a greater involvement and commitment than busy users are willing to give.
Less efficient use of system resources. The shortcuts that make rapid prototyping iterations possible do not always allow for efficient use of computer resources. As a result, poor performance and reliability and high maintenance and support costs may be incurred.
Incomplete system development. In large or complex systems with many users, prototyping may not lead to a comprehensive and thorough requirements analysis.
Inadequately tested and documented systems. Because prototypes are used heavily before acceptance, developers are often tempted to shortchange the testing and documentation process.
Negative behavioral reactions. If a prototype is a throwaway, users may react negatively to learning the system and then not being able to use it. They nay also become dissatisfied if all their demands for improvements are not net or if they have to go through too many iterations.
Never - ending development. If prototyping is not managed properly, it may never be completed. Unending iterations and revisions may be proposed because changes are simple to make.
Another tool for improving the development process is a set of software tools referred to as CASE, which is discussed in next section.
Computer - Aided Software Engineering
Software developers have been compared with the shoemaker whose children had to go barefoot: They develop software for others, yet fail to create software to simplify their own work. The development of powerful computer - aided software (or systems) engineering (CASE) tools, an integrated package of computer - based tools that automate important aspects of the software development process, has changed that. CASE tools are used to plan, analyze, design, program, and maintain an information system. They also are used to enhance the efforts of managers, users, and programmers to understand information needs.
Many companies are currently using CASE tools. For example, Florida Power's $86 million customer information system was created using a CASE tool sold by Accenture. The system has been so successful that Accenture packaged it for other utility companies. America West Airlines has more than half of its 90 programmers developing applications using a PC - based CASE tool. Its employees use the tool to model data and business processes, and then the tool uses this information to design and construct a system.
CASE tools do not replace skilled designers. Instead, they are a host of well integrated tools that give developers effective support for all phases of the SDLC. CASE software typically has tools for strategic planning, project and system management, database design, screen and report layout, and automatic code generation.
Less costly. Some prototype systems can be developed for 10% to 20% of the cost of traditional systems. For example, one utility company claimed a 13 - to - 1 improvement in development time over traditional methods when prototyping was used to develop 10 major applications.
Disadvantages of Prototyping
Prototyping has the following disadvantages:
Significant user time. Prototyping requires users to devote significant time to working with the AIS and providing the developer with feedback and suggestions. Prototyping may require a greater involvement and commitment than busy users are willing to give.
Less efficient use of system resources. The shortcuts that make rapid prototyping iterations possible do not always allow for efficient use of computer resources. As a result, poor performance and reliability and high maintenance and support costs may be incurred.
Incomplete system development. In large or complex systems with many users, prototyping may not lead to a comprehensive and thorough requirements analysis.
Inadequately tested and documented systems. Because prototypes are used heavily before acceptance, developers are often tempted to shortchange the testing and documentation process.
Negative behavioral reactions. If a prototype is a throwaway, users may react negatively to learning the system and then not being able to use it. They nay also become dissatisfied if all their demands for improvements are not net or if they have to go through too many iterations.
Never - ending development. If prototyping is not managed properly, it may never be completed. Unending iterations and revisions may be proposed because changes are simple to make.
Another tool for improving the development process is a set of software tools referred to as CASE, which is discussed in next section.
Computer - Aided Software Engineering
Software developers have been compared with the shoemaker whose children had to go barefoot: They develop software for others, yet fail to create software to simplify their own work. The development of powerful computer - aided software (or systems) engineering (CASE) tools, an integrated package of computer - based tools that automate important aspects of the software development process, has changed that. CASE tools are used to plan, analyze, design, program, and maintain an information system. They also are used to enhance the efforts of managers, users, and programmers to understand information needs.
Many companies are currently using CASE tools. For example, Florida Power's $86 million customer information system was created using a CASE tool sold by Accenture. The system has been so successful that Accenture packaged it for other utility companies. America West Airlines has more than half of its 90 programmers developing applications using a PC - based CASE tool. Its employees use the tool to model data and business processes, and then the tool uses this information to design and construct a system.
CASE tools do not replace skilled designers. Instead, they are a host of well integrated tools that give developers effective support for all phases of the SDLC. CASE software typically has tools for strategic planning, project and system management, database design, screen and report layout, and automatic code generation.
การแปล กรุณารอสักครู่..