Course syllabus
Course: 2h/week
Lab work: 1h/week = 2h/2weeks
Project: 1h/week = 2h/2weeks
Credit points: 5
Laboratory and Project:
Andrei Vasilateanu, andraevs@gmail.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 30%
- Final exam 40%
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.
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 early 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: not available
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.
