Software project management kemerer

Kemerer, S. Slaughter, M. Kemerer, and J. Liu and M. Smith , Communications of the ACM, v. PhD Apply Now. Faculty Overview Directory News. Academics Overview Job Placements. Overview Alumni Testimonials. This study develops and empirically tests the idea that the impact of structural complexity on perfective maintenance of object-oriented software is significantly determined by the team strategy of programmers independent or collaborative.

We analyzed two key dimensions of software structure, coupling and cohesion, with respect to the maintenance effort and the perceived ease-of-maintenance by pairs of programmers. Hypotheses based on. On the uniformity of software evolution patterns more. Towards a metrics suite for object oriented design more. ABSTRACT While software metrics are a generally desirable feature in the software management functions of project planning and project evaluation, they are of especial importance with a new technology such as the object-oriented ABSTRACT While software metrics are a generally desirable feature in the software management functions of project planning and project evaluation, they are of especial importance with a new technology such as the object-oriented approach.

Software Development. Worldwide: The State of the Practice more. Software Complexity and Maintenance Costs more. Many of the attempts to link software Many of the attempts to link software complexity to maintainability are based on Software Maintenance and Software Complexity.

Systems developers and researchers have long been interested in the factors that affect software development productivity. Identification of factors as either aiding or hindering productivity enables management to take steps to encourage Identification of factors as either aiding or hindering productivity enables management to take steps to encourage the positive influences and to eliminate the negative ones.

This research has explored the possibility of developing an estimable model of software development productivity using a frontier estimation method.

The approach taken is based upon output metrics for the entire project life-cycle, and includes project quality metrics. A large number of factors potentially affecting software maintenance productivity were included in this initial investigation.

The empirical analysis of a pilot data set indicated that high project quality did not necessarily reduce project productivity. Significant factors in explaining positive variations in productivity included project team capability and good system response turnaround time.

Factors significantly assoc Computer, , Vol. Object-oriented OO technology represents one of the most important innovations in software process technology to emerge in the last twenty years. We found the burden of learning how to use the technology and the costs of joining an immature technological network were the most serious adoption challenges.

The required project team members and resources office space, project team equipment needs etc. To achieve this, a new internet based facility will be developed.

To ensure that they get it right this time the following high level requirements have been agreed. Business Requirements: 1. The system will be functionally simple so that customers will find it easy to use 3. A secure system is essential but ease of use must not be sacrificed. An IT architecture plan must be developed.

All new hardware, network infrastructure and security solutions will be purchased under a Request for Proposal process. A pilot version of the new system must be built, tested and evaluated 4.

Software Requirements: 1. Staff issues — many of the current problems can be attributed to staff issues involving dissatisfaction with working conditions and poor management leading to high staff turnaround. This exacerbated many technical problems because of the loss of corporate knowledge. This has been unsatisfactory and has contributed to both staff issues and the unreliable service of the current IT systems.

Poor architectural planning - this is probably the most important lesson learnt. The overall hardware and software architecture and design was not good enough. The high cost of maintenance. Teaching Assistant. Subrahmantam, Shyamsundar Shyam , E-mail : subrahmanyams yahoo. Required Textbook.

PMBOK Case studies, other documents. Bennatan, E. Kemerer, Chris F. Course Description. Project management techniques and their application to the management of software projects. How to develop a software development plan and its associated tasks, milestones and deliverables. Software project scheduling and the establishment of relationships among the different tasks. Tasks, dependencies and conflict resolution. Resource management and allocation. Software project cost estimation.

Risk assessment and its impact in the planning and scheduling of software projects. Software project measurement and tracking. Comparative review of software tools for software project management. Software configuration management and its importance in the management of large software projects.

Project management in the large and in the small.