This thesis emphasizes on surveying the state-of-the-art in software requirements specification with a focus on, autonomic, self-adapting software systems. Since various requirements are brought forward accord with environments, modeling requirements for adaptive software systems may be changed at run-time. Nowadays, Keep All Objectives Satisfied (KAOS) is an effective method to build goal model. Various manipulations, such as change, remove, active and de-active goals, appear new goals, could mediate conflicts among goals in adaptive software system. At specification time, specifications of event sequences to be monitored are generated from requirements specification.

Submitted by Fabio Sobreira Campos da Costa (fabio.sobreira@ufpe.br) on 2017-02-21T16:58:53Z No. of bitstreams: 2 license_rdf: 1232 bytes, checksum: 66e71c371cc565284e70f40736c94386 (MD5) Dissertação_SilviaVersaoFinal.pdf: 3562807 bytes, checksum: d273ad6c061161f899cab3d232a82a79 (MD5) / Made available in DSpace on 2017-02-21T16:58:54Z (GMT). No. of bitstreams: 2 license_rdf: 1232 bytes, checksum: 66e71c371cc565284e70f40736c94386 (MD5) Dissertação_SilviaVersaoFinal.pdf: 3562807 bytes, checksum: d273ad6c061161f899cab3d232a82a79 (MD5) Previous issue date: 2016-08-01 / FACEPE / Contexto: A fase de especificação de requisitos é fundamental no processo de desenvolvimento de software. O uso de cenários é bastante popular para especificar requisitos, por serem descritos em linguagem natural. No entanto, a linguagem natural dá margem a requisitos ambíguos, incompletos e inconsistentes, o que vai de encontro com os objetivos da fase de especificação de requisitos. Nesse sentido, uma técnica baseada em Cenário & LEL (Language Extended Lexicon), chamada de C&L, pode ser a solução adequada, pois LEL é um glossário que define um conjunto de palavras que pertencem a um domínio e que devem ser usadas para descrever os cenários. Assim, C&L é considerada uma técnica de cenários baseada em linguagem natural controlada que ajuda a minimizar os problemas previamente mencionados, além de poder ser utilizada para criar casos de teste de forma mais sistemática. Objetivo: Neste trabalho, são propostas duas abordagens: a primeira abordagem usa regras de mapeamento para derivar modelos statechart a partir de C&L visando verificar a completude e consistência desses cenários e a segunda usa heurísticas para obter sistematicamente casos de teste a partir de modelos statechart. Método: A pesquisa apresentada nessa dissertação seguiu a abordagem de Engenharia para definir as regras de mapeamento e as heurísticas que, por sua vez, foram avaliadas empiricamente. Resultados: As regras de mapeamento apoiam a derivação de statechart a partir de C&L. As heurísticas apoiam a derivação de casos de teste a partir dos modelos statechart. Foi realizado um experimento para comparar o número de erros de incompletude e inconsistência detectados pelos grupos experimental e controle e o tempo gasto pelos grupos para detectar esses erros. Também foi verificado se os statecharts gerados através da aplicação das regras de mapeamento possuem grau de corretude e semelhança. Foi realizada uma avaliação qualitativa das heurísticas utilizadas para derivar os casos de teste, com o intuito de saber se as heurísticas foram utilizadas corretamente, se estão claras e são fáceis de usar. Conclusões: Os resultados do experimento mostram que o número de erros de incompletude detectados pelo grupo experimental foi superior ao número obtido pelo grupo controle e em relação aos erros de inconsistência não houve diferença entre quantidade de erros detectados pelos dois grupos. Além disso, a média do tempo gasto para identificar erros de incompletude e inconsistência pelo grupo experimental foi ligeiramente superior a média do tempo gasto pelo grupo controle. Em relação ao grau de corretude, dentre os modelos gerados pelo grupo experimental, existe um que apresenta o maior grau de corretude com 85,7%. No entanto, o grau de semelhança entre os modelos é considerado de “baixa semelhança”. O resultado da avaliação qualitativa mostrou que os participantes concordaram que as regras de mapeamento e as heurísticas são compreensíveis e fáceis de utilizar. Também foi observado que as heurísticas foram usadas de maneira correta na derivação dos casos de teste. / Context: The requirements specification phase is fundamental in the software development process. The use of scenarios is quite popular to specify requirements because they are described in natural language. However, natural language gives rise to ambiguous, incomplete and inconsistent requirements, jeopardizes the objectives of the requirements specification phase. In this context, a technique based on Scenarios and LEL (Language Extended Lexicon), called C&L, may be an appropriate solution because LEL is a glossary that defines a set of words that belong to a domain and should be used to describe the scenarios. Thus, C&L is a scenario technique based on controlled natural language that helps to minimize the problems previously mentioned, and can be used to create test cases in a more systematic way. Objective: In this study, two approaches are proposed: the first approach uses mapping rules to derive statechart models from C & L in order to verify the completeness and consistency of these scenarios and the second uses heuristics to systematically derive test cases from statechart models. Method: The research presented in this work follows the engineering approach to define the mapping rules and heuristics that, in turn, were empirically evaluated. Results: Mapping rules support the derivation of statechart from C & L. Heuristics support the derivation of test cases from statechart models. An experiment was conducted to compare the number of incompleteness and inconsistency errors detected by the experimental and control the groups and the time spent by groups to detect these errors. Also it was verified whether the statecharts generated by the application of the mapping rules have degree of correctness and likeness. A qualitative evaluation of the heuristics used to derive the test cases was made, in order to know whether the heuristics were correctly used and if they are clear and easy to use. Conclusions: The results of the experiment show that the number of incompleteness errors detected by the experimental group was higher than the number obtained by the control group, and in relation to inconsistency errors, there was no difference among the number of errors detected by the two groups. Furthermore, the average time spent to identify incompleteness and inconsistency errors by the experimental group was slightly higher than the average time spent by the control group. In relation to the degree of correctness among the models generated by the experimental group, there is one that has the highest degree of correctness with 85.7%. However, the degree of similarity between the models is considered "low similarity”. The result of the qualitative evaluation showed that the participants agreed that the mapping rules and heuristics are comprehensible and easy to use. It was also observed that the heuristics were used correctly in the derivation of test cases.

