Context: Requirement Engineering (RE) is one of the important phases inthe development of any software. Hence, there is a need to take much careon the elicitation and management of these requirements. Attributes playan important role in order to store and manage the important informationabout the requirements. There has been a lot of research performed inthe literature regarding the attributes of requirements engineering, but stillthere is a gap in the research that is concerned to requirement attributesin particular. Hence we focused more on identification and management ofthese requirement attributes. Objectives: In the current thesis, we focused mainly on the requirementattributes used in the companies and how they are managed. The majorobjectives we have framed in order to achieve our aim are: 1. To identify the publication trends in the literature of requirementsengineering that mainly focus on requirement attributes. 2. To identify the requirement attributes that are used by the softwarecompanies which includes both global attributes and project specificattributes. 3. To investigate how the requirement engineering models impact theselection of requirement attributes in companies. 4. To identify the phase and sequence of the requirement attributesbased on the four phases (elicitation, analysis, documentation and validation)of requirements engineering. 5. To investigate how the requirement attributes help in documentingand managing the continuous changes to requirements. Methods: In this thesis, we have performed Systematic Mapping Study(SMS),Systematic Literature Review (SLR) and Survey methods in order to achieveour aim and objectives. SLR is performed through the snowballing procedurebased on the guidelines of Wohlin[1].SMS is performed based on theguidelines of petersen et al.[2]. The main aim of the SMS is to identifythe publication trends in the literature on requirements engineering. Themain aim of SLR is to extract important information about the RE modelsand changes in requirements engineering. The main aim of the Survey is tovalidate the information retrieved from the SLR. Results: 83 requirement attributes were identified through the SLR outof which 15 attributes are in common. These 15 attributes are includedin the survey questionnaire. From these attributes, ID and description areidentified as most commonly used attributes from the survey. Publication trends related to requirement attributes are observed from the past 25 yearsrequirement attributes. From the survey, it is observed that there is a highimpact of RE models on requirement attributes. It is also observed thatmaximum number of attributes is stored in the form of documents and indatabases by the companies and the attributes are generally documented inanalysis phase and in specification phase. Results from the survey indicatedthat there is no particular sequence to document the attributes and theyare identified and documented based on the needs. Conclusions: This thesis lists different attributes that are used by thecompanies and also gives important information about the requirement attributesin detail that is close to the practical scenarios. It also gives scopefor further researches related to requirement attributes. This thesis helpthe practitioners to know the importance of consideration of requirementattributes in developing a project and its advantages. This work can beextended further by considering large number of attributes and retrievingresponses and opinions by large population.

Background: Technical debt(TD) is incurred when developers accept compromises in a system in one dimension to meet urgent demand in some other dimensions (e.g., a deadline). If technical debt is not managed correctly, it will cause hidden danger to software’s long term success. It does not get enough attention when TD applies to the requirements engineering. Objectives: In this study, we investigate the current state of requirements debt(ReD). We aim to give a precise definition of ReD. We also focus on the factors that can induce ReD in the requirement engineering and requirement management process. Moreover, we want to summarize the measurement tools to detect and locate the ReD. Finally, we try to find approaches and ideas to manage ReD. Methods: We conducted a systematic mapping study (SMS) and a survey for all of the objectives. When performing the systematic mapping study, we applied snow- balling method to ensure we find related and enough papers. Results: According to the analysis and results of SMS and the survey, we concluded the definition of requirements debt. We also presented and classified 54 ReD induced factors into 8 categories. 10 ReD measurement techniques searched from literatures were listed with a brief description for each one, suggestions from software practi- tioners on ReD detection also gathered and displayed. The management techniques and theoretical suggestions were presented based on related factors. Conclusions: From research result, we find academia and industry lay different emphasises on how to manage ReD. To stimulate Industry pay more attention on control and manage ReD effectively, this paper calls for the two sides to work on the same point.

