I recently came across the expression 前提に:

'feature1, just like feature2, is a way to embed classification into content, but it is designed for rigidity-focussed use cases, losing in flexibility.'

I think it means "to require", but I am very unsure, could someone confirm/infirm this?

  • Haha, I guess I'm not the only StackOverflow user here :)
    – makdad
    Commented Jun 1, 2011 at 2:51
  • 2
    actually pretty much all stackexchange users are stackoverflow users in my experiance it's hard to find a stackexchange site with no significant amount of programming users.
    – Ken Li
    Commented Jun 1, 2011 at 2:58
  • 1
    @Ken Li I was actually listening to a StackOverflow podcast, where either Joel Spolsky and Jeff Atwood were saying how a large amount of SE users are now "civilians", or people who weren't SO users first. I forget the exact fraction, but it was close to half. Commented Jul 12, 2011 at 16:31

3 Answers 3


前提 has a meaning of on the assumption that, or on the premise of.

In your case its meaning is closer to

it is designed under the assumption of rigid focused use cases.


Designed with rigid focused use cases in mind.

Another example from a site for something completely different:


Which means

On the assumption that there is a boyfriend, the 7 ways of confirming if there's a boyfriend.


前途 is "premise" and 設計 is "architected" (or in this context, "designed"). Xを前提に設計された therefore means "designed under the premise of X".

By the way, I would translate your sentence slightly differently:


Feature1, like feature2, is a way to embed into content discriminatory flags for classification. However, since they were designed under the premise of unified (homogeneous) usage cases, they lack flexibility.

Mostly the same as your translation, except for "designed for rigidity-focused use cases" :)


設計する is "to design" and 前提 could be interpreted as, say, "condition" or something that was proposed. So you could read it as "something was designed for the purposes of so-and-so".

I guess it's possible to read it as something related to requirements as you're trying to satisfy some constraint but I don't think I've ever seen 設計する used as "to require" anyway.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .