Skip to main contentCal State San Bernardino
>> [CNS] >> [Comp Sci Dept] >> [R J Botting] >> [New Bibliographic Items] >> newb0829 [Blog/News] || [Purpose] || [Notation] || [Copyright] || [Site Search] || [Bibliography Search]
Tue Aug 30 15:08:18 PDT 2005

Contents


    PendhakarSubramanianRodger05

    1. Parag C Pendhakar & Girish H Subramanian & James A Rodger
    2. A Probabilistic Model for Predicting Software Development Effort
    3. IEEE Trans Software Engineering V31n7(Jul 2005)pp615-624
    4. =ADVERT BAYESIAN ESTIMATION
    5. Bayesian network don't just calculate a value but a distribution.
    6. Demonstrates on a standard data set that Bayesian networks (trees) work as well as other data mining models.

    TsantalisChatzigeorgiouStephanides05

    1. Nikolaos Tsantalis & Alexander Chatzigeorgiou & George Stephanides
    2. Predicting the probability of Change in Object-Oriented Systems
    3. IEEE Trans Software Engineering V31n7(Jul 2005)pp601-614
    4. =DEMO METRICS COUPLING CHANGE OBJECTS TOOL Java
    5. Defines Axes of Change: Inheritance, Reference, Dependency, Internal...
    6. Claims these lead to better predictions than using classic metrics.
    7. Has problems with cyclic dependencies leading to matrix equations.

    MoonYeomChae05

    1. Mikyeong Moon & Keunhyuk Yeom & Heung Seol Chae
    2. An Approach to Developing Domain Requirements as a Core Asset Based on Commonality and Variability Analysis in a Product Line
    3. IEEE Trans Software Engineering V31n7(Jul 2005)pp551-569
    4. =CASE STUDY ETRAVEL REQUIREMENTS VARIABILITY DOMAIN MODEL COMPONENTS CASE TOOL DREAM USECASE UML XML
    5. Primitive Requirements: parts of use cases.
    6. Matrix of primitive requirements vs products.
    7. Stereotype use cases as<<common>>or <<optional>>

    Ommering05

    1. Rob van Ommering
    2. Software reuse in product populations
    3. IEEE Trans Software Engineering V31n7(Jul 2005)pp537-550
    4. =EXPERIENCE CONSUMER PHILLIPS REUSE COMPONENTS KOALA PROOF
    5. cf [Ommering00]
    6. Subsystems tend to be completely rewritten every 3.years or completely stable.
    7. (Yawnoc's Law): Make the organization mirror structure of the system.

    FrakesKang05

    1. William B Frakes & Kyo Kang
    2. Software Reuse Research: Status and Future
    3. IEEE Trans Software Engineering V31n7(Jul 2005)pp529-536
    4. =SURVEY =POLL =HISTORY REUSE

    BondG05

    1. Gregory W Bond
    2. Software as Art
    3. Commun ACM V48n8(Aug 2005)pp118-124
    4. =ESSAY ART
    5. Knuth

    Glass05b

    1. Robert L Glass
    2. "Silver Bullet" milestones in Software History
    3. Commun ACM V48n8(Aug 2005)pp15-18
    4. =HISTORY LANGUAGES MODULES OPERATING SYSTEMS ACADEMIC METHODS CASE TOOLS Object-Oriented agile open source

End