This part of ISO/IEC/IEEE 24748 -- specifies the Technical Management processes from ISO/IEC/IEEE 15288 that are required to be implemented for planning a systems engineering project; gives guidelines for applying the required processes; specifies a required information item, a plan for the technical management and execution of the project that is to be produced through the implementation of the Project Planning process; gives guidelines for the format and content of the required information… read more item, and; provides normative definition of the content of the information item that results from the application of these processes to that end. In this part of ISO/IEC/IEEE 24748 that plan for technical project management is termed the Systems Engineering Management Plan (SEMP). This part of ISO/IEC/IEEE 24748 is applicable to those who use or plan to use ISO/IEC/IEEE 15288 on projects dealing with man-made systems including software-intensive systems, software products, and services related to those systems and products; those who are responsible for the technical management of projects concerned with the engineering of systems; those responsible for executing ISO/IEC/IEEE 15288 system life cycle processes at a project level; organizations and individuals who are subcontracting a project management effort; anyone developing engineering management documentation to complete technical planning aspects of their project's processes. In many organizations, the various responsibilities of technical management are assigned to more than one person. Where the term "technical manager" or "systems engineering manager" is used in this part of ISO/IEC/IEEE 24748, the guidance, advice or normative requirement applies to the applicable role within the project or organization. This part of ISO/IEC/IEEE 24748 is intended to provide guidance for two-party situations and may be equally applied where the two parties are from the same organization. This part of ISO/IEC/IEEE 24748 can also be used by a single party as self-imposed tasks. This part of ISO/IEC/IEEE 24748 can also serve as guidance in multi-party situations, where high risks are inherent in the supply and integration of complex systems, and procurement can involve several suppliers, organizations or parties. read less
This part of ISO/IEC/IEEE 29119 defines an efficient and consistent solution for Keyword-Driven Testing by: - giving an introduction to keyword-driven testing; - providing a reference approach to implement keyword-driven testing; - defining requirements on frameworks for keyword-driven testing to enable test engineers to share their work items, such as test cases, test data, keywords, or complete test specifications; - defining minimum requirements for tools, which are necessary to fully… read more utilize keyword-driven testing. These requirements could apply to any tools which support the keyword-driven approach (e.g. test automation, test design and test management tools); - defining interfaces and a common data exchange format to ensure that tools from different vendors can exchange their data (e.g. test cases, test data and test results); - defining levels of hierarchical keywords, and giving advice when to use hierarchical keywords, when to use "flat" structured keywords, and describe specific types of keywords (e.g. keywords for navigation or for checking something); - providing an initial list of suggested generic technical (low level) keywords, such as "inputData" or "checkValue". These keywords can be used to specify test cases on a technical level, and may be composed to create business level keywords as required. This standard is applicable for all those who want to create keyword-driven test specifications, create corresponding frameworks, or build test automation based on keywords. read less
Link Aggregation provides protocols, procedures, and managed objects that allow the following: One or more parallel instances of full-duplex point-to-point links to be aggregated together to form a Link Aggregation Group (LAG), such that a MAC Client can treat the LAG as if it were a single link.; A resilient interconnect using multiple full-duplex point-to-point links among one to three nodes in a network and one to three nodes in anotherre, separately administered, network, along with a means… read more to ensure that frames belonging to any given service will use the same physical path in both directions between the two networks. This standard defines the MAC-independent Link Aggregation capability and general information relevant to specific MAC types that support Link Aggregation. The capabilities defined are compatible with previous versions of this standard. read less