A rational design process: How and why to fake it
IEEE Transactions on Software Engineering
A": A Language for Implementing Language Processors
IEEE Transactions on Software Engineering
Designing software for ease of extension and contraction
ICSE '78 Proceedings of the 3rd international conference on Software engineering
Chapter I: Notes on structured programming
Structured programming
On the Design and Development of Program Families
IEEE Transactions on Software Engineering
The Modular Structure of Complex Systems
IEEE Transactions on Software Engineering
Jargons for domain engineering
Proceedings of the 2nd conference on Domain-specific languages
Jargons for domain engineering
DSL'99 Proceedings of the 2nd conference on Conference on Domain-Specific Languages - Volume 2
A document driven methodology for developing a high quality Parallel Mesh Generation Toolbox
Advances in Engineering Software
| Hi-index | 0.00 |
Successful software products bring with them the same advantages and difficulties of successful products in other fields: they provide capabilities that their customers need and want. they provide income to the companies that create and sell them. and they must evolve to meet changing needs. Maintaining such software frequently means that it undergoes continual redevelopment and requires special sources of expertise. i.e ., that its developers become specialists in particular aspects of the product, and that new developers added to the task of maintaining the software require long training periods. One approach for ameliorating the maintenance problem is to organize software into families, and to invest in facilities that enable rapid production of family members. We are using a systematic process to define families. design languages for specifying members of families. and quickly develop tools for such languages. The process is known as family-oriented abstraction, specification. and translation (FAST).We have applied FAST to the task of specifying the commands and reports used by technicians to monitor the operation of a telecommunications switch. Such commands. their associated reports. and the accompanying customer documentation form a software family. A key part of the specification for a command or report is the customer documentation for using the command or understanding the report. Our specification language makes the specification of the customer documentation an integral part of the command and report specification. This approach promotes consistency between the software and the customer documentation. makes it easier for developers to write consistent and complete documentation. and allows us to generate the customer documentation from the specification.