What’s a technical way to describe removed functionality in a software application or framework?

I’m not trained programmer, so be gentle with my ignorance.
I’m trying to search changelog files for where an open source project dropped a feature I need. I was just wondering if there may be a good set of terms to describe this.

What is the name to differentiate between parts of an app that have different types of users in each part?

On a project I’m working on, I’m trying to find a noun to describe the different parts of the application dependent on user interface. There are three parts: super admin, admin and regular users. Each of these parts consist of modules, interfaces with users, interfaces with the other parts.

Are the terms stable and reliable interchangeable?

Is there a difference between stability and reliability (at least in software engineering context) or can they be used interchangeably? If not, what would be some examples of reliable but not necessarily stable systems, and vice versa?

What is the term for this type of refactoring

I am sure there is a term for the following bit of refactoring, but I can’t remember it and my Google-fu is failing me!

Is functional spec a “design document”?

So I have been a bit lost in the terms, so first of all I present you what I have learned so far:
System requirements specification – what users want, what the system should do
Functional requirement – how the things, which users want, will actually work in the application

What does the term “Payload” mean in programming

I was going through the source code of an open source framework, where I saw a variable “payload” mentioned many times. Any ideas what “payload” stands for?

Coincidence or rule?

I was reading about Assemblies (modules, which Microsoft CLR works with). The Assembly contains so called Manifest, which by definition describes a set of files in the Assembly.

What does it mean by expected running time and average running time of an algorithm?

Let’s say we want to analyze running time of algorithms. Sometimes we say that we want to find the running time of an algorithm when the input size is n and for the worst possible case it is denote it by O(n). Sometimes though I see books/papers saying that we need to find the expected time of an algorithm. Also sometimes the average running time is used .

What makes a component or product “enterprise” software vs non-enterprise ready? [duplicate]

Possible Duplicate:

parsing terminology: comments+whitespaces vs actual code

In languages like c/c++ spacing and comments are ignored and only actual code gets into compiler.
I’m interested if there is accepted way of naming these two things?