Software Process Improvement

A term (29) 4 points

1. Software life cycle
   software life cycle (software life cycle), also known as software life cycle, survival. Refers to the concept of software development from the formation of the future use of the developed software, the whole process until lose value until the demise. In general, the whole life cycle including planning (define), development, operation (maintenance) three periods, each period is divided into several stages. Each stage has a clear mandate, so that the large-scale, complex structure and manage complex software development becomes easy to control and manage.
   SDLC six stages: 1. Definition and Requirements Analysis Planning 2. 3. 4. design software program code 5. 6. operation and maintenance of software testing

2. Project
   Project is a series of unique, complex and mutually related activities, these activities has a clear goal or purpose, must, budget, within the limited resources, according to the specification completed at a specific time. Temporary work for the project is to create a unique product, service or result carried out.
   Project parameters include project scope, quality, cost, time and resources.

3. Milestone
   in the development of the project schedule, set up some important points to check on the progress of time schedule, so that it can be checked and controlled process of the project take advantage of these important time checkpoints during project execution. These important time of the checkpoint is called a milestone project (Milestone).

4. Software Metrics
   Software Metrics is a software development project, process and product data definition, collection and continuous quantitative process analysis with the aim of this be understood, forecast, evaluate, control and improve.

5. Function Point Analysis
   Function Point Analysis is the most important and most effective software measurement scale method, which can be measured on a software project early in the project, and constantly update the data in the development process, in order to achieve a sustained consistent management. From the application perspective, the world has thousands of projects using Function Point Analysis. From the research point of view, Function Point Analysis has also become the basis for many other new measuring methods.
   Function Point Analysis is a commonly used method for estimating workload items, available seven steps outlined: 1. Determine the type of feature points calculated; 2 determines the calculation range and application boundaries; 3 determines all the functionality and complexity of the data;. 4. determine the functionality and complexity of all transactions; 5 stars No adjustment dot count; 6 derived value based on the basic features of system adjustment factor; 7. adjustment dot count is calculated.

6. Work Breakdown Structure (WBS)
   WBS project management is one of the important technical terms. WBS basic definition: A deliverable-oriented grouping of project elements is carried out, it summarized and define a more detailed definition of the project work throughout the project scope of work for each layer representing decline. In terms of project management practice, or in the PMP, IPMP exam, work breakdown structure (WBS) is one of the most important content. WBS is always at the center of the planning process, but also an important basis for the development schedule, resource requirements, cost estimates, risk management plans and procurement plans and the like. WBS is also an important basis for project change control.

7. Software Quality
   Software Quality is the "software with explicit and implicit definition of requirements consistent degree." Specifically, the software is software quality in line with a clear description of the function and performance requirements, development standards document explicitly described, as well as professional development of all software should have the features of consistent and implied degree. The main factors affecting the quality of the software, these factors are measured from the point of view of software quality management. It can be divided into three groups, three views reaction user when using the software product. Correctness, robustness, efficiency, integrity, availability, risk (product runs); understandability, maintainability, flexibility, testability (product modification); portability, reusability, interoperability of operation (product transfer).

8. RMMM plan (Risk Mitigation, Monitoring and Management Plan )
   software project risk management is an important part of software project management. During software project risk management, risk identification to assess the impact and probability of their appearance generated, and then create a plan to manage the risk. The main objective of risk management is to prevent risks.
   Software project risk refers to the impact of problems encountered during the software development process and progress of the budget as well as the problems of software projects. Software project risk will affect the realization of the project plan, if project risks become a reality, it may affect the progress of the project, increasing the cost of the project, and even the software project can not be achieved. If the project risk management, you can minimize the occurrence of risk.

9. COCOMO model
   structural cost model. It is a software cost estimation method proposed by Barry Boehm (Barry Boehm). This model uses a basic regression equation that is essentially a parametric project estimation method, parametric modeling are some of the features of the project as a parameter to predict project costs through the establishment of a digital model (similar to live area as a whole, housing costs calculated parameters).

10. Project PERT
    PERT is the project as a system, with a network diagram or table or matrix to represent the sequence of the specific work and relationships to time as the center, to find out the required time from start to completion the longest route, and the system overall planning around critical path, and reasonable arrangements to complete the progress of the work under strict control, in order to achieve a plan with minimal time and resources consumed to complete the intended target and control system method.

11. Software quality model
    quality software often involves a number of different quality attributes, different types of software quality attributes of interest are not the same. Therefore, in order to better understand, predict and evaluate the quality of software and information systems, all kinds of people to build a quality model for evaluation of software quality at various stages of the software life cycle. Common generic software quality model includes hierarchical model and the relational model, they played a positive role in the current software development.

