Skip to main contentCal State San Bernardino
>> [CNS] >> [Comp Sci Dept] >> [R J Botting] >> [New Bibliographic Items] >> newb0912 [Blog/News] || [Purpose] || [Notation] || [Copyright] || [Site Search] || [Bibliography Search]
Mon Sep 12 12:15:43 PDT 2005

Contents


    MeservyFenstermacher05

    1. Thomas O Meservy & Kurt D Fenstermacher
    2. Transforming software development: the MDA Road map
    3. IEEE Computer Magazine V38n9(Sep 2005)pp-58
    4. =ADVERT MODELLING MDA CIM PIM PSM OptimalJ EJB IBM Rose
    5. Defines of terms.
    6. Uses maps as analogies and gives an incomplete demo.
    7. Assumes that MDA starts with Computation Independent work-flow models -- activity diagrams.
    8. Also see alternate views [Thomas04] [CaplatSourrouille05] [ArlowNeustadt03]

    JanzenSaiedian05

    1. David Janzen & Hossein Saiedian
    2. Test-Driven Development: Concepts,Taxonomy, and future directions.
    3. IEEE Computer Magazine V38n9(Sep 2005)pp43-50
    4. =SURVEY TEST-DRIVEN PROCESS TDD XP SCRUM AGILE EDUCATION
    5. Well written survey of history and literature on test-driven development.
    6. Predicts that TDD will not go away.
    7. Refs [Beck01] [Reifer02] [ErdogmasMorisioTorchiano05]

    FairleyWilshire05

    1. Richard E (Dick) Fairley & Mary Jane Wilshire
    2. Iterative Rework: The Good, the Bad, and the Ugly
    3. IEEE Computer Magazine V38n9(Sep 2005)pp34-41
    4. =ESSAY PROCESS STATISTICS QUALITY CONTROL CHARTS REWORK EVOLUTION ITERATION REFACTORING REWORK AGILE ITERATIVE
    5. Too much (>20%) or too little rework(<10%) means something is wrong. So track % rework on a statistical control chart (Shewart 1920s) with upper and lower control levels. Trends, spikes, and random walks over the same limit trigger root cause analysis and improvement.
    6. All types of rework can be good, bad, or ugly!
    7. Rework= Evolutionary_rework | Avoidable_rework.
    8. Evolutionary_rework::=response to changing world.
    9. Avoidable_rework::=Retrospective_rework | Corrective rework.
    10. Retrospective_rework::= work that could have been before.
    11. Corrective rework::= work the fixes defects in current or previous versions.
    12. Distinctions are not very objective but good enough to suggest process improvements.

    Lawton05

    1. George Lawton
    2. LAMP Lights Enterprise Development Efforts
    3. IEEE Computer Magazine V38n9(Sep 2005)pp18-20
    4. =ESSAY MicroSoft vs Sun Java vs Open Source
    5. LAMP::=Platform(OS=Linux, Web_server=Apache, database=MySQL, scripting={Perl, PHP, Python})

    Shumba05

    1. Rose Shumba
    2. Usability of Rational Rose and Visio in a software engineering course
    3. ACM SIGCSE Bulletin V37n2(Jun 2005)pp107-110
    4. =POLL 173 STUDENTS UML GRAPHIC CASE TOOLS Visio Rose USER
    5. Visio is good for documents & Rose good for producing software.

    MatosGrasser05

    1. Victor Matos & Becky Grasser
    2. SQL-based Discovery of exact and approximate functional dependencies
    3. ACM SIGCSE Bulletin V36n4(Dec 2004)pp58-63
    4. =DEMO SQL MATH

    SmithMooresChang05

    1. Deborah K Smith & Trevor Moores & Jerry Chang
    2. Prepare your mind for learning
    3. Commun ACM V48n9(Sep 2005)pp115-
    4. =IDEA IGNORANCE
    5. cultivate a beginners mind
    6. question your knowledge
    7. seek criticism
    8. review the work of others
    9. teach
    10. relish the plateau between growth spurts

    WoodOw05

    1. Charles A Wood & Terence T Ow
    2. WEBVIEW: an SQL extension for joining corporate data to data derived from the web
    3. Commun ACM V48n9(Sep 2005)pp99-104
    4. =ADVERT SQL WWW DATA LANGUAGE KM

    ShahKesan05

    1. Rajiv C Shah & Jay P Kesan
    2. Nurturing Software
    3. Commun ACM V48n9(Sep 2005)pp80-85
    4. =CASE STUDY university NCSA Mosaic firm Netscape cookies consortia PICS open source APACHE ONE SIZE CULTURE
    5. |-Institutional culture shapes attributes of software.

End