IT technical department structure is divided:
Products Division: user requirements, interface prototype (expected results)
Development department: coding, program (the actual effect)
Test Division: find Bug (ratio of the difference between the actual results and expected results)
Operation and maintenance department: on-line, maintenance
First, the software-related
1. What is software?
= + Software program documentation
2, the software life cycle (how software is made out of)
For example: to build a house
Plans, requirements, design (outline design, detailed design), construction, testing, use
(1) program (time, personnel, resources, risk assessment)
(2) requirements (functional requirements, performance requirements, security requirements, compliance requirements, etc.)
(3) design (outline design, detailed design)
(4) coding (C, C ++, Java, Python, etc. source, object program)
(5) Test (verify that the software meets the requirements specification, SRS)
(6) the operation and maintenance
3, soft-development model
(1) Waterfall (time must be from top to bottom)
100% 100% design requirements ------ ------ ------ 100% on-line test coding -------
Advantages: less demand change, reduce a lot of duplication of work, quality greatly improved.
Disadvantages: very long period
(2) model agile (scrum, spiral model)
Pros: short development cycle
4, software testing
(1) Definition:
(2) Test Purpose:
Positive test; reverse the test
Principle (3) Software Testing
All software testing should be traced back to user needs;
Early start of testing (phase involves testing needs work)
Exhaustive testing is impossible;
Test is risky;
Not all defects are worthy of repair;
Cluster bug effect: the more defects found, the defects will be described more;
Two steps forward, a step back;
5, composed of personnel software project
(1) Project Manager
(2) the analyst
(3) Designers
(4) coder
(5) testers
(6) QA
Duties:
a. norm
b. supervise whether the project team in accordance with normative work
c. Review the results of the test (test plan, test plan, test cases, bug reports)
(7) Configuration Management
a. + CI = Code Document
5. The reason for introducing software defects
(1) demand
(2) Design
(3) coding
(4) Other