Abstract: An apparatus and a method for a product-line description and verification is provided. The apparatus includes: a product-line architecture model conversion tool for classifying related architecture model components according to variant characteristics by analyzing inputted scenarios, generating a dependency relationship model by extracting a dependency relationship between architecture model elements based on a variant element, and generating a product-line architecture from an inputted architecture model based on the dependency relationship model; and a product-line architecture verification tool for receiving a scenario of a system requirement, mapping the scenario to related architecture model components, analyzing an architecture model dependency by analyzing static modeling information and dynamic modeling information of a product architecture, and generating an aspect model of the requirements, the scenario and the related architecture model components.

Abstract: In an apparatus for extracting enterprise beans from a servlet source code, a servlet source code input device receives the servlet source code and a Java class. A Java class extraction device extracts Java classes from the servlet source code. A Java class clustering device groups the Java classes on the basis of interrelated classes. A session bean extraction device and an entity bean extraction device extract a session bean and an entity bean from the clustered classes, respectively. An enterprise bean relationship information extraction device extracts relationship information between enterprise beans from the extracted session bean and entity bean.

Abstract: A method and apparatus for wrapping existing procedure oriented program into component based system are disclosed. In identification algorithm identifying a function capable of being reused in an existing system, user adjusts weighting value of basic constituent elements on the basis of only a general knowledge of a system such as use case without detailed knowledge about the system, so that a business logic is identified easily in top-down, and that a workflow of the system is identified in bottom-up to component wrap the identified business logic, thereby generating automatically the necessary constraint condition and the external interface.