CS:4/53901-001 Software Engineering Fall 2008

Grading is all done, grades were calculated, and posted to the registrar system.

In the repository, all grades have been posted, including Assignment 4 and Extra Credit.

Have a good break. Rest up so that you can work hard in the Spring, just like you did this semester.

If you have any comments, observations about the UML questionnaire (aka Assignment 5), please email those to myself and Ms. Bonita Simoes (bsimoes@cs.kent.edu). The study that she is doing is a work in progress, and any input from you about the difficulty, confusions, etc. would further her work.

The grader started to put scores in for those that had completed Assignment 5 (the survey). However, these files were put into the Assignment 4 part of Eval. This will be fixed soon. Ignore any blank Score.txt files on Assignments 4 and 5.

Office hours for Finals Week are:

Tuesday, Dec 9 2 - 3 pm

Thursday, Dec 11 12 - 12:30 pm

I am also available by appointment. Just send me an email.

The grader and I are starting to grade the refactoring assignment. If you would like more time on it, email both me and the grader.

The final exam is on Thursday December 11, 2008 from 12:45 - 3:00 pm. The topics are:

• Software Lifecyle with Waterfall and Agile approaches
• Refactoring - motivation, definition, integration into process, parts (Fowler entry), main categories, know a couple of examples
• Design Patterns - elements of, categories: creational, structural, behavioral, with one example of each category
• Metrics - measure vs. metric, size-oriented metrics, object-oriented metrics and examples of each
• Software Testing - unit, integration, black box, white (clear) box,

As you can see, the list is the material that wasn't covered on the midterm. However, I may ask some overall questions regarding object-oriented analysis and design and UML as they fit into the overall process.

The final exam will be on Thursday December 11, 2008 from 12:45 - 3:00 pm. I will post a more detailed list soon, but the main topics will be:

• Software Lifecyle with Waterfall and Agile approaches
• Refactoring
• Design Patterns
• Metrics
• Software Testing

As you can see, the list is the material that wasn't covered on the midterm. However, I may ask some overall questions regarding object-oriented analysis and design and UML as they fit into the overall process.

Improve the Class Diagram design of Charts using design patterns. Investigate which patterns would be applicable to your design. If you decide to use a design pattern, then alter your class diagram to reflect this. Even if you find no design pattern is applicable, write up why not in your Readme.txt file.

Due by the Final Exam.

The fifth assignment is to complete an online UML Class Diagram questionnaire. This is part of a survey that Ms. Bonita Simoes, a CS Ph.D. Candidate, is doing as part of her dissertation work.

The login page for the study is available through the link for this news item. The username is the same as your subversion id, and the password is the same as your username (e.g, John Doe, Username: jdoe Password: jdoe). Ms. Simoes does not have access to your departmental password.

The study consists of:

• UML Class Diagram Tutorial (Optional)
• UML Study on Qt
• UML Study on wxWidgets
• A short Post Questionnaire

By completing the three required parts (Tutorial is optional) you will receive full credit on this. Your grade will only reflect that you completed the study, not on the quality of your answers. I will get a list from Ms. Simoes on who completed the study.

The assignment is due by the Final Exam.

The fifth assignment is to complete an online UML Class Diagram questionnaire. This is part of a survey that Ms. Bonita Simoes, a CS Ph.D. Candidate, is doing as part of her dissertation work.

The assignment is due by the Final Exam.

Assignment 3 scores are now in the repository. I thought that I had posted these before, but an error in one of the student accounts was blocking these.

VideoStore's due date is now on Thursday (instead of Tuesday).

The slides on software metrics presented by Ms. Natalia Dragan are now posted in the notes directory.

Assignment 4 is to perform a series of refactorings. Each refactoring must be separately committed with a proper svn comment. The Assignment is due Tuesday, Nov 18.

Due to the Holiday, there is no class or office hours on Tuesday, Nov 11.

I will be out of town Wednesday, Nov 12 - Friday, Nov 14. Class on Thursday, Nov 13 will be handled by Ms. Natalia Dragan. She will speak on Software Metrics. You are responsible for this material.

