JPH11259283A - Software development method and development system - Google Patents

Abstract

(57) [Summary] [Problem] A software development method for classifying objects included in a framework and associating the objects with a viewpoint for understanding the framework so as to smoothly develop an application system based on the framework. And provide a development system. SOLUTION: The objects included in the framework are classified and arranged, the association with the design judgment is managed, and the environment surrounding the object such as the user of the application system assumed by the framework and the related system and the object are controlled. , The understanding of the framework can be facilitated, the changed portion of the framework can be easily specified, and the application system based on the framework can be smoothly developed.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

[0001] The present invention relates to a software development method and a development system for developing an application system based on an object-oriented framework.

[0002]

2. Description of the Related Art In order to develop an application system based on an object-oriented framework (hereinafter, referred to as a framework), a developer understands the design decision of the framework and how it is realized. It is necessary to change the objects and methods in the framework so as to match the functional requirements of the target application system after grasping the requirements.

[0003]

However, since the framework has a complicated class structure, is difficult to learn, and takes time, it is not easy to develop an application system based on the framework. There's a problem. This is one of the factors that make it difficult to fully utilize the advantages of the framework or that the introduction of the framework does not progress.

[0004] The present invention has been made in view of the above,
The object is to classify and classify the objects included in the framework, and to associate the viewpoint with the viewpoint for understanding the framework with the objects, thereby enabling a software development method and development capable of smoothly developing an application system based on the framework. It is to provide a system.

[0005]

According to one aspect of the present invention, there is provided a software development method for developing an application system based on an object-oriented framework. Categorize and organize, manage the association with design decisions, and manage the association between the environment and surrounding objects, such as the users of the application system assumed by the framework and related systems, and thereby the frame. The objects included in the work are classified and hierarchized, and the viewpoints for understanding the framework are associated with the objects to make it easier for the developer to understand the framework. Makes it easy to identify And summarized in that further development of the application system based on the work smoothly.

According to a second aspect of the present invention, there is provided a software development system for developing an application system based on an object-oriented framework, wherein objects included in the framework are classified and arranged, and a design decision is made. Means for managing associations, and means for managing associations between objects surrounding the environment, such as users of the application system assumed by the framework and related systems, and objects included in the framework. Classify the objects into hierarchies, link the viewpoints that understand the framework with the objects to make it easier for developers to understand the framework, and narrow down the changes in the framework step by step to identify the changes in the framework Facilitate and framework And summarized in that further development of the application system based on smoothly.

According to the first and second aspects of the present invention, the objects included in the framework are classified and arranged, the correspondence with the design judgment is managed, and the user of the application system assumed by the framework is used. In order to manage the correspondence between the surrounding environment aspects such as and related systems and objects, it is easy for developers to understand the framework, to identify the changed parts of the framework, and to The development of an application system based on this can proceed smoothly.

[0008]

Embodiments of the present invention will be described below with reference to the drawings.

FIG. 1 is a diagram showing a basic configuration of an embodiment of the present invention. In the figure, reference numeral 21 denotes a requirement for a target application system developed based on a framework, and this requirement is an input of the present embodiment. Reference numeral 22 denotes a target application system developed as a result of applying the present invention, which is an output of the present embodiment.

[0010] In order to grasp the framework from the environment surrounding the user such as a user of an application system assuming the framework and related systems, the viewpoint is associated with three viewpoints indicated by reference numerals 11, 12, and 13 in FIG.

(A) Organization: Relationship between companies, functional organizational structure such as organizational hierarchy and roles of people, etc. (b) Process: Vertical classification taking into account business processes and tasks (c) Role: Object Horizontal Classification Considering Roles Viewpoint (a) means the role structure in the real world assumed by the framework, such as the relationship between organizations to which system users belong and the relationship between companies. Ie, company, department, section,
It is a functional organization structure of the real world such as clerk and responsible person. In these functional organizations, there are business rules executed by the organization, data managed by the organization or the responsible person, and the like, and the like. Since the framework includes business logic, data, and the like, these real-world functional organization structures are associated with the framework via system users assumed by the framework.

