A presentation of the motivation, contents, and organization of the forthcoming Software Engineering II course at Politecnico di Torino

1. Software Engineering II
Version 1.3.0 - May 2019
© Marco Torchiano Antonio Vetrò, 2019
Course Overview
Marco Torchiano, Antonio Vetrò

2. Software Engineering
 Attended SE course?
 You know the basics of SE
“You know nothing
Jon Snow!”
- Ygritte

3. SOFTWARE + ENGINEERING

4. Software
..is the invisible language that
whispers stories of possibility
to the hardware
- Grady Booch

5. Engineering
 Design: the intentional solution to a
problem within a set of constraints
 Construction: planning, monitoring,
controlling the activities to achieve a
solution, tools and techniques
 Operation: conduction of the solution
and adaptation, within its limits

6. Construction
 How does Sw development work in
practice?
 Effort estimation
 Planning development and release
 Day-by-day practices
 Customer relationship
 Acquisition
 …

7. Software life cycle processes
Primary processes Supporting processes
Organisational processes
Acquisition
Supply
Development
Maintenance
Operating
Documentation
Configuration
management
Quality
management
Management Improvement Infrastructure Training
https://ieeexplore.ieee.org/servlet/opac?punumber=4475822
ISO/IEC 12207

8. Agile manifesto - Values
 Individuals and interactions
 over processes and tools
 Working software
 over comprehensive documentation
 Customer collaboration
 over contract negotiation
 Responding to change
 over following a plan

9. From manifesto to practice
 Tight collaboration between developers
and stakeholder
 over the entire course of the project
 Self-organizing teams
 Software SCRUM is the most used
methodology
 Other methodologies like Kanban and
eXtreme Programming are less used

10. Software SCRUM
 User stories
 Estimation
 Planning
 Tight
Feedback Loops
 Reflection

11. Software Quality
 Quality is a key component in any
engineering practice
 How does it work in Sw engineering?
 Sw analytics allow measuring and
controlling Sw projects
 Code smells indicate possible problems
 Technical debt

12. Evolution
 Evolution is intrinsic in software
 How do you tame it?
 Advanced debugging methods,
 Log analysis
 Reverse engineering

13. Course Organization
 Theory + Practice
 Roughly 50% + 50%
 Short theory presentations then
application in practice
 Team project work
 Individuals and interaction
 Customer collaboration
 Self-organizing teams

14. In summary