Course Outline

Department of Computing Science

COMP 3520 3 Software engineering (3,1,0) Winter, 2014 Instructor: Mridula Sharma Office: HL 407 Office Hours: As posted on office door Phone/Voice Mail: (604) 723-1124 E-Mail: msharma@tru.ca

Calendar /Course Description This course introduces students to large-scale software development including software design, implementation and maintenance. Topics included are: software life cycle, design techniques, psychology and economics of software testing, organization and management of modular inter-communication, software engineering tools, project management including resource estimation, team organization and review. The students will apply these techniques to develop a software project in a software engineering project course.

Course/Learning Outcomes To learn about methods for developing large, multi-module software projects using the software engineering approach. Specifically to learn about: the design and implementation of large, multimodule program systems, software life cycle, design tools, object oriented design, intermodule communication, project management, user interface design, and testing. Prerequisites Note: A prerequisite course must be completed with a grade of C or better for unconditional acceptance into the succeeding course. As stated in the Calendar: Please note that good presentation skills and technical writing skills in the English language are extremely important in software engineering because of the preparation of documents that is required. Corequisites None

Recommended Texts/Materials Text: Sommerville Ian, Software Engineering, 9th Edition, Addison Wesley; ISBN-10: 0137035152

Other References: Schach, Stephen, Object-Oriented and Classical Software Engineering, Eight Edition, ISBN-13: 9780073376189 Pooley, Rob and Perdita Stevens Using UML Software Engineering with Objects and Components Booch Grady Object Oriented Analysis and Design with Applications, Brooks, The Mythical Man Month. de Champeaux, Object Oriented Systems Development, QA 76.64.D43, 1993, Dennis. Ghezzi, C., M. Jazayeri, D. Mandrioli, Fundamentals of Software Engineering, Prentice-Hall, 1991. Ince, Darrel, Object Oriented Software Engineering, QA 76.64.I53. Jacobson, Ivar Object-oriented Software Engineering-A Use Case Driven Approach. Kernighan and Plauger, The Elements of Programming Style, MacGraw-Hill, 1978. Moore, James, Software Engineering Standards. Mynatt, B., Software Engineering With Student Project Guidance, Prentice-Hall, 1990. Pressman, Software Engineering A Practitioner's Approach, McGraw-Hill, 1982. Sobell, M. G. Mark G. Sobell A Practical Guide to the Unix System. Strunk and White, Elements of Style, MacMillan, 1972. Material Required N/A Student Evaluation Projects and Assignments (Including marks for participation in class) ................... Midterm ............................................................................................................................ Class Presentations ........................................................................................................... Final Exam ......................................................................................................................... 25% 25% 5% 45%

Note: To pass the course you must achieve a minimum of 50% overall. In addition, you must achieve at least 50% on the supervised work. Evaluation of Project Work where a student is working as part of a Team As a member of a software development team, your teammates are depending on you to complete your obligations in a timely manner. It is also expected that students will behave cooperatively with their project development teammates. Anyone who fails to do so by not attending team meetings or not working on assigned project elements will be removed from the team, and fail that portion of the grade.

Delivery of Course Material All material for which an electronic version exists will be posted electronically.

Exams All supervised work must be written at the time scheduled. Each missed supervised work, will receive a 0 mark unless a medical note from a doctor is provided. Attendance Policy Attendance will be taken. In addition, every student is responsible for everything covered in class as well as assigned readings in the text. Assignments (including presentations and projects)

COMP 3520

Introduction to Software Engineering

Page 2 of 3

 The best way to learn the material is by doing assignments. You will be working in small groups since the best way to understand the subtleties of the assignments is to argue about the answers. Both of the partners should look at the problems independently. The team should not just divide the work into two. Unless you learn how to solve problems, you will get burned on the exams. The group system relies upon a certain maturity amongst its members. A late assignment counts as a missed assignment and is generally not accepted unless a medical note from a doctor is provided. If a due date needs to be extended it will be done for the whole class and not for individuals. Class Presentations Copies of transparencies (excluding talk notes) must be handed out to students and the instructor before the beginning of the class. All presentations must be professional. Academic honesty All assessments given for the computing science courses are governed by the academic honesty policy of both TRU and the Computing Science Department. Academic dishonesty is a serious offense. All work submitted must be your own or that of your assigned team. Preliminary discussions may be held with other students but the work produced finally must be your own or that of your assigned team. Jointly produced work, with the exception of designated team work, will result in a zero for that assignment for all students involved in the joint work and may result in loss of a letter grade for the course. The student may also be expelled from the University. Syllabus Module 01 02 03 04 05 06 07 08 09 10 11 12 13 Description Introduction Software processes Agile software development Requirements engineering System modeling Architectural design Design and Implementation Software testing Software Evolution Socio-technical Systems Software Reuse Component-based Software Engineering Distributed Software Engineering Total Chapter 1 2 3 4 5 6 7 8 9 10 16 17 18 13 weeks

Special Activities Part of the training involves learning to work as teams. If an assignment is a team assignment, then teams rather than individuals must do the work. The instructor reserves the right to form some or all project teams and to move members from one team to another (including creating a new project for some students to work on). Use of Technology The instructor website may be used to assist in course delivery. Students are expected to learn to obtain instructional material and assignments electronically.

COMP 3520

Introduction to Software Engineering

Page 3 of 3