209.
Эммерих В. Конструирование распределенных объектов. Методы и средства
программирования интероперабельных объектов в архитектурах OMG/CORBA, Microsoft/
COM и Java/RMI. – М.: Мир, 2002. – 510 с.
210.
Beech D. Modularity of computer languages // Software – practice and experience.– 1982.–12, №
10.–P. 929–958.
211.
Beynon-Davies P. Software Engineering and Knowledge Engineering: Unhappy Bedfellows //
Polytechn. of Wales.– Pontypridd. UK.– 1987.– 3, PT. 4.–P. 9–11.
212.
Bril R. J. Safe Use of Partial Operations // Informatie (Netherlands), Philips, Eindhoven,
Netherlands.– 1987.– 29, № 7/8.–P. 700–703, 706-709.
213.
Burstall R., Lampson B. Kernel language for Abstract Data Types and Modules // Lecture Notes in
Comput. Sci.– 1984.– 173. – P. 1–50.
214.
Campbell F. The portable UCSD p. system // Microprocess and Microsyst– 1983.–7, № 8.–P. 394–
398.
215.
Chen P.P. The entity relationship model: toward a unified view of data // ACM Trans. Database
System.– 1976.– P. 9–36.
216.
Chiang J.C. Software in the Large // Afips Conf. Proc. Vol. 56. Nation. Comput. Conf. (Chicago. IL.
USA, June 15–18 1987).–Chicago, 1987.– P. 473–490.
217.
Consel C. From a program family to a domain-specific language // Symposium on Principles of
Programming Languages, Charleston, SC, USA, ACM Press, 1993.– P 19–29.
218.
Danahue P. On the semantics of data types // SIAM J. Comput.– 1979.– 8, N 4.– P. 546–560.
219.
Goel A.L. Software reliability models: assumptions limitations and applicability // IEEE Trans.
Software Engrg.–1985.–Vol. SE, № 11/12.–P. 23—45.
220.
Harders N. Software Engineering as a Methodology // Electronic (West Germany).–1987.–36, №
21.–P. 160–163.
221.
Horowitz E., Munson B. An Expensive View of reusable Software // IEEE Trans. Software,–1984.–2,
№ 5.—P. 477—487.
222.
http://www.acm.org/education/curricula.html та http://computer.org/curriculum.
223.
http://www.cwi.nl/ftp/CWIreports/SEN/SEN-E0309.pdf
224.
ISO/IEC 12207: 2002.– Information technology – Software life cycle processes) Информационные
технологии – Процессы жизненного цикла программного обеспечения.
225.
ISO/IEC 9126–2. Infofmation Technology. - Software Quality Characteristics and metrics. – 1997.
226.
Jacobson I. Object-oriented Software Engineering. A use case Driven Approach, Revised Printing.–
New York: Addison Wesley, Publ. Co.– 1994.– 529c.
227.
Jacobson I., Griss M., Johnson P. Software Reuse: Architecture, Process and organization for
Business Success – Addison Wesley, Reading , MA, May 1997.– 501 p.
228.
Johnsson R.K., Wick J.D. An Overview of the MESA Processor Architecture // Computer
Architecture News.–1982.–№ 2. –P. 20-29.
229.
Jones C. A short history of Function Points and Feature Points // Cambridge, Massachusetts:
Software Productivity Research, Inc.– 1988.– 45 p.
230.
Lubars M.D., Harandi M.J. Intelligent support for software application and design // IEEE expert.–
1986.–№ 4.–P. 33–41.
231.
Macleish K.S., Vennergrund D.A. An expert system development life cycle model and its relevance to
traditional software systems // 5 Ann. Int. Phoenix. Conf. Comput. And Comm. (Scottsdale, Ariz.
March 26—28 1986: Conf. Proc.)—Washington (D. C), 1986,—P. 592—596.
232.
McCabe J.L. A complexity measure // IEEE Trans. Software Engrg.– 1976. 2, № 4.–P. 308–320.
233.
Mclauchlan M.R. Specification of VLSI Designs: A Software Engineering Approach // IEE
Colloquium on'VLSI System Design: Specification and Synthesis' (London, UK, Oct. 29 1987).–
London, IEE, 1987.–P. 32.
234.
Mernik M., Heering J., Sloane A: When and how to develop domain-specific languages. Technical
Report SEN-E0309, CWI, Amsterdam, 2003, Available from
235.
Misra P.N. Software reliability analysis // IBM systems.– 1983.–22, № 9.–P. 262–270.
236.
Model Driven Development and Software Product Lines. BigLever Software Inc. – 2007.
http://www.biglever.com/technotes/mdd_spl.html?source=mdd
237.
Mohanty S.N. Software cost Estimation: Present and Future, P. E. 1981.–l. –p. 27—31.
238.
Moranda P.B. Predictions of software reliability during debugging // Proc. Reliability and Maint
Symp. (Washington, June 1975).–Washington (D.C.).1975. –327—332.
239.
Muller K. Fundamental Principle of Software Engineering: The Phases Model // Electronic
(West Germany).–1987.–36, № 21.–P. 169–172.