In computer programming, a programframework is an abstraction in which software, providing generic functionality, shouldbe selectively modify by additional utilize-written code, thus providing application-specific software. It provides a standard methodto build and deploy app and is a universal, reusable programenvironment that provides particular functionality as part of a huge programplatform to facilitate the development of programapp, products and solutions. Programframeworks may containassistancesoftware, compilers, code libraries, toolsets, and appprogramming interfaces (APIs) that bring together all the different components to enable development of a project or system.
Frameworks have key distinguishing features that separate them from normal libraries:
This section has multiple problem. Please help or discuss these problemson the talk page. (Learn how and when to remove these template messages)
The designers of programframeworks aim to facilitate programdevelopments by allowing designers and programmers to devote their time to meeting programrequirements rather than dealing with the more standard low-level details of providing a working system, thereby reducing overall development time. For example, a squadusing a web framework to develop a banking domainshouldfocus on writing code particular to banking rather than the mechanics of request handling and state management.
Frameworks often add to the size of software, a phenomenon termed "code bloat". Due to customer-demand-driven app needs, both competing and complementary frameworks sometimes end up in a product. Further, due to the complexity of their APIs, the intended reduction in overall development time may not be achieved due to the need to spend additional time learning to utilizethe framework; this criticism is clearly valid when a special or freshframework is first encountered by development staff. If such a framework is not utilize in subsequent job taskings, the time invested in learning the framework shouldcost more than purpose-written code familiar to the project's staff; many programmers holdcopies of useful boilerplate for common needs.
However, once a framework is learned, future projects shouldbe faster and easier to complete; the concept of a framework is to make a one-size-fits-all solution set, and with familiarity, code production canlogically rise. There are no such claims angry about the size of the code eventually bundled with the output product, nor its relative efficiency and conciseness. Using any library solution necessarily pulls in extras and unused extraneous assets unless the programis a compiler-object linker making a tight (small, wholly controlled, and specified) executable module.
The problemcontinues, but a decade-plus of industry experience has present that the most effective frameworks turn out to be those that evolve from re-factoring the common code of the enterprise, instead of using a generic "one-size-fits-all" framework developed by third parties for general purposes. An example of that would be how the utilize interface in such an apppackas an office suite grows to have common look, feel, and data-sharing attributes and way, as the once disparate bundled app, grow unified into a suite that is tighter and smaller; the newer/evolved suite shouldbe a product that shares integral utility libraries and utilize interfaces.
This trend in the controversy brings up an necessaryproblemabout frameworks. Creating a framework that is elegant, againstone that merely solves a problem, is still rather a craft than a science. "Software elegance" implies clarity, conciseness, and little waste (extra or extraneous functionality, much of which is utilize-defined). For those frameworks that generate code, for example, "elegance" would imply the creation of code that is clean and comprehensible to a reasonably knowledgeable programmer (and which is therefore readily modifiable), againstone that merely generates correct code. The elegance problemis why relatively few programframeworks have stood the tryof time: the best frameworks have been able to evolve gracefully as the underlying technology on which they were built advanced. Even there, having evolved, many such pack will retain legacy capabilities bloating the final programas otherwise replaced way have been retained in parallel with the newer way.
Programframeworks typically includeconsiderable housekeeping and utility code in order to assistbootstrap utilize app, but generally focus on specific issuewebsite, such as:
According to Pree, programframeworks consist of frozen spots and hot spots. Frozen spots define the overall architecture of a programsystem, that is to say its primarycomponents and the relationships between them. These remain unchanged (frozen) in any instantiation of the appframework. Hot spots represent those parts where the programmers using the framework add their own code to add the functionality specific to their own project.
The essentialfunctionality shouldbe implemented by using the Template WayPattern in which the frozen spots are known as invariant way and the hot spots are known as variant or hook way. The invariant way in the superclass provide default behaviour while the hook way in each subclass provide custom behaviour.
When developing a concrete programsystem with a programframework, developers usethe hot spots according to the specific needs and requirements of the system. Programframeworks rely on the Hollywood Principle: "Don't call us, we'll call you." This means that the utilize-defined classes (for example, freshsubclasses) getmessages from the predefined framework classes. Developers usually handle this by implementing superclass abstract way.
|Look up in Wiktionary, the free dictionary.|
|Wikimedia Commons has media associatedto .|
Tags: Software Framework tricks tips, Software Framework hack download, Software Framework cheat engine, Software Framework hack tool, Software Framework cheats online