Software Requirements Analysis Tutorial: The fourth chapter read the fifth chapter software Risk Management Foundation

As we improve the demand process, it is important to note that putting the theoretical approach into practice is at the core of improving the software process, and our two main goals in improving the software development process are to address problems encountered in previous projects or current projects, and to prevent and avoid problems that you may encounter in future projects. In the software development process must master some other very valuable and quite effective requirements engineering methods to prevent the software organization facing some unexpected situation is unable to.

The requirements process is the key to the success of the software project, and the impact on the requirements process as other project processes change the process of the project in which changes are made: the development of the project planning process (narrowing the scope of the project before the baseline is determined or adopting a version plan so that the project plan is completed within the allowed resources and time), Project tracking and control process, change control process, System test process (verify that the function is completed on schedule) user documentation process (to write out the user display interface and performance of the final change version), the construction process. In the process of software transformation to keep in mind 1, the improvement process should be revolutionary, thorough, continuous, repeated. 2, people and organizations are only willing to change 3 when they are motivated , the process change is goal-oriented 4, and the improvement activities are seen as small projects.

When we perform any process improvement activities, we first assess the strengths and weaknesses of the methods currently used in the organization, and we can use a self-questionnaire approach, but a more thorough approach is to let external consultants objectively evaluate your current software development methodology. In the process of improvement, we should analyse each of the improvement activities considered to ensure that he is able to implement at the allowable cost, and select those improvement activities that may bring a considerable return on investment.

Next we begin to develop a plan for improvement activities, and we should note that each tactical action plan should be well-known for the objectives of the action, the stakeholders and some of the activity items that must be completed.

After the plan has been completed, the implementation of the plan, and then the implementation of the new plan for their own heart process or document template to plan an experiment to prevent the appearance of a good way to become both impractical and inefficient, the book puts forward recommendations on the pilot experiment:1, select the participants in the experiment, They will try out new methods and provide feedback. 2, determining the criteria used to evaluate the experiment is that the resulting results are easy to interpret. 3. Inform those engineering stakeholders who need to know what the experiment is and why it should be implemented. 4, consider experimenting with different parts of the new process in different projects. 5, as part of the assessment, asked the participants if they had to go back to their original methods of work and how they felt.

The final step in the improvement process is to evaluate the results, which will help to do better in the next transformation.

The accumulation of materials in the requirements process includes checklists, examples, plans, guidelines, procedures, process descriptions, and templates. Accumulation of requirements development process materials: Project view and scope template, requirements development process, requirements allocation process, use instance template, software Requirements Specification template, requirements prioritization process,SRS and use case review checklist. Accumulation of requirements Management process: Change control process, change Control committee process, requirements change impact Analysis Checklist and template, requirement status tracking process, requirements tracking capability matrix template, demand Process Improvement roadmap.

The next step is software requirements and risk management, and software project managers must identify and control their project risks to avoid potential threats that hinder projects from being planned. Risk management is the identification, assessment, and control of risk before the risk is brought to the project. Risk management means dealing with a worry before it turns into a crisis or actual difficulty.

Software risk management activities to adapt to the scale of the project small-scale projects can only list a simple risk list, but for a large-scale project success, the formal risk management plan is very important. Elements of risk management include risk assessment (the process of inspecting a project and identifying potential areas of risk), risk avoidance (a way to deal with risk: Try not to take risks), writing project risk documents (to help stakeholders understand risk situations and status throughout the project development process).

Software Requirements Analysis Tutorial: The fourth chapter read the fifth chapter software Risk Management Foundation