CP3110 - Fundamentals of Software Engineering (3 Units)

IMPORTANT: Click Here for Project information.

Your Marks for Feasibility study, SRS, Plan document and tutorials.

Teaching Staff

Dr. Krishna Rao MADALA

Contact Hours

Tutorial participation carries 10% in assessment. A set of questions will be released every Friday, you should hand over your answers (need not be perfect solutions, but it should show that you apply yourself to the task) to me at the beginning of the Tutorial in the next week. My solutions will be posted on the web after the tutorial.

Room MT103 has been booked for us until 9pm (just in case we need it any time), but we shall generally finish by 8pm. There will be a break of 10 minutes in the middle, during which we distract ourselves solving a small puzzle or discussing cricket (who should succeed Steve Waugh as next Test captain, Warne, Ponting, Gilchrist?) or Tennis (Can Mark Philippoussis win a few grandslams and become No. 1 just like Pat Rafter and Hewitt?).

Text Book

• Textbook:
  Ian Sommerville, Software Engineering (Sixth Edition), Addison-Wesley, 2001.
• Reference Books:
  
  1. Roger Pressman, Software Engineering: a practitioner's approach (Fifth Edition), McGraw Hill, 2001.
  2. James F. Peters and Witold Pedrycz, Software Engineering: an engineering approach, John-Wiely, 2000.
  3. Stephen R. Schach, Object-Oriented and Classical Software Engineering: (Fifth Edition), McGraw Hill, 2002.
  4. Eric Braude, Software Engineering: an object-oriented perspective, John-Wiely, 2001.
  If two (or more) students study together, it advisable that one buys Sommerville and the other buys Pressman. You are encouraged to look at Pressman's textbook webpage: Software Engineering: A Practitioners Approach, 5th Edition for a wealth of student resources.

Content, Lecture notes and Tutorials

• Contents: We plan to cover the whole book except Chapters 11, 13, 24 and 28 of the textbook.
• Lecture notes will be made available during the semester after each class.
• Tutorials (and solutions) will be made available during the semester.

Assessment

To pass, you should get at least a total of 50 marks (out of 100).
To get C, you should get at least a total of 65 marks (out of 100) and at least 30 marks in the exam.
To get D, you should get at least a total of 75 marks (out of 100) and at least 39 marks in the exam.
To get HD, you should get at least a total of 85 marks (out of 100).

Pre-requisites

Learning Objectives

1. understand the importance of software engineering to computer science and the most important general approaches to structuring the software production process;
2. analyse the requirements for a software system and produce a software design (including user interface) from requirements;
3. use formal specification techniques to aid the specification process;
4. appreciate the benefits and difficulties of performing software engineering in a group, including the development of requirements and design documents and interaction with a client;
5. understand how reliability, reusability, verification and validation are vital concerns for any software engineering effort;
6. understand the important issues for managing and supporting the software engineering process at both the group and individual level.