Use Case Template) Clause Samples
Use Case Template). In MIDIH project (and as well in this document) the Use Case represents the rationale behind the industrial experiment/s to occur. Industrial Experiments (IE) Definition According to the scientific world, the experiment is an empirical procedure to compare competing models or hypotheses and also to test existing theories or new hypotheses to support or disprove them (▇▇▇▇▇▇▇▇ & Brosing 2001). Hypotheses are the expectation about how a particular entity (process, system or phenomenon) works. However, experiments can be conducted with the final aim to answer a "What-if" question, without a specific expectation about the experiment outcome. Experiments provide insight into cause - effect relations among different part or variables describing the entity under study by demonstrating what outcome occurs when a particular factor is manipulated. Experiments deliver demonstrators and need to show a substantial measurable strategic and/or economic impact. More specifically, in engineering disciplines experiments are the primary component of the scientific method. They are used to test how physical processes or systems work under particular conditions. IEs’ focus on processes is one of their main characterizing elements. Experimentations are generally performed to increase knowledge of a particular machine/process/system and to adjust the settings/components of a machine/process/system in a systematic manner and to learn which factors have the greatest impact on the resultant outcome, which modifications are needed and how the modification work in a field/laboratory/virtual environment (▇▇▇▇▇▇ 1999). Specifically, the goal of IE is to identify the optimum settings for the different factors that affect the machine/process/system. In that light, in MIDIH project (and as well in this document) it is referred to IE as the deployment of the developed system/solution intended to the digitalization of specific manufacturing processes/activities/value chains in a field/laboratory/virtual environment to arise business performances of the involved manufacturing enterprises and, in a broader meaning, of manufacturing industry. Scenario analysis and requirements elicitation Use Case description An overall picture of the Use Case must be provided in this section where the use case must be named and described. The Use Case partner’s (the company that wants to go through a process of digitalization of its processes/system/value chain) name must be recorded as the name of the manufa...
Use Case Template). The use case template that is used in Europeana Inside was constructed from three different sources: • A use case template provided by the project partner Knowledge Integration (K-INT), who uses this template to build and base their software solutions on; • The template used within the ECLAP2 project to specify user requirements for the online portal; • The INK management model3. Although this model is not a use case model as such, it provides a useful context to use case modelling for the exchange of digital information. All three were merged together in order to create a use case template that would fit the needs and purpose of describing use case scenarios for Europeana Inside. The resulting structure for the use case template is as follows: <the use case number + a short statement which indicates the core goal of the use case> <brief description of what the user’s goal is with this specific use case> <overview of which of the target user(s) will execute the use case> <which software systems and/or tools need to be used; e.g. CMS, ▇▇▇> <a summary of the flow of events, which describes the essentials of the use case> 2 ECLAP: E-Library for performing Arts <▇▇▇▇://▇▇▇.▇▇▇▇▇.▇▇/drupal/?q=node/3609> 3 INK Management Model <▇▇▇▇://▇▇▇.▇▇▇.▇▇/nl/p4bd81e110a03e/ink-managementmodel.html> <definition of the technical conditions (CMS, data conditions) which have to be present for the use case to be fully executed> <basic flow of events: the numbered steps which make up the entire use case from beginning to end; plus an indication of the responsible actors involved> <description of the changes that will have occurred in the system when the use case is fully completed: ‘system’ can also refer to the content provider situation or data condition> <issues that need to be taken into account when developing the use case> To ensure this deliverable constitutes a usable, legible and understandable use case overview, some simplification of the use case scenario templates was unavoidable. For example, D2.1 has pointed out a number of differences or even contradictions in user requirements related to different workflow steps. Within the use case templates, it is impossible to reflect all contradictions in detail. However, it is unavoidable that some of these contradictory views will have to be discussed again at the time when final decisions will have to be made in the project in light of the functional requirements and technical specifications. For reasons of readability it...