Showing papers in "IEEE Software in 1987"
••
TL;DR: The faceted scheme described here is a partial solution to the classification and retrieval problem of software component reuse.
Abstract: To reuse a software component, you first have to find it. The faceted scheme described here is a partial solution to this classification and retrieval problem.
723 citations
••
TL;DR: The Cleanroom process gives management an engineering approach to release reliable products that can be engineered under statistical quality control and delivered with better quality.
Abstract: Software quality can be engineered under statistical quality control and delivered with better quality. The Cleanroom process gives management an engineering approach to release reliable products.
452 citations
••
TL;DR: Reusability remains a puzzle despite its promise, and the authors discuss some answers and possibilities.
Abstract: Reusability remains a puzzle despite its promise. Why? What can be done? The authors discuss some answers and possibilities.
360 citations
••
TL;DR: The issues are technical, not managerial as discussed by the authors, and the answers lie in object-oriented design, not in simply being more organized will not make the reuse problem go away, and the solutions lie in Object-Oriented Design.
Abstract: Simply being more organized will not make the reuse problem go away. The issues are technical, not managerial. The answers lie in object-oriented design.
345 citations
••
TL;DR: The concept of generalized icons is a framework for the design of the next genertion of visual languages.
Abstract: Research into visual and growing in popularity. The concept of generalized icons is a framework for the design of the next genertion of visual languages.
213 citations
••
TL;DR: Reusable components are not enough; program designers need tools that help them understand the components and how to use them.
Abstract: Reusable components are not enough. Program designers need tools that help them understand the components and how to use them. Fortunately, some support tools do exist.
157 citations
••
TL;DR: The RSL couples a passive database with interactive design tools to make reuse an integral part of the software development process.
Abstract: The RSL couples a passive database with interactive design tools to make reuse an integral part of the software development process.
135 citations
••
IBM1
TL;DR: An IBM group recently developed the concept of specification, design, and code can all be reused easily if handled as a building block and applied to systems programming – with success.
Abstract: Specification, design, and code can all be reused easily if handled as a building block. An IBM group recently developed this concept and applied it to systems programming – with success.
112 citations
••
TL;DR: This automated design system conforms to the programmer using a variety of techniques to create systems that meet the needs of the programmer.
Abstract: Program designers use a variety of techniques when creating their systems. This automated design system conforms to the programmer.
98 citations
••
TL;DR: This declarative language takes the best features from the three most popular reusability approaches, but overcomes their flaws and supports language independence, component composition, and tailoring.
Abstract: This declarative language takes the best features from the three most popular reusability approaches, but overcomes their flaws. It supports language independence, component composition, and tailoring.
••
TL;DR: To be a good object-oriented programmer, you should use types and inheritance wisely and ThiS tutorial will help you to do so.
Abstract: To be a good object-oriented programmer, you should use types and inheritance wisely. ThiS tutorial will help you do so.
••
TL;DR: Testing Ada programs is easier with this visual debugger that graphically depicts what the program is doing—and how it is being done.
Abstract: Testing Ada programs is easier with this visual debugger that graphically depicts what the program as doing—and how it is being done.
••
TL;DR: ITS's system focuses on the overall project task instead of focusing on the language tools, which allows for more comprehensive project support.
Abstract: Most integrated environments are built bottom-up, starting with language tools. But this limits comprehensive project support. IST's system focuses on the overall project task instead.
••
TL;DR: How do you keep teams of programmers informed of system changes without burying them in mail messages?
Abstract: How do you keep teams of programmers informed of system changes without burying them in mail messages? Make the environment responsible for propagating changes.
••
TL;DR: No one likes to debug programs, and there is no way to automate the task, but knowledge-based approaches offer some possibilities for the future.
Abstract: No one likes to debug programs, and there is no way to automate the task. However, knowledge-based approaches offer some possibilities for the future.
••
TL;DR: This experimental system features flexible document retrieval, a distributed architecture, and the capacity to store many very large documents.
Abstract: New technology is changing the way we store documents. This experimental system features flexible document retrieval, a distributed architecture, and the capacity to store many very large documents.
••
TL;DR: In this paper, an experiment asked programmers untrained in reuse to evaluate component reusability, and they did poorly, and the experiment was extended to a wider class of programmers.
Abstract: An experiment asked programmers untrained in reuse to evaluate component reusability. They did poorly. Are reusability's promises hollow? Or are there some answers?
••
TL;DR: A new generaffon of operating system, based on extended databases, will supplant the original phase-sequencing and current pipelining program composition mechanisms and is described in this article.
Abstract: A new generaffon of operating system, based on extended databases, will supplant the original phase-sequencing and current pipelining program composition mechanisms. This article describes a working prototype.
••
TL;DR: One of reusability's main problems is how to easily modify available components, so this frame-based approach handles the problem.
Abstract: One of reusability's main problems is how to easily modify available components. This frame-based approach handles the problem.
••
TL;DR: The unique system provides powerful interprocess communication that uses duplex links, does not buffer messages in the kernel, and does not block on communication requests.
Abstract: The unique system provides powerful interprocess communication that uses duplex links, does not buffer messages in the kernel, and does not block on communication requests
••
TL;DR: An effective way to improve software quality is to set measurable goals and then manage your projects to achieve those goals.
Abstract: An effective way to improve software quality is to set measurable goals and then manage your projects to achieve those goals. Hewlett-Packard has developed some methods to do just that.
••
[...]
TL;DR: New exploratory environmetas, like Smailtalk-80, offer improvements in system support for program reading as well as writing, and help train programmers to write readable programs.
Abstract: Research has focused on training programmers to write readable programs. New exploratory environmetas, like Smailtalk-80, offer improvements in system support for program reading as well as writing.
••
TL;DR: Bounded disorder uses hashing and tree indexing to speed key-associative access to data and is robust, coping well with arbitrary key distributions.
Abstract: Bounded disorder uses hashing and tree indexing to speed key-associative access to data. It supports range searches and is robust, coping well with arbitrary key distributions.
••
TL;DR: DSEE provides the best of networks and parallel ism, which lets resources be shared flexibly, and can reduce system build time from overnight to over lunch.
Abstract: DSEE provides the best of networks and parallel ism. It lets resources be shared flexibly, and can reduce system build time from overnight to over lunch.
••
TL;DR: This Lisp-based system helps designers get from prototype to product faster by providing an open architecture and highly integrated development tools.
Abstract: This Lisp-based system helps designers get from prototype to product faster. The key is an open architecture and highly integrated development tools.
••
TL;DR: This proposed mechanism does not yet support secure and well-behaved activity termination in block-structured systems, but is likely to do so.
Abstract: Few exception-handling language proposals support secure and well-behaved activity termination in block-structured systems. This proposed mechanism does.
••
IBM1
TL;DR: This model seeks to change the way tools are developed by enabling them to be extended to handle new kinds of input, not just new function.
Abstract: Monolithic tools that can't be extended to handle new kinds of input, not just new function, are hampering development. This model seeks to change that.
••
TL;DR: This study pinpointed how to make maintenance a part of SQA, the next step in protecting quality as a system evolves.
Abstract: Maintenance plays a vital role in protecting quality as a system evolves. The results of this study pinpoit this study pinpoint how to make maintenance a part of SQA.
••
TL;DR: BNR Pascal reduces the amount of compilation work required to compile BNR Pascal modules, enabling greater flexibility in the way that these modules are implemented.
Abstract: Modularity is invaluable, but changes in one module can have a domino effect on others, requiring significant extra compilation. BNR Pascal reduces this extra compilation.