Programming Laboratories

Code:

EEC0030

Acronym:

LPRO

Keywords
Classification	Keyword
OFICIAL	Informatics

Instance: 2016/2017 - 1S

Active?	Yes
Web Page:	http://www.fe.up.pt/~jlopes/doku.php/teach/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	65	Syllabus	4	-	6	28	162

Teaching language

Suitable for English-speaking students

Objectives

Within the context of the specification, development and maintenance of software applications with graphical user interfaces (GUI) using client/server architectures, this course aims to:

• Promote the acquisition of software engineering concepts, methods and techniques and enable students to apply them in the design and development of software systems.
• Equip students with practical skills in the use of software development tools appropriate to the specification and development of the product throughout its life-cycle, including debugging, testing and documentation of the Java programming language code.

Learning outcomes and competences

After completing this course, the student will be able to:

1. Identify and document the requirements of a Software System using "user stories"
2. Describe the use cases using UML
3. Implement a prototype of the User Interface
4. Identify and document additional requirements
5. Obtain the conceptual domain model using UML
6. Obtain business process models using UML
7. Describe the architecture using UML
8. Validate the architecture through a prototype
9. Modelling the structure of classes using UML
10. Modelling the behaviour of objects using UML
11. Prepare the User manual
12. Prepare the Deployment manual
13. Write Java classes using standard APIs
14. Documenting Java code using Javadoc
15. Test the code using Junit
16. Provide for data persistence
17. Use a collaborative documentation development tool
18. Use an integrated development environment (IDE) in software maintenance
19. Use a version control system

Working method

Presencial

Pre-requirements (prior knowledge) and co-requirements (common knowledge)

Knowledge of Programming languages.

Program

- Introduction to Engineering requirements. Requirements documentation.
- UML modelling language.
- Object-oriented software design. Modelling of architecture. Structure, behaviour and architecture design.
- User interfaces design.
- Coding using the Java programming language.
- Verification, validation and software testing.
- Software maintenance. Versioning.
- Data persistence using SQL.
- Project management.

Mandatory literature

Scott W. Ambler; The object primer. ISBN: 978-0-521-54018-6
F. Mário Martins; Projetos de POO em JAVA, FCA - Editora Informática, 2014. ISBN: 978-972-722-792-1

Complementary Bibliography

Bruce Eckel; Thinking in Java, Prentice Hall, 4th Edition, 2006. ISBN: 0131-87248-6
Russ Miles and Kim Hamilton; Learning UML 2.0. ISBN: 978-0-596-00982-3
Mauro Nunes e Henrique O'Neill; Fundamental de UML, FCA - Editora Informática, 2004. ISBN: 978-972-722-481-4
Alberto Manuel Rodrigues da Silva e Carlos Alberto Escaleira Videira; UML, metodologias e ferramentas CASE. ISBN: 989-615-009-5
Henrique O.Neil, Mauro Nunes, Pedro Ramos; Exercícios de UML. ISBN: 978-972-722-616-0

Teaching methods and learning activities

Tutorial lectures (2 hours per week) will be used to briefly present the software development phases and its related artefacts, and to present and give practical examples of the methodologies and tools to be used in laboratories by following the corresponding script. Reading materials are also indicated.

In the laboratory classes (2 hours per week), the students will work in groups of four or five people in a software project.

Software

IDE NetBeans
Dokuwiki
Enterprise Architect
SVN / GIT

keywords

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

Evaluation Type

Distributed evaluation without final exam

Assessment Components

Designation	Weight (%)
Participação presencial	10,00
Teste	40,00
Trabalho laboratorial	50,00
Total:	100,00

Amount of time allocated to each course unit

Designation	Time (hours)
Elaboração de projeto	90,00
Estudo autónomo	16,00
Frequência das aulas	56,00
Total:	162,00

Eligibility for exams

Practical work (PROJ) will be evaluated through the documentation submitted, the application developed and individual performance in the class (P1 to P7).

The theoretical concepts (IND) are evaluated through the individual response, closed book, to tests (M1 and M2) and through the development of practical exercises in Java (J1 to J4).

Minimum required to pass this course: 50% in each of the practical components (P1 to P7 from PROJ) and 40% overall mark in the individual component (IND).

This course, due to its laboratory nature, can not be replaced by taking an exam.

Calculation formula of final grade

Classification = 80% PROJ + 20% IND

where:

PROJ = ((2*P1 + 3*P2 + 4*P3 + 2*P4 + 8*P5 + P6) / 20) + P7
IND = (J1 + J2 + J3 + J4 + 8*M1 + 8*M2) / 20

The classification of the practical component (PROJ) may vary from element to element in the same group by plus or minus 2 values (P7), based on the opinion of teachers and the self-evaluation to be conducted internally within each group.

Examinations or Special Assignments

Further to the demonstration of the product, an oral session may be required for some of the students.

Special assessment (TE, DA, ...)

Classification improvement

Improving the classification requires a new enrolment in the course.