Made available in DSpace on 2014-07-29T14:57:52Z (GMT). No. of bitstreams: 1 Diss LuNishi.pdf: 535052 bytes, checksum: 312e4f56b2249ade58df12ebfe2b4dcb (MD5) Previous issue date: 2009-09-16 / This work uses mind maps to describe requirements and investigates this not well known application through an experiment. The experiment was based on desirable features sought by requirements engineers in notations and functions offered by tools. Both provided input to small changes in mind maps before a real specification was produced for the experiment. The results show that mind maps should be considered seriously as an alternative notation to describe software requirements / Este trabalho investiga o uso de mapas mentais na engenharia de requisitos, com destaque para o registro de requisitos. Características e funcionalidades desejáveis por engenheiros de requisitos foram coletadas e motivaram adaptações nos mapas mentais para uso neste domínio. Um experimento empregou a notação alterada e forneceu indícios positivos e negativos. O experimento permite, contudo, considerar o uso de mapas mentais como uma alternativa viável para o registro de requisitos e merecedora de pesquisas posteriores

Since the first lines of code were introduced in the automotive domain, vehicles have transitioned from being predominantly mechanical systems to software intensive systems. With the ever-increasing computational power and memory of vehicular embedded systems, a set of new, more powerful and more complex software functions are installed into vehicles to realize core functionalities. This trend impacts all phases of the system development including requirements specification, design and architecture of the system, as well as the integration and testing phases. In such settings, creating and managing different artifacts during the system development process by using traditional, human-intensive techniques becomes increasingly difficult. One problem stems from the high number and intricacy of system requirements that combine functional and possibly timing or other types of constraints. Another problem is related to the fact that industrial development relies on models, e.g. developed in Simulink, from which code may be generated, so the correctness of such models needs to be ensured. A potential way to address of the mentioned problems is by applying computer-aided specification, analysis and verification techniques already at the requirements stage, but also further at later development stages. Despite the high degree of automation, exhaustiveness and rigor of formal specification and analysis techniques, their integration with industrial practice remains a challenge. To address this challenge, in this thesis, we develop the foundation of a framework, tailored for industrial adoption, for formal specification and analysis of system requirements specifications and behavioral system models. First, we study the expressiveness of existing pattern-based techniques for creating formal requirements specifications, on a relevant industrial case study. Next, in order to enable practitioners to create formal system specification by using pattern-based techniques, we propose a tool called SeSAMM Specifier. Further, we provide an automated Satisfiability Modulo Theories (SMT)-based consistency analysis approach for the formally encoded system requirements specifications. The proposed SMT-based approach is suitable for early phases of the development for debugging the specifications. For the formal analysis of behavioral models, we provide an approach for statistical model checking of Simulink models by using the UPPAAL SMC tool. To facilitate the adoption of the approach, we provide the SIMPPAAL tool that automates procedure of generating network of stochastic timed automata for a given Simulink model. For validation, we apply our approach on a complex industrial model, namely the Brake-by-Wire function from Volvo GTT. / VeriSpec

I en rapport från 2005 framtagen av FoU-Väst i samverkan med Centrum för management i byggsektorn (CMB) konstateras att en betydande del av allt slöseri i byggsektorn är kopplat till fel och konsekvenserna av dessa, med andra ord felkostnader. Studien visar att felkostnader står för cirka 10 % av ett projekts produktionskostnad.   Byggsektorn står nu, år 2012, inför förändringar i sitt arbetssätt för att minska antalet fel, öka kvaliteten och effektiviteten. BIM – Building Information Modeling, möjliggör ett smartare sätt att skapa, använda och förvalta information genom hela bygg- och förvaltningsprocessen. BIM ger möjligheten att anpassa informationen i varje delprocess och därigenom effektivisera arbetet. Det nya arbetssättet innebär ett livscykeltänk där information används på ett systematiskt och kvalitetssäkrat sätt i en objektbaserad 3D-modell.  Studiens syfte är att fastställa vilka arbetssätt som behöver förändras för att implementera BIM i ett av Skanskas distrikt i regionen Hus Stockholm Ombyggnad samt fastställa vilka kostnadsbesparingar beställare gör tack vare implementeringen. BIM består av mer än en datamodell. För att uppnå de nyttor BIM kan ge krävs förändrade processer och gemensamma begreppsmodeller. Processerna, organisationen och modelleringen av produkten måste planeras noggrant. Detta medför att mer resurser läggs i ett tidigt skede i projekteringen vilket krävs för att kravspecifikationen ska uppfyllas i ett BIM-projekt. Flera respondenter i studien ger uttryck för att fler och/eller utförligare informationsleveranser i systemskedet skulle höja kvaliteten på bygghandlingarna. Studien konstaterar att BIM-projektering kräver ett nära och öppet samarbete mellan, de för BIM-användingen aktuella aktörerna. / In a 2005 report written by FoU-Väst in collaboration with Centrum för management i byggsektorn (CMB) it is determined that a significant proportion of wastage in the construction sector is linked to defects and their impact, in other words costs of errors. The study shows that these costs are accounting for about 10 % of a project´s production costs.  Construction sector now, in 2012, face changes in their ways of working to reduce errors, increase quality and efficiency. BIM - Building Information Modeling, provides a smarter way to create, use and manage information throughout the construction and management process. BIM provides the ability to customize the information in each sub- process and thereby improve efficiency. The new ways of working involves a life- cycle thinking in which information is used in a systematic and quality assured manner in an object-based 3D model.  The study aims to determine the ways of working that needs to change to implement BIM in one of Skanska's district in the region Stockholm Hus Ombyggnad and identify cost savings clients make through the implementation. BIM consists of more than one data model. To achieve the benefits that BIM can provide, changes in processes and common conceptual models are required. Processes, the organization and modeling of the product must be carefully planned. This means that more resources are added in the early stages of the design process which is necessary to meet the specification of requirements in a BIM project. A number of respondents in the study reflect on the fact that additional and / or more detailed information deliveries during the schematic design phase would increase the quality of construction documents. The study finds that a BIM design process require near and open cooperation between the, to the BIM-use relevant participants.

