Introduction to Software Engineering/Tools/Modelling and Case Tools. Computer- aided software engineering (CASE) is the scientific application of a set of tools and methods to a software system which is meant to result in high- quality, defect- free, and maintainable software products.[1] It also refers to methods for the development of information systems together with automated tools that can be used in the software development process.[2]Overview[edit]The term "computer- aided software engineering" (CASE) can refer to the software used for the automated development of systems software, i. The CASE functions include analysis, design, and programming. CASE tools automate methods for designing, documenting, and producing structured computer code in the desired programming language. CASE software supports the software process activities such as requirement engineering, design, program development and testing. Therefore, CASE tools include design editors, data dictionaries, compilers, debuggers, system building tools, etc. CASE also refers to the methods dedicated to an engineering discipline for the development of information system using automated tools. CASE is mainly used for the development of quality software which will perform effectively. History[edit]The ISDOS project at the University of Michigan initiated a great deal of interest in the whole concept of using computer systems to help analysts in the very difficult process of analysing requirements and developing systems. Several papers by Daniel Teichroew fired a whole generation of enthusiasts with the potential of automated systems development. His PSL/PSA tool was a CASE tool although it predated the term. His insights into the power of meta- meta- models was inspiring, particularly to a former student, Dr. Hasan Sayani, currently Professor, Program Director at University of Maryland University College. Another major thread emerged as a logical extension to the DBMS directory. By extending the range of meta- data held, the attributes of an application could be held within a dictionary and used at runtime. This "active dictionary" became the precursor to the more modern "model driven execution" (MDE) capability. However, the active dictionary did not provide a graphical representation of any of the meta- data. It was the linking of the concept of a dictionary holding analysts' meta- data, as derived from the use of an integrated set of techniques, together with the graphical representation of such data that gave rise to the earlier versions of I- CASE. The term CASE was originally coined by software company Nastec Corporation of Southfield, Michigan in 1. Graphi. Text, which also was the first microcomputer- based system to use hyperlinks to cross- reference text strings in documents—an early forerunner of today's web page link. Graphi. Text's successor product, Design. Aid, was the first microprocessor- based tool to logically and semantically evaluate software and system design diagrams and build a data dictionary. Under the direction of Albert F. Case, Jr. vice president for product management and consulting, and Vaughn Frick, director of product management, the Design. Aid product suite was expanded to support analysis of a wide range of structured analysis and design methodologies, notably Ed Yourdon and Tom De. Marco, Chris Gane & Trish Sarson, Ward- Mellor (real- time) SA/SD and Warnier- Orr (data driven). The next entrant into the market was Excelerator from Index Technology in Cambridge, Mass. While Design. Aid ran on Convergent Technologies and later Burroughs Ngen networked microcomputers, Index launched Excelerator on the IBM PC/AT platform. While, at the time of launch, and for several years, the IBM platform did not support networking or a centralized database as did the Convergent Technologies or Burroughs machines, the allure of IBM was strong, and Excelerator came to prominence. ![]() Hot on the heels of Excelerator were a rash of offerings from companies such as Knowledgeware (James Martin, Fran Tarkenton and Don Addington), Texas Instrument's IEF and Accenture's FOUNDATION toolset (METHOD/1, DESIGN/1, INSTALL/1, FCP). CASE tools were at their peak in the early 1. At the time IBM had proposed AD/Cycle, which was an alliance of software vendors centered around IBM's Software repository using IBM DB2 in mainframe and OS/2: The application development tools can be from several sources: from IBM, from vendors, and from the customers themselves. IBM has entered into relationships with Bachman Information Systems, Index Technology Corporation, and Knowledgeware, Inc. IBM complementary marketing program to provide offerings that will help to achieve complete life- cycle coverage.[3]With the decline of the mainframe, AD/Cycle and the Big CASE tools died off, opening the market for the mainstream CASE tools of today. Nearly all of the leaders of the CASE market of the early 1. Computer Associates, including IEW, IEF, ADW, Cayenne, and Learmonth & Burchett Management Systems (LBMS). Supporting software[edit]Alfonso Fuggetta classified CASE into 3 categories: [4]Tasks support only specific tasks in the software process. Workbenches support only one or a few activities. Environments support (a large part of) the software process. Workbenches and environments are generally built as collections of tools. Tools can therefore be either stand alone products or components of workbenches and environments. CASE tools are a class of software that automate many of the activities involved in various life cycle phases. For example, when establishing the functional requirements of a proposed application, prototyping tools can be used to develop graphic models of application screens to assist end users to visualize how an application will look after development. ![]() Subsequently, system designers can use automated design tools to transform the prototyped functional requirements into detailed design documents. Programmers can then use automated code generators to convert the design documents into code. Case Tool software free downloads and reviews at. Inspection CASE tool v.1.0 A CASE (Computer-Aided Software Engineering). open source CASE Tool HIDS CASE. Using Computer-Aided Software Engineering (CASE)--tools to document the current logical model of a system for DoD requirements specifications. Computer Aided Systems Engineering ToolsAutomated tools can be used collectively, as mentioned, or individually. For example, prototyping tools could be used to define application requirements that get passed to design technicians who convert the requirements into detailed designs in a traditional manner using flowcharts and narrative documents, without the assistance of automated design software.[5]Existing CASE tools can be classified along 4 different dimensions: Life- cycle support. Integration dimension. Construction dimension. Knowledge- based CASE dimension[6]Let us take the meaning of these dimensions along with their examples one by one: Life- Cycle Based CASE Tools. This dimension classifies CASE Tools on the basis of the activities they support in the information systems life cycle. They can be classified as Upper or Lower CASE tools. Upper CASE Tools support strategic planning and construction of concept- level products and ignore the design aspect. They support traditional diagrammatic languages such as ER diagrams, Data flow diagram, Structure charts, Decision Trees, Decision tables, etc. Lower CASE Tools concentrate on the back end activities of the software life cycle, such as physical design, debugging, construction, testing, component integration, maintenance, reengineering and reverse engineering.
![]() Integration dimension. Three main CASE Integration dimensions have been proposed: [7]CASE Framework. ICASE Tools. Integrated Project Support Environment(IPSE)Workbenches[edit]Workbenches integrate several CASE tools into one application to support specific software- process activities. Hence they achieve: a homogeneous and consistent interface (presentation integration). CASE workbenches can be further classified into following 8 classes: [4]Business planning and modeling. Analysis and design. User- interface development. Programming. Verification and validation. Maintenance and reverse engineering. Configuration management. Project management. Environments[edit]An environment is a collection of CASE tools and workbenches that supports the software process. CASE environments are classified based on the focus/basis of integration[4]Toolkits. Language- centered. Integrated. Fourth generation. Process- centered. Toolkits. Toolkits are loosely integrated collections of products easily extended by aggregating different tools and workbenches. Typically, the support provided by a toolkit is limited to programming, configuration management and project management. What are examples of case tools? Examples of CASE tools include diagram tools, documentation tools, process modeling tools, analysis and design tools, system software tools, project management tools, design tools, prototyping tools, configuration manage tools, programming tools, Web development tools, testing tools, maintenance tools, quality assurance tools, database management tools and re- engineering tools. Upper CASE tools support the analysis and design phase of a software system and include tools such as report generators and analysis tools. Examples of lower CASE tools are code designers and program editors, and these tools support the coding, testing and debugging phase. Integrated CASE tools support the analysis, design and coding phase. CASE tools offer several benefits. These include improved project management, improved system quality, increased productivity, reduced development time and effort, easier and better maintenance of the software system and better documentation. A CASE tool should flexible and easily integrated, and it should support standard software development techniques and methodology. In spite of the fact that CASE tools are not cheap, they do help create high- quality software systems. Learn more about Tools.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
November 2017
Categories |