Background Bipolar intuitionistic fuzzy graphs (BIFGs) extend fuzzy graphs by assigning both positive and negative membership and non-membership degrees to vertices and edges, capturing more nuanced uncertainty. The chromatic number of a BIFG, unlike that of crisp graphs, depends on the interplay of these bipolar parameters. This article introduces level graphs and strong level graphs as tools to define and compute the chromatic number of BIFGs. Method We defined a level graph of a BIFG for given thresholds on positive and negative membership values. Using these level graphs, we derive a procedure to assign colors to vertices such that two adjacent vertices have different colors. The chromatic number of the BIFG is then computed as the least number of colors necessary across all valid level graphs. Result The chromatic number of a BIFG is shown to be equal to the maximum chromatic number among its level graphs for all admissible threshold pairs. Several examples illustrate that the proposed level-graph method yields exact chromatic numbers for classes of BIFGs. Conclusion We successfully extended graph coloring to bipolar intuitionistic fuzzy graphs by introducing level graphs and strong level graphs. The chromatic number defined via these structures is well-defined and computable, providing a foundation for further study of BIFG coloring problems. Future work may explore algorithms for efficient determination and applications in bipolar uncertainty-driven scheduling or conflict resolution.
This publication proposes a definition and a classification of agile software development approaches and analyses ten software development methods that can be characterized as being "agile" against the defined criterion.
P. Abrahamsson, O. Salo, Jussi Ronkainen et al.· arXiv.org· 727 citations· ⚡54
The study shows that agile practices improve both informal and formal communication, but indicates that, in larger development situations involving multiple external stakeholders, a mismatch of adequate communication mechanisms can sometimes even hinder the communication.
M. Pikkarainen, Jukka Haikara, O. Salo et al.· Empirical Software Engineeri...· 401 citations· ⚡48
The results indicate that software engineering work practices are chosen opportunistically, adapted and configured to provide value under the constrains imposed by the startup context.
Nicolò Paternoster, Carmine Giardino, M. Unterkalmsteiner et al.· Information and Software Tec...· 394 citations· ⚡54
The perception of the impact of agile methods is predominantly positive, and several challenge areas were discovered, but based on this study, agile methods are here to stay.
M. Laanti, O. Salo, P. Abrahamsson· Information and Software Tec...· 260 citations· ⚡20
Related blog posts
MIT News · Artificial Intelligence· news.mit.eduOct 8, 2026
Jennifer Neville did not want to go into computer science—but that’s exactly where she landed. Neville discusses the starts and stops that led to her professional sweet spot and her work identifying “surprising failures” making it hard for AI to handle complexity. The post What AI gets wrong and what failure teaches us appeared first on Microsoft Research.
We use cookies to run the site and, with your consent, for analytics and to show ads.
See our Cookie Policy.