74 software engineering terms

1. Software
Software is a part of computer systems that are mutually dependent on hardware. It is a complete set of programs, data, and related documents.

2. Software Crisis
Software Crisis refers to a series of serious problems encountered during the development and maintenance of computer software.

3. Software Engineering
Software Engineering is to research and use systematic, standardized, and measurable methods to develop, run, and maintain software, that is, to apply engineering to software.

4. software life cycle
The software life cycle refers to the entire process from the consideration of its concept to the delivery and use of the software product until the final retirement, it generally includes planning, analysis, design, implementation, testing, integration, delivery, and maintenance.

5. Software Reuse
Software reuse is to use some developed software elements that are useful for creating new systems to generate new software systems.

6. Quality
Quality is a collection of features and features that allow products or services to meet clear or implicit requirements. In the contract environment, the requirements are clear; in other environments, the implied requirements need to be identified and defined.

7. Quality Planning
Quality Planning includes product planning, management and operation planning, as well as quality plan preparation and quality improvement preparation.

8. Quality Improvement
Quality improvement is a continuous activity with the highest efficiency and efficiency.

9. Quality Control
Quality control is a process and product conformity evaluation. Independent deficiencies are analyzed and corrected so that the products and requirements are consistent.

10. Quality assurance
Quality assurance is a planned and systematic activity that provides sufficient confidence in the ability of components or products to meet identified technical needs.

11. Software Quality
Software Quality refers to the fulfillment of declared functional and performance requirements, documented development standards, and all implied features of software developed by professionals.

12. Formal technical review
Formal technical review is a software quality assurance activity conducted by software developers to discover functional, logical, or implemented errors in any form of representation of the software, verify that the reviewed software meets the requirements, ensure that the software meets the predefined standards, and develop the software in a consistent manner, making the project easier to manage.

13. ISO
ISO stands for International Organization for Standardization ".

14. ISO9000
ISO9000 is an international standard for quality management and quality assurance developed by ISO/tc176.

15. Quality Certification
Quality Certification is an activity by a third party that can fully trust a product or service that has been identified to comply with specific standards or normative documents.

16. Software Process
Software processes are a series of activities that people use to develop and maintain software and related processes, including software engineering activities and software management activities.

17. Software Process Capability
A Software Process Capability describes the extent to which a development organization or project team can achieve the expected results in compliance with its software process, either for the entire software development organization or for a software project.

18. Software Process Performance
The software process performance representation (development organization or project team) follows the actual results of the software process. The software process performance describes the actual results obtained, the software process capability describes the most likely expected results, either for the entire software development organization or for a specific project.

19. software process maturity
Software process maturity refers to the extent to which a specific software process is clearly and effectively defined to manage measurement and control.

20. Software maturity level
Software maturity level refers to the software development organization's several platforms with clearly defined maturity of software process capabilities on the way to maturity.
21. Key process Domains
Each Software Capability Maturity level contains several process domains that are critical to the level of maturity. Their implementation guarantees the achievement of the level of maturity, these process domains are the key process domains of the maturity level.

22. Key Practices
Key Practices refer to the establishment of policies, procedures, measures, activities and related infrastructure that play a key role in the practice of key process domains.

23. Software Capability Maturity Model
The Software Capability Maturity Model refers to the process of defining, implementing, measuring, controlling, and improving the software by the software organization, and the software organization's capability also advances along with these stages, describes the software organization evolution stage.

24. software requirements
Software requirement refers
(1) Conditions or capabilities required by the user to solve the problem or achieve the goal;
(2) The conditions or capabilities required by the system or system components to meet the contract, standards, specifications or other formal provision documents;
(3) A document describing the conditions or capabilities described above (1) or (2.

25. Business Needs
Business requirement reflects the high-level objective requirements of organizations or customers on systems or products, which are described in the project view and scope document.

26. User Requirements
User requirement describes the tasks that must be completed when you use a product. You can describe the tasks in the use case model or solution script.

27. Functional Requirements
Functional requirements define the software functions that developers must implement so that users can complete their tasks and meet business needs.

28. non-functional requirements
Non-functional requirement is the constraint and restriction on the system from various perspectives, reflecting the additional requirements of the application on the quality and characteristics of the software system.

29. Demand Engineering
Demand engineering is a proven principle and method. It uses appropriate tools and symbols to systematically describe the system to be developed, its behavior characteristics, and related constraints.

30. Demand Analysis
The demand analysis mainly aims to refine, analyze, and carefully review the collected requirements to ensure that all risk owners understand the meaning and identify the errors, omissions, or other deficiencies, form a complete analysis model.

31. Specification of software requirements
The Specification Description of a software requirement is the final result of demand development. It precisely describes the functions and performance required by a software system and the constraints it must consider. The Software Requirement Specification Description is not only the basis of system testing and user documentation, but also the basis for planning, designing and coding for all sub-series projects.

32. risk owner
The risk owner is any person who will be substantially affected by the implementation of the new system or application.

33. software prototype
Software prototype is a part of the implementation of the new product. Its purpose is to solve the problem of uncertain demand in the early stages of product development.

34. Object relationship diagram
The object relationship diagram describes the data objects and their relationships.

35. Data Flow Diagram
A data flow chart is a basic tool for structured analysis. It describes the information flow and data conversion.

36. Status transition diagram
The status transition chart describes the status and events that cause the system to change the status.

37. Data Dictionary
A Data Dictionary describes the data storage, processing (bottom-layer processing), and data flow of a data flow chart.

38. Object
An object is an entity used in the system to describe objective things. It is a basic unit of the system and is composed of a group of attributes and a group of services that operate on these attributes.

39. Class
A class is a set of objects with the same attributes and services. It provides a unified abstract description for all objects of the class, it includes attributes and services.

40. Encapsulation
Encapsulation combines object attributes and services into an independent system unit and hides the internal details of objects as much as possible.
41. Inheritance
Inheritance means that a subclass can automatically own all attributes and services of the parent class.

42. Messages
A message is a service request sent by an object. It generally contains the Object ID, service ID, input information, and response information of the provided service.

43. Polymorphism
Polymorphism refers to the inheritance of attributes defined in the parent class or service quilt class, which can have different data types or show different behaviors.

44. Active Object
An active object is a set of attributes and encapsulation body of a group of services. At least one service can be actively executed (called an active service) without receiving messages ).