12. Arrival time based on the defect pattern of
    defect density of the product, or testing phase defect rate is a general indicator, the defect arrival pattern may provide more information about the process, sometimes even with the overall defect rate is the same, but the quality difference may the larger reason is that the defect arrival pattern is not the same. The more defects arrive sooner, the better the quality of the testing process. Whether it is from the point of view of the progress of the test, or rediscovered from the user (customer rediscoveries) point of view, the process defect tracking is very important in the development cycle of a large number of serious flaws will be possible to stop the progression of the test, it is bound to affect directly quality and performance of software products. Qualitative analysis easier, more mature test team, to reach the peak sooner, sometimes reached a peak in the first week or second week. This value depends on the quality of the code peak, test execution strategy and design quality of the test cases, horizontal, etc., in most cases, you can push the baseline (or historical data). Reaches a peak from a low and stable level, it requires a much longer time, at least 4-5 times the peak time used. The time depends on the peak, defect removal efficiency, and so on.
    In the early stages of testing defect rate is growing rapidly. After reaching a peak, time to drop at a slower rate, lowered to the lowest point - zero.

13. Software process
    software process as a framework to build high-quality software for the tasks required, namely the formation of a series of steps of software products, including the category of intermediate products, resources, methods and process to take the role, tools and so on.
    (Courseware)
    activities of people in the development and maintenance of software products related machinery involved, methods, practices and reforms. Software-related products which include software project plans, design documents, code, test cases and user manuals.

14. Software basic process
    of software acquisition, supply, development, operation and maintenance of process, including requirements analysis, software design, coding process.

15. Software support process
    including documentation process, configuration management process, the quality assurance process, the process of verification and validation (test), review processes.

16. Software organizational processes
    of the organization and support processes major software assurance process, including process management, process infrastructure, process improvement and training process.

17. Process framework
    by defining the process of software architecture, software process improvement plans, software process assessment, software process improvement activities to establish a framework program four basic conceptual structure for the target software project in the software process environment.

18. Capability Maturity Model
    Capability Maturity Model a software organization in the definition, implementation, measurement, control and improve the standard practice of describing its software during the development of the various stages of formation. CMM is the core of software development as a process, and process monitoring and research on software development and maintenance in accordance with this principle, to make it more scientific, standardized, enabling enterprises to better achieve business goals.

19. Unified Process
    The Unified Process is divided into five stages: start-up phase (inception), the refinement phase (elaboration), the construction phase (construction), the transition phase (transition), production (production). Rational Unified Process Rational company is the development and maintenance of process products. Rational Unified Process is a process of software engineering. It provides a disciplined method dispatch tasks and responsibilities within a development organization. It aims at a predictable schedule and budget premise, ensure that end-user demand high-quality products.

20. Process model
    series for generic object-oriented software technology, behavior, or a variety of tasks, an important feature of the process model is that it only describes a software developer should do, but there is no precise description of the details of what should be done. When the process model can be organized together applications, they can be used to generate software process to improve software development mechanism. Because the process model does not specify how to do a given job, they can become building blocks can be reused. Software developers can customize a software process pursuant to the specific needs of software development organizations to meet.

21. Personal Software Process
    PSP Personal Software Process (Personal Software Process, PSP) is a kind of used to control, manage and improve ourselves continually improve process personal works, is a software development forms, guidelines and procedures structured framework. PSP and specific technical (programming languages, design tools or methods) are relatively independent, which in principle can be applied to almost any software engineering tasks. PSP able to explain the principles of individual software process; help software engineers to make accurate plans; determining software engineers to improve product quality to take steps; build a measure of individual software process improvement benchmarks; impact on the ability of software engineers to determine the change process.

22. Team Software Process TSP
    team software process is to provide guidance for the development of software product development team, TSP early practice focuses on helping development teams improve their quality and productivity, to make it better meet the target cost and schedule. TSP is designed to meet the 2 to 20-person development team, TSP large, multi-team process is designed to be up to about the size of about 150 people.
    Team Software Process (TSP) plus high performance PSP help engineers work in a team, to develop a quality assurance software products, the production of security software products, improve process management in the organization. By TSP, an organization can establish self-managed teams to track their work plan, establish goals, and have their own processes and plans. These teams may be pure software development team, can also be integrated product team, the scale can range from 3-20 engineer. TSP team might use XP, RUP or other methods in wide range of areas. TSP with the PSP team of project staff can learn and succeed. If your organization use TSP, it will help your organization build a mature standard engineering practices, to ensure the safety and reliability of software.

