Skip to main contentCal State San Bernardino
>> [CNS] >> [Comp Sci Dept] >> [R J Botting] >> [New Bibliographic Items] >> newb0219 [Blog/News] || [Purpose] || [Notation] || [Copyright] || [Site Search] || [Bibliography Search]
Mon Feb 20 15:58:42 PST 2006

Contents


    Stepanek05

    1. G. Stepanek
    2. Software project secrets: Why Software Projects Fail
    3. APress, Berkeley, CA, 2005. CR
    4. =ADVERT AGILE EVOLUTION MANAGEMENT COSTS XP RUP PMBOK
    5. Continuous development, SWAT, Feature trade off, Triage, Subteam encapsulation, scoping study

    Charbonneau04

    1. Serge Charbonneau
    2. Software Project Management -- A Mapping between RUP and the PMBOK
    3. The Rational Edge, (14 May 2004), Online [ 4721.html ]
    4. =HOWTO MANAGEMENT RUP PMBOK
      • Quote
      • This paper compares the Rational Unified Process (RUP) with the PMI's Project Management Body of Knowledge (PMBOK) and provides a mapping between best practices in the RUP project management discipline and best practices in the PMBOK.

    BowenHinchey06

    1. Jonathan P Bowen & Michael G Hinchey
    2. Ten Commandments of Formal Methods ... Ten years later
    3. IEEE Computer Magazine V39n1(Jan 2006)pp40-48
    4. =HISTORY FORMAL Z TLA
    5. CF [BowenHinchey95a]
      ThenNow
      I. Thou shalt Choose an Appropriate Notation. More now. Hybrids.
      II. Thou shalt Formalize but not Overformalize. 3 levels: specs, Proofs, machine checked.
      III. Thou shalt Estimate Costs.
      IV. They shalt have a Formal Methods Guru On Call. Plus a domain expert early on.
      V. Thou shalt not Abandon Traditional methods.
      VI. Thou shalt Document Sufficiently. Iterative. Including why & when decided.
      VII. Thou shalt not Compromise thy QUALITY Standards. Notation & method.
      VIII. Thou shalt not be Dogmatic. Gap between analysis & specification.
      IX Thou shalt Test, Test, and Test again.
      X. Thou Shalt Reuse.

    Doernhoefer06

    1. Mark Doernhoefer
    2. Surfing the Net for Software Engineering Notes: Software Process Improvement
    3. ACM SIGSOFT Software Engineering Notes V31n1(Jan 2006)pp5-13 [ http://www.acm.org/sigsoft/SEN/ ] [ 1108768.1108783 ]
    4. =SURVEY PROCESS IMPROVEMENT CMM-I SEI SPICE PSP SWPI SEPO USNAVY SWEBOK

    Oquendo06

    1. Flavio Oquendo
    2. Formally Modeling Software Architectures with the UML 2.0 Profile for p-ADL
    3. ACM SIGSOFT Software Engineering Notes V31n1(Jan 2006)pp25-26(abstract) [ http://www.acm.org/sigsoft/SEN/ ] [ 1108768.1108773 ] (full text)

    4. =PROPOSAL PROFILE UML2.0 FORMAL ARCHITECTURE pi-ADL

    Gilb05

    1. Tom Gilb
    2. Competitive Engineering
    3. Elsevier 2005 ISBN 0-7506-6507-6
    4. =UNREAD HANDBOOK EXPERIENCES REQUIREMENTS SPECIFICATION
    5. Reviewed (wonderful contribution) in
    6. ACM SIGSOFT Software Engineering Notes V31n1(Jan 2006)p28
    7. by Larry Bernstein

End