Spelling suggestions: "subject:"canprocess description"" "subject:"3.3vprocess description""
1 |
Bakom Ladan : En skiss eller två på en hälsoträdgård på Wij Trädgårdararvidsson, emma January 2014 (has links)
Abstract The research in the interdisciplinary field of natural-human-health-design has in recent decades gainedmomentum and led to new or new-old ways of thinking and acting in terms of planning and design of outdoorenvironments with the aim of health promotion. Concrete concept models and design guides have begun toemerge as a result of this research.The purpose of this work is to use these guides to develop a design proposal for a supposed health garden,with Wij Trädgårdar in Ockelbo as a base. This has been done in the form of a process description. The targetgroup for the design proposal is long-term unemployed and people who have come to Sweden as refugees.Since the specific design recommendations could not be found for the selected target group, the main materialwas general guidelines for health gardens in combination with guidelines for health gardens directed to targetgroups with stress-related problems, which is a broad target group for which there are relatively much currentresearch.The result is a process description of the progression towards a sketch on a health garden, designed for aspecific spot on Wij Trädgårdar, but available for use in other locations, provided adjustments is made to thespecific location. The sketch is supplemented with plant suggestions to different parts of the garden. A sketchof an alternative proposal is included as a smaller, faster and cheaper version of the main design proposal. / Sammanfattning Forskningen inom det tvärvetenskapliga området natur-människa-hälsa-design har under de senastedecennierna tagit fart och lett fram till nya, eller ny-gamla, sätt att tänka och handla när det gäller planeringoch utformning av utomhusmiljöer i hälsofrämjande syfte. Konkreta konceptmodeller och design-guider harbörjat dyka upp som resultat av forskningen.Syftet med det här arbetet är att använda sådana guider för att ta fram ett designförslag till en tänkthälsoträdgård, med Wij Trädgårdar i Ockelbo som utgångsplats. Detta har gjorts i form av enprocessbeskrivning. Målgruppen för designförslaget är långtidsarbetslösa och människor som har kommit tillSverige som flyktingar. Eftersom specifika designrekommendationer inte kunnat hittas för den valdamålgruppen har utgångsmaterialet varit allmänna riktlinjer för hälsoträdgårdar i kombination med riktlinjer förhälsoträdgårdar för målgrupper med stressrelaterad problematik, vilken är en bred målgrupp som det finnsrelativt mycket aktuell forskning för.Resultatet är en processbeskrivning av vägen fram till en skiss på en hälsoträdgård, framtagen för en specifikplats på Wij Trädgårdar, men möjlig att använda på andra platser, förutsatt att anpassning görs till aktuell plats.Skissen kompletteras med förslag på växter till olika delar av trädgården. En skiss på ett alternativt förslag finnsmed som en mindre, snabbare och billigare variant till det huvudsakliga designförslaget.
|
2 |
Návrh technologie výroby zvolené součásti a aplikace navržených změn do výrobního procesu / Technology Design of a Selected Part and Application of the Designed Changes in the Manufacturing ProcessTurčín, Jiří January 2017 (has links)
This master thesis deals with a design of technological process description for a mechanical engineering part called „pressure plate“. The component is analyzed in regards to its mechanical engineering design and used material. Some brief theoretical prerequisites for an effective solution of the problem are summarized in the paper. A detailed research of current technological methods is provided, together with an analysis of the State-of-the-Art in manufacturing, introduction of technological possibilities of the company and a timeline records of the manufacturing process. In regards to the current methods and technologies, changes to the technological process are applied. Among these changes is a unification of machinery used in the process. This leads to an innovation of the methodology and the ways to clamp the component. Other applied alternations focus on a stabilization of the drilling process, which is reached by a choice of new tools and adjustment of cutting parameters. Furthermore, a variable coding of tools in case of automatic tool change is designed. This paper then provides two possible solutions based on proposed changes and alternations. These solutions, together with the tools mentioned, are subjects to a techno-economical assessment.
|
3 |
RGML: A Specification Language that Supports the Characterization of Requirements Generation ProcessesSidky, Ahmed Samy 27 August 2003 (has links)
Despite advancements in requirements generation models, methods and tools, low quality requirements are still being produced. One potential avenue for addressing this problem is to provide the requirements engineer with an interactive environment that leads (or guides) him/her through a structured set of integrated activities that foster "good" quality requirements. While that is our ultimate goal, a necessary first step in developing such an environment is to create a formal specification mechanism for characterizing the structure, process flow and activities inherent to the requirements generation process. In turn, such specifications can serve as a basis for developing an interactive environment supporting requirements engineering.
Reflecting the above need, we have developed a markup language, the Requirements Generation Markup Language (RGML), which can be used to characterize a requirements generation process. The RGML can describe process structure, flow of control, and individual activities. Within activities, the RGML supports the characterization of application instantiation, the use of templates and the production of artifacts. The RGML can also describe temporal control within a process as well as conditional expressions that control if and when various activity scenarios will be executed. The language is expressively powerful, yet flexible in its characterization capabilities, and thereby, provides the capability to describe a wide spectrum of different requirements generation processes. / Master of Science
|
4 |
En processbeskrivning för utveckling av webbaserade system och gränssnitt : En fallstudie av utvecklingsprocesser på GMP-Systems AB / A process-description for development of web-based systems and interface : A case study of development processes at GMP-Systems ABIbrahim, Goran, Ek, Leonard January 2017 (has links)
Affärssystem som inte har tydliga användargränssnitt tenderar att göra användarvänligheten sämre, vilket i sin tur kan leda till att delar av systemet inte nyttjas effektivt. Det kan därför vara lämpligt att ha en specifik och tydlig processbeskrivning för utveckling av system med hänsyn till användarvänlighet. I detta projekt undersöktes möjligheten att ta fram en processbeskrivning för IT-projekt vid framtagning av ett nytt gränssnitt i ett system. Mer konkret så är frågan som ska besvaras i denna rapport följande: ”Hur ska en utvecklingsmetod eller utvecklingsprocess för IT-system se ut för att tillvarata vetenskapliga, teoretiska och tekniska aspekter på Människa-Dator Interaktion (MDI)?” En fallstudie i detta projekt har utförts på företaget GMP-Systems AB. För att komma fram till ett resultat, och för att få svar på frågeställningen, så har en litteraturstudie på aspekter inom MDI utförts. Dessutom har en analys huruvida teknisk implementation av detta kan åstadkommas med hjälp av ramverk. Vidare har intervjuer genomförts, samt tester där användaren har fått interagera med systemet. Resultatet av feedbacken har sedan analyserats. Detta för att senare kunna bygga prototyper till systemet. I resultatdelen levereras en utvecklingsmetod och en processbeskrivning som är kopplad till den litteraturstudie och de erfarenheter som erhållits från projektets fallstudie. Till företaget GMP-Systems levereras en prototyp, en use-case model[1] med user-stories[2] samt ett sekvensdiagram[3]. [1] Use-Case Model är en beskrivning på åtgärder och handlingar som en användare kan utföra, och definierar interaktionen mellan rollerna i ett system för att utföra ett mål.[2] User-stories är ett verktyg inom systemutveckling för att kunna ta fram en beskrivning av önskad funktionalitet som ofta utgår utifrån ett användarperspektiv.[3] Ett sekvensdiagram visar metodanrop mellan objekt i en tidsbegränsad situation och vilken ordning. / Business systems lacking a clear interface and subsequently a diminished usability, can lead to limited usage or no usage of parts of the system. It may therefore be critical to have a process outlined for the development of such system and its interface to ensure that all parts of the system are used. The objective of this case study was to investigate whether it is possible to develop a process description for IT projects at the initial stages of the development phase of a new interface in a system. More specifically, the question investigated in this report follows: “How should a development method or development process for IT systems look to seize scientific, theoretical and technical aspects of Human Computer Interaction (HCI)?” A case study of the project was carried out at the company GMP-Systems AB. A literature-study on aspects of Human-Computer Interaction (HCI) was carried out to arrive at a result and answer the question. Further, an analysis was conducted to consider whether the technical implementation of such process can be accomplished by adopting frameworks. In addition, interviews were conducted with users that have interacted with the system, and an analysis was carried out on the feedback provided to develop prototypes for the system. A development method and process description linked to the literature and the experience gained from the projects case study is outlined in the result section. To the client, GMP-Systems, a prototype, a use-case model[1] with user-stories[2] and a sequential diagram[3] will be delivered. Keywords: HCI, evaluation method, Angular JS, Knockout JS, React, Moqups, process description, development method. [1] Use-Case model is a description of actions that a user can perform and defines the interaction between the roles of a system to accomplish a goal[2] User stories are a tool in system development to provide a description of the desired functionality, often from an end user perspective.[3] A sequential diagram shows how objects operate with one another and in what order.
|
5 |
Návrh procesů v oblasti podpory a péče o zákazníka / Design processes in customer care and supportMüller, Vladimír January 2010 (has links)
The Diploma thesis is engaged in the modelling of business processes, focusing on their design. Especially processes in area of providing support and customer care. The main goal of the thesis is application modelling method for selected business processes in a particular company engaged in telecommunications services. The theoretical part is focused on processes, process management and standards for the business process modelling. In the practical part are then described selected processes related to ABC satellite television services. These processes are designed by selected methodology. Under the proposed processes that take place after activation are calculated costs of operation the process (financial, human resources). These costs are calculated to the time when it is expected to 200,000 customers of ABC satellite television. Summary of costs is in evaluating the proposal.
|
6 |
MDR 2017/745 - New EU Regulation for Medical Devices: A Process Description for EHR Manufacturers on How to Fulfill the Regulation / MDR 2017/745 - Ny EU-förordning för medicintekniska produkter: En processbeskrivning för tillverkare av journalsystem om hur man uppfyller förordningenGermundsson, Frida, Kvist, Nicole January 2020 (has links)
On the 26th of May 2021 the new regulation for medical devices, MDR 2017/745, will come into force. The underlying incentives to go from the medical device directive (MDD 93/42/EEC) to MDR are a series of adverse events involving medical devices. The main goal of MDR is to strengthen and improve the already existing legislation and thus will entail large changes for manufactures, one of them being manufacturers of Electronic Health Record (EHR) systems. For medical software, such as EHR systems, the new regulation will imply an upgrade in risk classification. This upgrade will bring additional requirements for EHR manufacturers. Furthermore, the released guidelines have been insufficient regarding the specific requirements for medical device software and thus EHR manufacturers are in need of tools and guidance to fulfill MDR. This thesis examines the new regulation for medical devices and thus identifies main requirements for EHR manufacturers. A qualitative approach was conducted comprising a literature study as well as a document study of the medical device regulation along with interviews with experts within the field of medtech regulatory affairs and quality assurance. The information gathered was analyzed to create a process description on how EHR manufacturers are to fulfill MDR. The process description is a general outline and presents the main steps on the route to be compliant with MDR in a recommended order of execution. The main steps are: divide the system into modules, qualify the modules, classify the modules, implement a quality management system, compile a technical documentation, compile the declaration of conformity, undergo a conformity assessment and finally, obtain the CE-mark. To each of the main steps additional documentation provides further information and clarification. The process description functions as a useful tool for EHR manufacturers towards regulatory fulfillment. Even though the process description is created for EHR manufacturers, it can be useful for other medical device software manufacturers. The process description provides an overview of the path to a CE mark and functions as a guidance. It can be used in educational purposes as well as to serve as a checklist for the experienced manufacturer to make sure everything is covered. However, it is not sufficient to rely solely on the process description in order to be in full compliance with MDR. Moreover, there is still a need for further clarifications from the European Commission regarding specific requirements on medical device software.
|
Page generated in 0.1028 seconds