검색어: software engineering project scheduling (스페인어 - 영어)

"software engineering project management".
"software engineering project management".

"a discipline for software engineering".
"a discipline for software engineering".

from ieee transactions software engineering, january 1980.
from ieee "transactions software engineering", january 1980.

"software engineering economics", prentice-hall.
"software engineering economics", prentice-hall.

in: "modern software engineering, foundations and current perspectives".
in: "modern software engineering, foundations and current perspectives".

project work: the organisation of collaborative design and development in software engineering.
project work: the organisation of collaborative design and development in software engineering.

"component-based software engineering: putting the pieces together".
"component-based software engineering: putting the pieces together".

"system design from provably correct constructs : the beginnings of true software engineering".
"system design from provably correct constructs : the beginnings of true software engineering".

parness, d. l. a course on software engineering. proc. sigcse technical symposium, mar. 1972.
parness, d. l. a course on software engineering. proc. sigcse technical symposium, mar. 1972.

), "encyclopedia of software engineering", taylor & francis, 2010, pages 308–320.
), "encyclopedia of software engineering", taylor & francis, 2010, pages 308–320.

798. en apoyo de su reclamación, engineering project proporcionó un certificado de despacho de aduanas de fecha 2 de julio de 1995.
in support of its claim, engineering projects provided a customs clearance certificate dated 2 july 1995.

" in: "aerospace software engineering", edited by christine anderson and merlin dorfman, 5–15.
" in: "aerospace software engineering", edited by christine anderson and merlin dorfman, 5–15.

humphrey era miembro de la junta directiva del software engineering institute (sei) y de la association for computing machinery (2008).
humphrey was a fellow of the software engineering institute (sei) and of the association for computing machinery (2008).

desarrollamos aplicaciones, siguiendo las metodologías de ieee y las normas internacionales expresadas en el ieee swebok (software engineering body of knowledge), compilación del estado del arte y mejores prácticas para la ingeniería del software.
we develop applications following ieee methodologies and international standards contained in the ieee swebok (software engineering body of knowledge), a compilation of the state of the art and best practices for software engineering.

797. el grupo recomienda que no se pague ninguna indemnización por la reclamación en concepto de gastos de agua, electricidad, etc., porque engineering project no ha demostrado que las pérdidas alegadas fueron una consecuencia directa de la invasión y ocupación de kuwait por el iraq.
the panel recommends no compensation for the claim for the utility expenses because engineering projects failed to establish that the alleged losses arose as a direct result of iraq's invasion and occupation of kuwait.

* brian randell: the nato software engineering conferences (the site includes the original two nato reports—from 1968 and 1969—as well as photographs of the participants and some of the sessions at garmisch)
* brian randell: the nato software engineering conferences (the site includes the original two nato reports—from 1968 and 1969—as well as photographs of the participants and some of the sessions at garmisch)

=== software engineering ===it has been argued that the structure and internal quality attributes of a working, non-trivial software artifact will represent first and foremost the engineering requirements of its construction, with the influence of process being marginal, if any.
"=== software engineering ===it has been argued that the structure and internal quality attributes of a working, non-trivial software artifact will represent first and foremost the engineering requirements of its construction, with the influence of process being marginal, if any.

), "computer science handbook", 2nd edition, section xi, "software engineering", chapter 106, pages 106-1 – 106-25, chapman & hall / crc press, association for computing machinery, 2004.
), "computer science handbook", 2nd edition, section xi, "software engineering",chapter 106, pages 106-1 – 106-25, chapman & hall / crc press, association for computing machinery, 2004.