|
|
|
|
Remus, Horst
IBM
San Jose, California
|
|
|
|
|
|
|
|
Date Reviewed |
|
|
1 - 10 of 35
reviews
|
|
|
|
|
|
|
|
How to Improve the Calibration of Cost Models Ebrahimi N. IEEE Transactions on Software Engineering 25(1): 136-140, 1999. Type: Article
Estimating costs and schedules for software engineering productshas been a problem from the beginning of computer programming in the1950s. It has been complicated by the often misleading dependency ofproductivity on product size and by...
|
Jun 1 1999 |
|
|
|
|
|
|
Software process quality: management and control Kenett R., Baker E., Marcel Dekker, Inc., New York, NY, 1999. 241 pp. Type: Book (9780824717339)
In the 1950s, programmers were so excited when they were getting atechnical solution to a problem to work that quality and otheruser-oriented characteristics were almost completely ignored. Some ofthat is still true today, but with pro...
|
Apr 1 1999 |
|
|
|
|
|
|
Modeling and Evaluating Design Alternatives for an On-Line Instrumentation System: A Case Study Waheed A., Rover D., Hollingsworth J. IEEE Transactions on Software Engineering 24(6): 451-470, 1998. Type: Article
When hardware and software became more reliable, the question of performance, running time, and disk space used became more important. In the 1970s, the requirement of instrumentation, involving real-time monitoring of the process and ...
|
Mar 1 1999 |
|
|
|
|
|
|
Distributed application development with PowerBuilder 6 Barlotta M., Manning Publications Co., Greenwich, CT, 1999. Type: Book (9781884777684)
PowerBuilder has become one of the leading environments for the development of large programming systems. It is not surprising that there is a trend toward specialization of various application areas. The publisher is offering a series...
|
Jan 1 1999 |
|
|
|
|
|
|
Parameterized duplication in strings Baker B. SIAM Journal on Computing 26(5): 1343-1362, 1997. Type: Article
Baker discusses duplication of code within the same programming system, which she applies to software maintenance. Of course, this work has much broader application, such as the detection of pirated code or of plagiarism....
|
Dec 1 1998 |
|
|
|
|
|
|
Discovering models of software processes from event-based data Cook J., Wolf A. ACM Transactions on Software Engineering and Methodology 7(3): 215-249, 1998. Type: Article
The authors define a process as “a set of activities applied to artifacts, leading to the design, development, or maintenance of a software system.” They observe that inherent in every project is a process (whether ...
|
Dec 1 1998 |
|
|
|
|
|
|
Cognitive patterns Gardner K., Rush A., Crist M., Konitzer R., Teegarden B., Cambridge University Press, New York, NY, 1998. Type: Book (9780521649988)
The authors discuss extending the benefits of abstraction (which led to object-oriented programming) to the whole program development process, starting with the modeling of business systems. The basis of this approach is cognitive mode...
|
Aug 1 1998 |
|
|
|
|
|
|
Surviving a process performance crash Laitinen M., Fayad M. (ed) Communications of the ACM 41(2): 83-86, 1998. Type: Article
Laitinen and Fayad briefly discuss how and why to introduce a software development process. They state that the only way to improve work quality or increase productivity is to change the process, not to set goals above the current stat...
|
May 1 1998 |
|
|
|
|
|
|
PowerBuilder 5 developer’s resource Schumacher R., Bosworth B., Prentice-Hall, Inc., Upper Saddle River, NJ, 1997. Type: Book (9780132711562)
Teaching advanced programming techniques without first teaching their theoretical backgrounds leads to the need for lengthy explanations, such as the explanations of polymorphism and other mathematical terms found here, and consequentl...
|
Feb 1 1998 |
|
|
|
|
|
|
Using a Protean Language to Enhance Expressiveness in Specification Bloom B., Cheng A., Dsouza A. IEEE Transactions on Software Engineering 23(4): 224-234, 1997. Type: Article
In the 1950s and 1960s, the early years of computer programming, there was a saying among programmers that every professional programmer had to invent his own programming language, or at least had to be involved in the definition of on...
|
Oct 1 1997 |
|
|
|
|
|
|
|
|
|
|
|