SwePub
Sök i SwePub databas

  Utökad sökning

Träfflista för sökning "WFRF:(Loconsole Annabella) "

Sökning: WFRF:(Loconsole Annabella)

  • Resultat 1-26 av 26
Sortera/gruppera träfflistan
   
NumreringReferensOmslagsbildHitta
1.
  • Bjarnason, Elizabeth, et al. (författare)
  • Challenges and practices in aligning requirements with verification and validation : a case study of six companies
  • 2014
  • Ingår i: Empirical Software Engineering. - : Springer. - 1382-3256 .- 1573-7616. ; 19:6, s. 1809-1855
  • Tidskriftsartikel (refereegranskat)abstract
    • Weak alignment of requirements engineering (RE) with verification and validation (VV) may lead to problems in delivering the required products in time with the right quality. For example, weak communication of requirements changes to testers may result in lack of verification of new requirements and incorrect verification of old invalid requirements, leading to software quality problems, wasted effort and delays. However, despite the serious implications of weak alignment research and practice both tend to focus on one or the other of RE or VV rather than on the alignment of the two. We have performed a multi-unit case study to gain insight into issues around aligning RE and VV by interviewing 30 practitioners from 6 software developing companies, involving 10 researchers in a flexible research process for case studies. The results describe current industry challenges and practices in aligning RE with VV, ranging from quality of the individual RE and VV activities, through tracing and tools, to change control and sharing a common understanding at strategy, goal and design level. The study identified that human aspects are central, i.e. cooperation and communication, and that requirements engineering practices are a critical basis for alignment. Further, the size of an organisation and its motivation for applying alignment practices, e.g. external enforcement of traceability, are variation factors that play a key role in achieving alignment. Our results provide a strategic roadmap for practitioners improvement work to address alignment challenges. Furthermore, the study provides a foundation for continued research to improve the alignment of RE with VV.
  •  
2.
  •  
3.
  •  
4.
  •  
5.
  •  
6.
  • Loconsole, Annabella, et al. (författare)
  • An Industrial Case Study on Requirements Volatility Measures
  • 2005
  • Ingår i: Proceeding of APSEC: 12th IEEE Asia Pacific Software Engineering Conference. ; , s. 845-
  • Konferensbidrag (refereegranskat)abstract
    • Requirements volatility is an important risk factor for software projects. Software measures can help in quantifying and predicting this risk. In this paper, we present an industrial case study that investigated measures of volatility for a medium size software project. The goal of the study was twofold: 1) to empirically validate a set of measures associated with the volatility of use case models (UCM); 2) to investigate the correlation between subjective and objective volatility. Measurement data was collected in retrospect for all use case models of the software project. In addition, we determined subjective volatility by interviewing stakeholders of the project. Our data analysis showed a high correlation between our measures of size of UCM and total number of changes, indicating that the measures of size of UCMs are good indicators of requirements volatility. No correlations was found between subjective and objective volatility. These results suggest that project managers at this company should measure their projects because of the risk to take wrong decisions based on their own and the developer´s perceptions.
  •  
7.
  •  
