LEADER 04069nam a2200433Ii 4500 001 991003247129707536 006 m d 007 cr cn||||||||| 008 070806s2004 ne a sb 001 0 eng d 020 $a9781555583132 020 $a155558313X 035 $ab13654901-39ule_inst 037 $a103562:103582$bElsevier Science & Technology$nhttp://www.sciencedirect.com 040 $aOPELS$cOPELS 049 $aTEFA 082 04$a005.1/068$222 100 1 $aRittinghouse, John W.$0627521 245 10$aManaging software deliverables$h[electronic resource] :$ba software development management methodology /$cby John W. Rittinghouse. 260 $aAmsterdam :$bElsevier ;$aBoston :$bDigital Press,$cc2004. 300 $axxxiii, 315 p. :$bill. ;$c23 cm. 504 $aIncludes bibliographical references and index. 505 0 $aForeword by Dr. Bill Hancock; Introduction to the Systems Engineering Process (SEP); Understanding Software Program Management O (SPMO); SEP Phases: Initiation; Analysis and Detailed Planning; Detailed Design; Construction; Testing; Implementation; Support; Project Closeout; Choosing a Development Strategy; Putting It All Together; Appendices: Roadmaps; Answers to Chapter Review Questions. 505 0 $aUnderstanding the SPMO -- SEP phase I : initiation -- SEP phase II : analysis and detailed planning phase -- SEP phase III : detailed design phase -- SEP phase IV : construction phase -- SEP phase V : testing -- SEP phase VI : implementation -- SEP phase VII : support phase -- SEP phase VIII : project closeout -- Project wizardry 101 -- Some software best practices to consider -- Putting it all together. 520 $aManaging Software Development describes a set of proven processes for establishing an effective Software Program Management Office (SPMO) function in a corporate setting. Every business that has people performing Software Project Management (PM) activities has a need for these processes. In some instances, an organization may already have a PMO chartered with overall responsibility for each project managed in an enterprise. In those cases, this book will either provide validation of their efforts or it will provide some techniques and useful approaches that can be utilized to further improve on their overall implementation of the PMO. In the vast majority of cases in business, however, a PMO is unheard of. Each project managed in the enterprise is unfortunately managed separately from all others (at great cost in both time and money to the enterprise). The book provides a downloadable "drop-in" web site containing every type of template needed to perform the activities described here. *Phase Roadmaps clearly depict what is expected by all parties at each phase of effort *Pre-built Intranet is ready to deploy in a corporate setting and provides immediate use *Process Methodology adheres to proven best-practices for software development. 533 $aElectronic reproduction.$bAmsterdam :$cElsevier Science & Technology,$d2007.$nMode of access: World Wide Web.$nSystem requirements: Web browser.$nTitle from title screen (viewed on Aug. 2, 2007).$nAccess may be restricted to users at subscribing institutions. 650 0$aComputer software$xDevelopment$xManagement. 650 0$aComputer programming$xManagement. 650 0$aProject management. 655 7$aElectronic books.$2local 776 1 $cOriginal$z155558313X$z9781555583132$w(DLC) 2003062587$w(OCoLC)53059466 856 40$3Referex$uhttp://www.sciencedirect.com/science/book/9781555583132$zAn electronic book accessible through the World Wide Web; click for information 856 42$zPublisher description$uhttp://catdir.loc.gov/catdir/description/els041/2003062587.html 856 41$zTable of contents$uhttp://www.loc.gov/catdir/toc/els041/2003062587.html 907 $a.b13654901$b24-02-22$c24-01-08 912 $a991003247129707536 994 $aC0$bTEF 996 $aManaging software deliverables$91212825 997 $aUNISALENTO 998 $ale029$b24-01-08$cm$dm $e-$feng$gne $h0$i0