|
Type A
|
Code |
Competences Specific | | | A1 |
Project, calculate and design products, processes and installations in all areas of computer engineering. |
| | A2 |
Manage projects and installations of computer systems, complying with the current regulations and ensuring the quality of the service. |
| | D2 |
Undertake strategic planning, manufacture, direction, coordination and technical and economic management in the field of computer engineering related to, among others: computer systems, applications, services, networks, infrastructure or installations and centres or factors for software development, observing the proper compliance with quality and environmental criteria and in multidisciplinary working environments. |
| | D3 |
Undertake the management of research, development and innovation projects, in companies and technological centres, guaranteeing safety for people and goods, the final quality of the products and their approval. |
| | T1 |
Model, design, define the architecture, implement, manage, operate, administrate and maintain computer applications, networks, systems, services and content. |
| | T3 |
Ensure, manage, audit and certify the quality of the computer developments, processes, systems, services, applications and products. |
| | T4 |
Design, develop, manage and evaluate mechanisms to certify and guarantee security in handling information and access to it in a local or distributed processing system. |
| | T5 |
Analyse the information needs considered in an environment and execute all stages of the construction process of an information system. |
|
Type B
|
Code |
Competences Transversal | | | B2 |
Aplicar el pensament crític, lògic i creatiu, demostrant capacitat d’innovació. |
| | B3 |
Treballar de forma autònoma amb responsabilitat i iniciativa. |
|
Type C
|
Code |
Competences Nuclear | | | C3 |
Be able to manage information and knowledge |
|
Type A
|
Code |
Learning outcomes |
| | A1 |
Design and implement software products with validation mechanisms and software quality.
| | | A2 |
Coordinate and manage an IT project in all stages of development.
| | | D2 |
Plan development software projects with software engineering techniques.
| | | D3 |
Coordinate and manage an IT research or innovation project in all stages of development.
| | | T1 |
Model, design and define the software architecture of a computer system.
| | | T3 |
Manage the quality of the software in an IT project.
| | | T4 |
Design and implement the security of a computer system regarding data access.
| | | T5 |
Analyse the requirements of a computer system.
Manage the life cycle of an IT project.
|
|
Type B
|
Code |
Learning outcomes |
| | B2 |
Search for new procedures and methods.
| | | B3 |
Decide how to do a particular job so that it is of the highest quality possible.
|
|
Type C
|
Code |
Learning outcomes |
| | C3 |
Critically evaluate information and its sources, and add it to their own knowledge base and system of values.
|
| Topic |
Sub-topic |
| 1. Software Architecture General Concepts |
Definitions; Uses; Architectures and technologies |
| 2. Introducing a Case Study |
Overview; Description; ITIL v3 |
| 3. Software Architectures and Patterns |
Classification; Microservice architectures; MVC pattern |
| 4. Service Oriented Architectures and Integration |
Technologies; SOA; Web Services; REST |
| 5. Software Quality and Validation |
TDD; BDD; Testing Phases |
| 6. Notations and Description Languages |
UML; BPMN 2.0; DSL |
| 7. Model and Process Architectures |
MDA; BPM; Outline; Design; Execution |
| 8. Case Study Design |
Overview; Architecture requirements; Solution |
| Methodologies :: Tests |
| |
Competences |
(*) Class hours
|
Hours outside the classroom
|
(**) Total hours |
| Introductory activities |
|
1 |
0 |
1 |
| Lecture |
|
33 |
30 |
63 |
| Laboratory practicals |
|
22 |
40 |
62 |
| Personal tuition |
|
1 |
5 |
6 |
| |
| Practical tests |
|
3 |
15 |
18 |
| |
(*) On e-learning, hours of virtual attendance of the teacher.
(**) The information in the planning table is for guidance only and does not take into account the heterogeneity of the students. |
Methodologies
| |
Description |
| Introductory activities |
Course presentation: contents, calendar of activities, evaluation, bibliography, ... |
| Lecture |
Regular lectures in which the contents of the subject is explained. |
| Laboratory practicals |
Class and off-class hours addressed to solve a practical case. |
| Personal tuition |
Personalized attention to solve student doubts. Out of class hours. |
|
Description |
|
The lecturer provides four outclass hours per week to attend individual and group doubts. |
|
Methodologies |
Competences
|
Description |
Weight |
|
|
|
|
| Laboratory practicals |
|
The student alone or in group will develop a practical case. |
50% |
| Practical tests |
|
Three exams (1 to 2 hours) the students have to solve individual problems and short questions, and a set of complementary virtual sessions |
50% |
| Others |
|
|
|
| |
|
Other comments and second exam session |
|
If the student does not pass the first call, a second call will be available as a single exam. During the exams the use of any communication and data transmission device is not allowed. The unfulfillment of this obligation means not passing of the exam. |
| Basic |
Gorton, Ian, Essential Software Architecture, Springer, 2011
|
|
| Complementary |
|
|
| Subjects that continue the syllabus |
| HIGH PERFORMANCE ARCHITECTURES/17665102 | | MANAGEMENT OF INFORMATIC PROJECTS/17665106 | | ARCHITECTURES FOR DISTRIBUTED SYSTEMS/17665107 | | VISUALISATION AND INTERACTION SYSTEMS/17665104 | | DEVELOPMENT OF INFORMATIC PROJECTS/17665109 |
|
(*)The teaching guide is the document in which the URV publishes the information about all its courses. It is a public document and cannot be modified. Only in exceptional cases can it be revised by the competent agent or duly revised so that it is in line with current legislation. |
|