曝光臺 注意防騙 網曝天貓店富美金盛家居專營店坑蒙拐騙欺詐消費者

decision. The change management was a central and global consideration :
• Data conversion
• A single platform for un-structured and structured documents
• New processes
• New tool : XML under S1000D authoring and management
• New means of dissemination
So the open source based solution became the best option and we will explain why it remains the best for any
army in the world. Armies are transitioning to a new management model that affects all their means including
the documentation. We’ll explore this in our presentation.
Title: Requirements Engineering supports Life Cycle Management
Authors: M. Mäuseler
GfU Gesellschaft für Unternehmenslogistik mbH
Time: November 3, 2009 5:00 pm
Room: Lumen
Various functions of a company use product data during the life cycle. First, the product will be invented or
developed. Partially, complete systems or parts will be subcontracted. Suppliers must be selected and deliverables
must be tested and integrated. After the entry into service components will be changed, redesigned,
varied or used for new developments. Product manager has to monitor the impact of changes in all phases of
the life cycle. The higher the complexity of the product the higher the effort he has to spend to fulfill this task.
Forgotten requirements from connected processes, functions or products cost more money the later they will be
identified. Requirements Engineering (RE) is the method to save costs by identifying these impacts immediately
in all phases of the life cycle.
Prerequisite is the capturing of all requirements as objects with an unique identifier and additional information from
the beginning. The benefits are manifold. First all requirements will be identified quicker than reading a continuous
text. Beside this the clearness of the specification will increase. Further on each requirement could be addressed in
communication precisly with e.g. stakeholders for requirement validation, potential suppliers or test departements.
18
The exceeding of a certain amount of requirements in a single collection is attended by a loss of its clearness.
Requirements should be allocated into several subcollections. A cascade of collections arise. Each collection
remains manageable. To keep the overview links will be established between the collections on requirement
level. If one requirement changes all linked requirements will be identified automatically. It could be checked
easily, if these requirements are impacted of the change.
Capturing requirements in a solution neutral way has various advantages over the life cycle. The solution isn’t
fixed; every feasible solution could be checked. Beyond that potential suppliers could offer new approaches,
technologies, processes that were unknown yet. In the case of asking for fixed solutions, innovations will be
blocked.
Another advantage of the solution neutral capturing is the high rate of reuse of requirements. Products of one
family varies in several dimensions and parameters. But by checking the differences in detail, commonly up to
90% are the same. Best for specifications, that are solution neutral. The authors needn’t start from scratch, but
could start from 90 %, which implies enormous time and cost savings.
But what about the rest of 10% difference between both products? If all requirements were linked even these
requirements at all levels could be identified instantly. The consequences of changes will be displayed and
remain manageable. The exact amount of requirements will be checked against the changes. No dissipation of
ressources is the consequence.
Linking of requirements is the key for high reaction time on changing markets. Market requirements will be followed
through the collection cascade down to part level. All related risks and opportunities could be identified
instantly. Even in the case of fluctuation of employees the product knowledge is implemented in the specification.
If every requirement has additional information brain drain has less impacts.
Finally the optimum can be reached, if the product manager looks beyond RE and integrates other useful methods
in the life cycle management as functional analysis, target costing or logstics-orientated product development.
Title: Model for Eddy Current testing of CFRPs
Authors: M. Cacciola, A. Gasparics, G. Megal, D. Pellicanò, F.C. Morabito
Time: November 3, 2009 5:20 pm
Room: Lumen
In order to improve manufacturing quality and ensure public safety, components and structures are commonly
inspected for early detection of defects or faults which may reduce their structural integrity. Non Destructive
Testing (NDT) techniques present the advantage of leaving the specimens undamaged after inspection. Within
　
中國航空網 m.k6050.com
航空翻譯 www.aviation.cn
本文鏈接地址：航空資料1(43)