Software architecture is represented by different views that are derived from architectural concerns. However, when different design methods are applied to generate different views, implicit conflicts might happen between views, due to neglecting the concern conflicts behind each view. To solve this problem, this study uses the software architecture documentation as a common communication platform and derives the implicit conflicts between different views through a procedure of four activities. In this approach, a guideline is suggested to model the relationship between the concerns and views and a set of mathematical representation that is defined for precisely presenting the relations in order to support the automation of the approach.