Approved for public release, distribution is unlimited / A military deployment is visible and vulnerable. But, deployments are currently planned assuming they can be completed with surprise, or defended from any threat. JFAST, the current deployment planning and visualization tool of choice, uses heuristics of unknown reliability that yield deployment plans of unknown quality, and ignores vulnerability. We introduce LIFTER, an integer-linear program (ILP) that optimizes a time-phased force deployment (TPFDD) by day, by asset cycle, and by TPFDD line (individual shipment from an origin to a destination), and ATTACKER, also an ILP, representing a smart enemy's resource-limited interdictions to maximally disrupt LIFTER's subsequently re-optimized TPFDD plan. LIFTER activates transport assets from an allocation list, and yields a complete logistic plan that minimizes disruption represented by penalties for early, tardy, late, or dropped shipments, and for under-utilization of asset capacity. We use LIFTER to qualitatively assess JFAST heuristic plans. We also link both ILPs in a decomposition-based search for the best deployment plan around the worst-case interdiction, given that the actions of deployer and interdictor are transparent to both parties. We explain how JFAST could be embellished with its own version of ATTACKER. A key discovery here is a gauge of the value of intelligence, deception, and secrecy. / Lieutenant, United States Navy

Dans le cycle de vie logiciel nous avons principalement les activités (1) de pré-développement (l’analyse des besoins, les spécifications, la conception architecturale et la conception détaillée), (2) de développement (l’implémentation, le prototypage, les tests unitaires et les tests d’intégration) et (3) de post-développement (déploiement). Le déploiement de logiciel couvre l’ensemble des activités post-développement. Les activités de déploiement permettent de rendre une application utilisable. Elles sont identifiées comme cycle de vie de déploiement couvrant l'archivage des logiciels, leur chargement, leur installation sur les sites clients, leur configuration, leur activation ainsi que leur mise à jour. Le développement de systèmes à composants a permis de mieux identifier cette partie du cycle de vie global du logiciel, comme le montrent de nombreux travaux industriels et académiques. Cependant ces travaux sont en général développés de manière ad’ hoc, spécifiques à une plate-forme donnée. Peu flexibles, ils s'adaptent difficilement aux stratégies des entreprises. Les systèmes de déploiement comme le montrent ceux supportés par les environnements de type intergiciel CCM, .Net, EJB développent de manière spécifique les mécanismes et outils de déploiement et introduisent des choix prédéfinis et figés de stratégies de déploiement. Nos travaux se situent dans le contexte de logiciels à base de composants distribués et portent sur la proposition d'un environnement générique pour supporter leur déploiement. C'est une nouvelle génération de systèmes proposée essentiellement par le monde académique de génie logiciel qui s'est approprié la problématique de déploiement à large échelle. Dans ce contexte, nous proposons une approche basée sur l’ingénierie dirigée par les modèles où nous introduisons les abstractions nécessaires pour décrire les logiciels à déployer, les infrastructures de déploiement, les stratégies de déploiement ainsi que le processus de déploiement avec l’identification et l’ordonnancement des activités à accomplir et le support pour leur exécution. / In the software life cycle we have mainly (1) the pre-development (requirements, specification and design), (2) the development (implementation, prototyping, testing) and (3) the post-development (deployment) activities. Software deployment encompasses all post-development activities that make an application operational. These activities, identified as deployment life cycle, include: i) software packaging, ii) loading and installation of software on client sites, iii) instance creation, iv) configuration and v) updating. The development of system-based components made it possible to better highlight this part of the global software lifecycle, as illustrated by numerous industrial and academic studies. However these are generally developed ad hoc, and consequently platform-dependent. Deployment systems, such as supported by middleware environments (CCM, .Net and EJB), specifically develop mechanisms and tools related to pre-specified deployment strategies. Our work, related to the topic of distributed component-based software applications, aims at specifying a generic deployment framework independent of the target environments. Driven by the meta-model approach, we first describe the abstractions used to characterize the deployed software. We then specify the deployment infrastructure and processes, highlighting the activities to be carried out and the support for their execution.Keywords

The aim of this dissertation is to examine gender differences in salutogenic functioning in military deployment. Salutogenisis focuses on the origin of health and wellness, and the salutogenic constructs sense of coherence (SOC), hardiness (PVS) and self-efficacy (SES) which were conceptualised focus on how individuals handle stressors positively and still remain healthy. Gender differences in military deployment were discussed, focusing on different stressors that impact on individuals' functioning when deployed. Empirically the salutogenic constructs: SOC, PVS and SES were measured. The population consisted of males and females working at 7 SAI Phalaborwa who were deployed in Kwa-Zulu Natal. Statistical techniques were applied to determine differences between males and females. The data was analysed statistically using the SPSS programme. Statistical significance was found in the SOC sub-scale "meaningfulness" and the PVS sub-scales "commitment" and "challenge". / Industrial and Organisational Psychology / M. Admin (Industrial and Organisational Psychology)

