Systems engineering is the application of the systems theory, systems science and systems thinking, in the real world.
This is not aboutEdit
Informatics, Computer Science.
- The above requires clarification. Any meaningful analysis of complex modern high tech systems or projects involving large data sets will of necessity be heavily influenced by both computer science and informatics. Perhaps what is meant is that Systems Engineering focuses on practical results of those fields rather than the leading theoretical edge. Lazyquasar 16:06, 16 December 2005 (UTC)
Where to startEdit
In this place we would like to think and develop collaboratively new ideas, concepts and tools related to the learning process of an emerging field: Systems Engineering.
(Maybe for the next edit will be a good idea to start a Glossary with links to the Wikipedia).
- Systems Engineering is not an emerging field. It has been taught in U.S. universities for decades and used by the U.S. military industrial complex since and during World War II. Lazyquasar 16:06, 16 December 2005 (UTC)
- System engineering is cross-disciplinary in nature; a system can be biological, chemical, electrical, mechanical or even mathematical. But what characterizes a "system" is the existence of a set of discoverable processes - events and relationships- and a common methodology for analyzing and influencing these processes within the scope of general scientific and engineering principles.
- (Regretfully, Microsoft recently "corrupted" the meaning of "system engineer" to mean someone who configures and manages the Microsoft suite of server operating system tools - otherwise called a system administrator. Emphatically, a system administrator is not a system engineer.)
Competencies to developEdit
- To understand and to apply concepts
- To define systems
- To model systems
- To be able to predict behavior of systems LuMorehead 15:27, 22 September 2009 (UTC)
Dean: Arturo Tovar.
- Lazyquasar 16:06, 16 December 2005 (UTC)