[CSUSB] >> [CNS] >> [Comp Sci] >> [R J Botting] >> [New Bib 2004] >> newb0914
[Index] || [Blog/News] || [Research] || [Teaching] || [Site Search] || [Bibliography Search] Tue Sep 14 10:53:17 PDT 2004

Contents


    CarrollL77

    1. Lewis Carroll (ed. William W Bartley III)
    2. Symbolic Logic Pts I & II
    3. Harvester Press 1977 Hassocks Sussex England
    4. =MONOGRAPH LOGIC syllogisms SORITES EXAMPLES
    5. Pt II uses something like resolution and semantic tableaux!

    ArisholmSjoberg04

    1. Erik Arisholm & Dag I J Sjoberg
    2. Evaluating the Effect of a delegate versus centralized Control Style on the maintainability of Object-Oriented Software
    3. IEEE Trans Software Engineering V30n8(Aug 2004)pp521-534
    4. =EXPERIMENT EVOLUTION MAINTENANCE Object-Oriented MODULES Expert REALITY vs novice Java SESE RDD Responsibility GLM ANOVA
    5. Comparison of the correctness and effort for maintaining two OO designs for the Coffee-Machine problem from OOPSLA'97 OO. Compared consultants(3 levels: junior, intermediate, senior) and Students(Ugrad vs Grad).
    6. Two designs: one centralizes most of the responsibilities into a FrontPanel object. The decentralized design models ideas like product, ingredient, recipe and spreads the functionality over 12 modules.
    7. Overall correctness on 4 tasks: 59%, correctness increases with expertise, centralized(69%) done correctly more often than decentralized(50%)!
    8. Effort drops with expertise for students, but for consultants the effort on decentralized design drops with expertise and increases for the centralized.

    MoriPaternoSantoro04

    1. Giulio Mori & Fabir Paterno & Carmen Santoro
    2. Design and development of Multi-device user interfaces through multiple logical descriptions
    3. IEEE Trans Software Engineering V30n8(Aug 2004)pp507-520
    4. =EXPERIMENT TOOL THEORY MODEL USER PLATFORM TASKS NOMADIC TERESA XML UML
    5. TERESA::="Transformation Environment for interActivE Systems representAtions".
    6. ConcurTaskTrees::XML_DTD=models a task as a tree of subtasks.
    7. CTT::=ConcuTaskTrees.
    8. Theory and tool easily learned.
    9. Enable rapid prototyping, but slower redesign.
    10. Notes

    ArisholmBriandFoyen04

    1. Erik Arisholm & Lionel C Briand & Auden Fvyen
    2. Dynamic Coupling Measurement for Object-Oriented Software
    3. IEEE Trans Software Engineering V30n8(Aug 2004)pp491-506
    4. =CASESTUDY DYNAMIC RUNTIME Java COUPLING METRICS TOOL JDissect
    5. Notes interaction of inheritance and message passing: the object-level coupling is determined at runtime but class-level is static (and different).
    6. Figure 2, p494 is UML Metamodel of classes, methods, objects, etc..
    7. Studied Velocity open source in Apache Jakarta Project. 17 versions 408 classes, 17KLOC, 65 inheritance relation, 149 methods overridden.
    8. Average dynamic import and export couplings are always equal.
    9. Principle components confirm that dynamic coupling is not correlated with static metrics.
    10. Regression of change proneness on SLOC and each proposed metric.
    11. |-the dynamic export coupling metrics predict change proneness.
    12. Similar to work done on Smalltalk.
    13. Export coupling occurs when one method is called by another one.
    14. Changes come from calls

    ThimblebyGow04

    1. Harold Thimbleby & Jeremy Gow
    2. Computer Algebra in User Interface design research
    3. Proc 9th Int'l Conf on Intelligent user interface (Jan 2004) ACM Press NY NY 2004, pp366-367
    4. =DEMO FSM SPECIFICATION MATRIX MATHEMATICS MODEL USER INTERFACE MAUI
    5. Notes

    Fowler03e

    1. Martin Fowler
    2. UML Distilled: A brief Guide to the standard object modeling language
    3. Addison-Wesley Longman, Boston MA 2003 ISBN 0321193687 CR 0408-0893
    4. =REFERENCE UML2.0
    5. Second edition updated to UML 2.0, Previous edn by Fowler and Scott.

    ApvrilleEtal04

    1. Ludovic Apvrille & Jean-PIere Courtat & Christophe Lohr & Pierre de Saqui-Sannes
    2. TURTLE: A Real-Time UML Profile Supported by a Formal Validation Tool
    3. IEEE Trans Software Engineering V30n7(Jul 2004)pp473-487
    4. =TYPE REALTIME MODEL V&V UML1.5 PROFILE TCLASSES TTOOL RT-LOTOS RTL
    5. Notes

    GlasserGurevichVeanes04

    1. Uwe Glasser & Yuri Gurevich & Margus Veanes
    2. Abstract Communication Model fro Distributed Systems
    3. IEEE Trans Software Engineering V30n7(Jul 2004)pp458-472
    4. =THEORY COMMUNICATION MicroSoft Plug-and-Play UPnP XLANG AsmL
    5. AsmL::="Microsoft's abstract state machine language", compiles into .NET.
    6. ASM::="Abstract State Machine".
    7. Describes AsmL. Nondeterminstic Object-Oriented nonsequential language.
    8. Uses AsmL to define an Abstract Communication Model that generalizes UPnP XLANG (XML business processes), Model-Based testing and analysis etc.

    KangCheng04

    1. Jeong A Kang & Albert Mo Kim Cheng
    2. Shortening Matching Timne in OPS5 Production Systems
    3. IEEE Trans Software Engineering V30n7(Jul 2004)pp448-457
    4. =EXPERIMENT RULE PERFORMANCE TIME QUALITIES OPS5 RETE
    5. Compares speed of original and two improved algorithms for extracting rules from a rule base.

    EshuisWieringa04

    1. Rik Eshuis & Roel Wieringa
    2. Tool Support for Verifying UML Activity Diagrams
    3. IEEE Trans Software Engineering V30n7(Jul 2004)pp437-447
    4. =DEMO TOOL MODEL CHECKING FAIRNESS WORKFLOW WFMS UML TCM CTS NuSMV LTL

    El-FakihYevtushenkoBochmann04

    1. Khaled El-Fakih & Nina Yevtushenko & Grego v Bochmann
    2. FSM-Based Incremental Conformance Testing Methods
    3. IEEE Trans Software Engineering V30n7(Jul 2004)pp425-436
    4. =THEORY =EXPERIMENT FSM/STD SPECIFICATION EVOLUTION TEST

    Glass04b

    1. Robert Glass
    2. The Mystery of Formal Methods Disuse
    3. Commun ACM V47n8(Aug 2004)pp15-17
    4. =POLEMIC FORMAL METHODS
    5. Criticizes [Wordsworth99] for threatening to sneak formal methods into practice.
    6. Agrees that formal methods are not taught or taken seriously.
    7. Suggests that customers don't want "vague" requirements so much as have a need to keep them flexible to cover "problem evolution".


Formulae and Definitions in Alphabetical Order