EPOKA UNIVERSITY
FACULTY OF ECONOMICS AND ADMINISTRATIVE SCIENCES
DEPARTMENT OF BUSINESS ADMINISTRATION
COURSE SYLLABUS
2022-2023 ACADEMIC YEAR
COURSE INFORMATIONCourse Title: SOFTWARE ENGINEERING |
Code | Course Type | Regular Semester | Theory | Practice | Lab | Credits | ECTS |
---|---|---|---|---|---|---|---|
CEN 302 | B | 6 | 2 | 0 | 2 | 3 | 6 |
Academic staff member responsible for the design of the course syllabus (name, surname, academic title/scientific degree, email address and signature) | NA |
Main Course Lecturer (name, surname, academic title/scientific degree, email address and signature) and Office Hours: | Dr. Aida Bitri abitri@epoka.edu.al , Monday 14:30-15:30, Tuesday 14:30-15:30, Wednesday 11:30-13:30. |
Second Course Lecturer(s) (name, surname, academic title/scientific degree, email address and signature) and Office Hours: | M.Sc. Enesh Orazova eorazova@epoka.edu.al , M.Sc. Edison Reshketa ereshketa@epoka.edu.al |
Teaching Assistant(s) and Office Hours: | NA |
Language: | English |
Compulsory/Elective: | Compulsory |
Study program: (the study for which this course is offered) | Bachelor in Business Informatics (3 years) |
Classroom and Meeting Time: | Tuesday 8:45-10:30 , E/213. |
Code of Ethics: |
Code of Ethics of EPOKA University Regulation of EPOKA University "On Student Discipline" |
Attendance Requirement: | Yes/ 75 % |
Course Description: | This course presents contemporary issues related to the field of software engineering. It deeply examines the software life cycle models, including phases of requirements specification, design, development, test, and maintain. Object-oriented design methods (UML) and practices, their application to the development of computer-based systems. Particular emphasis is on a team project in which a group of students implement a system from its specification. |
Course Objectives: | This course introduces the concepts, tools, and techniques of Software Engineering. It emphasizes the development of reliable and maintainable software via system requirements and specifications, software analysis, and design methodologies including object-oriented design, implementation, integration and testing, software project management, and life-cycle documentation. Students undertake a semester group mini-project as a major part of the course. |
BASIC CONCEPTS OF THE COURSE
|
1 | Software Engineering |
2 | Software process |
3 | Software development life cycle |
4 | Object-oriented modeling |
5 | Software design and modeling |
6 | architectural modeling |
7 | Testing and Software maintenance |
8 | Software evolution |
9 | Project Management |
10 | Team work |
COURSE OUTLINE
|
Week | Topics |
1 | Introduction to Software Engineering. The objectives of this chapter are to introduce software engineering and to provide a framework for understanding the rest of the lecures. Chapter I. |
2 | SDLC and Software Processes. Waterfall Model & Boehm Spiral. The objective of this chapter is to introduce students to the idea of a software process—a coherent set of activities for software production. Chapter 2. |
3 | Agile Development. Extreme Programming & Scrum software process. The objective of this chapter is to introduce sstudents to agile software development methodsChapter 3. |
4 | Requirements Engineering. Understanding of functional and non functional requirements. The objective of this chapter is to introduce software requirements and to discuss the processes involved in discovering and documenting these requirements. Chapter 4. |
5 | Requirements Modeling. Composition of the requirements document. The objective of this chapter is to introduce software requirements and to discuss the processes involved in discovering and documenting these requirements. Chapter 4. |
6 | System Modeling. Model types. The aim of this chapter is to introduce some types of system model that may be developed as part of the requirements engineering and system design processes.Chapter 5. |
7 | System Modeling. Model Driven Engineering. The aim of this chapter is to introduce some types of system model that may be developed as part of the requirements engineering and system design processes. Chapter 5, 6. |
8 | Midterm exam |
9 | Architectural Design. The objective of this chapter is to introduce the concepts of software architecture and architectural design. Chapter 6 |
10 | Overview of OOAD with UML. The Unified Modeling Language (UML) used for model driven Engineering. The objective of this chapter is to introduce the concepts of software architecture and architectural design. Chapter 6,7. |
11 | Implementation. Understanding of activities related to Test-driven software engineering. The objectives of this chapter are to introduce object-oriented software design using the UML and highlight important implementation concerns. Chapter 7. |
12 | Software Testing. System testing & component testing.The objective of this chapter is to introduce software testing and software testing processes. Chapter 8. |
13 | Maintenance and Reengineering. Connecting software lifecycle with software evolution. The objectives of this chapter are to explain why software evolution is an important part of software engineering and to describe software evolution processes. Chapter 9. |
14 | Project Presentations |
Prerequisite(s): | - |
Textbook(s): | Lecture slides in PPT format Software Engineering, Ian, Sommerville, Pearson, 2021 |
Additional Literature: | 1. Essentials of Software Engineering, 5th Edition, Frank Tsui; Orlando Karam; Barbara Bernal,Jones & Bartlett Learning, 2022 2. Beginning Software Engineering, Rod Stephens, Wiley, 2022 3. Software Engineering: A practitioner’s Approach, 8th Edition by Roger Pressman. 4. Software Engineering: A Methodical Approach, Elvis C. Towle Jr., Bradford A. Foster, CRC Press, 2021 |
Laboratory Work: | Yes |
Computer Usage: | Yes |
Others: | No |
COURSE LEARNING OUTCOMES
|
1 | Students should be able to identify formal requirement specification document. |
2 | Students should be able to analyze the requirements of a software project. |
3 | Students should be able to build a software from UML diagrams. |
4 | Students should be able to build a software from requirements and design diagrams. |
5 | Students should be able to Understand the importance of Risk management and Configuration Management. |
6 | Students should be able to test the code of their project, creation of test cases, and Test plan, etc. |
7 | Students should be able to understand the lifecycle development of a software endeavor. |
8 | Students should be aware of the variety of existing software processes. |
9 | Students should be able to Evaluate the Usability of an Integrated Development Environment. |
COURSE CONTRIBUTION TO... PROGRAM COMPETENCIES
(Blank : no contribution, 1: least contribution ... 5: highest contribution) |
No | Program Competencies | Cont. |
Bachelor in Business Informatics (3 years) Program | ||
1 | Identify activities, tasks, and skills in management, marketing, accounting, finance, and economics. | 4 |
2 | Apply key theories to practical problems within the global business context. | 4 |
3 | Demonstrate ethical, social, and legal responsibilities in organizations. | 3 |
4 | Develop an open minded-attitude through continuous learning and team-work. | 5 |
5 | Integrate different skills and approaches to be used in decision making and data management. | 4 |
6 | Combine computer skills with managerial skills, in the analysis of large amounts of data. | 5 |
7 | Provide solutions to complex information technology problems. | 5 |
8 | Recognize, analyze, and suggest various types of information-communication systems/services that are encountered in everyday life and in the business world. | 5 |
COURSE EVALUATION METHOD
|
Method | Quantity | Percentage |
Midterm Exam(s) |
1
|
30
|
Project |
1
|
30
|
Final Exam |
1
|
40
|
Total Percent: | 100% |
ECTS (ALLOCATED BASED ON STUDENT WORKLOAD)
|
Activities | Quantity | Duration(Hours) | Total Workload(Hours) |
Course Duration (Including the exam week: 16x Total course hours) | 16 | 4 | 64 |
Hours for off-the-classroom study (Pre-study, practice) | 16 | 3 | 48 |
Mid-terms | 1 | 10 | 10 |
Assignments | 0 | ||
Final examination | 1 | 20 | 20 |
Other | 1 | 8 | 8 |
Total Work Load:
|
150 | ||
Total Work Load/25(h):
|
6 | ||
ECTS Credit of the Course:
|
6 |
CONCLUDING REMARKS BY THE COURSE LECTURER
|
Students caught with plagiarism or receive a misbehavior report during lectures, labs, and exams will be automatically graded 0 points. |