Tag: Software Engineering

  • DBSCAN identified clusters for early IT configuration item detection

    What the study found

    The study found that an adapted DBSCAN, or Density-Based Spatial Clustering of Applications with Noise, clustering method could be used for early identification of configuration items in an enterprise information system. It also produced cluster sets describing monolithic, modular, and service-oriented architectures.

    Why the authors say this matters

    The authors conclude that implementing the results could automate synthesis of an information system architecture description. The study suggests this may improve information system development by identifying architectural entities for design, and that this set is smaller than the set of elementary information system functions.

    What the researchers tested

    The researchers adapted DBSCAN to the task of early identifying configuration items in the functional task "Formation and maintenance of an individual plan of a scientific and pedagogical employee at a department." They used 10 functions and 12 database entities as initial configuration items and compared DBSCAN with Divisive Analysis, Agglomerative Nesting, Chameleon, and k-means using the criteria "Cumbersome solution" and "Identification of separated CIs."

    What worked and what didn't

    According to the abstract, DBSCAN made it possible to form a solution from one cluster for monolithic and modular architectures and from two clusters for service-oriented architecture. It also detected separated configuration items. These values were reported as the best among the selected clustering methods and algorithms for the stated criteria.

    What to keep in mind

    The summary does not describe detailed limitations of the study. The results are reported for one functional task and a specific set of initial configuration items, so the scope described in the abstract is limited.

    • An adapted DBSCAN clustering method was used for early identification of configuration items in an enterprise information system.
    • The study considered 10 functions and 12 database entities as initial configuration items.
    • DBSCAN produced cluster sets describing monolithic, modular, and service-oriented architectures.
    • DBSCAN detected separated configuration items and was reported as best on the two stated comparison criteria.
    • The authors say the results could help automate information system architecture description synthesis.
  • Spectral metrics predicted integration effort better than density metrics

    What the study found

    The study found that spectral measures, which are metrics based on eigenvalues from a network structure, predicted integration effort very strongly. Structural metrics also performed well, while density-based metrics did not show significant predictive validity.

    Why the authors say this matters

    The authors conclude that these findings help bridge a methodological gap between architectural complexity analysis and requirements engineering practice. They suggest the validated metrics provide a foundation for using requirements structure to predict integration effort.

    What the researchers tested

    The researchers used natural language processing methods to extract structural networks from textual requirements. They then ran a controlled experiment using molecular integration tasks as structurally equivalent stand-ins for requirements integration, taking advantage of the topological equivalence between molecular graphs and requirement networks while reducing domain expertise and semantic ambiguity.

    What worked and what didn't

    Spectral measures correlated with integration effort at above 0.95, and structural metrics correlated above 0.89. Density-based metrics did not show significant predictive validity.

    What to keep in mind

    The abstract says the experiment used molecular tasks as proxies for requirements integration, so the results are based on that controlled setting. It also notes that similar structural complexity patterns may predict integration effort in requirements engineering, but it does not provide additional limitations in the available summary.

    • Spectral measures predicted integration effort with correlations exceeding 0.95.
    • Structural metrics also predicted integration effort well, with correlations above 0.89.
    • Density-based metrics did not show significant predictive validity.
    • The study used NLP methods to extract structural networks from textual requirements.
    • A controlled experiment used molecular integration tasks as proxies for requirements integration.