Browsing by Author "Stan Jarzabek"

Now showing 1 - 8 of 8
  • No Thumbnail Available
    Item
    The Case for User-Centered CASE Tools
    (1997-09-01T00:00:00Z) Stan Jarzabek; Riri Huang
    Abstract not available.
  • No Thumbnail Available
    Item
    Conceptual Modeling for Families of Software Systems
    (1994-08-01T00:00:00Z) Stan Jarzabek; Tang Siong Tiing
    Conceptual models must be sometimes built for a family of software systems rather than for a single system. Situations when this happens include evolutionary software development, software reengineering and reuse. In all those cases a conceptual model should characterize a given application domain and all the systems in that domain, e.g., payroll. For example, in software reuse, we look for reoccurring features (or concepts) such as objects, business rules, procedures, requirement/design patterns and code modules that can be reused across payroll systems. Capturing commonalties is a primary goal of a conceptual model. But apart from commonalties, we find that there are also some variations in feature specifications from one system to another. For example, some of the employee characteristics or rules for computing employee salary may differ from one payroll system to another. The premise of work described in this paper is that conceptual models should capture both commonalties and differences across a family of similar systems. In the reuse context, if variations in feature specification are not anticipated and explicitly modeled, customization of a component for reuse will not be easy: component customization will be done in an ad hoc way and programmers will have to go through the same customization process many times. Such reuse will be expensive and resulting systems will be difficult to maintain. These problems can be avoided if we explicitly model variations in feature specification. This paper shows how such multi-version models can be created. Conceptual models are composed of frames organized in Object-Oriented way. Our domain modeling method combines independent domain analysis and reverse engineering of low level design abstractions from existing programs.
  • No Thumbnail Available
    Item
    Domain Model-Driven Software Reengineering and Maintenance
    (1992-03-01T00:00:00Z) Stan Jarzabek
    Abstract not available.
  • No Thumbnail Available
    Item
    A Knowledge Model for Business Re-engineering Methods and Tools
    (1995-03-01T00:00:00Z) Stan Jarzabek; Tok Wang Ling
    What do we need to know about the business in order to understand and, eventually, to improve business operations? Many business modeling methods have been described in literature and applied in business re-engineering projects. We feel that current business modeling methods do not have a precise enough model of the underlying business knowledge. A model should be comprehensive enough to allow for a systematic study and precise formulation of re-engineering methods. It should also provide a conceptual framework for designing tools to support business re-engineering projects. We identified information requirements for business re-engineering based on the commonly used business re-engineering methods and case studies published in the literature. We formalized these requirements within the business knowledge model that is described in this paper. The business knowledge models vary from company to company and from one business re-engineering project to another. Therefore, we build a generic model first and then we customize the generic model to needs of a given company and to a business re-engineering project in hand. We build the core of a tool environment for business understanding and re-engineering around the generic business model. The business knowledge model defines conceptual schema for the business knowledge to be acquired and stored in a tool repository. We derive the physical schema for tool repository and generate customized tools from the customized business knowledge model specifications. Tools built around our model can support business knowledge acquisition, business process modeling, performance/quality analysis and analysis of alternative business process re-engineering solutions. We use frames to model business features such as a customer, business process or event. Frames are organized into an inheritance network. Frame slots describe properties of features in the mixture of formal and informal specifications. In the paper, we describe the generic business knowledge model, explain how we use the model and discuss user-level views of the model.
  • No Thumbnail Available
    Item
    A Lifecycle Approach to Strategic Reengineering of Software
    (1992-09-01T00:00:00Z) Stan Jarzabek
    Abstract not available.
  • No Thumbnail Available
    Item
    Model-based Design of Tools for Business Understanding and Re-engineering
    (1995-03-01T00:00:00Z) Stan Jarzabek; Tok Wang Ling
    Tools can provide useful assistance for business re-engineering planning. Activities such as business knowledge acquisition, business process modeling, performance, quality and impact analysis all can be done more effectively if supported by proper tools. In this paper, we describe a design scenario for business understanding and re-engineering tools that is based on systematic modeling of business knowledge. The business knowledge model forms conceptual schema for the tool repository. We start by building a generic business model. As both the model and required tool characteristics vary from company to company and from one business re- engineering project to another, we customize the generic model and tools to reflect needs of a given company and a business re-engineering project in hand. We achieve a required level of tool flexibility by applying meta-CASE techniques. The physical repository schema and tools themselves are automatically generated from the customized business model specifications. In the paper, we describe components of an integrated computer-aided business understanding and re-engineering tool environment. We illustrate benefits of building tools on a rich business model, focusing on tools and analysis methods that have not been extensively described in other sources. In particular, we describe an interview assistant tool, support for impact analysis methods and an end-user query language in which a user can define new business analysis methods, not supported by a generic tool environment.
  • No Thumbnail Available
    Item
    An Object-Oriented Model for Recovered Designs in Software Engineering
    (1993-03-01T00:00:00Z) Stan Jarzabek; K Tham
    Abstract not available.
  • No Thumbnail Available
    Item
    Towards a Precise Description of Reverse Engineering Methods and Tools
    (1997-09-01T00:00:00Z) Stan Jarzabek; Irene Woon
    Abstract not available.