I will not have office hours on Thursday. If you did not pick up your midterm, then ask Ms. Dragan after class on Thursday (she will have them with her).

Assignment 4 is to do some refactoring. I am not quite finished with the directions, but you can start of the first part.

I will have office hours from 1 - 2 pm on Tuesday before the exam. These are in place of my regular hours.

In the Eval directory.

The midterm exam will be on Thursday, Oct 23 Tuesday, Oct 28. The main topics will be:

• Why Software is inherently complex (Ch 1)
• Attributes of a "good" complex system (Ch 1)
• Algorithmic and Object-Oriented Decomposition (Ch 1)
• Object Model - 7 parts (abstraction through persistence) (Ch 2)
• Types of abstraction (Ch 2)
• Object - state, behavior, identity (Ch 3)
• Relationships between objects (Ch 3)
• Classes - interface, implementation (Ch 3)
• Relationships between classes (Ch 3)
• Coupling and Cohesion
• Class Diagrams (Ch 5)
• Use-Case Diagrams, and use-case scenarios (Ch 5)
• Sequence Diagrams (Ch 5)
• Basic stages of the software engineering process (Ch 6)

The midterm exam will be on Thursday, Oct 23. I will post a more complete list later, but the main topics will be:

• First 3 Chapters of the book
• Class diagrams, sequence diagrams, and use-case diagrams (Chapter 5)
• Basic stage of the software engineering process

The folder for the work in Assignment 3 has been added (it was not before). Move your artifacts into this directory (Assignment3/Charts).

Due to the folder problem, Use Case diagrams and scenarios are due Tuesday, Oct 14. Sequence Diagrams are now due Thursday, Oct 16.

The third assignment is to create use case diagrams, scenarios, and sequence diagrams for the Chart project. More details at the title link. You will submit your work in the folder Assignments/Assignment3/Charts. Please do not hand in any printed copies. This folder has already been created in the repository.

The assignment is due Tuesday, Oct 14. Preliminary Use Case diagrams are due Thursday, Oct 9.

In class on Tuesday I vaguely mentioned something about the "barn color". What I was referring to is called the "color of the bikeshed". Go to the link for this news item for more explanation. Another use of this term is by Linus Torvaldes about Linux Kernel development where he uses the term "bike-shed-painting". Term is also explained as part of BSD

A few comments on how Assignment 1 was graded (as mentioned in class). The score reflects the items listed in the assignment (.hpp and .cpp files, compilation, Readme, etc.) and how much work was put into it. It does not reflect the quality of the design. So make sure to consider the points made in the feedback of the Score.txt file.

A few main common issues:

• Class names that indicated action (verbs) rather than things (nouns)
• Lack of a control class
• Lack of a class that interfaces with the user (not the same as the control class)
• Too much detail with missing higher-level design, e.g., vector

I put the PowerPoint slides in the notes directory. There is now a link for it on the class page.

The second assignment is to write the design for a Charts program as UML Class Diagrams. More details at the title link. You will submit your work in the folder Assignments/Assignment2/Charts. Please do not hand in any printed copies. This folder has already been created in the repository.

The assignment is due Tuesday, Sep 30.

If you have any questions, do not know how to do something, etc. then you need to ask, either me or the Teaching Assistant. This is the time to do so.

The second assignment is to write the design for a Charts program as UML Class Diagrams. More details at the title link. You will submit your work in the folder Assignments/Assignment2/Charts. Please do not hand in any printed copies. This folder has already been created in the repository.

The assignment is due Tuesday, Sep 30 Thursday, Oct 2.

If you have any questions, do not know how to do something, etc. then you need to ask, either me or the Teaching Assistant. This is the time to do so.

Trying out an online drawing tool (similar to Visio)

To add a file to the repository, create an empty file first. For the svn client use the command:

	  svn add filename
	

If you are using TortoiseSVN, then the submenu TortoiseSVN has an Add item.

Note that like any change in your working copy, you will have to commit your file addition to the repository before it will show up there. Always use a web browser to check what is in the repository.

