1. Management of Software1 Advanced Software Engineering COM360 University of Sunderland © 1998

2. Management of Software2 Management of…. 4The nature of software 4The environment of software 4Management concerns... 4 3Ps, people, problem, process 4Project planning 4Software quality

3. Management of Software3 The Nature of Software Software is…… code, documentation, and data but it’s more…… created, complex, doesn’t wear out, shelf life (often short!)

4. Management of Software4 The Environment of Software requirements business issues cost/budget timescale project technology available human resources available devt. environment size

5. Management of Software5 Management Concerns 4 3 Ps ; 4 people 4 problem 4 process

6. Management of Software6 Management Concerns - People (1) “The most important ingredient was having smart people…...very little else matters in my opinion…..” “The only rule I have …. is to ensure I have good people….. and an environment in which good people can produce.”

7. Management of Software7 Management Concerns - People (2) The ‘constituents’: 4Senior Managers 4Project Managers 4Practitioners/Developers 4Customer and ‘end-users’

8. Management of Software8 Management Concerns - People (3) Project Managers - are project leaders... Jerry Weinberg’s model of leadership…. Edgemon gives 4 key traits….

9. Management of Software9 Weinberg’s Model of Leadership Motivation - ability to ‘push / pull’ technical staff Organisation - to revise old, or create new, processes to do the job Ideas / Innovation - to encourage creativity within the boundaries of the project

10. Management of Software10 Edgemon’s Key Traits Problem solving - diagnosing technical and organisational issues, structuring a solution or motivating others to, applying lessons learnt Identity - ability to assume control when necessary and encourage others similarly Achievement - reward accomplishment Team building - ‘read’ and react appropriately to others, foster intercommunication, remain in control

11. Management of Software11 Management Concerns - People (4) Team structure: Democratic Decentralised (DD) Controlled Decentralised (CD) Controlled Centralised (CC)

12. Management of Software12 Management Concerns - People (5) Co-ordination and Communication: ~Formal, impersonal approaches ~Formal, interpersonal procedures ~Informal, interpersonal procedures ~Electronic communication ~Interpersonal network

13. Management of Software13 Management Concerns - Problem The need is; planning, organisation & estimates, but often solid information is unavailable and requirements are still fluid. Project scope must be determined; context, information objectives, function & performance. Problem decomposition, partitioning; applied to functionality required, process for delivery.

14. Management of Software14 Management Concerns - Process Generic phases (definition, development, testing) are applicable to all process models. The trick is to choose and combine the right models and develop the framework of tasks. A common framework of tasks supports structure and ensures tasks are not omitted.

15. Management of Software15 Project Planning (1) “If we fail to plan, we plan to fail….” anon. Objective: Provide a framework for understanding the scope of the problem and for making estimates of resources, cost and schedule.

16. Management of Software16 Project Planning (2) 4scope the problem 4use historical data (measurements) 4decompose the problem (divide & conquer) 4estimate function and effort 4risk analysis 4work breakdown structure 4schedule

17. Management of Software17 Software Quality - Definition “The totality of features and characteristics of a product or service that bear on its ability to satisfy stated or implied needs.” - ISO 8402

18. Management of Software18 Software Quality 4policy 4management system 4plan 4procedures 4standards