23. Process specification
    process specifications is to process input / output activity and consisting of or expressly provided for the de facto standard. Software is a software development organization process specifications and guidelines for a guide to action, can establish the appropriate specification based on the characteristics of various types of processes described above, the basic processes such as software specifications, process specifications and software support organization software process specifications.

24. Process model
    called software process model is a development strategy that provides a range of form for all phases of software engineering, the progress of the project to achieve the desired purpose. For a software development regardless of their size, we need to choose a suitable software process model, this choice based on the nature of projects and applications, the approach, the need to control, and the characteristics of the product to be delivered.
    Common models include the waterfall model, spiral model, incremental model, iterative model, V model.

25. Configuration Management
    Configuration Management (Configuration Management, CM) is controlled, a series of measures to regulate the software development process and its product lifecycle through technical or administrative means. Configuration management goal is to record the evolution of software products to ensure that software developers at all stages of the software life cycle can get accurate product configuration.

26. Configuration item
    configuration item refers to all items included in the scope of configuration management. Those who work results are included in the scope of Configuration Management Configuration Item (CI); CIs a pure software commonly referred to as software configuration (CSCIs). CIs are two major categories: the results of the work belongs to the part of the product; documentation project management and institutional support process produced.
    The main properties of each configuration item include: name, ID file status, version, author, date and so on.

27. Baseline
    Baseline project repository version of each artifact a "snapshot" of a particular period. It provides a formal standard, subsequent work based on this standard, and only after authorization is required to change this standard. After establishing an initial baseline, after each change will be recorded as a difference until completion of the next baseline.

28. Preventive Maintenance
    Preventive maintenance is the modifications made after the delivery of software products to potential errors in the software products before actual errors to be detected and corrected them.

29. Adaptive maintenance
    all aspects of development and changes in the computer field very quickly, often there will be a new system or a new version, the original external devices and other systems often change, and application software usage time, tend to use time more than the original system environment as long, therefore, often we need to transform the software to adapt to the new environment. To make software products can still be carried out maintenance in the new environment, called adaptive maintenance.

Second, the short answer questions (15) for each question 10 minutes

1. Show the evaluation and improvement process using two two advantages and disadvantages of the methods in the SEI CMMI model.

2. Consider the type of software process in your organization used. Use SEI model to find out how many key process areas? According to this model, the process in your organization's maturity level how to draw?

3. If the process of improvement measures including people who work in the process, and thorough process of change, whether such a project is inhumane? Process improvement which conflict behavior occurs?

4. SEI's CMMI given two areas can not be applied, and explain the reasons.

5. How to convert existing software development to agile development methods? What are the difficulties encountered during what is the solution?

6. Similarities and differences between the analysis and comparison of CMMI, ISO15504 and 6sigma.

7. Why software process must be improved?
   (Soft Engineering courseware)
   all activities, there are processes; all process, there are improved; all improvements, there is no end. The need for software process improvement mainly in the following points:
   After a period of time, the process of reducing the performance of the region;
   customers have increasingly higher demands;
   the process of organizing is to gradually mature;
   the target tissue may be changed;
   organizations the environment is constantly changing;
   competitors improvement.

8. What software engineering process software introduced the role and meaning?
   (Soft Engineering Review Questions)
   software process is a set of software engineering activities in the lifetime of the software. Each software process is a set of tasks, project milestones, deliverables and software product engineering, quality assurance point and so on.
   Software process framework is to obtain a series of tasks you need to complete high-quality software, it provides for the completion of the task of working steps. The pros and cons of the software process determines the level of software quality, good-quality and efficient process is a prerequisite.

9. Software Process Improvement How to manage change?
   (Courseware)
   Partnership Strategy: depends on the relationship between the individual; the use of seminars, luncheons and events to announce and discuss what needs to change and how to change.
   Policy strategy: trying to influence the official and unofficial leader of the powerful organizational structure change 'find and convince those most respected, there are many supporters of the people.
   Economic policy: I believe has the best money convincing; based on the assumption - people driving force of economic stimulus.
   Confrontation strategy: based on the assumption - if we can arouse and mobilize people on current issues of resentment and anger, they would be willing to change; rely more on persuasion strategist is that people feel the existing problems, but do not advocate violence.
   Academic strategy: assume that if you provide people with enough information and facts right, they will accept change; usually generate employers, research report of the Committee of Experts and consulting.
   Project strategy: assume that the nature of work changes, many people had to change; emphasis on the organizational structure of the problem, leading to very sensitive to the environment.
   Military strategy: force or rely on harsh ignorance; from time to time by the military, police, students and political pressure groups, political parties, with a focus on learning to use weapons in the struggle; require strength and agility, discipline will be rewarded.

