Pub Date : 2009-10-01DOI: 10.1109/CEE-SECR.2009.5501136
A. Mayorov
Agile requires accordingly agile software architecture and programming tools. For web development popular agile architecture is MVC (Model-View-Controller). For transferring data between controller and view XML is very suitable. And to transform it into final form it's better to use XSLT. XSLT is not very popular among developers, because they think this is just yet another “strange” language, without any real advantage comparing to usual languages. But advantages are real - XSLT allows for very interesting results, not possible with other templating languages. It definitely worth studying and this is not hard.
{"title":"XSLT in Agile web development","authors":"A. Mayorov","doi":"10.1109/CEE-SECR.2009.5501136","DOIUrl":"https://doi.org/10.1109/CEE-SECR.2009.5501136","url":null,"abstract":"Agile requires accordingly agile software architecture and programming tools. For web development popular agile architecture is MVC (Model-View-Controller). For transferring data between controller and view XML is very suitable. And to transform it into final form it's better to use XSLT. XSLT is not very popular among developers, because they think this is just yet another “strange” language, without any real advantage comparing to usual languages. But advantages are real - XSLT allows for very interesting results, not possible with other templating languages. It definitely worth studying and this is not hard.","PeriodicalId":402768,"journal":{"name":"2009 5th Central and Eastern European Software Engineering Conference in Russia (CEE-SECR)","volume":"15 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2009-10-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"129286874","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Pub Date : 2009-10-01DOI: 10.1109/CEE-SECR.2009.5501144
Dmitry Zaretskiy, V. Serbin
Recommendations on the usage of agile methods in companies creating and implementing complex software applications are given. Peculiarities of product software development in comparison with be-spoke projects are disclosed. These peculiarities arise from the necessity to take into account the needs of several different stakeholders' groups simultaneously. It is shown that Scrum is possible to use for the whole product development including maintenance and support. Practices specific for application development and deviations from the standard Scrum practices are given, which increases the Scrum efficiency. The use of those practices allowed increasing the velocity measured in product backlog items by 30–40% and significantly improved motivation of the personnel participating in development.
{"title":"Using agile methods for product software development","authors":"Dmitry Zaretskiy, V. Serbin","doi":"10.1109/CEE-SECR.2009.5501144","DOIUrl":"https://doi.org/10.1109/CEE-SECR.2009.5501144","url":null,"abstract":"Recommendations on the usage of agile methods in companies creating and implementing complex software applications are given. Peculiarities of product software development in comparison with be-spoke projects are disclosed. These peculiarities arise from the necessity to take into account the needs of several different stakeholders' groups simultaneously. It is shown that Scrum is possible to use for the whole product development including maintenance and support. Practices specific for application development and deviations from the standard Scrum practices are given, which increases the Scrum efficiency. The use of those practices allowed increasing the velocity measured in product backlog items by 30–40% and significantly improved motivation of the personnel participating in development.","PeriodicalId":402768,"journal":{"name":"2009 5th Central and Eastern European Software Engineering Conference in Russia (CEE-SECR)","volume":"33 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2009-10-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"121953499","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Pub Date : 2009-10-01DOI: 10.1109/CEE-SECR.2009.5501171
Dmitry Isaychenko
Having IT Service management as the main professional focus we perform projects for local and international companies in various industries including banking. It is not difficult to see that even in the most mature companies signs of “island-thinking” between Development and Operations are present. Lack of cooperation between these two IT teams often appears to be the root cause of various service incidents or becomes an obstacle for attempts to solve problems caused by errors in software itself or its improper operation. The aim of this work is to show the importance of effective cooperation between Development and Operations basing on a real-life case.
{"title":"Life after implementation: operation-friendly software development","authors":"Dmitry Isaychenko","doi":"10.1109/CEE-SECR.2009.5501171","DOIUrl":"https://doi.org/10.1109/CEE-SECR.2009.5501171","url":null,"abstract":"Having IT Service management as the main professional focus we perform projects for local and international companies in various industries including banking. It is not difficult to see that even in the most mature companies signs of “island-thinking” between Development and Operations are present. Lack of cooperation between these two IT teams often appears to be the root cause of various service incidents or becomes an obstacle for attempts to solve problems caused by errors in software itself or its improper operation. The aim of this work is to show the importance of effective cooperation between Development and Operations basing on a real-life case.","PeriodicalId":402768,"journal":{"name":"2009 5th Central and Eastern European Software Engineering Conference in Russia (CEE-SECR)","volume":"12 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2009-10-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"133408734","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Pub Date : 2009-10-01DOI: 10.1109/CEE-SECR.2009.5501169
Tatyana Peftieva, Stanislav Kalkanov
In current economic conditions quality issues as well as issues of effectiveness and efficiency in software development are become rather much more critical then usual. Process Improvement practices can propose a lot of appropriate “recipes” for companies which are interested in enhancement of their software development processes. This article contains description of original approach of software development efficiency analysis based on CMMI Gap Analysis (GA). Described method summarizes Luxoft experience and expertise during the last 2 years in mentioned areas and has already proved his practical value. Luxoft Gap Analysis method description, average estimated efforts and information about benefits and ways of results usage are given to audience attention.
{"title":"Mind the GAP or how to provide stability and evolution in software development using CMMI GAP-analysis","authors":"Tatyana Peftieva, Stanislav Kalkanov","doi":"10.1109/CEE-SECR.2009.5501169","DOIUrl":"https://doi.org/10.1109/CEE-SECR.2009.5501169","url":null,"abstract":"In current economic conditions quality issues as well as issues of effectiveness and efficiency in software development are become rather much more critical then usual. Process Improvement practices can propose a lot of appropriate “recipes” for companies which are interested in enhancement of their software development processes. This article contains description of original approach of software development efficiency analysis based on CMMI Gap Analysis (GA). Described method summarizes Luxoft experience and expertise during the last 2 years in mentioned areas and has already proved his practical value. Luxoft Gap Analysis method description, average estimated efforts and information about benefits and ways of results usage are given to audience attention.","PeriodicalId":402768,"journal":{"name":"2009 5th Central and Eastern European Software Engineering Conference in Russia (CEE-SECR)","volume":"73 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2009-10-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"124191691","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Pub Date : 2009-10-01DOI: 10.1109/CEE-SECR.2009.5501185
A.A. Lyanguzov
What the Context Driven Testing (CDT) is - a personal approach to testing that allows you to be more efficient, helpful and successful in your everyday work and your profession in whole. - a good base for establishing your effective, flexible and rational internal testing process. - a way to get comprehensive, honest and accurate feedback about the product's quality in appropriate time. - a method to unfold project from different points of view. What the Context Driven Testing is NOT - a set of practices. It's not a technical methodology or approach to solve some particular tasks. - a cult, religion, theory or doctrine. CDT is lifestyle of thinking testers!
{"title":"Content driven testing: Practical use in software testing","authors":"A.A. Lyanguzov","doi":"10.1109/CEE-SECR.2009.5501185","DOIUrl":"https://doi.org/10.1109/CEE-SECR.2009.5501185","url":null,"abstract":"What the Context Driven Testing (CDT) is - a personal approach to testing that allows you to be more efficient, helpful and successful in your everyday work and your profession in whole. - a good base for establishing your effective, flexible and rational internal testing process. - a way to get comprehensive, honest and accurate feedback about the product's quality in appropriate time. - a method to unfold project from different points of view. What the Context Driven Testing is NOT - a set of practices. It's not a technical methodology or approach to solve some particular tasks. - a cult, religion, theory or doctrine. CDT is lifestyle of thinking testers!","PeriodicalId":402768,"journal":{"name":"2009 5th Central and Eastern European Software Engineering Conference in Russia (CEE-SECR)","volume":"55 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2009-10-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"131210795","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Pub Date : 2009-10-01DOI: 10.1109/CEE-SECR.2009.5501166
Grachev Anton
On SECR-2008 conference an article, representing an experience of creating a solution for software development project management - LUXproject, was presented. The report highlighted technical questions related to integration of LUXproject components, in the last part of the article implementation questions were briefly observed. This paper discusses questions and problems that customer and project team face during implementation of the solution (internal and external customers were taken as an example). In article, major implementation scenarios are presented: implementation of the process that is already used within an existing project as well as implementation of the predefined process templates applied to the new projects.
{"title":"Practical experience in solution implementation of integrated software development project automation","authors":"Grachev Anton","doi":"10.1109/CEE-SECR.2009.5501166","DOIUrl":"https://doi.org/10.1109/CEE-SECR.2009.5501166","url":null,"abstract":"On SECR-2008 conference an article, representing an experience of creating a solution for software development project management - LUXproject, was presented. The report highlighted technical questions related to integration of LUXproject components, in the last part of the article implementation questions were briefly observed. This paper discusses questions and problems that customer and project team face during implementation of the solution (internal and external customers were taken as an example). In article, major implementation scenarios are presented: implementation of the process that is already used within an existing project as well as implementation of the predefined process templates applied to the new projects.","PeriodicalId":402768,"journal":{"name":"2009 5th Central and Eastern European Software Engineering Conference in Russia (CEE-SECR)","volume":"47 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2009-10-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"115820424","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Pub Date : 2009-10-01DOI: 10.1109/CEE-SECR.2009.5501176
S. Bogdan, A. Kudinov, N. Markov
Today's trend in automation of the large industrial enterprises is gradual filling of intermediate layer between low level systems of automation (management information systems of technological process) and control systems of the enterprise on the basis of ERP and BI. Traditionally MES which users are, first of all, engineers and analysts of the main experts here apply for a link role. The overwhelming majority of the systems presented today in the market, have a narrow branch orientation. It is caused by complexity of balance between the flexibility of architectural and interface decisions necessary for expansion of systems, and convenience to the user, wishing to have the simple tool of the decision of the daily problems. Design and implementation of such systems is interfaced to a number of serious problems, as characteristic for working out of the big distributed information systems, and specific for MES. An experience of solving such problems on example of MES “Magistral-Vostok” by Tomsk polytechnical university is considered.
{"title":"Example of implementation of MES “Magistral-Vostok” for oil and gas production enterprise","authors":"S. Bogdan, A. Kudinov, N. Markov","doi":"10.1109/CEE-SECR.2009.5501176","DOIUrl":"https://doi.org/10.1109/CEE-SECR.2009.5501176","url":null,"abstract":"Today's trend in automation of the large industrial enterprises is gradual filling of intermediate layer between low level systems of automation (management information systems of technological process) and control systems of the enterprise on the basis of ERP and BI. Traditionally MES which users are, first of all, engineers and analysts of the main experts here apply for a link role. The overwhelming majority of the systems presented today in the market, have a narrow branch orientation. It is caused by complexity of balance between the flexibility of architectural and interface decisions necessary for expansion of systems, and convenience to the user, wishing to have the simple tool of the decision of the daily problems. Design and implementation of such systems is interfaced to a number of serious problems, as characteristic for working out of the big distributed information systems, and specific for MES. An experience of solving such problems on example of MES “Magistral-Vostok” by Tomsk polytechnical university is considered.","PeriodicalId":402768,"journal":{"name":"2009 5th Central and Eastern European Software Engineering Conference in Russia (CEE-SECR)","volume":"24 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2009-10-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"129885390","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Pub Date : 2009-10-01DOI: 10.1109/CEE-SECR.2009.5501151
Alexey Ieshin, Marina Gerenko, V. Dmitriev
F-Secure is a global leader in providing security as a service through ISP's and mobile operators [1]. The company first used Agile more than 5 years ago and is still in the transition and building the true Agile culture. Test automation (TA) is one of Agile practices that the company has been focusing on and improving lately [2]. This paper describes how TA has been implemented in the company, benefits and drawbacks of different approaches, and key learnings. Our findings may be of interest and help for other Agile teams using or building a automation test system.
{"title":"Test automation: Flexible way","authors":"Alexey Ieshin, Marina Gerenko, V. Dmitriev","doi":"10.1109/CEE-SECR.2009.5501151","DOIUrl":"https://doi.org/10.1109/CEE-SECR.2009.5501151","url":null,"abstract":"F-Secure is a global leader in providing security as a service through ISP's and mobile operators [1]. The company first used Agile more than 5 years ago and is still in the transition and building the true Agile culture. Test automation (TA) is one of Agile practices that the company has been focusing on and improving lately [2]. This paper describes how TA has been implemented in the company, benefits and drawbacks of different approaches, and key learnings. Our findings may be of interest and help for other Agile teams using or building a automation test system.","PeriodicalId":402768,"journal":{"name":"2009 5th Central and Eastern European Software Engineering Conference in Russia (CEE-SECR)","volume":"33 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2009-10-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"130086031","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Pub Date : 2009-10-01DOI: 10.1109/CEE-SECR.2009.5501180
A.N. Karpov, E. A. Ryzhkov
The goal of this paper is to tell about the methodology and tools for errors detection in parallel programs at the code writing stage. Applying static code analysis methodology allows developers to significantly reduce the error correction costs at the testing and support stages. The error diagnostics in multithread applications will be demonstrated with the examples of PC-Lint, VivaMP, and Intel C++ “Parallel Lint” analyzers. The paper will be useful for developers who create parallel Windows applications in C/C++ languages.
{"title":"Early errors detection in parallel programs","authors":"A.N. Karpov, E. A. Ryzhkov","doi":"10.1109/CEE-SECR.2009.5501180","DOIUrl":"https://doi.org/10.1109/CEE-SECR.2009.5501180","url":null,"abstract":"The goal of this paper is to tell about the methodology and tools for errors detection in parallel programs at the code writing stage. Applying static code analysis methodology allows developers to significantly reduce the error correction costs at the testing and support stages. The error diagnostics in multithread applications will be demonstrated with the examples of PC-Lint, VivaMP, and Intel C++ “Parallel Lint” analyzers. The paper will be useful for developers who create parallel Windows applications in C/C++ languages.","PeriodicalId":402768,"journal":{"name":"2009 5th Central and Eastern European Software Engineering Conference in Russia (CEE-SECR)","volume":"46 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2009-10-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"129013409","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Pub Date : 2009-10-01DOI: 10.1109/CEE-SECR.2009.5501172
N. Sushkov, S. Zykov
This article covers the message delivery system refactoring using Domain Driven Development (DDD) and Domain Specific Language (DSL) approach. First it explains the main concepts of Domain Driven Development and Domain Specific Language. After that it describes the steps of development process based on Domain Specific Language including domain model design and development of DSL notation by the example of message delivery system. In conclusion it overviews key benefits provided by DDD and DSL approach (compare with previous version of message delivery system).
{"title":"Message system refactoring using DSL","authors":"N. Sushkov, S. Zykov","doi":"10.1109/CEE-SECR.2009.5501172","DOIUrl":"https://doi.org/10.1109/CEE-SECR.2009.5501172","url":null,"abstract":"This article covers the message delivery system refactoring using Domain Driven Development (DDD) and Domain Specific Language (DSL) approach. First it explains the main concepts of Domain Driven Development and Domain Specific Language. After that it describes the steps of development process based on Domain Specific Language including domain model design and development of DSL notation by the example of message delivery system. In conclusion it overviews key benefits provided by DDD and DSL approach (compare with previous version of message delivery system).","PeriodicalId":402768,"journal":{"name":"2009 5th Central and Eastern European Software Engineering Conference in Russia (CEE-SECR)","volume":"7 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2009-10-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"131662855","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
京公网安备 11010802042870号
京ICP备2023020795号-1
扫码关注我们
求助内容：
应助结果提醒方式：