JCL

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== Course Fact Sheet ======

**Master in Electrical and Computers Engineering\\
  Programming Laboratories\\
  Instance: 2015/2016**
\\
---
\\

//**[[https://sigarra.up.pt/feup/en/ucurr_geral.ficha_uc_view?pv_ocorrencia_id=365723|Institutional page]]**// 

===== General Information =====

**Course Unit**: Programming Laboratories\\
**Code**: EEC0030\\
**Programmes**: MIEEC, 4º\\
**Academic Year**: 2015/2016\\
**Semester**: 1S\\
**Credits**: 6 ECTS\\
**Hours/Weeks**: 1x2T, 3x2P\\
**Coordinator**: [[http://sigarra.up.pt/feup/en/func_geral.FormView?p_codigo=230756|João Correia Lopes]] (coordinator) | [[https://sigarra.up.pt/feup/pt/fest_geral.cursos_list?pv_num_unico=199702627|Filipe Correia]]

===== 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.

===== Skills and learning outcomes =====

After completing this course, the student will be able to:
  - Identify and document the requirements of a Software System using "user stories"
  - Describe the use cases using UML
  - Implement a prototype of the User Interface
  - Identify and document additional requirements
  - Obtain the conceptual domain model using UML
  - Obtain business process models using UML
  - Describe the architecture using UML
  - Validate the architecture through a prototype
  - Modelling the structure of classes using UML
  - Modelling the behaviour of objects using UML
  - Prepare the User manual
  - Prepare the Deployment manual
  - Write Java classes using standard APIs 
  - Make versions of software components
  - Documenting Java code using Javadoc
  - Test the code using Junit
  - Provide for data persistence
  - Use a collaborative documentation development tool 
  - Use an integrated development environment (IDE) in software maintenance
  - Use a version control system 

===== 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. Configurations and versioning.
  * Data persistence using SQL.
  * Project management. 

===== Work mode =====

Attendance

===== Previous knowledge =====

Knowledge of Programming languages.

===== Main bibliography =====

  * Scott Ambler, //The Object Primer//, Cambridge University Press, 3rd Edition, 2004, ISBN: 978-0-521-54018-6[[http://aleph.fe.up.pt/F/-?func=find-b&find_code=SYS&request=000153367|Library]]
  * Bruce Eckel, //Thinking in Java//, Prentice Hall, 4th Edition, 2006, ISBN: 0131-87248-6 [[http://aleph.fe.up.pt/F/-?func=find-b&find_code=SYS&request=000055636|Library]]

===== Complementary bibliography =====

  * Oracle Java Documentation, //The Java™ Tutorials//, online at [[https://docs.oracle.com/javase/tutorial/]], last accessed September 2015
  * Russ Miles e Kim Hamilton, //Learning UML 2.0//, O'Reilly, 2006, ISBN: 978-0-596-00982-3 [[http://aleph.fe.up.pt/F/-?func=find-b&find_code=SYS&request=000126325|Library]]

===== Teaching procedures =====

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 people in a software project.

===== Software =====

  * [[http://www.sparxsystems.com.au/|Enterprise Architect]] (Windows)
  * [[http://netbeans.org/|IDE NetBeans]] (Linux, MAC, Windows)
  * [[https://www.dokuwiki.org/|Dokuwiki]] (Web)
  * [[http://subversion.apache.org/|SVN]]

===== Keywords =====

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

===== Evaluation type =====

Distributed evaluation without final exam

===== Registered evaluation and occupation components =====

^ Description                          ^ Type                          ^  Time (Hours)  ^  Date of conclusion  ^
| Attendance (estimated)               | Lectures                      |  56            |                      |
| P1: User interfaces Prototype        | Laboratory work or fieldwork  |  8             |  07/10/2015          |
| P2: Requirements specification       | Laboratory work or fieldwork  |  6             |  21/10/2015          |
| P3: High level design and Prototype  | Laboratory work or fieldwork  |  20            |  11/11/2015          |
| P4: Detailed design                  | Laboratory work or fieldwork  |  8             |  02/12/2015          |
| P5: Product                          | Laboratory work or fieldwork  |  60            |  06/01/2016          |
| P6: Product presentation             | Attendance                    |  1             |  06/01/2016          |
| P7: Individual performance           | Work                          |                |                      |
| J1-J4: Java assessment               | Exercise                      |                |                      |
| M1: Java test                        | Test/Examination              |  1,5           |  19/10/2015          |
| M2: UML test                         | Test/Examination              |  1,5           |  09/11/2015          |
|                                      |                        Total: |  162           |                      |

===== Admission to 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 to show in some laboratory classes (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.

===== 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 peer assessment within each group.

===== Special assignments =====

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

===== Special evaluation (TE, DA, ...) =====

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

Students that are not required to be present in the classes, have to present the evolution of their work to the teacher simultaneously with the regular students, and conduct the same theoretical tests.

===== Improvement of final/distributed classification =====

Improving the classification requires a new enrolment in the course.

\\
 --- //JCL//