plexity demandsthat the so

neerslearn the samelessons

engineerslearned, but from a
perspective. Mathematicians
atepreciseboundariesarounda
and make it as neat as
can solve it. However. systems
don't usuallyexpecta piecise<
they a
IemsbfGlecring from a serof
1970Seminal
papers
onstructured
analvsis basedon trade-offs(equally
andviewpoint
analysis,
Unix,Arpanet
and management-oriented)
1957Firstsystems
engineering
textboo[Sputnik
project life cycle. On the
1955RAND
Systems Development
Division
the system engineeringdisci
methods that engineershave
1945ColdWarbegins
the yearsto reinforcea -.st
proach. These come from an
1937BrilishAirDefense
Systems
based on requirements
and allocation.I7hile rcqu
basedon strategicneedand
Figure l. $ystems enginceringand soltware engineeringhistory.
the functional allocation is ba
torical precedenceand is
learning." From a cultural anthropology tems engineeringcommunities approach stovepipes,such as the telemetn
approach, we can examine some funda- the requirements discipline. These ele- nent, radar, and so forth.
mental beliefs and assumptions,shared mentswork togetherto form cultural fil- composition approach, s
values,behavioralpatterns (or customs). ters that predisposeour problem-solving neers regard solfware as a
behavioral norms, and artifacts to gain approach(seeThble1). rather than a complex svsrem
insight into how the .software and sys- So, we can see that sofrware's com- and intertwined much like

$oltwareengineeringcultureuercussystemsengineeringculture
Softwarc
engineering Systems
engineering
be'iefsandI Engineers canreduce problems orproblem I Formalisms
help,butcommunication
ismost
::ijffi:fl solutions to a setofformalisms. I Collect,
mix,andmatch methods
andtechniques
I Precisely specifyingandapplying methods theminyourtoolkit.
Apply
asappropriate;
none
willproduce equal resultsregardlessofthe guarantees.
people involved. I Thesoftware
isa system
component.
I Thesoftware isthesystem.
I Developing formalisms fora problem oi (inctuding
domain isthemostimportant stepinsolving nonnegotiables)
andtheirinterpersonal
dynamics
theproblem. mostimportant.
patterns
Behavioral (orcustoms) I Precisely stateorformalize theproblem Developa fullunderstandrnf
ofalro$ictive
even jf it requires narrowing thescope. operational
aspects,
andusenaturallanguageto
r Model theproblem using formalisms. establish
anagreement.
I Avoid themessiness oi systems inthereal I Applya of managementandengineerrng
wodd, suchasdeployment, aging,poor toachievethedesired
outcome.
physical environments, andchaos. I Beriskaverse.
I Befaddish-sometimes cultish-about new
methods.
Artifacts r Artifacts include UMLdiagrams anduser r Artifacts
include
operationiGcenarioffi
scenarios. management documents,
suchasSEMp (systems
engineering
managementplan),
TEMp (testand
managementplan).
riskmanagement
plans,and

60 f E E E S 0 F T W A R Ew w w . c 0 n p u t e r . o r g / s 0 f t w a r e