One thing I found interesting is user acceptance testing, which determines whether the new system meets user needs. Two common acceptance tests are alpha testing and beta testing. Alpha testing simulates and uses typical data for system testing, including recovery testing, security testing, stress testing, performance testing and other tests. Recovery testing is interesting because it forces the software to be unable to verify that the recovery was performed correctly. Stress testing is also interesting because it tries to destroy the system and see what happens. Beta testing uses real-time data used in the user’s actual work environment to determine whether software, documentation, technical support, and training activities are working as expected. Any problems found during the testing phase need to be corrected before the user actually accepts the system.
I’m interested in the testing methods.
Inspections: testing technique in which participants examine program code for predictable language-specific errors.
Desk checking: testing technique in which the program code is sequentially executed manually by the reviewer.
Unit testing :the process of testing each model alone in an attempt to discover any errors in it’s code.
Integration testing: the process of bring together all of the modules that a program comprises for testing process.
System testing:the bring together of all of the programs that a system comprises for testing process.
Sub testing:a technique used in testing modules,especially where modules are written and tested in a top down fashion,where a few lines of code are used to substitute for subordtinate modules.
After planning and maintenance, the system implementation phase is the beginning phase of all operations and the most expensive phase. I find the interesting part of this chapter is the process of documenting the system, training users, and supporting users. Analysts need to prepare documents that reveal all the important information about this system that you have accumulated during the development and implementation process.
From the reading material, I learn about that implementing a new information system into an organizational context is not a mechanical process. The organizational context has been shaped and reshaped by the people who work in the organization. The work habits, beliefs, interrelationships, and personal goals of an organization’s members all affect the implementa¬tion process. Although factors important to successful implementation have been identified, there are no sure recipes you can follow. During implementation, you must be attuned to key aspects of the organizational context, such as history, politics, and environmental demands— aspects that can contribute to implementation failure if ignored.
In reading Chapter 13, I was interested in the question “Why Implementation Sometimes Fails”. Although it is impossible for all projects to be successfully implemented in the end, according to the traditional view, a successful implementation should be achieved by satisfying the two conditions of “support for the system management under development” and “user participation in the development process”. . However, actual operation shows that despite the great help and cooperation provided by the management and users, the information system sometimes fails to implement. In 1997, Lucas put forward the point that the most common and most dependable way to determine whether the implementation is successful is the use of the system and the user’s satisfaction with the system. The six factors of user’s personal shares, system characteristics, user demographics, organizational support, performance, and satisfaction will affect the degree of use of the system.
One of the things that interested me from reading the material was “testing for information system implementation.” An integral part of information system implementation is the correct selection of test methods, the development of test plans that are fully traceable to requirements, and the acquisition of basic resources for successful completion of tests. Once completed, testing provides the stakeholders with confidence that the system or system components are performing as expected and delivering the required benefit realization at the beginning of the project.
Implementing a new information system into an organizational context is not a mechanical process. The organizational context has been shaped and reshaped by the people who work in the organization. The work habits, beliefs, interrelationships, and personal goals of an organization’s members all affect the implementation process. Although factors important to successful implementation have been identified, there are no sure recipes you can follow. During implementation, you must be attuned to key aspects of the organizational context, such as history, politics, and environmental demands— aspects that can contribute to implementation failure if ignored.
From this chapter I can learn about the knowledge about system implementation and have a better understand of the system.But one interesting thing for me is that like many other analysis and design activities, system implementation and operation of an Internet-based electronic commerce application is no different than the processes followed for other types of applications.Previously, you read how Jim Woo and the Pine Valley Furniture (PVF) development team transformed the conceptual data model for the WebStore into a set of normalized relations. To help focus the development of test cases and to assign primary responsibility to members of his team to specific areas of the system, Jim developed the following list of testing categories:Simple functionality ; Multiple functionality ; Function chains ; Elective functions ; Emergency/crisis.And at last a big part of successful system testing is to make sure that no information is lost and that all tests are described in a consistent way.
Security Issues:
The security of information systems has become an increasingly important issue for organizations and their management. One estimate for how much security breaches cost companies comes from a survey on security conducted by IBM Security and the Ponemon Institute. For 2017, the reported estimated annual average financial loss due to a data breach incident was US$3.62 million. However, we can be sure the actual amount of loss across the entire global economy is much, much more. Most firms do not like to admit financial losses due to security breaches, and those that do are hesitant to report the actual true amounts.
A majority of firms report that they have been victims of external threats, including malware (malicious software) and hacking. Other external security threats include phishing attacks, exploitation of applications, denial of service, and theft of computing or storage devices. Denial of service is a popular tactic used to prevent access to a Website.Common solutions include firewalls, e-mail security and spam filtering software, antivirus software, virtual private networks, and data encryption.
One of things that make me feel interesting is what is system implementation. System implementation is made up of many activities. The six major activities we are concerned with in this chapter are coding, testing, installation, documentation, training, and support. The purpose of these steps is to convert the physical system specifications into working and reliable software and hardware, docu- ment the work that has been done, and provide help for current and future users and caretakers of the system.
In this section the analyst needs to prepare documentation that reveals all the important information about the system that you have accumulated during development and implementation. During the implementation, you must adapt to key aspects of your organization’s environment, such as historical, political, and environmental requirements, which can lead to implementation failure if ignored.
After implementation, work on the system is just beginning. Today, as much as 80 percent of the life cycle cost of a system occurs after implementation.
Seven Different Types of Tests.
Why testing fail: 1. User’s personal stake. 2. System characteristics. 3. User demographics. 4. Organizational support. 5. Performance. 6. Satisfaction. At the same time, security of information system is becoming more and more important.
After reading MSAD, I was interested in security issues. The security of information systems has become an increasingly important issue for organizations and their management. a majority of firms report that they have been victims of external threats, including malware (malicious software) and hacking. Other external security threats include phishing attacks, exploitation of applications, denial of service, and theft of computing or storage devices. Although external threats are common, internal threats are common as well. Internal actors were responsible for over one-quarter of recorded data breaches. Common solutions include firewalls, e-mail security and spam filtering software, antivirus software, virtual private networks, and data encryption. Yet the weakest link in any computer defense is the people who use the computer system. The best defensive technology in the world cannot overcome human laziness and negligence. Sound systems security practice demands the effective use of appropriate information technologies as well as the diligent involvement of employees and decision makers in the defense of organization information technology assets.
I am more interested in how to test software applications.
There are two important things to remember about testing information systems:
1. The purpose of the test is to confirm that the system meets the requirements.
2. The test must be planned.
The test is not accidental. You have to pay to pay attention to many different aspects of the system, such as response time, response to boundary data, response to no input, response to a large number of inputs, etc. You must test anything and the system that might go wrong or go wrong. At the very least, you should test some of the most commonly used systems and other paths of the entire system within the time allowed.
Testing usually requires a lot of work. Manual code reviews can be very time-consuming and tedious work; and, most importantly, not always the best solution. Therefore, a special test software called a test tool is being developed. Developed specifically for various environments, it can help designers automatically check the quality of their code.
One thing that I am interested in is that the methods of computer training.In this chapter ,we got two types training ,computer training, self-training .
The common methods of computer training in 1987 were tuturial,course,computer-aided instruction ,interactive training manuajs,resident experts ,software help components ,and external sources such as vendors .training models now include videos, interactive television fo remote training ,multimedia training ,onlinr tutorials ,and electronic perfomance support systems .The training modes are delivered via DVDS, intranets, and the Internet.
After reading Chapter 13 “System Implementation”, I think the testing process is very fascinating. After all, the primary purpose of system testing is to evaluate whether the system meets the specified requirements. Testing can not only find deviations or errors from the target, but also eliminate potential risks that may affect the user’s business in the future to a certain extent. The textbook mentions seven different types of tests for applications, making the tests more practical. Know how to test and why it is necessary. The system will enter the new installation phase only after passing the different test phases. This shows that acceptance testing is a laborious and important cycle. Compared with the risk of finding defects in production, the cost of repairing the project in development is lower and the risk is less.
After reading Chapter 13 “System Implementation” of the textbook, I found that the loop structure of the system implementation is very interesting. The realization process is divided into different steps, which makes the process clearer and also enhances the practicality.
System implementation consists of many activities, mainly including six parts——coding, testing, installation, documentation, training and support. Coding requires a lot of experience, effort and skill. Coding may be simple or complex depending on the project, so it also needs to understand the nature of the testing process. Analysis, design, code, and testing often cannot be carried out separately from each other.
Of course, for system implementation, documentation is also a key activity that cannot be ignored. Documents are often ignored because they are “lengthy, tedious, or time-consuming.” In fact, a full understanding of the content of the document can help developers increase their attention and focus on the core functions that the solution should provide without deviating from the requirements. Communicating requirements without adequate documentation may cause significant risks and even lead to serious deviations between key requirements and expected functions.
The process of the test of software application is more attractive than other processes.
Like how changes to fix errors will be documented, what the test plan is and which people will do the system testing etc. And lots of requirements should follow during the test.
The purpose of testing is to confirm that the system satisfies requirements.
Testing must be planned.
A test case is a specific scenario of transactions, queries, or navigation paths that represent a typical, critical, or abnormal use of the system. A test case should be repeatable so that it can be rerun as new versions of the software are tested.
Chapter 13 addresses the variety of work done during system implementation. I am interested in the difference between agile methodologies and traditional methodologies while projects which is based on agile methodologies, coding and testing are done in concert with analysis and design, so systems resulting from such efforts will begin their implementation phases with coding and testing already completed. In other hand, Projects which based on traditional methodologies will begin implementation with detailed design specifications that are handed over to programming teams for coding and to quality assurance teams for testing.
Through reading the materials, I had a rough understanding of the implementation process of the system, methods of testing software programs, installation strategies, environmental hazards and remedial measures of the system, as well as practical application problems.
One of the things I’m most interested in is the installation of the system. System installation can not be generalized, need to choose from four ways according to the actual situation:1)direct,when the old system is shut off just as the new one is turned
on;2)parallel, when both old and new systems are run together until it is clear the new system is ready to be used exclusively;3)single-location, when one site is selected
to test the new system;4)phased, when the system is installed bit by bit.
After reading this paper, as far as I concerned, the paper main describes about the thought that the implemetation of the system is one of the important phase of the system, it also face threat from outside and inside, these dangerous problems need administrators of the system to improve their technologies regularly so that the system can be adopted at a relative safely environment, otherwise, the system users will also gain the impacts from the dangerous problems, which means that, the problems will cause the operation of the businesses of the users like organizations.
An essential part of information system implementation is the correct selection of test methods, the development of test plans that are fully traceable to requirements, and the acquisition of the basic resources needed to successfully complete the tests. Once completed, testing will reassure stakeholders that the system or system components are performing as expected and that the required revenue realization has been achieved at the beginning of the project. The textbook mentions seven different types of tests for the application, which makes testing more practical. Know how to test and why it’s necessary. Only after passing the different test phases will the system enter the new installation phase. This shows that acceptance testing is a difficult and important cycle. A project in development is less costly and less risky to fix than the risk of finding a manufacturing defect.
The process of testing software applications is more attractive than other processes involved.
Just like how the changes to correct errors will be recorded, how the test plan will be recorded, and the system will be tested by some person, there are many requirements that should be followed during the test.
The purpose of the test is to confirm that the system meets the requirements.
The test must be planned.
A test case is a specific scenario of a transaction, query or navigation path, and represents the type of system, critical or abnormal use. The test case should be repeatable, and it can be rerun when a new version of the software is tested.
I am interested in security issues, I have reviewed the relevant information and summarized as follows
According to the overall structure of information system security, information system security can be protected from five levels: physical, network, host system, application system and data. Therefore, technical security requirements are also divided into five levels accordingly. The safety requirements:
Physical security requirements: mainly provide basic background support and guarantee for the safe operation of information systems from the external environment, infrastructure, operating hardware, media, etc.;
Security requirements at the network level: Provide support for the information system to operate in a secure network environment, ensure the safe operation of the network system, and provide effective network services;
Host-level security requirements: Provide a secure operating system and a secure database management system in the case of physical and network security to achieve the safe operation of the operating system and database management system;
Application-level security requirements: with the support of physical, network, and system security, to achieve the security goals determined by user security requirements;
Data and backup and recovery level security requirements: Fully pay attention to the security of data in the process of storage, transmission, and processing in the information system.
Acceptance Testing by Users
Once the system tests have been satisfactorily completed, the system is ready for
acceptance testing, which is testing the system in the environment where it will
eventually be used. Acceptance refers to the fact that users typically sign off on the
system and “accept” it once they are satisfied with it. The purpose of acceptance
testing is for users to determine whether the system meets their requirements. The
extent of acceptance testing will vary with the organization and with the system
in question.
Acceptance testing
The process whereby actual users test a completed information system, the end result of which is the users’ acceptance of it.
Alpha testing
User testing of a completed information system using simulated data.
Beta testing
User testing of a completed information system using real data in the real user environment.
What I am most interested in is the test method. An essential part of the implementation of the information system is to correctly select the test method, develop a test plan that can be fully traced back to the requirements, and obtain the basic resources needed to successfully complete the test. And in the implementation process, you must adapt to key aspects of the organizational environment, such as historical, political, and environmental needs, which can lead to implementation failure if ignored.
There is a section in this chapter that introduces various test methods in detail:
Software application testing is an umbrella term covering multiple types of testing. The test can be carried out using static or dynamic technology, and can be selected automatically or manually. Static testing means that the code being tested is not executed. The result of running the code is not a problem for that particular test. And dynamic testing involves the execution of code. Automated testing means that the computer performs the test, while manual testing means that people complete the test.
1. Inspection: A testing technique in which participants can check whether there are predictable language-specific errors in the program code.
2. Inspection on the table: A testing technique in which the program code is manually executed in sequence by the reviewer.
3. Unit testing: the process of individually testing each module to find any errors in its code.
4. Integration test: the process of combining all the modules included in the program for testing purposes. Modules are usually integrated in a top-down, incremental manner. To
5. System testing: All the programs included in the system are combined for testing purposes. Programs are usually integrated in a top-down, incremental manner.
6. Stub test: a technique for testing modules, especially when writing and testing modules in a top-down manner, replacing subordinate modules with a few lines of code.
7. User acceptance test: The actual user tests a complete information system, and the final result is the process of user acceptance. The most complete acceptance testing will include alpha testing, which uses simulated but typical data for system testing; beta testing, which uses real-time data in the user’s real work environment; and the system conducted by the organization’s internal auditors or quality assurance team members Audit.
The types of tests performed during alpha testing include:
(1) Recovery test-Force the software (or environment) to fail to verify that the recovery has been performed correctly.
(2) Security test—Verify that the built-in protection mechanism of the system will protect the system from improper intrusion.
(3) Stress test-try to destroy the system (for example, write records to the database in the case of incomplete information, or what happens when there is an extreme online transaction load or a large number of concurrent users).
(4) Performance testing-to determine the performance of the system in the range of possible environments (for example, different hardware configurations, networks, operating systems, etc.); usually, the goal is to make the system have a similar response time in each environment And other performance metrics to perform.
In beta testing, a subset of target users use their own data to run the system in the user’s own environment. The purpose of beta testing is to determine whether software, documentation, technical support and training activities are effective
8. Sub-testing: a technique for testing modules, especially in the process of writing and testing modules in a top-down manner, using a few lines of code to replace subordinate modules.
Yu Hu says
One thing I found interesting is user acceptance testing, which determines whether the new system meets user needs. Two common acceptance tests are alpha testing and beta testing. Alpha testing simulates and uses typical data for system testing, including recovery testing, security testing, stress testing, performance testing and other tests. Recovery testing is interesting because it forces the software to be unable to verify that the recovery was performed correctly. Stress testing is also interesting because it tries to destroy the system and see what happens. Beta testing uses real-time data used in the user’s actual work environment to determine whether software, documentation, technical support, and training activities are working as expected. Any problems found during the testing phase need to be corrected before the user actually accepts the system.
Yujia Hu says
I’m interested in the testing methods.
Inspections: testing technique in which participants examine program code for predictable language-specific errors.
Desk checking: testing technique in which the program code is sequentially executed manually by the reviewer.
Unit testing :the process of testing each model alone in an attempt to discover any errors in it’s code.
Integration testing: the process of bring together all of the modules that a program comprises for testing process.
System testing:the bring together of all of the programs that a system comprises for testing process.
Sub testing:a technique used in testing modules,especially where modules are written and tested in a top down fashion,where a few lines of code are used to substitute for subordtinate modules.
Lei Tian says
After planning and maintenance, the system implementation phase is the beginning phase of all operations and the most expensive phase. I find the interesting part of this chapter is the process of documenting the system, training users, and supporting users. Analysts need to prepare documents that reveal all the important information about this system that you have accumulated during the development and implementation process.
Ying Cheng says
From the reading material, I learn about that implementing a new information system into an organizational context is not a mechanical process. The organizational context has been shaped and reshaped by the people who work in the organization. The work habits, beliefs, interrelationships, and personal goals of an organization’s members all affect the implementa¬tion process. Although factors important to successful implementation have been identified, there are no sure recipes you can follow. During implementation, you must be attuned to key aspects of the organizational context, such as history, politics, and environmental demands— aspects that can contribute to implementation failure if ignored.
Yijing Zhan says
In reading Chapter 13, I was interested in the question “Why Implementation Sometimes Fails”. Although it is impossible for all projects to be successfully implemented in the end, according to the traditional view, a successful implementation should be achieved by satisfying the two conditions of “support for the system management under development” and “user participation in the development process”. . However, actual operation shows that despite the great help and cooperation provided by the management and users, the information system sometimes fails to implement. In 1997, Lucas put forward the point that the most common and most dependable way to determine whether the implementation is successful is the use of the system and the user’s satisfaction with the system. The six factors of user’s personal shares, system characteristics, user demographics, organizational support, performance, and satisfaction will affect the degree of use of the system.
Xiaohan Chen says
One of the things that interested me from reading the material was “testing for information system implementation.” An integral part of information system implementation is the correct selection of test methods, the development of test plans that are fully traceable to requirements, and the acquisition of basic resources for successful completion of tests. Once completed, testing provides the stakeholders with confidence that the system or system components are performing as expected and delivering the required benefit realization at the beginning of the project.
Chang Cui says
Implementing a new information system into an organizational context is not a mechanical process. The organizational context has been shaped and reshaped by the people who work in the organization. The work habits, beliefs, interrelationships, and personal goals of an organization’s members all affect the implementation process. Although factors important to successful implementation have been identified, there are no sure recipes you can follow. During implementation, you must be attuned to key aspects of the organizational context, such as history, politics, and environmental demands— aspects that can contribute to implementation failure if ignored.
Yiqiong Zhang says
From this chapter I can learn about the knowledge about system implementation and have a better understand of the system.But one interesting thing for me is that like many other analysis and design activities, system implementation and operation of an Internet-based electronic commerce application is no different than the processes followed for other types of applications.Previously, you read how Jim Woo and the Pine Valley Furniture (PVF) development team transformed the conceptual data model for the WebStore into a set of normalized relations. To help focus the development of test cases and to assign primary responsibility to members of his team to specific areas of the system, Jim developed the following list of testing categories:Simple functionality ; Multiple functionality ; Function chains ; Elective functions ; Emergency/crisis.And at last a big part of successful system testing is to make sure that no information is lost and that all tests are described in a consistent way.
Xiaomeng Chen says
Security Issues:
The security of information systems has become an increasingly important issue for organizations and their management. One estimate for how much security breaches cost companies comes from a survey on security conducted by IBM Security and the Ponemon Institute. For 2017, the reported estimated annual average financial loss due to a data breach incident was US$3.62 million. However, we can be sure the actual amount of loss across the entire global economy is much, much more. Most firms do not like to admit financial losses due to security breaches, and those that do are hesitant to report the actual true amounts.
A majority of firms report that they have been victims of external threats, including malware (malicious software) and hacking. Other external security threats include phishing attacks, exploitation of applications, denial of service, and theft of computing or storage devices. Denial of service is a popular tactic used to prevent access to a Website.Common solutions include firewalls, e-mail security and spam filtering software, antivirus software, virtual private networks, and data encryption.
Yue Ma says
One of things that make me feel interesting is what is system implementation. System implementation is made up of many activities. The six major activities we are concerned with in this chapter are coding, testing, installation, documentation, training, and support. The purpose of these steps is to convert the physical system specifications into working and reliable software and hardware, docu- ment the work that has been done, and provide help for current and future users and caretakers of the system.
Yalin Zou says
In this section the analyst needs to prepare documentation that reveals all the important information about the system that you have accumulated during development and implementation. During the implementation, you must adapt to key aspects of your organization’s environment, such as historical, political, and environmental requirements, which can lead to implementation failure if ignored.
Haoyu Bai says
After implementation, work on the system is just beginning. Today, as much as 80 percent of the life cycle cost of a system occurs after implementation.
Seven Different Types of Tests.
Why testing fail: 1. User’s personal stake. 2. System characteristics. 3. User demographics. 4. Organizational support. 5. Performance. 6. Satisfaction. At the same time, security of information system is becoming more and more important.
Tianyu Zhang says
After reading MSAD, I was interested in security issues. The security of information systems has become an increasingly important issue for organizations and their management. a majority of firms report that they have been victims of external threats, including malware (malicious software) and hacking. Other external security threats include phishing attacks, exploitation of applications, denial of service, and theft of computing or storage devices. Although external threats are common, internal threats are common as well. Internal actors were responsible for over one-quarter of recorded data breaches. Common solutions include firewalls, e-mail security and spam filtering software, antivirus software, virtual private networks, and data encryption. Yet the weakest link in any computer defense is the people who use the computer system. The best defensive technology in the world cannot overcome human laziness and negligence. Sound systems security practice demands the effective use of appropriate information technologies as well as the diligent involvement of employees and decision makers in the defense of organization information technology assets.
Shengyuan Yu says
I am more interested in how to test software applications.
There are two important things to remember about testing information systems:
1. The purpose of the test is to confirm that the system meets the requirements.
2. The test must be planned.
The test is not accidental. You have to pay to pay attention to many different aspects of the system, such as response time, response to boundary data, response to no input, response to a large number of inputs, etc. You must test anything and the system that might go wrong or go wrong. At the very least, you should test some of the most commonly used systems and other paths of the entire system within the time allowed.
Testing usually requires a lot of work. Manual code reviews can be very time-consuming and tedious work; and, most importantly, not always the best solution. Therefore, a special test software called a test tool is being developed. Developed specifically for various environments, it can help designers automatically check the quality of their code.
Weiwei Zhao says
One thing that I am interested in is that the methods of computer training.In this chapter ,we got two types training ,computer training, self-training .
The common methods of computer training in 1987 were tuturial,course,computer-aided instruction ,interactive training manuajs,resident experts ,software help components ,and external sources such as vendors .training models now include videos, interactive television fo remote training ,multimedia training ,onlinr tutorials ,and electronic perfomance support systems .The training modes are delivered via DVDS, intranets, and the Internet.
Zijie Yuan says
After reading Chapter 13 “System Implementation”, I think the testing process is very fascinating. After all, the primary purpose of system testing is to evaluate whether the system meets the specified requirements. Testing can not only find deviations or errors from the target, but also eliminate potential risks that may affect the user’s business in the future to a certain extent. The textbook mentions seven different types of tests for applications, making the tests more practical. Know how to test and why it is necessary. The system will enter the new installation phase only after passing the different test phases. This shows that acceptance testing is a laborious and important cycle. Compared with the risk of finding defects in production, the cost of repairing the project in development is lower and the risk is less.
Xuemeng Li says
After reading Chapter 13 “System Implementation” of the textbook, I found that the loop structure of the system implementation is very interesting. The realization process is divided into different steps, which makes the process clearer and also enhances the practicality.
System implementation consists of many activities, mainly including six parts——coding, testing, installation, documentation, training and support. Coding requires a lot of experience, effort and skill. Coding may be simple or complex depending on the project, so it also needs to understand the nature of the testing process. Analysis, design, code, and testing often cannot be carried out separately from each other.
Of course, for system implementation, documentation is also a key activity that cannot be ignored. Documents are often ignored because they are “lengthy, tedious, or time-consuming.” In fact, a full understanding of the content of the document can help developers increase their attention and focus on the core functions that the solution should provide without deviating from the requirements. Communicating requirements without adequate documentation may cause significant risks and even lead to serious deviations between key requirements and expected functions.
Zhiyuan Lian says
The process of the test of software application is more attractive than other processes.
Like how changes to fix errors will be documented, what the test plan is and which people will do the system testing etc. And lots of requirements should follow during the test.
The purpose of testing is to confirm that the system satisfies requirements.
Testing must be planned.
A test case is a specific scenario of transactions, queries, or navigation paths that represent a typical, critical, or abnormal use of the system. A test case should be repeatable so that it can be rerun as new versions of the software are tested.
Yongheng Luo says
Chapter 13 addresses the variety of work done during system implementation. I am interested in the difference between agile methodologies and traditional methodologies while projects which is based on agile methodologies, coding and testing are done in concert with analysis and design, so systems resulting from such efforts will begin their implementation phases with coding and testing already completed. In other hand, Projects which based on traditional methodologies will begin implementation with detailed design specifications that are handed over to programming teams for coding and to quality assurance teams for testing.
Yanxue Li says
Through reading the materials, I had a rough understanding of the implementation process of the system, methods of testing software programs, installation strategies, environmental hazards and remedial measures of the system, as well as practical application problems.
One of the things I’m most interested in is the installation of the system. System installation can not be generalized, need to choose from four ways according to the actual situation:1)direct,when the old system is shut off just as the new one is turned
on;2)parallel, when both old and new systems are run together until it is clear the new system is ready to be used exclusively;3)single-location, when one site is selected
to test the new system;4)phased, when the system is installed bit by bit.
Yutong Sun says
After reading this paper, as far as I concerned, the paper main describes about the thought that the implemetation of the system is one of the important phase of the system, it also face threat from outside and inside, these dangerous problems need administrators of the system to improve their technologies regularly so that the system can be adopted at a relative safely environment, otherwise, the system users will also gain the impacts from the dangerous problems, which means that, the problems will cause the operation of the businesses of the users like organizations.
Yuting Yang says
An essential part of information system implementation is the correct selection of test methods, the development of test plans that are fully traceable to requirements, and the acquisition of the basic resources needed to successfully complete the tests. Once completed, testing will reassure stakeholders that the system or system components are performing as expected and that the required revenue realization has been achieved at the beginning of the project. The textbook mentions seven different types of tests for the application, which makes testing more practical. Know how to test and why it’s necessary. Only after passing the different test phases will the system enter the new installation phase. This shows that acceptance testing is a difficult and important cycle. A project in development is less costly and less risky to fix than the risk of finding a manufacturing defect.
Dacheng Xu says
The process of testing software applications is more attractive than other processes involved.
Just like how the changes to correct errors will be recorded, how the test plan will be recorded, and the system will be tested by some person, there are many requirements that should be followed during the test.
The purpose of the test is to confirm that the system meets the requirements.
The test must be planned.
A test case is a specific scenario of a transaction, query or navigation path, and represents the type of system, critical or abnormal use. The test case should be repeatable, and it can be rerun when a new version of the software is tested.
Shengjie Zhang says
I am interested in security issues, I have reviewed the relevant information and summarized as follows
According to the overall structure of information system security, information system security can be protected from five levels: physical, network, host system, application system and data. Therefore, technical security requirements are also divided into five levels accordingly. The safety requirements:
Physical security requirements: mainly provide basic background support and guarantee for the safe operation of information systems from the external environment, infrastructure, operating hardware, media, etc.;
Security requirements at the network level: Provide support for the information system to operate in a secure network environment, ensure the safe operation of the network system, and provide effective network services;
Host-level security requirements: Provide a secure operating system and a secure database management system in the case of physical and network security to achieve the safe operation of the operating system and database management system;
Application-level security requirements: with the support of physical, network, and system security, to achieve the security goals determined by user security requirements;
Data and backup and recovery level security requirements: Fully pay attention to the security of data in the process of storage, transmission, and processing in the information system.
Lisheng Lin says
Acceptance Testing by Users
Once the system tests have been satisfactorily completed, the system is ready for
acceptance testing, which is testing the system in the environment where it will
eventually be used. Acceptance refers to the fact that users typically sign off on the
system and “accept” it once they are satisfied with it. The purpose of acceptance
testing is for users to determine whether the system meets their requirements. The
extent of acceptance testing will vary with the organization and with the system
in question.
Acceptance testing
The process whereby actual users test a completed information system, the end result of which is the users’ acceptance of it.
Alpha testing
User testing of a completed information system using simulated data.
Beta testing
User testing of a completed information system using real data in the real user environment.
Ziqiao Wang says
What I am most interested in is the test method. An essential part of the implementation of the information system is to correctly select the test method, develop a test plan that can be fully traced back to the requirements, and obtain the basic resources needed to successfully complete the test. And in the implementation process, you must adapt to key aspects of the organizational environment, such as historical, political, and environmental needs, which can lead to implementation failure if ignored.
Hang Zhao says
There is a section in this chapter that introduces various test methods in detail:
Software application testing is an umbrella term covering multiple types of testing. The test can be carried out using static or dynamic technology, and can be selected automatically or manually. Static testing means that the code being tested is not executed. The result of running the code is not a problem for that particular test. And dynamic testing involves the execution of code. Automated testing means that the computer performs the test, while manual testing means that people complete the test.
1. Inspection: A testing technique in which participants can check whether there are predictable language-specific errors in the program code.
2. Inspection on the table: A testing technique in which the program code is manually executed in sequence by the reviewer.
3. Unit testing: the process of individually testing each module to find any errors in its code.
4. Integration test: the process of combining all the modules included in the program for testing purposes. Modules are usually integrated in a top-down, incremental manner. To
5. System testing: All the programs included in the system are combined for testing purposes. Programs are usually integrated in a top-down, incremental manner.
6. Stub test: a technique for testing modules, especially when writing and testing modules in a top-down manner, replacing subordinate modules with a few lines of code.
7. User acceptance test: The actual user tests a complete information system, and the final result is the process of user acceptance. The most complete acceptance testing will include alpha testing, which uses simulated but typical data for system testing; beta testing, which uses real-time data in the user’s real work environment; and the system conducted by the organization’s internal auditors or quality assurance team members Audit.
The types of tests performed during alpha testing include:
(1) Recovery test-Force the software (or environment) to fail to verify that the recovery has been performed correctly.
(2) Security test—Verify that the built-in protection mechanism of the system will protect the system from improper intrusion.
(3) Stress test-try to destroy the system (for example, write records to the database in the case of incomplete information, or what happens when there is an extreme online transaction load or a large number of concurrent users).
(4) Performance testing-to determine the performance of the system in the range of possible environments (for example, different hardware configurations, networks, operating systems, etc.); usually, the goal is to make the system have a similar response time in each environment And other performance metrics to perform.
In beta testing, a subset of target users use their own data to run the system in the user’s own environment. The purpose of beta testing is to determine whether software, documentation, technical support and training activities are effective
8. Sub-testing: a technique for testing modules, especially in the process of writing and testing modules in a top-down manner, using a few lines of code to replace subordinate modules.