IFSM 461 – CASE Tools Analysis – MetaEdit+

IFSM 461: Systems Analysis and Design –  CASE Tools Analysis – MetaEdit+

Our company has been experiencing a number of challenges in our normal software development role. One of the major challenges experienced in the software development in the company include unresolvable bugs, poor design and inability to satisfy the user requirements. This has highly attributed to poor systems or software design since unlike our competitors who use CASE tool to model their design, the company normally relies on simple modeling that can be obtain from the available computer application software such as Microsoft office. This has made it hard for the company to develop complex systems and applications without making mistakes, either omission or inability to fully meet the client requirements. This has resulted to the loss of huge number of customers to our competitors who apply modern CASE tools to develop their systems. To remain competitive and viable in the market, I strongly believe that the company will need to employ new measures in the software development and to embrace the change in the technology so as to stand up for our competitors. The company will therefore need to employ a modeling CASE tool to assist in capturing customers’ requirements and ensuring effective design of the anticipated system (UMSL.edu, 2009).

After realizing the problem that the company is facing, I have been conducting a research to establish the best CASE Tool the company can employ for this purpose. The most viable Tools for this task in the market include MetaEdit+. MetaEdit+ is a CASE tool for structuring a modeling language and then creating diagramming functionalities. The CASE tool offers full modeling functionality for multiple projects, multiple users, and executing on all main platforms. The CASE tool automatically follows the MetaEdit+ workbench modeling language by retrieving it from the repository. It allows the developer to drastically improve development quality and productivity by directly creating full code from models. The designer is needed to use Metaedit+ Workbench to design the modeling language and to use other developers’ models with MetaEdit + Modeler language. The CASE tool permits the programmer to develop own modeling tools without writing a single line of code. The company can start using the MetaEdit+ tool as soon as the modeling language is selected or even after having a partial prototype (Kelly, 2004).

Another CASE tool that can be used for this purpose is Rational Rose. Rational Rose is a model driven and Unified Modeling Language (UML) tool which contains the aptitude to integrate with the current integrated developments languages or environment. The tool can be used to create systems with UNIX, and Windows platform. It can also be used as visual studio and also as an enterprise. The software has can operate in visual modeling environment which permits the developer to streamline applications development. It also allows the integration of the development with application design and unites the project team by offering common UML model notation and execution (IBM, n.d.). The main similarities between the two CASE Tools are used to assist in developing software for Windows platforms. In addition, the two CASE Tools are used in software modeling. However, MetaEdit+ are more powerful modeling tools as compared to Rational Rose since MetaEdit+ can model in different languages other than object oriented language alone. MetaEdit+ is very extensive and thus, it can be used for varieties of designs as compared to Rational Rose.

Beside this, MetaEdit+ generates codes for the programmer as the programmer develops the model. This is an ability that lacks in the Rational Rose. Thus MetaEdit+ can help a company to complete the most complex application software with no or minimal errors as compared to Rational Rose. Thus MetaEdit+ will be of great importance to the company as compared to Rational Rose since it will address various designs and hence increase the company’s extensibility when it comes to the number of projects to be handled. Another major difference is that MetaEdit+ is much expensive as compared to Rational Rose. The MetaEdit+ cost £9500 while Rational Rose costs $4870. In this regard, the extra services provided by MetaEdit+ are catered for by its extra cost. The two CASE Tools contain both upper and lower case facilities; however the MetaEdit+ tool does not contain analysis tools. The two tools are considered to be the most comprehensive tools in the market. The only main disadvantage of using Rational Rose is that the tool is limited based on the programming language to use. It is only viable for object oriented programs while MetaEdit+ is viable for different languages and will always generate the code based on the programmer selected language. Thus, it is highly advantageous for an enterprise company hoping to expand its software development operations for and wide (UMSL.edu, 2009).

Download full sample paper on CASE Tools Analysis and in this case MetaEdit+ or order a unique and high quality paper on any case tool at an affordable price. 

Order Unique Answer Now

Add a Comment

Your email address will not be published. Required fields are marked *