In order to cope with the operational risk resulting from drastic changes of financial market and diversified financial products (e.g. product design, training for sales personnel, risk management, etc.), Basel Committee on Banking Supervision¡]BCBS¡^decided that, under the minimum capital requirement, the banking groups are requested to increase the operational risk capital requirement, which will be implemented in the banking business by the end of 2006. The operational risk, defined by Basel Committee on Banking Supervision¡]BCBS¡^is ¡§the risk of loss resulting from inadequate or failed internal processes, people and systems or from external events¡¨. Although the scope of the operational risk has been narrowed down, the definition is still ambiguous to the banking groups. The operational risk needs to be clearly distinguished from the credit risk and the market risk such that categorization and quantification of the banking business can be realized. In fact, besides the natural disasters and irresistible causes, most of operational risk results from the failure of internal control and policy execution rather than from causes of systemic risks. Therefore, it is inappropriate to apply the same risk coefficient to the banking groups without taking their operation quality and scale into consideration. It is also questionable that the capital requirement can entirely offset the financial loss caused by the operational risk. In order to minimize the loss from the operational risk, risk mitigation should be applied. The strategy is to collect the historical data and information to establish a database, which is commonly found in the following four approaches in performing the operational risk capital requirement¡GBasic Indicator Approach ¡]BIA¡^, Standardized Approach¡]SA¡^, Alternative Standardized Approach¡]ASA¡^, Advanced Measurement Approaches¡]AMA¡^. Hence, it is inevitable that the banking groups need to invest substantial amount of manpower and capital, which could become a huge burden to the banking groups but is the price to pay to arouse the banking groups¡¦ attention to reinforce the risk management and evaluation. Establishment of the systems and execution of the policies will not always be impeccable and there will always be room for discussion and modification. Nevertheless, the ultimate goal for the management is to well-operate the banking groups and maximize the shareholders benefit.

Software quality and reliability is a primary concern for successful development organizations. Over the years, researchers have focused on monitoring and controlling quality throughout the software process by helping developers to detect as many faults as possible using different fault based techniques. This thesis analyzed the software quality problem from a different perspective by taking a step back from faults to abstract the fundamental causes of faults. The first step in this direction is developing a process of abstracting errors from faults throughout the software process. I have described the error abstraction process (EAP) and used it to develop error taxonomy for the requirement stage. This thesis presents the results of a study, which uses techniques based on an error abstraction process and investigates its application to requirement documents. The initial results show promise and provide some useful insights. These results are important for our further investigation.

Today, software ecosystems have become transparent, allowing users to submit issue reports and new feature requests to the development team. The more permeable boundaries of ecosystems provide an open culture paradigm where stakeholders, customers, developers and other user groups have the access to participate during all phases of requirement development. One example of this open culture in software ecosystems is found in work item discussions, which are aimed to improve how requirements are elicited, analyzed and validated. In this thesis, we investigate who participates in requirements discussions, identifying and focusing on emergent contributors; discussants that are not officially part of the development team or required to participate, but contribute to work item discussions. We report form a case study of online requirement discussion in IBM’s collaborative lifecycle management. We find that external contributors emerge frequently during discussions and that they mediate the clarification of requirements. Our results indicate that it is important for emergent contributors to be involved early in the requirements process, otherwise there is a negative effect on the work items’ progress. We discuss the implications of our findings for both practitioners and researchers with suggestions for future studies. / Graduate / 0984 / 0291 / 0790 / aminah.yussuf@gmail.com