A Modelagem Orientada a Objetos (MOO) é o processo de construção de modelos de sistemas através da identificação e definição de um conjunto de objetos relacionados, que comportam-se e colaboram entre si conforme os requisitos estabelecidos para o sistema. Esta definição inclui os três aspectos ortogonais, ou dimensões, deste tipo de modelagem: a dimensão estrutural dos objetos, a dimensão dinâmica do comportamento e a dimensão funcional dos requisitos. Conforme a importância relativa dada a cada uma destas dimensões, podem ser definidas três estratégias possíveis para conduzir a MOO. Estas estratégias são as dirigidas por dados, por comportamento e por processos. A estratégia dirigida por processos já esta superada. Atualmente, a estratégia dirigida por dados domina na maioria das técnicas de MOO. A estratégia dirigida por comportamento propõe que a estrutura dos objetos em um sistema pode ser determinada a partir do comportamento externo e interno que o sistema deve apresentar. Esta idéia é interessante, porque permite introduzir tardiamente o encapsulamento na MOO. Conforme é argumentado neste trabalho, as vantagens atribuídas a orientação a objetos são de implementação, isto é, a decisão de orientar ou não a objetos é, na realidade, uma decisão de design. Ao introduzir o encapsulamento na modelagem inicial do sistema, ganha-se o benefício da continuidade estrutural ao custo de colocar a MOO mais perto do design. Neste contexto, este trabalho apresenta um processo de modelagem conceitual de sistemas do ponto de vista comportamental que introduz tardiamente o encapsulamento da orientação a objetos como primeiro passo de design. Em outras palavras, é proposta uma técnica de modelagem sob uma estratégia dirigida por comportamento (privilegiando, assim, o aspecto dinâmico dos sistemas) com o suficiente poder de expressão para, ao mesmo tempo, permitir a modelagem de sistemas de informação no nível conceitual e derivar dos modelos dinâmicos obtidos uma representação estrutural orientada a objetos. 0 sistema, na concepção desta proposta, é composto por um conjunto de processos concorrentes, cada um dos quais recebe um estimulo do ambiente, realiza um tratamento especifico sobre ele e gera para o ambiente uma resposta. Os estímulos externos são decompostos em conjuntos de eventos concorrentes tratados no interior do processo. As ações realizadas no interior do mesmo são compostas nas respostas geradas para o exterior. Os processos são modelados comportamentalmente, utilizando o formalismo proposto High-Level Statecharts (HLS). HLS é uma extensão dos statecharts de Harel. As principais extensões propostas são a introdução de estados "parametrizados" usando variáveis e a representação genérica de conjuntos de estados concorrentes e exclusivos. 0 modelo de processos e desintegrado em unidades de comportamento que tratam das mesmas variáveis. Estas unidades são integradas em um modelo de ciclos de vida para estas variáveis. Finalmente, apos a aplicação da técnica de modelagem conceitual, e obtido um modelo estrutural orientado a objetos. Este modelo e derivado utilizando unicamente informações contidas nos modelos dinâmicos gerados no processo da técnica proposta. No modelo estrutural são identificadas classes, objetos, atributos, associações estáticas, hierarquias de herança e operações. Todo o processo e exemplificado utilizando o problema padrão de preparação de congressos da IFIP. / Object-Oriented Modeling (OOM) is the process of construction of systems models, through an identification and definition of a set of relating objects. These objects have a collaborative behavior according to the system requirements previously defined. This definition includes three modeling aspects or dimensions: object structural dimension, behavior dynamic dimension and requirements functional dimension. Depending on a relative importance of each dimension, three possible strategies to drive OOM are defined. The strategies are: data-driven, behavior-driven and process-driven. Process-driven strategy is obsolete. Nowadays, data-driven is the dominant strategy in the world of OOM techniques. Behavior-driven strategy suggests both internal and external system behaviors define its object structure. This idea is attractive because it allows a late encapsulation in the OOM. As explained in this work, the main advantage to use object-orientation is for implementation. So, to object-orient or not to object-orient is a design decision. If encapsulation is introduced in the very beginning of systems modeling, the structural continuity is achieved at the cost of pulling OOM closer to design. In this context, the work presents a process of systems conceptual modeling using a behavioral point of view. This process introduces object-oriented encapsulation lately as a first step in the design phase. In other words, this work is a proposal of a modeling technique under a behavior-driven strategy (focusing the dynamic aspect of the systems) with enough expression power to model information systems at conceptual level and, at the same time, to derive of an object-oriented structural representation from the dynamic models. As conceived in the proposal, a system is composed by a set of concurrent processes. Each process receives a stimuli from the environment, makes a specific treatment on it and generates a response to the environment. The external stimuli is decomposed into a set of concurrent events which are internally handled by the process. Actions internally performed by the process are composed into a response which is sent outside the process. Processes are behaviorally modeled using a proposed formalism called High-Level Statecharts (HLS). HLS is a extension of Harel's statecharts. The main extensions proposed are parameterized states using variables and generic representation of concurrent and exclusive sets of states. Process model is disintegrated into behavior units handling the same variables. The units are integrated into a life cycle model for these variables. Finally, after the modeling technique has been applied, an object-oriented structural model is obtained. This model is derived exclusively using information from the dynamic models constructed during the modeling process. Classes, objects, attributes, static associations, inheritance hierarchies and operations in the structural model are identified. Examples used in all the modeling process are taken from the standard problem of IFIP conference.