10. What constitutes software process improvement framework is? What is the role of each component?
    (Courseware)
    1) Software Process Improvement plans
    Role: divided in different stages of process improvement, and pointed out that at each stage should have what kind of features and attributes.
    2) Software Process Assessment
    effect: the software processes of an organization to evaluate and inspect. By assessment can help organizations have a correct understanding of the current software environment and process basis. Acted as a catalyst to improve the activity plan.
    3) Software Process Improvement Program
    effect: According to assess problems found, targeted to develop process improvement program.

11. The main activities description output in the software design process and how these activities. Using an entity - relationship diagram (E - R diagram), the relationship that may exist between the activity output.

12. We discussed the role of metrics in software process improvement.

13. What is Integrated Process Improvement? What is its meaning?

14. What is the development of software process improvement plan is the process? The main purpose of the role and activities of the interpretation of them?

15. Brief CMMI - DEV V1.3 process areas each maturity level included.

(Courseware)
Maturity Level 2 (7): requirements management, project planning, project monitoring and control, supply contracts management, measurement and analysis, process and product quality management, configuration management
maturity level 3 (11): requirements development , technology solutions, product integration, verification, validation, organization-wide process focus, organizational-level process definition, organization-wide training, integrated project management, risk management, decision analysis and solution
maturity level 4 (2): the organization level process performance, quantitative project management
maturity level 5 (2): organization-wide reform and implementation, causal analysis and solutions

Third, the essay questions (7) 20 points for each question

1. Under what circumstances may the product quality depends on the quality of the development team? Examples of what types of software products is particularly dependent on the individual talents and abilities.

2. ISO 9001: PDCA cycle 2008 standard, also known as the Deming cycle, is the US quality management expert Dr. Hugh Hart first proposed, adopted by the Deming, publicity, gained popularity, which is also known as "Deming ring." It is a total quality management should follow scientific procedures. It discusses the role and significance in assessing the quality of software project management.

3. In conjunction with CMMI implementation, discusses the role of software process during the main phase of improvements.

4. One of the key obstacles to reuse of software engineers to consider is to make use of existing components, rather than re-development of new components, please suggest 3-4 kinds of software organizations can use to motivate software engineer multiplexed manner. In order to support reuse, what technology should be used?

5. On the enterprise software process improvement implementation. Please focus on "enterprise software process improvement of implementation of the" thesis, in turn discussed the following four aspects:
   (1) describe the main software process improvement activities implemented.
   (2) a summary description of your participation in the implementation of enterprise software process improvement projects and major work you have served.
   (3) discuss the implementation of major enterprise software process improvement methods and procedures of how the project uses standard model based on the actual situation of enterprises and implementation.
   (4) specifically addressed in the implementation of the enterprise software process improvement activities and address the major problems and effects found.

6. In today's "3C" environment, continuous improvement is the eternal theme of survival and development, its use is not a single tool. A company intends for "a service rate of customer complaints" to improve, what tools can be used at different stages.

7. According to the diagram, analysis shows CMMI - DEV V1.3 interaction between, the five engineering process areas.

8. How to convert existing software development to agile development methods? What are the difficulties encountered during what is the solution?

9. Summarize the basic process model of the enterprise.

10. Whether the units need to introduce new software development method? Reasons given measures.

11. Lifetime lifetime software and software projects What is the difference?

12. In your unit or project team which measure activity? Do you think there is a need to improve the place?

13. Current business operations are in a globalized, rapidly changing operating environment, traditional software development process can not adapt to the rapid software requirements arising therefrom. The late 1990s, a number of software developers in the "Agile Alliance 2001" in the systematic exposition of the principles of agile development, trying to emphasize the role of flexibility in a fast and efficient production of software played. Currently a large number of software production enterprises have been accepted and practiced basic principles of agile development methods in the actual software development process.
    Question 1: There are many typical method of agile development, extreme programming (eXtreme Programming), Scrum, Crystal , DSDM and so on. What Will these methods common basic principles?
    Question 2: Agile proponents tend to exaggerate the advantages of this method, but in practice, the basic principles of Agile methods are sometimes really difficult to implement. Please use the text of 200 words or less description Agile methods in which the principle difficult to implement in practice.
    Question 3: Agile development methodology most famous Extreme Programming. Please explain the concept of pair programming Limit (Pair Programming) is.
    Question 4: Agile development methods in the specific practice, often requires a development environment or tool support, commonly referred to as rapid application development techniques and visual development technologies. Please use less than 150 words to text tool for rapid application development techniques included what, and a brief description of the basic concepts and technical principles of visual development technologies.