No description available.

No description available.

Preem verkar inom drivmedelsbranschen som styrs av en mycket hög omsättning med förhållandevis små marginaler. Det är därför viktig med en väl fungerande lagerkontroll. Det man idag är ute efter är en ökad precision i lageruppföljningen och därmed behövs ett nytt systemstöd till detta. Jag fick i min roll hos Preem uppgiften att titta närmre på GUI och processerna bakom. Det resulterade i denna rapport med ett framtaget förslag på användargränssnittet till det nya systemet och dess affärsprocesser som är kopplat till detta. Arbetet fokuserar på hur de två framställs i förhållande till varandra och vilka metoder som används för att konstruera dessa. Arbetet inkluderar illustrationer av as-is och to-be processmodeller enligt BPMN specifikation, wireframes och en sitemap. Denna rapport visar ett förslag på ett sammanfört system och ett intuitivare GUI med nya processer bakom, för just Preem, och hur balansgången går mellan att skapa affärsprocesser och ett grafiskt användargränssnitt ur varandra, beroende av vilka som är involverade i projektet. / Preem is a Swedish company that operates in the oil industry, which is controlled by very high sales and with relatively small margins. It’s therefore essential with a well working stock control. Today they are looking for a better way of monitoring the stock with a higher precision and therefore they need a new system for that. My role at Preem was to take a closer look at the GUI and the processes behind that. It resulted in this thesis that includes the user interface for the new system and the business processes that are linked to this. The work will focus on how these two methods are produced in relation to each other, and the methods that are used to construct them. The thesis includes illustrations of as-is and to-be process models of the BPMN specification, wireframes and a sitemap. This report shows a proposal of an integrating system and an intuitive GUI with new processes, at Preem, and how the balance is between creating business processes and a graphical user interface out of each other, depending on the people who are involved in the project.

>Magister Scientiae - MSc / The purpose of this thesis is to discuss the development of a web application from scratch. It serves to build a health management information system from basic principles and covers all the software engineering activities starting from the gathering of requirements, evaluating these and eventually implementing a health management information system by applying several iterations of the Agile-extreme-programming-software-engineering approach to develop a Health Management System for the Kabul University Poly-clinic located at Kabul University campus in order to computerize clerical activities at the hospital. Questionnaires were used to uncover the clerical problems experienced by the hospital sta . Attempts to address these problems by designing and im- plementing software and re ne the software after some iterations of feedback- redesign-and-implementation following the guidelines of Agile extreme pro- gramming. The previous Health management systems at the hospital were paper based. The new computerized system has eased the burdens of tracking the les of patients at the hospital, leading to easier and more e cient access to information by the health-care professionals at the hospital. An assessment of the impact this has had on the medical and clerical sta and the smoother administration of the hospital by repeated user acceptance testing by means of questionnaires con rms the success of the project.

Made available in DSpace on 2015-03-05T13:58:27Z (GMT). No. of bitstreams: 0 Previous issue date: 23 / Coordenação de Aperfeiçoamento de Pessoal de Nível Superior / Uma das tarefas críticas na confecção de sistemas de software é a elicitação de requisitos, a qual configura uma ação de descoberta de conhecimento. Assim, muitas técnicas são empregadas na tentativa de minimizar conflitos de idéias, conceitos mal formados, interpretações redundantes e omissão de dados; sendo que, para tanto, o uso de cenários, entrevistas, cartões, viewpoints e diagramas de Use Case são utilizados como ferramentas para diminuir a distância entre o técnico e o usuário na definição dos requisitos. Além disso, os Mapas Conceituais têm sido empregados com muita eficiência em tarefas de captura de conhecimento, portanto, este trabalho utiliza esse conceito como forma de organizar, identificar, aprimorar conceitos e definições dos requisitos de um software de forma cooperativa, formatado em User Story da metodologia Extreme Programming (XP). Com esse objetivo, o processo é apoiado por uma ferramenta baseada na web, que automatiza a geração, organização e acompanhamento da captura dos requisitos ge / One of the hardest tasks of building a software system is requirements elicitation, which triggers a knowledge discovery action. Thus, many techniques are used with the intention to minimize idea conflicts, misformed concepts, erroneous interpretations and missing data; In order to achieve this goal, scenarios interviews, User Stories, viewpoints and Use Case diagrams are techniques to reduce the distance between the researcher and the user on requirement elicitation. Concept maps have been used as efficient way to represent knowledge. This research uses concept maps to deal with the organization, identification and improvement of concepts and software requirements definitions in a cooperative way, making use of the User Story format introduced by the Extreme Programming (XP) methodology. The proposed process is supported by a web-based tool, which automates the generation, organization and management of the requirements capture generated in the Concept Maps format

