Glossary entry (derived from question below)
English term or phrase:
framework documentation
Lithuanian translation:
(tiekėjo parinkimo proceso) sąlygų dokumentacija
Added to glossary by
Gintautas Kaminskas
Jul 17, 2011 12:36
13 yrs ago
English term
framework documentation
English to Lithuanian
Law/Patents
Law: Contract(s)
services agreement, scope of services
What does "framework documentation" mean in Lihuanian in the following context:
A description and recommendation as to the most appropriate supplier selection process, including framework documentation and negotiation strategy.
My translation is, except for "framework documentation":
Tinkamiausio tiekėjo parinkimo proceso aprašymas bei rekomendacija, įskaitant "framework documentation" ir derybų strategiją
Thank you very much in advance.
A description and recommendation as to the most appropriate supplier selection process, including framework documentation and negotiation strategy.
My translation is, except for "framework documentation":
Tinkamiausio tiekėjo parinkimo proceso aprašymas bei rekomendacija, įskaitant "framework documentation" ir derybų strategiją
Thank you very much in advance.
Proposed translations
(Lithuanian)
3 | (tiekėjo parinkimo proceso) sąlygų dokumentacija |
Gintautas Kaminskas
![]() |
3 | sistemą dokumentus |
VEIKMANE DAIGA
![]() |
Change log
Aug 13, 2011 07:08: Gintautas Kaminskas Created KOG entry
Proposed translations
15 mins
English term (edited):
(supplier selection process) framework documentation
Selected
(tiekėjo parinkimo proceso) sąlygų dokumentacija
Here the "framework documentation" refers to the supplier selection process just mentioned. Therefore it is documentation pertaining to the "framework", i.e. the conditions, for supplier selection.
A description and recommendation as to the most appropriate supplier selection process, including framework documentation and negotiation strategy. = Tinkamiausio tiekėjo parinkimo proceso aprašymas bei rekomendacija, įskaitant ir tiekėjo parinkimo proceso sąlygų dokumentaciją bei derybų strategiją.
A description and recommendation as to the most appropriate supplier selection process, including framework documentation and negotiation strategy. = Tinkamiausio tiekėjo parinkimo proceso aprašymas bei rekomendacija, įskaitant ir tiekėjo parinkimo proceso sąlygų dokumentaciją bei derybų strategiją.
2 KudoZ points awarded for this answer.
16 mins
sistemą dokumentus
From a development point of view, a framework has to be general enough to be useful, but it has to be precise enough to be programmable and to have reasonable performance. From a reuse point of view, we have to document frameworks succinctly, unambiguously, and understandably. The components of the framework should be searchable. In the process of documentation, there are issues related to representing the existing frameworks, their inter-object behaviors, their usages, scalability, extensibility, and searchability [6].
Accurate and comprehensible documentation is crucial to the success of large-scale frameworks. Documenting frameworks must describe the purpose of the framework, how to use the framework, and the detailed design of the framework. The design of the framework fixes certain roles and responsibilities amongst the classes, as well as standard protocols for their collaboration. The variability within the family of applications is factored into hot spots. The framework provides simple mechanisms to customize each hot spot. The documentation should document both general and specific functionalities.
Documenting frameworks is a costly activity and contemporary tools often focus on low-level method-oriented documentation, which fails to capture the strategic roles and collaborations among framework components. With the advent of tools for reverse-engineering the structure of classes and objects in complex frameworks, accuracy and utility of framework documentation will be improved. An increase in the current trend of using design patterns will provide higher-level descriptions of frameworks.
Generally, traditional framework documentation just provides static views of a framework. The static views are very important to understand the basic structures and general functionalities of the frameworks, but it is not enough to represent the whole framework. The run-time architecture of a framework is characterized by an inversion of control. Sometimes, documenting the dynamic side of a framework is more important for framework reuse. Each framework has control flow among the various methods of the framework's classes. Documenting framework behaviors is very critical for application developers to understand the whole structure of the framework. Documenting dynamic views of a framework is more difficult than documenting static views, and it requires more advanced techniques.
Accurate and comprehensible documentation is crucial to the success of large-scale frameworks. Documenting frameworks must describe the purpose of the framework, how to use the framework, and the detailed design of the framework. The design of the framework fixes certain roles and responsibilities amongst the classes, as well as standard protocols for their collaboration. The variability within the family of applications is factored into hot spots. The framework provides simple mechanisms to customize each hot spot. The documentation should document both general and specific functionalities.
Documenting frameworks is a costly activity and contemporary tools often focus on low-level method-oriented documentation, which fails to capture the strategic roles and collaborations among framework components. With the advent of tools for reverse-engineering the structure of classes and objects in complex frameworks, accuracy and utility of framework documentation will be improved. An increase in the current trend of using design patterns will provide higher-level descriptions of frameworks.
Generally, traditional framework documentation just provides static views of a framework. The static views are very important to understand the basic structures and general functionalities of the frameworks, but it is not enough to represent the whole framework. The run-time architecture of a framework is characterized by an inversion of control. Sometimes, documenting the dynamic side of a framework is more important for framework reuse. Each framework has control flow among the various methods of the framework's classes. Documenting framework behaviors is very critical for application developers to understand the whole structure of the framework. Documenting dynamic views of a framework is more difficult than documenting static views, and it requires more advanced techniques.
Reference:
Something went wrong...