ECTS credits ECTS credits: 6
ECTS Hours Rules/Memories Student's work ECTS: 99 Hours of tutorials: 3 Expository Class: 24 Interactive Classroom: 24 Total: 150
Use languages Spanish, Galician, English
Type: Ordinary Degree Subject RD 1393/2007 - 822/2021
Departments: Electronics and Computing
Areas: Languages and Computer Systems
Center Higher Technical Engineering School
Call: Second Semester
Teaching: Sin docencia (Extinguida)
Enrolment: No Matriculable
The basic aim of the subject is to provide the students with a set of design techniques and principles that allow them to face the construction of software in a systematic way. Especially, given the demonstrated efficiency of the object-oriented paradigm in developing flexible and reusable software, the modelling of applications under this perspective is embraced.
The three pillars which sustain the subject are: the learning of modelling principles based on a standard graphical language; the description of a light construction process driven by use cases, architecture-centric, iterative and incremental; and the application of design patterns as efficient solutions to recurring modelling problems.
Design concepts
Models and strategies
Architectural design
Reference architectures
Introduction to the object-oriented paradigm
Modelling of functional requirements
Structural modelling
Behavioural modelling
Physical modelling
Object-oriented development process
Design patterns
No class notes are provided by the professors in this subject.
Basic Bibliography:
1. FOWLER, Martin. UML Distilled: a brief guide to the standard object modeling language. 3rd ed. Boston: Addison-Wesley, 2004. ISBN 0-321-19368-7
2. BOOCH, Grady, RUMBAUGH, James, JACOBSON, Ivar. El Lenguaje Unificado de Modelado. 2ª ed. Madrid: Addison-Wesley, 2006. ISBN 84-7829-076-1
3. LARMAN, Craig. UML y patrones: una introducción al análisis y diseño orientado a objetos y al Proceso Unificado. 2ª ed. Madrid: Prentice Hall, 2003. ISBN 84-205-3438-2
4. GAMMA, Erich et al. Patrones de Diseño: elementos de software orientado a objetos reutilizable. Madrid: Addison-Wesley, 2002. ISBN 84-7829-059-1
Complementary Bibliography:
1. MARTIN, Robert C. UML para programadores en Java. Madrid: Prentice Hall, 2004. ISBN 84-205-4109-5
2. RUMBAUGH, James, JACOBSON, Ivar, BOOCH, Grady. El Lenguaje Unificado de Modelado: manual de referencia. 2ªed. Madrid: Addison-Wesley, 2007. ISBN 978-84-78290871
3. JACOBSON, Ivar, BOOCH, Grady, RUMBAUGH, James. El Proceso Unificado de desarrollo de software. Madrid: Addison-Wesley, 2000. ISBN 84-7829-036-2
4. FREEMAN, Eric et al. Head first Design Patterns. Sebastopol (CA): O’Reilly, 2004. ISBN 0-596-00712-4
To contribute to the acquisition of the global competences of the Degree in Computer Engineering of the USC (namely, CG1, CG5, CG8, CG9, TR2, TR3) and those competences associated to the Software Engineering Module (in particular, RI1, RI8, RI16, TI2).
With regard to the concrete competences which are comprised by that module, this subject contributes to the acquisition of the following ones:
- The students will be able to rationally select a life cycle for a project, and to understand its phases and resulting deliverables.
- They will understand the consequences that different processes have over the software construction model and over the software itself.
- They will be able to specify a set of software requirements for a middle size project.
- They will be able to talk through the properties a fine design shows.
- They will be able to assess the quality of a design in accordance with the concepts and principles of design.
- They will be able to appropriately select and apply design patterns.
- They will understand the purpose of tests and their impact to process and software product.
- They will recognize the possibilities and consequences of software reuse.
- They will understand the advantages and limitations of development methodologies.
The activities to be carried out during the term are:
1. Theoretical lectures centred on the necessary concepts to systematically face the construction of software. In particular, the professor will deal with topics related to the specification of functional requirements, the modelling of the duality structure / behaviour, and the application of design patterns. Consequently, in these sessions the students are provided with the fundamentals for developing general competences CG5, CG8 and CG9, and the transversal abilities TR2 (critical reasoning) and TR3 (self-learning and adaptation to new conditions), as well as computing branch competences RI1 and RI8, and IT capability TI2.
2. Short individual or group works. The individual activities will consist on the solving of exercises proposed by the professor, whereas the groups made for collective activities will rely on cooperative learning techniques such as Aronson’s Jigsaw in order to investigate and present particular contents of the subject. Therefore, this type of activities focuses on developing software modelling abilities (which means to work on competences CG5, RI1, RI8 and TI2) and group work (competence TR2).
3. Practical group activities. The dynamics of the practical sessions in the computer room will follow an interactive approach. At the very beginning of the term students will be organized in work teams to solve the proposed activities using project-based learning methods. A software construction project will be faced by the students using the design techniques presented in the subject and the professor will supervise each team’s progression by means of intermediate submissions. This type of activities comprises tasks which belong to each of the three axis of the subject (as stated in the Objectives section), so it contributes to the acquisition of all the competences that were previously enumerated in the proper section; nevertheless, the spotlight is mainly turned on competences CG1 (ability to conceive, draw up, organize, plan, develop and sign off computer engineering projects which aim at the inception, developing or exploitation of computer systems, services or applications), TR2 (team work) and RI16 (knowledge and application of principles, methodologies and life cycles in the field of software engineering).
4. Follow-up and feedback. The tutorial sessions will lay emphasis on the active orientation of the students, with a special attention to the development of the team practices proposed at the computer room.
5. Final exam. At the end of the term, students will have to individually show the level reached with regard to the competences of the subject. Particularly, skills closely related to software modelling are pursued (namely, competences CG5, RI1, RI8 and TI2).
June Opportunity:
Continuous evaluation through activities 2 and 3 has a weight of 75% in the final mark, whereas the final exam has a contribution of 25%. Within the continuous assessment, activity 3 contributes with 80% and activity 2 with the remaining 20%.
To succeed, students have to independently pass the continuous evaluation and the exam.
Any student who sits the theoretical exam or submits any piece of activity 3 will officially become examined.
July Opportunity:
All the students that had not passed the exam in the June assessment will have to sit a new theoretical exam whose contribution to the final mark will be of 25%.
On the one hand, those students who had submitted the project in the first assessment but had not got a minimum mark with regard to continuous assessment will have a chance to improve the previous version under the same conditions. Therefore, marks to type 2 activities (see Methodology) will be kept. Students under this situation must independently succeed with respect to both continuous evaluation and examination in order to pass the subject.
On the other hand, students under the condition of not examined in the first assessment due to a missing group project will have to develop a new individual project with a weight of 75% of the final mark. This project will measure the performance in relation to type 2 and 3 activities. In this case, no previous marks to type 2 activities will be saved, and independent success will be required for both project and examination in order to pass the subject.
In any case, those students who take the theoretical examination or submit the project will get the official consideration of examined.
Extraordinary Exams:
Assessment will take place through a theory test with a weight of 25% followed by a practical examination that will yield the remaining 75%. It is required to pass both exams separately in order to succeed. The students who sit any of these examinations will automatically get the consideration of examined.
Under no circumstances will marks be kept among assessments belonging to different academic years. The presence of the students in the expositive and interactive sessions will not be directly taken into account for the assessment.
The subject is comprised of 6 ECTS. Besides the on-site work, the student must distribute about 90 hours of personal work among work writing, exercise solving, practice resolution, and autonomous study.
It is very desirable a previous knowledge of the object-oriented paradigm. Therefore, it is highly advisable to have passed before the subject Object-Oriented Programming (OOP).
The regular attendance to theoretical classes, practical sessions, and tutorials is much encouraged. The student must assume the necessary effort to keep the subject up-to-date.
All the activities will be supported by USC’s Virtual Campus (Moodle platform).
Type 3 activities (see the Methodology section) will be developed using the object-oriented modelling tool StarUML.
The preferential languages in this subject are Spanish and Galician.
Xosé Manuel Pardo López
- Department
- Electronics and Computing
- Area
- Languages and Computer Systems
- Phone
- 881816438
- xose.pardo [at] usc.es
- Category
- Professor: University Lecturer
Jose Varela Pet
Coordinador/a- Department
- Electronics and Computing
- Area
- Languages and Computer Systems
- jose.varela.pet [at] usc.es
- Category
- Professor: Temporary PhD professor
| Monday | |||
|---|---|---|---|
| 16:00-17:00 | Grupo /CLE_01 | Spanish | Classroom A1 |
| Tuesday | |||
| 09:00-12:00 | Grupo /CLIL_04 | Spanish | Computer Room I6 |
| Wednesday | |||
| 09:00-12:00 | Grupo /CLIL_02 | Spanish | Computer Room I5 |
| 17:00-18:00 | Grupo /CLE_01 | Spanish | Classroom A1 |
| Thursday | |||
| 09:00-12:00 | Grupo /CLIL_03 | Spanish | Computer Room I6 |
| Friday | |||
| 09:00-12:00 | Grupo /CLIL_01 | Galician | Computer Room I6 |
| 01.20.2021 09:15-14:00 | Grupo /CLIL_04 | rest room / dining room |
| 01.20.2021 09:15-14:00 | Grupo /CLE_01 | rest room / dining room |
| 01.20.2021 09:15-14:00 | Grupo /CLIL_01 | rest room / dining room |
| 01.20.2021 09:15-14:00 | Grupo /CLIL_02 | rest room / dining room |
| 01.20.2021 09:15-14:00 | Grupo /CLIL_03 | rest room / dining room |
| 07.09.2021 16:00-20:45 | Grupo /CLIL_01 | Classroom A1 |
| 07.09.2021 16:00-20:45 | Grupo /CLIL_02 | Classroom A1 |
| 07.09.2021 16:00-20:45 | Grupo /CLIL_03 | Classroom A1 |
| 07.09.2021 16:00-20:45 | Grupo /CLIL_04 | Classroom A1 |
| 07.09.2021 16:00-20:45 | Grupo /CLE_01 | Classroom A1 |
| 07.09.2021 16:00-20:45 | Grupo /CLE_01 | Classroom A2 |
| 07.09.2021 16:00-20:45 | Grupo /CLIL_01 | Classroom A2 |
| 07.09.2021 16:00-20:45 | Grupo /CLIL_02 | Classroom A2 |
| 07.09.2021 16:00-20:45 | Grupo /CLIL_03 | Classroom A2 |
| 07.09.2021 16:00-20:45 | Grupo /CLIL_04 | Classroom A2 |