Course OverviewKenneth M. AndersonUniversity of Colorado, BoulderCSCI 5828 — Lecture 1 — 01/15/2008© University of Colorado, 20081Wednesday, January 16, 2008Goals of this Class (I)• Survey traditional software engineering concepts, terminology, and techniques• Take an in-depth look at software engineering techniques for dealing with concurrency in software systems• Also take a glance at Tim Bray’s Wide Finder project and its associated issues• Learn about Agile Design methods, including Scrum and Extreme Programming• Review the philosophy and techniques of a successful Web 2.0 company2Wednesday, January 16, 2008Goals of this Class (II)• First topic ensures that a student new to software engineering leaves the course with a grasp of the basic concepts and tenets of the field• Second topic provides students with an explicit example of how software engineering techniques can be used to tackle complex problem domains• Relevant topic: hardly a week goes buy without some mention of multi-core computers and how they are changing the game on developers• Single threaded / Single process applications will soon be outshone by multi-threaded / multi-process applications• Consider an image processing example• The latter two topics will provide the student with insight into how the field of software engineering is changing3Wednesday, January 16, 2008CAETE Announcements• In-Class Students• CAETE has a busy studio schedule• Be sure to exit promptly so next class can begin on time• Food and Drink are not technically allowed• Drinks are tolerated, as long as you keep the studio clean!• Distance Students• Textbooks can be ordered from the CU Bookstore• Call 303-492-6411 or 800-255-9168• Or order on-line at <http://cubooks.colorado.edu/>4Wednesday, January 16, 2008Due Dates for CAETE Students• Due dates for assignments and exams for CAETE students are one week behind the due dates for in-class students• CAETE students need to make sure that they have a “test proctor” at their company who will be willing to administer the midterm for them• If you don’t know who your test proctor is, contact CAETE to find out• (Do this during the first week of classes!)5Wednesday, January 16, 2008A bit about me…• Associate Professor• At CU since July 1998• Ph.D. at UC Irvine• Research Interests• Software Engineering• Hypermedia / WWW• In field since 1991• REST-based Web Services6Wednesday, January 16, 2008A little bit more…• 20th semester at CU (!)• 4th time teaching CSCI 5828• Software Development Experience• Approximately 16 systems, 30K — 100K each• Some industry experience with IBM & Unisys• Experience with academic/industry collaboration7Wednesday, January 16, 2008Office Hours• ECOT 822• Monday: 10:30 AM — 11:30 AM• Thursday: 1:00 PM — 2:00 PM• … or by appointment8Wednesday, January 16, 2008Class Website:<http://www.cs.colorado.edu/~kena/classes/5828/s08/>9Wednesday, January 16, 2008• Check the website every day!• An RSS feed of the What’s New page makes this an easy task• The website is your source for• class schedule• lectures• assignments• announcements• etc.About the Class Website10Wednesday, January 16, 2008Textbooks (I)Pfleeger and Atlee’s Software Engineering: Theory and PracticeOur guide to traditional software engineering. Well written and comprehensive.Addresses “art versus science” debate with respect to developing software-based systemsSee for instance “Undergraduate Programming” written recently by Joel Spolsky11Wednesday, January 16, 2008Textbooks (II)Magee and Kramer’s Concurrency: State Models & Java Programmingaka “The Two Jeffs”Every developer needs to understand concurrency (esp. in a multi-core world)This book does an excellent job covering this topic with a software engineering perspective; indeed it shows the power that lies in the techniques and tools of traditional software engineering12Wednesday, January 16, 2008Textbooks (III)• The course will switch between the two topics• presenting an intro to software engineering one day• looking at the issues of modeling concurrency the next• Please start reading the first two chapters of each text book13Wednesday, January 16, 2008Class Participation• I welcome participation by students• Feel free to interrupt me during lecture to ask questions!• “Stupid Questions” — No such thing!• Discussion: “Silent Tomb” — Boring for me and you!• If I’m speaking too fast, stop me and ask me to slow down14Wednesday, January 16, 2008Teaching Philosophy• “sage-on-stage” vs. “guide-at-your-side”• Answering questions• Sometimes the answer will be “I don’t know!”• Current Tech• I try to incorporate references to current technology in my teaching• Ruby, Python, Ruby on Rails, Django, etc.• Bias?• I don’t use Microsoft Windows and so have no experience with .Net, C#, Vista, etc., however I’m not “anti-Microsoft” and I will welcome student’s use of and presentations about Microsoft technology15Wednesday, January 16, 2008Course Evaluation• Your grade will be determined by your work on• Reviews (simple questions to make sure you do the reading)• One a week (including this week), grades: “+”, “✓”, or “-”• Review for this week will be posted tomorrow• Will be on chapter 1 of the Pfleeger textbook• Homeworks (typically problems from the Concurrency textbook)• Midterm (Tuesday, March 4th in-class, by Tuesday March 11th CAETE)• Class Project (Due at the last class session; students will work in teams)• NO FINAL!16Wednesday, January 16, 2008Moodle• We will be using a Web-based system called “The Moodle” to submit homework assignments• You will need to enroll in the CSCI 5828 course• Go to http://moodle.cs.colorado.edu/• If you do not have a moodle account, create one• Log in• Click on “All Classes” button and look for CSCI 5828 for Spring 2008• Click on it and follow instructions to enroll• You will need an enrollment key: seTaPSpring200817Wednesday, January 16, 2008Honor Code• I encourage collaboration in this class via the reviews and the class project• I’d like, however, for the homeworks and midterm to be worked on individually• As such, the honor code statement will be printed on each homework assignment and the midterm to remind you that collaboration is not allowed• The Student Honor Code
View Full Document
Unlocking...