By Topic

CASE (Computer Aided Software Engineering): Towards Software Process Maturity, IEE Colloquium on (Digest No.1993/222)

Date 22 Nov 1993

Filter Results

Displaying Results 1 - 8 of 8
  • CASE tools and method integration

    Page(s): 7.1 - 7.5
    Save to Project icon | Click to expandQuick Abstract | PDF file iconPDF (288 KB)  

    Discusses the Software Process Maturity Model (SPMM). Its notions of process improvement and statistically based control of the main production activities are seen as the base concepts underlying the total quality movement, with its stress on continuing improvement against measured standards of achievement. Unfortunately the central focus of the TQ movement has excluded or been indifferent to many concerns central to the domain of information systems and software engineering, and only recently has this begun to be redressed. The author considers how the SPMM, now in its amended form of the Capability Maturity Model (CMM), represents the most sustained attempt to extend the TQ perspective to software-based systems: not a simple task, since the production-based assumptions of TQ do not transfer easily to the processes of information systems and software development View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Beyond the SEI maturity model: transforming systems development through the use of IT

    Page(s): 4.1 - 4.4
    Save to Project icon | Click to expandQuick Abstract | PDF file iconPDF (160 KB)  

    Surveys of CASE users show that software development quality and productivity have improved as a result of CASE (Wijers and van Dort, 1990, Stobart et al., 1991 and Aaen et al., 1992). However, these results are based on the perception of IS managers and have yet to be supported by figures. What is required is a change in organisation supported by a change in technology. The SEI Software Process Maturity Model (Humphrey, 1989) quite rightly recommends that the process should not be automated until it has been understood. However, even with well-planned automation there is a danger that the efficiency of the process will be improved without improving process effectiveness, in other words we continue to do the same work, but quicker. In this paper the transformation of software/IS development is examined View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • IEE Colloquium on `CASE (Computer Aided Software Engineering): Towards Software Process Maturity' (Digest No.1993/222)

    Save to Project icon | Click to expandQuick Abstract | PDF file iconPDF (16 KB)  

    The following topics were dealt with: software quality, software process maturity and CASE; CASE strategy development; the enabling role of CASE-engineered CASE in optimizing the software process; information systems development, the influence of CASE; software process maturity and the Capability Maturity Model; system modelling problems and methods for software development with CASE; and CASE tools and method integration View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Process: a suitable CASE for improvement

    Page(s): 1.1 - 1.3
    Save to Project icon | Click to expandQuick Abstract | PDF file iconPDF (192 KB)  

    With the increase in organisational maturity, the software process is institutionalised through policies, standards and organisational structures. The question is how does CASE fit in with this growing maturity. In other words, what CASE strategies should be developed and what impact will they have on the organisational structures. The author considers how one should develop a CASE strategy View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • The enabling role of CASE-engineered CASE in optimizing the software process

    Page(s): 3.1 - 3.4
    Save to Project icon | Click to expandQuick Abstract | PDF file iconPDF (240 KB)  

    AT&T ISTEL has been operating a software process improvement programme. This paper focuses on the role which our in-house corporate CASE has played in enabling that programme to meet its goals. As the programme is business-critical and its goals timeless, a critical success factor for the CASE tool has been its ability to continuously improve as the business processes it supports need to improve. To this end the CASE tool has itself been engineered using CASE. This paper shows the pivotal role of CASE-engineered CASE in optimizing key software processes without our organization View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • CASE, software process maturity (SPM) and the Capability Maturity Model (CMM)

    Page(s): 5.1 - 5.4
    Save to Project icon | Click to expandQuick Abstract | PDF file iconPDF (172 KB)  

    Many organisations, including some of the largest ones, have moved away from `all-singing all dancing' CASE solutions to `budget' CASE tools providing support for only a fraction of their total software development activities. Other organisations are focusing their efforts on the software process and how to increase its maturity. Key issues for them are how it can be defined, measured, improved and eventually automated. Are these two `philosophies', CASE and process, mutually exclusive alternatives or can thoughtful organisations put CASE and process together to get real benefits? This paper contends that they can and will look at the relationships between CASE and process and explore the issues surrounding the question of whether one needs advanced maturity for CASE or CASE for advanced maturity View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Methods for software development with CASE-avoiding mind-set traps

    Page(s): 6.1 - 6.8
    Save to Project icon | Click to expandQuick Abstract | PDF file iconPDF (464 KB)  

    Some problems of system modelling and CASE technology are examined. In particular, the paper examines our tendency for us to continue to think in the same way (conceptual inertia), even when new approaches are called for. This can cause us to behave inappropriately, because we are not aware of the required change (a `mind-set trap'). In particular, the underlying paradigm used in system development must be changed for full advantage to be taken of CASE. CASE tools should provide a generic framework to support integration of different paradigms and knowledge domains. Finally, the very idea of process maturity is examined to see if it contains implicit assumptions about the way systems will be provided View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.
  • Quality, process maturity and CASE

    Page(s): 2.1 - 2.2
    Save to Project icon | Click to expandQuick Abstract | PDF file iconPDF (104 KB)  

    Product quality depends upon processe quality: it is the process that delivers the required attributes, and as soon as we start asking any interesting questions about a software product we immediately have to ask questions about the process. Against this background, the author asks: what is the relationship between process maturity and process quality; and what is the role of CASE in promoting process quality. The term process maturity has no generally accepted definition. However, for purposes of discussion the author assumes that the term implies concepts closely akin to those embodied in SEI's Capability Maturity Model (CMM) View full abstract»

    Full text access may be available. Click article title to sign in or learn about subscription options.