SE
SE Glossary
SE — SE
Information on SE
SE started to emerge as a formal discipline
in the 1950s, primarily driven by the US DoD programs
of the era. These programs were failing at a worrying
rate and were characterised by: complex and challenging requirements; incomplete
and/or poor definition of these requirements; use of emerging technologies,
reliance on the integration of a number of disciplines; and
high levels of technical risk. The more successful programs managed
these challenges using early forms of what is now known
as SE.
SE provides a framework within
which complex problems can be defined and analysed and in
which solutions can be considered, specified and manufactured with a
lifecycle focus. SE therefore provides an environment in
which adequate systems can be delivered, operated and supported successfully.
Systems
engineering focuses on the system as a whole not
on individual parts of the system and relies on strong
inter-disciplinary integration and cooperation. SE also focuses on
requirements engineering, a top-down approach, and system optimisation and balance.
Other topics in our resources on SE related to SE include:
To nominate related words or phrases to be added to this glossary, please contact Argos Press. © Argos Press Pty Ltd, Canberra, 2003-2004. All rights reserved. Please contact Argos Press to obtain information on licensing Argos Press content (such as this glossary entry on SE).