A Modelagem Orientada a Objetos (MOO) é o processo de construção de modelos de sistemas através da identificação e definição de um conjunto de objetos relacionados, que comportam-se e colaboram entre si conforme os requisitos estabelecidos para o sistema. Esta definição inclui os três aspectos ortogonais, ou dimensões, deste tipo de modelagem: a dimensão estrutural dos objetos, a dimensão dinâmica do comportamento e a dimensão funcional dos requisitos. Conforme a importância relativa dada a cada uma destas dimensões, podem ser definidas três estratégias possíveis para conduzir a MOO. Estas estratégias são as dirigidas por dados, por comportamento e por processos. A estratégia dirigida por processos já esta superada. Atualmente, a estratégia dirigida por dados domina na maioria das técnicas de MOO. A estratégia dirigida por comportamento propõe que a estrutura dos objetos em um sistema pode ser determinada a partir do comportamento externo e interno que o sistema deve apresentar. Esta idéia é interessante, porque permite introduzir tardiamente o encapsulamento na MOO. Conforme é argumentado neste trabalho, as vantagens atribuídas a orientação a objetos são de implementação, isto é, a decisão de orientar ou não a objetos é, na realidade, uma decisão de design. Ao introduzir o encapsulamento na modelagem inicial do sistema, ganha-se o benefício da continuidade estrutural ao custo de colocar a MOO mais perto do design. Neste contexto, este trabalho apresenta um processo de modelagem conceitual de sistemas do ponto de vista comportamental que introduz tardiamente o encapsulamento da orientação a objetos como primeiro passo de design. Em outras palavras, é proposta uma técnica de modelagem sob uma estratégia dirigida por comportamento (privilegiando, assim, o aspecto dinâmico dos sistemas) com o suficiente poder de expressão para, ao mesmo tempo, permitir a modelagem de sistemas de informação no nível conceitual e derivar dos modelos dinâmicos obtidos uma representação estrutural orientada a objetos. 0 sistema, na concepção desta proposta, é composto por um conjunto de processos concorrentes, cada um dos quais recebe um estimulo do ambiente, realiza um tratamento especifico sobre ele e gera para o ambiente uma resposta. Os estímulos externos são decompostos em conjuntos de eventos concorrentes tratados no interior do processo. As ações realizadas no interior do mesmo são compostas nas respostas geradas para o exterior. Os processos são modelados comportamentalmente, utilizando o formalismo proposto High-Level Statecharts (HLS). HLS é uma extensão dos statecharts de Harel. As principais extensões propostas são a introdução de estados "parametrizados" usando variáveis e a representação genérica de conjuntos de estados concorrentes e exclusivos. 0 modelo de processos e desintegrado em unidades de comportamento que tratam das mesmas variáveis. Estas unidades são integradas em um modelo de ciclos de vida para estas variáveis. Finalmente, apos a aplicação da técnica de modelagem conceitual, e obtido um modelo estrutural orientado a objetos. Este modelo e derivado utilizando unicamente informações contidas nos modelos dinâmicos gerados no processo da técnica proposta. No modelo estrutural são identificadas classes, objetos, atributos, associações estáticas, hierarquias de herança e operações. Todo o processo e exemplificado utilizando o problema padrão de preparação de congressos da IFIP. / Object-Oriented Modeling (OOM) is the process of construction of systems models, through an identification and definition of a set of relating objects. These objects have a collaborative behavior according to the system requirements previously defined. This definition includes three modeling aspects or dimensions: object structural dimension, behavior dynamic dimension and requirements functional dimension. Depending on a relative importance of each dimension, three possible strategies to drive OOM are defined. The strategies are: data-driven, behavior-driven and process-driven. Process-driven strategy is obsolete. Nowadays, data-driven is the dominant strategy in the world of OOM techniques. Behavior-driven strategy suggests both internal and external system behaviors define its object structure. This idea is attractive because it allows a late encapsulation in the OOM. As explained in this work, the main advantage to use object-orientation is for implementation. So, to object-orient or not to object-orient is a design decision. If encapsulation is introduced in the very beginning of systems modeling, the structural continuity is achieved at the cost of pulling OOM closer to design. In this context, the work presents a process of systems conceptual modeling using a behavioral point of view. This process introduces object-oriented encapsulation lately as a first step in the design phase. In other words, this work is a proposal of a modeling technique under a behavior-driven strategy (focusing the dynamic aspect of the systems) with enough expression power to model information systems at conceptual level and, at the same time, to derive of an object-oriented structural representation from the dynamic models. As conceived in the proposal, a system is composed by a set of concurrent processes. Each process receives a stimuli from the environment, makes a specific treatment on it and generates a response to the environment. The external stimuli is decomposed into a set of concurrent events which are internally handled by the process. Actions internally performed by the process are composed into a response which is sent outside the process. Processes are behaviorally modeled using a proposed formalism called High-Level Statecharts (HLS). HLS is a extension of Harel's statecharts. The main extensions proposed are parameterized states using variables and generic representation of concurrent and exclusive sets of states. Process model is disintegrated into behavior units handling the same variables. The units are integrated into a life cycle model for these variables. Finally, after the modeling technique has been applied, an object-oriented structural model is obtained. This model is derived exclusively using information from the dynamic models constructed during the modeling process. Classes, objects, attributes, static associations, inheritance hierarchies and operations in the structural model are identified. Examples used in all the modeling process are taken from the standard problem of IFIP conference.

