Key Performance Indicators for the Nato Centres of Excellence

Abstract The NATO Centres of Excellence (COEs), entities involved in various fields of transformation in support of the Alliance, are subject of different levels of accreditation performed by NATO. An important aspect of such recognition comes with the NATO institutional accreditation for Quality Assurance (QA) in the case of the COEs involved in education and training delivery (alongside other NATO, National and Partner Education and Training Centres). The NATO QA seal is the trustworthy mark that a COE fulfils the expected quality requirements (based on a solid Quality Management System) in the educational process, and provides deliverables "fit for purpose" as solutions for the NATO education and training requirements. While the individual strategies of the COEs are pretty much different in this endeavour, we would outline the commonality of the standards they rely on. This paper focuses on institutional performance measurement as reference in the Quality Management System, trying to identify benchmarks for Key Performance Indicators (KPIs) based on the current experience at the COEs level - extended to the wider NATO Transformation Network - and shared best practice. DISCLAIMER: This paper expresses the views, interpretations, and independent position of the authors. It should not be regarded as an official document, nor expressing formal opinions or policies, of NATO or the HUMINT Centre of Excellence (HCOE

Creating a methodology and tool to capture and resolve conflicts in developing software requirements: Requirement Lifecycle Modeling Views manager (RLMV)

Due to the character of the original source materials and the nature of batch digitization, quality control issues may be present in this document. Please report any quality issues you encounter to [email protected], referencing the URI of the item.Includes bibliographical references (leaf 18).Requirements management has been a traditionally overlooked aspect in designing software based systems. This lack of emphasis on managing requirements has lead to a large percent of projects either failing to meet all the needs of the customer, or in extreme cases, being cancelled when budgets or schedules have been exceeded. Companies could potentially save time and money by ensuring that requirements are accurately represented in each phase of development. The purpose of my research is to design a tool that will aid in tracing requirements throughout the software development lifecycle. The tool, named Requirement Lifecycle Modeling Views (RLMV), follows the architecture, as defined in The Unified Modeling Language Users Guide, for modeling software-intensive systems. This architecture is based on five views which are the use case view, design view, process view, implementation view, and deployment view. These views work together to define the modeling of a system by representing different aspects of the system, as it is developed. RLMV works with existing software tools created by a corporation named Rational. The tool itself is implemented using Java and Oracle. RLMV is designed to trace pre-defined requirements to modeling diagrams created for each of the five views. Though the tool was designed to work with Rational RequisitePro and Rational Rose, it is generalized enough to work with most software designing tools. In this manner, a user can select a requirement and display the names of diagrams and files, for each phase of development, associated with that requirement. The benefit to RLMV is that a user can actively trace the requirement through development to ensure that each requirement is being satisfied and prevent deviations

Regulation of providers on the Early Years Register : consultation document

"This is a consultation document on proposals for a revised framework for the regulation of registered early years provision. Ofsted seeks the widest possible range of views from those who have an interest in, or expertise relating to, registered early years provision to ensure that the regulatory framework takes proper account of the needs and circumstances of all interested parties. Above all, the framework must assure the quality of services for all children in registered early years provision and promote their continuing improvement. The closing date for the consultation is 6 April 2012" -- front cover