Abstract
This paper describes the design rationale of OOMMS, a module management system based on an object-oriented model. The concepts of object and module are defined. Modules refer to the software products in general which have interface parts and body parts. Related concepts of a cluster of modules, versions of a module, and revisions of a version are also defined. The tools for checking in C program modules into OOMMS are discussed.
Similar content being viewed by others
Explore related subjects
Discover the latest articles, news and stories from top researchers in related subjects.References
A. Goldberg and D. Robson. SmallTalk-80: The Language and Its Implementation. Addison-Wesley, Massachusetts, U. S. A., 1983.
B. Meyer, Object Oriented Software Construction. Prentice-Hall International, London, U. K., 1988.
D. Ungar and R. B. Smith, Self: The Power of Simplicity. Proceedings of the Second ACM Conference on Object-Oriented Programming Systems, Languages and Applications, 1987, 227–241.
D. L. Parnas, A technique for software module specification with examples,Communications ACM, 1972, 15(5), 330–336.
M. C. Pong and Y. Yang, A coding convention for modular C programs and tools for checking of modular C program interfaces.Chinese Journal of Computers, 1987, 10(10), 637–640.
S. Gibbset al., Class management for software communities.Communications ACM, 1990, 33(9), 90–103.
Author information
Authors and Affiliations
Rights and permissions
About this article
Cite this article
Man-Chi, P., Yongguang, Z., Hong, X. et al. OOMMS: A module management system based on an object-oriented model. J. of Compt. Sci. & Technol. 8, 172–181 (1993). https://doi.org/10.1007/BF02939480
Received:
Issue Date:
DOI: https://doi.org/10.1007/BF02939480