Just-In-Time Systems for Computing Environments

Just-In-Time Systems for Computing Environments

Just-In-Time Systems for Computing Environments

Just-In-Time Systems for Computing Environments


In the information highway age, Just-In-Time Systems - JITS - are becoming increasingly visible: customers want to purchase rather than develop customized computing systems and they want these systems now. JITS will allow for developing systems at the right time, in the right place, and at the right price to address the right needs. This is promoted by covenant relationships between customer and supplier; JITS developers recognize that all system development projects and their maintenance have commonalities. They can apply technical, operational, and managerial approaches to similar problems - the management structure or system components of a project, for example, may be applicable to similar projects and follow similar lifecycles. JITS developers, therefore, avoid "reinventing the wheel". JITS will not appear overnight; its adoption will only come through evolution, not revolution. This incremental growth does not, however, imply that it's not revolutionary in substance. Managers, designers, programmers, engineers, analysts, planners, librarians, quality assurance specialists, customers, users, and suppliers of computing systems can benefit from this book.


Contrary to popular belief, a systems crisis doesn't exist. Instead, it's a tragedy that functions as an open sore, draining the life blood of small, medium, and large firms. Cost overruns, schedule slides, and poor quality have become commonplace as professionals and users alike shrug their shoulders and respond, "Oh well, that's the world of systems."


Capers Jones, president of Software Productivity Research, Inc., conducted a study of large systems (that is, ones exceeding 64,000 lines of code) and revealed some startling statistics. He noted that a quarter of the systems were abandoned before completion and never used; that 60 percent "significantly" overran cost and schedule budgets; that less than 1 percent finished on time and within budget; and that the "average" large system was a year or more late and doubled in cost.

A recent study of 115 organizations noted that very little improvement in systems performance has occurred. It noted that more than 75 percent of the respondents did not meet typical performance criteria (schedule, cost, and quality) for development projects. In addition, it noted that 63 percent of those respondents exceeded their budget.

The General Accounting Office also conducted a review of its reports on developing large systems and had similar findings. It concluded that most systems under development had extended development cycles and overran budget estimates. In fact, it even noted that many systems did not meet users' needs and did not work.

Most of the leading computing publications confirm the above studies . . .

Search by... Author
Show... All Results Primary Sources Peer-reviewed


An unknown error has occurred. Please click the button below to reload the page. If the problem persists, please try again in a little while.