Skip to main contentCal State San Bernardino
>> [CNS] >> [Comp Sci Dept] >> [R J Botting] >> [New Bibliographic Items] >> newb0330 [Blog/News] || [Purpose] || [Notation] || [Copyright] || [Site Search] || [Bibliography Search]
Fri Apr 1 15:08:17 PST 2005

Contents


    JorgensonMolokken-Ostvold04

    1. Magne Jxrgenson & Kjetil Molxkken-Xstvold
    2. Reasons for software estimation Error: Impact of Respondent Role, information collection approach, and data analysis method
    3. IEEE Trans Software Engineering V30n12(Dec 2004)pp993-1007
    4. =EMPIRICAL INTERVIEWS SURVEYS PEOPLE ESTIMATION ERRORS
    5. People blame errors on things they don't control and take credit for things they do control.
    6. Also see .Lookup Jorgenson

    LuqiZhangBerzinsQiao04

    1. Luqi & Lin Zhang & Valdis Berzins & Ying Qiao
    2. Documentation driven development complex real-time systems
    3. IEEE Trans Software Engineering V30n12(Dec 2004)pp936-952
    4. =DEMO TOOL CAPS-PC AUTOMATE DOCUMENTATION REQUIREMENTS DESIGN CODE TIMING FSA/STD CARA AGILE STAKEHOLDERS LATTICES METRICS
    5. DDD::= "Documentation Driven Development".
    6. Central dynamic data base with automatic translation between requirements, architecture, and components plus translations and executable prototypes for stakeholders.
    7. Process management. Risk assessment. metrics: requirements volatility, organization efficiency, product complexity, technology maturity (temperature) , ...
    8. CARA blood pressure maintenance IV for army stretcher.

    Vokac04

    1. Marek Vokac
    2. Defect frequency and design patterns: an empirical study of industrial code
    3. IEEE Trans Software Engineering V30n12(Dec 2004)pp904-917
    4. =EXPERIENCE TECHNICAL PATTERNS TOOL QUALITY DEFECTS factory template singleton observer decorator class size superoffice CRM5
    5. Larger classes are changed more often.
    6. Singleton & observer are associated with complex situations that need extra effort & care.

    RobilardCoelhoMurphy04

    1. Martin P Robilard &Wesley Coelho & Gail C Murphy
    2. How Effective Developers Investigate Source Code
    3. IEEE Trans Software Engineering V30n12(Dec 2004)pp889-903
    4. =EXPERIMENT 5 PEOPLE CODE EVOLUTION MAINTENANCE Jedit Java
    5. Those who made changes well also did them quicker and used a planned and methodical search of the source code for what needed changing.
    6. Browsing and scrolling did not work as well as keyword and cross reference searching.

    EdwardsEtal04

    1. Stephen H Edwards & Murali Sitaraman & Bruce W Weide & Joseph Hollingsworth
    2. Contract-check Wrappers for C++ Classes
    3. IEEE Trans Software Engineering V30n11(Nov 2004)pp794-810
    4. =DEMO WRAPPERS CONTRACT ASSERTIONS TECHNICAL C++ V&V SQA FACTORY
    5. Instead of inline code checking assertions, can provide optional compiled wrappers that contain assertions.

    TianRudrarajuLi04

    1. Jeff Tian & Sunita Rudraraju & Zhao Li
    2. Evaluating Web Software Reliability Based on Workload and Failure Data Extracted from Server Logs
    3. IEEE Trans Software Engineering V30n11(Nov 2004)pp754-769
    4. =EXPERIENCE WEB/NET RELIABILITY WORKLOAD LOGGING DATA STATISTICS SMU/SEAS KDE
    5. Access logs provide evidence of problems in content: "permission denied" and "file does not exist".
    6. Errors consistent with a Poisson process with time varying parameters,
    7. Can measure the growth in reliability.
    8. (Goel-Okumoto model): expected_number_of_errors(time) = N*(1-exp(-b*time)) for some N and b.
    9. Similar models of work load for two different web sites: weekly cycle.
    10. Similar reliability models.
    11. What measures workload? Bytes served, hits, users, sessions?

    TraoreAredo04

    1. Issa Traore & Demissie B Aredo
    2. Enhancing Structured Review with Model-Based Verification
    3. IEEE Trans Software Engineering V30n11(Nov 2004)pp736-753
    4. =EXPERIMENT V&V SQA INSPECTION TOOL PrUDE UML OCL PVS DNF
    5. Harder to find defects when no guidelines or tool help available. 50% missed. 30.min/defect.
    6. PVS checks conjectures generated by reviewers.
    7. Checked a use case model, an analysis model, and a design model.
    8. PVS semantics for a subset of the UML.
    9. PrUDE::= "Precise UML Development Environment".
    10. Generates test data.

    CostagliolaDeufemiaPolese04

    1. Gennaro Costagliola & Vincenzo Deufemia & Giuseppe Polese
    2. A Framework for Modeling and Implementing Visual Notations with Applications to Software Engineering
    3. ACM TOSEM Trans Software Eng & Methodology V13n4(Oct 2004)pp431-487
    4. =DEMO THEORY GRAPHICS LANGUAGE GRAMMAR PARSING METACASE VLDesk XPG XpLR UML Statecharts
    5. XPG::="eXtended Positional Grammar", syntactic description of visual notations in terms of visual symbols (vsymbols), plus spatial relations generating visual sentences.
    6. Ontology of spatial relations:
      Net
      1. Relation = Connection | Geometric
      2. Plex ==>Graph==>Connection,
      3. String ==>Iconic==>Box==>Geometric.

      (End of Net)

    7. XpLR::=parsing method associated with XPG.
    8. VLDesk::tool, provides a "desk" where methodologists can develop CASE tools.

End