Analysis Assignment 1

Topics: Software engineering, Software development, Software development process Pages: 5 (828 words) Published: March 25, 2015


System Analysis and Design

Assignment 1

By
Rangan Dasgupta
1000344 | Bachelor of Computer Engineering

Question:
From the introductory conversation Chip and Anna shared, which elements mentioned might suggest the use of CASE tools?

Answer:
CASE tools are used for increasing analyst productivity, Improving analyst-user communication and integrating life cycle activities.

CASE tools would be used to help Chip and Anna communicate with each other and share portions of the design that they have completed.

Because there are many users for the Computer System, CASE tools will help to facilitate communication among the users and analyst and document the information that they have received as a result of interviews, document analysis, and questionnaires.

Features of Case Tools:
Increasing analyst productivity, Improving analyst-user communication and integrating ly of 53 companies, found that 39 (73.5%) had never used CASE. Of the 14 companies who had tried CASE, five had subsequently abandoned use of the tools. People within these fourteen companies believed that use of CASE tools improved documentation quality, improved analysis, and resulted in systems that were easier to test and maintain. However, they also found use of CASE tools difficult and time consuming. In another cross organization survey, found that only 24% of companies were using CASE tools. In a follow-up survey of thirteen managers who had been using CASE tools two years earlier, reported that continued CASE use could only be verified for four managers. The reasons for abandonment included cost, lack of measurable turns, and unrealistic expectations. Looking within organizations that used CASE tools it was found that large numbers of their systems developers were not using CASE tools.ife cycle activities.

The term Computer-Aided Software Engineering (CASE) encompasses many different products with different functionalities. In the International Workshop on Computer-Aided Software Engineering (IWCASE) definition of CASE very broad terms are used: “...tools and methods to support engineering approach to systems development at all stages of the process”. When the term CASE is used, it is important to clarify what is being discussed. Most classifications of CASE tools start by considering whether the tool is upper CASE, lower CASE, or integrated CASE [3]. An upper CASE tool (front end CASE) provides support for the early stages in the systems development life cycle such as requirements analysis and design. A lower CASE tool (back end CASE) provides support for the later stages in the life cycle such as code generation and testing. Integrated CASE tools support both the early and later stages. Further classifications usually list which functionalities are supported by the tool, such as data flow diagrams, entity relationships data models, etc. provides a different type of model of CASE functionality which helps organize CASE tools.

CASE tools may be divided into several categories, namely:

A. Upper CASE tools are used to perform analysis and design. B. Lower CASE tools are used to generate computer language source code from CASE design. The advantage in generating source code are:

a. The time to develop new systems decreases.
b. The time to maintain generated code is less than to maintain traditional systems. c. Computer programs may be generated in more than one language. d. CASE design may be purchased from third-party vendors and tailored to organizational needs. e. Generated code is free from program coding errors.

Web References

http://en.wikipedia.org/wiki/Computer_aided_software_engineering http://www.clariondeveloper.net/modules/weblinks/viewcat.php?cid=32 http://www.openden.com/opensource/viewcat/id/5752850
www.infoweblinks.com/content/casetools.htm
www.downloadthat.com/pda/catalog/Case_Tools
www.itmweb.com/case.htm...


References: Norman, R.J. and Forte, G. “Automating the Software Development Process: CASE in the ‘9Os,” Communications of the ACM (35:4), 1992, p. 27
Brown, et al., Principles of CASE Tool Integrations, Oxford University Press, New York
Elshazly, H. and Grover, V. “A Study on the Evaluation of CASE Technology,” Journal of Information Technology Management (4:1), 1993.
Forte, G. and Norman, R.J. “A Self-Assessmenbty the Software Engineering Community,” Communications of the ACM (35:4), 1992, 28-32.
P. Jallaart et ai., " A Reflective Approach to Process Model Customization, Enactment and Evolution ", Pro¢ of the 3rd International Conference on the Software Process, 1994, pp.21-32.
F. Russell, " The case for Case ", Software Engineering : A European Perspective, edited by Richard H. Thayer and Andrew D. McGettriek, IEEE Computer Society Press, Los Alamitos, California, pp.531-547.
I. Aaen, "CASE Tool Bootstrapping--how little strokes fell great oaks ", Next Generation CASE Tools, edited by K. Lyytinen, V.-P. Tahvanainen, lOS, Netherlands, 1992, pp.8-17.
A. Brown, et al., Princ~les of CASE Tool Integrations, Oxford University Press, New York, 1994.
P. Jallaart et ai., " A Reflective Approach to Process Model Customization, Enactment and Evolution ", Pro¢ of the 3rd International Conference on the Software Process, 1994, pp.21-32.
U. Leonhardt et al., " Decentralized Process Enactment in a Multi-Perspective Development Environ-ment ", Proc of the 17th International Conference on Software Engineering, 1995, pp.255-264.
Continue Reading

Please join StudyMode to read the full document

You May Also Find These Documents Helpful

  • Economic Analysis
  • Assignment 1 Becoming an effective Leader Essay
  • Essay about Assignment 1 curriculum analysis
  • Assignment 1 Financial Analysis Essay
  • Quantitative Analysis Assignment 1 Essay
  • HLTA Assignment 1 Essay
  • assignment brief unit 1 Essay
  • CELTA ASSIGNMENT 1: LANGUAGE ANALYSIS Essay

Become a StudyMode Member

Sign Up - It's Free