Reference no: EM131887120

Please don't pass/outsource my work for others to do, be original, and cite anyone you quote or paraphase please. Label your sections also and which student post you reply to (the response should sound like you are responding to that specific person or post).

Part 1:

Perfection vs. Deadlines

Software typically has errors. Some are known about and others (called latent defects) have not been discovered. Please respond to the following in not more than 250 words:

What factors might help your team decide when to put a new system or release into production?

Demonstrate your thinking in a specific example.

NOTES: " If you work longer work on a software product, it will probably get better. On the other hand, there are big benefits to getting the product into the market quickly.

So, how do you decide when the product is good enough, or when it needs more work before release? I'd like you to be as specific as you can get; we can debate whether your metrics are workable. "

Part 2:

In a separate post, follow up on one of your fellow students in substantive post of up to 150 words that further the discussion. For example, you may support or politely challenge a post with your own insights or experience, make a suggestion, or ask probing follow-up questions. (choose one)

a. A product is good enough when the documentation for the product is complete. The system needs to be tested and presented to management.

When the system is ready to go, a separate operational test performed in a different environment, users trained, data conversion or system changeover performed, a post-evaluation performed, and a final report is sent to management.

b. When putting new system into production testing requires testing of all modules to make sure they all work together. Next make sure to use personnel to whom is going to be using the system and real numbers not just made up ones for accuracy.

The down side to testing is you cannot test all bugs out of a system, there has to be a time to go live and live with the results. I have no experience with this but have friends that do this for a living and after talking to them the y said the same thing. Make sure to get consistent results in testing then go live and fix bugs on the fly.

c. A factor that might help a development team to decide when to release a new system into production is when the development team has met the requirements that the software needs before releasing the software. Software requirements are different with each software development.

Requirements: make sure that the coding, programing is tested and working properly, make sure that there is not a need for immediate improving of the software, having more than one person test out the software and complete a use case or go live test to fix any bugs or errors that make arise while operating the software.

After completing the use case or go live of the system, the organization or owner of the software will determine when to implement or release the the new software into production.

If the software that is being developed is for a consumer, the owner of the software might want to monitor other software competitors so he/she can known when to put out the new software for the consumers. As the professor stated, if you work on a software product for a while; it will get better. But you don't want to wait to long to get the product on the market.

Attachment:- Chapter- 11 Managing system.rar