Fotgangarsimuleringar anvands frekvent vid planering av o entliga utrymmen, dar fotgangarbeteendet ar betydande for andamalet. Simuleringarna anvands saledes inom bade den privata och den o entliga sektorn. Pa senare tid har automatiserad analys av insamlad videodata om faktiska fotgangare blivit allt mer vanligt som en grund for validering inom forskningsomradet. Conditional Transition Maps utgor en representation av dynamiska element i en miljo, dar varje diskret cell i kartan associeras med en sannolikhetsdistribuering for overgangar till och fran cellen. CTMaps har tidigare anvants inom navigering for mobila robotar. Denna uppsats utgor en utredning av mojligheterna att anvanda en CTMap som en grund for en fotgangarmodell. CTM-datat som anvants i uppsatsen har tagits fram ur insamlad videodata om faktiska fotgangare. En fotgangarmodell har tagits fram, med hjalp av utvecklingsmiljon SeSAm, och jamforts med en redan etablerad modell for fotgangarsimulering. / Pedestrian simulation is widely used in both the public and private sector for designing public spaces, when pedestrian behavior is central to the design. Recently, automated analysis of recorded data of actual pedestrians has emerged as a means of introducing empirical validation in the eld of pedestrian simulation. Conditional Transition Maps represent dynamic elements of an environment as transition probabilities and map them to discrete oor-elds. These maps have been previously used for mobile robot navigation. This thesis constitutes an investigation into the possibilites of using a CTMap as a basis for a pedestrian simulation model. The CTMap used in the thesis has been produced by analyzing recorded video data of actual pedestrians. A pedestrian model based on the CTMap was developed, using SeSAm, and compared to an already established pedestrian simulation model.

This bachelor thesis looks at the functionality of different frameworks for data analysis atlarge scale and the purpose of it is to serve as a guide among available tools. The amount ofdata that is generated every day keep growing and for companies to take advantage of thedata they collect they need to know how to analyze it to gain maximal use out of it. Thechoice of platform for this analysis plays an important role and you need to look in to thefunctionality of the different alternatives that are available. We have created a guide to makethis research easier and less time consuming. To evaluate our work we created a summaryand a survey which we asked a number of ITstudents,current and previous, to take part in.After analyzing their answers we could see that most of them find our thesis interesting andinformative.

Denna rapport handlar om projektgruppens samlade erfarenheter om hur det är att arbetamed ett större mjukvaruprojekt. Fokus för detta ligger på erfarenheter inom gruppdynamikoch kundinteraktion. Rapporten lyfter även fram hur användandet av Essence Kernel Alpha:spåverkade gruppens arbete. Rapporten försöker också undersöka och ge förslag påfinansieringsmodeller för projekt med öppen källkod. Det som iakttogs var att planering ochöppen kommunikation i stor del påverkar ett projekts utveckling. Liknande slutsatser kundedras vad gäller kundinteraktion. Användandet av Alpha-tillstånd sågs som mindre användbartför mindre mjukvaruprojekt. Flertalet finansieringsmodeller kan användas för projekt medöppen källkod och vilken som passar beror på projektets struktur och gruppenssammansättning. De som skulle passat det projekt som gruppen gjorde ansågs vara enoptimeringsstrategi, dubbellicensstrategi, sponsringstrategi eller crowdfunding.Denna rapport avslutas även med utredningar gjorda individuellt av gruppens olikamedlemmar. Dessa handlar om jämförelser av olika ärendehanteringssystem, problem ochlösningar inom kravelicitering, fördelar med parprogrammering på distans, hurkodgranskning kan användas som testmetod, vad riskbedömning kan bidra med och hur ettkodskelett kan användas som underlag för uppgiftsutdelning.

The development of autonomous Mobile Robot Systems is attracting nowadays more and moreinterest from both researchers and practitioners, mainly because they may open for a wide rangeof improvements for quality of life. Mobile robots are systems capable of accomplishing missionsby moving in an unknown environment without human supervision. Throughout mechanisms ofdetection, communication and adaptation, they can adapt their behavior according to changes ofthe environment. Individual robots can even join teams of autonomous mobile robots that, throughindividual tasks, accomplish common missions. These are called Mobile Multi-Robot Systems andare meant to perform missions that a single robot would not be able to carry out by itself.When it comes to the development of Mobile Robot Systems, currently there is no standard methodology.This is mainly due to the complexity of the domain and the variety of di↵erent platformsthat are available on the market. A promising methodology that recently has gained attention insoftware industry for its ability of mitigating complexity and boosting platform-independence, isModel-Driven Engineering.This thesis proposes a systematic mapping study on the state-of-the-art of Model-Driven Engineeringfor Mobile Robot Systems. Through our contribution, researchers can get a picture of theactual trends and open challenges for further research, while practitioners can realize the suitabilityof Model-Driven Engineering by checking to what extent it has been applied to real-world projects.

Context: Requirements prioritization is used in software product management and is concerned with identifying the most valuable requirements from a given set. This is necessary to satisfy the needs of customers, to provide support for stakeholders and more importantly for release planning. Irrespective of the size of the organization (small, medium and large), requirements prioritization is important to minimize the risk during development. However, few studies explore how requirements prioritization is practiced in start-ups. Software start-ups are becoming important suppliers of innovative and software-intensive products.Earlier studies suggest that requirements discovery and validation is the core activity in start-ups. However, due to limited resources, start-ups need to prioritize on what requirements to focus. If they do it wrong it leads to wasted resources.While larger organizations may afford such waste, start-ups cannot.Moreover, researchers have identified that start-ups are not small versions of large companies and the existing software development practices cannot be transferred directly due to low rigor in current studies.Thus, we planned to conduct an exploratory study on requirements prioritization practices in the context of software start-ups. Objectives: The main aim of our study is to explore the state-of-art of requirements prioritization practices used in start-ups.We also identify the challenges associated with the corresponding practices and few possible solutions. Methods: In this qualitative research, we conduct a literature review by referring to many article sources like IEEE Xplore, Scopus, and Google Scholar to identify the prioritization practices and challenges in general. An interview study is conducted by using semi-structured interviews to collect data from practitioners.Thematic analysis was used to analyze the interview data. Results: We have identified 15 practices from 8 different start-ups companies with corresponding challenges and possible solutions. Our results show mixed reviews in terms of the prioritization practices at start-ups. From the total of 8 companies about 6 companies followed formal methods while in the remaining 2 companies, prioritization was informal and not clear. The results show that value-based method is the dominant prioritization technique in start-ups. The results also show that customer input and return on investment aspects of prioritization play a key role when compared to other aspects. Conclusions: The results of this study provide an understanding of the various requirements prioritization practices in start-ups and challenges faced in implementing them.These results are validated from the answers found in the literature. The solutions identified for the corresponding challenges allow the practitioners to approach them in a better way. As this study focused only on Indian software start-up companies, it is recommended to extend to Swedish software start-up companies as well to get a broader perspective. Scaling of sample size is also recommended. This study may help future research on requirements engineering in start-ups. It may also help practitioners who have an intention to begin a software start-up company to get an idea of what challenges they may face while prioritizing requirements and can use these solutions to mitigate them.

Although we cannot show a direct link between tool adoption and tool interoperability in this thesis, we have completed the first step by increasing our understanding of interoperability. This thesis shows how to use existing technology such as XML, SOAP and GXL to improve interoperability. Although the ideas behind XML are not new, XML has been used to increase interoperability between systems. While the goal is to improve interoperability, we also keep in mind other software engineering design concerns, such as ease of maintenance and scalability. To evaluate our ideas about improving interoperability, we completed a prototype, which allows us to compare our approach to other existing systems. Our prototype is a reverse engineering tool for which existing systems and requirements are readily available. Some of the more relevant requirements include tool customization, persistence, tool deployment and interoperability. These requirements were combined with the reverse engineering requirements in the design stages of development in the hope of creating a more cohesive system. In our quest to improve interoperability of reverse engineering tools, we considered three types of integration. Data integration refers to the extent to which applications can share or use each other's data. Control integration is the ability of one system to request another system to perform some action. Process integration is similar to other forms of integration in so far as it looks at how to easily move between two user processes or actions. In this thesis we compare our prototype, the ACRE Engine, with the Rigi system. The comparison focused on our understanding of interoperability. We found that the Rigi system has many data integration features-most of which stem from its proprietary data format, Rigi Standard Format (RSF). Rigi's ability to integrate control between applications is restricted to file system messages. We did find the Rigi system could complete process integration tasks effectively. In this thesis we show that the ACRE System is at least as good, and in most cases better than the existing Rigi system with respect to the three forms of interoperability mentioned above.

M.Com. / Please refer to full text to view abstract

Background: Recruitment and onboarding of software developers are essential steps in software development undertakings. The need for adding new people is often associated with large-scale long-living projects and globally distributed projects. The formers are challenging because they may contain large amounts of legacy (and often complex) code (legacy projects). The latters are challenging, because the inability to find sufficient resources in-house may lead to onboarding people at a distance, and often in many distinct sites. While onboarding is of great importance for companies, there is little research about the challenges and implications associated with onboarding software developers and teams in large-scale globally distributed projects with large amounts of legacy code. Furthermore, no study has proposed any systematic approaches to support the design of onboarding strategies and evaluation of onboarding results in the aforementioned context. Objective: The aim of this thesis is two-fold: i) identify the challenges and implications associated with onboarding software developers and teams in large-scale globally distributed legacy projects; and ii) propose solutions to support the design of onboarding strategies and evaluation of onboarding results in large-scale globally distributed legacy projects. Method: In this thesis, we employed literature review, case study, and business process modeling. The main case investigated in this thesis is the development of a legacy telecommunication software product in Ericsson. Results: The results show that the performance (productivity, autonomy, and lead time) of new developers/teams onboarded in remote locations in large-scale distributed legacy projects is much lower than the performance of mature teams. This suggests that new teams have a considerable performance gap to overcome. Furthermore, we learned that onboarding problems can be amplified by the following challenges: the complexity of the product and technology stack, distance to the main source of product knowledge, lack of team stability, training expectation misalignment, and lack of formalism and control over onboarding strategies employed in different sites of globally distributed projects. To help companies addressing the challenges we identified in this thesis, we propose a process to support the design of onboarding strategies and the evaluation of onboarding results. Conclusions: The results show that scale, distribution and complex legacy code may make onboarding more difficult and demand longer periods of time for new developers and teams to achieve high performance. This means that onboarding in large-scale globally distributed legacy projects must be planned well ahead and companies must be prepared to provide extended periods of mentoring by expensive and scarce resources, such as software architects. Failure to foresee and plan such resources may result in effort estimates on one hand, and unavailability of mentors on another, if not planned in advance. The process put forward herein can help companies to deal with the aforementioned problems through more systematic, effective and repeatable onboarding strategies.

No description available.

M.Ing.