COURSE SYLLABUS

COURSE INFORMATION: Course Title: Course MEU Number: Course Date: Course Location: CLASS HOURS: COURSE PAGE: NAME: OFFICE: OFFICE HOURS: OFFICE PHONE: E-MAIL ADDRESS: WEB PAGE: SOFTWARE ENGINEERING 0402521 FALL, 2011 - Second Semester Building B, Room 111 05:00-08:00 http://www.

INSTRUCTOR INFORMATION:

Dr. Hazim A. FARHAN

Building C, Room 422 04:00-05:00 Monday,

00000
hfarhan@meu.edu.jo (school) info@meu.edu

COURSE DESCRIPTION:

This is a course to introduce theory and practice for software engineering in terms of software development that includes software requirement specifications, design, implementation, and testing. Students will undertake a team-based project. A team-based project working in small groups addresses requirements analysis and specification, software architecture, detailed design, implementation, and testing through a relatively complex software system. The Unified Modeling Language (UML) is used to specify requirements and design the system.

COURSE OBJECTIVES:

After completing the course, the students will be able to:

1. Understand the basic concepts of project management including scheduling, risk analysis, and cost estimation 2. Understand the differences among software development process models 3. Use the Unified Modeling Language including the use case model, class model and collaboration model. 4. Identify functional and non-functional requirements for software systems 5. Specify software requirements using the use case model 6. Analyze static and dynamic aspects of software requirements using the class model and collaboration model 7. Design software architecture in terms of components and interactions between the components 8. Understand the differences among basic software architectural patterns 9. Make detailed design including operation interface design and relational database schema derivation 10. Make differences between software inspection and testing in Validation and Verification 11. Understand how to make test cases for software testing 12. Know the assurance approaches for critical systems 13. Understand maintenance of software systems through software reengineering 14. introduce the quality management process, key quality management

activities, role of standards used in assessing software quality management,

TEXT BOOK AND REFERENCES

TEXT BOOK 1."Software Engineering", By Ian Sommerville, Addison Wesley, 9th Ed., 2010. 2. "Object-Oriented and Classical Software Engineering", By Stephen R. Schach, WCB/McGraw-Hill, 7th Ed, 2006. REFERENCES

Books

1. "Using UML: Software Engineering with Objects and Components" by

Stevens P. and Pooley, R., Addison-Wesley, (Updated edition, 2006).

2. "The Unified Modelling Language User Guide", By G Booch, J Rumbaugh, 3.

and I Jacobson, Addison Wesley, 2005 "Software Engineering: A Practitioner's Approach", By RS Pressman, McGraw-Hill, 2003.

Webs

INSTRUCTIONAL METHODS:

This course is taught using a variety of instructional methods including

lecture( using PPT slides on data show), class discussions, small group work, project creation and presentations. tutorials, and problem solving.

GRADING:

Coursework will be weighted as follows: 1. First Term Exam 30% 2. Project 10% 3. Presentation 10% 4. Quizzes 5% 5. Attendance 5% 6. Final exam 40% 100% Total Mark:

COURSE SCHEDULE The weekly course schedule helps keep the course on track throughout a semester, help the instructor from "running out of time" at the end of a course, enable students to always see what is coming up or what they will miss if absent, and evidences good planning and organization. It also saves the instructor significant planning time during the course. The schedule should not be so tight, though, that it is difficult to keep up with it or that it makes the course rigid. Until a course has been taught, a schedule is probably preferable to a weekly schedule.

No. DATE 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16

TOPIC/ACTIVITY

Chap.

14/2

Introduction to Software Engineering Software Processes Software Project Management Software Requirements System Models Software Design From Modules to Object Object-Oriented Design Mid-Term Exam Rapid Software Development and Prototyping Verification and Validation Software Testing Software Evolution /Maintenance and System re-engineering Quality Management Project Discussions and Student Presentation Final Exam

1 4 5 6,7 8 11 7(2) 14,13(2) 17 22,24 23 21 27