Coordenação de Aperfeiçoamento de Pessoal de Nível Superior / Cloud computing offers resources to reduce the computational costs in the institutions that uses hardware and software resources through virtualization, in addition the delivery of software as a service. There are mechanisms for automated software deployment in cloud providers, however it requires encoding or extensive knowledge for developer on the cloud provider specific technology, particularly the various requirements reconstruction, because cloud environments have their own software architectures. In this research was presented a model-based approach to automatic software deployment in the cloud environment. We presented a brief review of literature, with existing proposals for automated software deployment in cloud. In analyzed solutions, we found five that presents deployment mechanisms are script or programming language based, two proposals used manual mechanisms and two proposals applied the model-based approach to software deployment in the cloud, however still strongly linked to manual aspects and complex modeling, because it requires the developer to understand the cloud provider architecture. This research presents a new solution with detailed architecture, use cases, data flow and conceptual view of a model-based approach to automatic software deployment in the cloud. In this research was also conducted an experiment, where the solution presented positive impacts in maintainability, learn-ability and reduction of developer´s workload to deploy software services in the cloud, using UML deployment diagrams as input. / A computação em nuvem oferece recursos para reduzir os custos computacionais nas instituições que utilizam recursos de hardware e software através da virtualização, além da entrega de software como serviço. Existem mecanismos automáticos para implantação de software em provedores de nuvem, no entanto, demandam codificação ou requerem conhecimento aprofundado do desenvolvedor acerca da tecnologia específica do provedor de nuvem, sobretudo da reconstrução de vários requisitos, já que ambientes em nuvem possuem arquiteturas de software próprias. Nesta pesquisa foi apresentada uma abordagem baseada em modelos para implantação automática de software no ambiente em nuvem. Foi apresentada uma breve revisão da literatura sobre as propostas existentes para implantação automática de software na nuvem. Foram analisadas as propostas, onde cinco mecanismos de implantação baseiam-se em script ou linguagem de programação, duas propostas utilizaram em mecanismos manuais e duas propostas aplicaram uma abordagem baseada em modelos para implantação de software na nuvem, no entanto ainda fortemente ligadas a aspectos manuais e de modelagem complexa, uma vez que requer do desenvolvedor a compreensão da arquitetura do provedor de nuvem. Esta investigação apresenta uma nova solução com arquitetura detalhada, casos de uso, fluxo de dados e visão conceitual de uma abordagem dirigida a modelos para implantação de software automática na nuvem. Nesta pesquisa também foi realizado um experimento onde a solução apresentou impactos positivos em manutenibilidade, apreensibilidade e na redução na carga de trabalho do desenvolvedor para implantar serviços de software na nuvem por meio de diagramas de implantação UML como entrada.

Coordenação de Aperfeiçoamento de Pessoal de Nível Superior / Cloud computing offers resources to reduce the computational costs in the institutions that uses hardware and software resources through virtualization, in addition the delivery of software as a service. There are mechanisms for automated software deployment in cloud providers, however it requires encoding or extensive knowledge for developer on the cloud provider specific technology, particularly the various requirements reconstruction, because cloud environments have their own software architectures. In this research was presented a model-based approach to automatic software deployment in the cloud environment. We presented a brief review of literature, with existing proposals for automated software deployment in cloud. In analyzed solutions, we found five that presents deployment mechanisms are script or programming language based, two proposals used manual mechanisms and two proposals applied the model-based approach to software deployment in the cloud, however still strongly linked to manual aspects and complex modeling, because it requires the developer to understand the cloud provider architecture. This research presents a new solution with detailed architecture, use cases, data flow and conceptual view of a model-based approach to automatic software deployment in the cloud. In this research was also conducted an experiment, where the solution presented positive impacts in maintainability, learn-ability and reduction of developer´s workload to deploy software services in the cloud, using UML deployment diagrams as input. / A computação em nuvem oferece recursos para reduzir os custos computacionais nas instituições que utilizam recursos de hardware e software através da virtualização, além da entrega de software como serviço. Existem mecanismos automáticos para implantação de software em provedores de nuvem, no entanto, demandam codificação ou requerem conhecimento aprofundado do desenvolvedor acerca da tecnologia específica do provedor de nuvem, sobretudo da reconstrução de vários requisitos, já que ambientes em nuvem possuem arquiteturas de software próprias. Nesta pesquisa foi apresentada uma abordagem baseada em modelos para implantação automática de software no ambiente em nuvem. Foi apresentada uma breve revisão da literatura sobre as propostas existentes para implantação automática de software na nuvem. Foram analisadas as propostas, onde cinco mecanismos de implantação baseiam-se em script ou linguagem de programação, duas propostas utilizaram em mecanismos manuais e duas propostas aplicaram uma abordagem baseada em modelos para implantação de software na nuvem, no entanto ainda fortemente ligadas a aspectos manuais e de modelagem complexa, uma vez que requer do desenvolvedor a compreensão da arquitetura do provedor de nuvem. Esta investigação apresenta uma nova solução com arquitetura detalhada, casos de uso, fluxo de dados e visão conceitual de uma abordagem dirigida a modelos para implantação de software automática na nuvem. Nesta pesquisa também foi realizado um experimento onde a solução apresentou impactos positivos em manutenibilidade, apreensibilidade e na redução na carga de trabalho do desenvolvedor para implantar serviços de software na nuvem por meio de diagramas de implantação UML como entrada.

