Identity formation is the process of the development of the distinct personality of an individual regarded as a persisting entity (known as personal continuity) in a particular stage of life in which individual characteristics are possessed by which a person is recognized or known (such as the establishment of a reputation). This process defines an individual to others and themselves. Pieces of the entity's actual identity include a sense of continuity, a sense of uniqueness from others, and a sense of affiliation. Identity formation leads to a number issues of personal identity and an identity where the individual has some sort of comprehension of him or herself as a discrete, separate entity. This may be through individuation whereby the undifferentiated individual tends to become unique, or undergoes stages through which differentiated facets of a person's life tend toward becoming a more indivisible whole.

Theory of developmental stages
Self-concept or self-identity is the sum total of a being's knowledge and understanding of his or her self. The self-concept is different from self-consciousness, which is an awareness of one's self. Components of the self-concept include physical, psychological, and social attributes, which can be influenced by the individual's attitudes, habits, beliefs and ideas. These components and attributes can not be condensed to the general concepts of self-image and the self-esteem.
Cultural identity is the (feeling of) identity of a group or culture, or of an individual as far as she/he is influenced by her/his belonging to a group or culture. Cultural identity is similar to and has overlaps with, but is not synonymous with, identity politics. There are modern questions of culture that are transferred into questions of identity. An ethnic identity is the identification with a certain ethnicity, usually on the basis of a presumed common genealogy or ancestry. Recognition by others as a distinct ethnic group is often a contributing factor to developing this bond of identification. Ethnic groups are also often united by common cultural, behavioral, linguistic, ritualistic, or religious traits. Processes that result in the emergence of such identification are summarized as ethnogenesis. Various cultural studies and social theory investigate the question of cultural and ethnic identities. Cultural identity remarks upon: place, gender, race, history, nationality, sexual orientation, religious beliefs and ethnicity. National identity is an ethical and philosophical concept whereby all humans are divided into groups called nations. Members of a "nation" share a common identity, and usually a common origin, in the sense of ancestry, parentage or descent.
A religious identity is the set of beliefs and practices generally held by an individual, involving adherence to codified beliefs and rituals and study of ancestral or cultural traditions, writings, history, and mythology, as well as faith and mystic experience. The term "religious identity" refers to the personal practices related to communal faith and to rituals and communication stemming from such conviction.
In business, a professional identity is the "persona" of a professional which is designed to accord with and facilitate the attainment of business objectives. A professional identity comes into being when there is a philosophy which is manifest in a distinct corporate culture - the corporate personality. A business professional is a person in a profession with certain types of skills that sometimes requiring formal training or education. The career development of an individual focuses on how individuals manage their careers within and between organizations and how organizations structure the career progress of their members, can be tied into succession planning within some organizations.
In sociology, gender identity describes the gender with which a person identifies (i.e, whether one perceives oneself to be a man, a woman, or describes oneself in some less conventional way), but can also be used to refer to the gender that other people attribute to the individual on the basis of what they know from gender role indications (social behavior, clothing, hair style, etc.). Gender identity may be affected by a variety of social structures, including the person's ethnic group, employment status, religion or irreligion, and family.

Interpersonal identity development

Main article: Hegelian dialectic Self, other, and interaction
Individuals gain a social identity and group identity by their affiliation. This is from membership in various groups. These groups include, among various categories,:
The term collective identity is a sense of belonging to a group (the collective) that is so strong that a person who identifies with the group will dedicate his or her life to the group over individual identity: he or she will defend the views of the group and assume risks for the group, sometimes as great as loss of life. The cohesiveness of the collective goes beyond community, as the collective suffers the pain of grief from the loss of a member.

family
ethnic
occupation
friendship
dating
sex roles See also

Keith Campbell may refer to:
Keith Campbell (biologist), English biologist involved in the study of cloning.
Keith Campbell (motorcyclist), Australian former Grand Prix motorcycle world champion.
Keith Campbell (philosopher)
Keith Campbell (cricketer), New Zealand cricketer
Keith Campbell (ice hockey)

