 |
General Information:
Course syllabus
Course: 2h/week
Lab/project work: 1h/week = 2h/2weeks
Credit points: 5
Laboratory and Project:
Andrei Mihai Moisei andrei.moisei@outlook.com
Prerequisites:
"Formal Models in Software Engineering", "Programming Paradigms" and "Principles of Software Engineering" courses
Grading and workload
Our grade in the course will be earned / calculated as follows:
- Homework and frequency(c/l/p) 20%+10%
- Project 20%
- Final exam 50%
Homeworks will be given roughly every week or two, and will each consist of a small number of problems. For the final project, you can pick any topic you want for further study. Your project has to involve implementing an application with the methods presented at the course. In all cases, the end product will be a written report and a software delivery. Grades may also be adjusted upward slightly based on regular, positive contributions to class discussions.
Project Policy.
1.The projects cover the whole life cycle of software products development: analysis, design, and coding. The result of the project is a real software product. 2.The course lectures and homeworks provide necessary guidance for project realization.
2.Project submissions must not include external materials (e.g., web downloads).
3. The project must be turned in on the due date. Late projects are not accepted for any reason and will receive a zero mark. 4.The project is an individual research work. 5. The projects will require substantial time commitment. We strongly recommend that students begin working on assignments early. 5. Admission to final examination for only projects that are evaluated with at least 5 .
Guidelines to Projects
1. At the beginning of the semester a list of project topics is made available at the web. Each student reports his/her preferred choice for a topic and the list of their submissions will be published in early March.
2. Throughout the semester, students will be responsible for development of a project.
3. The project report is submitted in May. On the profs' request the student may rewrite the report in late May.
4. In the last two weeks of the semester the students are to give a 15 minutes presentation of the project. The presentation is a separate requirement for passing the exam in this subject and part of the grading of the project work.
We expect that effort spent will help the student to gain a thorough understanding of software project development.
Examination Policy
The comprehensive exam consists of a written answer to a quiz and a closed-book, two hours test consisting in analysis, design and implementation of a small application.
Lecture notes: Please, look at the course notes published in the Lecture Schedule column of this page
Textbooks:
The Software Process
1. R.S.Pressman, Software Engineering: A Practitioner's Approach, 6/e, McGraw-Hill, 2004.
2. L.D.Serbanati, Integrating Tools for Software Development, Yourdon Press Computing Series, Prentice Hall, 1992.
Object Oriented Methodologies
3. M. Fowler, UML Distilled: A Brief Guide to the Standard Object Modeling Language, 3/e, Addison-Wesley, 2003.
4. C. Larman, Applying UML and Patterns: An Introduction to Object-Oriented Analysis and Design and Iterative Development, 3/e, Prentice Hall, 2004.
|
|
Very important!!!
How working at homework and project packages
All students are warmly invited to attend the course lectures and read the lecture notes because working homework assignments requires knowledge only covered by the course. The lab will never replace the course lectures or resume the knowledge transmitted during the course lectures. It is used to:
-verify current homework solving,
-correct errors or defaults in homeworks, and propose alternative or better ways to solve the problem,
-verify and evaluate students’ knowledge of specific facts or concepts with focused questions, and
-validate delivery of current workpackage of the assigned project.
Schedule of the Laboratory Topics and Homework
The lab assignments will require knowledge of materials covered by the course lectures and will follow the phased development of a case study project.
Here is the case study project description.
A link to the homework assignment and the corresponding topic will be released for each 4 hour-laboratory session.
Lab.# Week |
Homework Link & Topic |
Lab #1
Thu, 31 Mar/ 6 Apr
18h-20h
|
Systems Engineering Methodology
Homework #1 HW1
|
Lab #2
Thu, 14 Apr
18h-20h
CJ202
|
Enterprise-Wide Information System Methodologies
Homework #2:
HW2
Homework #2bis:
HW2-BPMN
A BPMN Tutorial
Drawio, a CASE tool to be used for BPMN diagram: |
Lab #3
Thu, 21 April
18h-20h
CJ202
|
Introduction to Software Engineering
Homework #3 HW3
|
Lab #4
Thu, 28April 18h-20h
CJ202
|
Structured Methodology
Homework #4.1
pdf
|
Lab #5
Thu 5 May
18h-20h
CJ202 |
Structured Methodology
Homework #4.2 pdf |
Lab #6
Thu 19 May
18h-20h
CJ202
|
Object-Oriented Methodology
Homework #5
pdf
|
Lab #7
Thu, 2 June
18h-20h
CJ202
|
Final Project delivery and defence
|
List of project topics
#Project |
Mini-Project Name |
# 1 |
|
# 2 |
|
# 3 |
|
# 4 |
|
# 5 |
|
# 6 |
|
# 7 |
|
# 8 |
|
Mini-Project Schedule
Date |
Work Package |
Lab #3
Thu, 21 Apr
18h-20h
CJ202
|
Deadline WP1: Systems Engineering Methodology
|
Lab #4
Thu,28Apr
18h-20h
CJ202
|
Deadline
WP2: Enterprise Wide Methodology
|
Lab #5
Thu,5 May
18h-20h on line
|
Deadline WP3: Structured Methodology
|
Lab #6
Thu, 19 May
18h-20h
|
Deadline WP4: Object Oriented Methodology
|
Lab #7
Thu, 2 June
18h-20h
|
Final Project defence
|
|
|
|
|
Lecture Schedule
Date/Time |
Lesson Topic/Room |
Thu, 3 Mar
16h - 20h online |
Part I. Systems Engineering Methodologies
- Introduction to Systems Engineering
- From System Requirements to System Architecture
Lecture Notes. Part 1
|
Thu, 10 Mar
16h - 20h online
|
Part II. Enterprise-wide Methodologies
- Enterprise Engineering
- Information Engineering
- Business Engineering
|
Thu,17 Mar
16h - 20h
online |
|
Thu, 18 Mar
14h - 16h
online
|
Part III. Introduction to Software Engineering
-Software Engineering
-Software Process Models
Lecture Notes. Part 3
|
Thu, 24 Mar
16h - 20h
online
|
Part IV. Structured Software Methodology
- Structured life cycle model
- Tools for the Structured Methodology
- Structured Analysis
|
Thu, 31 Mar
16h - 18h
online
|
- Structured Analysis
|
Fri, 1 Apr
14h - 16h
online
|
|
Thu, 7 Apr
16h - 18h CJ202
|
- The Unified Process
- Requirements Analysis
- Domain Analysis
|
Thu, 14 April
16h - 18h CJ202
|
- Behavioral Modeling
- Architectural Design
- Object Design
- Dynamicity Model
|
Thu, 21 April
16h - 18h
online
|
|
Examinations
Exam Date |
Time/Room |
Sun, 19 June 10h:00m CB020
|
Final Examination
The final results are here
|
|
|