Prioritizing Stakeholders Role in Prioritization Process
|
|
- Melvin Gregory
- 6 years ago
- Views:
Transcription
1 Prioritizing Stakeholders Role in Prioritization Process Nasir Mehmood Minhas, Muhammad Aasem, Qaim Khan Khtatak, Sumaira Jamsheid University Institute of Information Technology (UIIT), Pir Maher Ali Shah Arid University of Arid Agriculture (PMASUAAR), Rawalpindi, Pakistan. Abstract The quality requirements of a software system have great concerns with the decisions made by stakeholders about them. Not all stakeholders have same approach toward each requirement. Even some core requirements might not be of any worth to some stakeholder. This problem can greatly reduce the quality of prioritization outputs. In this paper a technique has been presented to prioritize stakeholders roles by considering two elements i.e., Stakeholder Profile Weight (SPW) and Requirement Specific Stakeholder Weight (RSSW). The result of given technique has been discussed theoretically and assure quality improvement in software requirements prioritization. 1. INTRODUCTION Software requirements prioritization is a complex communication and negotiation process that involves the participation of many stakeholders [5]. They may have many different attributes that could make their views different from each other about a requirement. A person closer to the domain of a specific requirements set can make better decision about its priority than anyone else. Moreover, broader understanding of overall project/organization can also lead a one toward making good decision about the requirement. Due to these facts, it can be concluded that not all stakeholder have same importance for every requirement. There are many prioritization techniques that are based on stakeholders opinions to prioritize the software requirement. The techniques like Numerical Assessments, Hundred dollars test, Top Ten National Science Conference 2012, Rawalpindi Pakistan, January
2 requirements, Ranking, etc [1, 6, 7, 8, 9] are strongly based on stakeholders participation but none of them have focused their attention to analyze them. Without properly considering their role in prioritization, the resultant prioritized requirements would have much difference in actual result. Therefore, it is suggested to prioritize stakeholders in order to prioritize the requirements sufficiently in more qualitative way. In this paper, we suggest to identify and classify the role of each stakeholder according to their intensity toward the relationships with requirements. Prioritizing the different rules of stakeholders in requirement engineering have many benefits like right people can be used in the right way to take better decision about their related and most concern field of requirement. The next section presents an overview of related literature that advocate prioritizing stakeholder in prioritization process. In section 3, a brief discussion has been presented to explain the two core elements of the proposed technique. Using these two elements, section 4 presents the calculation of final value of each requirement with the help of pseudo code. Finally the whole discussion has been concluded and future direction has been set. 2. LITERATURE REVIEW The nature of software requirement is multifaceted. A set of requirement may be of less worth from one perspective highest of worth from another perspective [17]. In such a case we should not give equal weight to each view; rather they shall be given worth according to their association. These views can be further linked with different stakeholders or group of stakeholders that shall be prioritized. Giesen and Volker argue that not all stakeholders have same importance. In case of large software projects; a large number of stakeholders have similar number of different view and expectations from the underlying project. They all play their roles to make the project successful. But their different preferences and expectations have high degree of changes to conflict each others views [13]. This phenomenon reveals the fact that requirements have dependencies and correlations between underlying attributes, whose understandability is essential for successful projects. Lehtola et al [12] discussed some challenges in requirements prioritization. It is stated that some customers might not want to prioritize their requirements with the fear that only top most would be entertained by developers. Similarly, developers do not want to disclose that they are not able to
3 implement all the requirements. In some cases, when there are very few strong stakeholders whose wishes are very hard to neglect, it would be hard to prioritize their roles. Other problems like political issues and interdependencies between requirements might also create difficulties in prioritization process for stakeholders. According to Lubars et al. [3], almost none of the companies in their study had sufficient understanding of assigning, modifying, and communicating priorities effectively to other project members. This means that they were mostly expert of one or few specific field and so were not fully capable to assess each requirement exactly. This fact also reveals that the hierarchy of users can assess a hierarchy of requirements. A simple hierarchy of functional users has been illustrated in figure 1. Users at level 1 have breadth knowledge of all requirements then level 2 and level 2 users have broader information then level 3, so on and so forth. There are also some literatures that have identified and discussed different concerns of stakeholders in software requirement engineering. Like Pacheco et al state that each software project may have different types of stakeholders and their appropriate selection has a strong impact on the quality of software requirements [14, 15]. The quality the software project is consequently affected by these requirements. Analyzing the stakeholders preferences in requirement engineering has been addressed in [13] that suggest prioritizing stakeholders in requirement engineering. Moreover, some classification schemes have also been discussed in [10, 11, 16] that can be used as parameters in prioritizing them. 3. STAKEHOLDERS WEIGHTING ELEMENTS A stakeholder may be defined as a person or organization, which influences system s requirements and/or impacted by that system [2]. The stated influence and resultant impact in the definition are the focus interests of this technique. We propose two essential elements to be included when software requirements are to be prioritized by human involvements. These two elements shall be calculated in order to calculate the final priority values of each requirement. The first element is called as Stakeholder Profile Weight (SPW) that is calculated against each stakeholder to assess each individual s weight in the overall project. Second element is Requirement Specific Stakeholder Weight (RSSW) that varies requirement to requirement.
4 A. STAKEHOLDER PROFILE WEIGHT (SPW) 1) Mapping View Parameters on Scale A stakeholder can be associated with a software project in more than one aspect. At the same time, he/she might be end-user, in-directly involved; yet has broader required knowledge to take better decisions to make it successful. But one of the phenomenon in assessing the right opinions of multiperson dependent decision is answering the question, who shall be preferred on whom? One of the best way to answer this question is to find a generalize answer that could be altered according to project requirement. Following this idea, we present multi-role illustration of each stakeholder. In this regard, we searched stakeholder s grouping from different perspectives in the literature and found some good findings. According to Martin and Roel [10], stakeholders can be assigned to a group like critical, major, and minor according to their impact on overall project. Another classification can be of End-users, managers, customers and domain experts [16]. The direct and indirect divisions of Stakeholders can also consider revealing the impact of his/her involvement. Figure 2 presents an illustration of stakeholder from different viewpoints discussed earlier. These are few viewpoints to understand the basic concept and subject to be altered to reflect the project need. Once they are identified, the next step is to map it on a scale ranges from 0 to 1 to rank the importance of each view s parameter. Here parameter is referred to a single value of a viewpoint. The mapping process would be simply an assigning process of each view s parameter to the scale values such that they influence the weight of stakeholder s opinion. In figure 3, we have mapped these parameters to form a simple example. The above mapping has been derived from figure 2 and can be express as shown in table 1. 2) Assessment of hierarchal levels A company s organograms clearly shows the hierarchy of personnel roles with respect to their relationships in rank-wise. This is also a very helpful tool in assessing the quantitative value of each employee regarding their authority. Moreover, it represents the breadth understanding of knowledge about overall organization procedure. In order to calculate the weight of each stakeholder, it is important to include their weights of authority in order to reflect the importance of their decision. The
5 greater authority value is also a factor of greater responsibility and hence more preference shall be given. The other aspect related to this hierarchy is the breadth of functional area the person is looking after. A stakeholder who is one of the last nodes of hierarchy might have narrow view as compare to upper level regarding overall organizational procedures understanding. Considering such a factor becomes important when dealing with requirements that have stakeholders from general to specific domain areas. A domain specialist can better express the value of a given requirement if it is most closed to his/her area. A generalist, on the other hand would express the value of a given requirement in the light of overall project or from organizational view point. Therefore, including this factor will improve the quality of stakeholder s judgments he/she would make about a requirement. In order to imitate the effect of stakeholders hierarchal values of both Overall Understanding and Authority level, we propose a scale shown in figure 4. It consists of two pyramids displaying mirror reflection to each other. The upper opposite pyramid shows the breadth of overall organization knowledge. The top portion of upper pyramid refers to the group of stakeholders having at-least clear abstract understanding of all procedures. They have clear picture about the project and/or about the company. Their understanding is at generic level as compared to the lower levels. The stakeholders at lower levels have comparatively narrow view about overall organization but have broader understanding about some specific domains in organization. The lower pyramid shows the organization s authority level. Stakeholders at upper level have the most limited authority as compare to the lower levels. In this illustration, the number of groups in each pyramid is same that are also subject to be changed. B. REQUIREMENT SPECIFIC STAKEHOLDERS WEIGHT (RSSW) The second essential element of this technique is the calculation of Requirement Specific Stakeholders Weight (RSSW). Its significance has been realized due to the fact: not every requirement is concerned to each stakeholder at the same intensity. Perhaps, there might be some requirements that have no worth
6 to some key stakeholders but have core importance to another group of key stakeholders. Therefore, keeping such scenarios into consideration, we recommend to include the effect of RSSW to reflect the association of each requirement with each stakeholder. A requirement can be associated with a stakeholder using two aspects i.e., Relationship and Distance. 1) Relationship The Relationship depicts the domain area association of a stakeholder with a given requirement. It has strong link with domain area of stakeholders. In order to prevent the negative effect of unconcerned stakeholders opinion, we can use followings weights: Strong: if the requirement lies exactly in the specific domain of a stakeholder. In this case highest weight shall be given in the scale. Dependent: if the requirement is not of stakeholder s specific domain but due to this requirement his/her specific domain requirement may affect. Weak: if the requirement has no concern in the specific domain of a stakeholder. In this case zero or lowest weight shall be given in the scale. 2) Distance The hierarchal nature of organization s functions might lower the role of RSSW, if we use Relationship factor without Distance factor. People at the lowest nodes of hierarchy might have strong depth knowledge compared to the upper ones. Therefore their distance shall be calculated from the specific domain. This can be calculated by just considering the grade level. 4. PRIORITIZING STAKEHOLDER BY SPW & RSSW At the point when we have assessed the weight property of stakeholder role, it is time to evaluate the weight of each stakeholder. The evaluation procedure is just mapping the stakeholders against the scales and aggregating the figures that will be the weights of each stakeholder referred as SPW. In figure 5, we have illustrated a simple example of evaluating the SPWs of three stakeholders. There are three scales used in this example i.e., Viewpoint parameters, Overall Understanding (of all requirements) and Authority level. All of these scales are in range 0 to 1. We have mapped each
7 stakeholder against each of these three scales one by one according to their related attributes. The strong relation has been referred a value more closely to 1 and 0 to represent weaker association. The aggregated value of each stakeholder i.e., SPW has been calculated by adding the association value of each mapping value (represented by arrows). This final value shall be referred by SPW and express the quantitative value of each stakeholder opinion with respect to their role. We can also use SPWs to prioritize the stakeholders in this way. But this prioritization shall be at overall project level not necessarily on each requirement level. Our proposed approach suggests to calculate the priority value of each record on both elements i.e., SPW and RSSW. Therefore, next we calculate RSSW using SPW. As discussed earlier in previous sections that not all requirements have same significance for each stakeholder and hence they shall be associated with a stakeholder using two aspects i.e., Relationship and Distance. We have also discussed their significance in detail in previous sections. Regarding their calculation toward evaluating final priority values; we propose to use a simple template like a one presented in figure 6. It contains four parts 1) Stakeholder role (can be either name or ID) along with his/her SPW value. 2) Description of each requirement that can is required to be prioritized, 3) A value column for each requirement where the stakeholder is supposed to write a value based on a given scale and 4) RSSW based fields so that we can calculate the final priority. The calculation of final priority value for can be obtained by finding the average of each requirement s suggested values regarding stakeholders opinion. Elements SPW and RSSW are added up and multiplied by the given value such that it increase its frequency. The result of this manipulation is divided by number stakeholders to find the final value. Using this value all requirements can be prioritized. For simplicity; the following pseudo-code is presented to understand and calculate of final priority values of each requirement.
8 Stakeholder={S 1,S 2,..,S m } Requirement={R 1,R 2,..,R n } for r=1 to n for s=1 to m W= W + Requirement[r][s].Value (Stakeholder[s].SPW + Requirement[r][s].RSSW) * Requirement[r][s].Value AvgPriority[r]= W/m 5. CONCLUSION AND FUTURE WORK In this paper we highlighted the significance of prioritizing stakeholder roles in software requirement prioritization. Different aspects of a stakeholder have been discussed and their impact has been discussed on final priority values. Two main elements were identified to prioritize software requirements based on stakeholders i.e., Stakeholder Profile Weight (SPW) and Requirement Specific Stakeholder Weight (RSSW). SPW is used to calculate the overall weight of each individual while RSSW is calculated for each requirement using SPW. REFERENCES [1] A. Aurm, Engineering and maangeing software requirements. Springer. [2] IEEE Std , Standard Glossary of Software Engineering Terminology, IEEE Press, [3] Lubars, M., Potts, C., Richter, C.: A review of the state of the practice in requirements modelling. In: Proceedings of IEEE Symposium on Requirements Engineering (RE 93), IEEE Computer Society Press (1993) [4] Karlsson, J., Ryan, K.: A cost-value approach for prioritizing requirements. IEEE Software 14 (1997) [5] Aurum, A., Wohlin, C.: The fundamental nature of requirements engineering activities as a decisionmaking process. Information and Software Technology 45 (2003) [6] J. Karlsson, "Software Requirements Prioritizing", Proceedings of the 2nd International Conference on Requirements Engineering (ICRE'96), 1996, pp
9 [7] A. Ahl, "An Experimental Comparison of Five Prioritization Techniques - Investigating Ease of Use,Accuracy, and Scalability", Master Thesis No. MSE , BTH, [8] S. Jenny, Early Requirements Prioritization Technique (best practice white paper).version 1, December 2008 [9] L. Lehtola and K. Marjo. Suitability of requirements prioritization methods for market-driven software product development, John Wiley & Sons, Ltd.2006 [10] G. Martin and W. J. Roel, Guest Editors' Introduction: Stakeholders in Requirements Engineering, IEEE Software, March 2007,v.24 n.2, p [11] Davis, A., M. The Art of Requirements Triage, IEEE Computer, 2003, 36(3), pp [12] Lehtola, L., Kauppinen, M., and Kujala, S. (2004): Requirements Prioritization Challenges in Practice'. Proceedings of 5th International Conference on Product Focused Software Process Improvement, pp [13] Giesen J. and Volker A. Requirements Interdependencies and Stakeholders Preferences, Proceedings of the IEEE Joint International Conference on Requirements Engineering (RE 02) [14] Pacheco, Carla Garcia, Ivan, Effectiveness of Stakeholder Identification Methods in Requirements Elicitation: Experimental Results Derived from a Methodical Review. Eight IEEE/ACIS International Conference on Computer and Information Science 2009 [15] Pacheco, Carla & Garcia, Ivan. Stakeholder Identification Methods in Software Requirements: Empirical Findings Derived from a Systematic Review [16] Kotonya, G. and Sommerville, I. (1998) Requirements Engineering: processes and techniques. John Wiley. [17] Aasem, M, Ramzan M, Jaffar, I, Multi Faceted Requirements Classifications for Prioritization.
10 Figures and Tables Figure 1. Hierarchy of functional users Figure 2. Different concerns of a stakeholder in a project Internal External Direct user Indirect user Involved in Development Not Involved in Development Decision makers Domain Experts Managers End-Users Customers Baseline Satellite Supplier Critical Major Minor
11 Figure 3. A mapping example of SPW Table 1. Tabular illustration of SPW Viewpoint Parameter Scale value Viewpoint 1 Decision makers 0.9 Domain Experts 0.8 Managers 0.7 End-Users 0.4 Customers 0.2 Viewpoint 2 Viewpoint 3 Direct user 0.5 Indirect user 0.3 Internal 0.5 External 0.3 Viewpoint Involved in Development
12 Figure 4. The levels of hierarchy mapped on scales
13 Figure 6. Assessment Of Requirements Specific Stakeholder Weight (RSSW)
Requirements Engineering
Requirements Engineering Professor Ray Welland Department of Computing Science University of Glasgow E-mail: ray@dcs.gla.ac.uk The Importance of Requirements Identifying (some) requirements is the starting
More informationA Survey on Prioritization Methodologies to Prioritize Non-Functional Requirements
A Survey on Prioritization Methodologies to Prioritize Non-Functional Requirements Saranya. B. Department of Computer Science and Engineering Sri Krishna College of Technology, Coimbatore, Tamilnadu, India
More informationRequirements Prioritization Challenges in Practice
Requirements Prioritization Challenges in Practice Laura Lehtola, Marjo Kauppinen, and Sari Kujala Helsinki University of Technology, Software Business and Engineering Institute, P.O. Box 9210, FIN-02015
More informationUsing Architectural Models to Predict the Maintainability of Enterprise Systems
Using Architectural Models to Predict the Maintainability of Enterprise Systems Robert Lagerström*, Pontus Johnson Department of Industrial Information and Control Systems Royal Institute of Technology
More informationComparison of various Elicitation Techniques and Requirement Prioritisation Techniques
Comparison of various Elicitation Techniques and Requirement Prioritisation Techniques Nilofar Mulla Department of Information Technology, MIT Pune 38, Maharashtra, India Sheetal Girase Assistant Professor,
More informationversion NDIA CMMI Conf 3.5 SE Tutorial RE - 1
Requirements Engineering SE Tutorial RE - 1 What Are Requirements? Customer s needs, expectations, and measures of effectiveness Items that are necessary, needed, or demanded Implicit or explicit criteria
More informationEvaluation method for climate change mitigation instruments
Evaluation method for climate change mitigation instruments Popi A. Konidari* National and Kapodistrian University of Athens Department of Informatics and Telecommunications pkonidar@kepa.uoa.gr Abstract.
More informationDifferent Approaches of Software Requirement Prioritization
International Journal of Engineering Science Invention ISSN (Online): 2319 6734, ISSN (Print): 2319 6726 Volume 5 Issue 9 September 2016 PP. 38-43 Different Approaches of Software Requirement Prioritization
More informationA Comparison among Various Techniques to Prioritize the Requirements
A Comparison among Various Techniques to Prioritize the Requirements Ritu 1 and Dr. Nasib Singh Gill 2 1 Department of Computer Science and Applications, M. D. University, Rohtak-1241, Haryana, India ritudhankhar8@gmail.com
More informationChapter 5. Job-Based Structures and Job Evaluation
Chapter 5 Job-Based Structures and Job Evaluation Learning Objectives Job-based structures: Job evaluation Defining job evaluation: Content, value, and external market links How-to : Major decisions Job
More informationIntroduction. Analytical Hierarchy Process. Why AHP? 10/31/2011. The AHP is based on three principles: Decomposition of the decision problem
Introduction A multi-criteria decision making process. Analytical Hierarchy Process The analytical hierarchy process (AHP) is a comprehensive, logical and structured framework. 56:134 Process Engineering
More informationAbstract Number: Abstract Title: Supplier Selection with Component Commonality
Abstract Number: 007-0144 Abstract Title: Supplier Selection with Component Commonality R Samuel Sale Louisiana Tech University 407 Kennon Lane Apt 39 Ruston LA, 71270 rssale@hotmail.com POMS 18 th Annual
More informationChapter 4 Fuzzy Analytic Hierarchy Process of Green Supply Chain Management in the Pharmaceutical Industry
Chapter 4 Fuzzy Analytic Hierarchy Process of Green Supply Chain Management in the Pharmaceutical Industry 4.1 Introduction During the past decade with increasing environmental concerns, a consensus, the
More informationD.P.M. METHOD - A PERFORMANCE ANALYSIS INSTRUMENT OF A STRATEGIC BUSINESS UNIT
D.P.M. METHOD - A PERFORMANCE ANALYSIS INSTRUMENT OF A STRATEGIC BUSINESS UNIT Ionescu Florin Tudor Bucharest Academy of Economic Studies Marketing Faculty Considering the uncertain economic conditions,
More informationValidation of NORM (Needs Oriented Framework for Producing Requirements Decision Material) Framework in Industry
Master Thesis Software Engineering Thesis no: MSE-2012:102 09 2012 Validation of NORM (Needs Oriented Framework for Producing Requirements Decision Material) Framework in Industry Salman Nazir Rizwan Yousaf
More informationRequirements Prioritization Techniques Comparison
Modern Applied Science; Vol. 12, No. 2; 2018 ISSN 1913-1844 E-ISSN 1913-1852 Published by Canadian Center of Science and Education Requirements Prioritization Techniques Comparison Amjad Hudaib 1, Raja
More informationAIS Electronic Library (AISeL) Association for Information Systems. Eswar Ganesan Infosys Technologies,
Association for Information Systems AIS Electronic Library (AISeL) AMCIS 2009 Proceedings Americas Conference on Information Systems (AMCIS) 2009 Key Performance Indicators Framework - A Method to Track
More informationTransactions on Information and Communications Technologies vol 11, 1995 WIT Press, ISSN
A quality assessment method for application management R.M. Hather, E.L. Burd, C. Boldyreff Centre for Software Maintenance, University of Durham, Durham, DEI 3EL, UK, Email: ames@durham.ac.uk Abstract
More informationBefore the Office of Administrative Hearings 600 North Robert Street St. Paul, MN 55101
Rebuttal Testimony Anne E. Smith, Ph.D. Before the Office of Administrative Hearings 00 North Robert Street St. Paul, MN 0 For the Minnesota Public Utilities Commission Seventh Place East, Suite 0 St.
More informationRequirements Validation and Negotiation
REQUIREMENTS ENGINEERING LECTURE 2014/2015 Dr. Sebastian Adam Requirements Validation and Negotiation AGENDA Fundamentals of Requirements Validation Fundamentals of Requirements Negotiation Quality Aspects
More informationApplying PSM to Enterprise Measurement
Applying PSM to Enterprise Measurement Technical Report Prepared for U.S. Army TACOM by David Card and Robert MacIver Software Productivity Consortium March 2003 SOFTWARE PRODUCTIVITY CONSORTIUM Applying
More informationRequirements Analysis, Modeling and Specification
Requirements Analysis, Modeling and Specification Requirements Analysis, Modeling and Specification Problem Carving the Solution Space Prioritizing Requirements What is a Model? Requirements Analysis,
More informationConduct a job evaluation
Work Essentials Home > Help and How-to > Work Essentials > Human Resources Conduct a job evaluation Applies to: Microsoft Office InfoPath 2003, Word 2003 By Susan M. Heathfield Your employees want fair
More informationRequirement Engineering Trends in Software Industry of Pakistan
Requirement Engineering Trends in Software Industry of Pakistan RoohulMunim Shakeel 1, Muhammad Shafi 1, Kamran Ghani 2 and Basharat Jehan 1 1 Department of computer software engineering, University of
More informationApplying Multi-Criteria Decision Analysis for Software Quality Assessment
Master Thesis Software Engineering Thesis no: MSE-2010-34 October 2010 Applying Multi-Criteria Decision Analysis for Software Quality Assessment - Systematic Review and Evaluation of Alternative MCDA Methods
More informationTowards a Development of an Operational Process for Software Requirements: Case study application for Renewable Energy Software s
, pp. 11-26 http://dx.doi.org/10.14257/ijseia.2015.9.7.02 Towards a Development of an Operational Process for Software Requirements: Case study application for Renewable Energy Software s Khalid T. Al-Sarayreh
More informationA Survey of Requirement Prioritization Methods
A Survey of Requirement Prioritization Methods Gurkiran Kaur Computer Science and Engineering Department Thapar University, India Seema Bawa Computer Science and Engineering Department Thapar University,
More informationUnderstanding the Current Situation of E-Government in Saudi Arabia: A Model for Implementation and Sustainability
Understanding the Current Situation of E-Government in Saudi Arabia: A Model for Implementation and Sustainability Majed Alfayad and Edward Abbott-Halpin School of Computing, Creative Technology, and Engineering,
More informationThe risk assessment of information system security
The risk assessment of information system security Miroslav Baa, PhD University of Zagreb, Faculty of Organization and Informatics, Varaždin, Croatia, miroslav.baca@foi.hr Abstract Every organisation today
More informationA RANKING AND PRIORITIZING METHOD FOR BRIDGE MANAGEMENT
A RANKING AND PRIORITIZING METHOD FOR BRIDGE MANAGEMENT Saleh Abu Dabous and Sabah Alkass Department of Building, Civil and Environmental Engineering, Concordia University, Rm: EV-6139 1455 de Maisonneuve,
More informationRequirements Elicitation
Elicitation Who are the stakeholders in determining system requirements, and how does their viewpoint influence the process? How are non-technical factors such as political, social, and organizational
More informationSoft Systems Methodology for Hard Systems Engineering - The Case of Information Systems Development at LIT/INPE/BRAZIL
Soft Systems Methodology for Hard Systems Engineering - The Case of Information Systems Development at LIT/INPE/BRAZIL Ana Claudia de Paula Silva 1, Geilson Loureiro 1 Abstract The Soft Systems Methodology
More informationBaselining Software Processes as a Starting Point for Research and Improvement
Baselining Software Processes as a Starting Point for Research and Improvement Thomas Olsson and Per Runeson Dept. of Communication Systems Lund University Box 118, SE-221 00 Lund, Sweden [thomas.olsson
More informationRequirements Engineering
Requirements Engineering Software Engineering Andreas Zeller Saarland University Requirements Engineering The Real World Requirements Engineering A description of what the system should do (but not how)
More informationTRANSPORTATION ASSET MANAGEMENT GAP ANALYSIS TOOL
Project No. 08-90 COPY NO. 1 TRANSPORTATION ASSET MANAGEMENT GAP ANALYSIS TOOL USER S GUIDE Prepared For: National Cooperative Highway Research Program Transportation Research Board of The National Academies
More informationWeighted Summation (WSum)
Table of Contents Weighted summation...1/6 1 Introduction...1/6 2 Methodology...1/6 3 Process...1/6 3.1 Value functions and standardization methods...2/6 3.2 Weighting methods...2/6 4 Review...3/6 4.1
More informationSuccess Factors in ERP Systems Implementations. Result of Research on the Polish ERP Market
Association for Information Systems AIS Electronic Library (AISeL) AMCIS 2004 Proceedings Americas Conference on Information Systems (AMCIS) December 2004. Result of Research on the Polish ERP Market Piotr
More informationApplying Evaluate Marketing Processes Corporation Marketing Capability Maturity Model Evidence from Bursa Malaysia Market
Applying Evaluate Marketing Processes Corporation Marketing Capability Maturity Model Evidence from Bursa Malaysia Market Suseela Devi Chandran Phd Candidate, Institute of Malaysia & International Studies,
More informationResource allocation for strategic quality management: An analytic network process (ANP) model
Griffith Research Online https://research-repository.griffith.edu.au Resource allocation for strategic quality management: An analytic network process (ANP) model Author Alidrisi, Hisham, Mohamed, Sherif
More informationThe Project Planning Process Group
3 The Project Planning Process Group............................................... Terms you ll need to understand: Activity Activity attributes Activity list Activity on arrow diagram (AOA) Activity
More informationPrioritizing IT Projects: An Empirical Application of an IT Investment Model
Communications of the International Information Management Association, Volume 3 Issue 2 Prioritizing IT Projects: An Empirical Application of an IT Investment Model Adam D. Denbo California State Polytechnic
More informationA Metamodel for Collaboration Formalization
A Metamodel for Collaboration Formalization Loïc Bidoux 1,2, Frédérick Bénaben 1, and Jean-Paul Pignon 2 1 Mines Albi Université de Toulouse {loic.bidoux,frederick.benaben}@mines-albi.fr 2 Customer Innovation
More informationExamining and Modeling Customer Service Centers with Impatient Customers
Examining and Modeling Customer Service Centers with Impatient Customers Jonathan Lee A THESIS SUBMITTED IN PARTIAL FULFILLMENT OF THE REQUIREMENTS FOR THE DEGREE OF BACHELOR OF APPLIED SCIENCE DEPARTMENT
More informationAREA I: ASSESS NEEDS, ASSETS, AND CAPACITY FOR HEALTH EDUCATION
AREA I: ASSESS NEEDS, ASSETS, AND CAPACITY FOR HEALTH EDUCATION Competency 1.1: Plan Assessment Process 1.1.1 Identify existing and needed resources to conduct assessments. 1.1.3 Apply theories and models
More informationRequirements Engineering. Andreas Zeller Saarland University
Requirements Engineering Software Engineering Andreas Zeller Saarland University Communication project initiation requirements gathering Planning estimating scheduling tracking Waterfall Model (1968) Modeling
More information2013, IJARCSSE All Rights Reserved Page 392
Volume 3, Issue 11, November 2013 ISSN: 2277 128X International Journal of Advanced Research in Computer Science and Software Engineering Research Paper Available online at: www.ijarcsse.com Risk Analysis
More informationSTUDY UNIT 9 THE ORGANISATIONAL SYSTEM FOUNDATIONS OF ORGANISATIONAL STRUCTURE
STUDY UNIT 9 THE ORGANISATIONAL SYSTEM FOUNDATIONS OF ORGANISATIONAL STRUCTURE WHAT IS ORGANISATIONAL STRUCTURE An organisational structure defines how job tasks are formally divided, grouped and coordinated:
More informationEvolutionary Differences Between CMM for Software and the CMMI
Evolutionary Differences Between CMM for Software and the CMMI Welcome WelKom Huan Yín Bienvenue Bienvenido Wilkommen????S???S??? Bienvenuto Tervetuloa Välkommen Witamy - 2 Adapting an An Integrated Approach
More informationA Comparative Study of Requirements Engineering Process Model
ISSN No. 0976-5697 Volume 8, No. 3, March April 2017 International Journal of Advanced Research in Computer Science RESEARCH PAPER Available Online at www.ijarcs.info A Comparative Study of Requirements
More informationIntegrating Risk Management with Software Development: State of Practice
Integrating Risk Management with Software Development: State of Practice Jaana Nyfjord and Mira Kajko-Mattsson Abstract In this paper, we investigate the state of practice of integrating risk management
More informationHIA Report Guide December 2010 Prepared by Human Impact Partners for Health Impact Project HIA grantees
HIA Report Guide December 2010 Prepared by Human Impact Partners for Health Impact Project HIA grantees The following information is meant to provide a basic structure for your HIA report including the
More informationTIPS PREPARING AN EVALUATION STATEMENT OF WORK ABOUT TIPS
NUMBER 3 2 ND EDITION, 2010 PERFORMANCE MONITORING & EVALUATION TIPS PREPARING AN EVALUATION STATEMENT OF WORK ABOUT TIPS These TIPS provide practical advice and suggestions to USAID managers on issues
More informationMs. Maridel Piloto de Noronha, PAS Secretariat Via
October 7, 2015 Ms. Maridel Piloto de Noronha, PAS Secretariat Via email: semec@tcu.gov.br RE: Exposure Drafts ISSAI 3000 Performance Audit Standard; ISSAI 3100 Guidelines on central concepts for Performance
More informationThe Seven Areas of Responsibility of Health Educators Area of Responsibility I: ASSESS NEEDS, ASSETS AND CAPACITY FOR HEALTH EDUCATION COMPETENCY
The Seven Areas of Responsibility of Health Educators Area of Responsibility I: ASSESS NEEDS, ASSETS AND CAPACITY FOR HEALTH EDUCATION COMPETENCY 1.1. Plan Assessment Process 1.1.1 Identify existing and
More informationWhat are Requirements? SENG1031 Software Engineering Workshop 1. My Notes. System Overview: The Big Picture
What are Requirements? SENG1031 Software Engineering Workshop 1 Requirements, An Overview Peter Ho CSE, UNSW 5 Aug 2010 Requirements are a collection of statements defined by the System Stakeholders. These
More informationCenterwide System Level Procedure
5.ARC.0004.1 1 of 17 REVISION HISTORY REV Description of Change Author Effective Date 0 Initial Release D. Tweten 7/17/98 1 Clarifications based on 7/98 DNV Audit and 6/98 Internal Audit (see DCR 98-028).
More informationProduct quality evaluation system based on AHP fuzzy comprehensive evaluation
Journal of Industrial Engineering and Management JIEM, 2013 6(1):356-366 Online ISSN: 2013-0953 Print ISSN: 2013-8423 http://dx.doi.org/10.3926/jiem.685 Product quality evaluation system based on AHP fuzzy
More informationSoftware Project & Risk Management Courses Offered by The Westfall Team
Software Project & Risk Management is a 5-day course designed to provide a knowledge base and practical skills for anyone interested in implementing or improving Software Project and Risk Management techniques
More informationEvaluating and Building Portfolio Management Maturity
Evaluating and Building Portfolio Management Maturity Hostetter and Norris, UMD PM Symposium 2016 Evaluating and Building Portfolio Management Maturity Susan Hostetter and Sherri Norris U.S. Census Bureau,
More informationREQUIREMENTS ENGINEERING
1 REQUIREMENTS ENGINEERING Chapter 4- by Ian Sommerville TOPICS COVERED Functional and non-functional requirements The software requirements document Requirements specification Requirements engineering
More informationRequirements Engineering Process Improvement Approach for Embedded Software Systems in Android-Based Mobile Devices
Requirements Engineering Process Improvement Approach for Embedded Software Systems in Android-Based Mobile Devices 1 1 Universiti Kuala Lumpur Malaysian Institute of Information Technology, aedah@miit.unikl.edu.my
More informationQuality Management System Guidance. ISO 9001:2015 Clause-by-clause Interpretation
Quality Management System Guidance ISO 9001:2015 Clause-by-clause Interpretation Table of Contents 1 INTRODUCTION... 4 1.1 IMPLEMENTATION & DEVELOPMENT... 5 1.2 MANAGING THE CHANGE... 5 1.3 TOP MANAGEMENT
More informationCHAPTER 2 LITERATURE SURVEY
10 CHAPTER 2 LITERATURE SURVEY This chapter provides the related work that has been done about the software performance requirements which includes the sub sections like requirements engineering, functional
More informationEMPIRICAL EVALUATION OF METRICS FOR COMPONENT BASED SOFTWARE SYSTEMS Abhikriti Narwal 1 Lecturer, S.D.I.T,M, Israna, Panipat
International Journal of Latest Research in Science and Technology Vol.1,Issue 4 :Page No.373-378,November-December (2012) http://www.mnkjournals.com/ijlrst.htm ISSN (Online):2278-5299 EMPIRICAL EVALUATION
More informationA suggested methodology for evaluating the Industrial glass design by using the concept of (Sigma σ)
A suggested methodology for evaluating the Industrial glass design by using the concept of (Sigma σ) Mohamed Hassan Al Khashab Assistant Professor Glass Department Faculty of Applied Arts, Helwan University,
More informationTenStep Project Management Process Summary
TenStep Project Management Process Summary Project management refers to the definition and planning, and then the subsequent management, control, and conclusion of a project. It is important to recognize
More informationThe Assessment Center Process
The Assessment Center Process Introduction An Assessment Center is not a place - it is a method of evaluating candidates using standardized techniques under controlled conditions. These techniques offer
More informationSuitability of the Requirements Abstraction Model (RAM) Requirements for High Level System Testing
Master Thesis Software Engineering Thesis no: MSE-2007:27 October 2007 Suitability of the Requirements Abstraction Model (RAM) Requirements for High Level System Testing Naeem Muhammad School of Engineering
More informationFiat Group Automobiles Policy for Software Quality Improvement
Fiat Group Automobiles Policy for Software Quality Improvement 2010-01-2329 Published 10/19/2010 Edoardo Sivera Fiat Group Automobiles (FGA) Copyright 2010 SAE International ABSTRACT Automotive systems
More informationDecision Making Delays with Regard to IT Investments
Available online at www.sciencedirect.com Procedia - Social and Behavioral Sciences 40 ( 2012 ) 258 263 2012 International Conference of Asia Pacific Business Innovation and Technology Management Decision
More informationOn of the major merits of the Flag Model is its potential for representation. There are three approaches to such a task: a qualitative, a
Regime Analysis Regime Analysis is a discrete multi-assessment method suitable to assess projects as well as policies. The strength of the Regime Analysis is that it is able to cope with binary, ordinal,
More informationManufacturing Technology Committee Risk Management Working Group Risk Management Training Guides
Manufacturing Technology Committee Management Working Group Management Training Guides Ranking and Filtering 1 Overview Ranking and Filtering is one of the most common facilitation methods used for Management.
More informationIf software is simply for automation, what would a washing machine be like?
If software is simply for automation, what would a washing machine be like? 1 Requirements Analysis, Modeling and Specification Requirements Analysis, Modeling and Specification Problem Carving the Solution
More information1 * Policy Development/Program Planning Skills (please rate each
Page of 8 202 Prioritizing Core Competencies for our Health Commissioner Questions marked with an asterisk (*) are mandatory. We are in the process of developing a job description for our Health Commissioner.
More informationRequirements Validation Techniques: An Empirical Study
Requirements Validation Techniques: An Empirical Study Hafiz Anas Bilal Dept. of Computer Science COMSATS Institute of Information Technology, Islamabad, Pakistan Muhammad Ilyas Dept. of Computer Science
More informationProduct Evaluation of Rijal Tashi Industry Pvt. Ltd. using Analytic Hierarchy Process
Proceedings of IOE Graduate Conference, 2016 pp. 239 244 Product Evaluation of Rijal Tashi Industry Pvt. Ltd. using Analytic Hierarchy Process Rojan Shrestha 1, Shree Raj Sakya 2 1,2 Department of Mechanical
More informationWhen Recognition Matters WHITEPAPER OCTAVE RISK ASSESSMENT WITH OCTAVE.
When Recognition Matters WHITEPAPER OCTAVE RISK ASSESSMENT WITH OCTAVE www.pecb.com CONTENT 3 4 4 5 5 6 6 6 7 8 8 Introduction About OCTAVE History OCTAVE ALLEGRO RoadMap Steps How to use OCTAVE? Preparing
More informationBefore You Start Modelling
Chapter 2 Before You Start Modelling This chapter looks at the issues you need to consider before starting to model with ARIS. Of particular importance is the need to define your objectives and viewpoint.
More informationMCReF: A Metric to Evaluate Complexity of Functional Requirements
MCReF: A Metric to Evaluate Complexity of Functional Requirements Carlos Roberto Paviotti São Paulo Federal Institute of Education, Science and Technology, IFSP Capivari, Brazil e-mail: carlinhos@ifsp.edu.br
More informationA Method for Early Requirements Triage and Selection Utilizing Product Strategies
14th Asia-Pacific Software Engineering Conference A Method for Early Requirements Triage and Selection Utilizing Product Strategies Mahvish Khurum, Khurum Aslam and Tony Gorschek Blekinge Institute of
More informationSoftware Test Factory (A proposal of a process model to create a Test Factory)
International Journal of Computational Intelligence Techniques, ISSN: 0976 0466 & E-ISSN: 0976 0474 Volume 1, Issue 1, 2010, PP-14-19 Software Test Factory (A proposal of a process model to create a Test
More informationLeader Culling Using AHP - PROMETHEE Methodology
Chapter 4 Leader Culling Using AHP - PROMETHEE Methodology 4.1 Introduction In earlier two chapters we worked on Multi Objective Decision Making (MODM) models where multiple objectives are simultaneously
More informationA decision modelling approach for analysing requirements configuration trade-offs in time-constrained Web Application Development
A decision modelling approach for analysing requirements configuration trade-offs in time-constrained Web Application Development Sven Ziemer 1, Pedro R. Falcone Sampaio 2 and Tor Stålhane 1 1 Department
More informationAn Example Portfolio Management Process
BEST PRACTICES WHITE PAPER An Example Portfolio Management Process Jenny Stuart, Vice President of Consulting, Construx Software Version 1, June 2009 Contributors Jerry Deville, Professional Software Engineer
More informationThe Investment Comparison Tool (ICT): A Method to Assess Research and Development Investments
Syracuse University SURFACE Electrical Engineering and Computer Science College of Engineering and Computer Science 11-15-2010 The Investment Comparison Tool (ICT): A Method to Assess Research and Development
More informationSoftware Project Management
Software Project Management Ali Ameer Gondal Assistant Professor University of Engineering & Technology Taxila, Pakistan ali.ameer@uettaxila.edu.pk 27 th Oct. 2011 Software Project Management Lecture #
More informationA Simple Multi-Criteria Selection Model to Set Boundary Sample for Auto Parts
2011 International Conference on Management and Service Science IPEDR vol.8 (2011) (2011) ICSIT Press, Singapore Simple Multi-Criteria Selection Model to Set Boundary Sample for uto Parts Unchitha Kachawong
More informationRequirements Engineering Processes. Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 7 Slide 1
Requirements Engineering Processes Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 7 Slide 1 Objectives To describe the principal requirements engineering activities and their relationships
More informationBasic Terminology. Identification of Correct Population. Random and Fixed Interval Sampling. MUS for Substantive and Compliance Tests
Basic Terminology Identification of Correct Population Random and Fixed Interval Sampling MUS for Substantive and Compliance Tests Attribute Sampling Haphazard Selection the specific item of which the
More informationMES ERP. Critical Manufacturing, 2015
MES vs ERP Critical Manufacturing, 2015 Defining MES Loosening the categories The case for modular MES Modular MES in practice Strategic enterprise integration still matters 3 6 7 8 9 Originally written
More informationThe Scientific Method
The Scientific Method My advice that organizations create a project-selection decision model in order to define project evaluation metrics is nothing more than a recommendation to follow the "scientific
More informationChapter 10 Crown Corporation Governance
Crown Corporation Governance Contents Background............................................................. 123 Scope................................................................... 124 Results in
More informationThe Three Dimensions of Requirements Engineering: 20 Years Later
The Three Dimensions of Requirements Engineering: 20 Years Later Klaus Pohl and Nelufar Ulfat-Bunyadi Abstract Requirements engineering is the process of eliciting stakeholder needs and desires and developing
More informationIntroduction to the BaRE Method
Introduction to the BaRE Method Uolevi Nikula, Lappeenranta University of Technology Goal The purpose of this presentation is to clarify the BaRE method Boundaries Concepts Elements Adoption and usage
More informationWNR Approach: An Extension to Requirements Engineering Lifecycle
WNR Approach: An Extension to Requirements Engineering Lifecycle Ahmad Abdollahzadeh Barforoush, Abbas Rasoolzadegan, Reza Gorgan Mohammadi Information Technology and Computer Engineering Faculty Amirkabir
More informationRequirements Prioritization and using Iteration Model for Successful Implementation of Requirements
Requirements Prioritization and using Iteration Model for Successful Implementation of Requirements Muhammad Yaseen 1, Noraini Ibrahim 2, Aida Mustapha 3 Faculty of Computer Science and Information Technology
More informationIn this ever-changing business and technology
Requirem TRacing Matthias Jarke, Guest Editor In this ever-changing business and technology environment, the risk of inconsistencies in systems development and evolution multiplies. Experience reuse becomes
More informationAsset Management. Why Alignment in Asset Management? Achieve better value for your organization by aligning financial and non-financial functions
Asset Management Briefing Note Why Alignment in Asset Management? Achieve better value for your organization by aligning financial and non-financial functions First Edition April 2018 About ISO/TC 251
More informationOperations and Supply Chain Management Prof. G. Srinivasan Department of Management Studies Indian Institute of Technology, Madras
Operations and Supply Chain Management Prof. G. Srinivasan Department of Management Studies Indian Institute of Technology, Madras Module - 01 Lecture - 08 Aggregate Planning, Quadratic Model, Demand and
More informationSTAFF QUESTIONS AND ANSWERS
1666 K Street, N.W. Washington, DC 20006 Telephone: (202) 207-9100 Facsimile: (202) 862-8430 www.pcaobus.org STAFF QUESTIONS AND ANSWERS AUDITING INTERNAL CONTROL OVER FINANCIAL REPORTING Summary: Staff
More information