The electronic system in automobiles has become more important in providing safety, comfort and entertainment, at the same time less harmful to the environment. Due to the fact that there are varieties in automobile electronic devises, product development has become more complex. For example, shortening product development period while maintaining quality and fulfilling requirements of each company are all important issues. The development of automobile electronic products cannot only emphasize on functionality but also need to be more customer-oriented to fulfill the needs and expectations of the users. The initial phase of product development should focus on confirming the types of products with clients in order to develop and manufacture into what have been expected. The goal of product development expected by the market has obvious differences with the actual products that have been manufactured. The reason for the differences is the emphasis on functionality during the initial phase of product development. Also, the development process has focused mainly on technological development instead of customer expectations and the changes that occur during the product life cycle, which brings in the need for ¡§Requirements Management.¡¨ Problems such as large amount of development cost, compensation, loss of order and reliability can be resolved through the application of ¡§Requirements Management.¡¨ Through observation and interviews with management team and project managing engineers, what is lacking is the method of demand analysis for system engineer of suppliers during the demand analysis stage to better analyze customer needs and to combine with existing system; thus managers can utilize the requirement analysis method to familiarize with the product. In addition, system engineers can better distribute resources and confirm demands. Based on the architecture-oriented model for auto electrical products, demand analysis method can clearly integrated different aspects, including structural and behavioral. These statistics can be utilized in the following phases during project development, such as system design, production, testing, and proofing stages, especially where integration with software, electrical and structural system is important and complex for the development of auto electrical products. The architecture-oriented model can maintain consistency and can be traceable along with the requirements model.

Problems of requirements which are identified in the earlier phase of a software development project can deeply affect the success of the project. Thus studies which aim to decrease these problems are crucial. Automation is foreseen to be one of the possible solutions for decreasing or removing some of the problems originating from requirements. This study focuses on the development and implementation of an automated tool that will generate requirements in natural language from business process models. In this study, The benefits of the tool are discussed, and the tool is compared with other software requirement s related tools with respect to their functionality. The developed tool has been tested within a large military project and the results of using the tool are presented.

Reikalavimų inžinerija yra bene svarbiausias etapas informacinės sistemos kūrime. Tik tikslus reikalavimų specifikavimo proceso valdymas leis sėkmingai projektuoti, realizuoti ir įdiegti informacines sistemas kompiuterizuojamose srityse. Dažnai neefektyvus reikalavimų rinkimo procesas tampa projekto nesėkmės ar programinės įrangos defekto pagrindu. Be to, aptiktų netikslumų pašalinimo kaina kyla eksponentiškai, kai jie atrandami vėlyvosiose projekto stadijose. Todėl įmonės ar asmenys, siekiantys pagerinti projekto kokybę ir produktyvumą, turėtų ypatingai atkreipti dėmesį į reikalavimų valdymo procesą. Pastebėta, jog reikalavimų specifikavimo procesas vis labiau kompiuterizuojamas, o reikalavimų valdymo įrankių bei šablonų naudojimas gerina reikalavimų specifikacijos ir būsimo produkto kokybę. Šis magistrinis darbas yra skirtas reikalavimų specifikavimo šablonų pagrindu eksperimentiniam tyrimui ir jo vertinimui. / The usage of computers takes more important place in our modern life. It was noticed that more and more enterprises use requirement management tools and specification templates to increase quality of requirement specification and projects. Very often ineffective requirements-gathering processes are the source of project failures and software defects. In addition, the cost of fixing defects rises exponentially as their discovery occurs later in the development process. However, a solid requirements process is fundamental to an effective overall process, and companies seeking increased quality and productivity should start with the requirements process. The intention of this work is to make the experimental research of requirements specification using templates and evaluate it.

No description available.

The usage of computer networks has increased enormously recently due to many benefits; it facilitates data distribution speed, long distance communication and industrial system control. Due to these reasons, industry systems have started to use computer networks for system control and data transmission. Meanwhile, the limitations of network devices also raise many challenges for network system configuration. To have the best optimized network system, we need to study the network system by performing experiments. However, experiments on the real systems could be expensive and dangerous. Therefore, we need a model to represent the behaviours of the system. This thesis work uses object-oriented acasual modelling language Modelica to model a local area network system, and the development is performed in OpenModelica, an open source Modelica-based modelling and simulation environment. The simulation results are analysed and verified by using a separate requirement verification model.