Software review

Summary Quibbles aside,Notebook II is a solid program for people who need a database manager for large fields of text. It is efficient, reliable, well documented, and easy to use.WordStar users may well already know about Pro/Tem Software's other programs,Footnote andBibliography.Lawrence C. Becker, a professor of philosophy at Hollins College, is adding to his list of books a study of reciprocity and nonvoluntary social obligations.     

Software review

Conclusion Given the current state of word processing and the hardware for which it has been designed, Word-Perfect seems to be among the best of what is available. It manifests a reasonable balance between the demands of the novice, who will appreciate the simplicity of its user interface, and those of the experienced person, who will be more interested in the power and flexibility of the tool. This simplicity has, however, been achieved at the cost of a certain amount of rigidity. We wonder, then, how long the package can remain current with respect to the evolution of word processing. At the same time, we realize that not every academic user of word processing will care about the evolution of this genre. For those who don't our criticisms are mostly irrelevant, although anyone interested in this package would do well to compare it to something on the level of Nota Bene or T3.Dr. Willard McCarty, an active Miltonist, is also interested in word processing and database management for microcomputers. Patricia Hood specializes in text processing on microcomputers and mainframes and does consulting and teaching in these areas. Both work at the University of Toronto.     

Software architecture review by association

During the process of software design, software architects have their reasons to choose certain software components to address particular software requirements and constraints. However, existing software architecture review techniques often rely on the design reviewers’ knowledge and experience, and perhaps using some checklists, to identify design gaps and issues, without questioning the reasoning behind the decisions made by the architects. In this paper, we approach design reviews from a design reasoning perspective. We propose to use an association-based review procedure to identify design issues by first associating all the relevant design concerns, problems and solutions systematically; and then verifying if the causal relationships between these design elements are valid. Using this procedure, we discovered new design issues in all three industrial cases, despite their internal architecture reviews and one of the three systems being operational. With the newly found design issues, we derive eight general design reasoning failure scenarios.