L. B. S. Raccoon. The complexity gap. ACM SIGSOFT Software Engineering Notes, 20(3):37-- 44, 1995.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....a translation between both domains. Not only from the problem domain to the solution domain, but also the opposite way (for example, testing and integration) The translation between both domains isn t straightforward and this is where the main activity of software engineering should take place [25]. Closing this gap will improve the engineering process of software tremendous. Features can help to narrow the gap. Features are not only present in the problem domain, but can also be identified in the solution domain (see also 1.2.4) making it possible to decrease the gap. The notion of ....

L. B. S. Raccoon. The complexity gap. ACM SIGSOFT Software Engineering Notes, 20(3):37-- 44, 1995.

....concept should be applied as a general means of exiting vehicles. Another problem, not specifically mentioned above since it plagues many other disciplines as well, is the misuse of statistics, although specific complaints about their misuse in the field of software metrics have been made [163][164]. Serving as a complement to the misuse of statistics is a complete lack thereof. One investigation into the number of computer science research papers containing experimentally validated results found that nearly half the papers taken from a random sample of refereed computer science journals ....

"The Mathematical Validity of Software Metrics", B.Henderson-Sellers, ACM SIGSOFT Software Engineering Notes, Vol.21, No.5 (September 1996), p.89.

....BDI architecture that can be used as the basis for providing such formal specifications of more sophisticated systems. The spirit of this is thus similar to that of Garlan s reusable formal frameworks in which an underlying abstract specification enables refinement to many possible instantiations [11]. Indeed, the notion of framework specifications that can be instantiated and refined to specify systems of a similar class has already been adopted in several areas [6, 9, 19] In line with this, the specification in this paper has been checked for type correctness, but has not been animated nor ....

D. Garlan. The role of formal reusable frameworks. ACM SIGSOFT: Software Engineering Notes, 15(4):42--44, 1990.

....role, commitment, temporality, etc. Document centered models usually represent traces as relations between documents of di erent types. An example is sodos (Horowitz and Williamson 1986b, 1986a) which also includes concepts for software life cycle. Other examples are hypertext models like reth (Kaindl 1993) and hydra (Pohl and Haumer 1995) Hypertext models are particularly suitable for capturing informal or originally unstructured information. Also, using hypermedia features they allow the assessment of information in its original format. Database guided models are used to register trace ....

H. Kaindl. The missing link in requirements engineering. ACM SIGSOFT Software Engineering Notes, 18(2):30-39, 1993.

....PRG TR 10 92 Delta Oxford University Computing Laboratory 11 Keble Road, Oxford OX1 3QD Select Z Bibliography Jonathan Bowen Abstract This document gives an up to date list of Z references. A version of this bibliography is due appear in the Proceedings of the Z User Workshop, York 1991, edited by John Nicholls, in the Springer Verlag Workshops in Computing series. Further copies of this Technical Report may be obtained from the Librarian, Oxford University Computing Laboratory, Programming Research Group, 11 Keble Road, Oxford OX1 3QD, England (Telephone: 44 865 273837, ....

....preparation system [154] We aim to keep the bibliography up to date and to issue it at least on a yearly basis to coincide with the Z User Meeting. The BibT E X source file used for this bibliography [36] is available via electronic mail by sending a message containing the command send z z91.bib to the PRG archive server [299] at the address archive server comlab.ox.ac.uk . For more information on using the archive server, send the message help to the same address. To add new references to this list, please contact Joan Arnold, the industrial liaison secretary at the PRG, ....

David Garlan. The role of reusable frameworks. ACM SIGSOFT Software Engineering Notes, 15(4):42--44, September 1990.

.... The definition of our dependency hierarchy, which is described in [25, 48] is based on a comprehensive literature survey (e.g. requirements engineering [10, 14, 57, 56, 19, 22, 62] text analysis [42, 61] knowledge acquisition [45, 44] recording design rationale [7, 8, 57, 15] hypertext [11, 12, 3, 2, 16, 4, 67, 33, 17, 27, 39, 63, 68, 9, 35, 64, 69]) The objects between which the dependency can be created are defined by the attribute from obj and to obj. In addition, an ranking can be defined for the dependency for which temporary is the default value. The above described generic dependency type is defined in O Telos as: ....

H. Kaindl. The Missing Link in Requirements Engineering. ACM SIGSOFT Software Engineering Notes, 19(2):30--39, 1993.

....needed in refactoring, specifically class invariants and exclusive components. The research described here helps lay the foundation for the Software Refactory [85] research project at the University of Illinois. A refactory is a place where refactoring is performed. Whereas a Software Factory [110] takes in a specification as the raw materials and produces from them a software implementation, a Software Refactory takesinbothanexistingsoftware implementation and new specifications and uses refactoring and other techniques to produce an improved software implementation. The next two ....

Walt Scacchi. The USC system factory project. ACM SIGSOFT Software Engineering Notes, 14(1):61--82, January 1989. 194

....from their importance in real time systems as many accidents could have been avoided if formal methods were used. An example of such an incident is the delay in the first space shuttle flight due to an improbable race condition that went undetected during the multiple hand runs through the system [Gar81]. Existing formalisms that are applied in the specification of real time systems may be grouped into four broad categories [Roe90] ffl Temporal Logics ffl Operational Semantics ffl Process Algebras ffl Assertional Methods 2.1 Temporal Logics Temporal logics have been a popular way of trying ....

J.R. Garman. The bug heard round the world. ACM SIGSOFT Software Engineering Notes, 1981.

....but, in broad terms, is restricted to a description of the languages and tool sets, the data objects and aggregates, and the external and internal policies that affect the behaviour and usage of the tools. The emergence of the Portable Common Tools Environment (PCTE) standardisation effort [27] served to focus attention more precisely onto some finer issues, such as details of the database support requirements for SEEs and other complex environments such as CAD support systems, and onto issues of tool interconnection. Subsequently, several reference models have emerged, including the ....

Thomas, I., The PCTE Initiative and the Pact Project, ACM SIGSOFT Software Engineering Notes, 13 (4) Oct. 1988: pp. 52-56.

....the associations between entities and relationships, the cardinalities of these associations, etc. Supplementary product information subsumes additional (product) artifacts which must be recorded to enable traceable system development, for example annotations which provide explanations (e.g. [17]) contribution structures (e.g. 10] goals and organizational information (e.g. 35;34] and design decisions (e.g. 4] Process observation information subsumes data about the process by which the (supplementary) product has been produced. This may include information about the executed ....

H. Kaindl. The Missing Link in Requirements Engineering. ACM SIGSOFT Software Engineering Notes, 19(2):30--39, 1993.

No context found.

Part 1: The Language of Case Studies and Formal Experiments, ACM SIGSOFT Software Engineering Notes, vol. 19, no. 4, pp. 16 20, Oct. 1994.

No context found.

D. Garlan. The role of reusable frameworks. ACM SIGSOFT Software Engineering Notes, 15(4):42--44, September 1990. 13

No context found.

D. Garlan. The role of reusable frameworks. ACM SIGSOFT Software Engineering Notes, 15(4):42--44, September 1990.

No context found.

D. Garlan. The role of reusable frameworks. ACM SIGSOFT Software Engineering Notes, 15(4):42--44, September 1990.

No context found.

D. Garlan. The role of reusable frameworks. ACM SIGSOFT Software Engineering Notes, 15(4):42--44, September 1990.

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC