Computer Aided Software Engineering

6 Key excerpts on "Computer Aided Software Engineering"

• 

  eBook - ePub

  Fundamentals of Software Engineering

  Designed to provide an insight into the software engineering concepts

  • Hitesh Mohapatra, Hitesh Mohapatra, Amiya Kumar Rath(Authors)
  • 2020(Publication Date)
  • BPB Publications

    (Publisher)

  Computer Aided Software Engineering (CASE) .

  Objective

  The CASE tools to be used to automate and support the system development process with the objective of increasing productivity and improving the overall quality of system. CASE should provide the software engineer an ability to automate manual activities and to improve engineering insight.

  Many organizations use CASE to:

  • Improve the quality of the system developed
  • Increase the speed with which systems are designed and developed
  • Ease and improve the testing process through the use of automated checking
  • Improve the integration of development activities via common methodologies
  • Improve the quality and completeness of documentation
  • Help to standardize the development process
  • Improve the management of the project
  • Simplify program maintenance
  • Promote reusability of modules and documentation
  • Improve software portability across environments

  Driving organizational forces for adaptation of CASE, Organizations adopt CASE to:

  • Provide new systems with shorter development time
  • Improve the productivity of the system development process
  • Improve the quality of the systems development process
  • Improve workers skill
  • Improve the probability of new system
  • Improve the management of the system development process

  Resisting organizational forces for adaptation of CASE, Organizations reject CASE because of:

  • The high cost of purchasing CASE software
  • The high cost of training the personnel
  • Low organizational confidence in the Information System (IS) department to deliver high-quality systems on time and within the budget
  • Lack of methodology standards within the organization
  • Viewing CASE as a threat to job security
  • Lack of confidence in CASE products

  Taxonomy of CASE tools

  A number of risks are inherent whenever we attempt to categorize CASE tools. There is a subtle implication that to create an effective CASE environment, one must implement all the categories of tools, is simply not true. Confusion (or antagonism) can be created by placing a specific tool within one category when others might believe that it belongs to another category. It is necessary to create taxonomy of CASE tools, to better understand the breadth of CASE and to better appreciate where such tools can be applied in the software engineering process.

  Sign up to read

  Learn more about book
• 

  eBook - ePub

  Foundations of Computer Technology

  • Alexander John Anderson(Author)
  • 2020(Publication Date)
  • CRC Press

    (Publisher)

  The coding process is such that the high level source program, or assembly language program, to solve the software task is written by a programmer with the use of some type of editor program. The source program is subsequently input to the translator program, which produces the equivalent machine code along with a listing of the original source program. In the group of translator programs are such things as assemblers, compilers, emulators and interpreters which allow source programs to be changed into the object machine code. In the process of assembling or compiling the source program, the translator checks for any violations of the rules governing the structure of instructions, syntactic errors, and for consistency and completeness of the programs. The syntax errors are usually indicated on the program listing adjacent to each incorrect program statement.

  On discovering errors in the source code the programmer must reuse the editor to make the required corrections in the source statements before the program can be re-assembled or re–compiled. In practice it may take several translations followed by use of the editor to locate and correct all the syntax errors in a program.

  Article 9.1 Computer Aided Software Engineering (CASE)

  CASE is the use of software tools to aid in the design of computer programs. Many of these tools use microprocessor based workstations with powerful graphic capabilities and user friendly interfaces. CASE tools redefine the software development environment allowing all phases of the software development cycle to be linked together. CASE software includes the following facilities:

  1.  Diagramming tools for drawing structure diagrams and creating pictorial system specifications.

  2.  Screen and report painters for creating system specifications and a form of simple prototyping.

  3.  Dictionaries, data base management systems and reporting facilities for storing, reporting and querying technical and project management system information.

  4.  Specification checking tools to automatically detect incomplete, syntactically incorrect and inconsistent system specifications.

  5.  Code generators to generate executable code automatically from pictorial system specifications. Some CASE systems also include code generators that when given the specifications for a part of a system produce high level language programs that implement the part of the system. Manual programming in some cases can be replaced by CASE code generators that automatically produce 80 to 100% of the code.

  6.  documentation generators to produce technical and user system documentation required by structure analysts.

  It is claimed by many software engineers that the use of software tools has a number of advantages. These are noted in the Table 9.1

  Sign up to read

  Learn more about book
• 

  eBook - PDF

  Software Engineering Education

  Proceedings of the IFIP WG3.4/SEARCC (SRIG on Education and Training) Working Conference, Hong Kong, 28 September - 2 October, 1993

  • B.Z. Barta, S.L. Hung, K.R. Cox(Authors)
  • 2013(Publication Date)
  • North Holland

    (Publisher)

  DISCUSSION SUMMARIES This page intentionally left blank Software Engineering Education (A-40) B.Z. Barta, S.L. Hung and K.R. Cox (Editors) Elsevier Science B.V. (North-Holland) 319 © 1993 IFIP. All rights reserved. CASE Tools in Software Engineering Education SUMMARY OF DISCUSSION DISCUSSION LEADERS: J. Barrie Thompson and Angela Goh 1. INTRODUCTION For this discussion group preprinted copies of the opening statements and copies of a set of issues prepared by the chairpersons were circulated. The group considered these points and others raised during discussion. Initially a free form exchange covered the topic in general. Finally the group returned to each of the issues and attempted to reach conclusions on each issue. 2. OPENING STATEMENTS There has been a great deal of interest and enthusiasm over the past decade in Computer Aided Software Engineering (CASE) products. These products were hailed as a major breakthrough in solving application backlogs. They have been compared with computer aided design (CAD) workstations in that just as CAD is becoming indispensable to the engineer, so also CASE is seen to be vital to the systems analyst, designer and programmer. In recent years, there has been a proliferation of CASE products. Many of these are on PC-based machines, with features that are as varied as the costs. The products support different techniques and these are presented at varying levels of sophistication. A number of these products also support a PC-mainframe link, which is essential for a total integration of the development process. These statements were accepted as a fair summary of the current state of the art. However, a major point discussed was what constituted a CASE product and what did not. For the purposes of the discussion a general definition of — a product that automates a part of parts of the Software Development Life Cycle (SDLC) was adopted.

  Sign up to read

  Learn more about book
• 

  eBook - ePub

  Reliability 91

  • R.H. Matthews(Author)
  • 2018(Publication Date)
  • Chapman and Hall/CRC

    (Publisher)

  Nevertheless, CASE technology is not fallible and tool users must understand the limitations of their tools. CASE tools are simply an aid to development and do very little actual automation, requiring highly skilled software engineers to operate them. Using CASE tools in the design of a system will not guarantee that the design is in anyway a more accurate reflection of users requirements than one produced manually. In other words, using tools alone will not produce more reliable quality software.

  Finally, while this paper has examined those reliability benefits that can be achieved from the use of CASE one must remember that no reliability benefits will be realized without the perceived need for, and the willingness to use, automated tools by all levels of management and by the system developers themselves.

  REFERENCES

  1.   Fisher, A.S., CASE: Using Software Development Tools . Wiley, New York, 1988, pp. 6–7.

  2.   Locklyer, M.A. and Griffiths, G., Method support within CASE tools, Software Quality Workshop . 27–28 June, 1989.

  3.   Llewellyn, D., A Possible Functional Architecture for Design Tools in a Software Engineering Support Environment, Data Processing: From discourse to method convention informatique . Paris, 1986, pp.340–344.

  4.   Longworth, M. and Nichols, D., The SSADM Manual . NCC Publications, Manchester, 1986.

  5.   Yourdon, E., Software Development Methodology , Yourdon Inc, New York, 1982.

  6.   Finkelstein, C., An Introduction to Information Engineering: From Strategic Planning to Information Systems . Addison Wesley, Singapore, 1989.

  7.   Gane, C. and Sarson, T., Structured Systems Analysis: Tools and Techniques . Prentice Hall, Englewood Cliffs, 1977.

  8.   Jackson, M.A., Principles of Program Design . Academic Press, London, 1975.

  9.   Cook, S., Languages and object-oriented programming, IEE/BCS Software Engineering Journal . 1(2), 1986.

  10.   Jones, R., Pack up your troubles in a CASE environment, Computing

  Sign up to read

  Learn more about book
• 

  eBook - ePub

  Data Architecture

  From Zen to Reality

  • Charles Tupper(Author)
  • 2011(Publication Date)
  • Morgan Kaufmann

    (Publisher)

  4. Understanding Development Methodologies

  Design Methods

  Many software projects suffer from budget overruns, time synchronization problems, and the delivery of applications that do not satisfy the specified client requirements. Moreover, the developed application systems need to be responsive to change and yet be maintainable to reflect changing requirements. In order to address these issues in a structured manner, design methodologies were created. Many design methodologies have survived the revolutions that have taken place in the data processing industry, and they still provide methods of addressing these issues.

  Principle

  Methodologies provide guidelines for the application development process. They specify analysis and design techniques as well as the stages in which they occur. They also develop event sequencing. Lastly, they specify milestones and work products that must be created and the appropriate documentation that should be generated.

  Computer-aided software engineering (CASE) tools are useful for supporting the software development process by providing heuristics encoded into their software that help with design decisions. They are also helpful with the preparation and maintenance of the design documentation, which often includes graphic as well as textual material.

  Increasingly, CASE software tools are available with some capacity for code and database schema generation. Commentary on this subject will be covered in another chapter. In order to examine some of the characteristics of the existing methodologies, we must review when and where the methodologies arose and what problems were trying to be solved at the time. Practical discussion of the problems with some of these implemented methodologies will be discussed in a later chapter. The review covered here is to show the stepwise evolution to current significantly successful methodologies.

  Sign up to read

  Learn more about book
• 

  eBook - ePub

  Advances in Concurrent Engineering

  CE00 Proceedings

  • Biren Prasad(Author)
  • 2023(Publication Date)
  • CRC Press

    (Publisher)

  CHAPTER 12 CE Perspectives Passage contains an image

  A Survey of how UK SMEs use Computer Aided Solid Modelling – And an outline for better Implementation

  J. Lawson School of Design, University of East London, 4-6 University Way, London, E16 2RD A. King School of Design, University of East London, 4-6 University Way, London, E16 2RD

  Abstract

  With the globalisation of business the manufacturing sector now trades in a highly competitive market where design efficiency is essential New technology, and particularly Computer Aided Design, plays an essential part in achieving this goal However, simply having the technology is no solution: it needs to be used effectively. This paper explains the problems that Small to Medium sized Enterprises (SMEs) face when investing in CAD technology and in particular Computer Aided Solid Modelling (CASM).

  The paper concludes with an evaluation and gives recommendations for future research.

  1. Computer Aided Solid Modelling (CASM)

  Computer Aided Solid Modelling (CASM) is a prime example of a new technology that can, if implemented correctly, bring massive cost and time savings to a company’s new product development process. Although various forms of CAD have been used for 30 years, it is the more recent development of CASM that has made its use more widespread in the earlier stages of design [1 ]. There are two main reasons why CASM has become a viable technology for SMEs to use.

  Firstly, the cost of implementing powerful hardware and software systems has significantly dropped meaning that state-of-the-art CASM software is now an option for even the smallest of companies. With this the software has become much more usable due to user-interface developments.

  Secondly, CASM software represents much more design information than older 2D Computer Aided Drafting software. Therefore, CASM acts as the “bridge” for the further integration of secondary technologies including Finite Element Analysis, Computational Fluid Dynamics, Rapid Prototyping, and Computer Numerical Control manufacture. CASM is an ideal foundation to enable further business development.

  Sign up to read

  Learn more about book