A Modelagem Orientada a Objetos (MOO) é o processo de construção de modelos de sistemas através da identificação e definição de um conjunto de objetos relacionados, que comportam-se e colaboram entre si conforme os requisitos estabelecidos para o sistema. Esta definição inclui os três aspectos ortogonais, ou dimensões, deste tipo de modelagem: a dimensão estrutural dos objetos, a dimensão dinâmica do comportamento e a dimensão funcional dos requisitos. Conforme a importância relativa dada a cada uma destas dimensões, podem ser definidas três estratégias possíveis para conduzir a MOO. Estas estratégias são as dirigidas por dados, por comportamento e por processos. A estratégia dirigida por processos já esta superada. Atualmente, a estratégia dirigida por dados domina na maioria das técnicas de MOO. A estratégia dirigida por comportamento propõe que a estrutura dos objetos em um sistema pode ser determinada a partir do comportamento externo e interno que o sistema deve apresentar. Esta idéia é interessante, porque permite introduzir tardiamente o encapsulamento na MOO. Conforme é argumentado neste trabalho, as vantagens atribuídas a orientação a objetos são de implementação, isto é, a decisão de orientar ou não a objetos é, na realidade, uma decisão de design. Ao introduzir o encapsulamento na modelagem inicial do sistema, ganha-se o benefício da continuidade estrutural ao custo de colocar a MOO mais perto do design. Neste contexto, este trabalho apresenta um processo de modelagem conceitual de sistemas do ponto de vista comportamental que introduz tardiamente o encapsulamento da orientação a objetos como primeiro passo de design. Em outras palavras, é proposta uma técnica de modelagem sob uma estratégia dirigida por comportamento (privilegiando, assim, o aspecto dinâmico dos sistemas) com o suficiente poder de expressão para, ao mesmo tempo, permitir a modelagem de sistemas de informação no nível conceitual e derivar dos modelos dinâmicos obtidos uma representação estrutural orientada a objetos. 0 sistema, na concepção desta proposta, é composto por um conjunto de processos concorrentes, cada um dos quais recebe um estimulo do ambiente, realiza um tratamento especifico sobre ele e gera para o ambiente uma resposta. Os estímulos externos são decompostos em conjuntos de eventos concorrentes tratados no interior do processo. As ações realizadas no interior do mesmo são compostas nas respostas geradas para o exterior. Os processos são modelados comportamentalmente, utilizando o formalismo proposto High-Level Statecharts (HLS). HLS é uma extensão dos statecharts de Harel. As principais extensões propostas são a introdução de estados "parametrizados" usando variáveis e a representação genérica de conjuntos de estados concorrentes e exclusivos. 0 modelo de processos e desintegrado em unidades de comportamento que tratam das mesmas variáveis. Estas unidades são integradas em um modelo de ciclos de vida para estas variáveis. Finalmente, apos a aplicação da técnica de modelagem conceitual, e obtido um modelo estrutural orientado a objetos. Este modelo e derivado utilizando unicamente informações contidas nos modelos dinâmicos gerados no processo da técnica proposta. No modelo estrutural são identificadas classes, objetos, atributos, associações estáticas, hierarquias de herança e operações. Todo o processo e exemplificado utilizando o problema padrão de preparação de congressos da IFIP. / Object-Oriented Modeling (OOM) is the process of construction of systems models, through an identification and definition of a set of relating objects. These objects have a collaborative behavior according to the system requirements previously defined. This definition includes three modeling aspects or dimensions: object structural dimension, behavior dynamic dimension and requirements functional dimension. Depending on a relative importance of each dimension, three possible strategies to drive OOM are defined. The strategies are: data-driven, behavior-driven and process-driven. Process-driven strategy is obsolete. Nowadays, data-driven is the dominant strategy in the world of OOM techniques. Behavior-driven strategy suggests both internal and external system behaviors define its object structure. This idea is attractive because it allows a late encapsulation in the OOM. As explained in this work, the main advantage to use object-orientation is for implementation. So, to object-orient or not to object-orient is a design decision. If encapsulation is introduced in the very beginning of systems modeling, the structural continuity is achieved at the cost of pulling OOM closer to design. In this context, the work presents a process of systems conceptual modeling using a behavioral point of view. This process introduces object-oriented encapsulation lately as a first step in the design phase. In other words, this work is a proposal of a modeling technique under a behavior-driven strategy (focusing the dynamic aspect of the systems) with enough expression power to model information systems at conceptual level and, at the same time, to derive of an object-oriented structural representation from the dynamic models. As conceived in the proposal, a system is composed by a set of concurrent processes. Each process receives a stimuli from the environment, makes a specific treatment on it and generates a response to the environment. The external stimuli is decomposed into a set of concurrent events which are internally handled by the process. Actions internally performed by the process are composed into a response which is sent outside the process. Processes are behaviorally modeled using a proposed formalism called High-Level Statecharts (HLS). HLS is a extension of Harel's statecharts. The main extensions proposed are parameterized states using variables and generic representation of concurrent and exclusive sets of states. Process model is disintegrated into behavior units handling the same variables. The units are integrated into a life cycle model for these variables. Finally, after the modeling technique has been applied, an object-oriented structural model is obtained. This model is derived exclusively using information from the dynamic models constructed during the modeling process. Classes, objects, attributes, static associations, inheritance hierarchies and operations in the structural model are identified. Examples used in all the modeling process are taken from the standard problem of IFIP conference.

