THE METHODOLOGY Sample Clauses

THE METHODOLOGY. The principles set out in the Methodology Guidance Notes prepared by the Government Digital Services should be adhered to. SCHEDULE 5 - CUSTOMER RESPONSIBILITIES The Customer shall ensure that representatives from strategy, policy, risk and case working are available during the Inception period to prioritise deliverables and requirements.

THE METHODOLOGY. The project will incorporate Agile methodology and adhere to guidance set out by Government Digital Services. Delivery across Lots 1 and 2 will be seamless, Lot 3 has been omitted. The timetable for delivery is compact with short 2 week cycles “timeboxes” for Alpha, Beta and Live phase as illustrated in the revised plan, below. A minimum viable product should be available by early February to enable other elements of the ERW project (linked dependencies) to be fulfilled before 31 March 2015. The CEH project team will establish two groups (Technical and End User Focus Groups) to facilitate links with Jasmin and product development. Owing to the distributed involvement from representatives across the NERC centres and HEI’s, early notice (minimum 3 weeks) is required to convene workshops or meetings of the Technical or End User Focus Groups. NERC's science remit covers terrestrial, marine, freshwater, science-based archaeology, atmospheric and polar sciences, and Earth observation. Establishing meaningful “user stories” from the Focus Group will be key to providing a system that has credibility across the different science areas, The primary audience will incorporate science disciplines of climate, hydrology, geology, ecology, oceanography. Initial uptake is anticipated to be low and likely spurred from those participating in the User Group (approximately 35 people). A key feature of success is that the ERW attracts interest from the NERC community and achieves a broad user base; as such the solution should be scalable and “capable of supporting a growing ecosystem of services”. Product evaluation will be two-fold with frequent review by CEH project Team and Project Board members between timeboxes and involvement of the wider End User Focus Groups between phases. Contact with members of the Focus Groups should be via CEH in the first instance. SCHEDULE 5 - CUSTOMER RESPONSIBILITIES  SCISYS has assumed that all environments are provided by JASMIN (development, test, staging, live) including all infrastructure and resource management and are remotely accessible by SCISYS. It is the responsibility of SCISYS to provision and configure these environments from the available ERWB quota of resources.  The JASMIN Cloud service will expose an orchestration service enabling the start, stop, suspend, resume, snapshot and monitoring of deployed ERW model library service.  The JASMIN Cloud service will allow command line interface access for super-users.  The departmen...

THE METHODOLOGY. The SEESCOA modelling methodology offers the fol- lowing concepts to construct an embedded application: components, ports, port specifications, connectors and port contracts. The CCOM [1] development tool offers full-fledged support for these concepts in order to en- xxxxx the development process. The following overview describes the concepts: components: are the entities composing the applica- tion. There are component blueprints, which are the design-time entities and there are component instances. The latter are instantiated at run-time and perform a certain subtask of the application. Components are isolated from each other, and their only way to communicate is via their port in- tances. Thanks to these properties, they are highly reusable.

THE METHODOLOGY. The method we propose to generate the WRSPM-based model consists in taking the customer requirements (expressed in natural language) one by one. This way we incrementally produce the specification S in terms of phenomena, invariants and operations. We break requirements into W, R, and establish traceability relating the labels of the atomic requirements with the labels of the invariants and operations manually (in the future, with the development of tools, this should be done automat- ically). In Figure 7.1 we have a flowchart illustrating the process step-by-step. We take each requirement (already decomposed into an atomic requirement) and firstly iden- tify all the phenomena. Then, for each phenomena that has been identified for the first time we define first invariants regarding to its type and next the invariants and operations relevant to its state. Once all phenomena of that single requirement are identified and (the new ones) typed and invariant/operation related, we break the 7 Formal Methods as an Improvement Tool 109

THE METHODOLOGY