1. Mr. Larry Bernstein - President,
National Software Council
"Process Improvement via Rapid Prototyping"
Prototyping the user interface screens based on the requirements and reviewing them with customers uncovers a number of gaps and misunderstandings that can be remedied. Finding the disconnects early, at the requirements phase of the project, saves about 30 times the effort of finding them after delivery to the customer. This prototyping approach is a best practice and can be extended throughout software system development. Coupling prototyping with function point analysis measuring software size can control software complexity and feature-creep. The goal is to reduce the function point count by 40% (from initial requirements to delivery) while still delivering the required functionality. Prototypes allow designers to examine alternate approaches and simplify the product. The mantra is "Make it Work, Make it Work Right and, only then, Make it Work Better."
2. Mr. Steve Cross - Director,
Software Engineering Institute
(SEI)
"Enterprise Improvement - Making it happen smarter, faster, cheaper"
Many organizations now recognize the importance of process improvement and have witnessed benefits from using such industry standards as the Software CMM(r), ISO 9001, and other Capability Maturity Models(sm). But looking long term and to the larger picture; the secret to future industrial competitiveness will lie, in large part, on an organization's capability to more smartly and rapidly adopt promising new methodologies and technologies to improve business performance and achieve their long-term business goals.
3. MAJ. David A. Dampier, Ph.D. -
Professor Information Resources Management College National Defense University
"Rapid Prototyping and Incremental Evolution"
Software development is no longer an enterprise where the traditional waterfall method of system construction is acceptable. Information technology is changing at a pace that requires complete system development and fielding in less than 18 months. This is due in part to faster technology insertion, and in part by increased user expectations. Both reasons provide justification for changing the way software is built and fielded. Increased user expectations require that we involve the user more in the requirements engineering process, and deliver the software to the user much more quickly. Faster technology insertion requires that we incorporate new technology into existing products much faster and with less rework.
A new software evolution process is needed to accomplish these goals, along with the automated tools to realize the benefits. Computer-Aided Prototyping is one such method that incorporates the goals and opinions of the user from the beginning of the software evolution process, throughout the lifecycle, and into retirement.
4. Mr. Erik Mettala - Vice President, Microelectronics and Computer Technology Corporation
Topic: To Be Decided
The DACS Track at STC'98 will be
24 April 1998 in Salt Lake City, Utah
For more information visit the STC'98 Web Site at:
http://www.stc-online.org/cd-rom/1998/compend.html