8.
  • Loconsole, Annabella, et al. (författare)
  • Are Size Measures Better than Expert Opinion? An Industrial Case Study on Requirements Volatility
  • 2007
  • Ingår i: Proceedings of the 14th Asia-Pacific Software Engineering Conference (APSEC'07). ; , s. 577-
  • Konferensbidrag (refereegranskat)abstract
    • Expert judgment is a common estimation approach in industry. However, there is very little research on the accuracy of expert judgment outside the area of effort estimation. In this paper, we present an industrial case study investigating subjective and objective measures of requirements volatility. Data was collected in retrospect for all use cases of a medium-size software project. In addition, we determined subjective volatility by interviewing developers and managers of the project. Our data analysis show that structural measures perform better than expert judgment in estimating the total number of changes to use case based requirements. These results confirm results from a previous case study by the authors and suggest that project managers should not rely on expert judgment alone for decision making.
  •  
9.
  •  
10.
  • Loconsole, Annabella, et al. (författare)
  • Comparing the CDIO educational framework with University West’s WIL certification: do they complement each other?
  • 2021
  • Ingår i: VILÄR. - 9789189325036 ; , s. 15-16
  • Konferensbidrag (övrigt vetenskapligt/konstnärligt)abstract
    • Higher education institutions (HEIs) need to continuously improve their quality to prepare the students to the society of the 21st Century. They need to develop efficient ways of collaborating with various partners in the surrounding community. Close ties with business and industry, and diversity among staff and students are necessary, especially within engineering education. An engineering degree should prepare students to develop a wide range of knowledge and skills. These range from technical, scientific, and mathematical knowledge but also soft skills such as teamwork, business skills and critical analysis, which are also central sustainability competences. It is vital that learning for engineers takes place in the context of authentic engineering problems and processes to develop these skills and to put theory into practice. Several initiatives focused on incorporating these skills in higher education exists. CDIO (Conceive, Design, Implement, Operate) is one of the most prominent initiatives within engineering education. CDIO targets the typical tasks an engineer performs when bringing new systems, products and services to the market or the society. The CDIO initiative was created to strengthen active and problem-based learning and improving students' communication and professional skills. CDIO focus on improving practical and work-related skills to better prepare engineering students for their future professional life.University West employs another initiative, Arbetsintegrerat lärande (AIL), which “roughly” translates to Work Integrated Learning (WIL). WIL shares much of the same philosophy as CDIO. All programs at University West are currently undergoing an AIL-certification process. For engineering programs, that have been working with CDIO, it is interesting to compare them. It is currently unclear how they differ. In this study we compare the CDIO educational framework with the WIL-certification through a series of workshops to identify in which areas they overlap and which areas they differ. Would a program that has adopted the CDIO educational framework automatically fulfill the WIL-certification? 
  •  
11.
  • Loconsole, Annabella, et al. (författare)
  • Construction and Evaluation of an Algorithmic and Distributed Prioritization Method
  • 2011
  • Ingår i: 17th International Working Conference on Requirements Engineering: Foundation for Software Quality (REFSQ 2011). Proceedings of the REFSQ 2011 Workshops REEW, EPICAL and RePriCo, the REFSQ 2011 Empirical Track (Empirical Live Experiment and Empirical Research Fair), and the REFSQ 2011 Doctoral Symposium. - : Institute for Computer Science and Business Information Systems, University of Duisburg‐Essen. ; , s. 110-121
  • Konferensbidrag (övrigt vetenskapligt/konstnärligt)abstract
    • Prioritization of requirements and tasks is an important activity of the development process; it can however be a very complex and time-consuming activity. In this paper we present MAAD (Method for Agile, Automated and Distributed prioritization) an algorithmic prioritization method. The method was developed at Flygprestanda AB, which needed a systematic and automated way of prioritizing requirements and work tasks. The method is constructed based on existing prioritization methods, focusing on minimizing the end-user time-consumption. Factors considered in the priority calculation are Urgency, Benefit, Cost, and Type. Furthermore, in order for the method to suit different companies and projects the importance of the different factors is adjustable. An evaluation was performed, which showed that MAAD prioritization was easierto- use, less time-consuming, more accurate, more scalable and the prioritization method most suitable for Flygprestanda compared to Wiegers method and the prioritization method used at the company.
  •  
12.
  •  
13.
  •  
14.
  • Loconsole, Annabella, et al. (författare)
  • Construction and Validation of Prediction Models for Number of Changes to Requirements
  • 2007
  • Rapport (övrigt vetenskapligt/konstnärligt)abstract
    • In this paper we present a correlational study in which we assess the ability of five size measures to predict the number of changes to requirements for a medium size software project. The study is explorative, i.e. we analyse the data collected for our measures to find out the best predictor of number of changes. To our knowledge, no empirical validation of requirements change measures as predictors has been performed in an industrial setting. Based on the data collected from two industrial projects for five measures of size of requirements (number of actors, use cases, words, lines, and revisions), we have built and evaluated prediction models for number of changes to requirements. These models can help project managers to estimate the volatility of requirements and minimize the risks caused by volatile requirements, like schedule and costs overruns.We performed a cross systems validation. For our best model we calculated a pred(0.25)=0.5, which is better than the accuracy of common effort prediction models like for example COCOMO. Although our models are likely to have only local validity, the general method for constructing the prediction models could be applied in any software development company. In an earlier study, we showed that decisions solely based on developer perception are unreliable. Predictions models, like the one presented here can help to mitigate that risk.
  •  
15.
  • Loconsole, Annabella, 1965- (författare)
  • Definition and validation of requirements management measures
  • 2007
  • Doktorsavhandling (övrigt vetenskapligt/konstnärligt)abstract
    • The quality of software systems depends on early activities in the software development process, of which the management of requirements is one. When requirements are not managed well, a project can fail or become more costly than intended, and the quality of the software developed can decrease. Among the requirements management practices, it is particularly important to quantify and predict requirements volatility, i.e., how much the requirements are likely to change over time. Software measures can help in quantifying and predicting requirements attributes like volatility. However, few measures have yet been defined, due to the fact that the early phases are hard to formalise. Furthermore, very few requirements measures have been validated, which would be needed in order to demonstrate that they are useful. The approach to requirements management in this thesis is quantitative, i.e. to monitor the requirements management activities and requirements volatility through software measurement. In this thesis, a set of 45 requirements management measures is presented. The measures were defined using the goal question metrics framework for the two predefined goals of the requirements management key process area of the capability maturity model for software. A subset of these measures was validated theoretically and empirically in four case studies. Furthermore, an analysis of validated measures in the literature was performed, showing that there is a lack of validated process, project, and requirements measures in software engineering. The studies presented in this thesis show that size measures are good estimators of requirements volatility. The important result is that size is relevant: increasing the size of a requirements document implies that the number of changes to requirements increases as well. Furthermore, subjective estimations of volatility were found to be inaccurate assessors of requirements volatility. These results suggest that practitioners should complement the subjective estimations for assessing volatility with the objective ones. Requirements engineers and project managers will benefit from the research presented in this thesis because the measures defined, proved to be predictors of volatility, can help in understanding how much requirements will change. By deploying the measures, the practitioners would be prepared for possible changes in the schedule and cost of a project, giving them the possibility of creating alternative plans, new cost estimates, and new software development schedules.
  •  
16.
  • Loconsole, Annabella (författare)
  • Definition and Validation of Requirements Volatility Measures
  • 2006
  • Ingår i: Proceeding of SERPS'06 Sixth Conference on Software Engineering Research and Practice in Sweden. - 9172641983 ; , s. 99-
  • Konferensbidrag (refereegranskat)abstract
    • This paper is a summary of a PhD thesis which describes our effortto define and validate requirements volatility measures. Thesemeasures have been proven to be reliable predictors ofrequirements volatility.
  •  
17.
  • Loconsole, Annabella (författare)
  • Empirical studies on requirement management measures
  • 2004
  • Ingår i: Proceedings of the 26th International Conference on Software Engineering, 2004. ICSE 2004.. - 0769521630 ; , s. 786-
  • Konferensbidrag (refereegranskat)abstract
    • The goal of this research is to demonstrate that a subset of a set of 38 requirements management measures are good predictors of stability and volatility of requirements and change requests. At the time of writing we have theoretically validated ten of these 38 measures. We are currently planning and performing an industrial case study where we want to reach the goal described above.
  •  
18.
  •  
19.
  •  
20.
  •  
21.
  • Lundqvist, Thomas, 1967-, et al. (författare)
  • Comparing the Cdio Standards with the Work Integrated Learning Certification
  • 2022
  • Ingår i: Proceedings of the International CDIO Conference 18th International CDIO Conference, CDIO 2022 Reykjavik. - : Chalmers University of Technology. - 9789935965561 ; , s. 37-47
  • Konferensbidrag (övrigt vetenskapligt/konstnärligt)abstract
    • Improving the quality of higher education is an important responsibility of universities and colleges. Several approaches have been developed with the goal of improving the quality of university study programs. In this paper we compare the CDIO (Conceive, Design, Implement, Operate) and the work-integrated learning (WIL) initiatives based on recently completed WIL certifications at University West. Through a series of workshops, the CDIO standards are compared with the aspects and criteria of the WIL certification guidelines, to identify overlapping areas and differences between the two initiatives. The results show that both initiatives overlap but also differ in several aspects. These differences could be useful to strengthen the WIL certification process at University West as well as clarifying the connection between CDIO and work-integrated learning.  
  •  
22.
  •  
23.
  • Sabaliauskaité, Giedré, et al. (författare)
  • Challenges in Aligning Requirements Engineering and Verification in a Large-Scale Industrial Context
  • 2010
  • Ingår i: Requirements Engineering: Foundation for Software Quality /Lecture Notes in Computer Science. - Essen : Springer Berlin Heidelberg. - 1611-3349 .- 0302-9743. - 9783642141911 ; 6182, s. 128-142
  • Konferensbidrag (refereegranskat)abstract
    • [Context and motivation] When developing software, coordination between different organizational units is essential in order to develop a good quality product, on time and within budget. Particularly, the synchronization between requirements and verification processes is crucial in order to assure that the developed software product satisfies customer requirements. [Question/problem] Our research question is: what are the current challenges in aligning the requirements and verification processes? [Principal ideas/results] We conducted an interview study at a large software development company. This paper presents preliminary findings of these interviews that identify key challenges in aligning requirements and verification processes. [Contribution] The result of this study includes a range of challenges faced by the studied organization grouped into the categories: organization and processes, people, tools, requirements process, testing process, change management, traceability, and measurement. The findings of this study can be used by practitioners as a basis for investigating alignment in their organizations, and by scientists in developing approaches for more efficient and effective management of the alignment between requirements and verification.
  •  
24.
  • Shao, Deo, et al. (författare)
  • M-Health : A Mobile Data Collection Prototype for Monitoring and Evaluation of Public Health Service in the Developing World
  • 2012
  • Ingår i: Journal of Informatics and virtual education. - : University of Dodoma, College of Informatics and Virtual Education, Tanzania. - 1821-7087. ; 2:1, s. 43-50
  • Tidskriftsartikel (refereegranskat)abstract
    • The rapidly growing use of mobile technologies has increased pressure on the demand for mobile-based data collection solutions to bridge the information gaps in the public health sector. In this paper, a prototype for mobile health data collection (MHDK) is proposed. MHDK is built based on open source data collection frameworks. The proposed prototype offers ways of collecting health data through mobile phones and visualizes the collected data in a web application. The evaluation of the prototype seems to show the feasibility of mobile technologies, particularly open source technologies, in improving the health data collection and reporting systems for the developing world. The use of cellular phones for public health service monitoring and evaluation is therefore one of the most promising developments in the quest to achieve improved public health services.
  •  
25.
  • Svahnberg, Mikael, et al. (författare)
  • Perspectives on Requirements Understandability : for Whom Does the Teacher's Bell Toll?
  • 2008
  • Konferensbidrag (refereegranskat)abstract
    • Software development decision makers use many different information sources as a basis for their decisions. One of these sources is the requirements specification, which is used in a large number of processes throughout the software development cycle. In order to make good decisions, the quality and completeness of the available information is important. Hence, requirements must be written in a way that is understandable for the different decision makers. However, requirements are rarely written with an explicit perception of how to make them understandable for different target usages. In this study we investigate the implicit assumptions of current and future requirements engineers and their teachers regarding which usages they perceive as most important when creating requirements. This is contrasted with industrial viewpoints of the relative importance of different requirements usages. The results indicate that the teachers and future requirements engineers have a strong focus towards in-project perspectives, and very little in common with the perspectives of industry managers. Thus, we are training students to serve as software developers, and not software engineering managers.
  •  
26.
  •  
Skapa referenser, mejla, bekava och länka
  • Resultat 1-26 av 26

Kungliga biblioteket hanterar dina personuppgifter i enlighet med EU:s dataskyddsförordning (2018), GDPR. Läs mer om hur det funkar här.
Så här hanterar KB dina uppgifter vid användning av denna tjänst.

 
pil uppåt Stäng

Kopiera och spara länken för att återkomma till aktuell vy