<p>Det finns olika strategier och många olika metoder inom strategierna för att tidsuppskatta ett IT-projekt. Dessa strategier och metoder skiljer sig mer eller mindre åt och många gånger har företag egna metoder för tidsuppskattning. Dessa strategier och metoder har samma syfte, vilket är att göra så noggranna tidsuppskattningar som möjligt för att undvika försenade projekt. Examensarbetets syfte är att visa på hur LexiConsult AB kan förbättra sina tidsuppskattningar av inkommande IT-projekt genom att följa studiens rekommendationer, vilket leder till bättre tidsuppskattningar och nöjdare kunder. Undersökningen har utförts genom en litteraturstudie, där genomgång av de olika delarna inom IT-projekt skett. Det teoretiska kapitlet ligger senare till grund för den empiriska undersökning som utförts på företaget vilket ger insikt och perspektiv i hur företaget arbetar med sina projekt. Teorin visade att en bra tidsuppskattningsmetod inkluderar alla delarna i ett projekt och att dessa måste genomgås innan en bra tidsuppskattningsmetod kan tas fram.</p><p>Det komplexa ämnet tidsuppskattning har gjort att en deduktiv ansats har valts för arbetet, där utgångspunkten ligger i teorin. Den djupa teorigenomgång som har utförts av författarna avspeglar sig i den kvalitativa forskningsmetod som valts för studien där syftet med metoden är att få djupare kunskap genom analyser och tolkningar i teori och verklighet. Författarna har försöktsäkerställa examensarbetets kvalité genom att beakta det insamlade materialets validitet, reliabilitet och relevans.</p><p>De analyser som genomförs i arbetet där LexiConsults arbetssätt analyseras mot den teori som har genomgåtts leder till ett flertal rekommendationer i slutsatsen av arbetet. Företagets brister i informationsstruktur leder till rekommendationer om införandet av en databas med kategorier av de projekt företaget utför. Vikten av bra kravspecifikationer inom tidsuppskattning leder i slutsatsen till en förbättrad kravspecifikation med uppdelning av de olika faserna i projektet med tidsuppskattning och kommentarer på varje del. Vikten av bra uppföljning av projekt framhävs och rekommendationer ges till en uppföljningsmall, vilket resulterar i designen till en sådan. Företagets arbetsmetoder och historik tas tillvara och en analogisk tidsuppskattningsmetod rekommenderas för framtida projekts tidsuppskattningar. Den analogiska metodens nackdelar förbättras genom tillämpandet av den nya kravspecifikationen där projekt delas i olika faser och tidsuppskattas separat enligt mikrostrategin inom tidsuppskattningar. Uppföljningsdokumentet samt den nya kravspecifikationen och den nya informationsstrukturen kommer enligt studiens slutsats att leda till flera positiva förändringar inom företaget. De nya förändringarna tillför större ansvar för den enskilde i projekt, bättre kunskapsdelning i företaget där erfarenhetsmässig kunskap kommer att ligga till grund för nya tidsuppskattningar, bättre beslutsunderlag för konsultchef samt för kund att lättare följa upp företagets tidsuppskattningar och hitta svagheter.Det finns olika strategier och många olika metoder inom strategierna för att tidsuppskatta ett IT-projekt. Dessa strategier och metoder skiljer sig mer eller mindre åt och många gånger har företag egna metoder för tidsuppskattning. Dessa strategier och metoder har samma syfte, vilket är att göra så noggranna tidsuppskattningar som möjligt för att undvika försenade projekt.</p><p>Examensarbetets syfte är att visa på hur LexiConsult AB kan förbättra sina tidsuppskattningar av inkommande IT-projekt genom att följa studiens rekommendationer, vilket leder till bättre tidsuppskattningar och nöjdare kunder. Undersökningen har utförts genom en litteraturstudie, där genomgång av de olika delarna inom IT-projekt skett. Det teoretiska kapitlet ligger senare till grund för den empiriska undersökning som utförts på företaget vilket ger insikt och perspektiv i hur företaget arbetar med sina projekt. Teorin visade att en bra tidsuppskattningsmetod inkluderar alla delarna i ett projekt och att dessa måste genomgås innan en bra tidsuppskattningsmetod kan tas fram.Det komplexa ämnet tidsuppskattning har gjort att en deduktiv ansats har valts för arbetet, där utgångspunkten ligger i teorin. Den djupa teorigenomgång som har utförts av författarna avspeglar sig i den kvalitativa forskningsmetod som valts för studien där syftet med metoden är att få djupare kunskap genom analyser och tolkningar i teori och verklighet. Författarna har försöktsäkerställa examensarbetets kvalité genom att beakta det insamlade materialets validitet, reliabilitet och relevans.De analyser som genomförs i arbetet där LexiConsults arbetssätt analyseras mot den teori som har genomgåtts leder till ett flertal rekommendationer i slutsatsen av arbetet. Företagets brister i informationsstruktur leder till rekommendationer om införandet av en databas med kategorier av de projekt företaget utför. Vikten av bra kravspecifikationer inom tidsuppskattning leder i slutsatsen till en förbättrad kravspecifikation med uppdelning av de olika faserna i projektet med tidsuppskattning och kommentarer på varje del. Vikten av bra uppföljning av projekt framhävs och rekommendationer ges till en uppföljningsmall, vilket resulterar i designen till en sådan. Företagets arbetsmetoder och historik tas tillvara och en analogisk tidsuppskattningsmetod rekommenderas för framtida projekts tidsuppskattningar. Den analogiska metodens nackdelar förbättras genom tillämpandet av den nya kravspecifikationen där projekt delas i olika faser och tidsuppskattas separat enligt mikrostrategin inom tidsuppskattningar. Uppföljningsdokumentet samt den nya kravspecifikationen och den nya informationsstrukturen kommer enligt studiens slutsats att leda till flera positiva förändringar inom företaget. De nya förändringarna tillför större ansvar för den enskilde i projekt, bättre kunskapsdelning i företaget där erfarenhetsmässig kunskap kommer att ligga till grund för nya tidsuppskattningar, bättre beslutsunderlag för konsultchef samt för kund att lättare följa upp företagets tidsuppskattningar och hitta svagheter.</p> / <p>There are many different strategies and different approaches within the strategies to estimate the time of an IT project. These methods and practices differ in several aspects and many times companies have developed their own method for estimating time. The common factors for these strategies and methods are the objectives, which is to make time estimation as accurate as possible, to avoid delays in projects. This study aims to show how LexiConsult AB can improve it’s time estimations by following the recommendations made in this study, which leads to reduction in their time estimates and better customer satisfaction. The study was conducted through a literature review of where the various components of IT projects are reviewed. The theoretical analysis is later the subject of the empirical investigation in the company giving instinct and perspective into how the company is working on their projects. The theory showed that a good time estimation method includes all the elements of a project and these must be examined before a good time estimation method can be developed.</p><p>Because of the complexity of this topic, a deductive approach was chosen for the study, where the starting point lies in the theory. The deep theory examination conducted by the authors is reflected in the qualitative research method chosen for study where the purpose of the method is to gain deeper knowledge through analysis and interpretation of the theory and reality.The authors have tried to ensure the quality of work by considering the collected material's validity, reliability and relevance.Because of the complexity of this topic, a deductive approach was chosen for the study, where the starting point lies in the theory. The deep theory examination conducted by the authors is reflected in the qualitative research method chosen for study where the purpose of the method is to gain deeper knowledge through analysis and interpretation of the theory and reality.The authors have tried to ensure the quality of work by considering the collected material's validity, reliability and relevance.</p><p>The analysis conducted in the study, is LexiConsult's project methods which are compared against the theory. These comparisons led to a number of recommendations in the conclusion of the study. The company's shortcomings in information structure area are identified and leads to recommendations on the establishment of a database with project categories. The importance of good requirements specifications for time estimation is identified and in the conclusion an improved specification is shown. The new specification has separated phases of the project with time estimates and comments on each part. The importance of good monitoring of the projects is highlighted in the study and recommendations are given to follow a template, resulting in the design of one. The company's working methods and use of the experience is indicative, and an analogy time estimation method is recommended for future time estimations. The analogical method has disadvantages that are improved through the new specification which the project is divided into different phases and time is estimated separately according to the Micro strategy for every phase. The recommendations made in this study leads to greater responsibility for individuals within the projects, better knowledge sharing in the company where old experiences will be the basis for the new time estimates. The new changes will lead to making the decision making within a project easier for both the costumer and LexiConsult AB.</p>

