Skip to content

Latest commit

 

History

History
101 lines (62 loc) · 6 KB

course-info.md

File metadata and controls

101 lines (62 loc) · 6 KB

CS/COE 1530 Software Enginer

Software Engineering

Course Information

Taught by: Bill Laboon (laboon at cs dot pitt dot edu)

Professor's Office Hours:

  • SENSQ 6305
  • Wednesday 1:00 - 4:00 PM
  • ...or by appointment.

Class Time: Tue/Thu 9:30 AM - 11:15 AM

Room: G37 Benedum Hall

TA: Tazin Afrin (GitHub username: TBD)

Class GitHub repo: https://www.github.com/laboon/CS1530_Summer2017

Required Texts:

  • Growing Object-Oriented Software, Guided by Tests. Authors: Steve Freeman and Nat Pryce. ISBN 9780321503626

  • Code Complete (Second Edition). Author: Steve McConnell. ISBN 0790145196705

  • Online essays/articles will also be assigned.

This course provides students with a broad understanding of modern software engineering. Although it will cover theory, the emphasis is on providing practical skills in software engineering currently used in industry. To that end, it will cover project and product management, software architecture and design patterns, team communications, and other material relevant to engineering software instead of just coding it.

Grading

  • Group Project - 80%
    • Sprint 1 Deliverable - 10%
    • Sprint 2 Deliverable - 10%
    • Sprint 3 Deliverable - 15%
    • Sprint 4 Deliverable - 20%
    • Final Deliverable and Presentation - 25%
  • In-Class Exercises - 20%

It is strongly recommended that you come to class each for each lecture. Material may be presented or covered in class that is not in the reading. I also expect active participation in class (there will be various projects done in class). However, I will only take roll for the class exercise days. On these days, attendance and participation is mandatory.

The syllabus is subject to modification if circumstances dictate (e.g. a guest lecturer is unable to make the scheduled day).

The following grading scale will be used.

Score Grade
100.00-94.00 A (A+ for extraordinary work)
93.99-91.00 A-
90.99-88.00 B+
87.99-84.00 B
83.99-81.00 B-
80.99-78.00 C+
77.99-74.00 C
73.99-71.00 C-
70.99-68.00 D+
67.99-64.00 D
63.99-61.00 D-
60.99-0.00 F

All groups are expected to do their own work on the group project, but are more than welcome to collaborate and ask questions with other groups, the Internet, or other colleagues. Projects may be analyzed with the Stanford moss system to detect unauthorized collaboration between groups.

Note that there are no exams or midterms during the summer version of this course.

It is recommended you keep all of your graded assignments until final grades are posted and accepted, in order to resolve any discrepancies in grading.

Readings

Readings are listed in the syllabus.md file for each day. The instructor may not mention the reading for the next class. The onus is on you to review the syllabus and do the appropriate reading before class.

Attendance

Presence for the class exercises are REQUIRED. They will be individually re-scheduled only in the event of an emergency. If you are facing an emergency, please contact the instructor IMMEDIATELY (if it is safe to do so, of course). Failure to show up for a class exercise without clearing it first with the instructor will result in a 0 (zero) for that exam or exercise.

Group Project Details

Students will be grouped into groups of approximately 4, and will work on a project for the duration of the course. There will be several sprints, at the end of each of which the students will have a working version of their software available on GitHub, as well as documentation and other information (specified for each particular sprint).

Deliverables must be committed to GitHub by the beginning of class on the day that it is due. Late deliverables will NOT be accepted unless authorized at least 24 hours before the due date.

Programming Language Selection

All software projects for this course will be written in the Java language (version 1.8 or later). Additionally, we will be using associated tools, libraries and frameworks such as Swing, Gradle and JUnit. These will be discussed in class.

Collaborative Programming

Note that all works produced by you are your intellectual property and you may do what you want with it. However, this class is collaborative. You may need to show and share your work to other students under the direction of the instructor.

Participating in Class

Under reasonable circumstances, it is almost always better to participate in class than not. Questions and comments are invited and strongly encouraged! However, this implies raising your hand and waiting to be called upon. In dire circumstances, some waving of the hands in order to get the instructor's attention is allowed, but suboptimal. Talking out of turn or while the instructor is speaking is generally frowned upon. If it persists after a warning has been given, the instrutor may ask any offending parties to leave the room to continue their discussion elsewhere.

Disability Services Statement

The Office of Disability Resources and Services (DRS) provides a broad range of support services to assist students with disabilities. Services include, but are not limited to, tape-recorded textbooks, sign language interpreters, adaptive and transportation. Contact DRS at 412-648-7890 or 412-383-1355 (TTY) in 216 William Pitt Union or see www.drs.pitt.edu for more computer technology, Braille translation, and nonstandard exam arrangements, DRS can also assist students with accessibility to campus housing information.

Academic Integrity Statement

As members of the University of Pittsburgh community, A&S students are expected to meet the obligation to exhibit honesty and to respect the ethical standards of the University community and of their chosen field of study in carrying out academic assignments. A&S students are therefore expected to familiarize themselves with the published rules and regulations go to http://www.provost.pitt.edu/info/acguidelinespdf.pdf