No abstract

No abstract

No abstract

Most discipline of science have their own method of investigation built on foundation that is empirical and verifiable. Cognitive Informatics is no different. Cognitive Informatics is a field that studies internal information processing mechanism of the human brain and its application in software coding and computing. This paper attempts to empirically demonstrate the amount of information contained in software and develops a concept of cognitive information complexity measure based on the information contained in the software. It is found that software with higher cognitive information complexity measure has more information units contained in it. Therefore cognitive information complexity measure can be used to understand the cognitive information complexity and the information coding efficiency of the software.

Due to the constant change in technology, lack of standardization, difficulties of changes and absence of distributed architecture, the business value of legacy systems have become weaker. We cannot undermine the importance of legacy systems because some of their functions are too valuable to be discarded and too expensive to reproduce. The software industry and researchers have recently paid more attention towards the component based software development to enhance the productivity and accelerate time to market. Instead of re-implementing the business critical applications with-in time and resource constraints, the best option is Software Reengineering (SRE) with effective design and architecture which can make the system better for reusability and maintainability. The main motive behind the reengineering is integrating the legacy system with emerging technologies.To achieve these goals, we have proposed a systematic and concrete model named as Component Oriented Reverse Engineering (CORE). It aims to identify and develop reusable software components. By using the reverse engineering techniques; we can extract architectural information and services from legacy system and later on convert these services into components Keywords: legacy system, reverse engineering, component based software engineering, component oriented reverse engineering, CRUD matrix. CREATING REUSABLE SOFTWARE COMPONENT FROM OBJECT-ORIENTED LEGACY SYSTEM THROUGH RESERVE ENGINEERING 134J OURNAL OF OBJECT TECHNOLOGY

The various complexity measure established so far are based on code and cognitive value of the software. It is established that a high quality SRS is pre requisite for high quality software, hence this work attempts to empirically demonstrate that the complexity of the code to be produced can be determined based on IEEE software requirement specification document (IEEE 830-1993). Considering the shortcoming of code based approaches, the proposed approach is able to compute the complexity of yet to be coded software immediately after freezing the requirement in SDLC (Software Development Life Cycle) process. Results obtained show that the complexity values are comparable with other established measures and hence the complexity of the software to be produced could be computed from SRS documents. Its validity is established by evaluating proposed measure against Weyuker properties.

No abstract

Requirement engineering document (IEEE-830: 1998) plays a very significant role in software development. The size and complexity of software systems are continuously increasing. As scale changes to more complex and larger systems, new problems occur that did not exist in smaller systems This leads to redefining priorities of the activities that go into developing software. As systems ges complex, it becomes evident that the goals of the entire system can't be easily comprehended. Hence the need of more rigorous requirement analysis arises. The requirement analyst has to identify the requirements by using various methods like interviews, brainstorming, FAST (facilitated application specification techniques), quality function deployment, use-case etc. To overcome these issues, this paper proposes object based semi-automated system that categorize the requirements and further identifies the component based on requirement engineering document in a component library and further analyses the complexity of components and its usage.