Ficha

Versión en español

Course: 2024/2025

Software Engineering

(15974)

Bachelor in Computer Science and Engineering (Plan: 489 - Estudio: 218)

Coordinating teacher: ALVAREZ RODRIGUEZ, JOSE MARIA

Department assigned to the subject: Computer Science and Engineering Department

Type: Compulsory

ECTS Credits: 6.0 ECTS

Course: 2º

Semester: 1º

Requirements (Subjects that are assumed to be known)

Writing and Communication Skills (1st course, 1st semester)

Skills and learning outcomes

Link to document

¿	Know how to obtain, describe and manage requirements for the functional and non-functional description of a software application.
¿	Design and develop conceptual and 	architectural models of a software application.

Description of contents: programme

Block I. Requirements engineering Unit 1. Introduction to requirements engineering Unit 2. Elicitation, description and management of requirements Unit 3. Properties, attributes and organization of requirements Unit 4. Types of requirements Block II. Conceptual modeling with UML Unit 5. Introduction to conceptual modeling Unit 6. Conceptual modeling: classes and objects Unit 7. Conceptual modeling: associations Unit 8. Conceptual modeling: hierarchies Block III. Architectural modeling with UML Unit 9. Introduction to architectural modeling Unit 10. Architectural modeling: components Unit 11. Architectural modeling: interfaces Unit 12. Architectural modeling: design by contracts

Learning activities and methodology

Theoretical-Practical Lectures: 1 ECTS - Review of contents before class Practical Lectures: 1 ECTS - Exercise resolution - General tutoring - Partial oral expositions of the project Team Work: 3 ECTS - Proposal of project statement - Project development - Project peer review - Proposal of questions for the theoretical exam Individual Work: 1 ECTS - Contribution to team project - Individual practical exercises - Study and preparation of final exam

Assessment System

% end-of-term-examination 55
% of continuous assessment (assigments, laboratory, practicals...) 45

Calendar of Continuous assessment

CONTINUOUS EVALUATION (45%)
-       Week    5:   Activities, participation, and exercises in the classroom (Theory, 5%)
-       Week   12:  Exercises in groups (Practice, 10%)
-       Week   13:  Activities, participation and exercises in the classroom (Theory, 5%)
-       Week   13:  Final project (team) delivery and monthly reviews (Practice, 15%)
-       Week   14:  Individual practical exercises (Practice, 10%)

FINAL EVALUATION (55%)
-	Final project: technical report: 25%
-	Final exam: 30%

A minimum grade of 5 is required in both the final project and the final exam to pass the course.The final exam will comprise exercises related to the application of all contents of the course.

Extraordinary call: regulations

Basic Bibliography

Alexander, I. and Stevens, R.. Writing Better Requirements. Addison-Wesley. 2002
Arlow, J. and Neustadt, I.. UML and the Unified Process. Practical Object-Oriented Analysis & Design. Addison-Wesley. 2002
Braude, E.. Software Engineering. An Object-Oriented Perspective.. John Wiley & Sons, 2001..
ESA Board for Software Standardisation and Control (BSSC).. ESA Software Engineering Standards.. European Space Agency, February 1991..
Fowler, M. and Scott, K.. UML Distilled. A Brief Guide to the Standard Object Modeling Language. Addison-Wesley. 2004
Larman, C.. Applying UML and Patterns. An Introduction to Object-Oriented Analysis and Design and the Unified Process. Prentice Hall. 1998
Mark Richards, Neal Ford. Fundamentals of Software Architecture. O'Reilly Media, Inc. 2020
Martin Fowler. Patterns of Enterprise Application Architecture. Addison-Wesley . 2002
Martin Fowler. Refactoring. Addison-Wesley . 2018
Pressman, Roger S.. Ingeniería del software: un enfoque práctico, 6ª ed.. McGraw-Hill, 2006..
Robert Martin. Clean Code: A Handbook of Agile Software Craftsmanship. Prentice Hall. 2008
Robert Martin. Clean Architecture. Prentice-Hall. 2017
Sommerville, I.. Ingeniería del Software.. Pearson-Addison Wesley, 2005..
Sommerville, I. and Sawyer, P.. Requirements Engineering: A Good Practice Guide. John Wiley & Sons. 1997
Stevens, P. and Pooley, R.. Using UML, Software Engineering with Objects and Components. Addison-Wesley. 2000
Wiegers, K. and Beaty, J.. Software Requirements. Microsoft Press. 2013

Electronic Resources *

IEEE Software Special Issue · 50 Years of Software Engineering : https://ieeexplore.ieee.org/document/8474511
Ian Sommerville · Software Engineering, Tenth Edition : https://iansommerville.com/software-engineering-book/
Jose María Alvarez Rodríguez · Lista de lectura de DevOps : https://learning.oreilly.com/playlists/bc1031bc-6189-42b8-85b7-789a7e59b0bd
Jose María Alvarez Rodríguez · Lista de lectura de Arquitectura de Software : https://learning.oreilly.com/playlists/80425411-f3fe-4b47-8415-35cfffcfce0f
UC3M · The Software Architect Code: Building the Digital World : https://www.edx.org/course/software-architect-code-building-digital-uc3mx-inf-1x
edX Platform · List of courses on Software Engineering : https://www.edx.org/course?search_query=SOFTWARE+ENGINEERING

Additional Bibliography

ISO. ISO/IEC/IEEE 15288:2023 Systems and software engineering System life cycle processes. ISO. 2023
N. Ford, M. Richards, P. J. Sadalage, and Z. Dehghani. Software Architecture: The Hard Parts: Modern Trade-Off Analyses for Distributed Architectures . O'Reilly. 2021
Titus Winters, Tom Manshreck, Hyrum Wright. Software Engineering at Google. O'Reilly Media, Inc.. 2022

Electronic Resources *

IEEE Software Special Issue · 50 Years of Software Engineering : https://ieeexplore.ieee.org/document/8474511
Marc Andreessen · Why Software Is Eating The World (Divulgative) : https://www.wsj.com/articles/SB10001424053111903480904576512250915629460
Robert N. Charette · How Software Is Eating the Car : https://spectrum.ieee.org/cars-that-think/transportation/advanced-cars/software-eating-car

(*) Access to some electronic resources may be restricted to members of the university community and require validation through Campus Global. If you try to connect from outside of the University you will need to set up a VPN

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