Day |
Date |
Content |
1 |
01/08/2016 |
Part 1: Course introduction, books, papers, assessment criteria, final project, etc.
|
2 |
08/08/2016 |
Part 1: Introduction to software quality
Part 2: Introduction to software measurement
Part 3: Examples of Product Metrics
Part 4: Metrics for Object-Oriented Programs
|
3 |
17/08/2016 |
Part 1: Exercise about Software Measurement
|
4 |
22/08/2016 |
Part 1: Introduction to Empirical Software Engineering
Part 2: Empirical Strategies
Part 3: Survey
Part 4: Case Study
Part 5: Experiment
|
5 |
24/08/2016 |
Part 1: Measurement and Scales
Part 2: Classification of Measures
Part 3: The Goal-Question-Metric Method (GQM)
Part 4: Experiment Scoping
|
6 |
29/08/2016 |
Part 1: Refactoring
Part 2: Examples of Refactoring
Part 3: Bad Smells in Code
Part 4: Software Code Clone (Duplicated Code)
|
7 |
31/08/2016 |
Part 1: Metric Thresholds
Part 2: Definition of Detection Strategies
Part 3: Examples of Detection Strategies
Part 4: Tools for Bad Smell Detection
Final Project: Deadline for abstracts is today
|
8 |
05/09/2016 |
Part 1: Separation of Concerns
Part 2: Concern Metrics
Part 3: Concern-Sensitive Detection Strategies
|
9 |
12/09/2016 |
Part 1: Exercise
|
10 |
14/09/2016 |
Paper 1: When and Why Your Code Starts to Smell Bad
Paper 2: Why Good Developers Write Bad Code: an Observational Case Study of the Impacts of Organizational Factors on Software Quality
Discussions and summary
|
11 |
19/09/2016 |
Exercise: Review for the 1st Exam
|
12 |
21/09/2016 |
1st Exam
|
13 |
26/09/2016 |
Part 1: Software Visualization
Part 2: Distribution Map
Part 3: Visualizing Crosscutting Concerns
|
14 |
28/09/2016 |
Paper 1: A Review-based Comparative Study of Bad Smell Detection Tools
Paper 2: Identifying Code Smells with Multiple Concern Views
Discussions and summary
|
15 |
03/10/2016 |
Part 1: Design Patterns (GoF)
Part 2: Structural Design Patterns
|
16 |
05/10/2016 |
Part 1: Software Architecture
Part 2: Architectural Patterns (POSA)
Part 3: Architectural Patterns: From Mud to Structure
|
17 |
10/10/2016 |
Part 1: Architectural Patterns: Distributed Systems, Interactive Systems, and Adaptable Systems
Part 2: Software Engineering Principles (S.O.L.I.D)
|
18 |
17/10/2016 |
Paper 1: Applying and Evaluating Concern-Sensitive Design Heuristics
Paper 2: On the Effectiveness of Concern Metrics to Detect Code Smells: An Empirical Study
Discussions and summary
|
19 |
19/10/2016 |
Paper 1: Defining Metric Thresholds for Software Product Lines: A Comparative Study
Paper 2: A Method to Derive Metric Thresholds for Software Product Lines
Discussions and summary
|
20 |
24/10/2016 |
Part 1: Exercise
|
21 |
26/10/2016 |
Parte 1: Software Process
Parte 2: Waterfall Model
Parte 3: Agile Software Development
Parte 4: Scrum
Parte 5: Software Process Improvement
Parte 6: CMMI
|
22 |
31/10/2016 |
Paper 1: Are Students Representatives of Professionals in Software Engineering Experiments?
Paper 2: The Emerging Role of Data Scientists on Software Development Teams
Discussions and summary
|
23 |
07/11/2016 |
Paper 1: Preliminary Guidelines for Empirical Research in Software Engineering
Paper 2: Avoiding Code Pitfalls in Aspect-Oriented Programming
Discussions and summary
|
24 |
09/11/2016 |
Paper 1: Measuring Programming Experience
Part 2: Review for the 2nd Exam
Discussions and summary
|
25 |
16/11/2016 |
2nd Exam
|
26 |
21/11/2016 |
Part 1: Review for the 3rd Exam
|
27 |
23/11/2016 |
3rd Exam (optional)
|
28 |
28/11/2013 |
Workshop on Software Engineering (WSE): Final Project
Presentation Ordering: Each talk must last between 10 and 15 minutes.
|
29 |
30/11/2016 |
Workshop on Software Engineering (WSE): Final Project
Presentation Ordering: Each talk must last between 10 and 15 minutes.
|
30 |
05/12/2016 |
Workshop on Software Engineering (WSE): Final Project
Presentation Ordering: Each talk must last between 10 and 15 minutes.
|
gmail.com