Universitatea Babeş-Bolyai Cluj-Napoca
Facultatea de Matematică şi Informatică
Ciclul de studii: Licenţă
Domeniul: Informatică
Programul de studii: Informatică - în limba engleză
Limba de predare: Engleză

SYLLABUS

I. General data
Code	Subject	
MID0006	Individual Project	

Semester	Hours: C+S+L	Category	Status	
3	0+0+1	specialty	compulsory	

II. Full status faculty members
Name and	Scientific	Didactic	Chair	Type of activity	
surname	title	title		C	S	L	
POP Horia Florin	Ph.D.	Prof.	Programming  Languages and Methods			*	

Associated faculty members
Name and	Scientific	Institution	Type of	Type of activity	
surname	title		position	C	S	L	

III. Course objectives
•	To complete a significant (Pascal or C ++) program, going through all programming activities (specification, design, coding, verification of these activities, validation, and documentation) 
•	To elaborate a clear and complete documentation, and to respect the schedule of a project.	

IV. Course contents
•	Development of a software product (corresponding to a problem to be solved by a second year student in four two-hours labs), by fulfilling all the required phases:
•	specification
•	design
•	coding
•	verification of each phase (inspection and testing);
•	For each phase, a complete development documentation has to be written in parallel;
•	The user guide for the final product will be realized as well.	

V. Bibliography
1.	M. Frenţiu, H. F. Pop, G. Serban, Programming Fundamentals, Cluj University Press, 2006, 234 pages (library)
2.	M. Frentiu I. Lazăr,  Bazele Programării: Proiectarea Algoritmilor, 2000, Ed. Univ. Petru Maior, Tg.Mureş 184 pages (library)
3.	M. Frenţiu, I. Lazăr, S. Motogna, V. Prejmerean, Elaborarea algoritmilor, Ed. Presa Universitară  Clujeană, Cluj-Napoca, 1998, 188 pages (library) 
4.	M. Frenţiu, M., I. Lazăr, S. Motogna, V. Prejmerean, Programare Pascal,  Ed. Presa Universitară Clujeană, Cluj-Napoca, 1998, 392 pages (library)
5.	I. Lupea, M. Lupea, Limbajul C. Teorie şi aplicaţii. Editura Casa Cărţii de ştiinţă, Cluj-Napoca 1998 (library)
6.	M. Frenţiu, Verificarea corectitudinii programelor, Ed. Univ. Petru-Maior, Tg. Mureş, 2001  (library)	

VI. Thematic of didactic activities per weeks

No. 	
Name of phase	
Deadline	

1.	
Definition and specification of the given problem
Specification inspection	
lab. 2	

2.	
Design documentation for the project. Design inspection	
lab. 3	

3.	
Coding documentation. Coding inspection	
lab. 4	

4.	
Program testing	
lab. 5	

5.	
Testing documentation. Corrections during debugging 	
lab. 6	

6. 	
User guide. Program validation	
lab. 6 and 7	

7. 	
Final delivery and grading	
lab. 7	

Each student will have a file with all the documents written during the semester (both original and corrected documents). The documents will be written in ink or with a ball-point pen, excepting the source code, testing results and the user guide.  Documentation printing is absolutely forbidden, in order to highlight the fact that many of the developed activities take place before actually sitting at the computer.
All documents will be marked with the author name and the creation date.
All the written documents will be conserved with the signed date of the professor, even if the documents have corrected mistakes. For these cases, an extra document describing the corrections made, and the final version of the document will be added. The final grade will be based on the fulfillment of the deadlines for each particular phase. 
The attendance of lab classes is compulsory, and the process of writing a program is continuous and requests discipline. 
The files, together with the corresponding grades, will be maintained in the de department library. For the program validation phase, real world data should be available! 	

VII. Didactic methods used
Lab-oriented class, including projects, individual study, homework assignments. Use and practice of already studied programming methods and techniques. Use and practice of already studied methods for software development.	

VIII. Assessment
Grading will be done for every step from the following table, the grade of the semester activity being their average (grade A). Any documentation step not delivered will be graded with 1. If the delivering of a document is done later than scheduled, the grade will be diminished by the number of delay weeks.
For the program correctness and completeness, at the moment of program validation a second grade will be given (grade V). This grade takes into account the realized documentation and the correspondence between the original specification, the project documentation and the final product.
During the last week each student will deliver the whole documentation set. The documentation written during the semester, as well as the source code and the users guide, both in electronic format, will be handed over to the coordinating faculty member (stated at the beginning of this document) and will be graded (grade D). No delays are accepted, the lack of documentation having as a consequence failure to promote this course. The grades corresponding to non-promotions for this reason will be marked in the official exam catalogue in the first day of the examination session!
The final grade will be computed as follows:  Final grade =  (A + V + D)/3	

IX. Additional references
Internet resources on software projects and on the particular topics of the projects	

	Dean,							Chair head,

	Date,							Course responsible,
	October 1, 2008					Prof. POP Horia Florin, Ph.D.