Project Management: Three ways to look at stages

My journey towards a Bachelors degree continues, now with the OU Module M258 (IT Project and Service Management). As I continue to study the module, I will write down my thoughts on various subjects. Like with my first module, TU100, these will all be collected under a category for easy reference. This time, unsurprisingly, the category will be M258.
 
These days, I am making my first serious foray into the world of Project Management, as I am studying the Open University’s module M258 (IT Project and Service Management). From working with the first chapter of our assigned text book I have gleaned the following three ways to look at the stages of a (software) project:
 
The basic overview

• Feasibility Study
• Planning
• Project Execution

(Hughes and Cotterell, 2009, p.5)
 
The Software Development specific overview

• Requirements Analysis
• Architecture Design
• Detailed Design
• Code and Test
• Integration
• Qualification Testing
• Installation
• Acceptance Support

(Hughes and Cotterell, 2009, pp. 6-8)
 
The detailed stage overview

• Project Evaluation
• Planning
• Requirements Elicitation and Analysis
• Specification
• Design/Coding
• Verification and Validation
• Implementation
• Maintenance and Support

(Hughes and Cotterell, 2009, p. 338)
 
While these three are all variations over the same basic theme, I find it interesting to see how the different parts of the basic overview can be broken down. Comparing the first and the last list, the latter breaks down into the first roughly as follows:
 
Feasibility study:

• Project Evaluation

Planning

• Planning
• Requirements Elicitation and Analysis
• Specification

Project execution

• Design/Coding
• Verification and Validation
• Implementation
• Maintenance and Support

 
Hughes, B and Cotterell, M (2009) Software Project Management, London, McGraw Hill