Component-based development has an intuitive underlying idea. Instead of developing a system by programming it entirely from scratch, develop it by using preexisting building blocks, components, and plug them together as required to the target system. The benefits are obvious. Parts of a system which do not have to be programmed do not entail costs and do not face the project manager with the risks typically encountered in software projects. It was expected that using components will also contribute to an increase in system quality. However, this expectation is fulfilled only holds in certain circumstances; quality assurance techniques, particularly testing, are still required. Magnet tries to fulfill this issues. We defined three language to lead the analysts to produce better product using component-based development. We retain that, using text language with visual language (such as UML), you can pass from model to code in simplified way. Industrial development of software systems, often called software development in the large, generally needs to be guided by engineering principles similar to those in mature engineering disciplines. Informal methods, which might be appropriate for the development of simple software, cannot be employed for the development of software systems with high inherent complexity. This is one of the lessons learnt from the software crisis. The software crisis lead to the creation of the term software engineering to make clear that software development is an engineering discipline.
We’ve developed three languages: Magnet Language : a basic language defined over python interpreter (we use a just-in-time compiler to speed up the environment) . It supports three paradigms : functional, imperative, object-oriented and other no programmatic paradigms (aspects and unit testing). Magnet Architecture Language: This language allows you to analyze the subcomponent and simulating the behavior . Contextually, this is the entry point of software programs ( the main method is defined here). Magnet Model-Checking Language: This language defines a simplified model-checking language to perform quantitative and qualitative analysis. It’s suitable to perform intra-component testing and performance analysis.
Ohloh computes statistics on FOSS projects by examining source code and commit history in source code management systems. This project has no code locations, and so Ohloh cannot perform this analysis
Is this project's source code hosted in a publicly available repository? Do you know the URL? If you do, click the button below and tell us so that Ohloh can generate statistics! It's fast and easy - try it and see!