front means ahead, infront , forward end means last point, finishing point, but what does FRONTEND mean? for example engineering design is clear to me, but "frontend engineering design" what exactly wants to tell us about engineering design? i am looking for an explanation for frontend without any prefix of suffix actualy. purely for " frontend".
It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center.If this question can be reworded to fit the rules in the help center, please edit the question.
In software engineering 'front end' refers to the user interface. It is based on the idea that the part of the system that the user interacts with is the front of the system.
In electronics and signal processing the 'front end' refers to the electronics used to capture signals from the 'real' world into the electronic or digital domain. This is the front of the system in the sense signals enter through this part of the system.
In general engineering usage it refers to the early part of any process where front is used to refer to the part of the process that occurs first.
Examples would be:
'The system front end provides the ability for the user to select and view patient records.'
'The front end provides ESD protection, EMC and anti-alias filtering with a 25 MHz bandwidth.'
'The root cause of the problem was in the front end when the functional requirments were defined ambiquously.'
The specific example of 'frontend engineering design' without further context is most likely to mean the design of transducers and analogue signal processing prior to digital signal processing.
I have seen all usages in my experieance as an engineer. The most common is to refer to the input signal handling of a system as the front end.
First, the basics. Front is a deictic word, and thus its semantics are not simple.
That's for physical fronts. But in software, everything is Metaphorical, not physical, including front and front( )end. So we have to apply the tests that Fillmore gives. How do they apply to a piece of software?
The first two criteria (natural models, which tells us which part of a rocking horse is the front end, and objects in motion, which tells us which part of a bicycle is the front) don't really apply, because there are no natural models for software (which is why it's all metaphors) and it's not in motion. So we proceed to the next two.
Fillmore's user-orientation and access criteria both suggest that the front end of a program should be its user interface, as both the part of the program to which users are oriented while in use, and as the part to which users typically and importantly (and sometimes only symbolically) have access.
As with most such fixed phrases, especially in IT English, the space in front end is optional.