Maria H Penedo
ABSTRACT
Software Engineering Environments (SEE) have been determined as good means of increasing software productivity by shifting projects from the paper world into the automated world. An environment database has been identified as the core of any automated Software Engineering Environment. It should provide the means for accessing, storing and relating all the project's products, the means for automating the process by which these components are entered in this library, modified, controlled and disseminated, and the means for supporting “active databases1”. The inherent complexity of building such a database is widely recognized.
We have been studying issues associated with such an environment database, which we denote Project Master Data Base (PMDB), with the overall objective of defining, designing and developing a PMDB as an integrated part of a SEE. Due to the lack of explicit requirements for its design, a prototype of the PMDB was developed in order to gain information and experience on both the specifications of the PMDB itself and also on different implementation approaches. This paper discusses our prototyping exercise; it describes the prototype, how the problem reporting, evaluation, and tracking process was modeled, and some of the lessons learned as a result of this effort.
- 1.Buxton, J., Requirements for Ada Programming Support Environments: Stoneman, U.S. Department of Defense, OSD/R&D, Washington, D.C., February 1980.Google Scholar
- 2.Wasserman, A.I., Tutorial: Software Development Environments, IEEE Computer Society, IEEE Cat. No. EHO 187-5, 1981.Google Scholar
- 3.(STARS) The Software Technology for Adaptable, Reliable Systems Program Strategy, Department of Defense, April 1983.Google Scholar
- 4.Santoni, P.A. (now P.A. Oberndorf), The Project Development Data Base: The Core of an Automated Software Engineering Environment, NOSC Technical Note 932, Naval Ocean Systems Center San Diego, CA, 92152.Google Scholar
- 5.Penedo, M.H., and E.D. Stuckle, PMDB - A Project Marter Database for Software Engineering Environments, Proceedings of the 8th International Conference on Software Engineering, London, England, August 1985. Google ScholarDigital Library
- 6.Oberndorf P.A. and M.H. Penedo, Environment Databases - Working Croup Report, Proceedings of the Future Ada Environment Workshop, Software Engineering Notes, April 1985.Google Scholar
- 7.Requirements for Software Engineering Databases - Final Report, Imperial Software Technology Ltd and Imperial College DoC, England, CSELT SpA, Italy, and Logica SA/NV, Belgium, June 1983.Google Scholar
- 8.Boehm, B.W. et al, A Software Development Environment for Improving Productivity, Computer Magazine, pp. 30-44, June 1984.Google Scholar
- 9.Ritar I., M.H. Penedo and E.D. Stuckle, "Lessons Learned in building the TRW Software Productivity Systern", Proceedings of Spring Compcon, San Francisco, Feb 85.Google Scholar
- 10.Chen P. P., "The Entity Relationship Model: towards a unified view of data", ACM Transactiona on Datobasc Sgstems, l,l, March 1976. Google ScholarDigital Library
- 11.Penedo, M.H., and S. Wartik, "Reusable Tools for Software Engineering Environments", Proceedings of the ArAA Computers in Aerospace Conference, Long Beach, CA, Ott 1985.Google ScholarCross Ref
- 12.Morgenstern, M., "Active Databases as a Paradigm for Enhanced Computing Environments", Proceedings of the 9th International Very Large Data Base Conference, Florence, Italy, October 1983. Google ScholarDigital Library
- 13.Balzer, R., N. Goldman, and B. Neches, "Specilication- Based Computing Environments for Information Management", Proceedings of the Computer Data Engineering Conference, April 1984. Google ScholarDigital Library
- 14.Bit L., and J. Gilbert, " Learning from AI: New Trends in Database Technology", Computer, March 1986. Google ScholarDigital Library
- 15.Knuth, D. E., The QXbook, Addison-Wesley, 1984.Google Scholar
- 16.Wartik, S., and M. H. Penedo, "Fillin: A Reusable Tool supporting Form Oriented Software Development", IEEE Software, pp. 61-69, March 1986.Google Scholar
- 17.Boehm, B., Software Engineering Economics, Prentice Hall, Inc., Englewood Cliffs, NJ, 1981. Google ScholarDigital Library
- 18.Higgs, M. J., and P. Stevens, "Developing an Environment, Manager for an IPSE", GEC Software, 1986.Google Scholar
Index Terms
- Prototyping a project master database for software engineering environments
Recommendations
Prototyping a project master database for software engineering environments
Software Engineering Environments (SEE) have been determined as good means of increasing software productivity by shifting projects from the paper world into the automated world. An environment database has been identified as the core of any automated ...
PMDB—a project master database for software engineering environments
ICSE '85: Proceedings of the 8th international conference on Software engineeringAlthough the use of Software Engineering Environments (SEE) results in increased software productivity, current SEEs are still in the infant stages and lack critical characteristics such as an integrated project database which stores all data pertinent ...
The Master of Software Engineering degree: an integrative engineering discipline
FIE '95: Proceedings of the Frontiers in Education Conference on 1995. Proceedings., 1995 vol 1. - Volume 01Software based products are an ever increasing portion of industrial output. However few engineers who produce software have had formal training in the specification, design, implementation, documentation, and maintenance of large software systems. In ...
Comments