5.  CMMI  REQUIREMENT DEVELOPMENT  SPECIFIC AND GENERIC GOALS  SG1: Develop CUSTOMER Requirement  SG2: Develop Product Requirement  SG3: Analyze and Validate Requirements  GG1: Institutionalize the defined Process

8. CMMI means Capability Maturity Model Integration Capability Maturity Model Integration (CMMI) models provide guidance to use when developing processes. CMMI models are not processes or process descriptions

10. We Will Discuss

11. The Purpose of Requirement Development is to produce and analyze:  Customer  Product  Product-components requirements.

12. Elicitation, analysis, validation, communication and constraints. Collection and coordination of stakeholders needs Development of the life cycle of requirements of the product Establishment of the customer requirements Establishment of initial product and product component requirement.

14. In requirement development we handle two types of goals  Specific Goals (SG)  Generic Goal (GG)

15. A specific goal is such a type of a goal that incorporates an action plan that outlines.  How you will achieve the goal.  Performance measure that tells you how to evaluate the goal.

16. These are such types of goals which are required model components that apply to all process areas. E.G.  Train the people  Assign Responsibility  Plan the Process

19. Every goal we set is carried out by some practices that we have to follow to achieve the goal, we desire for. This intact a specific relationship between goals and the practices to be followed.

20. SG 1

22.  The needs of the stakeholders are the basis for determining customer requirements  An iterative process is used through out the life of the project to accomplish these objectives.  A surrogate is involved for customer to represent their needs and help to resolve conflicts.

24. Elicit stakeholder needs, expectations, constraints and interfaces for all phases of the product lifecycle. Eliciting : identifying additional requirements, these are not provided by customer. Some examples of techniques to elicit needs  Brainstorming  Market surveys  Beta testing  Usecases

25.  The various inputs from the customer should be gathered  The conflicts must be solved in documenting the recognized set of customer requirements.  The customer requirements will include needs, expectations and constraints with regards to verification and validation

26. Develop Product Requirement

28. Customer requirements are refined and elaborated to develop product and product – component requirements. Practices to be followed : Establish product and product components requirements Allocate product –component requirements Identify interface requirements

29.  Customer requirements are also analyzed with the development of the operational concept to derive precise sets of requirements called product and product-component requirements.  Derived requirements arise from constraints, consideration of issues, selected architecture and design.  The requirements are re-examined and the preferred product concept is refined.

32.  Customer requirements may be expressed in the customer’s terms or non-technical description.  Product requirements are the expression of customer requirements in technical terms. Example : Solid-sounding door(Non- technical) Might be mapped to size, weight, fit and resonant frequencies ( technical)

33.  Derived requirements  Product requirements  Product-Component requirements

34.  Develop requirements in technical terms for product and product-component design.  Derive requirements from design decisions.  Establish and maintain relationships between requirements for consideration during change management and requirements allocation.

36.  Allocate requirements to functions.  Allocate requirements to product component.  Allocate design constraint to product component.

37. Interfaces between function are identified. The Corresponding Work Products are:  Interface requirements. The Corresponding Sub Practices are:  Identify interfaces  Develop the requirements for the identified interfaces

39. The requirements are analyzed and validated and definition of the required functionality is developed. Practices to be followed Establish operational concepts Establish a definition of required functionality Analyze requirements Analyze requirements to achieve balance Validate requirements with comprehensive method

40.  Analysis provides us the needs of the stakeholders and the constraints of the product.  The objectives of the analysis are to determine candidate requirements for product that will satisfy stakeholders.

42.  Establish and maintain operational concepts and associated scenarios.

43.  Disposal concepts.  Use cases.  Timeline scenarios.  New requirements.

44.  Define the environment the product will operate in, including boundaries and constraints.  Review operational concepts and scenarios to refine and discover requirements.

45.  Establish and maintain a definition of required functionality.  The definition of functionality includes actions, sequence, inputs or other information that communicates the manner in which the product will be used.

46.  Functional architecture  Activity diagrams and use cases  Object –oriented analysis with services identified

47. Analyze and quantify functionality required by end users. Analyze requirements to identify logical or functional partitions

48. Analyze requirements to ensure that they are necessary and sufficient.

49. Analyze requirements to determine whether they satisfy objectives of higher level requirements Analyze requirements to ensure that they are complete and verifiable

51. Assessments of risks related to requirements

52. Use proven models, simulations and prototyping to analyze the balance of stake holder needs and constraints. Perform a risk assessment on the requirements and functional architectures.

54.  Validate requirements to ensure the resulting product will perform as intended in the user’s environments using multiple techniques as appropriate.  Typical work products:  Record of analysis methods and results.

55. Analyze the requirements to determine the risk that might be faced by the resulting product. Explore the adequacy and completeness of requirements by developing product representations and by obtaining feed back about them from relevant stake holders.

56. GG 3 Institutionalize the defined process

58.  When we are following generic goals we make some commitments that we have to ensure at the end of the project so that customer gets satisfaction.

59. Establish and maintain an organizational policy for planning and performing the requirements development process.  This policy establishes organizational expectations for collecting stakeholder needs, formulating product and product-component and validating those requirements

60. Establish and maintain the description of a defined requirements development process.

61. Establish and maintain a plan for performing the requirement development process

62. Provide adequate resources for performing the requirements development process, developing the work products and providing the services of the process  Requirements specification tools  Requirements tracking tools  Prototyping tools

63. Assign responsibility and authority for performing the process, developing the work products and providing the services of the requirements development process.

65. Review the activities,status and result of the requirements development process with higher level management and resolve issues.

69. ANY QUESTIONS