Browse Prior Art Database

Validating Solutions to Major Problems in Software Engineering Project Management

IP.com Disclosure Number: IPCOM000131528D
Original Publication Date: 1982-Aug-01
Included in the Prior Art Database: 2005-Nov-11
Document File: 18 page(s) / 58K

Publishing Venue

Software Patent Institute

Related People

Richard H. Thayer: AUTHOR [+5]

Abstract

University of California, Santa Barbara

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 7% of the total text.

Page 1 of 18

THIS DOCUMENT IS AN APPROXIMATE REPRESENTATION OF THE ORIGINAL.

This record contains textual material that is copyright ©; 1982 by the Institute of Electrical and Electronics Engineers, Inc. All rights reserved. Contact the IEEE Computer Society http://www.computer.org/ (714-821-8380) for copies of the complete work that was the source of this textual material and for all use beyond that as a record from the SPI Database.

Validating Solutions to Major Problems in Software Engineering Project Management

Richard H. Thayer, California State University, Sacramento Arthur Pyster and Roger C. Wood,

University of California, Santa Barbara

A survey of software engineering managers reveals that project success is related to planning, organizing, and control, but more research is needed to find out exactly how and why.

In August of 1980, we wrote an articles in which we hypothesized 20 major software engineering project management problems. (To avoid later confusion, we define a "software engineering project" as a software development task that has a prescribed starting point, a specific budget and resources, established responsibilities, and a completion schedule.) We also conducted an opinion survey on a sample of the data processing industry to verify these hypothesized SEPM issues. Our sample consisted primarily of senior computer scientists, authors and lecturers on software engineering and project management, software development project managers, and highly visible individuals who, because of their position in industry, government, and universities, influence the opinion of the computing community.

Below is a listing of the twenty problems used in our survey.

Planning Problems

1. Plan Requirements:

Requirement specifications are frequently incomplete, ambiguous, inconsistent, and/or unmeasurable.

2. Plan Success:

Success criteria for a software development are frequently inappropriate, which results in poor "quality" delivered software; i.e., not maintainable, unreliable, difficult to use, relatively unit documented, etc.

3. Plan Project:

Planning for software engineering projects is generally poor.

4. Plan Cost:

The ability to estimate accurately the resources required to accomplish a software development is poor.

IEEE Computer Society, Aug 01, 1982 Page 1 IEEE Computer Volume 15 Number 8, Pages 65-77

Page 2 of 18

Validating Solutions to Major Problems in Software Engineering Project Management

5. Plan Schedule:

The ability to estimate accurately the delivery time on a software development is poor.

6. Plan Design:

Decision rules for use in selecting the correct software design techniques, equipment, and aids to be used in designing software in a software engineering project are not available.

7. Plan Test:

Decisionrulesforuseinselectingthecorrect procedures, strategies, and tools to be used in testing software developed in a software engineering project are not available.

8. Plan Maintainability:

Procedures, techniques, and strateg...