I kursen Examensarbete i Integrerad produktutveckling på Högskolan i Skövde har under våren 2017 ett produktutvecklingsprojekt för Kinnarps utförts av designingenjörsstudenterna Eva Henriksson och Sofie Johansson. Kinnarps är ett företag som tillverkar möbler för offentliga miljöer och vill nu i samband med deras nya satsning, att utveckla utformningen av hur lärmiljöer ser ut, ta fram ett höj- och sänkbart elevbord anpassat för årskurs 4-9. Under projektet användes och utvärderades också QFD – Quality Function Deployment som ett verktyg för att identifiera och uppfylla rätt kundbehov. Förstudien och användandet av QFD innebar bland annat att genomföra intervjuer och observationer av användare och målgruppen, identifiera trender i lärmiljöer, utföra konkurrentanalyser, utvärdera och vikta kundbehov samt att översätta behoven till kvalitéer som gick att uppfylla.Förstudien visade på att bordets viktigaste kvaliteter att uppfylla var att det skulle vara flexibelt, mobilt, tyst och enkelt att justera.Konceptutvecklingen inleddes med att identifiera och utvärdera olika höj- och sänkmekanismer. Därefter påbörjades konceptgenerering som utfördes med hjälp av olika kreativitetsmetoder. Koncepten utvärderades och sållades kontinuerligt under processen efter hur väl de uppfyllde kundbehoven samt genom användartester och återkoppling med målgruppen. Inför konceptvalet återstod till sist två koncept. Beslutet av det slutliga konceptet grundades i hur väl det uppfyllde de identifierade kundbehoven.Resultatet blev ett bord som uppfyller de ställda kraven och passar väl in i de lärmiljöer som finns idag men är också anpassat för hur lärmiljöer troligtvis kommer se ut i framtiden. Bordet har den funktionalitet som efterfrågades av användarna samtidigt som det har en utformning som är unik och tilltalande. / During the spring semester of 2017 a product development project has been carried out by two Design Engineering Students, Eva Henriksson and Sofie Johansson, in cooperation with Kinnarps. Kinnarps is a company who develops and sells furniture for public environments and as they are now focusing on the development of how educational spaces are formed and furnished they wanted to develop a height adjustable student desk for pupils between the ages of 10 to 16. To be able to reassure whether the correct customer requirements were identified and fulfilled in the right way QFD – Quality Function Deployment was used and analyzed as a part of the project. The use of QFD during the pre-study included, amongst other things, the execution of interviews and observations of users and the target group, performing competitive analyses, looking into trends , evaluate and weighing the importance of different needs and translating those into measureable specifications.The pre-study showed that needs like mobility, flexibility, simple adjustment and that the table should be as quiet as possible were the most important ones.The concept generation phase started by identifying and evaluating different options of height adjustment mechanisms. Creativity methods were used to generate ideas on how different parts of the table could be constructed. The generated concepts were then evaluated and screened continuously by looking on how well they fulfilled the customer requirements and through user tests and feedback from the target group. Two concepts remained before the final selection. The choice between these two concepts were based on to which extend each of them fulfilled the customer requirements. The final design of the table fulfills the requirements that were set and fits well into the educational spaces as they are formed today and how they probably will be designed in the future. The functionality that were requested by the users have been fulfilled while the table still has a unique and appealing look.

No description available.