45. Object-Oriented Analysis
Object-Oriented Analysis (OOA) is to use the object-oriented method for demand analysis. Its main task is to analyze and understand the problem domain and find out the classes and objects required to describe the problem domain and system responsibility, analyzes their internal structures and external relationships and establishes the OOA model.

46. Object-oriented Design
Object-Oriented Design (OOD) is to use object-oriented technology to design system software based on the established analysis model. It directly converts the OOA model into an Ood model and supplements some implementation-related parts, such as man-machine interfaces, data storage, and task management.

47. Object-Oriented Programming
Object-Oriented Programming (OOP) is to use an object-oriented programming language to compile various components in the Ood model into a program.

48. Object-oriented Testing
Object-oriented testing (OOT) refers to the process of continuing to use OO Technology for software testing that is developed using OO technology.

49. Unified Modeling Language (UML)
Unified Modeling Language (UML) is a general visual modeling language for visual, clear, built, and documented software system products.

50. use case diagram
The use case diagram defines the functional requirements of the system. It views the system functions from outside the system and does not describe the specific implementation of the functions in the system.

51. Class Diagram
A class diagram describes the static structure of the system, indicating the class in the system and the relationship between the class and the class.

52. object graph
An object graph describes a group of objects and their relationships, indicating the object instances of the class.

53. status chart
A state chart indicates a state machine that emphasizes the Event Sequence of object behavior.

54. Sequence Chart
A time sequence diagram shows the dynamic collaboration between a group of objects, reflecting the time sequence of messages sent between objects.

55. Collaboration Diagram
A collaboration diagram shows the dynamic collaboration between a group of objects, reflecting the structure of the objects for sending and receiving messages.

56. activity diagram
The activity diagram reflects the process from one activity to another in the system, emphasizing the control process between objects.

57. Component Diagram
A component diagram describes components and their relationships, indicating the system's static implementation view.

58. distribution chart
The distribution chart reflects the physical architecture of software and hardware in the system, indicating the processing nodes and the configuration of components in the nodes during system operation.

59. Software Architecture
The software architecture includes a set of software components and the visible characteristics of the software components and their relationships, the visible features outside the software refer to the services, performance, features, error handling, and shared resource usage provided by software components.

60. Software Testing
Software testing systematically identifies potential errors and defects in the software with minimal time and manpower.

61. static testing
Static testing means that the tested program does not run on the machine, but uses manual testing and computer-aided static analysis to detect the program.

62. Dynamic Testing
Dynamic Testing refers to identifying errors through running programs. In general, testing mainly refers to dynamic testing.

63. Black box testing
Black box testing, also known as function testing or data-driven testing, is used to detect whether each function can be used properly when a product is known to have functionality.

64. white box testing
The white-box test is also called the structure test or logic-driven test. It knows the internal working process of the product and can be used to test whether the internal actions of the product are normal according to the specifications, test the program according to the internal structure of the program, and check whether each channel in the program can work correctly according to the predefined requirements, regardless of its function.

65. Software Debugging
Software Debugging is to determine the cause and accurate position of the error based on the error signs after the software test is successful and correct it.

66. software testing automation
Test automation is to automatically test the software system by developing and using some tools, which is particularly suitable for repeated and tedious activities during testing.

67. Software maintenance
Software maintenance refers to the modifications made to software products during the software operation or maintenance phase.

68. corrective maintenance
After the software is delivered and used, some errors that cannot be tested during development are exposed during the running stage due to incomplete or incomplete tests during development. In order to identify and correct software errors, correct Software Performance defects, and avoid mistakes in implementation, we should diagnose and correct errors. This is corrective maintenance.

69. Adaptive Maintenance
With the rapid development and upgrading of computer technology, the external environment or data environment required by the software system may be updated and upgraded, such as the replacement of the operating system or database system. In order to adapt the software system to this change, the software needs to be modified accordingly. This maintenance activity is called adaptive maintenance.

70. Excellent Maintenance
In the process of using the software, users often propose new functional and performance requirements for the software. To meet these requirements, software needs to be modified or re-developed to expand software functions, enhance software performance, improve processing efficiency, and improve Software maintainability. In this case, the maintenance activities are called Perfect Maintenance.

71. Preventive Maintenance
Preventive Maintenance refers to the use of advanced software engineering methods to re-design, compile and test a part of the software or software to be maintained, so as to improve the maintainability and reliability of the software, lay a good foundation for further software improvement.

72. Software maintainability
Software maintainability refers to the degree of difficulty that the software can be understood, corrected, adapted and improved to adapt to the new environment.

73. Project
A project is an effort made to achieve a specific goal by effectively utilizing resources on the premise of a unique and interrelated set of tasks.

74. Project Management
Project management is to achieve the goal of a plan by reasonably organizing and making use of all available resources according to the planned cost and schedule, it includes team management, risk management, procurement management, process management, time management, cost management, and quality management.