SWENG 411: Principles of Software Engineering

Textbook Information

Software Engineering, Ian Sommerville, 10th Edition, Addison-Wesley, 2015, ISBN-10: 0-13-394303-8

Published Remarks

None

Hardware Requirements

Software Requirements

Proctored Exams

Course Description

This course is the cornerstone of the SE curriculum covering software engineering principles, software process models, and project management.  To gain hands-on experience in software development, students will be grouped into teams to work on a semester-long project. The project will require team members to collaborate and produce an idea proposal, problem domain analysis, system requirement analysis, and system design.  Teams will then work together to implement and test their design. Finally, at the conclusion of this course, each team will produce three deliverables: a Software Requirements Specification Document, Software Design Specification Document, and a system executable. In addition to gaining a deeper understanding of SE principles, students will also expand their teamwork, documentation, and communication skills.

The course progression and submission due dates are detailed in the course schedule. To be successful, please conform to the schedule without delay.

Prerequisite:  SWENG311

Overview

This course is designed to focus on SE principles and Object-Oriented Methodologies, with the presumption that you have already mastered one or two object-oriented programming languages (CMPSE 121, 122, SWENG 311). Of its nature, this course is writing-intensive, demanding that you document system requirements and designs in standard formats and in UML (a semi-formal language). Given that no individual has the knowledge and experience of the team as a whole, teamwork is a critical factor to becoming a successful software engineer. Hence, while working on your project, each team should split tasks wisely, seek help proactively, and share thoughts frequently.

Course Outline:

Module 1 – Orientation Module 2 – Software Process Models Module 3 – Project Management and Planning Module 4 – Agile Software Development Module 5 – Object-Oriented Modeling Basics Module 6 – Software Requirements Module 7 – Use Cases Module 8 – System Architectural Design Module 9 – From Use Cases to Object Interactions Module 10 – System Structural Design Module 11 – System Behavioral Design Module 12 – Software Design Patterns Module 13 – Software Testing Module 14 – Software Maintenance Module 15 – Project Presentation

Learning Goals

Upon completion of the course, students will:

  1. Understand key concepts related to the Software Engineering discipline;
  2. Understand the ethical issues related to software engineering;
  3. Have a working knowledge of the software development process;
  4. Have practiced using various UML diagrams to represent software artifacts;
  5. Have practiced applying OO concepts in software construction;
  6. Know key techniques for analyzing and documenting software requirements;
  7. Know key concepts and techniques for software system modeling;
  8. Understand the general principles of human-computer interface design;
  9. Know a few design patterns and know how to use them in the course project;
  10. Understand the basics of unit testing and integration testing;
  11. Know the process and key activities for project planning and management.

Course Requirements and Grading

1. Grading Policy

Grading is based on midterm exams, quizzes, lab assignments, and course projects. The following weights are assigned to the different assessed components of the course:

Category Evaluation Percentage
Midterm Exam I Individual 7%
Midterm Exam II Individual 8%
Midterm Exam III Individual 10%
Quizzes (10 modules) Individual 15%
Module Discussions (first 4 modules) Individual 5%
Module Assignments Teamwork 25%
Team Project Final Deliverables Teamwork 30%

Labs: The hands-on laboratory component concentrates mainly on the application of object-oriented techniques to design and develop software projects. Course Project The course project will require the design and development of a moderately-sized software system. The main goal is to help you gain in-depth experience with object-oriented software design and construction. You will be asked to propose project ideas early in the semester. The course project grade consists of three parts, (a) software construction (from requirements to a working system), (b) software documentation, and (c) system presentation. Your individual grade for the group project will reflect the peer evaluations that will be performed at the end of the semester (each student will be evaluated by other team members about your involvement in the production of the project deliverables).

2. Grade Assignments

Assignments are based on 100 points with a final letter grade being assigned as follows:

A A- B+ B B- C+ C D F
93-100 89-92 85-88 80-84 75-79 70-74 65-69 60-64 0-59