Write a one paragraph or more answer to each of the following discussion question. APA format not required for this. Week 3 Discussion 1 Please respond to the following by creating your own thread. ‘Contract Development’ Please respond to the following: Gathering software requirements requires gathering of functional requirements, operational requirements, and technical specifications. These requirements can then be described in the contract development process. Describe what may happen if declarative statements contain ambiguous phrases such as “ands”, “ ors”, “ifs”, or “buts” as described within the operational requirements. Present example(s) to support your answer.Determine the typical items that should be included within a contractual agreement of a software project. Analyze how the inclusion of these items may help avoid risks in future phases of the software project life cycle.Week 3 Discussion 2Please respond to the following by creating your own thread.’Project Planning’ Please respond to the following:Operational requirements, software specifications, process constraints, and product constraints are all necessary inputs for project planning. Describe how each is used for defining the project planning processes. Provide specific examples to justify your answer.Synthesize the project management challenges that may occur without an explicitly written project plan. Summarize how this impacts a project manager’s ability to lead a technology project.Week 4 Discussion 1 Please respond to the following by creating your own thread.’Guidelines for WBS’ Please respond to the following:The Work Breakdown Structure is an essential tool for planning and managing the activities of a software project. Suggest three guidelines that may be used when developing a WBS. Explain why each guideline is critical to the development of the WBS.Analyze how each guideline identified in Part 1 of this discussion can enhance a project manager’s ability to manage the project during the planning and controlling phases of the project.Week 4 Discussion 2Please respond to the following by creating your own thread.’Critical Path Method (CPM)’ Please respond to the following:The Critical Path Method can be used as a project management tool for determining the durations and slack times of project activities. Describe how this tool can be used to recover from schedule overruns of specific activities that are not on the critical path. Provide an example to justify your answer.Analyze how the Program Evaluation and Review Technique (PERT) method may be used in conjunction with CPM to schedule activities throughout the project life cycle. Week 5 Discussion 1 Please respond to the following by creating your own thread.’Project Constraints’ Please respond to the following:Designing software deliverables may require an analysis of historical project experiences within the organization. Explain how past experiences of previous projects within the organization as well as existing project constraints impact and influence the design of software project deliverables. Include an example to support your answer.Analyze how a constrained solution box may help end users and upper management understand the limits of requirements, resources, and the schedule of a project.Week 5 Discussion 2Please respond to the following by creating your own thread.’Estimation Techniques’ Please respond to the following:There are various methods that may be used to determine activity estimates with respect to resources, costs, and durations. Choose at least three estimation techniques that may be used for determining activity estimates for an IT project. Describe the pros and cons of each. Determine the most efficient estimation technique for an IT project; include an example or scenario to support your response.Describe the accuracy level and the risk level of effort and the activities associated with each estimation technique you chose in Part 1 of this discussion. Determine the technique that would be efficient for the following: 1.   Estimating a source code based project  2.   Systems development project 3.   High-risk software project