{[ promptMessage ]}

Bookmark it

{[ promptMessage ]}

CS6704-Class3 - Advanced Topics in Software Engineering...

Info icon This preview shows pages 1–3. Sign up to view the full content.

View Full Document Right Arrow Icon
1 © 2008 Shawn A. Bohner Advanced Topics in Software Engineering: Software Systems Evolution Software Systems Evolution CS6704: Class CS6704: Class 3 Instructor: Shawn A. Bohner Voice: (540) 231-1132 Email: [email protected] 2 Agenda Discussion of Reading Assignment Brief Review Last Week’s Material A Case for Software Change Software Maintenance Perspective Homework Assignment 3 Jan Jan Feb Mar Apr May Class Begins Case for SW Change Software Maintenance Software Change Models Impact Analysis Technologies Model-Based Engineering Final Exam (5/5) Software Evolution Principles Biological Evolution Models Self- Adapting, Healing Systems Approaches for Long-lived Systems Spring Semester Timeline (Tentative) Mid-Term Exam (3/13) Reconfigurable Computing
Image of page 1

Info icon This preview has intentionally blurred sections. Sign up to view the full version.

View Full Document Right Arrow Icon
2 4 This Week’s Reading/Discussion Some questions to answer for each paper: What is the thrust or message of the paper? What did you learn regarding Software Systems Evolution? How could you apply these concepts to your research area? How could you apply these concepts to a class project? “Towards a Taxonomy of Software Change” by Jim Buckley et al 5 Software Evolution The Law of Continuing Change (1974): E-type systems must be continually adapted else they become progressively less satisfactory. The Law of Increasing Complexity (1974): As an E-type system evolves its complexity increases unless work is done to maintain or reduce it. The Law of Self Regulation (1974): The E-type system evolution process is self-regulating with distribution of product and process measures close to normal. The Law of Conservation of Organizational Stability (1980): The average effective global activity rate in an evolving E-type system is invariant over product lifetime. Source: Lehman, M., et al, “Metrics and Laws of Software Evolution—The Nineties View,” Proceedings of the 4th International Software Metrics Symposium (METRICS '97), IEEE, 1997, can be downloaded from : http://www.ece.utexas.edu/~perry/work/papers/feast1.pdf 6 Software Evolution (continued) The Law of Conservation of Familiarity (1980): As an E- type system evolves all associated with it, developers, sales personnel, users, for example, must maintain mastery of its content and behavior to achieve satisfactory evolution. The Law of Continuing Growth (1980): The functional content of E-type systems must be continually increased to maintain user satisfaction over their lifetime. The Law of Declining Quality (1996): The quality of E-type systems will appear to be declining unless they are rigorously maintained and adapted to operational environment changes. The Feedback System Law (1996): E-type evolution processes constitute multi-level, multi-loop, multi-agent feedback systems and must be treated as such to achieve significant improvement over any reasonable base.
Image of page 2
Image of page 3
This is the end of the preview. Sign up to access the rest of the document.

{[ snackBarMessage ]}

What students are saying

  • Left Quote Icon

    As a current student on this bumpy collegiate pathway, I stumbled upon Course Hero, where I can find study resources for nearly all my courses, get online help from tutors 24/7, and even share my old projects, papers, and lecture notes with other students.

    Student Picture

    Kiran Temple University Fox School of Business ‘17, Course Hero Intern

  • Left Quote Icon

    I cannot even describe how much Course Hero helped me this summer. It’s truly become something I can always rely on and help me. In the end, I was not only able to survive summer classes, but I was able to thrive thanks to Course Hero.

    Student Picture

    Dana University of Pennsylvania ‘17, Course Hero Intern

  • Left Quote Icon

    The ability to access any university’s resources through Course Hero proved invaluable in my case. I was behind on Tulane coursework and actually used UCLA’s materials to help me move forward and get everything together on time.

    Student Picture

    Jill Tulane University ‘16, Course Hero Intern