The viewpoint (b) means a cross-organizational work flow between companies and within a company, and associates these with business processes included in the framework. The viewpoint (c) associates viewpoints such as roles, events, business rules, and subjects with objects included in the framework. Viewpoint (b) represents the exterior of the system from the user's perspective, while
Viewpoint (c) represents the inside of the system from the developer's perspective.

The reason why these three viewpoints correspond to the framework will be described. Originally, the system to be developed is not unrelated to the organizational hierarchy of the company or the role relationships of the people in the real world. The viewpoint (a) relates the functional organization structure in the real world to the business rules and data in the framework. This makes the framework easier to understand.
Viewpoint of the framework from the user's point of view (b)
Can be understood by the user similarly to the viewpoint (a), and the user and the developer can grasp the framework from the same viewpoint, not from the viewpoint of a machine, a network, a programming language, or the like. Therefore, the effect of closing the communication gap between the two can be expected.
In viewpoint (c), by describing the relationships of objects hierarchically, developers can grasp the inside of the framework with concepts such as roles, events, business rules, subjects, etc., so that it is easy to understand and at the same time the changes are specified. Becomes easier.

Next, the viewpoint (c) for classifying objects in FIG. 1 will be described in more detail. The objects included in the framework are large, business-level objects necessary for realizing business, application levels that take into account physical constraints and system elements such as data distribution on the network and communication between servers. And classify them into system-level objects that take into account the implementation environment such as the middleware used and the middleware used. This classification itself is the design viewpoint and judgment itself. That is, as shown by reference numeral 15 in FIG. 1, the objects can be classified into business-level objects, application-level objects, and system-level objects.

The business level objects and the methods included therein are further classified into the following eight types (a) to (h) according to their roles and corresponded. Among them, (a) to (e) are layers having mainly functional meanings, and (f) to (h) are layers having mainly data meanings. This classification of the business level object means the role structure of the object of the viewpoint (c).

(A) A hierarchy representing a workflow in which processes performed by a plurality of persons are grouped together, focusing on a business process. (B) A class in which the roles of persons using the system are grouped together, focusing on the role of a person using the system. (C) Focusing on one process performed by one person, and a hierarchy meaning a class or method that summarizes the flow of a series of work performed in that process. (D) Included in the process Attention is paid to an atomic transaction, and a hierarchy means a class or a method that summarizes steps in the transaction. (E) A hierarchy means a calculation logic which is an operation on data. (F) Basic data and data are accessed. (G) Relationship class that has meaning as a relationship between base classes Meaning hierarchy (h) Hierarchy meaning base classes, relation classes, and derived classes that are also derived from the own class. In addition to these classifications, design decisions in the framework construction process and the emergence thereof Related objects, changed methods, etc.
That is, the design decision, the reason for the decision, the newly added object and method, the changed object and the method are associated with each other. Design decisions include decisions made to make the framework flexible and extensible. In addition, as shown by reference numeral 14 in FIG. 1, design patterns, meta patterns, recipes, and the like are also associated with these.

Next, the basic processing of this embodiment will be described with reference to the flowchart shown in FIG. In the present embodiment, the target application system is finally obtained by narrowing down the changed parts in the framework step by step from the requirements, identifying the changed parts, and customizing the changed parts.

In FIG. 2, first, requirements for the target application system are extracted (step S1). From the requirements for the target application system, a classification is made as to whether the requirement is a requirement that has a business impact or a systemic requirement unrelated to them (step S).
2). For business-impacting requirements, Organi
The difference between the environment surrounding the environment assumed by the framework from the viewpoint of zation and the environment surrounding the target application system is analyzed and determined (step S3). At this time, differences are determined by focusing on the functional role of the organization.

Next, from the viewpoint of Process, differences between processes and tasks implemented by the framework and processes and tasks to be realized by the target application system are analyzed and determined (step S4). In this way, the range affected by the framework is narrowed down in accordance with the procedure of step S3. Then, the following steps are performed within the narrowed range.

