a.       Determine the artefacts to be prioritized.

b.       Select the prioritization criteria

c.       Identify the relevant stakeholders

d.       Select one of more prioritization techniques

 

2.       List some of the techniques for requirements prioritisation? Provide your own example

a.       Ad-hoc ranking

b.       Top-ten

c.       Kano Classification

d.       Wiegers’ Prioritization Matrix

e.       One-Criterion Classification

 

3.       Why is it important to have version management in requirements artefacts? Explain in your own words. 

a.       Because quality attributes and contextual information for the artefact might change, which could cause confusion among the team if they have different versions of an artefact.

 

4.       Why is it important to have configuration management in the development process? Explain in your own words. 

a.       Configuration management is important to ensure that the artefacts  have the following properties: consistency, unique identification, not changeable and basis for roll-back.

-          Determine artefacts to be prioritized

-          Select the prioritization criteria 

-          Identify the relevant stakeholders

-          Select one of more prioritizations

 

2.       List some of the techniques for requirements prioritisation? Provide your own example

-          Ad hoc ranking and top-ten technique 

-          One-criterion classification

-          Requirement classification according to kano

-          Wieger’s prioritization matrix

 

3.       Why is it important to have version management in requirements artefacts? Explain in your own words. 

-          A system release reflects a certain configuration of requirements artefacts which are implemented and delivered to the customer.

-          The requirements of the system will change throughout the versions and must be managed to ensure the versions that are releasing will have the relevant requirements that satisfies the clients’ needs.

 

4.       Why is it important to have configuration management in the development process? Explain in your own words. 

-          Configuration management is the discipline of controlling changes in large and complex system. Its goal is to prevent the chaos caused by the numerous corrections, extensions, and adaptations which are applied to any large system over its lifetime

a.      Determine artefacts to be prioritized

b.      Select the prioritization criteria

c.      Identify the relevant stakeholders

d.      Select prioritization techniques 

2.      List some of the techniques for requirements prioritisation? Provide your own example

a.      Ad-hoc Ranking

b.      Top-Ten

c.      One-Criterion Classification

d.      Kano Classification

e.      Wiegers’ Prioritization Matrix

3.      Why is it important to have version management in requirements artefacts? Explain in your own words. 

- The requirements may change in the process of development where may involve new stakeholders or may not. New Requirements are needed to be analyzed and to see if may or may not affect the existing requirements. 
- To keep track on what has changed in the process of requirements development. 

4. Why is it important to have configuration management in the development process? Explain in your own words. 
- Configuration Management is to keep track on the quality and consistency of the requirement artefacts.