In conclusion, we explore in this paper the ontological distinctions underlying the different reasons for software change, by making a sharp distinction between different kinds of software artifacts, and describing the ways they are connected in the context of a software engineering process. While doing so, on one hand we shall take inspiration from the requirements engineering literature to better understand the ontological nature of software, and on the other hand we shall leverage on such ontological analysis to better understand the software engineering process, especially in the light of software change management.