In traditional Software Development Life Cycle, medium and large organizations tend to divide the activities of Operations and Development into separate departments. These groups often have a troublesome relationship because of different incentives during the software delivery process. As a result, conflicts occur between development and operations personnel as they blame each other to be the cause of long lead times and inefficient software delivery processes. The concept of DevOps emerged trying to resolve the problem that arises when separating the work of Development and Operations into organizational silos. The term DevOps is a combination of the abbreviations of Development (Dev) and Operations (Ops). DevOps aim to create a coalition that spans between Development (software developers and quality assurance) and Operation (experts responsible to roll out software to production and managing the infrastructure, e.g. system, network and database administrators and technicians). The idea is to increase the speed of the software delivery process and to quickly solve critical issues, enable organizations to better serve their customers. DevOps means that development teams who previously were solely responsible for the development of their applications now have to manage and govern both development and operational responsibilities. Thus, the adoption of DevOps might introduce new type of challenges and implications for the traditional development teams. Current literature and research about DevOps focus mainly on the challenges that DevOps attempts to overcome. There is a lack of literature on the challenges that practitioners encounter during the adoption of DevOps. As more organizations and companies tend to adopt the concept of DevOps, it increases the need to understand potential challenges and effects of adopting DevOps. Therefore, the aim of this study is to investigate the challenges that development teams encounter during the adoption of DevOps. This research was conducted by an inductive research approach through a single qualitative case study, with the use of semi-structured interviews. In total, four main challenges and fourteen sub-challenges were identified in this study. The four main challenges identified was, lack of awareness, lack of support for DevOps, implementing DevOps technology and adapting organizational processes to DevOps. This study concludes that the adoption of DevOps has a profound impact on the role of a software developer, and that the traditional role of a software developer needs to be evolved. The research provides four recommendations and means to overcome the challenges identified in this research, establishing common ways of working and spreading the knowledge, building commitment and trust by smarter seating, allocate time and resources to transition and trying out with one team and one application. / I traditionell livscykel för mjukvaruutveckling tenderar medelstora och stora organisationer att dela upp verksamheten i drift och utveckling i separata avdelningar. Dessa grupper har ofta en besvärlig relation på grund av olika incitament under mjukvaruleveransprocessen. Som ett resultat uppstår konflikter mellan utvecklings- och driftpersonal eftersom de beskyller varandra för att vara orsaken till långa ledtider och ineffektiva mjukvaruleveransprocesser. Konceptet DevOps uppstod för att försöka lösa det problem som uppstår när man separerar utveckling och drift i organisationella silosar. Termen DevOps är en kombination av förkortningarna för utveckling (Dev) och drift (Ops). DevOps syftar till att skapa en koalition som sträcker sig mellan utveckling (mjukvaruutvecklare och kvalitetssäkring) och drift (system-, nätverks- och databasadministratörer och tekniker). Idén är att öka hastigheten av mjukvaruleveranser och att snabbt lösa kritiska problem för att förbättra organisationens förmåga att betjäna sina kunder. DevOps innebär att utvecklingsgrupper som tidigare enbart ansvarade för utvecklingen av sina applikationer nu även har driftansvar. Således kan antagandet av DevOps introducera nya typer av utmaningar och konsekvenser för de traditionella utvecklingsgrupperna. Aktuell litteratur och forskning kring DevOps fokuserar främst på de utmaningar som DevOps försöker övervinna. Därav finns det brist på litteratur kring de utmaningar som utövare stöter på under antagandet av DevOps. Eftersom fler organisationer och företag tenderar att adoptera begreppet DevOps ökar behovet av att förstå potentiella utmaningar och effekter av att anta DevOps. Därav är syftet med denna studie att undersöka de utmaningar som utvecklingsgrupper bemöter under antagandet av DevOps. Denna forskning utfördes genom en induktiv forskningsinriktning, en kvalitativ fallstudie och datainsamling genom halvstrukturerade intervjuer. Totalt identifierades fyra huvudutmaningar och fjorton sub utmaningar i denna studie. De fyra huvudsakliga utmaningar som identifierades var, brist på medvetenhet, brist på stöd för DevOps, implementering av DevOps-teknik och anpassning av organisationsprocesser till DevOps. Den här studien drar slutsatsen att antagandet av DevOps har en djupgående inverkan på rollen som en mjukvaruutvecklare och att den traditionella rollen som en mjukvaruutvecklare behöver utvecklas. Studien ger fyra rekommendationer och medel för att övervinna de utmaningar som identifierats, etablering av gemensamma sätt att arbeta och sprida kunskapen, bygga upp engagemang och förtroende genom smartare sittplatser, fördela tid och resurser till övergången samt prova med ett lag och en applikation.

Målet med examensarbetet är att ta fram en lista på åtgärder vilka är ämnade åt att förbättra dokumenthanteringen och informationslagringen på Arcona, samt förbättra tillgängligheten av relevanta dokument och information.Åtgärderna ska ha en inbördes prioriteringsordning och vilka eventuella krav som ska ställas på förekommande system ska undersökas. Fokus ligger på erfarenhetsåterföring genom dokumentation och informationshantering.Vid genomförandet av projektet tillämpas Quality Function Deployment (kundcentrerad planering). Med utgångspunkten hos produktionsledarrollen har kundönskemål samlats och tolkats för att sedan presentera adekvata förslag på förbättringsåtgärder som uppdragsgivaren kan tillämpa. Resultatet innefattar en lista på åtgärder rangordnat efter föreslagen preliminär prioritering där vi högst upp finner kortfattat bland annat:- Att förstärka medarbetarnas medvetenhet kring rutiner och var de hittar särskildadokument & information.- Ett betygsättningssystem för underentreprenader som anlitas av Arcona AB.- Framtagandet av specifikt listade dokument.- En rutin för erfarenhetsåterföring som är återkommande i olika delar av produktionen.Information om vad varje punkt innefattar återfinns i rapporten. / The aim of the thesis work is to, with the role of the production managers role and function in focus, bring forth a list of suggested actions on how management of documents and information can improve and how relevant documents and information can be made more accessible. The suggested actions shall be arranged in a prioritized manner and the work shall investigate on the eventual requirements of such a system that can manage the documents/data adequately. Focus have been on utilizing experience feedback through documentation and information management. The method QFD (Quality Function Deployment) has been applied during the thesis work.The customer requirements/needs of the co-workers, primarily the productionmanagers, have been collected and interpreted to later on present adequate suggestions of action of improvement that the employer can apply.The result contains a list of actions arranged based on most highly to least highly recommended action to implement. At the top, we find amongst other actions:- To reinforce the co-workers knowledge about routines and whereabouts of specificdocuments & information.- A score-based rating system to be able to rate subcontractors that has been hired byArcona AB.- The production of certain listed documents.- A routine of documenting experience feedback that comes continuously in specific v stages of the production. Information regarding what every action includes is found inside of the thesis.

Syftet med studien var att studera fördelar samt utmaningar med att använda sig av modularisering. Vidare var syftet att undersöka hur kundens önskemål tas i beaktning vid produktutvecklingsprocessen för modulära produkter. Studien avgränsades till att undersöka ett svenskt teknikintensivt företag vars huvudsakliga produkterbjudande är lastbilar och bussar. En litteraturstudie genomfördes och låg till grund för resten av rapporten. Dessutom är rapporten baserad på en kvalitativ empirisk studie bestående av semistrukturerade intervjuer. Samtliga respondenter har goda kunskaper om modularisering och arbetar på olika avdelningar hos det studerade företaget. Studien visar många fördelar och utmaningar med att ha en modulär produktarkitektur. En av de främsta fördelarna är en stor slutproduktsvariantbildning vilket möjliggör skapande av högst kundanpassade produkter. Produktarkitekturen skapar tillfredsställda kunder som är- villiga att betala ett högre pris. Inom produktion leder den modulära produktarkitekturen till ett effektivare arbete samt kortare ledtider. Produkterna tillverkas efter order vilket minskar lagernivåerna samt logistikkostnaderna. Vid produktutveckling är det av stor betydelse att förhålla sig till befintliga gränssnitt och formfaktorer vilket gör att det krävs mer tankeverksamhet samt att kompromisser ibland behöver göras. Det är ett komplext system i många aspekter vilket ökar behovet av en stark företagskultur och en stabil IT-infrastruktur. / This report aims to study the benefits and challenges of using modularization. The purpose was also to investigate how customer requirements are taken into account in the product development process for modular products. The study was limited to examining a Swedish technology-intensive company whose main product offerings are trucks and buses. A literature review served as the basis for the rest of the report. In addition, the report is based on a qualitative empirical study consisting of semi-structured interviews. All respondents have good knowledge of modularization and work in different departments at the studied company. The study demonstrated many advantages and challenges of having a modular product architecture. One of the primary benefits was a large number of possible end product variations, which allows for highly customized products. Thus, the product architecture enables satisfied customers, making them willing to pay a higher price. In production, the modular product architecture leads to more efficient work and shorter lead times. Products are manufactured by make-to-order, reducing inventory levels and logistics costs. In product development, it is crucial to adhere to existing interfaces and form factors, which requires more thoughtful consideration and sometimes compromises. It is a complex system in many aspects, increasing the need for a strong corporate culture and a stable IT-infrastructure.