CMGT 555 Wk 5 DQ 1

profileodthesoikts

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.


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



PEER 1  


When ensuring quality when developing a new system, it’s good to have inputs and outputs when testing. When I think of inputs for testing having a plan in place with a scope and schedule is important, the next section of inputs goes to data, the environment and having test cases. With outputs those include test results, and reports. When I think of a relevant experience in my own organization is with testing in which I do test cases and when I put together our software test plans. Having those a part of our organization helps with software change requests as everything is kept in order which includes having test results.



PEER 2  


For my organization's security group, we're using a Security Information and Event Management (SIEM) called ArcSight. It's a powerful system that has improved security environments and forced other developers to work harder to make their SIEM's better. Well, the time has come that we move away from that and go to a new system called Securonyx. This baby has already proven to pack a huge punch against security threats! The system has much better servicing, newer features, improved alerting, and high-end detections using a massive Artificial Intelligence engine. No, it will not faze out our security analysts, as we will always need a human presence.

We are currently in testing right now for Securonyx. We're testing processing times, incoming alert detections, case creations, case management, data store needs, load times, load balancing, CPU utilization, web-only access, access securities, and much, much more. We'll remain in the testing or beta phase for approximately 2 more weeks and the head of our security department will make the ultimate decision to change over and when it'll happen. Eventually our ArcSight SIEM will reach End Of Life (EOL) in Sep 2019. The licenses, servers, and sensors will literally all end at the same time. It's kind of strange how that took place all in the same week, and it was not planned. The server support for warranty and licensing all end within the same week as the SIEM operations license does. I've never seen that happen before. Timing....what can you do?

So far, the output results are amazingly different from our current setup. We think that the reason for the differences are that our current ArcSight SIEM is local, in a desktop client mode, and the systems (e.g. servers, data stores, and infrastructure) are much older at 8 yrs now. The Securonyx system is all web-based with a "legacy" local access relay server (4 yrs old) being set up in our backup data center. The relay server is basically just used for authentication and providing us a direct connection to the service. We will maintain a brand new server relay in our primary data center when all testing has been completed. The Securonyx system has been fully customized just for us. No other system exists that matches our current corporate infrastructure configuration and needs. With the system being fully customized, we as a customer were able to sit in on every-other-day meetings to provide input, test options, change anything we needed, and so on. Having the alternating daily meetings allowed the developers to manipulate code each day and then have us test it out live.

To date, we are very happy with the results and our director has already informed us that we will move over to this new system. We are to continue testing until the last minute and will be on the new system by July. That will give us 2 months to obtain full on-site training for all analysts, work with the system hands-on, get a feel for how it truly operates while our team members are on shift doing the actual work and analysis live, and then shutdown the ArcSight services for good. In total, our managers finally told us how much they're spending on this overhaul. It was a whopping $2.1 mil. We were blown away. However, we feel that our detections and analysis is about to greatly improve!



PEER 3


For me when i am developing a new system or I am the lead on a new system being developed, i ensure that there is top class quality by doing the testing. At the testing phase i ensure that the product is checked, tested and that is performed according to the project plan and the organization expectation. Input and Outputs testing is to plan which consist of the scope and the schedule, Data which consist of clean information created from a baseline and is sufficiently protected. The input of testing consist of the environment and different test cases. The output of testing is basically the test results, the log which we can read with errors and defective code and the test report which is a summary of the testing that has been completed.

Reference:

http://www.qatutorial.com/Software_Testing_Input_Process_Output; retrieved 23 April 2019

    • 5 years ago
    • 7
    Answer(1)

    Purchase the answer to view it

    blurred-text
    NOT RATED
    • attachment
      order_117810_302674.doc