Look Out Behind

When acquiring a computer-aided software engineering (CASE) tool, a methodology, or other software engineering technique, management information systems (MIS) first must determine whether they are dealing with a symptom or a real problem. Rather than dwelling on symptoms, MIS should focus on the rea...

Full description

Saved in:
Bibliographic Details
Published inComputerworld Vol. 22; no. 42; p. 97
Main Author Yuval, Asher
Format Magazine Article
LanguageEnglish
Published Framingham Foundry 17.10.1988
Subjects
Computer aided software engineering
Computer programming
Management information systems
Software
Software engineering
Techniques
Online AccessGet full text

Cover

More Information
Summary:When acquiring a computer-aided software engineering (CASE) tool, a methodology, or other software engineering technique, management information systems (MIS) first must determine whether they are dealing with a symptom or a real problem. Rather than dwelling on symptoms, MIS should focus on the real problems facing software engineers, the most fundamental of which include: 1. a lack of physical properties, 2. the flexibility-to-rigidity shift, 3. transformation issues, and 4. an informal-to-formal shift. Other problems that are more difficult to classify are "small" details problems, user involvement problems, lack of a computer science, and psychological problems. A software solution that purports to reduce maintenance through CASE tools should include the following: 1. well-defined and easily measured software characteristics, 2. flexible database and module definitions, and 3. a minimum quantity of stages in the life cycle, with straightforward transformation between stages.
Bibliography:ObjectType-Article-2
SourceType-Scholarly Journals-1
ObjectType-Feature-1
content type line 23
ISSN:0010-4841