I'm a firm believer that requirements should be technology independent. I cringe when I hear terms such as object-oriented (OO) requirements, structured requirements, or component-based requirements. The terms OO, structured, and component-based are all categories of implementation technologies, and although you may choose to constrain yourself to technology that falls within one of those categories the bottom line is that you should just be concerned about requirements. That's it, just requirements. All of the techniques that I describe below can be used to model the requirements for a system using any one (or more) of these categories.
Your conclusion must answer the question posed in your introduction. It should contain no new material and be relatively short when compared to the rest of the essay. Essentially, it reiterates the main argument you have proposed.
Your conclusion is your last opportunity to remind the reader what your essay set out to do, and how you accomplished it. Your conclusion should, therefore, revisit the question posed, and, briefly, summarise how you answered it. Whereas your introduction will set out what you proposed to do or show, your conclusion will talk of what you did achieve through the course of your essay.
Example of a good conclusion
From 1946 to 1966, homosexual activist Kurt Hiller published a number of poems and articles in Swiss journal Der Kreis ("The Circle"). In one of them he joined the ongoing debate on terminology by suggesting the terms Androtrop and Gynäkotropin for male and female homosexuals, respectively. Hiller coined these German terms from the Greek words tropos (turning [to]) combined with "andro-" (male) and "gynaiko-" (female), with the addition of the German feminine ending "in". Neither term was adopted, though the first briefly gained some favor.