CHARACTERISTICS AND EVALUATION METHODS OF THE CASE TOOLS

The acronym CASE – Computer Assisted Software Engineering – is the term used to indicate a collection of methods, tools and processes used in the development of software products with the assistance of the computer.IPSE

Accident versus Essence: Investigating the Relationship Among Information Systems Development and Requirements Capabilities and Perceptions of Enterprise Architecture

Information systems (IS) are indelibly linked to the global economy and are indispensable to society and organizations. Despite the decisive function of IS in organizations today, IS development problems continue to plague organizations. The failure to get the system requirements right is considered to be one of the primary, if not the most significant, reasons for this high IS failure rate. Getting requirements right is most notably identified with Frederick Brooks' contention that requirements are the essence of what IT professionals do, all the rest being accidents or risk management. However, enterprise architecture (EA) may also provide the discipline to bridge the gap between effective requirements, organizational objectives, and the actual IS implementations. The intent of this research is to examine the relationship between IS development capabilities and requirements analysis and design capabilities within the context of enterprise architecture. To accomplish this, a survey of IT professionals within the Society for Information Management (SIM) was conducted. Results indicate support for the hypothesized relationship between IS development and requirements capabilities. The hypothesized relationships with the organizational demographics were not supported nor was the hypothesized positive relationship between requirements capabilities and EA perceptions. However, the nature of the relationship of requirements and EA provided important insight into the relationship leading to several explanations as to its meaning and contributions to research and practice. This research contributes to IS development knowledge by providing evidence of the essential role of requirements in IS development capabilities and in IS development maturity. Furthermore, contributions to the nascent field of EA research and practice include key insight into EA maturity, EA implementation success, and the role of IT professionals in EA teams. Moreover, these results provide a template and research plan of action to pursue further EA research in exploring EA maturity models and critical success factors, and the state of practice of EA in organization

Application of the systems approach to defining major projects for successful implementation

Despite advances in project management techniques and greatly improved levels of experience in managing major projects, a significant number of these projects still experience serious problems during implementation resulting in unacceptable loss of functionality with related cost and schedule growth, and sometimes outright cancellation. Research has shown that major contributors to these problems are systematic and can be associated with project size, complexity, technical uncertainty, schedule duration and urgency, physical and social environment, and government and politics. Several authors advocate that the application of systems problem solving methods and techniques during project definition could resolve these systematic problems and should be used to augment traditional project management approaches.This research is concerned with bringing together two important models, one concerned with traditional project definition (the Morris Model) and the other concerned with systems engineering (the M'Pherson Model), and harmonising the result with other systems methods and techniques to form a comprehensive model (to be called the MM Model) for defining major projects for successful implementation. The Morris Model is introduced in Chapter 2 as part of a study into the nature of major projects and what makes them successful or problematic. As part of the study, a compendium of project success criteria is compiled for later testing of the MM Model. Chapter 3 concentrates on discovering how systems methods and techniques, including those that can be categorised under the soft systems banner, could be used in project problem solving. The M'Pherson Model is introduced during the path through the Chapter. An important step in the early life of a project is the approval stage. If decisions regarding a project's viability are to be meaningful, appropriate information for gooddecision making must be generated during the project definition. Project approval is the subject of Chapter 4. The MM Model for project definition is formulated in Chapter 5 and tested firstly against the compiled compendium of project success criteria and, secondly, against three careful selected case studies; British Rail's Advanced Passenger Train, Thames Water's London Water Ring Main, and the Rolls Royce RB 211 Aero-engine. The first case study represents a cancelled project, the second a highly successful project, and the third a project that experienced extreme problems but resulted in a highly successful product. Finally, in Chapter 9 the author provides a reader's guide to the formulation of the MM Model, discusses the extent to which the objectives have been achieved, the contribution to knowledge and possible areas for further work