Browsing by Author "Mishra, A."

Filter results by typing the first few letters
Now showing 1 - 2 of 2
  • Thumbnail Image
    Article
    Citation Count: 10
    Component Co-Evolution and Component Dependency: Speculations and Verifications
    (Wiley, 2010) Yu, L.; Mıshra, Alok; Mishra, A.; Ramaswamy, S.; Software Engineering
    Software component interaction is essential for realising proper software system functions. Such interactions between software components induce interdependencies between multiple components. One effect of such a dependency is co-evolution, wherein changes made to one component also requires corresponding changes to other component(s). This study presents a mathematical framework for representing component co-evolution. Two types of co-evolution, internal co-evolution and external co-evolution are defined for an evolving software component. The component dependency metrics that are related with component co-evolutions are analysed and the correlations between component dependency and component co-evolution are hypothesised. Further, in a quasi-experiment of nine open-source Java projects, component dependencies are measured and component revision histories are mined to verify the speculated correlations.
  • Thumbnail Image
    Article
    Citation Count: 9
    Efficient Software Review Process for Small and Medium Enterprises
    (inst Engineering Technology-iet, 2007) Mishra, D.; Mıshra, Alok; Mishra, A.; Software Engineering
    A considerable amount of software is produced world-wide by small and medium enterprises (SMEs). These organisations do not have enough resources to implement a rigorous quality plan. It has been established that reviews of various artifacts play a very important role in ensuring the quality of software. Traditional review methods are rigorous and their implementation is cumbersome for SMEs. A new review process which is easy to implement and requires almost no documentation is introduced. It is based on reviewers' efforts to produce high-quality software while minimising the inspection cost. Additionally, people who are conducting this review need not be present at the same place during most phases of the review process. This process has been successfully implemented in a CMM level 3 software development company intending to achieve CMMI level 5 and results are found to be quite encouraging.