Go to:
Logótipo
Esta página em português Ajuda Autenticar-se
Formação regular da Biblioteca |fevereiro a maio
Today is sunday
You are here: Start > EIC0024
Authentication




Site map
Edifício A (Administração) Edifício B (Aulas) - Bloco I Edifício B (Aulas) - Bloco II Edifício B (Aulas) - Bloco III Edifício B (Aulas) - Bloco IV Edifício C (Biblioteca) Edifício D (CICA) Edifício E (Química) Edifício F (Minas e Metalurgia) Edifício F (Minas e Metalurgia) Edifício G (Civil) Edifício H (Civil) Edifício I (Electrotecnia) Edifício J (Electrotecnia) Edifício K (Pavilhão FCNAUP) Edifício L (Mecânica) Edifício M (Mecânica) Edifício N (Garagem) Edifício O (Cafetaria) Edifício P (Cantina) Edifício Q (Central de Gases) Edifício R (Laboratório de Engenharia do Ambiente) Edifício S (INESC) Edifício T (Torre do INEGI) Edifício U (Nave do INEGI) Edifício X (Associação de Estudantes)

Software Engineering

Code: EIC0024     Acronym: ESOF

Keywords
Classification Keyword
OFICIAL Software Engineering

Instance: 2014/2015 - 1S Ícone do Moodle

Active? Yes
E-learning page: https://moodle.fe.up.pt/
Responsible unit: Department of Informatics Engineering
Course/CS Responsible: Master in Informatics and Computing Engineering

Cycles of Study/Courses

Acronym No. of Students Study Plan Curricular Years Credits UCN Credits ECTS Contact hours Total Time
MIEIC 123 Syllabus since 2009/2010 3 - 6 56 162

Teaching - Hours

Lectures: 2,00
Recitations: 2,00
Type Teacher Classes Hour
Lectures Totals 1 2,00
Nuno Honório Rodrigues Flores 2,00
Recitations Totals 6 12,00
Nuno Honório Rodrigues Flores 4,00
Hugo José Sereno Lopes Ferreira 8,00

Teaching language

Portuguese

Objectives

This course aims to acquaint students with the engineering and management methods necessary for the cost-effective development and maintenance of high-quality complex software systems.

Learning outcomes and competences

At the end of the semester, students should:



    • be capable of describing the principles, concepts and practices of software engineering and software life cycle;

 

    • be acquainted with and be capable of applying the required tools and techniques to carry out and manage the various tasks in the development of high quality software;

 

    • be capable of explaining the development methods and processes of different types of software systems.

 

Working method

Presencial

Program

1. INTRODUCTION: large scale software development chalenges; objectives and scope of software engineering.

2. SOFTWARE PROCESS: concept of software process; process models; process activities; performance metrics; agile methods; example of the Rational Unified Process.

3. SOFTWARE PROJECT MANAGEMENT: software estimation; project planning, monitoring and control; classic and agile project managament; team organization and management; risk management.

4. REQUIREMENTS ENGINEERING: software requirements; the requirements document; requirements engineering process; requirements modeling with UML (use case diagrams and activity diagrams); user interface prototyping.

5. SOFTWARE DESIGN: architectural design; architectural modeling with UML (deployment, component and package diagrams); reuse (components, frameworks and product lines); detailed design.

6. SOFTWARE CONSTRUCTION: integrated development environments; rapid development environments; model-driven development environments; continuous integration; version control; agile development with XP.

7. SOFTWARE VERIFICATION AND VALIDATION: basic concepts; unit, integration, system and acceptance testing; software inspections and reviews; defect tracking; static code analysis.

8. SOFTWARE EVOLUTION: evolution processes; dynamics of program evolution; software maintenance; legacy systems; reverse engineering and software re-engineering.

9. PROCESS IMPROVEMENT: software process lifecycle; measurement; process improvement with the PSP/TSP; the CMMI maturity model.

Mandatory literature

Ian Sommerville; Software engineering (9th edition), Addison-Wesley, 2011. ISBN: 9780137035151

Complementary Bibliography

Russ Miles & Kim Hamilton; Learning UML 2.0, O'Reilly, 2006. ISBN: 0-596-00982-8
Silva, Alberto Manuel Rodrigues da; UML, metodologias e ferramentas CASE. ISBN: 989-615-009-5
Humphrey, Watts S; A discipline for Software engineering. ISBN: 0-201-54610-8

Teaching methods and learning activities

Theoretical classes will be based on the oral presentation of the themes and description of problems, as well methodology analysis and solutions/good practices. Theoretical-practical classes will be based on exercises, small projects and research work.

Software

Eclipse
Enterprise Architect

Evaluation Type

Distributed evaluation with final exam

Assessment Components

Designation Weight (%)
Exame 62,50
Participação presencial 0,00
Trabalho escrito 37,50
Total: 100,00

Amount of time allocated to each course unit

Designation Time (hours)
Elaboração de projeto 28,00
Estudo autónomo 78,00
Frequência das aulas 56,00
Total: 162,00

Eligibility for exams

Obtaining a minimum grade of 45% in the assignements.

Calculation formula of final grade

Final Mark will be based on the following formula: FM= 0,65*FE + 0,35*A where FE is the classification in Final Exam and A is classification in assignments.

Assignments comprise:

- realization of small experiments and exercises (4 classes) - 1 value (0.25 per class);

- modeling project - 4 values;

- bibliographic research project - 2 values.

To complete the course students have to: FM>=9,5 Reach a minimum mark of 45% in the two components In the case of students that, by justified reasons, miss the classes where the small experiments and exercises are conducted, will have the corresponding weight transfered to the final exam.

Special assessment (TE, DA, ...)

All assignments are mandatory even to students who have a special status. It is valid last year’s continuous assessment mark.

Classification improvement

Students can improve the mark of the exam in recurso (resit) season. Students can improve the mark of the assignments in the following year.

Observations

It is recommended that, for attending this course, students have completed LPOO.

Recommend this page Top
Copyright 1996-2019 © Faculdade de Engenharia da Universidade do Porto  I Terms and Conditions  I Accessibility  I Index A-Z  I Guest Book
Page generated on: 2019-05-26 at 17:11:08