6

I merged modelling into modeling, since that makes sense. I'm hesitant to do anything with model since it can refer to a model in the sense of a model of a system that you make when modeling, a model of a real world thing represented in software, or part of the MVC or MVVM or similar patterns.


5

I have approved the synonym. I will merge them later.


5

Merge complete. Aspect-oriented is now the preferred tag, since it provides more meaning by itself.


5

If I would have to choose between them, I would not be able to tell the difference. So, yes, I think they should be synonyms. As third-party-libraries has the most questions (28), I think that is the best option for the master tag.


5

They definitely should be synonyms. Honestly, I'm not a huge fan of synonyms if they could be merged and these could.


5

Unfortunately, I don't have time right now (just passing through real quick), but I'd want to take a closer look at how these tags are used. As words, they are very different things. Maintenance is a phase in the product lifecycle that exists after a system has been deployed. Although systems in a maintenance phase go through some form of requirements ...


4

I think since definition does not have a wiki summary [here] it is very easy to get confused. Better solution IMO would be to properly define the definition tag itself first and then let users ask question on that basis. If the tag is explained as Define xxxxxx Then possibly terminology and definition could be merged.


4

team-foundation-server should be the base tag and tfs should be mapped to it to be in line with other synonyms.


4

Yes, those two look like they should be merged. I propose we make duplicate-questions the master tag, it might have less questions but it's a better tag than exact-duplicates.


4

Done.


4

This task has been accomplished.


4

Looking through it, it looks like most embedded and embedded-systems questions are about embedded systems. There are few enough questions that a manual cleanup can be done after a merge. I'm just thinking about what tag should be preferred. I think I'd prefer embedded-systems, even though it's half the size. I think the tag is more descriptive and more in ...


4

Good idea. Created the synonym. Not merged yet, though.


4

Done, js is now a synonym of javascript.


3

Debugging is generally the more used term. "To debug" is the infinitive. That's a tad too Shatner even for me. Boldly merged, it is.


3

For the purposes of being able to accept an answer: status-completed


3

status-completed This tag has been renamed to natural-language-processing Agreed Now that the maximum tag length has been increased to 35, I don't see any reason why this tag can't be renamed to natural-language-processing.


3

Done. I kept client-server as the master tag, since it's the more common term. Also, Stack Overflow has the same mapping. Thanks for bringing this to our attention.


3

Wikipedia says: In computer software, business logic or domain logic is the part of the program that encodes the real-world business rules that determine how data can be created, displayed, stored, and changed. I wouldn't be opposed to merging the two into the more popular business-logic, I almost wonder if the tag shouldn't be changed to domain-logic (...


3

I consider that Business Rules are the business's rules, that is, policies determined by the business, i.e. specifically by business experts and those in charge of the business, who are likely non-programmers. (https://en.wikipedia.org/wiki/Business_rule) I consider that logic is programming and thus associated more with IT than business leaders and domain ...


3

There are only 7 tags about analysis. As you pointed out, algorithm-analysis, static-analysis, and dependency-analysis are already well-defined. Looking at code-analysis, this could use a little work, too. Some of the questions are really about static analysis. Others are about code quality. Others are about managing source code. There are likely to be ...


2

Done, thanks for bringing the tags to our attention.


2

maintainability tag wiki has been edited to help reader differentiate this tag from maintenance. Excerpt was set as follows: system quality aspect characterizing the ease of software maintenance Tag wiki were set as follows: Maintainability is a system quality aspect characterizing the ease of software maintenance. Related Wikipedia references......


2

The synonym suggestion has been placed in the system. It now needs a couple of (up) votes at https://softwareengineering.stackexchange.com/tags/exceptions/synonyms to take effect.


2

I have successfully completed the merging of these two tags.


2

Yes, these tags should be merged. Merge coding-standards into coding-style, since style is not only larger, but slightly more generic.


Only top voted, non community-wiki answers of a minimum length are eligible