Question? Leave a message!




Software Project Management

Software Project Management 17
EdenKelly Profile Pic
EdenKelly,United States,Professional
Published Date:12-07-2017
Website URL
Comment
Software Project Management Daniel M. Berry with material from James E. Tomayko 1994 Daniel M. Berry Software Enginering Software Project Management Pg. 1 ©Nature of Software Production SOFTWARE — program system product (PSP) PROJECT — planned MANAGEMENT — make sure that the PSP comes out as planned 1994 Daniel M. Berry Software Enginering Software Project Management Pg. 2 ©Software -1 We are not talking about programs, but about program system products (PSP) We all know all about programs, but what about PSPs? Fred Brooks explains the difference and shows the effort involved (multipliers may be bigger if the number of components is large): 1994 Daniel M. Berry Software Enginering Software Project Management Pg. 3 ©Software -2 Program Program x 3 Product x 3 x 9 x 3 Program Program x 3 System System Product 1994 Daniel M. Berry Software Enginering Software Project Management Pg. 4 ©Program: • program is complete by itself • program is ready to run by author for planned inputs on system on which it was developed, and probably under no other circumstances 1994 Daniel M. Berry Software Enginering Software Project Management Pg. 5 ©Program System: • each program is a component in integrated collection (system) • precisely defined interface to which all programs in system must comply • each program must stick to reasonable resources • each program is tested with other programs; number of combinations grows quadratically with each additional program 1994 Daniel M. Berry Software Enginering Software Project Management Pg. 6 ©Program Product: • product can be run, tested, repaired, extended by anyone, not just author • product runs on multiple platforms • product accommodates many sets of data • range and form of input to product must be generalized • product must test for validity of input and provide response to invalid inputs • must be product documentation for maintainers and users 1994 Daniel M. Berry Software Enginering Software Project Management Pg. 7 ©Program System Product: • all attributes of program system and • all attributes of program product 1994 Daniel M. Berry Software Enginering Software Project Management Pg. 8 ©Programs vs. PSPs -1 Perhaps the key problem in SPM is that when we should be thinking about PSPs, we continue to think about programs, and all expectations, • ease vs. difficulties, • time, • costs, • you name it, are off by an order of magnitude. 1994 Daniel M. Berry Software Enginering Software Project Management Pg. 9 ©Programs vs. PSPs -2 We see only the program in the heart of the PSP and forget all the other junk that must be added to make it a PSP 1994 Daniel M. Berry Software Enginering Software Project Management Pg. 10 ©Project The objective of the project to build a PSP is to make sure that all the necessary junk gets planned in. Projects have plans: • Specific work to do • Deliverables • Resources - Multiple People - Schedule - Budget 1994 Daniel M. Berry Software Enginering Software Project Management Pg. 11 ©Management -1 Any project with more than one person must be managed by definition, just to keep the communication going between the folk in the project. Note that the management does not need to be applied externally, the manager can be one of the managed folk 1994 Daniel M. Berry Software Enginering Software Project Management Pg. 12 ©Management -2 The job of management is to make sure that the planned junk does not get left behind in the zeal to release the PSP when only the program in its heart has been written 1994 Daniel M. Berry Software Enginering Software Project Management Pg. 13 ©Management -3 • Control leads to quality. • Deliver what you promise. • Allocate resources properly. • Communicate and facilitate communication. 1994 Daniel M. Berry Software Enginering Software Project Management Pg. 14 ©Truths about Management Boehm says: “Poor management can increase software costs more than any other factor”. “Poor management can decrease software productivity more rapidly than any other factor” “The single most important factor in the success of a (multi-person) software project is the talent of its project manager” 1994 Daniel M. Berry Software Enginering Software Project Management Pg. 15 ©Production of Managers Mark Kellner goes so far as to say: “The software engineering profession has not produced a cadre of capable/competent managers.” Promotion up the technical ladder requires skills different from those needed by a manager. 1994 Daniel M. Berry Software Enginering Software Project Management Pg. 16 ©Basic Equation Profit = Revenues Expenses Usually revenues are fixed, either by contract or by the market. Therefore to maximize, or even to guarantee, profit, it is essential to reduce expenses or costs. Cannot reduce anything unless you know what it is. 1994 Daniel M. Berry Software Enginering Software Project Management Pg. 17 © -Required Knowledge Therefore, we gotta know what the costs are. More importantly, we gotta what they will be if we’re using projected costs to determine what the price (i.e., revenues) is. 1994 Daniel M. Berry Software Enginering Software Project Management Pg. 18 ©Multi-pronged attack Actually, there is a mirror image to reducing costs that has the same net effect, when it is done right. • Reducing costs • Increasing productivity 1994 Daniel M. Berry Software Enginering Software Project Management Pg. 19 ©Reducing Costs To reduce cost, you have to know what you’re spending and where you’re spending it. 1994 Daniel M. Berry Software Enginering Software Project Management Pg. 20 ©