15-413 Software Engineering

Carnegie Mellon University

School of Computer Science

Handout 1

24 August 1999

Course Syllabus

Homepage: http://sierra.se.cs.cmu.edu/STARS/

People

Instructors

E-mail

Office

Bernd Bruegge

bob+@cs.cmu.edu

WeH 4123, 268-2567

William Scherlis

wls+@cs.cmu.edu

WeH 5220, 268-8741

Coaches

David Garmire

garmire+@andrew.cmu.edu

Tom Hawley

hawleyt+@cs.cmu.edu

Grace A Ritter

gritter+@cs.cmu.edu

Pooja Saksena

saksena+@andrew.cmu.edu

Eric Stein

es5f+@andrew.cmu.edu

Zia Syed

smzia+@cs.cmu.edu

Secretary

Dorothy Zaborowsky

daz+@cs.cm.edu, Mo-Fri

WeH 4116

Aside from office hours and weekly project meetings please feel free to stop by and make individual appointments.

Objectives

Upon completion of this course, a student should be able to:

  • Understand the difference between a program and a software product.
  • Apply model-based software engineering techniques.
  • Understand iterative and incremental development.
  • Reconstruct the analysis and design information in an existing software system.
  • Design and implement a module that will be integrated into a larger system.

Each student will have demonstrated the ability to

  • Work as a member of a project team, assuming various roles as necessary,
  • Create and follow project plans and test plans,
  • Create the full range of documents associated with software products,
  • Complete a project on time.

Administrative Matters

Meeting Times

First class: Tuesday, Aug 24, 1999

Class meetings: Tuesdays and Thursdays 9:00 - 10:20

  • Hammerschlag B103

Project Meeting: Weekly arranged by each team.

Client Acceptance Test: Dec 9

Textbook

Required :

Bernd Bruegge, Allen Dutoit: "Object-Oriented Software Engineering: Conquering Complex and Changing Systems". The first chapters are online and the book is due to be published in October.

Optional Readings

.

  • [Gamma 96] E. Gamma, R. Helm, R. Johnson, J. Vlissides: "Design Patterns", Addison-Wesley, 1996
  • [Jacobsen 92] I. Jacobson, M. Christerson, P. Jonsson, G. Övergaard, "Object-Oriented Software Engineering" Addison Wesley, 1992
  • [Booch 91] Grady Booch, "Object-Oriented Design with Applications", Benjamin Cummings, 1991. Ch. 1.
  • [Pfleeger 91] Sharie Pfleeger, "Software Engineering: The Production of Quality Software", MaxMillan Publishing Company, 1991. Ch. 9, 10 and 11.
  • [Otte 1996] "Understanding CORBA, The Common Object Request Broker Architecture", Prentice Hall, 1996
  • [Kayser 90] T. A. Kayers, "Mining Group Gold", Serif Publishing, 1990.
  • [IEEE 828] IEEE Standard for Software Configuration ManagementPlans, ANSI/IEEE Std. 828-1990.
  • [IEEE 1058] IEEE Standard for Software Project Management ANSI/IEEEStd.1058.1-1987.

Additional papers may be selected. Copies for readings are provided during the course.

Computing

The facilities in the Software Engineering Lab in Building D 154A are available only for the use in this course. In addition to the standard CS NT/Linux environment and six iMacs many tools and applications specific for this course will be used. Please check http://sierra.se.cs.cmu.edu/STARS/docs/computerLab.html in the 15-413 web site for an accurate listing.

Grading

Process and Products

(40 Points)

  • Equal weight is given to each of the following activities and/or associated documentation: Project plan, requirements analysis (domain model, analysis object model), system design, object design, implementation, testing, user manual, installation guide, posting meeting agenda & minutes.
  • The documentation has to be developed in cooperation between technical writers and software developers.

Communication

(5 Points)

  • For a presentation given during one of the project reviews (analysis review, client review, object review, dry-run, acceptance test) or group meetings.

Delivery (20 Points)

  • If a complete product (working code and complete documentation) with negotiated functionality is delivered to the client.

Homework (20 Points)

  • 4 points for each of 5 homeworks.

Quiz (15 Points)

  • 1 point for each quiz on main points of reading at the beginning of each class (except project review classes).

Instructors' evaluation

(+/-10 Points)

Standards

  • A: 90+
  • B: 75-89
  • C: 56-74, including at least 20 points fromlectures and 40 points from project
  • D: 40-55, or 56-74 with wrong proportion of lectureand project points
  • R: less than 40

Course Schedule

The course schedule will be updated as we progress through the semester. Check for the most up to date class schedule in the 15-413 home page.




This page is hosted by the Chair for Applied Software Engineering of the Technische Universität München.
Imprint (Impressum)