Det finns olika strategier och många olika metoder inom strategierna för att tidsuppskatta ett IT-projekt. Dessa strategier och metoder skiljer sig mer eller mindre åt och många gånger har företag egna metoder för tidsuppskattning. Dessa strategier och metoder har samma syfte, vilket är att göra så noggranna tidsuppskattningar som möjligt för att undvika försenade projekt. Examensarbetets syfte är att visa på hur LexiConsult AB kan förbättra sina tidsuppskattningar av inkommande IT-projekt genom att följa studiens rekommendationer, vilket leder till bättre tidsuppskattningar och nöjdare kunder. Undersökningen har utförts genom en litteraturstudie, där genomgång av de olika delarna inom IT-projekt skett. Det teoretiska kapitlet ligger senare till grund för den empiriska undersökning som utförts på företaget vilket ger insikt och perspektiv i hur företaget arbetar med sina projekt. Teorin visade att en bra tidsuppskattningsmetod inkluderar alla delarna i ett projekt och att dessa måste genomgås innan en bra tidsuppskattningsmetod kan tas fram. Det komplexa ämnet tidsuppskattning har gjort att en deduktiv ansats har valts för arbetet, där utgångspunkten ligger i teorin. Den djupa teorigenomgång som har utförts av författarna avspeglar sig i den kvalitativa forskningsmetod som valts för studien där syftet med metoden är att få djupare kunskap genom analyser och tolkningar i teori och verklighet. Författarna har försöktsäkerställa examensarbetets kvalité genom att beakta det insamlade materialets validitet, reliabilitet och relevans. De analyser som genomförs i arbetet där LexiConsults arbetssätt analyseras mot den teori som har genomgåtts leder till ett flertal rekommendationer i slutsatsen av arbetet. Företagets brister i informationsstruktur leder till rekommendationer om införandet av en databas med kategorier av de projekt företaget utför. Vikten av bra kravspecifikationer inom tidsuppskattning leder i slutsatsen till en förbättrad kravspecifikation med uppdelning av de olika faserna i projektet med tidsuppskattning och kommentarer på varje del. Vikten av bra uppföljning av projekt framhävs och rekommendationer ges till en uppföljningsmall, vilket resulterar i designen till en sådan. Företagets arbetsmetoder och historik tas tillvara och en analogisk tidsuppskattningsmetod rekommenderas för framtida projekts tidsuppskattningar. Den analogiska metodens nackdelar förbättras genom tillämpandet av den nya kravspecifikationen där projekt delas i olika faser och tidsuppskattas separat enligt mikrostrategin inom tidsuppskattningar. Uppföljningsdokumentet samt den nya kravspecifikationen och den nya informationsstrukturen kommer enligt studiens slutsats att leda till flera positiva förändringar inom företaget. De nya förändringarna tillför större ansvar för den enskilde i projekt, bättre kunskapsdelning i företaget där erfarenhetsmässig kunskap kommer att ligga till grund för nya tidsuppskattningar, bättre beslutsunderlag för konsultchef samt för kund att lättare följa upp företagets tidsuppskattningar och hitta svagheter.Det finns olika strategier och många olika metoder inom strategierna för att tidsuppskatta ett IT-projekt. Dessa strategier och metoder skiljer sig mer eller mindre åt och många gånger har företag egna metoder för tidsuppskattning. Dessa strategier och metoder har samma syfte, vilket är att göra så noggranna tidsuppskattningar som möjligt för att undvika försenade projekt. Examensarbetets syfte är att visa på hur LexiConsult AB kan förbättra sina tidsuppskattningar av inkommande IT-projekt genom att följa studiens rekommendationer, vilket leder till bättre tidsuppskattningar och nöjdare kunder. Undersökningen har utförts genom en litteraturstudie, där genomgång av de olika delarna inom IT-projekt skett. Det teoretiska kapitlet ligger senare till grund för den empiriska undersökning som utförts på företaget vilket ger insikt och perspektiv i hur företaget arbetar med sina projekt. Teorin visade att en bra tidsuppskattningsmetod inkluderar alla delarna i ett projekt och att dessa måste genomgås innan en bra tidsuppskattningsmetod kan tas fram.Det komplexa ämnet tidsuppskattning har gjort att en deduktiv ansats har valts för arbetet, där utgångspunkten ligger i teorin. Den djupa teorigenomgång som har utförts av författarna avspeglar sig i den kvalitativa forskningsmetod som valts för studien där syftet med metoden är att få djupare kunskap genom analyser och tolkningar i teori och verklighet. Författarna har försöktsäkerställa examensarbetets kvalité genom att beakta det insamlade materialets validitet, reliabilitet och relevans.De analyser som genomförs i arbetet där LexiConsults arbetssätt analyseras mot den teori som har genomgåtts leder till ett flertal rekommendationer i slutsatsen av arbetet. Företagets brister i informationsstruktur leder till rekommendationer om införandet av en databas med kategorier av de projekt företaget utför. Vikten av bra kravspecifikationer inom tidsuppskattning leder i slutsatsen till en förbättrad kravspecifikation med uppdelning av de olika faserna i projektet med tidsuppskattning och kommentarer på varje del. Vikten av bra uppföljning av projekt framhävs och rekommendationer ges till en uppföljningsmall, vilket resulterar i designen till en sådan. Företagets arbetsmetoder och historik tas tillvara och en analogisk tidsuppskattningsmetod rekommenderas för framtida projekts tidsuppskattningar. Den analogiska metodens nackdelar förbättras genom tillämpandet av den nya kravspecifikationen där projekt delas i olika faser och tidsuppskattas separat enligt mikrostrategin inom tidsuppskattningar. Uppföljningsdokumentet samt den nya kravspecifikationen och den nya informationsstrukturen kommer enligt studiens slutsats att leda till flera positiva förändringar inom företaget. De nya förändringarna tillför större ansvar för den enskilde i projekt, bättre kunskapsdelning i företaget där erfarenhetsmässig kunskap kommer att ligga till grund för nya tidsuppskattningar, bättre beslutsunderlag för konsultchef samt för kund att lättare följa upp företagets tidsuppskattningar och hitta svagheter. / There are many different strategies and different approaches within the strategies to estimate the time of an IT project. These methods and practices differ in several aspects and many times companies have developed their own method for estimating time. The common factors for these strategies and methods are the objectives, which is to make time estimation as accurate as possible, to avoid delays in projects. This study aims to show how LexiConsult AB can improve it’s time estimations by following the recommendations made in this study, which leads to reduction in their time estimates and better customer satisfaction. The study was conducted through a literature review of where the various components of IT projects are reviewed. The theoretical analysis is later the subject of the empirical investigation in the company giving instinct and perspective into how the company is working on their projects. The theory showed that a good time estimation method includes all the elements of a project and these must be examined before a good time estimation method can be developed. Because of the complexity of this topic, a deductive approach was chosen for the study, where the starting point lies in the theory. The deep theory examination conducted by the authors is reflected in the qualitative research method chosen for study where the purpose of the method is to gain deeper knowledge through analysis and interpretation of the theory and reality.The authors have tried to ensure the quality of work by considering the collected material's validity, reliability and relevance.Because of the complexity of this topic, a deductive approach was chosen for the study, where the starting point lies in the theory. The deep theory examination conducted by the authors is reflected in the qualitative research method chosen for study where the purpose of the method is to gain deeper knowledge through analysis and interpretation of the theory and reality.The authors have tried to ensure the quality of work by considering the collected material's validity, reliability and relevance. The analysis conducted in the study, is LexiConsult's project methods which are compared against the theory. These comparisons led to a number of recommendations in the conclusion of the study. The company's shortcomings in information structure area are identified and leads to recommendations on the establishment of a database with project categories. The importance of good requirements specifications for time estimation is identified and in the conclusion an improved specification is shown. The new specification has separated phases of the project with time estimates and comments on each part. The importance of good monitoring of the projects is highlighted in the study and recommendations are given to follow a template, resulting in the design of one. The company's working methods and use of the experience is indicative, and an analogy time estimation method is recommended for future time estimations. The analogical method has disadvantages that are improved through the new specification which the project is divided into different phases and time is estimated separately according to the Micro strategy for every phase. The recommendations made in this study leads to greater responsibility for individuals within the projects, better knowledge sharing in the company where old experiences will be the basis for the new time estimates. The new changes will lead to making the decision making within a project easier for both the costumer and LexiConsult AB.