Checking date: 06/05/2020


Course: 2019/2020

Software Development
(18179)
Dual Bachelor in Computer Science and Engineering, and Business Administration (Plan: 437 - Estudio: 233)


Coordinating teacher: GARCIA GUZMAN, JAVIER

Department assigned to the subject: Computer Science and Engineering Department

Type: Compulsory
ECTS Credits: 6.0 ECTS

Course:
Semester:




Requirements (Subjects that are assumed to be known)
Programming Software Engineering
The goal of the course is to allow the student knowing in depth the software development process, with features about software testing and quality software issues. To achieve this goal, the student must acquire the following PO: a, b, d, e, f, g, k 1. The transverse or generic competences that will be acquired throughout the course are 1.1 Abstraction capacity 1.2 Analysis and Synthesis Capacity (PO: b) 1.3 Capability to plan and organize (PO: b) 1.4 Ability to solve problems (PO: a, e, k) 1.5 Work in teams (PO: d) 1.6 Ability to apply knowledge in practice (PO: a, b, d, e, g, k) 2. The specific competences that will be developed throughout the course are: 2.1 Cognitive (Know) (PO: a, b, d, e, f, g, k) (CECRI8) 2.1.a To know how to develop software components in a disciplined way including software development processes and lifecycle (CECRI16) 2.1.b. Agile Software Development Culture 2.1.c. Agile Software Development Techniques 2.1.d. Test Driven Development 2.1.e. Simple Design and Refactoring 2.1.f. To know ethic features in software development process (CECRI1) 2.2 Instrumental (Know How) (PO :b, e, k) 2.2.a. Develop a software compoment applying coding standards 2.2.b. Develop a software compoment applying code collective ownership 2.2.c. Develop a software compoment applying test driven development 2.2.d. Develop a software compoment applying different testing techniques 2.2.e. Develop a software compoment applying different automated testing 2.2.f. Develop a software compoment applying continuous automated integration 2.2.h. Develop a software compoment applying refactoring 2.2.i. Develop a software compoment applying simple design patterns 2.3 Attitude (Be) (PO: e, k) 2.3.a. Abilities to generate new ideas 2.3.b. To develop a good work using quality measures 2.3.c. Problem solving orientation 2.3.d. To investigate and find solutions to new problems 2.3.e. To develop a good work using quality measures
Description of contents: programme
1.- Ethic and Legal Issues in the Software Engineering Profession 1.1.- The software engineering profession. 1.2.- The software engineers' code of ethics. 2.- Agile Software Development Techniques 2.1.- Pair Programming 2.2.- Coding Standards 2.3.- Code Collective Ownership 3.- Test Driven Development 3.1.- Principles of Test Driven Development 3.2.- Functional Testing Techniques 3.3.- Estructural Testing Techniques 3.4.- Unit Testing Automation 3.5.- Automated Continuous Integration 4.- Refactoring and Simple Design 4.1.- Refactoring 4.2.- Principles of Software Design 4.3.- Design Patterns for Responsibilities Assignment
Learning activities and methodology
Lectures: 1,5 ECTS, to get the specific cognitive and instrumental competences of the subject. (PO: a, b, e, f, g, k) Exercise Classes: 1,5 ECTS, to get the specific instrumental and generic competences, as well as the attitude competences of the subject. A practical example related to the development of a software component (including estimation, specification, design, software reviews and testing activities) will be carried out, considering ethic and legal features. (PO: a, b, d, e, f, g, k) Academic Work with professor assistance: 1 ECTS, Presentation and discussion of a specific software component development case, analyzing all the aspects considered in the theoretical part of the subject. (PO: a, b, d, e, f, g, k) Academic Work without professor assistance: 1 ECTS, Individual work for the development of a specific software component development case, analyzing all the aspects considered in the theoretical part of the subject. (PO: a, b, e, f, k) Exam: 1 ECTS (PO: a, b, d, e, f, g, k)
Assessment System
  • % end-of-term-examination 40
  • % of continuous assessment (assigments, laboratory, practicals...) 60

Basic Bibliography
  • Beck, Ken. Extreme Programming Explained. Addison-Wesley. 2000
  • Beck, Ken, et al.. Test-Driven Development By Example. Three Rivers Institute. 2002
  • Craig S. Larman. Applying UML and Patterns. Pearson Education . 3er Edition, 2012
  • Fowler, Martin et al.. Refactoring: Improving the Design of Existing Code. Addison-Wesley. 1999
  • Lee Copeland. A Practitioner's Guide to Software Test Design. . Artech House Publishers .
Additional Bibliography
  • Paul C Jorgensen. Software Testing: a craftsman's approach. CRC Press.
  • Roger S. Pressman. Software Engineering. A practical Approach. McGraw Hill. 7th Edition, 2009
  • Spyros Xanthakis, Michel Maurice, Antonio de Amescua, Olivier Houri, Luc Griffet. Test & Controle des Logiciels: Methodes, Techniques & Outils. EC2.

The course syllabus may change due academic events or other reasons.