CS-615 Software Engineering

• Course CS 615
• Purpose of Course
• Objectives
• Course notes and course books
• Course structure
• Assessment
  • 1. Quizes
  • 2. Final examination
  • 3. Project
• Study Material

Course CS 615

Instructor: Dr. S M Aquil Burney

Purpose of Course

To provide an overview of techniques and methodologies for applied software engineering.

Objectives

After completing this course the student will be able to:

• Describe the main requirements for software engineering.
• Be familiar with the variables affecting programming as human performance.
• Be familiar with interviewing and other information gathering techniques.
• Understand the importance of human factors and interface design.
• Understand the importance of documentation and manuals, their structure and production.
• Understand the measurement of the complexity of systems and software quality assurance.
• Be familiar with object oriented development in software engineering, and the issues in choosing class libraries.
• Be familiar with object oriented design.
• Understand the main privacy, security and other legal issues in software development.
• Understand the importance of social, ethical and professional issues in software development.
• Be familiar with the Software Engineering Institute software process improvement.
• Be familiar with the Software Engineering Institute capability maturity model.
• Be familiar with some techniques for cost and effort estimation.
• Design, manage and implement a medium sized project in a large group as a supplier.
• Assess the design, management and implementation of a medium sized project in a large group as customer.
• Be aware of the difficulties and necessity of keeping records in developing systems.

Course notes and course books:

Course notes will be on the World-Wide Web at http://www.cpsc.ucalgary.ca/~mildred/451

You are advised to use Netscape to view these documents.

There will be no compulsory text book, but the following are highly recommended:

• Software Engineering: A Practitioner's Approach by R.S. Pressman, McGraw-Hill (3rd ed.), 1992.
• Software Engineering by Ian Sommerville, Addison-Wesley (4th ed.), 1992.
• Software Engineering: Methods and Management by A. von Mayrhauser, Academic Press, 1990.
• Foundations of Business Systems by Andersen Consulting, Dryden Press, 1989.
• Managing the Software Process by W.S. Humphrey, Addison-Wesley, 1990.
• Making Software Engineering Happen by R.S. Pressman, Prentice Hall, 1988.
• Controlling Software Projects by T. de Marco, Yourdon Press, 1982.
• Software Design by D. Budgen, Addison-Wesley, 1993/4.
• Object Oriented Design With Applications by Grady Booch, Benjamin/Cummings, 1991.
• Using the Booch Method by Iseult White, Benjamin/Cummings, 1994.

Course structure

In order to cover the basic issues and techniques, and to understand future directions there will be two main parts to the course:

1. Techniques in software engineering: covers some of the techniques currently in use in organizations;

2. Large group project: involves the carrying through of a project from specification through implementation and testing, and also the evaluation of another group's project.

Assessment

This is in two parts. All two parts must be passed to achieve a pass in the course. Part A is theory, worth a total of 60%. Part B project, worth a total of 40%.

1. Quizes

This will be 1 hour in class time . It will cover any topic given by teacher of the course.

2. Final examination

This will be 3 hours in end of semister. It will cover material from week 1 to last week of the course.

3. Project

You will be assigned to a group of about 10-12 students. Each group will prepare an informal requirements document for the project (subject to be provided) and be responsible for its evaluation and criticism as it progresses.

On Line Study Material

Software Engineering Life Cycle