Course Progress Lecture Notes Managing Software Development Spring

  • Slides: 15
Download presentation
Course Progress Lecture Notes Managing Software Development Spring 2005

Course Progress Lecture Notes Managing Software Development Spring 2005

First week: • lecture 06 -project-planning. ppt – Why do we need better management

First week: • lecture 06 -project-planning. ppt – Why do we need better management of software development. Good planning technique. Growing software incrementally using phases. • hyperj. ppt, lec 0 -csu 670*, aop. ppt: – preparation for hw 1, Multidimensional separation of concerns. Using adaptive programming to implement concerns. Discussions of files in /hw/1

First week (not covered yet): • Software. Engineering 2. ppt: Intro. To software engineering

First week (not covered yet): • Software. Engineering 2. ppt: Intro. To software engineering (B. Meyer): delayed. • Basic. Intro. Lo. D. ppt: explains domain of project. • requirements. ppt: preparation for hw 2: writing a requirements document.

Plan for second week: • Review of material from previous lecture – Several of

Plan for second week: • Review of material from previous lecture – Several of you could not come • Agile Software Development: an unorthodox view of Software Engineering. – Agile Software Development. ppt • Discuss assignment 2 • Software Life Cycle: requirements. ppt (did not get to this)

3. week • Second assignment • Cover topics on the agenda for the first

3. week • Second assignment • Cover topics on the agenda for the first two weeks.

5 week • Discussion of hw 4 • Writing a software development plan •

5 week • Discussion of hw 4 • Writing a software development plan • Growth plans: lec 5 -short-csu 670 -f 04. ppt

The rest remains to be planned

The rest remains to be planned

Third week: • • Lo. D analysis: Basic. Intro. Lo. D. ppt (slides at

Third week: • • Lo. D analysis: Basic. Intro. Lo. D. ppt (slides at end) Aspect-Oriented Software Development aosd. ppt Hw 3 Continue Agile Software Development (continue with 29) • Continue Aspect. J (continue with 39) • Version control: berkeley/lecture 07*. ppt

4. week • Hw 4 • Continue Agile Software Development (continue with 36) •

4. week • Hw 4 • Continue Agile Software Development (continue with 36) • Continue Aspect. J: – Tutorial – Development aspects, Production aspects: aosd. ppt – Caching. ppt • Version control: berkeley/lecture 07*. ppt

5. week • Sergei Kojarski on Eclipse: . . /eclipse • Visit at MIT:

5. week • Sergei Kojarski on Eclipse: . . /eclipse • Visit at MIT: SE notes on decoupling mit/lec-02 jackson-Lo. D. ppt. • Visit to Berkeley: Project Planning Lecture: berkeley/lecture 06 -project-planning. ppt • Visit to CMU/Munich: Bruegge’s lectures: requirements. ppt • Review of Aspect. J: lec-Aspect. J-f 02. ppt • aosd. ppt: advice precedence

6. week • • Eclipse Sergei Hw #5. ppt Eclipse eclipse-slides. ppt Licensing Software

6. week • • Eclipse Sergei Hw #5. ppt Eclipse eclipse-slides. ppt Licensing Software Engineers. ppt Modeling aspect-oriented systems: what means crosscutting?

7. week • Midterm discussion • Hw 5 discussion • Sommerville on (see lectures/sommerville)

7. week • Midterm discussion • Hw 5 discussion • Sommerville on (see lectures/sommerville) – User Interface Design • Relevant to the Eclipse project – Systems Engineering • Emerging properties and AOSD – Verification and Validation • Applied to Lo. D checker and Eclipse plug-in • Extreme Programming; quick intro (extreme. ppt)

8. week • How to validate predictive capabilities of software metrics. A Validation of

8. week • How to validate predictive capabilities of software metrics. A Validation of Object. Oriented Design Metrics. ppt • CMM: process improvement: ch 25 -processimprovement. ppt • Lo. D implementation: design review • Eclipse: some demos

9. week • More on predictive software metrics: A Validation of Object-Oriented Design Metrics.

9. week • More on predictive software metrics: A Validation of Object-Oriented Design Metrics. ppt: done • Eclipse/Lo. D checker: presentation by Paul: done • Test coverage project by Dale, Richard, Ryan: done • Software change: chapter 27 Sommerville (directory sommerville) – My connection: Modeling service businesses, Verizon: done • Software testing: chapter 20 Sommerville – Apply to testing Lo. D • Design Patterns and Aspect. J (Hannemann – Kiczales OOPSLA 2002 paper) • Demos ?

10. week • Discussed take-home final in hw/take-home • Discussed Stamp Coupling Take. Home

10. week • Discussed take-home final in hw/take-home • Discussed Stamp Coupling Take. Home Final. ppt (in lectures) • Reviewed Lo. D checker Lo. D-overview. ppt • Brief course review: Software Engineering 2. ppt