Give an example of a software system for which developing a prototype would result in saving a significant amount of development time. Explain why the prototype will save development time in this case.

“Prototyping” Please respond to the following:

· Give an example of a software system for which developing a prototype would result in saving a significant amount of development time. Explain why the prototype will save development time in this case.

· Give a different example of a software system for which developing a prototype would not result in saving a significant amount of development time. Explain why the prototype will not save development time.

LG’s post states the following:Top of Form

“Prototyping” Please respond to the following:

Give an example of a software system for which developing a prototype would result in saving a significant amount of development time. Explain why the prototype will save development time in this case.

The best example I could think about for a prototype of a software system is a cloud system. The reason I selected the cloud system based on some exposure in the development of a cloud solution for an organization I worked in. The conception of the cloud is not something brand new; however, the organization did not have a commercial cloud service available to its customers. The process started within the Innovation Team, where the team spent a short amount of time asking customers what type of business needs would cloud help them with. Those needs turn into a set of requirements, and then the team used that information to develop a prototype or shell of what the commercial cloud service would entail. Using agile and scrum, the team developed a minimal viable product (MVP) on what the solution would have to operate. The prototype was presented back to those customers to “test drive” and provide feedback where the prototype transform based on the feedback into a more robust solution. The team was able to recruit customers to help in building on the prototype base on their experience or interest. Now a time of five, with only two being a technical resource, ended up compromising on 10-12, allow for more investment, both funding and people, to expand the prototype into that robust system. Development work was able to be farmed out to more people so that resource-load would be more balanced between 10-12 versus 2. Experience levels also increased, allowing for more development work completed. As more interest came, the development process reduced due to the volume of developers. The development model was more advance as the development and user interaction was almost simultaneously since these users were now part of the overall team — the real-life experience help to shake out issues or errors before the final development was completed.

Overall,l prototyping is a great way to develop software. The ability to build, test,t and then rework real-time help with ensuring your product is viable early in the process. Having the minimal requirements and then build from there while the inclusion of the customers helps to achieve a final solutions that is able to be used sooner than later. I wast better than spending a lot of time collecting requirements only to learn that when you’re ready to build,d the requirements will have change. Prototyping is beneficial because your customers are part of the process,s and instead of waiting until the end, they are available to provide insight on the product development to help shape the product to meet their satisfaction. It included addressing functionality issues or errors early in the development process,s and it allows them to understand the functionality of how the system will support operations when implemented.

Give a different example of a software system for which developing a prototype would not result in saving a significant amount of development time. Explain why the prototype will not save development time.

The website for a new small business may not be a good fit with prototyping and saving development time. Small businesses have limited personnel,l, and those employees (users) usually are focused on running the business. Spending time to provide requirements,s and being part of a team to develop the site may not be available due to other work priorities. The business may not be able to invest the time and money to through the prototype process. If there are no users available, the prototyping process would be ineffective because the user is needed for requirements gathering or available to the development team to identify functionality errors.

References:

freeCodeCamp.org. (2017, September 26). To prototype or not to prototype: that is the question. Retrieved from https://www.freecodecamp.org/news/to-prototype-or-not-to-prototype-that-is-the-question-2f85c8cde2b/

Rouse, M. (2019, September 9). What is the Prototyping Model? Retrieved from https://searchcio.techtarget.com/definition/Prototyping-Model

JR’s post states the following:Top of Form

A prototype can help in a case where a hospital wanted to implement a new system. A prototype is a mock-up of the desired functionality of a system (Fairley, 2009). Creating a prototype can help in this case by showing which approaches are useful and which ones are a waste of time. The prototype can also help with finalizing requirements and showcasing which requirements aren’t necessary. A prototype in this case can give the hospital staff a real-life representation of what they would be using and be able to give their input accordingly.

I think in a situation where delivery of a product needs to be quick or funds are low, a prototype wouldn’t be beneficial. A prototype can be time consuming and sometimes costly. A prototype wouldn’t save time in this case because developers would have to create, develop, test and then wait to get feedback from users/involved parties.

Reference

Fairley, R. (2009). Managing and Leading Software Projects: Chichester, U. K.: WIiley

Place your order
(550 words)

Approximate price: $22

Calculate the price of your order

550 words
We'll send you the first draft for approval by September 11, 2018 at 10:52 AM
Total price:
$26
The price is based on these factors:
Academic level
Number of pages
Urgency
Basic features
  • Free title page and bibliography
  • Unlimited revisions
  • Plagiarism-free guarantee
  • Money-back guarantee
  • 24/7 support
On-demand options
  • Writer’s samples
  • Part-by-part delivery
  • Overnight delivery
  • Copies of used sources
  • Expert Proofreading
Paper format
  • 275 words per page
  • 12 pt Arial/Times New Roman
  • Double line spacing
  • Any citation style (APA, MLA, Chicago/Turabian, Harvard)

Our Guarantees

Money-back Guarantee

You have to be 100% sure of the quality of your product to give a money-back guarantee. This describes us perfectly. Make sure that this guarantee is totally transparent.

Read more

Zero-plagiarism Guarantee

Each paper is composed from scratch, according to your instructions. It is then checked by our plagiarism-detection software. There is no gap where plagiarism could squeeze in.

Read more

Free-revision Policy

Thanks to our free revisions, there is no way for you to be unsatisfied. We will work on your paper until you are completely happy with the result.

Read more

Privacy Policy

Your email is safe, as we store it according to international data protection rules. Your bank details are secure, as we use only reliable payment systems.

Read more

Fair-cooperation Guarantee

By sending us your money, you buy the service we provide. Check out our terms and conditions if you prefer business talks to be laid out in official language.

Read more
error: