Dagens system har blivit allt mer komplexa och därmed även processen att utveckla systemen. Det finns många olika tillvägagångssätt för systemutvecklare att arbeta och flera olika verktyg att använda sig av. Den utvecklingsmiljö en utvecklare använder sig av kan därmed ha en påverkan på hur utvecklingsprocessen ser ut. Utvecklingsmiljön är ett viktigt verktyg i dagens utvecklande samhälle och vilka för- och nackdelar olika verktyg för med sig diskuteras flitigt mellan utvecklare på olika nätforum. Från dessa forum framkommer det att vissa utvecklare föredrar att använda textredigerare istället för integrerade utvecklingsmiljöer och vice versa. Tidigare forskning har exempelvis undersökt hur kännedom kring verktyg sprids effektivt mellan utvecklare (Murphy-Hill & Murphy, 2011), men denna uppsats syftar till att förklara varför utvecklare använder olika utvecklingsmiljöer och bakomliggande faktorer till detta. För att åstadkomma detta har respondenter med bred kunskap inom ämnet intervjuats och nämnt faktorer som påverkat deras val av utvecklingsverktyg. Samtliga intervjupersoner har arbetat i både integrerade utvecklingsmiljöer och textredigerare och har därmed åsikter om båda miljöerna. Enligt vår studie finns inga tydliga indikeringar för vilken utvecklingsmiljö som är att föredra i alla lägen. En utvecklare använder det verktyg som passar dess arbetsprocess bäst, men kan ibland använda andra verktyg för att komplettera sin verktygslåda. Vad som styr utvecklaren har att göra med personliga preferenser, hur utvecklaren har påverkats av utbildning och erfarenheter samt potentiella restriktioner inom organisationer. / Today's systems have become more complex and thus the process of developing systems. There are many different approaches for developers to work and several tools that can be used. The environment a developer uses can therefore have an impact on how the development process proceeds. The development environment is an essential tool in today’s evolving society, and what advantages and disadvantages different tools bring are being discussed frequently between developers on various online forums. From these forums, it appears that some developers prefer to use text editors instead of integrated development environments and vice versa. Previous research has shown, for example, how knowledge about the tools is spread effectively between developers (Murphy Hill & Murphy, 2011). But this paper seeks to explain why developers are using different development environments and the factors behind this. To achieve this, we interviewed respondents with broad knowledge about the subject that stated the factors that influenced their choice of development tools. All the interviewees have worked in both integrated development environments and text editors and therefore have opinions about both environments. According to our study, there are no clear indications that a specific development environment is preferred in all situations. A developer is using the tool that fits their work process best, but sometimes uses other tools to complement their toolbox. In choosing a tool the developer is influenced by personal preferences, how surroundings have influenced the developer through education and experience, and potential constraints within organizations.

The diploma thesis called Visual Style of the National Geographic Magazine (1914, 1964, 2014) is focused on the visual part of this American monthly magazine, that is renowned for its long-standing photography tradition. In the theoretical part the historic development of the National Geographic monthly magazine is summarized, characteristic features of its photographs are defined and compared to the different photographic genres. With relation to the magazine, issues of visual gatekeeping are discussed. The theoretical part is accompanied by examples of published photo manipulations and a chapter about the image-text relation is provided. The analytical part aims at the development of photographic techniques and photographic content in the selected years 1914, 1964 and 2014. Using the method of content analysis this work deals with over 1000 photographs and allocates them in different coding categories. It is explored which category or characteristic features were typical for each period, for example in connection with gender, locations or the way of capturing the image. The results of content analysis are put into context by semiotic study which is based on the methods of philosopher Roland Barthes. In addition to that, the analytical part is supplemented with the analysis of selected visual...

The thesis is concerned with the presence of news journalists and news institutions on social media sites. Mentioned modern technology had large effect on the development of the field as well as everyday journalistic routine. Social media not only brought brand new possibilities, it was also accompanied by modern age dilemmas and ethical conundrums that journalists have to face. Most of the Czech news institutions however still ignore the option of internal regulation via ethical code of any sorts which alienates them from the western media current praxis. In the sake of requiring information necessary to describe functioning of social media content production in Czech news media, the author carried out a qualitative research questioning members of social media departments of mentioned institutions. Based on the research, the thesis answers questions about personnel responsibilities in managing company social media profiles and introduces ethical codes and official internal rules they have to follow whereas the conclusion is that most of Czech news institution haven't implemented any of those yet.

