EASTERN MEDITERRANEAN UNIVERSITY
|COURSE CODE||CMPE 412||COURSE LEVEL||Fourth year|
|COURSE TITLE||Software Engineering||COURSE TYPE||department technical elective|
|CREDIT VALUE||(4, 1, 4) 4||ECTS VALUE|| 6|
|PREREQUISITES||CMPE 211||COREQUISITES|| |
|DURATION OF COURSE||One semester||Semester and year||Fall ||2018/2019|
|WEB LINK|| https://staff.emu.edu.tr/isikaybay/en/teaching/cmpe412|
| ||Name ||e-mail||Office||Telephone|
|Instructor||Prof. Dr. Işık AYBAY ||email@example.com||Cmpe-213||1484|
|Assistant||Begüm Koru (design studio)|| || |
The software life cycle and the phases in software development: Project scheduling, feasibility study, analysis, specification, design, implementation, testing, quality assurance, documentation, maintenance. Management issues: Planning, organization, control. Also included are formal specification techniques, structured programming, modular system design and other current issues. (Prerequisite: CMPE 218)
AIMS & OBJECTIVES
Teaching the basic concepts of software engineering with specific emphasis on the practical issues involved in software project management through the use of a one-semester design project.
GENERAL LEARNING OUTCOMES (COMPETENCES)
On successful completion of this course, all students will have developed knowledge and understanding of:
- Software engineering
Software life cycle, effort, time and cost estimation, requirements specification, modular design, testing
- Project management and planning
On successful completion of this course, all students will have developed their skills in:
- computer programming
- database design
- project management
On successful completion of this course, all students will have developed their appreciation of, and respect for values and attitudes to:
- software engineering projects
|75% - 84%|
|65% - 74%|
|50% - 64%|
|40% - 49%|
|39% or less|
|Not attending exams, classes, not submitting homeworks and assignments|
RELATIONSHIP WITH OTHER COURSES
Prerequisite for this course is CMPE-211, which teaches object-oriented programming. CMPE-354 course is the first course students learn database systems, therefore it is strongly recommended.
LEARNING -TEACHING METHODS
Lectures covering the text book material, basic software engineering project management concepts, weekly design studio meetings discussing the term project, and exams assessing student success.
A group term project, which is designing a software system for a current problem in the software market. The project includes a proposal, an intermediate report and presentation, and a final presentation and report. Design studio meetings are used to give information to students about the project management process and to assess the development towards the final product.
METHOD OF ASSESSMENT
Midterm Exam: 30%, Term project: 30%, Final exam:40%
Compulsory for design studio meetings.
Pressman, Software Engineering, 8th ed., McGraw-Hill, 2015.
Sommerville, Software Engineering, 10th ed., Pearson, 2016.
|2||Software development process|
|3||System requirements, system models|
|4||Project management – Problem, Process, People|
|5||Project planning – software requirements|
|6||Project metrics – LOC, FP , size and cost estimation|
|7||Term project – Intermediate presentations|
|9||Architectural design of software|
|12||Software quality management|
|14||Term project - Final presentations (1)|
|15||Term project - Final presentations (2)|
ACADEMIC HONESTY – PLAGIARISM
Cheating is copying from others or providing information, written or oral, to others. Plagiarism is copying without acknowledgement from other people's work. According to university by laws cheating and plagiarism are serious offences punishable with disciplinary action ranging from simple failure from the exam or project, to more serious action (letter of official warning suspension from the university for up to one semester). Disciplinary action is written in student records and may appear in student transcripts.
ANY OTHER RELEVANT INFORMATION