Record ID | marc_columbia/Columbia-extract-20221130-012.mrc:61600356:3826 |
Source | marc_columbia |
Download Link | /show-records/marc_columbia/Columbia-extract-20221130-012.mrc:61600356:3826?format=raw |
LEADER: 03826cam a22003014a 4500
001 5570464
005 20221121183953.0
008 041202s2006 njua b 001 0 eng
010 $a 2004061247
020 $a0471393339 (cloth : alk. paper)
035 $a(OCoLC)ocm57209130
035 $a(NNC)5570464
035 $a5570464
040 $aDLC$cDLC$dYDX$dBAKER$dIXA$dNNC$dOrLoB-B
042 $apcc
050 00 $aQA76.9.S88$bW373 2005
082 00 $a004.2/1$222
100 1 $aWasson, Charles S.,$d1948-$0http://id.loc.gov/authorities/names/n2004018846
245 10 $aSystem analysis, design, and development :$bconcepts, principles, and practices /$cCharles S. Wasson.
260 $aHoboken, N.J. :$bWiley-Interscience,$c2006.
300 $axii, 818 pages :$billustrations ;$c26 cm
336 $atext$btxt$2rdacontent
337 $aunmediated$bn$2rdamedia
504 $aIncludes bibliographical references and index.
505 00 $g1.$tIntroduction -- $g2.$tBook organization and conventions -- $g3.$tWhat is a system? -- $g4.$tSystem attributes, properties, and characteristics -- $g5.$tSystem roles and stakeholders -- $g6.$tSystem acceptability -- $g7.$tThe system/product life cycle -- $g8.$tThe architecture of systems -- $g9.$tSystem levels of abstraction and semantics -- $g10.$tThe system of interest architecture -- $g11.$tThe operating environment architecture -- $g12.$tSystem interfaces -- $g13.$tOrganizational roles, missions, and system applications -- $g14.$tUnderstanding the problem, opportunity, and solution spaces -- $g15.$tSystem interactions with its operating environment -- $g16.$tSystem mission analysis -- $g17.$tSystem use cases and scenarios -- $g18.$tSystem operations model -- $g19.$tSystem phases, modes, and states of operation -- $g20.$tModeling system and support operations -- $g21.$tSystem operational capability derivation and allocation -- $g22.$tThe anatomy of a system capability -- $g23.$tSystem analysis synthesis -- $g24.$tThe system development workflow strategy -- $g25.$tSystem design, integration, and verification strategy -- $g26.$tThe SE process model -- $g27.$tSystem development models -- $g28.$tSystem specification practices -- $g29.$tUnderstanding specification requirements -- $g30.$tSpecification analysis -- $g31.$tSpecification development -- $g32.$tRequirements derivation, allocation, flow down, and traceability -- $g33.$tRequirements statement development -- $g34.$tOperational utility, suitability, and effectiveness -- $g35.$tSystem design to/for objectives -- $g36.$tSystem architecture development -- $g37.$tDeveloping an entity's requirements domain solution -- $g38.$tDeveloping an entity's operations domain solution -- $g39.$tDeveloping an entity's behavioral domain solution -- $g40.$tDeveloping an entity's physical domain solution -- $g41.$tComponent selection and development -- $g42.$tSystem configuration identification -- $g43.$tSystem interface analysis, design, and control -- $g44.$tHuman-system integration -- $g45.$tEngineering standards, frames of reference, and conventions -- $g46.$tSystem design and development documentation -- $g47.$tAnalytical decision support -- $g48.$tStatistical influences on system design -- $g49.$tSystem performance analysis, budgets, and safety margins -- $g50.$tSystem reliability, availability, and maintainability (RAM) -- $g51.$tSystem modeling and simulation -- $g52.$tTrade study analysis of alternatives -- $g53.$tSystem verification and validation -- $g54.$tTechnical reviews -- $g55.$tSystem integration, test, and evaluation -- $g56.$tSystem deployment -- $g57.$tSystem operations and support (O&S).
650 0 $aSystem design.$0http://id.loc.gov/authorities/subjects/sh85131736
650 0 $aSystem analysis.$0http://id.loc.gov/authorities/subjects/sh85131733
852 00 $boff,eng$hQA76.9.S88$iW373 2006