Agile modeling data warehouse development

Detalhes bibliográficos
Autor(a) principal: Couceiro, Frederico da Silva
Data de Publicação: 2012
Tipo de documento: Dissertação
Idioma: eng
Título da fonte: Repositório Científico de Acesso Aberto de Portugal (Repositórios Cientìficos)
Texto Completo: http://hdl.handle.net/10400.22/4463
Resumo: Most of the traditional software and database development approaches tend to be serial, not evolutionary and certainly not agile, especially on data-oriented aspects. Most of the more commonly used methodologies are strict, meaning they’re composed by several stages each with very specific associated tasks. A clear example is the Rational Unified Process (RUP), divided into Business Modeling, Requirements, Analysis & Design, Implementation, Testing and Deployment. But what happens when the needs of a well design and structured plan, meet the reality of a small starting company that aims to build an entire user experience solution. Here resource control and time productivity is vital, requirements are in constant change, and so is the product itself. In order to succeed in this environment a highly collaborative and evolutionary development approach is mandatory. The implications of constant changing requirements imply an iterative development process. Project focus is on Data Warehouse development and business modeling. This area is usually a tricky one. Business knowledge is part of the enterprise, how they work, their goals, what is relevant for analyses are internal business processes. Throughout this document it will be explained why Agile Modeling development was chosen. How an iterative and evolutionary methodology, allowed for reasonable planning and documentation while permitting development flexibility, from idea to product. More importantly how it was applied on the development of a Retail Focused Data Warehouse. A productized Data Warehouse built on the knowledge of not one but several client needs. One that aims not just to store usual business areas but create an innovative sets of business metrics by joining them with store environment analysis, converting Business Intelligence into Actionable Business Intelligence.
id RCAP_ad13cdd4b605411e1d5cfd8e7b8b57c7
oai_identifier_str oai:recipp.ipp.pt:10400.22/4463
network_acronym_str RCAP
network_name_str Repositório Científico de Acesso Aberto de Portugal (Repositórios Cientìficos)
repository_id_str 7160
spelling Agile modeling data warehouse developmentData warehouseAgileMethodologyModelingMetodologiaModelaçãoArmazém de dadosMost of the traditional software and database development approaches tend to be serial, not evolutionary and certainly not agile, especially on data-oriented aspects. Most of the more commonly used methodologies are strict, meaning they’re composed by several stages each with very specific associated tasks. A clear example is the Rational Unified Process (RUP), divided into Business Modeling, Requirements, Analysis & Design, Implementation, Testing and Deployment. But what happens when the needs of a well design and structured plan, meet the reality of a small starting company that aims to build an entire user experience solution. Here resource control and time productivity is vital, requirements are in constant change, and so is the product itself. In order to succeed in this environment a highly collaborative and evolutionary development approach is mandatory. The implications of constant changing requirements imply an iterative development process. Project focus is on Data Warehouse development and business modeling. This area is usually a tricky one. Business knowledge is part of the enterprise, how they work, their goals, what is relevant for analyses are internal business processes. Throughout this document it will be explained why Agile Modeling development was chosen. How an iterative and evolutionary methodology, allowed for reasonable planning and documentation while permitting development flexibility, from idea to product. More importantly how it was applied on the development of a Retail Focused Data Warehouse. A productized Data Warehouse built on the knowledge of not one but several client needs. One that aims not just to store usual business areas but create an innovative sets of business metrics by joining them with store environment analysis, converting Business Intelligence into Actionable Business Intelligence.Tradicionalmente as metodologias associadas ao desenvolvimento de software e base de Dados tendem a ser sequenciais, não evolutivas e definitivamente não ágeis. As metodologias mais comuns tendem a ser rígidas, geralmente compostas por diversas fases ou níveis, onde para cada um destes existe um conjunto muito específico de tarefas a executar de acordo com uma ordem própria. Um exemplo claro é o Rational Unified Process (RUP), dividido em Modelação de Negócio, Requisitos, Análise e Desenho, Implementação, Testes e Disponibilização. Mas como reagir quando as necessidades de um plano bem estruturado e desenhado se deparam com a realidade de uma empresa start-up com múltiplos projectos que pretende desenvolver um sistema de informação baseado em experiência de loja. Uma empresa com recursos limitados em que o retorno sobre a produtividade necessita de ser explorado ao máximo, algo que obriga a contínua procura de melhoria e subsequentemente a constante alteração de foco e requisitos. Neste ambiente a necessidade de um desenvolvimento altamente colaborativo e progressivo é obrigatório. A constante alteração de foco implica a necessidade de um desenvolvimento iterativo, capaz de rapidamente reagir às alterações. Neste contexto o foco do projecto recai sobre o desenvolvimento de um armazém de dados e modelação de processo de negócio. Esta área específica é particularmente complexa, pois o conhecimento é intrínseco ao negócio. Como se trabalha? Quais os objectivos? O que é relevante para análise? Tudo isto é parte integrante da empresa e como tal conhecimento difícil de transmitir. Ao longo do documento é pretendido explicar a razão pela escolha de uma metodologia Agile para o desenvolvimento. Como uma metodologia iterativa e gradual, permitiu desenvolvimento flexível com suficiente planeamento e documentação. Mais importante como foi aplicada de forma a desenvolver um Armazém de Dados com foco em Retalhe. Um capaz de responder as necessidades de vários clientes. Construído através do conhecimento de não um, mas múltiplos clientes através da análise dos seus requisitos. Este pretende armazenar não só a informação tradicionalmente associada a um Armazém de Dados de retalhe, mas sim juntar as áreas de um armazém de dados tradicional com informação recolhida do ambiente de loja. Desta forma criando um novo conjunto de métricas de negócio com o objectivo de melhorar o ambiente de loja de forma dinâmica.Instituto Politécnico do Porto. Instituto Superior de Engenharia do PortoOliveira, PauloRepositório Científico do Instituto Politécnico do PortoCouceiro, Frederico da Silva2014-06-03T14:08:32Z20122012-01-01T00:00:00Zinfo:eu-repo/semantics/publishedVersioninfo:eu-repo/semantics/masterThesisapplication/pdfhttp://hdl.handle.net/10400.22/4463enginfo:eu-repo/semantics/openAccessreponame:Repositório Científico de Acesso Aberto de Portugal (Repositórios Cientìficos)instname:Agência para a Sociedade do Conhecimento (UMIC) - FCT - Sociedade da Informaçãoinstacron:RCAAP2023-03-13T12:44:34Zoai:recipp.ipp.pt:10400.22/4463Portal AgregadorONGhttps://www.rcaap.pt/oai/openaireopendoar:71602024-03-19T17:25:19.149962Repositório Científico de Acesso Aberto de Portugal (Repositórios Cientìficos) - Agência para a Sociedade do Conhecimento (UMIC) - FCT - Sociedade da Informaçãofalse
dc.title.none.fl_str_mv Agile modeling data warehouse development
title Agile modeling data warehouse development
spellingShingle Agile modeling data warehouse development
Couceiro, Frederico da Silva
Data warehouse
Agile
Methodology
Modeling
Metodologia
Modelação
Armazém de dados
title_short Agile modeling data warehouse development
title_full Agile modeling data warehouse development
title_fullStr Agile modeling data warehouse development
title_full_unstemmed Agile modeling data warehouse development
title_sort Agile modeling data warehouse development
author Couceiro, Frederico da Silva
author_facet Couceiro, Frederico da Silva
author_role author
dc.contributor.none.fl_str_mv Oliveira, Paulo
Repositório Científico do Instituto Politécnico do Porto
dc.contributor.author.fl_str_mv Couceiro, Frederico da Silva
dc.subject.por.fl_str_mv Data warehouse
Agile
Methodology
Modeling
Metodologia
Modelação
Armazém de dados
topic Data warehouse
Agile
Methodology
Modeling
Metodologia
Modelação
Armazém de dados
description Most of the traditional software and database development approaches tend to be serial, not evolutionary and certainly not agile, especially on data-oriented aspects. Most of the more commonly used methodologies are strict, meaning they’re composed by several stages each with very specific associated tasks. A clear example is the Rational Unified Process (RUP), divided into Business Modeling, Requirements, Analysis & Design, Implementation, Testing and Deployment. But what happens when the needs of a well design and structured plan, meet the reality of a small starting company that aims to build an entire user experience solution. Here resource control and time productivity is vital, requirements are in constant change, and so is the product itself. In order to succeed in this environment a highly collaborative and evolutionary development approach is mandatory. The implications of constant changing requirements imply an iterative development process. Project focus is on Data Warehouse development and business modeling. This area is usually a tricky one. Business knowledge is part of the enterprise, how they work, their goals, what is relevant for analyses are internal business processes. Throughout this document it will be explained why Agile Modeling development was chosen. How an iterative and evolutionary methodology, allowed for reasonable planning and documentation while permitting development flexibility, from idea to product. More importantly how it was applied on the development of a Retail Focused Data Warehouse. A productized Data Warehouse built on the knowledge of not one but several client needs. One that aims not just to store usual business areas but create an innovative sets of business metrics by joining them with store environment analysis, converting Business Intelligence into Actionable Business Intelligence.
publishDate 2012
dc.date.none.fl_str_mv 2012
2012-01-01T00:00:00Z
2014-06-03T14:08:32Z
dc.type.status.fl_str_mv info:eu-repo/semantics/publishedVersion
dc.type.driver.fl_str_mv info:eu-repo/semantics/masterThesis
format masterThesis
status_str publishedVersion
dc.identifier.uri.fl_str_mv http://hdl.handle.net/10400.22/4463
url http://hdl.handle.net/10400.22/4463
dc.language.iso.fl_str_mv eng
language eng
dc.rights.driver.fl_str_mv info:eu-repo/semantics/openAccess
eu_rights_str_mv openAccess
dc.format.none.fl_str_mv application/pdf
dc.publisher.none.fl_str_mv Instituto Politécnico do Porto. Instituto Superior de Engenharia do Porto
publisher.none.fl_str_mv Instituto Politécnico do Porto. Instituto Superior de Engenharia do Porto
dc.source.none.fl_str_mv reponame:Repositório Científico de Acesso Aberto de Portugal (Repositórios Cientìficos)
instname:Agência para a Sociedade do Conhecimento (UMIC) - FCT - Sociedade da Informação
instacron:RCAAP
instname_str Agência para a Sociedade do Conhecimento (UMIC) - FCT - Sociedade da Informação
instacron_str RCAAP
institution RCAAP
reponame_str Repositório Científico de Acesso Aberto de Portugal (Repositórios Cientìficos)
collection Repositório Científico de Acesso Aberto de Portugal (Repositórios Cientìficos)
repository.name.fl_str_mv Repositório Científico de Acesso Aberto de Portugal (Repositórios Cientìficos) - Agência para a Sociedade do Conhecimento (UMIC) - FCT - Sociedade da Informação
repository.mail.fl_str_mv
_version_ 1799131346573983744