1. Shari Lawrence Pfleeger and Joanne M. Atlee, Software Engineering Theory and Practice, 3rd Edition, Prentice-Hall, 2006. ISBN: 0-13-146913-4
2. Steve McConnell, Professional Software Development: Shorter Schedules, Better Projects, Superior Products, Enhanced Careers, Addison-Wesley, August 2003. ISBN: 0321193679.

• Roger S Pressman, Software Engineering: A Practitioner's Approach, 6th edition, McGraw Hill, 2005, ISBN: 0072853182
• Ian Sommerville, Software Engineering, 7th Edition, Addison-Wesley, ISBN 00321210263. This is one of the top two undergraduate software engineering texts. If you find Pressman difficult to understand, you may want to read the same material in Sommerville.
• Carlo Ghezzi, Mehdi Jazayeri, Dino Mandrioli, Fundamentals of Software Engineering, Second Edition, Prentice Hall, ISBN 0-13-305699-6. Another perspective on the discipline of software engineering.

• An understanding of the breadth and impact of the discipline of software engineering.
• A general understanding of software process including software lifecycle models such as the waterfall, spiral, and evolutionary models.
• An exposure to the role of project management including planning, control, organization, risk management, etc.
• An understanding of software requirements including requirements analysis, definition, specification and review.
• An exposure to software architectural styles.
• An understanding of the fundamentals of software design using UML as a notation including design evaluation and validation.
• An understanding of implementation issues including cohesion and coupling, modularity, coding standards, etc.
• An understanding of approaches to verification and validation including reviews, static analysis, and various testing approaches.
• An understanding of the issues involved in maintaining a large software system.
• An understanding of the role of documentation.

No late projects or homeworks are accepted. However, you are alloted 2 "free late days". These days may be used if you would like to delay handing in a project or homework late without penalty. Late days can only be used in increments of 24 hours (3 minutes late or 23 hours late still counts as using 1 late day). There is no bonus for unused late days. When applied to a project, late days will be incurred for all team members.

All cell phones must be turned off during class time, not just set on vibrate mode.

CPSC-240 Principles of Software Engineering is supported by a Blackboard site. The Blackboard site will be used for occasional quizzes and for posting grades. You are responsible for reading all announcements and postings on the bulletin board.

The Intellectual Honesty section of Trinity College's Student Handbook states that "students are expected to abide by the highest standards of intellectual honesty in all academic exercises." Note that turning in work that was performed partially or completely by someone else qualifies as academic dishonesty. Such academic dishonesty will not be tolerated and may result in severe consequences. Please refer to the Intellectual Honesty section of the Student Handbook for more details.