CS:4/53901-001 Software Engineering Fall 2008

Final has been given, all work has been turned in.

I will be posting grades to the Registrar this afternoon.

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

If you want to speak to me this week, email for an appointment. I will be in most days. I will have scheduled Office Hours right before the Final Exam on Friday, May 15 from Noon - 12:30 pm.

The final exam is on Friday, May 15, 2009 from 12:45 - 3:00 pm. The topics are:

• Sequence Diagrams (Ch 5)
• Basic stages of the software engineering process (Ch 6)
• 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
• 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.

Remember that all other work must be submitted by the start of the Final Exam.

The sixth assignment is to complete a convenient 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 5 steps that should be done in the order mentioned below. Each step can be done on different days. It is highly recommended to do step 1 and step 2 a day or so ahead of time. Note that the times given are approximate.

1. UML Class Diagram Tutorial -- optional
2. Design Pattern Tutorial (selected patterns) -- not optional and can be done multiple times ~15 minutes
3. Pre-Study Questionnaire (short background questions) ~10 minutes
4. Design Pattern Study ~20-30 minutes Available Wed May 6
5. Post-Study Questionnaire ~5 minutes Available Wed May 6

By completing questionnaire you will receive full credit. 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 Department of Computer Science continues its tradition of holding on Open House in the Spring. This year it is on Friday, May 1. You can get more information about the Open House using the link of this news item.

Included in the Open House is a Job Fair from 9 - 11 am. This is for students interested both in internships and full-time jobs.

To participate in the Job Fair bring your latest resume with you. More information is available on resume writing. Also, there is a list of companies that will be attending.

If you have further questions, please contact the Internship Coordination, Walter Pechenuk.

The sixth assignment is to complete a convenient 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.

By completing questionnaire you will receive full credit. 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.

Improve the Class Diagram design of Charts using design patterns. Investigate which patterns would be applicable to your design.

If you find an applicable design pattern, alter your class diagram to reflect this and create a Sequence Diagram to show how it will be used in a particular scenario. In the Readme.txt, write up how you found this pattern was applicable, and what other choices you considered.

If you do not find any applicable design pattern, then write up why not in your Readme.txt file. Then, create a Sequence Diagram for one of your scenarios.

Due by the Final Exam.

Assignment 4 contains a large number of steps. Also, I consider it an important assignment since it reflects the process of real-world development.

If you want to keep working on it, there will be no penalty. If you are not done by Friday, May 1, notify myself and the grader that you want more time.

Assignment 4 is to perform a series of refactorings. Each refactoring must be separately committed with a proper svn comment.

The starting code is in the repository. Make sure to commit after each step where you make changes.

Half of the steps must be completed by Monday, Apr 20. The rest are due by Friday, Apr 17 24.

Assignment 4 is to perform a series of refactorings. Each refactoring must be separately committed with a proper svn comment.

I am "under the weather" and won't make my office hours today.

I will be there for class.

Grades and comments are posted in the Eval subdirectory of the repository.

The third assignment is to create use case diagrams and scenarios 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 Thursday, Mar 19. Preliminary Use Case diagrams are due Tuesday, Mar 17.

The midterm exam will be on Thursday, Mar 19. 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)

Grades and comments are posted in the Eval subdirectory of the repository.

A few comments on how Assignment 1 was graded. 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:

• Missing classes to represent things in the description, e.g., XML
• 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, lists

Assignment 2 is due Thursday, Mar 12.

Make sure to take into account the feedback on Assignment 1.

Assignment 2 posted

We are covering the material in Chapter 3 of the textbook.

On a sheet of paper list all of the metrics mentioned in class. Approximately order the metrics from easiest to hardest to calculate.

I will be attending NSF (National Science Foundation) Day at the Student Center on Tuesday, Feb 10. I will not be in class, or hold office hours.

I am not sure of my schedule during the day, so you may see me around. If you have any questions about the assignment, then email and we can setup an appointment.

Ms. Natalia Dragan will present on Software Metrics in class.

Directory naming issue has been fixed. The url is the same:

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

If you checked it out previously, redo it.

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, Feb 12. By Monday, Feb 9 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 are covering the material in Chapter 2 of the textbook.

On a sheet of paper list the ...

We are covering the material in Chapter 1 of the textbook.

Read Chapter 1 of the textbook. We will start to cover this material 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 handed in on the second day of class.

Describe your previous software development efforts in terms of:

• Time - total time spent
• People - who was involved, e.g., Instructor,
• Kinds of files - source code, etc.
• Technologies - languages, build tools, IDE's

This will be handed in at the end of the first class.

This is news for the CS:4/53901-001 Software Engineering Spring 2009 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.