Professional Documents
Culture Documents
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:
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:
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
Webs
INSTRUCTIONAL METHODS:
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