Requirements are features or attributes which we discover at the initial stage of building a product. Requirements describe the system functionality that satisfies customer needs. An incomplete and inconsistent requirement of the project leads to exceeding cost or devastating the project. So there should be a process for obtaining sufficient, accurate and refining requirements such a process is known as requirement elicitation. Software requirement elicitation process is regarded as one of the most important parts of software development. During this stage it is decided precisely what should be built. There are many requirements elicitation techniques however selecting the appropriate technique according to the nature of the project is important for the successful development of the project. Traditional software development and agile approaches to requirements elicitation are suitable in their own context. With agile approaches a high-level, low formal form of requirement specification is produced and the team is fully prepared to respond unavoidable changes in these requirements. On the other hand in traditional approach project could be done more satisfactory with a plan driven well documented specification. Agile processes introduced their most broadly applicable technique with user stories to express the requirements of the project. A user story is a simple and short written description of desired functionality from the perspective of user or owner. User stories play an effective role on all time constrained projects and a good way to introducing a bit of agility to the projects. Personas can be used to fill the gap of user stories.

Made available in DSpace on 2016-06-02T19:05:56Z (GMT). No. of bitstreams: 1 4409.pdf: 4554321 bytes, checksum: 40828d088d2ef261abc9e99060a90ab0 (MD5) Previous issue date: 2012-06-26 / Universidade Federal de Sao Carlos / This project investigated an Agile Development Process for groupware on theWeb 2.0. The process has its based in different technologies, especially those of the Scrum agile method, integrated with functional testing at the acceptance level. To assist this integration, we established a greater intercommunication between the process disciplines, using the User Stories as artifacts in all disciplines. The process aims to take advantage of the agility of the Scrum without losing quality in the development of applications. It was developed based on the Scrum process, with the addition of technologies that support the creation and use of artifacts in the search for integration with functional testing. The process uses three disciplines, each one refining the User Stories, which occur in different degrees of abstraction throughout the development. These stories should be a most faithful portrait possible of user needs and are used both in the form of cards (Story Cards), for requirements specification, and in an executable format to guide the implementation and work as functional testing. Mockups are used to complement the requirements specified in the cards, assisting in the task of representing the requirements. This set is the basis for the creation of User Stories in executable format. Other modeling artifacts, like Class Diagram, can also be specified in order to elicit requirements of the application. The procedure is supported by tools developed to enable the integration of the functional tests. These tools define a tests specification language to write User Stories, created as a DLL for Visual Studio, and a converter of these User Stories for functional testing in C# code. Thus, the proposed process provides a greater integration of tests during the development and execution of each discipline in order to produce higher quality applications. To test the process, applications were developed in the domain of groupware in Web 2.0. The adoption of this area was motivated by the idea of exploring the development of collaborative software that supports group work of people involved in common tasks. / Este projeto pesquisou um Processo de Desenvolvimento Ágil para groupware na Web 2.0. O Processo tem suas bases em diferentes tecnologias, destacando-se as do método ágil Scrum, e é integrado com testes funcionais a nível de aceitação. Para auxiliar essa integração, estabeleceu-se uma maior intercomunicação entre as disciplinas do processo, utilizando as Histórias do Usuário como artefatos em todas as disciplinas. O processo visa à tirar proveito da agilidade do Scrum, sem perder qualidade no desenvolvimento das aplicações. Foi desenvolvido tendo como base o processo Scrum, adicionado de tecnologias que apoiam a criação e utilização de artefatos na busca para integração com testes funcionais. O processo utiliza três disciplinas (Comunicação, Modelagem e Construção), cada uma refinando as Histórias do Usuário, que ocorrem em diferentes graus de abstração ao longo do desenvolvimento. Essas histórias devem ser um retrato mais fiel possível das necessidades do usuário e são utilizadas tanto no formato de cartões (Cartões de História), para a especificação de requisitos, quanto em um formato executável para orientar a implementação e trabalhar como testes funcionais. Mock-ups são utilizados para complementar os requisitos especificados nos cartões, auxiliando na tarefa de representar os requisitos. Esse conjunto é a base para a criação das Histórias do Usuário no formato executável. Outros artefatos de modelagem, como o Diagrama de Classes, também podem ser especificados, para elicitar os requisitos da aplicação. O Processo é apoiado por ferramentas desenvolvidas para possibilitar a integração de testes funcionais. Essas ferramentas definem uma linguagem para especificação de testes para escrever as Histórias do Usuário, criada como uma DLL para o Visual Studio, e um conversor dessas Histórias do Usuário para testes funcionais em código C#. Assim, o processo proposto estabelece uma maior integração dos testes durante o desenvolvimento e execução de cada disciplina, visando a produção de aplicações com maior qualidade. Para testar o processo, foram desenvolvidas aplicações do domínio de groupware na Web 2.0. A adoção desse domínio foi motivada pela ideia de explorar o desenvolvimento de software colaborativo que apoia o trabalho em grupo de pessoas envolvidas em tarefas comuns.