Localization of A Flexible and Pragmatic Requirements Engineering Framework for SME
This frame  work is very hard to implement in an organization which already has process implemented such as CMMI as this framework requires an organization which has no or less processes defined as it suggests a new paradigm for risk assessment and management. The framework described here provides a complete approach for improving the requirements process. It incorporates enhancements/suggestions for the requirements process and ease decision making by providing experience data on the improvement suggestions. The motivation for coming up with this framework comes from working with small and medium sized enterprises, but the question is how much it will cost in order to accommodate this frame work in any small organization. I will suggest that the minimum activities from this framework will be taken out and used in Pakistan’s Software industry for companies who are not using any requirement engineering framework.
Besides this if there are any tools available in the market at low cost for managing requirement management risks is feasible rather than implementing this framework as it utilizes lots of efforts and expertise in the software engineering field.
Another vital part for the implementation of this model is you must have to record requirements somewhere from where we can keep log of requirement related changes.
What I experienced while implementing this framework was that it takes a lot of time and is not good for projects which are evolutionary in nature i.e. there was no time available and no resources for analysis.
Keeping in mind the Pakistan’s software industry there are always schedule related issues and even though the author of the paper suggests that it is cost effective and easy to implement but it requires time and circumstances which require the framework to be build on organization basis rather than on project.
Analysis of A Flexible and Pragmatic Requirements Engineering Framework for SME
This model  was validated and calibrated by the author of research paper , but my experience of implementing this model is not satisfactory enough to recommend this model for use in small and medium organizations, it is a best fit for organizations which are willing to spend money on quality and risk management and are a little more medium sized.
Localization of Requirement Reliability Metrics for Risk Assessment
This risk management approach  basically tries to connect the impact of quality attributes and relates them to the impact of risk to the requirements phase, the question here arises that why we have to wait until the certain iterations or versions of requirements are done and then we are able to assess if are going with the project or not and this also requires that the requirements are managed and stored in a repository or issue manager or source safe and their change history is managed in order to keep track and create the data necessary for this model.
I applied this approach to my current project and the results were pretty good as the approach gave the risk factor and I was able to identify the project risks better. This was easy to implement and very less effort was required to do this task but the only issue I faced was the maintenance of history although we have tools to take care of that problem but they don’t categorize requirements as per this model.
Localization of Managing Requirements Engineering Risks, an analysis and synthesis of literature
This is a very good model for risk management in the early phases of the requirement engineering and it is based on the expertise of the resource to rate requirements in the table which is adopted by McFarlane’s template. I implemented this model in my project as it was very easy to use and nothing was needed except a little time and we came to know what areas of project we need to focus on and the areas which need attention.
This model is pretty useful for small and medium organizations as it does not take much effort and low cost factor makes it very do able for organizations which do not want to spend money and time on this issue.
This model identifies the areas which need attention and suggests different techniques to cater the issue.
1. Mark Keil, Paul E. Cule, Kalle Lyytinen, and Roy C. Schmidt: A framework for identifying software project risks.
2. Amir Akhter Jamili: Requirement Reliability Metrics for Risk Assesment
3. Juan C. Nogueira, Luqi, Valdis Berzins and Nader Nada: A Formal Risk Assessment Model for Software Evolution
4. Thomas Olsson, Joerg Doerr, Tom Koenig and Michael Ehresmann: A Flexible and Pragmatic Requirements Engineering Framework for SME
5. Juan Carlos Nogueira, Luqi and Swapan Bhattacharya: A Risk Assessment Model for Software Prototyping Projects
6. Say-Wei Foo and Arumugam Muruganantham: Software Risk Assessment Model
7. By Mira Kajko and Janaa Nyfjord: State of Software Risk Management Practices
8. Lars Mathiassen, Timo Sarinen, Tuure Tuunanen, Matti Rosi: Managing Requirements Engineering Risks an Analysis and Synthesis
9. Borland: Mitigating Risk with Effective Requirement Engineering
10. Don Gotterbarn and Simon Rogerson: Responsible Risk Analysis for software development: Creating the software development impact statement
11. Keshnee Padayachee : An interpretive study of Software Risk Management Perspectives
12. Dipak Surie:Evaluation and Integration of Risk Management in CMMI and ISO/IEC 15504
13. C Williams: The CMMI RSKM Process Area as a Risk Management Standard
14. Roger S. Pressman: Software Engineering A Practitioner’s Approach