Este trabalho aborda a efetiva utilização de técnicas diagramáticas para o desenvolvimento de software orientado a objetos durante as fases de análise e projeto de sistemas. Durante o desenvolvimento de software normalmente as especificações resultantes das fases de análise e projeto possuem uma forma gráfica. A utilização de diagramas no desenvolvimento de software busca facilitar a criação de especificações de um sistema e ao mesmo tempo torná-las mais compreensíveis. A grande maioria das técnicas diagramáticas que existem atualmente são utilizadas para o apoio ao desenvolvimento de software segundo metodologias fundamentadas no paradigma tradicional de decomposição funcional. Diversas técnicas diagramáticas foram criadas ou adaptadas a fim de suportar os conceitos deste paradigma, acompanhando a própria evolução do mesmo. Neste contexto, são apresentadas as características básicas de técnicas diagramáticas tradicionais que apoiam a este paradigma. A partir da introdução dos conceitos de orientação a objetos no desenvolvimento de software, surge a necessidade de criação de novas técnicas diagramáticas ou adaptação de técnicas diagramáticas tradicionais para o suporte adequado ao desenvolvimento de sistemas sob este paradigma. Neste contexto, são abordados os conceitos envolvidos na orientação a objetos e apresentados os aspectos diferenciais no desenvolvimento de software decorrentes da utilização deste paradigma em contraposição aos paradigmas tradicionais. São também apresentadas as tarefas específicas realizadas durante o desenvolvimento de software, nas fases de análise e projeto, que estão inseridas no ciclo de vida de um software orientado a objetos. É proposto um conjunto de notações diagramáticas inter-relacionadas adequado ao apoio de um esquema de etapas básicas para o desenvolvimento de software orientado a objetos, bem como as metodologias já existentes. Durante a descrição destas notações diagramáticas, são apresentadas as suas características individuais, adaptações realizadas para o suporte a orientação a objetos, suas aplicações específicas no desenvolvimento de sistemas e o inter-relacionamento existente. Finalmente, são definidas as características de recursos e facilidades específicas para o apoio às notações propostas. Dentro dos recursos sugeridos inclui-se a definição da implementação de um editor diagramático que é descrito através das notações sugeridas neste trabalho. / This work tackles the effective use of diagramming techniques for object-oriented software development during analysis and design phases. During software development the specifications produced by analysis and design usually take a graphical form. The use of diagrams in software development occurs because designers and analysts like to express themselves that way to turn the specifications more understandable. Most of diagramming techniques in use nowadays support software development following methodologies based on the conventional functional decomposition paradigm. Various diagramming techniques were created or adapted in order to support the concepts of this paradigm, following its own evolution. With the introduction of object-oriented concepts new diagramming techniques were created or adapted from conventional methodologies. This work introduces the concepts of object orientation, as well as, the changes originated from the use of this paradigm in software development. Specific steps related to the analysis and design stages in the object-oriented software life cycle are also presented. A set of interrelated diagramming techniques for supporting object-oriented software development is presented. A set of interrelated diagramming techniques for supporting object-oriented software development is presented. The description of these diagramming techniques includes new features, discussion of adaptations for object-oriented techniques, specific applications and uses, and their integration. Finally, the features of specific resources and facilities for supporting the proposed notations are defined. The description of the implementation of a diagrammatic editor, using the notations presented in this work, is included.

Este trabalho aborda a efetiva utilização de técnicas diagramáticas para o desenvolvimento de software orientado a objetos durante as fases de análise e projeto de sistemas. Durante o desenvolvimento de software normalmente as especificações resultantes das fases de análise e projeto possuem uma forma gráfica. A utilização de diagramas no desenvolvimento de software busca facilitar a criação de especificações de um sistema e ao mesmo tempo torná-las mais compreensíveis. A grande maioria das técnicas diagramáticas que existem atualmente são utilizadas para o apoio ao desenvolvimento de software segundo metodologias fundamentadas no paradigma tradicional de decomposição funcional. Diversas técnicas diagramáticas foram criadas ou adaptadas a fim de suportar os conceitos deste paradigma, acompanhando a própria evolução do mesmo. Neste contexto, são apresentadas as características básicas de técnicas diagramáticas tradicionais que apoiam a este paradigma. A partir da introdução dos conceitos de orientação a objetos no desenvolvimento de software, surge a necessidade de criação de novas técnicas diagramáticas ou adaptação de técnicas diagramáticas tradicionais para o suporte adequado ao desenvolvimento de sistemas sob este paradigma. Neste contexto, são abordados os conceitos envolvidos na orientação a objetos e apresentados os aspectos diferenciais no desenvolvimento de software decorrentes da utilização deste paradigma em contraposição aos paradigmas tradicionais. São também apresentadas as tarefas específicas realizadas durante o desenvolvimento de software, nas fases de análise e projeto, que estão inseridas no ciclo de vida de um software orientado a objetos. É proposto um conjunto de notações diagramáticas inter-relacionadas adequado ao apoio de um esquema de etapas básicas para o desenvolvimento de software orientado a objetos, bem como as metodologias já existentes. Durante a descrição destas notações diagramáticas, são apresentadas as suas características individuais, adaptações realizadas para o suporte a orientação a objetos, suas aplicações específicas no desenvolvimento de sistemas e o inter-relacionamento existente. Finalmente, são definidas as características de recursos e facilidades específicas para o apoio às notações propostas. Dentro dos recursos sugeridos inclui-se a definição da implementação de um editor diagramático que é descrito através das notações sugeridas neste trabalho. / This work tackles the effective use of diagramming techniques for object-oriented software development during analysis and design phases. During software development the specifications produced by analysis and design usually take a graphical form. The use of diagrams in software development occurs because designers and analysts like to express themselves that way to turn the specifications more understandable. Most of diagramming techniques in use nowadays support software development following methodologies based on the conventional functional decomposition paradigm. Various diagramming techniques were created or adapted in order to support the concepts of this paradigm, following its own evolution. With the introduction of object-oriented concepts new diagramming techniques were created or adapted from conventional methodologies. This work introduces the concepts of object orientation, as well as, the changes originated from the use of this paradigm in software development. Specific steps related to the analysis and design stages in the object-oriented software life cycle are also presented. A set of interrelated diagramming techniques for supporting object-oriented software development is presented. A set of interrelated diagramming techniques for supporting object-oriented software development is presented. The description of these diagramming techniques includes new features, discussion of adaptations for object-oriented techniques, specific applications and uses, and their integration. Finally, the features of specific resources and facilities for supporting the proposed notations are defined. The description of the implementation of a diagrammatic editor, using the notations presented in this work, is included.

Este trabalho aborda a efetiva utilização de técnicas diagramáticas para o desenvolvimento de software orientado a objetos durante as fases de análise e projeto de sistemas. Durante o desenvolvimento de software normalmente as especificações resultantes das fases de análise e projeto possuem uma forma gráfica. A utilização de diagramas no desenvolvimento de software busca facilitar a criação de especificações de um sistema e ao mesmo tempo torná-las mais compreensíveis. A grande maioria das técnicas diagramáticas que existem atualmente são utilizadas para o apoio ao desenvolvimento de software segundo metodologias fundamentadas no paradigma tradicional de decomposição funcional. Diversas técnicas diagramáticas foram criadas ou adaptadas a fim de suportar os conceitos deste paradigma, acompanhando a própria evolução do mesmo. Neste contexto, são apresentadas as características básicas de técnicas diagramáticas tradicionais que apoiam a este paradigma. A partir da introdução dos conceitos de orientação a objetos no desenvolvimento de software, surge a necessidade de criação de novas técnicas diagramáticas ou adaptação de técnicas diagramáticas tradicionais para o suporte adequado ao desenvolvimento de sistemas sob este paradigma. Neste contexto, são abordados os conceitos envolvidos na orientação a objetos e apresentados os aspectos diferenciais no desenvolvimento de software decorrentes da utilização deste paradigma em contraposição aos paradigmas tradicionais. São também apresentadas as tarefas específicas realizadas durante o desenvolvimento de software, nas fases de análise e projeto, que estão inseridas no ciclo de vida de um software orientado a objetos. É proposto um conjunto de notações diagramáticas inter-relacionadas adequado ao apoio de um esquema de etapas básicas para o desenvolvimento de software orientado a objetos, bem como as metodologias já existentes. Durante a descrição destas notações diagramáticas, são apresentadas as suas características individuais, adaptações realizadas para o suporte a orientação a objetos, suas aplicações específicas no desenvolvimento de sistemas e o inter-relacionamento existente. Finalmente, são definidas as características de recursos e facilidades específicas para o apoio às notações propostas. Dentro dos recursos sugeridos inclui-se a definição da implementação de um editor diagramático que é descrito através das notações sugeridas neste trabalho. / This work tackles the effective use of diagramming techniques for object-oriented software development during analysis and design phases. During software development the specifications produced by analysis and design usually take a graphical form. The use of diagrams in software development occurs because designers and analysts like to express themselves that way to turn the specifications more understandable. Most of diagramming techniques in use nowadays support software development following methodologies based on the conventional functional decomposition paradigm. Various diagramming techniques were created or adapted in order to support the concepts of this paradigm, following its own evolution. With the introduction of object-oriented concepts new diagramming techniques were created or adapted from conventional methodologies. This work introduces the concepts of object orientation, as well as, the changes originated from the use of this paradigm in software development. Specific steps related to the analysis and design stages in the object-oriented software life cycle are also presented. A set of interrelated diagramming techniques for supporting object-oriented software development is presented. A set of interrelated diagramming techniques for supporting object-oriented software development is presented. The description of these diagramming techniques includes new features, discussion of adaptations for object-oriented techniques, specific applications and uses, and their integration. Finally, the features of specific resources and facilities for supporting the proposed notations are defined. The description of the implementation of a diagrammatic editor, using the notations presented in this work, is included.

The aim of this work is to design and implement applications for the creation of web page layout facilities using JavaScript. The work includes the descriptions of the available methods of object positioning using the CSS given possibilities, the CSS 2.1 standard, and the difficulties of object positioning using CSS. Further, it includes the analysis of how the object placement is solved in the Java programming language using grid based layout managers GridLayout and GridBagLayout. Based on the obtained knowledge, designs are created for the solving of object placement in the creation of web pages using the grid principle. The object placement is solved by defining new HTML attributes for position determination, and also by creating a graphical editor for object placement. All the solutions are implemented using JavaScript.

This work deals with the development and use of a graphical editor of object-oriented Petri nets implemented in the PNtalk language. First, Petri nets that expand over time are described here. They are followed by a description of the object-oriented paradigm. Next, the structure of object-oriented Petri nets in the implementation of PNtalk is described here. Further work presents a description of the application design, which shows the entire structure of the application from the perspective of views. The main motivation for creating this tool is the effort to make object-oriented Petri nets accessible to their users. The application was implemented in the JavaFX framework and the whole procedure is given in the following chapter together with testing. The result of the work is presented in the examples contained in the last chapter, which also contains detailed manuals for controlling the application. The tool in cooperation with the PNtalk server enables users to work more pleasantly with OOPN and their visual appearance.

Real-time collaboration editing is research area that has been studied for over 20 years. It involves multiple users editing a document such as plain-text, rich-text or an image concurrently over a high-latency network. Many problems involving consistency between users are associated with concurrent document editing, and an innovative technique called Operational Transformation developed by the GROVE (GRoup Outline Viewing Editor) system in 1989 addresses some of these issues. This paper will compare and contrast current implementations of real-time collaborative editors, and on the basis of this analysis describe the creation of a new web-based editor with support for concurrent editing. The design of our web editor will focus on methods of mutual communication between the individual instances of the editors, propagation of text changes, how to solve conflicts between multiple operations, and communication failures.

In the present thesis, the author aims at the issue of visual editor in television newscast. In practical part of the thesis, particular occupations of visual editors are characterized. The characteristics were conducted on the grounds of author's research in newsrooms at TV Nova and ČT 24. Furthermore, the practical part comprises comparison and description of differences among the observed occupations. It also provides analysis of visual information Události, the main news broadcast of Czech Television. Theoretical part covers issues related to the occupation of visual editor in television news broadcast such as digitalisation, computer graphics, principles of visual language in television news and characteristics of television studios at TV Nova and ČT 24.