Menú
Inicio
Visitar el Sitio Zona Militar
Foros
Nuevos mensajes
Buscar en los foros
Qué hay de nuevo
Nuevos mensajes
Última actividad
Miembros
Visitantes actuales
Entrar
Registrarse
Novedades
Buscar
Buscar
Buscar sólo en títulos
Por:
Nuevos mensajes
Buscar en los foros
Menú
Entrar
Registrarse
Inicio
Foros
Fuerzas Aéreas
Tecnologías, Tácticas y Sistemas Aereos
Todo sobre el Su-57 PAK-FA / Felon
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
Estás usando un navegador obsoleto. No se pueden mostrar estos u otros sitios web correctamente.
Se debe actualizar o usar un
navegador alternativo
.
Responder al tema
Mensaje
<blockquote data-quote="Rumplestilskin" data-source="post: 602735" data-attributes="member: 229"><p>Como acotación al margen, cito las palabras de un ingeniero en software estadounidense. Venían hablando sobre el desarrollo de una nueva versión del tanque indio Arjun; él se mofa en vista de los antecedentes con el primer modelo; alguien le contesta que hacer un tanque no es ingeniería de cohetes, y responde: </p><p></p><p><em>"Building a tank requires engineering, and thus requires good engineering methodology -- a systematic approach, incorporating complexity management, an eye towards externally-imposed constraints, and several small design / review / implement / debug cycles.</em></p><p><em></em></p><p><em>Methodology has not been well-taught in American universities for a long time (its decline was well underway when I was in school, an age ago), and this has manifested itself in industry. Development cycles are long, engineering teams are large, and products are overly-complex (and thus failure-prone). Matters of methodology are falling increasingly on the shoulders of management, who by and large are not engineers and don't understand the technical side of the projects they're expected to manage. Most managers learned business methodology in school, and business methodology is a poor substitute for engineering methodology.</em></p><p><em></em></p><p><em>I don't know if the same is true in India, but from what I have seen the Arjun project has the hallmarks of being plagued by engineering methodology problems. The project's phases were too few and too large. The team was tasked with designing too many systems (with subsequent growth of the team -- qv _The Mythical Man-Month_ for the rationale for smaller engineering teams). The design (particularly of the automotive components) failed to take into account practical constraints such as the state of the art of the Indian manufacturing industry.</em></p><p><em></em></p><p><em>Contrast this with Pakistan's engineering effort behind the Al-Khalid: It consisted of several small design cycles (each terminating with an incrementally more functional system which could be tested in the field). It relied on existing technology (primarily Chinese) as the basis for most of its systems. Where native production was not feasible, components were purchased from other countries (engines from Ukraine, for instance). Thus was Pakistan able to field a superior product in less time than its wealthier and better-industrialized rival.</em></p><p><em></em></p><p><em>Engineering methodology is one of the least glamorous and most neglected disciplines within the engineering profession, but it can make the difference between success and failure of seemingly simple technical projects.</em></p><p><em></em></p><p><em>(As an aside: Californian engineers tend to be a very mixed bag, in their national roots -- American, Korean, French, German, Japanese, etc. <u>Of all the engineers I've worked with, those who exhibited the best engineering methodology were educated in Russia. </u>I don't know what they're doing right over there, but someone should go find out.)"</em></p><p></p><p><a href="http://208.84.116.223/forums/index.php?showtopic=32346&st=20">India to design and manufacture entirely new MBT - Tanknet - Page 2</a></p><p></p><p>Ciertamente no resuelve la estrechez de recursos por completo, pero en vista de los resultados, y no de ahora, si no de los últimos 70 años, se ve que ayuda.</p></blockquote><p></p>
[QUOTE="Rumplestilskin, post: 602735, member: 229"] Como acotación al margen, cito las palabras de un ingeniero en software estadounidense. Venían hablando sobre el desarrollo de una nueva versión del tanque indio Arjun; él se mofa en vista de los antecedentes con el primer modelo; alguien le contesta que hacer un tanque no es ingeniería de cohetes, y responde: [I]"Building a tank requires engineering, and thus requires good engineering methodology -- a systematic approach, incorporating complexity management, an eye towards externally-imposed constraints, and several small design / review / implement / debug cycles. Methodology has not been well-taught in American universities for a long time (its decline was well underway when I was in school, an age ago), and this has manifested itself in industry. Development cycles are long, engineering teams are large, and products are overly-complex (and thus failure-prone). Matters of methodology are falling increasingly on the shoulders of management, who by and large are not engineers and don't understand the technical side of the projects they're expected to manage. Most managers learned business methodology in school, and business methodology is a poor substitute for engineering methodology. I don't know if the same is true in India, but from what I have seen the Arjun project has the hallmarks of being plagued by engineering methodology problems. The project's phases were too few and too large. The team was tasked with designing too many systems (with subsequent growth of the team -- qv _The Mythical Man-Month_ for the rationale for smaller engineering teams). The design (particularly of the automotive components) failed to take into account practical constraints such as the state of the art of the Indian manufacturing industry. Contrast this with Pakistan's engineering effort behind the Al-Khalid: It consisted of several small design cycles (each terminating with an incrementally more functional system which could be tested in the field). It relied on existing technology (primarily Chinese) as the basis for most of its systems. Where native production was not feasible, components were purchased from other countries (engines from Ukraine, for instance). Thus was Pakistan able to field a superior product in less time than its wealthier and better-industrialized rival. Engineering methodology is one of the least glamorous and most neglected disciplines within the engineering profession, but it can make the difference between success and failure of seemingly simple technical projects. (As an aside: Californian engineers tend to be a very mixed bag, in their national roots -- American, Korean, French, German, Japanese, etc. [U]Of all the engineers I've worked with, those who exhibited the best engineering methodology were educated in Russia. [/U]I don't know what they're doing right over there, but someone should go find out.)"[/I] [url=http://208.84.116.223/forums/index.php?showtopic=32346&st=20]India to design and manufacture entirely new MBT - Tanknet - Page 2[/url] Ciertamente no resuelve la estrechez de recursos por completo, pero en vista de los resultados, y no de ahora, si no de los últimos 70 años, se ve que ayuda. [/QUOTE]
Insertar citas…
Verificación
¿Cuanto es 2 mas 6? (en letras)
Responder
Inicio
Foros
Fuerzas Aéreas
Tecnologías, Tácticas y Sistemas Aereos
Todo sobre el Su-57 PAK-FA / Felon
Este sitio usa cookies. Para continuar usando este sitio, se debe aceptar nuestro uso de cookies.
Aceptar
Más información.…
Arriba