Theory of Software Fundamentals

One, what is a software product

It is a logical product without entities, including programs, documents and data, and needs to be displayed through terminal equipment to reflect its functions and functions

Second, intermediate process documentation of software products

Customer needs

Product Requirements

Requirements specification

Project plan

Version Plan

Technical selection report

Competitor research report

Outline Design

Detailed design

Test Plan

Test plan

Test cases

Test report

Defect Tracking Sheet

Third, what are the roles of the completion software

Product Manager (PM): Requirements research, customer docking, output requirements documents

Project Manager (PM): project planning, progress control, major event decision-making, personnel scheduling, risk management, and team coordination

Architect (FD): technical selection, technical experts, key module implementation

Programmer (FG): Design, code, fix bugs

Test Engineer (TE): Find bugs in software and submit them

Fourth, the development process of software products

The process of a software product from initial conception to final release

Five, common development models

Waterfall Model, Agile Development Model, V Model, W Model, X Model, H Model, Spiral Model

1, the process of waterfall model: project planning-requirements analysis-software planning-program development-software testing-integration maintenance

Features: Linear structure, each stage has milestonesMeaning, document-driven, stage review mechanism

Advantages: It provides a basic framework of software development, which is conducive to large-scale software development and management, and is conducive to the use of development methods and tools, and improves the quality and efficiency of software

Disadvantages: The development time is too long, and the cost of error correction is too high

2, V model

3, W model

4, Agile iterative model

Standing Meeting (Morning Meeting):

Three questions: what did you do yesterday, what are you going to do today, what problems did you encounter within 15 minutes
No need to actually solve the problem (after the meeting)

​ Product Owner (PO): Specify the product release date and content, and have the right to accept or reject the development results

​ Process Manager (SM): Responsible for the process management of the entire development process, breaking the communication barrier between development and customers

​ Development Team (ST): Complete the development work according to the prescribed process. Different people are responsible for different technical implementations. The working methods are not limited to the form, as long as the goals can be completed.

Six, the purpose of the software development process model

Make the software meet customer needs

Improve product quality and reduce development costs

The project can be managed and the progress can be controlled

As a test, use your skills to help create the perfect software as much as possible

Seven, software life cycle

Requirements-Design-Code-Test-Maintenance-Upgrade-Abandon

VIII. Definition of software quality: the sum of characteristics that reflect the ability of an entity to satisfy or imply a need

IX, Software Quality Model

Six features: functionality, reliability, ease of use, efficiency, maintainability, portability

(1) Functionality: Functionality refers to the ability of a software product to satisfy both explicit and implicit required functions when the software is used under specified conditions

(2) Reliability: The ability to perform a specified function under a specified time and under specified conditions

(3) Ease of use: easy to understand, easy to learn, easy to use, and attractive to users

(4) Efficiency: The ability of the software to provide appropriate performance for resource utilization situations

(5) Maintainability: Four provisions, the ability to repair the specified function under specified conditions, within specified time, and with specified methods or tools

(6) Portability: the ability to migrate from one environment to another

Ten, the difference between QA and QC

(1) QA: Mainly engaged in prior quality assurance activities, focusing on prevention, reducing the chance of reducing the occurrence of errors

(2) QC: Mainly engaged in post-event quality inspection activities, expecting to find and report problems

(3) QA orientation and quality management system and maintenance, quality training, certification system audit, QC orientation and quality inspection and control

(4) The work of QA involves all departments in the whole process and has a wide range. QC mainly focuses on quality inspection

Eleventh, CMMI: Software Capability Maturity Model Synthesis

(1) is divided into five grades

Level 1: Initial Level

Level 2: Managed Level

Level 3: Defined Level

Level 4: Quantitative Management Level

Level 5: Continuous Optimization Level

(2) PA: Process Area (a collection of practices)

(3) Goal: Goal

(4) Practice: Practice

Now I invite you to join our software testing learning exchange group: [746506216], note "join the group", everyone can join togetherDiscuss and communicate software testing, learn software testing techniques, interviews and other aspects of software testing together. There will also be free live classes to gain more testing skills. Let's advance Python automated testing/test development together and move towards a high-paying careerroad.

Friends who like software testing, if my blog is helpful to you, if you like my blog content, please "Like", "Comment" and "Favorite" with one click!