Skip to main contentCal State San Bernardino
>> [CNS] >> [Comp Sci Dept] >> [R J Botting] >> [New Bibliographic Items] >> newb0121 [Blog/News] || [Purpose] || [Notation] || [Copyright] || [Site Search] || [Bibliography Search]
Fri Jan 21 17:12:22 PST 2005

Contents


    Bibliographic Changes January 2005

      Add V21n6(Nov /Dec 2004)pp9-11 to [KambayashLedgard04]

      Add V21n6(Nov /Dec 2004)p9 to [Harrison04]

      Add CR 0501-0049 to [Reifer03]

      Jaksic04

      1. Mirjana Jaksic
      2. Mapping of bibliographical standards into XML
      3. Software: Practice and Experience V34n11(Sep 2004)pp1051-1064
      4. =HOWTO XML BIBLIOGRAPHY MARC UNIMARC Java

      EgyedGrunbacher04

      1. Alexander Egyed & Paul Grunbacher
      2. Identifying Requirements Conflicts and Cooperation: How Quality Attributes and Automated Traceability can help
      3. IEEE Software Magazine V21n6(Nov /Dec 2004)pp50-58
      4. =THEORY AUTOMATED REQUIREMENTS TRADE-OFFS PURPOSES QUALITIES DEMO VOD Video-on-demand
      5. Express all requirements as tests and run them tracing which ones execute the overlapping pieces of code.
      6. Classify requirements in terms of type.
      7. Types indicate likely cooperation and conflict in a semantic web.
      8. Hence able to express trade-off situations.

      OrtinEtal04

      1. Francisco Ortin & Benjamin Lopez &J Baltasar Garcia Perez-Schofield
      2. Separating Adaptable Persistence Attributes through computational Reflection
      3. IEEE Software Magazine V21n6(Nov /Dec 2004)pp41-49
      4. =DEMO TOOL SEPARATE PERSISTENCE DATA vs BUSINESS LOGIC Nitr0 Java REFLECTION
      5. Notes

      YilmazEtal04

      1. Cemal Yilmaz & Atif Memon & Adam A Porter & Arvind S Krishna & Douglas S Schmidt & Aniruddha Gokhale & Balachandran Natarajan
      2. Preserving Distributed System's Critical Properties: A Model-Driven Approach
      3. IEEE Software Magazine V21n6(Nov /Dec 2004)pp32-40
      4. =EXPERIMENT MODEL PERSISTENT QUALITIES SQA TOOL QoS PSA ACE+TAO Boeing Bold Stroke
      5. A semi-automatic tool (Skoll DCQA) running on a many CPUs found bugs in complex systems by searching out bad combinations of parameters that made tests fail.

      SerranoCalzadaAlonsoCiordia04

      1. Nicolas Serrano & Sonia Calzada & Fernando Alonso & Ismael Ciordia
      2. Automated Management of Multicustomer Code Basis
      3. IEEE Software Magazine V21n6(Nov /Dec 2004)pp26-31
      4. =EXPERIENCE TOOL MODEL DATA CODE SQLC MVC XML Java Ant Web/Net EVOLUTION VERSION

      BasiliDonzelliAsgari04

      1. Victor Basili & Paolo Donzelli &Sima Asgari
      2. A Unified Model of Dependability: Capturing Dependability in Context
      3. IEEE Software Magazine V21n6(Nov /Dec 2004)pp19-25
      4. =CASESTUDY UMD TOOL THEORY QUALITIES DEPENDABILITY TSAFE
      5. Jargon! Students simulate stakeholders?

      Voas04

      1. Jeffrey Voas
      2. Software's Secret Sauce: the "-ilities"
      3. IEEE Software Magazine V21n6(Nov /Dec 2004)pp14-15
      4. =ADVERT QUALITIES

      Blood04

      1. Rebecca Blood
      2. How Blogging Software reshapes the online community
      3. Commun ACM V47n12(Dec 2004)pp53-55
      4. =ANECDOTE SOFTWARE BLOG
      5. Software tools change the way things are done and what words mean in powerful ways.

      MalhotraGalletta04

      1. Yogesh Malhotra and Dennis F Galletta
      2. Building Systems that Users want to use
      3. Commun ACM V47n12(Dec 2004)pp89-
      4. =EXPERIENCE =THEORY PEOPLE USERS SYSTEMS
      5. If users are not committed and/or not motivated then they tend not to use systems that provided for them.
      6. Improvement and value comes from systems being used not from the existence of the system.
      7. Two classic anecdotes: the Pillsbury intranet for sharing information that nobody used for six months. The PriceWaterhouse Coopers institutional document repository was never used when an inferior mailing list became a primary channel for communication and collaboration.
      8. Commitment: compliance..identification.. internalization.
      9. Motivation: intrinsic and extrinsic.
      10. (dick) |- ownership and involvement in development is a powerful motivator.

      Sawyer04

      1. Steve Sawyer
      2. Software Development Teams
      3. Commun ACM V47n12(Dec 2004)pp95-99
      4. =THEORY PEOPLE TEAMS
      5. Three team archetypes: sequential (production line fixed process, SDLC), group(interaction and iteration toward a product, RAD), and network(product focus with expert hubs, CPT & Open Source). Teams can also have hybrid.
      6. Gives advice on the issues(team, method, tool) and opportunities for each archetype.

      Leavitt04

      1. Neal Leavitt
      2. are web services finally ready to deliver.
      3. IEEE Computer Magazine V37n11(Nov 2004)pp14-18
      4. =ARTICLE Web/NET
      5. WS-I::= "web services interoperability organisation".
      6. OASIS::= "organisation for the advancement of structured information standards".

      Holmes04

      1. Neville Holmes
      2. The usefulness of hindsight
      3. IEEE Computer Magazine V37n11(Nov 2004)pp120+ 118-119
      4. =ANECDOTE ANALYSIS USER DATA
      5. Ref [ StrongVolkov04 ]

      Petroski04

      1. Henry Petroski
      2. Past and future failures
      3. American Scientist V92n06(Nov/Dec 2004)pp500-504
      4. =HISTORY ENGINEERING RISKS BRIDGES Y2K
      5. Each generation of bridge builders (each 30.years) has had a disaster as some unknown effect emerged in a new technology.
      6. ref to research 1977 by P G Sibly.

    . . . . . . . . . ( end of section Bibliographic Changes January 2005) <<Contents | End>>

End