That is, from the role point of view, focusing on the role of the object, it is determined which business level object the requirement affects (step S5). At this time, not only the role of the object but also the design judgment that has influenced the class structure of the business object is referred to. This clarifies which object group is affected.

On the other hand, if it is determined in step S2 that the object is classified as a system requirement, the business level object is classified into three types of business level object, application level object, and system level object. Is not affected, it is determined whether the change is a change to an application level object or a change to a system level object with respect to system requirements (step S6), and a design decision corresponding to the change is made. To find related classes. That is, in the case of the change requirement corresponding to the application level object, the influence range is specified from the design judgment of the application level object (step S7), and in the case of the change request for the system level object, The influence range is specified based on the design judgment (step S8).

Next, in step S9, the framework is customized by deciding how to make changes based on the design patterns and meta-patterns associated with the found classes, a cookbook in which recipes are collected, and the like. Then, the above processing is repeated for all the requirements (step S10), and a target application system can be obtained (step S11).

As described above, according to the present invention, the framework can be easily understood, and the changed portion can be easily specified. That is, a new class (object) appears or a method is affected as the framework is sequentially refined in the construction process. From the experience of constructing a framework, the final framework requires physical objects such as objects necessary for realizing business (business-level objects), distribution of data over a network, and communication between servers. And various objects such as an object (application-level object) that considers system elements and an object (system-level object) that considers an implementation environment such as middleware to be used. For this reason, the framework itself can be easily understood by means of classifying the objects into classes and correlating them with design decisions. In addition, when using the framework, it is necessary to understand business, understand the structure and relationship of business level objects that realize the business, and understand the design viewpoint and judgment, but the application assumed by the framework The means of associating objects with surrounding environmental aspects such as system users and related systems makes it possible to grasp from the surrounding environmental aspects surrounding the framework, and on which business-level objects are referenced, the framework becomes more It will be easier to understand.

When an application system is constructed on the basis of a framework by means for managing the classification of objects and the association with the judgment on setting, and the means for managing the association with surrounding environmental aspects. In addition, it is possible to take measures to determine which part of the framework the requirement affects, and it is easy to specify a changed portion.

As described above, the advantage that the framework can be easily understood and the changed portion can be easily specified. As a result, the changed portion of the framework can be easily specified, and the application system can be developed based on the framework. Can proceed smoothly.

[0026]

As described above, according to the present invention,
Classify and organize the objects included in the framework,
It manages the association with design decisions and manages the association between the environment and surrounding objects, such as the users of the application system assumed by the framework and related systems, so that the framework can be easily understood. In addition, it is possible to easily identify a changed portion of the framework, and to smoothly develop an application system based on the framework.

[Brief description of the drawings]

FIG. 1 is a diagram showing a basic configuration of an embodiment of the present invention.

FIG. 2 is a flowchart showing the operation of the embodiment shown in FIG.

[Explanation of symbols]

 11 Organization: Functional organization structure in the real world 12 Process: Cross-organizational process 13 Role: Role structure of objects 14 Design decision 15 Design pattern, meta pattern, recipe 21 Requirements 22 Application system

Claims (2)

[Claims] 1. A software development method for developing an application system based on an object-oriented framework, comprising: classifying and organizing objects included in the framework; managing correspondence with design decisions; It manages the correspondence between the environment surrounding objects, such as the assumed user of the application system and related systems, and the objects, thereby classifying the objects included in the framework into a hierarchy and associating the objects with the viewpoints that understand the framework. To make it easier for developers to understand the framework, and to narrow down the changes in the framework step by step, to easily identify the changes in the framework,
A software development method characterized by facilitating the development of an application system based on a framework. 2. A software development system for developing an application system based on an object-oriented framework, comprising: means for classifying and organizing objects included in the framework and managing correspondence with design decisions; Means for managing the correspondence between objects surrounding the environment, such as users of the application system assumed by the work and related systems, thereby classifying and hierarchizing the objects included in the framework, Associate the viewpoint with the object to be understood with the object to make it easier for the developer to understand the framework. Application system A software development system that facilitates system development.