Curricular Unit: | Code: | ||
Systems and Networks Project | 833PSRS | ||
Year: | Level: | Course: | Credits: |
1 | Master | Computer Systems Engineering (Information Systems and Multimedia) | 6 ects |
Learning Period: | Language of Instruction: | Total Hours: | |
Portuguese/English | 78 | ||
Learning Outcomes of the Curricular Unit: | |||
At the end of the course students should be able to: - define the architecture and the components of a complex application - choose development environments and techniques - choose design patterns and other good practices - defined unit tests - assess performance - document the application | |||
Syllabus: | |||
1. General introduction to a software project 2. Source code control systems 3. Tickets and change control 4. Automatic testing of applications 5. Product delivery | |||
Demonstration of the Syllabus Coherence with the Curricular Unit's Objectives: | |||
The syllabus addresses the objectives of the course, covering the materials necessary for the students to acquire the competencies. As students will be working collaboratively on a real project,they can make use of skills acquired in other courses, and develop other skills in this course. | |||
Teaching Methodologies (Including Evaluation): | |||
The methodology of teaching and learning is expository, and demonstrative. The assessment includes: • Submission of the proposed assignments (50%) • Oral presentation of the dissertation project (50%) | |||
Demonstration of the Coherence between the Teaching Methodologies and the Learning Outcomes: | |||
The proposed methodologies are consistent with the objectives set for the course since they rely on the capacity to define and organize a software project. Students acquire the necessary skills by working collaboratively on a software project. | |||
Reading: | |||
[1] Herbert Schildt, Java, A Beginner's Guide, 5ª ed., McGraw-Hill, Oracle Press, 2012. [2] Kent Beck, Test Driven Development: By Example, Addison-Wesley, 2003. [3] Deepak Vohra, Java EE Development with Eclipse, Packt Publishing, 2012. [4] Eric Sink, Version Control by Example, Pyrenean Gold Press, 2011. |