The first assignment is to write the design for a Charts program as a set of C++ classes. More details at the title link. You will submit your work in the folder Assignments/Assignment1/Charts. Please do not hand in any printed copies. This folder has already been created in the repository.

The assignment is due Thursday, Sep 18. On Monday, Sep 15, you must have at least one class of your design coded and submitted.

If you have any questions, do not know how to do something, etc. then you need to ask, either me or the Teaching Assistant. This is the time to do so.

We are using a subversion repository to turn in all assignments for this class (not including inclass homework).

The url for your part of the repository is:

	  http://classes.cs.kent.edu/courses/cs43901/svn/001/username/cs43901_student/
	

where username is replaced with your departmental username. Your password is your departmental account password. I suggest you try this out in a web browser first.

To checkout a working copy of your repository (so you can edit and add files), you can use the svn tool with the command:

	  svn checkout http://classes.cs.kent.edu/courses/cs43901/svn/001/username/cs43901_student/
	

This will create a directory called cs43901_student.

If you are using a GUI subversion client (e.g., TortoiseSVN), then I suggest creating a folder with the name cs43901_student first, and then checkout your project in that folder.

Note It is very important to do your work in your working copy. Do not work on your files elsewhere, and then right before they are due move them to a working copy. If you are having problems using the repository, get help right away, not right before they are due.

We will be using the example of a temperature sensor to demonstrate various issues of the Object model. At the end of class, turn in a version of the class that we create keeping in mind issues of abstraction, encapsulation, modularity, hierarchy, typing, concurrency, and persistence.

We will finish most of Chapter 3 of the textbook this week.

A Teaching Assistant, Ms. Jalaa Hoblos, has been assigned to this course. She will be grading the homeworks, assist in grading assignments and tests, and recording scores. Instead of a set office hour times, she will be available for appointments. Her contact information is posted on the main page for the course under Information.

Read Chapter 2 of the textbook.

I posted (under Information links to the textbook online through Safari Books Online.

On the occasion of the title, actor Stephen Fry has released "Happy Birthday to GNU", a video with his explanation of what the GNU project is about.

The compilers gcc and g++, the Emacs editor, and more utilities then you can imagine are part of the GNU project.

Read the Tim Bray posting, and answer the following questions:

• Where did the maxim "Build One to Throw Away" come from?
• What is the full quote that states this maxim?
• Why might following this maxim literally have disadvantages?

This will be collected on Thursday, Sep 4 during class.

Periodically during the semester I will direct your attention to postings (primarily blog entries) on aspects of software development. The reasons for doing this include:

• Let you see that these issues exist in the real world
• Provide external validation to the statement made in class
• To get you started in reading good online resources for developer information

Tim Bray (Wikipedia to find out who he is) has an explanation of how a design decision turned out to be wrong when features were added to the system. Of even more importance is his observation about design that "... we're not smart enough to get anything important right the first time".

Note that the solution proposed in the title is really not what he did. We need to learn how to constantly and carefully evolve systems, replacing the parts that were not done "right" the first previous time. It is not that important how good your initial design is. It is more important how good it gets and how quickly it gets to be a good design.

On a sheet of paper write down what makes up the architecture of a well-designed system. This will be handed in at the end of class.

As you probably noticed, some of the news items no longer appear. Only the current ones remain listed on the course page. Note that all news items are available in the feed, and on the Archive page.

Read Chapter 1 of the textbook. We will be covering most of it on Thursday.

On a sheet of paper write down the following:

• Name
• When you completed CS 33001
• Other CS courses have you taken (after CS 33001)
• Other CS courses you are taking this semester
• Programming experience outside of CS classes

This will be done and handed in on the first day of class.

This is news for the CS:4/53901-001 Software Engineering Fall 2008 at Kent State University. All changes, updates, and clarifications to the pages for this course will be noted as news items. In addition, news will be used for announcements. Recent news will appear on the main page while all news will be available on a separate archive page. This news is available as an RSS feed, and you can monitor them using an RSS reader. If you are using the Firefox browser then you can add a Live Bookmark for this page. The link in the title directs you to instructions for doing so.