Wk 5 Discussion 1 [Due Thu] Answer The Question And Respond To Three Peers

Discussion Topic

Something that is easy to overlook, but critical to the success of a systems project, is the quality of the development work. Testing needs to occur and is generally based on the approved requirements and design.

How would you best ensure quality when developing a new system? Explain the inputs and outputs to testing. Use any relevant examples you have from your experiences within your own organizations, or organizations that you are familiar with.

Post your answers to the discussion forum.

Respond to at least three of your peers. In your response, consider providing other examples that support your peer’s perspective.

PEER 1

Hello Everyone,

When it comes to the quality of the software of a prototype or product, testing is going to ensure the success of the quality being produced. There is something to be said for testing to occur as often as possible and have various types of testing implemented. This is usually generated within a master plan set in the analysis phases. Integration and the test plans for the system are typically produced in the design phase. The plans are what dissect the actual testing and what is done through the implementation phase. Each team member role should already be specified and ensure the tests have been properly completed.

Input into the plans will also shape the quality desired. Going off of plans alone is not enough. You need perspective. Insight. Perception. Reality. By explaining the in and outs of the project as a whole, the testing phase will take a more firm hold.

There are several different types of testing used to test and track software issues and errors. Keep a list and track the code errors or bugs found in the programming language being worked with. Inspections are needed on a regular basis. Some of the highlights are the syntax, the units being worked with, other applications embedded into the system program, and the system overall. FOLLOW THE REQUIREMENTS! This is what is there to set you up for success. The requirements are going to assist with solving a lot of the problems possibly encountered along the way. The system will then end up being exactly or close to what was originally intended. This is why testing needs to be completed as often as possible because this is a self checking method to making sure the requirements are being followed and everyone is getting what they need. Then determine your next steps.

We had a system called ECF that was going to be used fr our clients. This was going to house personal data so we had strict requirements to adhere by in order to keep this type of data protected. It took a long time and lots of testing was done. In the end, it came out well. Linux is still used in government systems a lot. It pretty compatible with most other government systems.

References Used:

Valacich, J. S., & George, J. F. (2017). Modern systems analysis and design (8th ed.). Boston, MA: Pearson.

PEER 2

To ensure a quality software product, testing needs to begin early in the project. A master test plan is created in the analysis phase. Unit, integration and system test plans are created in the design phase. These plans are the inputs that help shape the actual testing that is done in the implementation phase, determines each team member’s role in the testing process and makes sure all tests have been done.

According to our Chapter 13 reading this week, there are seven different types of tests to check the software to check for errors in the code, bugs in the system or system failure: inspections, syntax checking, walk-throughs, desk checking, unit testing, integration testing and system checking. They also need to be sure that it meets the requirements and solves the business problem it was originally designed for. The outputs are the test case description documents that outline what portion of the software is being tested, who performed the test, the expected and actual results of the test. The test case results documentation lists the module being tested and a description of the difference between the actual and expected results and what the next steps will be.

The only experience I have with software testing is the project I worked on at my previous job to create an online portfolio for our new teachers. I worked with the development team to do the alpha testing to help work out the major issues and our department and a couple of schools did the beta testing to work out the little kinks. Several years ago my ex-husband did some beta testing on the Raspberry Pi. They sent him the little card to test and give them feedback, and he basically turned our tv into a computer. I have to admit, it was pretty cool when I was working from home to work on my Excel spreadsheets and Access database on such a huge screen….haha!

Reference:

Valacich, J. S., & George, J. F. (2017). Modern systems analysis and

design (8th ed.). Boston, MA: Pearson.

PEER 3

There is quite a bit that can be done to ensure the system being developed is of the highest quality. From the start, analysts need to plan early for tests. This gives analysts plenty of time to create tests that will identify problems within the logic. There various tests that fall under the umbrella of two types: Static and Dynamic. For static, no code is executed during the testing, and revolves around checks such as inspections and syntax checking. In dynamic testing, tests such as the unit test, integration test, and system tests ensure from the very basic modules to the most complex integration of modules that the logic is performing adequately. Test cases can be created that can test the functionality through specific scenarios, whether it be a standard scenario or an unusual scenario in which the software would not be typically used. These test should be performed each time a module is added and a new revision released to make sure that the modules are communicating correctly and producing the desired results when coupled with the other modules. A technique used in eXtreme programing to create better quality software is called refactoring, where the code is refined as much as possible to optimize the code and make it more readable. Alpha testing, which is the testing of a complete system using simulated data, and Beta testing, which is the testing of complete system using live data, can also be used to refine the system more and prepare it for production.