Programming Laboratories

Code:

EEC0030

Acronym:

LPRO

Keywords
Classification	Keyword
OFICIAL	Informatics

Instance: 2008/2009 - 1S

Active?	Yes
Web Page:	http://paginas.fe.up.pt/~jlopes/teach/2008-09/LPRO/
Responsible unit:	Department of Informatics Engineering
Course/CS Responsible:	Master in Electrical and Computers Engineering

Cycles of Study/Courses

Acronym	No. of Students	Study Plan	Curricular Years	Credits UCN	Credits ECTS	Contact hours	Total Time
MIEEC	75	Syllabus since 2006/2007	3	-	8	87	213
			4
		Plano para bachareis que em 06 estiveram no 5º ano	4	-	8	87	213
		Syllabus since 2007/2008	3	-	8	87	213
			4
		Plano para alunos que em 2006 estiveram no 3º ano	3	-	8	87	213
		Plano para alunos que em 2006 estiveram no 5º ano	3	-	8	87	213
		Plano para alunos que em 2006 estiveram no 4º ano	3	-	8	87	213
		Plano para bachareis que em 06 estiveram no 4º ano	4	-	8	87	213

Teaching language

Portuguese

Objectives

By the end of this course the student will be able to:
* List a set of functional requirements for the system
* Write the Requirements Manual
* Implement a prototype of the User Interface
* Write the High-level Design for the system
* Implement a vertical prototype for the system
* Write the Detailed Design for the system
* Write the User Manual
* Write the Deployment Manual
* Use UML to build the User Requirements Model
* Use UML to build the Domain Object Model
* Use UML to build the Architecture Model
* Use UML to build the Behavior Model
* Code the system using Java
* Use versioning
* Document the code using Javadoc
* Test the code using Junit
* Use a wiki to build the documentation in a collaborative way
* Use the Eclipse IDE to manage the software

Program

* Introduction to Software Engineering.
* Requirements engineering. Elicitation, analysis, specification, validation and management of requirements.
* Modelling languages. User Requirements Document.
* Object-oriented software design. Structure, behavior and architecture design.
* User interfaces design.
* Coding with Java.
* Verification, validation and testing of software.
* Software maintenance. Configurations and versioning.
* Project management.

Mandatory literature

Silva, Alberto Manuel Rodrigues da; UML, metodologias e ferramentas CASE. ISBN: 972-8426-36-4

Complementary Bibliography

Pressman, Roger S; Software engineering. ISBN: 0-07-709677-0
Grady Booch, James Rumbaugh, Ivar Jacobson; The The Unified Modeling Language User Guide. 2nd Edition., Addison Wesley Professional, 2005. ISBN: 0-321-26797-4
Sommerville, Ian; Software engineering. ISBN: 0-321-21026-3

Teaching methods and learning activities

The subject has lectures and laboratory classes. Lectures will be used to present the theoretical content, together with practical examples using the methodologies and tools to be used in laboratory. The students will work in groups of five people in a software project.

Software

CVS
dokuwiki
IDE Netbeans

keywords

Physical sciences > Computer science > Programming
Physical sciences > Computer science > Programming > Software engineering

Evaluation Type

Distributed evaluation without final exam

Assessment Components

Description	Type	Time (hours)	Weight (%)	End date
Subject Classes	Participação presencial	70,00
TP1: User Interface Prototype	Trabalho escrito	27,00		2008-10-06
TP2: User Requirements Document	Trabalho escrito	9,00		2008-10-13
TP3: Preliminary Design Document	Trabalho escrito	18,00		2008-11-03
TP4: Vertical Prototype	Trabalho escrito	12,00		2008-11-17
TP5: Detailed Design Document	Trabalho escrito	27,00		2008-12-08
TP6: Product	Trabalho escrito	36,00		2008-12-15
TP7: Demonstration	Trabalho escrito	4,00		2008-12-15
TP8: Continuous assessment of the students' own performanc	Trabalho escrito	0,00		2008-12-15
FT1: Use Cases Model	Teste	1,50		2008-10-13
FT2: Domain Object Model	Teste	1,50		2008-10-20
FT3: Architecture Model	Teste	1,50		2008-11-10
FT4: Java	Teste	1,50		2008-11-24
	Total:	-	0,00

Eligibility for exams

Practical work (TP) will be accessed through the documentation delivered, the product developed and the student's own performance in the laboratory classes:
* TP1: User Interface Prototype
* TP2: User Requirements Document
* TP3: Preliminary Design Document
* TP4: Vertical Prototype
* TP5: Detailed Design Document
* TP6: Product
* TP7: Demonstration
* TP8: Continuous assessment of the students' own performance

Theoretical content will be accessed through Continuous Assessment Test (CAT) sheets (FT1 to FT4) to be filled by each student in some of the laboratory classes.

Calculation formula of final grade

Classification = 80% TP + 20% FT,
where:
TP = TP1 + 3* TP2 + 2* TP3 + 2* TP4 + 3* TP5 + 7* TP6 + TP7 + TP8
and:
FT = FT1 + FT2 + FT3 + FT4

The classification of any component of assessment can vary from element to element in the same group by plus or minus 2 values, based on the opinion of teachers and the self-evaluation to be conducted internally within each group.

Examinations or Special Assignments

The practical work is required for all enrolled students and must be submitted before the deadlines advertised. After product demonstration, an oral session may be required for some of the students.

Special assessment (TE, DA, ...)

Students under special regimes are expected to submit the practical work required for this subject as ordinary students.

Classification improvement

Students may improve the mark obtained in the subject's next edition.