|
1. The importance of software error-processing before implementation
We can see from the figure, in the phrases in a project lifecycle, there are 6 phases, listed in order is feasibility, analysis, design, program specification, programming phrase, and unit test; while from the 指导留学生计算机本科论文software levels of testing, there are 4 steps, namely and orderly, acceptance test, system test, integration test and unit test. If the software errors have not been corrected before implementation, the following problems will be caused:
Firstly, the results of software operation with errors are unpredictable. After implementation, the consequences caused by software errors may cause abnormal program operation, or wrong results, or over-occupation of resources, such as memory and CPU, or collapse of the entire system thus damage the procedures and data been processing.
Secondly, the software with errors will increase cost of ownership. After implementation, the software errors will undergo all software engineering processes, therefore cost is not used in the places where need it.
Thirdly, the software with errors will increase development cost. The software error caused by architectural error may lead to the entire software modification from basis, which needs start from the very beginning and will substantially increase the development cost.
Finally, the software with errors may form software or system security vulnerabilities. After implementation, the software errors could leave the system or software itself the opportunities to be abused by malicious abusers like hacker.
However, if the software errors can be handled properly before implementation, the correctness of software architecture, process and results can be guaranteed, thus the software problems can be solved and the unnecessary cost can be reduced.
2. The process of dealing with client changes BEFORE and AFTER implementation
Receiving a client change requirement BEFORE software implementation, the processing procedures are as follows:
(1) In the feasibility phase, demonstrate what kind of impact will be brought to the entire software architecture and whether those changes can be realized in the original software architecture and function modules.
(2) In the analysis phase, define the client function and performance requirements to form the demand specification instruction as basis for software changes.
(3) In the design phase, reflect the client changes in the software architecture, function modules and coding to realize the software function and performance.
(4) In the test phase, because client changes have been presented in code, design and realization, the realization of client changes can conduct normal test as other function and performance requirements do, thus guarantee the realization of the software as a whole.
Receive a client change requirement AFTER implementation, the process is as follows:#p#分页标题#e#
In the feasibility demonstration phase, first of all, demonstrate that keep the software architecture basis unchanged, whether the client change requirements can be realized only by adding relevant modules.
There are two possibilities, namely, it can be realized on the basis of original software architecture and it can not be realized. The following is the discussion of the two possibilities:
a) It can be realized on the basis of original software architecture
Because it can be directly structured on the original software basis, the data can be realized only through adding software modules or modifying original software process; therefore, it can be completed by adding functional modules to the software.
b) It can not be realized on the basis of original software architecture
If not, the software basis needs re-structure, which may require the re-development of the entire software, or just inform the client that the new demand can not be achieved. In this case, the entire software needs re-structure, and should be re-developed in accordance with the new structure.
指导留学生计算机本科论文The importance of software system architecture can be seen from the comparison of the two processes. Users’ demands are changing constantly; therefore, try to adopt good basic software architecture to satisfy the changing needs of users, or through re-use, minimize the software development cycle if possible with the possibly lowest cost.
请明确第二个问题中应用phrase还是phase，因为按字面意思应为phase，如果惯用语应为phrase则不需要更改。
1.第一处应该是need，places是复数。
2，删除systematic 意思不变，更为精简。
3. 用phase。
|
