2 Course Structure

2.1 Sessions

• Recitations: Mon 1:00pm-3:00pm and Wed 6:00pm-8:00pm (selected weeks)

  Recitations will be used for special topics and for meetings with teams once the semester project is underway.

  • They will not meet every week.
  • Meetings will be on-line.
    • You will attend from your “development machine”.

• Lectures: No regularly scheduled meetings

  Lecture materials for this course will be available on-line, primarily in printed/text form.

2.3 Review Recordings

I provide recorded Reviews on the course site. These are, in general, condensed versions of what would traditionally be live lectures. This includes:

2.6 Semester Project

A moderately large program on which you will work in teams of 4-6 people.

Five phases:

1. Writing Requirements
2. Planning for construction: writing user stories
3. Early construction: build management, version control, story tracking, project website
4. Middle construction: configuration management, documentation management, continuous integration
5. Later construction: integration testing, analysis tools

In general, you will be evaluated upon process as much as upon you ability to produce working code.

2.6.1 Project Teams

• I will assign you to a team, at random, for the first phase (Phase 1).

• You will choose your own teams for the remaining phases

  • Must be members of your recitation section.

2.6.2 Project and Recitations

The final three phases will be evaluated in part via a team meeting with the instructor.

• Held during recitation period
• Instructor will ask questions about team’s overall progress.
• The instructor may direct questions to specific team members to be sure that everyone shares an understanding of the project and required skills.

  • General rule is that if one member of a team does not know something, that’s a mark against that person. If two people don’t know something, that’s a mark against the entire team.

• At end of some meetings, you may receive a short test/assignment, which each team member must complete individually within a limited time period (a day or less).

3 Course Pre-requisites

4.1 Office Hours

4.2 Course Forums

• Hallway
  • for general discussion of course topics
    • no discussion of assignment solutions!
• Janitor’s Closet
  • reports of site issues, broken links, missing or incorrect web pages, etc.

5 Important Policies

5.1 Late Submissions

… are not normally accepted. Exceptions may be made in cases of

• documented emergencies
• arranged prior to the due date when possible.

Extensions to due dates will not be granted due to

• difficulties “porting” from one system to another
• transient system crashes
• system overloaded

5.2 Academic Honesty

ODU is governed by a student honor code.

6 Course Themes

Questions

• What is “Software Engineering”?

  • What is “Engineering”?

  • Is there “engineering” in software development?

6.2 Areas of Emphasis

• Teamwork
• Test-Driven Development (JUnit)
• Build Management (Gradle)
• Version Control (Git)
• Configuration Management (Gradle)
• Documentation Management (Javadoc)

6.2.2 Test-Driven Development (TDD)

Exemplified by the philosophy of “write the tests first, then design and write the code.”

• A good build manager will not only compile and link the source code…

• A good build manager will not only compile and link the source code…

• It will also run the tests

• A good build manager will not only compile and link the source code…

• It will also run the tests

  • making it more difficult to not test after every change

• A good build manager will not only compile and link the source code…

• It will also run the tests

  • making it more difficult to not test after every change

• and update the documentation and reports

6.2.3 Build Management

Making sure that you and others can build the system easily.

• A good build manager will not only compile and link the source code…

• It will also run the tests

  • making it more difficult to not test after every change

• and update the documentation and reports

  • again, actually requiring the programmer to work harder to let these things get out of sync than to keep them up to date

6.2.4 Version Control

The ability to track changes in the software.

• Avoid accidents
• resolve conflicting changes
• Explore ideas, then discard ones that turn out to be undesirable

6.2.5 Configuration Management

• How do we cope with importing third-party libraries that are themselves changing and have version depencies among themselves?
• How do we cope with dependencies of our own software upon the underlying platform?

6.2.6 Documentation Management

• Integrating documentation into the development process,
  • minimizing the “chore”.