Software engineering is a discipline where methods, tools and processes are combined to develop quality software. In this course these principles are learnt through the development of a software project.

The main goal of the subject is to provide tools for designing and implementing software applications whose requirements are captured, defined and analyzed using UML modeling language and applying multi-tier software architectures. This methodology will ultimately make software project development a systematic task that relies on well-tested tools that improve significantly the quality of the product.



At the end of the day the student should be capable of:

1) distinguishing the different stages involved in Software Engineering;

2) understanding an object-oriented software system expressed in UML;

3) designing a software system from the requirements using a multi-tier architecture;

4) implementing a software system from the application design.

TOPIC 1: Requirements capture

1.1.- Use Case Model

1.2.- Domain Model



TOPIC 2: Design

2.1.- Sequence Diagrams

2.2.- Software design patterns

2.3.- Multi-tier software architectures



TOPIC 3: Implementation

3.1.- Graphical user-interfaces

3.2.- Object persistence

3.3.- Distributed computing

The subject's most outstanding activity will be undertaking a step-by-step software Project along the semester. Teaching methodology will be oriented to Project Based Learning (PBL) and other active teaching techniques, with teamwork sessions, debates and exercise solving presentations. In the laboratory a number of the tasks necessary to fulfill the project will be worked on, introducing specific useful software tools and environments.

• Continuous Assessment System
• Final Assessment System
• Tools and qualification percentages:
  • The percentages and types of evaluation are specified in the subsequent sections. (%): 100

Two evaluation methods are envisaged: Continuous Evaluation and End-of-course Evaluation.



CONTINUOUS EVALUATION: The student that opts in pledges to carry on a continuous follow-up of the course with systematic attendance, dedication to the face-to-face activities and integration in a team to undertake the Project.



The different activities to be considered within Continuous Assessment are the following:

1) Project: 70%

2) Individual written exercises: 20%

3) Other complementary activities (including labs): 10%



The project will be framed in three full iterations, all of which will undergo the essential phases of software development: identification and capture of system requirements, design and software architecture, implementation and deployment. Thus topics 1, 2 and 3 will not be learned sequentially but in a spiral cycle. Third iteration will also involve undertaking a global defense of the Project and passing a short test.



END-OF-COURSE EVALUATION: This is to be applied to students that either don't wish or aren't eligible for Continuous Evaluation. Anyway undertaking a Project (not necessarily the same one as in Continuous Evaluation) will be mandatory. End-of-course Evaluation will be graded with the average between the Project and a Global Exam that encompasses 100% of the subject's topics. The student wishing to undergo End-of-course Evaluation must arrange an interview with the teacher before 8rd week of the four month.



Evaluable activities can have restrictions that, if not met will imply not passing the subject. In particular the project must operate correctly according to the requirements.

To apply to this exam the student must have approved the project presented at the beginning of the course. The final grade is the average of the project grade and an overall examination covering 100% of the contents of the course. To pass the course both the project and the exam must be passed individually.

The use of the following resources is mandatory in order to course the subject:
- Egela platform of the UPV/EHU. http://egela.ehu.eus/
- Star UML. https://staruml.io/
- Eclipse development environment. http://www.eclipse.org

The set of slides used by the teacher to present the subject and the wordings of the exercises and of the project stages are also considered as required resources for the subject, and will be made available through the Egela platform.

Basic bibliography

- SOFTWARE ENGINEERING: A PRACTITIONER'S APPROACH (7th edition). Roger S. Pressman. MacGraw-Hill, 2010 (general reference on Software Engineering).



- APPLYING UML AND PATTERNS: AN INTRODUCTION TO OBJECT-ORIENTED ANALYSIS. Craig Larman. Prentice-Hall, 1998 (on UML and GRASP).

In-depth bibliography

- THE UNIFIED SOFTWARE DEVELOPMENT PROCESS. Ivar Jacobson, Grady Booch & James Rumbaugh. Pearson-Addison Wesley, 1999 (on UML and unified software development process).

- OBJECT-ORIENTED SOFTWARE. Bertrand Meyer. Prentice-Hall, 1998 (about object-oriented design).

Journals

javaHispano: http://javahispano.org

Web addresses

The Java Tutorials: http://docs.oracle.com/javase/tutorial/index.html
Pressman Software engineering resources: http://www.rspa.com/spi/
Agile Modeling: http://www.agilemodeling.com/
SCRUM Manual: http://jeffsutherland.com/scrumhandbook.pdf