Syllabus

Description

Software engineering is a very broad field. It encompase virtual everything a person might want to know in order to develop software - software that is correct, on time, and on budget. Most other computer science courses emphasize the technical foundations of software development, such as programming, algorithms, data structures, languages, etc.

This course focusses on the pragmatic aspects, such as requirements analysis, cost estimation, design, team organization, quality control, configuration management, verification, testing, and maintenance. Students work in teams on projects for real clients. This work includes a feasibility study, requirements analysis, object-oriented design, implementation, testing, and delivery to the client. Additional topics covered in lectures include professionalism, project management, and the legal framework for software development.

This course is compiled from documents of MIT OpenCourseWare, the Connexion project of Rice University, and from free online courses and documents such as

(External Link) ,

(External Link) ,

(External Link) ,

(External Link) ,

(External Link) ,

(External Link) ,

(External Link) ,

(External Link) ,

(External Link) ,

and etc…

We have arranged their contents to create a complete course. We hope it will be useful to study Software Engineering.

Course objectives

Theory, the students have

• got an overview of software engineering,
• got a survey of the history, ethics and risks of software engineering,
• understood various approaches and methodologies used in different phases of software development lifecycle, including requirements analysis and pecification, software design, software construction, software maintenance, and software process.

Practice

• students will execute a real software engineering project,
• students can apply that knowledge in their future research and practice.

Prerequisites

The formal prerequisites for this course are Programming Languages (C/C++, Perl, Java, .Net,…), Data Structures and Algorithms, and Database Management Systems.

The following are the specific capabilities you will need from the prerequisite courses:

• experience with the software development process
• skill in independent programming and problem solving
• skill using an object oriented language
• mathematical maturity, including at least:
  • methods of proof: induction, cases
  • elementary formal logic: working with formulae using logical connectives, quantifiers, modus ponens, implication, satisfaction
• finite state machines: state diagrams, state tables, reachability
• formal languages: BNF, regular expressions

Organization

Class sessions will be a combination of lecture and seminar formats. We'll cover the course's primary topics in these sessions, with reading and homework assigments that provide opportunities to gain a deeper understanding of the underlying issues and techniques of software engineering. Actual labs and software development projects will provide a hands-on approach to exploring these topics throughout the semester. Given that this is a 3 credit course, it is expected that you will spend an average of 10 hours per week (including in-class and lab time) on the course and related material for the duration of the semester.

Readings

Here are some general books on software engineering:

• Sommerville, Ian, Software Engineering, Eighth Edition, Addison-Wesley, 2007.
• Frederick P. Brooks, Jr., The Mythical Man Month, Addison-Wesley, 1972.
• Pfleeger, Shari Lawrence, Software Engineering Theory and Practice, second edition, Prentice- Hall 2001.
• Bernd Bruegge and Allen H. Dutoit, Object-Oriented Software Engineering Using UML, Patterns and Java, Second Edition, Prentice Hall, 2004.

Grading plan

Since software engineering is a broad subject matter, mastery of the topic as covered by the scope of our course can be manifested in a variety of ways. Your grade in the course will be based on your achievement of the course objectives as demonstrated in your homework assigments, programming deliveries, and participation in class discussions.

Course component grading weight :

• Exercises: 40%
• Group Software Project: 50%
• Participation: 10%

Schedule

Suggestions for success

• Make sure you know what you want to get out of the course before you get very far into it; there are lots of directions to go in, and having a focus will help to inspire you
• Update your journal often; use it as a tool to develop / explore ideas and track your progress
• Remember that the larger software development project is something to be considered throughout the semester; don't wait until the end!
• Raise concerns early; if an assignment or milestone doesn't seem feasible, say so as soon as you can
• "Work hard, learn lots, stay excited, and have fun." --Ray Ontko