CSCI 590: Summer Directed Research - CPT in Software Engineering

Summer 2000

        The following is a suggested approach to learning about MBASE for those who have not completed CS577a&b.
 

        1. First exposure & Big Picture
            When Models Collide: Lessons From Software System Analysis (PDF)

        2. MBASE Background:

            2.1. CS577a-1999 WebSite – Electronic Papers at http://sunset.usc.edu/classes/cs577a_99/EP.html

                        2.1.1. Escaping the Software Tar Pit: Model Clashes and How to Avoid Them (PDF)

                        2.1.2. Using the WinWin Spiral Model: A Case Study (PDF)

                        2.1.3. A Stakeholder Win-Win Approach to Software Engineering Education (PDF)

                        2.1.4. Software Requirements Negotiation: Some Lessons Learned (PDF)

                        2.1.5. Anchoring the Software Process (PDF)

                        2.1.6. Guidelines for MBASE Project Deliverables (PDF)

                        2.1.7. A Spiral Model of Software Development and Enhancement (PDF)

                        2.1.8. Theory-W Software Project Management: Principles and Examples (PDF)

                        2.1.9. Software Risk Management: Principles and Practices (PDF)

                        2.1.10. Requirements Engineering, Expectations Management, and The Two Cultures (PDF)

            2.2. OO/UML Books (CS577a Variant of MBASE):

                        2.2.1. Texts for CS577a-1999 & CS577b-2000:

                                2.2.1.1. WR refers to chapters in the textbook: Walker Royce, Unified Software Management,
                                            Addison Wesley, 1998

                                2.2.1.2. CL refers to chapters in the textbook: Craig Larman, Applying UML and Patterns.
                                            Prentice-Hall, 1998; ISBN: 0137488807

                        2.2.2. Supplemental reference books

                                2.2.2.1. The Unified Modeling Language User Guide by Grady Booch, James Rumbaugh and Ivar Jacobson;
                                            Addison-Wesley 1999; ISBN 0-201-57168-4

                                2.2.2.2. The Rational Unified Process by Philippe Kruchten; Addison-Wesley 1998; ISBN 0201604590

        3. MBASE Guidelines

            3.1. For those who have taken only CS577a, it is recommended that you also get the updated MBASE Guidelines:

                        3.1.1. RUP Guidelines for Model-Based Architecting and Software Engineering (MBASE) deliverables: Inception and Elaboration (PDF)

                        3.1.2. Guidelines for Model-Based Architecting and Software Engineering (MBASE) deliverables: Construction, Transition and Support (PDF)

            3.2. From the Electronic Papers (http://sunset.usc.edu/classes/cs577b_2000/EP.html)

                        3.2.1. Guidelines for Model-Based Architecting and Software Engineering (MBASE) deliverables: Inception and Elaboration (DOC)

                        3.2.2. Guidelines for Model-Based Architecting and Software Engineering (MBASE) deliverables: Construction, Transition and Support (DOC)

        4. MBASE Information from the MBASE Website:  http://sunset.usc.edu/research/MBASE/index.html

            4.1. Papers, in order of importance, not listing on the site Boehm, B. and Port, D.,
            "When Models Collide: Lessons From Software System Analysis," January 1999. (PDF):

            4.2. Presentations: both old

                        4.2.1. Mini-Tutorial on MBASE

                        4.2.2. Developing and Integrating Software/System Product Process Property and Success Models
 
 

Questions or Suggestions
Last Updated on 06/14/2000