CASE tool

When a single technique is employed only local life-cycle cost minimization is achieved. If the global life-cycle cost is to be minimized, a number of techniques have to be applied (Watson et al., 1996). In this case, tools and techniques shouldn t compete with each other, but be complementary in the product development process. The correct positioning of the various off-line tools and techniques in the product development process, therefore, becomes an important consideration in their effective usage. Patterns of application have been proposed by a number of workers over several years (Brown et al., 1989 Jakobsen, 1993 Norell, 1993) and the importance of concurrency has been highlighted as a critical factor in their use (Poolton and Barclay, 1996). 

Where are quality tools available Laboratory supply houses sell handy tool kits for normal repair and maintenance jobs. They may come in compaifmented boxes or pouches that are easy to carry to where they are to be used. Such organization also makes it simple to spot a tool left behind on a job. Unfortunately, kits are often quite expensive and may contain some tools that will never be needed, or they may lack tools required in a certain laboratory. In such cases, tools are best obtained separately from hardware... 

This section briefly discusses UML and explains how we have used it in Catalysis, including some of the extensions or interpretation we have found useful or necessary, such as parameterized attributes, frameworks, and use cases. There are systematic approaches to using Catalysis with existing CASE tools (refer to www.catalysis.org). 

Manual maintenance of RTM documents can be labor intensive and error prone, so it is recommended that the availabihty of software solutions or CASE tools for managing traceability information be considered as an alternative. Spreadsheet applications are an obvious choice in simple cases. For more complex document sets, a more sophisticated automated solution is much more likely to be up to the job. 

Development tools CASE tools. Computer Aided Design (CAD)... 

Computer Aided Software Environments (CASE) Tools designed to support the analysis and design phases of the software development life cycle. The tools are usually oriented toward the support of graphical notations. [Defined for this book.]... 

A drawback of the approach is that it cannot be represented within a single modeling language. Therefore, the CASE tool Rational Rose had to be used to manage the relations between the product data model and the DTD elements. In order to obtain a model represented within a single formalism, the Document Model introduced in Fig. 2.7 has been extended, as shown in Fig. 2.10. Newly introduced classes and relations are emphasized in bold print. 

The process modeler uses a commercial CASE tool - Rational Rose - to... 

Texas Instruments Personal Consultant and Procedures Consultant (39) series of expert system development shells could also be considered as specialized CASE tools. 

Maklakov SV. BPwin and ERwin. CASE-tools for information systems design. Moscow Dialog-MIPHI, 2000. 

D.9. Use and control of design methodologies (CASE tools) (see Section 8.1.3)... 

There are many compelling reasons to use CASE tools. CASE tools can greatly shorten development times without sacrificing system quality. The tools usually enforce consistency across different phases by providing automated consistency checking between DFDs, ERDs, and the data dictionary to ensure that the attributes and data structures have been named and defined consistently across all of them. This, in turn, can increase the productivity of the SDLC team because a data store defined in a DFD can be automatically inserted as an entry in the data dictionary. This, in turn, can increase the consistency of the development effort across projects. 

The disadvantages of CASE mostly revolve aronnd cost. CASE tools tend to be very expensive, both in monetary and in resomce terms. CASE tools cost a lot, and learning to use them can be very time consuming because of the number of features and the functionality that they provide. They also place great demands on the hardware in terms of processing needs and storage requirements at the server and workstation level. Essentially, aU they do is automate manual processes, so the decision to use CASE hinges on the traditional tradeoff between labor costs and automation costs. 

Both these techniques are realized by two software packages Teamwork and P-NUT. Teamwork is a computer aided software engineering (CASE) tool family that automates standard structured methodologies using interactive computer graphics and multiuser workstation power. P-NUT is a set of tools developed by the Distributed Systems Project in the Information and Computer Science... 

CASE tools such as ADW, on the other hand, support a specific design methodology by offering data models and function models (e.g., the entity relationship method (ERM) and structured analysis and design technique [SADT]). Their metastructure has to reflect this methodology. Thus, they automatically provide an information model for the repository functionality of this system. Because CASE tools cannot really claim to offer a complete repository, they are also called encyclopedias. 

Software, that produces indirectly application software is denoted as indirect 2 here. These are tools which support the development of software by a structured approach (CASE tools). Examples for such a structured approach are methods like SA (Structured Analyses), SD (Structured Design), SADT (Structured Analysis and Design Technique), etc. The tools based on approaches like this establish a framework within which the application software can be interactively developed. 

Orlikowski, W.J. (1993). CASE tools as organizational change Investigating incremental and radical changes in systems development. MIS Quarterly, 77(3), 309-340. 

Poly(acrylonitrile-co-butadiene-co-styrene), ABS. Applications housings, boxes, cases, tools, office equipment, helmets, pipes, fittings, frames, toys, sports equipment, housewares, packaging, panels, covers, automotive interior parts, food packaging, furniture, automobile parts. 

These additives reduce the potential for rusting in pipes and casings. Corrosion inhibitors are required in acid fluid mixtures because acids will corrode steel tubing, well casings, tools, and tanks. The solvent acetone is a common additive in corrosion inhibitors (Penny and Conway, 1996). Corrosion inhibitors are quite hazardous in their undiluted form. These products are diluted to a concentration of 1 gal per 1000 gal of make-up water and acid mixture (USEPA, 2004). Acids and acid corrosion inhibitors are used in very small quantities in fracturing operations (5(X) to 2000 gal per treatment). 

These objectives are generally not achievable without substantial computer assistance provided by some form of CASE tool. It is important tliat any new approach and any new toolset should be judged on its ability to meet these four objectives. While tliere are many other objectives that a specification should attain, in this paper we concentrate only on the above four. 

Complex products with embedded software have a complex requirements structure. As a result the test case structure can also be quite complex. The test cases should be maintained in a test case database. To support requirements traceability the test case tool should be able to interface with the requirements management tool, where all the product requirements are maintained. Also an interface to the configuration management tooling is advised. Configuration references can be explicitly defined and maintained. 

Programmable electronic integration (Clause 7.5) Major issues are integration of software into hardware of PEs, and hardware and software in combination meet the requirements of intended SIL and associated testing such as test data, test criteria, corrective actions on test failure case, tools, etc. 

Many of the certifying authorities use their own software tools (e.g., Exida s Safety Case tool) for the entire system. 

Automotive industry Radiator expansion tanks, brake fluid reservoirs fittings, steering wheel covers, wheel arch liner, bumpers, bumper covers, side strips, spoilers, mudguards, battery cases, tool boxes... 

Safety cases have been increasingly accepted as an assurance technique by many industrial sectors, e.g. defence, air traffic control, railway, automobile and medical devices [1]. In the past decade, there are considerable research and application efforts placed on safety case notations, safety case life cycles, argument patterns, safety case tools and argument and evidence meta-models. However, a supportive element in the safety case development process, the strategy for describing the relationships between safety claims of different levels has not been emphasized as much as other key safety case elements, e.g. claims and evidence items. 

---