• Managing complexity of the product in making it accessible to each team, then to each individual in the team. This leads to break down the product into certain “concurrent engineering products” or business objects, which represent design domains (geometrical, functional), and which enable to maximize the work in parallel.
• Synchronization, to ensure that the resulting development cycle is under control.
• Control of interfaces of the different design domains.
• Multidisciplinary engineering.
• “Break the walls”, especially by developing collaborative techniques throughout the extended enterprise.
• Permanent traceability of product configuration information.
• Think process, then method and then tool.
This process based paradigm implies:
1. to really consider how design teams actually cooperate in design context, what business objects they use, how they share them, how these objects evolve as design evolves or when change occurs.
2. to think as much as possible in terms of process integration, to streamline the overall workflow, and to maximize process quality.