scientific article; zbMATH DE number 108418

Authors Wolfgang Hesse, Günter Merbeth, Rainer Frölich

Publication date 23 January 1993

action models CASE-Tools configuration management documentation support life cycle models project management quality assurance software development software engineering software maintenance

Mathematics Subject Classification ID

Introductory exposition (textbooks, tutorial papers, etc.) pertaining to computer science (68-01) Theory of software (68N99)

Review text

The book covers three subject areas: fundamentals of software engineering, project management, software maintenance. At the begin a historical outline of software engineering. The major stages are programming languages, structured programming, programming environments, structured analysis and structured design, and CASE. Life cycle models are the focus in the first sub-area. Types of phase models, action models and project models are explained. One of the most important aspects is the connection between the phases. That yields linear, circular and evolutionary forms of models. The authors suggest a generalization of models and derive a so-called landscape of software development. The landscape is characterized by means of areas for requirements, design, integration and application. In addition, a meta- model of software development is derived. Project management involves planning, tracing and quality assurance. It concerns members of development teams and mile-stones of projects. The evaluation of expense is based on the function point method. Quality assurance is related to review and inspection. In addition, automatic tests are explained. In that context quality assurance tools are described, too. Part three contains software maintenance. The sub-topics are requirements to data storage, integration of CASE-Tools and CASE-Repositories. Requirements concern storage of documents, project management, configuration management and CASE-Tools. The integration of tools is shown as string and as shell-architecture. CASE-Repositories are based on relational and ER- or ERA-structures. The differences and examples of repositories are discussed. It follows a chapter on documentation support. Some aspects of configuration management are shown at the end.

Cited in

(5)

This page was built for publication:

Report a bug (only for logged in users!)Click here to report a bug for this page (MaRDI item Q4023875)