# US 2001/0025236 A1 · Method for developing complex systems

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2001/0025236 A1
- Document ID: US20010025236A1
- Status: Published application
- Kind: A1
- Application number: 09/801,602
- Filed: 2001-03-08
- Published: 2001-09-27
- Earliest claimed: 2000-03-09
- Assignees: Koninklijke Philips Electronics N.V.
- Inventors: Petrus Hubertus Maria America
- Web page: https://patentgrep.com/patent/US20010025236A1

## CPC

- G06F 8/20: Software design
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

A method is proposed for developing a family of complex systems having a common software architecture platform. The method comprises set up of a functional requirements specification (FRS) which includes use cases that describes interaction of users with said complex systems in terms of abstract concept and set up of a requirements object model which explains the abstract concepts in terms of a structured vocabulary The use cases are developed hand-in-hand with the requirements object model. The FRS specifies the interaction of the complex systems with their users. Notably, the FRS specifies the activities which are performed in the interaction of the complex systems with their users, i.e. ‘what’ the complex systems do. This is preferably done in terms of the use cases which are usually written in a natural language such as English. The requirements object model specifies the concepts to which the activities specified in the FRS relate. The FRS may be divided into several chapters. Preferably, the requirements object model is written in an object modeling language such as UML.

## Claims

### Claim 1

A method for developing a family of complex systems having a common software architecture platform, the method comprising
set up of a functional requirements specification which includes use cases that describes interaction of users with said complex systems in terms of abstract concepts
set up of a requirements object model which explains the abstract concepts in terms of a structured vocabulary
wherein
the use cases are developed hand-in-hand with the requirements object model.

### Claim 2 (depends on 1)

A method as claimed in claim 1, wherein
the functional requirements specification includes one or more chapters and one or more FRS authoring teams are established for separate chapters
a single object model control team control internal consistency of the requirement object model
one or more overlapping modeling teams are formed where each modeling team includes members of the object model control team together with one or more members of respective FRS authoring teams,
which overlapping modeling teams for their chapters construct use cases and provide respective portions of the structured vocabulary.

### Claim 3 (depends on 1)

A method as claimed in claim 1, wherein differences between members of the family are expressed in the requirements object model, notably using one or more of the following mechanisms:
Different members of the family using different subclasses of a generalised class,
Different members of the family using different multiplicities in relationships between classes,
Different members of the family using different values for an attribute of a class.

### Claim 4 (depends on 2)

A method as claimed in claim 2, wherein
in at least one of the modeling teams an initial model is constructed and
the FRS authoring of the use cases is performed on the basis of the initial model and
fine tuning of the use cases is performed by the object model control team.

### Claim 5 (depends on 2)

A method as claimed in claim 2, wherein
FRS authoring of the use cases of several chapters is carried out in parallel by the respective FRS authoring teams.

### Claim 6 (depends on 1)

A method as claimed in claim 1, wherein the complex systems are medical diagnostic imaging systems, notably, diagnostic x-ray examination systems.

### Claim 7

A family of complex systems, notably a family of medical imaging systems,
separate complex systems supporting respective, different subsets of use cases.

### Claim 8 (depends on 1)

A method as claimed in claim 1 a, where the precise behaviour of one or more use cases differs among members of the family according to variations expressed in the object model, notably by different subclasses of a general class, by different multiplicities of relationships, or by different values of attributes.
