1. 1 Course Intro Construction & Evolution CSSE 375 Steve Chenoweth

2. 2 Today Logistics of the course – see syllabus Intro to the course – this : –Problem –Inspiration(s) –What it’s about, & course outcomes –& related goals –What’s changing about it –What would you like? –Things to do next…

3. 3 Problem I.e., Why’s this course here? Most “new” development is done – –“using” other people’s software, and –assuming this stuff itself will be “used” for a long time. Systems are built from components and from other systems. Most “development” isn’t new at all – it’s “maintenance.” Learning to do this well – makes sense.

4. 4 Inspiration Candid shot from the Creation Museum, Hebron, KY:

5. 5 Further Inspiration – Lehman’s Laws of Software Evolution LawStatement ? Continuing change Increasing complexity Self regulation Conservation of organisational stability Conservation of familiarity Continuing growth Declining quality Feedback system From http://openlearn.open.ac.uk/mod/resource/view.php?id=179612http://openlearn.open.ac.uk/mod/resource/view.php?id=179612

6. 6 So… 375 is about evolving software What’s the real “life cycle”? How to hold down costs by doing things right –In the original construction –As the system evolves Which leads to our course “outcomes” --

7. 7 Course Outcomes – 1-5 1. Explain how to plan for and transition to maintenance. 2. Use the software maintenance process model. 3. Participate on a software maintenance team. 4. Re-engineer requirements and design for an existing project. 5. Effectively employ in construction implementation methods and tools studied in earlier courses.

8. 8 Course Outcomes – 6-10 6. Utilize a common development environment for construction activities (currently C++). 7. Engineer software to meet performance and reliability objectives. 8. Develop software user documentation. 9. Verify the Laws of Software Evolution. 10. Develop white-box tests for construction activities.

9. 9 And, also leads to stuff we’ll do / try as part of this First-hand experience supporting other people’s code Learn about using / adding to Open Source tools Pad your resume with C++ skills Focus on good coding practices …as part of good development practices Build on your design & testing skills How to engineer-in quality attributes Enhance your teaming skills

10. 10 Things I’m still evolving…vs what you now see on course website Course schedule – Adjusting for a few new outcomes Fridays – lab days Assume you can apply skills from 371, 372, 373, 374, 376, 377 The daily quizzes – slightly more challenging Assume you’ve read relevant sections in book before class Emphasize good practices -- 375  Senior project  Work

11. 11 Tell me about you! Who you are What’s your domain track? Something interesting you just did Something you’d like from this course

12. 12 Things to do A.Bring your laptop tomorrow! B.Read Maintenance book – Ch 6. C.If you didn’t yet fill out my email survey, please do so by end of the day today. Here’s a copy of the questions: In order for us to target the class for “where you are in your own experience,” please reply with answers to the following 3 quick questions: 1. In a sentence, please describe your current amount of experience in the software development industry, especially in terms of developing and supporting code: 2. Are you already familiar / experienced in using C++ ? If you are, what development environments (e.g., Visual Studio) have you used? 3. Have you developed or supported Open Source software before? If so, which ones?