Israel (Hebrew: יִשְׂרָאֵל, Yisra'el), officially the State of Israel (Hebrew: מְדִינַת יִשְׂרָאֵל (help·info), Medinat Yisra'el; Arabic: دَوْلَةْ إِسْرَائِيل, Dawlat Isrā'īl), is a country in Asia located on the southeastern edge of the Mediterranean Sea. It has borders with Lebanon in the north, Syria and Jordan in the east, and Egypt on the southwest, and contains geographically diverse features within its relatively small area. Partly or wholly reckoned in Oceania.
 Djibouti  ·   Egypt  ·   Eritrea  ·   Israel  ·   Jordan  ·   Saudi Arabia  ·   Somalia  ·   Sudan  ·   Yemen
   Egypt
 Ethiopia

Ausubel, Natan (1964), The Book of Jewish Knowledge, New York, New York: Crown Publishers, ISBN 051709746X
Barton, John & Julie Bowden (2004), The Original Story: God, Israel and the World, Wm. B. Eerdmans Publishing Company, ISBN 0802829007
Best, Anthony (2003), International History of the Twentieth Century, Routledge, ISBN 0415207398
Bregman, Ahron (2002), A History of Israel, Palgrave Macmillan, ISBN 0333676319
Cole, Tim (2003), Holocaust City: The Making of a Jewish Ghetto, Routledge, ISBN 0415929687
Crowdy, Terry (2006), The Enemy Within: A History of Espionage, Osprey Publishing, ISBN 1841769339
Dekmejian, R. Hrair (1975), Patterns of Political Leadership: Egypt, Israel, Lebanon, State University of New York Press, ISBN 087395291X
Gelvin, James L. (2005), The Israel-Palestine Conflict: One Hundred Years of War, Cambridge University Press, ISBN 0521852897
Gilbert, Martin (2005), The Routledge Atlas Of The Arab-Israeli Conflict (8th ed.), Routledge, ISBN 0415359007
Goldreich, Yair (2003), The Climate of Israel: Observation, Research and Application, Springer, ISBN 030647445X
Hamilton, Victor P. (1995), The Book of Genesis (2nd revised ed.), Wm. B. Eerdmans Publishing Company, ISBN 0802823092
Harkavy, Robert E. & Stephanie G. Neuman (2001), Warfare and the Third World, Palgrave Macmillan, ISBN 0312240120
Kornberg, Jacques (1993), Theodor Herzl: From Assimilation to Zionism, Indiana University Press, ISBN 0253332036
Laqueur, Walter (2003), The History of Zionism, Tauris Parke Paperbacks, ISBN 1860649327
Lustick, Ian (1988), For the Land and the Lord: Jewish Fundamentalism in Israel, Council on Foreign Relations Press, ISBN 0876090366
Mazie, Steven (2006), Israel's Higher Law: Religion and Liberal Democracy in the Jewish State, Lexington Books, ISBN 0739114859
Morçöl, Göktuğ (2006), Handbook of Decision Making, CRC Press, ISBN 1574445480
Mowlana, Hamid; George Gerbner & Herbert I. Schiller (1992), Triumph of the Image: The Media's War in the Persian Gulf — A Global Perspective, Westview Press, ISBN 0813316103
Rosenzweig, Rafael (1997), The Economic Consequences of Zionism, Brill Academic Publishers, ISBN 9004091475
Rees, Matt (2004), Cain's Field: Faith, Fratricide, and Fear in the Middle East, Simon and Schuster, ISBN 0743250478
Scharfstein, Sol (1996), Understanding Jewish History, KTAV Publishing House, ISBN 0881255459
Shamir, Michal & Alan Arian (2002), The Elections in Israel, 1999, State University of New York Press, ISBN 0791453154
Skolnik, Fred (2007), Encyclopedia Judaica, vol. 9 (2nd ed.), Macmillian, ISBN 0028659287
Shindler, Colin (2002), The Land Beyond Promise: Israel, Likud and the Zionist Dream, I.B.Tauris Publishers, ISBN 186064774X
Smith, Derek (2006), Deterring America: Rogue States and the Proliferation of Weapons of Mass Destruction, Cambridge University Press, ISBN 0521864658
Stendel, Ori (1997), The Arabs in Israel, Sussex Academic Press, ISBN 1898723230
Wenham, Gordon J. (1994), Word Biblical Commentary, vol. 2 (Genesis 16-50), ISBN 0849902010
(Hebrew) Israel Government Portal (with links to English, Arabic versions)
(Hebrew) Prime Minister's Office, official site (with links to English, Arabic versions)
(Hebrew) President of the State of Israel, official site (with links to English, Arabic versions)
The Knesset, official site of Israel's parliament
(Hebrew) The Supreme Court, official site (with links to English, Arabic versions)
Ministry of Foreign Affairs, official site
(Hebrew) Central Bureau of Statistics, official site (with links to English, Arabic versions)
Ministry of Tourism, official site
CIA World Factbook entry on Israel
Encyclopædia Britannica entry on Israel
BBC country profile of Israel
Library of Congress Country Studies entry on Israel
Columbia University library related to Israel
The Jerusalem Post, Israel's most popular English-language newspaper
Ynet News, based on Tel Aviv
(Hebrew) Israel Broadcasting Agency, state broadcasting network (with link to English version)
Israel travel guide from Wikitravel
Israel at WikiMapia
Israel at the Open Directory Project
Wikimedia Atlas of Israel, holding maps related to Israel.

Extreme Programming (or XP) is a software engineering methodology, the most prominent
Proponents of XP and agile methodologies in general regard ongoing changes to requirements as a natural, inescapable and desirable aspect of software development projects; they believe that adaptability to changing requirements at any point during the project life is a more realistic and better approach than attempting to define all requirements at the beginning of a project and then expending effort to control changes to the requirements.

History
Software development in the 1990s was shaped by two major influences: internally, object-oriented programming replaced procedural programming as the programming paradigm favored by some in the industry; externally, the rise of the Internet and the dot-com boom emphasized speed-to-market and company-growth as competitive business factors. Rapidly-changing requirements demanded shorter product life-cycles, and were often incompatible with traditional methods of software development.
The Chrysler Comprehensive Compensation project was started in order to determine the best way to use object technologies, using the payroll systems at Chrysler as the object of research, with Smalltalk as the language and GemStone as the data access layer. They brought in Kent Beck, a prominent Smalltalk practitioner, to do performance tuning on the system, but his role expanded as he noted several issues they were having with their development process. He took this opportunity to propose and implement some changes in their practices based on his work with his frequent collaborator, Ward Cunningham.
The first time I was asked to lead a team, I asked them to do a little bit of the things I thought were sensible, like testing and reviews. The second time there was a lot more on the line. I thought, "Damn the torpedoes, at least this will make a good article," [and] asked the team to crank up all the knobs to 10 on the things I thought were essential and leave out everything else. —Kent Beck
Beck invited Ron Jeffries to the project to help develop and refine these methods. Jeffries thereafter acted as a coach to instill the practices as habits in the C3 team.
Information about the principles and practices behind XP was disseminated to the wider world through discussions on the original Wiki, Cunningham's WikiWikiWeb. Various contributors discussed and expanded upon the ideas, and some spin-off methodologies resulted (see agile software development). Also, XP concepts have been explained, for several years, using a hyper-text system map on the XP website at "www.extremeprogramming.org" circa 1999 (website ^XPORG).
Beck edited a series of books on XP, beginning with his own Extreme Programming Explained (1999, ISBN 0-201-61641-6), spreading his ideas to a much larger, yet very receptive, audience. Authors in the series went through various aspects attending XP and its practices, even a book critical of the practices.

Origins
XP created quite a buzz in the late 1990s and early 2000s, seeing adoption in a number of environments radically different from its origins.
The high discipline required by the original practices often went by the wayside, causing certain practices to be deprecated or left undone on individual sites. Agile development practices have not stood still, and XP is still evolving, assimilating more lessons from experiences in the field. In the second edition of Extreme Programming Explained, Beck added more values and practices and differentiated between primary and corollary practices.

Current state
Extreme Programming Explained describes Extreme Programming as being:
The main aim of XP is to reduce the cost of change. In traditional system development methods (like SSADM) the requirements for the system are determined at the beginning of the development project and often fixed from that point on. This means that the cost of changing the requirements at a later stage (a common feature of software engineering projects) will be high.
XP sets out to reduce the cost of change by introducing basic values, principles and practices. By applying XP, a system development project should be more flexible with respect to changes.

An attempt to reconcile humanity and productivity
A mechanism for social change
A path to improvement
A style of development
A software development discipline Goal of XP
Extreme Programming initially recognized four values in 1999. A new value was added in the second edition of Extreme Programming Explained. The five values are:
Building software systems requires communicating system requirements to the developers of the system. In formal software development methodologies, this task is accomplished through documentation. Extreme Programming techniques can be viewed as methods for rapidly building and disseminating institutional knowledge among members of a development team. The goal is to give all developers a shared view of the system which matches the view held by the users of the system. To this end, Extreme Programming favors simple designs, common metaphors, collaboration of users and programmers, frequent verbal communication, and feedback.
Extreme Programming encourages starting with the simplest solution and refactoring to better ones. The difference between this approach and more conventional system development methods is the focus on designing and coding for the needs of today instead of those of tomorrow, next week, or next month. Proponents of XP acknowledge the disadvantage that this can sometimes entail more effort tomorrow to change the system; their claim is that this is more than compensated for by the advantage of not investing in possible future requirements that might change before they become relevant. Coding and designing for uncertain future requirements implies the risk of spending resources on something that might not be needed. Related to the "communication" value, simplicity in design and coding should improve the (quality of) communication. A simple design with very simple code could be easily understood by most programmers in the team.
Within Extreme Programming, feedback relates to different dimensions of the system development:
Feedback is closely related to communication and simplicity. Flaws in the system are easily communicated by writing a unit test that proves a certain piece of code will break. The direct feedback from the system tells programmers to recode this part. A customer is able to test the system periodically according to the functional requirements (aka user stories). To quote Kent Beck, "Optimism is an occupational hazard of programming, feedback is the treatment."
Several practices embody courage. One is the commandment to always design and code for today and not for tomorrow. This is an effort to avoid getting bogged down in design and requiring a lot of effort to implement anything else. Courage enables developers to feel comfortable with refactoring their code when necessary. This means reviewing the existing system and modifying it so that future changes can be implemented more easily. Another example of courage is knowing when to throw code away: courage to remove source code that is obsolete, no matter how much effort was used to create that source code. Also, courage means persistence: A programmer might be stuck on a complex problem for an entire day, then solve the problem quickly the next day, if only they are persistent.
The respect value manifests in several ways. In Extreme Programming, team members respect each other because programmers should never commit changes that break compilation, that make existing unit-tests fail, or that otherwise delay the work of their peers. Members respect their work by always striving for high quality and seeking for the best design for the solution at hand through refactoring.
Adopting four earlier values led to respect gained from others in team. Nobody on the team should feel unappreciated or ignored. This ensures high level of motivation and encourages loyalty toward the team, and the goal of the project. This value is very dependent upon the other values, and is very much oriented toward people in a team.

Communication
Simplicity
Feedback
Courage
Respect
Feedback from the system: by writing unit tests, or running periodic integration tests, the programmers have direct feedback from the state of the system after implementing changes.
Feedback from the customer: The functional tests (aka acceptance tests) are written by the customer and the testers. They will get concrete feedback about the current state of their system. This review is planned once in every two or three weeks so the customer can easily steer the development.
Feedback from the team: When customers come up with new requirements in the planning game the team directly gives an estimation of the time that it will take to implement. XP values
The principles that form the basis of XP are based on the values just described and are intended to foster decisions in a system development project. The principles are intended to be more concrete than the values and more easily translated to guidance in a practical situation.
Feedback is most useful if it is done rapidly. The time between an action and its feedback is critical to learning and making changes. In Extreme Programming, unlike traditional system development methods, contact with the customer occurs in small iterations. The customer has clear insight into the system that is being developed. He or she can give feedback and steer the development as needed.
Unit tests also contribute to the rapid feedback principle. When writing code, the unit test provides direct feedback as to how the system reacts to the changes one has made. If, for instance, the changes affect a part of the system that is not in the scope of the programmer who made them, that programmer will not notice the flaw. There is a large chance that this bug will appear when the system is in production.
Assuming simplicity is about treating every problem as if its solution were "extremely simple". Traditional system development methods say to plan for the future and to code for reusability. Extreme programming rejects these ideas.
The advocates of Extreme Programming say that making big changes all at once does not work. Extreme Programming applies incremental changes: for example, a system might have small releases every three weeks. By making many little steps the customer has more control over the development process and the system that is being developed.
The principle of embracing change is about not working against changes but embracing them. For instance, if at one of the iterative meetings it appears that the customer's requirements have changed dramatically, programmers are to embrace this and plan the new requirements for the next iteration.

Principles
XP describes four basic activities that are performed within the software development process.

Activities
The advocates of XP argue that the only truly important product of the system development process is code (a concept to which they give a somewhat broader definition than might be given by others). Without code you have nothing.
Coding can be drawing diagrams that will generate code, scripting a web-based system or coding a program that needs to be compiled.
Coding can also be used to figure out the most suitable solution. For instance, XP would advocate that faced with several alternatives for a programming problem, one should simply code all solutions and determine with automated tests (discussed in the next section) which solution is most suitable.
Coding can also help to communicate thoughts about programming problems. A programmer dealing with a complex programming problem and finding it hard to explain the solution to fellow programmers might code it and use the code to demonstrate what he or she means. Code, say the exponents of this position, is always clear and concise and cannot be interpreted in more than one way. Other programmers can give feedback on this code by also coding their thoughts.

Coding
One cannot be certain of anything unless one has tested it. Testing is not a perceived, primary need for the customer. A lot of software is shipped without proper testing and still works (more or less). In software development, XP says this means that one cannot be certain that a function works unless one tests it. This raises the question of defining what one can be uncertain about.

You can be uncertain whether what you coded is what you meant. To test this uncertainty, XP uses Unit Tests. These are automated tests that test the code. The programmer will try to write as many tests he or she can think of that might break the code he or she is writing; if all tests run successfully then the coding is complete.
You can be uncertain whether what you meant is what you should have meant. To test this uncertainty, XP uses acceptance tests based on the requirements given by the customer in the exploration phase of release planning. Testing
Programmers do not necessarily know anything about the business side of the system under development. The function of the system is determined by the business side. For the programmers to find what the functionality of the system should be, they have to listen to business.
Programmers have to listen "in the large": they have to listen to what the customer needs. Also, they have to try to understand the business problem, and to give the customer feedback about his or her problem, to improve the customer's own understanding of his or her problem.
Communication between the customer and programmer is further addressed in The Planning Game.

Listening
From the point of view of simplicity, one could say that system development doesn't need more than coding, testing and listening. If those activities are performed well, the result should always be a system that works. In practice, this will not work. One can come a long way without designing but at a given time one will get stuck. The system becomes too complex and the dependencies within the system cease to be clear.
One can avoid this by creating a design structure that organizes the logic in the system. Good design will avoid lots of dependencies within a system; this means that changing one part of the system will not affect other parts of the system.

Practices
Unstable Requirements: Proponents of Extreme Programming claim that by having the on-site customer request changes informally, the process becomes flexible, and saves the cost of formal overhead. Critics of XP claim this can lead to costly rework and project scope creep beyond what was previously agreed or funded.
User Conflicts: Change control boards are a sign that there are potential conflicts in project objectives and constraints between multiple users. XP's expedited methodology is somewhat dependent on programmers being able to assume a unified client viewpoint so the programmer can concentrate on coding rather than documentation of compromise objectives and constraints. This also applies when multiple programming organizations are involved, particularly organizations which compete for shares of projects.
Other Aspects: Other controversial aspects of Extreme Programming include:
Dependence upon all other aspects of XP: "XP is like a ring of poisonous snakes, daisy-chained together. All it takes is for one of them to wriggle loose, and you've got a very angry, poisonous snake heading your way." was introduced as an evolution of XP. It brings ability to work in big and distributed teams. It now has 23 practices and flexible changeable values. As it is a new member of Agile family, there is not enough data to prove its usability, however it claims to be an answer to XP's imperfections.
Hybrid/Unified Methodologies: Other authors have tried to reconcile XP with the older methods in order to form a unified methodology. Some of these XP sought to replace, such as the waterfall method; example: Project Lifecycles: Waterfall, Rapid Application Development, and All That.
JPMorgan Chase & Co. tried combining XP with the computer programming methodologies of Capability Maturity Model Integration (CMMI), and Six Sigma. They found that the three systems reinforced each other well, leading to better development, and did not mutually contradict, see Extreme Programming (XP) Six Sigma CMMI.
Finally, XP is not the only controversial methodology, because XP is a response to the controversy and criticisms about other methods used in software development.

Requirements are expressed as automated acceptance tests rather than specification documents.
Requirements are defined incrementally, rather than trying to get them all in advance.
Software developers are required to work in pairs.
There is no Big Design Up Front. Most of the design activity takes place on the fly and incrementally, starting with "the simplest thing that could possibly work" and adding complexity only when it's required by failing tests. Critics fear this would result in more re-design effort than only re-designing when requirements change.
A customer representative is attached to the project. This role can become a single-point-of-failure for the project, and some people have found it to be a source of stress. Also, there is the danger of micro-management by a non-technical representative trying to dictate the use of technical software features and architecture. Application of Extreme Programming

Software Development Rhythms
Software engineering
Agile software development
Extreme project management
Extreme Programming Practices
Pair Programming
Toyota Production System
List of software development philosophies

A differential equation is a mathematical equation for an unknown function of one or several variables which relates the values of the function itself and of its derivatives of various orders. Differential equations play a prominent role in engineering, physics, economics, and other disciplines.

Introduction
The study of differential equations is a wide field in both pure and applied mathematics. Pure mathematicians study the types and properties of differential equations, such as whether or not solutions exist, and should they exist, whether they are unique. Applied mathematicians emphasize differential equations from applications, and in addition to existence/uniqueness questions, are also concerned with rigorously justifying methods for approximating solutions. Physicists and engineers are usually more interested in computing approximate solutions to differential equations, and are typically less interested in justifications for whether these approximations really are close to the actual solutions. These solutions are then used to simulate celestial motions, simulate neurons, design bridges, automobiles, aircraft, sewers, etc. Often, these equations do not have closed form solutions and are solved using numerical methods.
Mathematicians also study weak solutions (relying on weak derivatives), which are types of solutions that do not have to be differentiable everywhere. This extension is often necessary for solutions to exist, and it also results in more physically reasonable properties of solutions, such as shocks in hyperbolic (or wave) equations.
The study of the stability of solutions of differential equations is known as stability theory.

Types of differential equations
The theory of differential equations is closely related to the theory of difference equations, in which the coordinates assume only discrete values, and the relationship involves values of the unknown function or functions and values at nearby coordinates. Many methods to compute numerical solutions of differential equations or study the properties of differential equations involve approximation of the solution of a differential equation by the solution of a corresponding difference equation.

Connection to difference equations
A large number of fundamental laws of physics and chemistry can be formulated as differential equations. In biology and economics differential equations are used to model the behavior of complex systems. The mathematical theory of differential equations first developed together with the sciences where the equations had originated and where the results found application. However, diverse problems, sometimes originating in quite distinct scientific fields, may give rise to identical differential equations. Whenever this happens, mathematical theory behind the equations can be viewed as a unifying principle behind diverse phenomena. As an example, consider propagation of light and sound in the atmosphere, and of waves on the surface of a pond. All of them may be described by the same second order partial differential equation, the wave equation, which allows us to think of light and sound as forms of waves, much like familiar waves in the water. Conduction of heat, whose theory was brilliantly developed by Joseph Fourier, is governed by another second order partial differential equation, the heat equation. It turned out that many diffusion processes, while seemingly different, are described by the same equation; Black-Scholes equation in finance is for instance, related to the heat equation.

Famous differential equations

Picard-Lindelöf theorem on existence and uniqueness of solutions

All India Institute of Medical Sciences
All India Institute of Medical Sciences (AIIMS) (created 1956) is a medical college in India. It is located in New Delhi. It has been consistently ranked the top medical college in India by India Today.
It is one of India's Institutes of National Importance, a distinguished category of premier institutions including the IITs, Indian Statistical Institute, ICAR etc.

Academics

Admission
Every year AIIMS accepts 45 students, of which 33 belong to General Category and 11 belong to the reserved category (SC/ST) and 1 orthopedic physically handicapped, based on the results of an all-India entrance examination for its MBBS program. The number of students who take the entrance exam every year varies from 70,000 to 80,000. Five international students (nominated by Government of India) complete the class size of 50.
AIIMS also specializes in paramedical and basic science training.

MBBS course
There are about 42 speciality post-graduate courses conducted at AIIMS. The entry is through a nationwide competitive examination held every six months. These courses are highly coveted by the medical graduates across the country because of the institution's excellent medical services, exposure to unusual & referred cases and excellent opportunities for research.

Post-graduate courses
AIIMS has been ranked repeatedly at the top in its field in annual surveys (starting in 1997) published by India Today.

Ranking
AIIMS was originally built as a Superspeciality

Integrating clinics and research
As per the AIIMS Citizen's Charter,

Medical services
There is a separate cardiothoracic and neurosciences centre (CNC) offering superspeciality level patient care, training and research in the respective fields.
Dr. Rajendra Prasad Centre for Ophthalmic Sciences is a 300 bed ophthalmic (eyes) speciality centre devoted to the education, research and patient care. It is designated as the apex eye referral centre for India and is the WHO collaborating centre for ophthalmic programs.
Recently Dr. BR Ambedkar Institute Rotary Cancer Hospital's construction has been completed. It specializes in medical, radiation and surgical oncology.
Jai Prakash Narayan Apex Trauma Centre is the latest addition to the existing facilities. It is India's first full-fledged trauma centre to treat victims of trauma. It is located about 1 KM west from the main campus.

Speciality Centres at AIIMS
AIIMS is a residential university where the faculty members, staff and students live on either the main campus or one of the several campuses which form a part of the Institution. There are five hostels for men undergraduate students and a single hostel available for women undergraduate students. These six hostels together can accommodate 850 students. For Post-graduate students, there are three hostels available for the men students and a single hostel for the women students. Additional hostels for Nursing students and Post-graduate students are available at a facility in the Masjid Moth area, situated near to the main AIIMS campus.
Students of AIIMS involve themselves in extra-academic movements, including Pulse, the annual, inter-college festival hosted by AIIMS.

Residential facilities

AIIMS is the first Indian center to perform a successful cardiac transplant. The surgery was performed by Dr.P Venugopal, the current director of AIIMS in 1994. Achievements

Controversies
Prior to Supreme court judgment of 25th Aug, 2001 and changes in institutional quota, AIIMS was criticised for the way 33% of Post Graduation Seats were reserved for those who complete their MBBS in AIIMS. The quota has been quashed by the Supreme Court as per its Judgment in the year 2001.

Institutional Quota

Main articles: Indian anti-reservation protests, 2006 and Reservation in India Notable faculty and Alumni

PGI Chandigarh
Sanjay Gandhi PGIMS Lucknow
NEIGRIHMS Shillong
JIPMER

Andreas Palaiologos (or Palaeologus) (1453 - 1503) de jure Byzantine emperor and Despot of Morea from 1465 until death in 1503.
He was the nephew of Constantine XI Palaiologos, the last Byzantine Emperor of Constantinople. After Constantine was defeated and killed by the forces of Mehmed II on May 29, 1453, Andreas continued to live in Morea, which was ruled independently by Andreas' father Thomas Palaiologos, the younger brother of Constantine, until 1460. At this time he escaped to the Italian peninsula following an Ottoman invasion. Before entering Italy, Thomas and all his children made the conversion to the Roman Catholic religion. When his father died in 1465, Andreas stayed in Italy under the protection of the Papal States.
During his lifetime, Andreas is believed to have wasted enormous sums of money given to him by the Pope. However, modern historians now believe that the money received from the Pope was only enough for a meager standard of living.
Looking for money and a better life, Andreas tried to sell the rights to the Byzantine crown, which had fallen to him de jure since the death of his father Thomas. Charles VIII of France originally agreed to purchase the rights of succession from Andreas in 1494. However Charles predeceased him on April 7, 1498.
Andreas' younger brother Manuel Palaiologos arranged a deal with the Ottoman Sultan Bayazid II, exchanging his rights to the Byzantine throne for a comfortable pension.
Andreas died a pauper in 1502. According to his will his heirs were Ferdinand II of Aragon and Isabella of Castile. While most scholars believe Andreas left no descendants of his own, Donald M. Nicol's The Immortal Emperor recognises a Constantine Palaiologos who served in the Papal Guard and a Maria who married Russian noble Mihail Vasilivich as possible offspring of Andreas.
References
Jonathan Harris, Greek Émigrés in the West, 1400-1520, Camberley: Porphyrogenitus, 1995. ISBN 1 871328 11 X
Jonathan Harris 'A worthless prince? Andreas Palaeologus in Rome, 1465-1502', Orientalia Christiana Periodica 61 (1995), 537-54
Donald M. Nicol, The Immortal Emperor, Cambridge University Press, 1992, pp. 115-22. ISBN 0 521 41456 3.
Steven Runciman, The Fall of Constantinople 1453, Cambridge University Press, 1965, pp. 183-4. ISBN 0 521 09573 5