Analysis of Requirements

Please the following to paragraphs and answer replies. They should be thoughtful and supportive with references.

1.Prototyping is in itself a self-sufficient mechanism to collect system requirements and can take two forms, evolutionary and throwaway. The main benefit of prototyping is the development of an information system that more closely fits the needs of the organization (Huston, T.H. & D’Ouville, E. L., 1988). A prototype is a basic working model, mock-up or a simple simulation of the product which leads us to create a minimal viable product to final product and variations (Entrepreneur, 2018).

While, evolutionary prototypes are generally turned into a full working production system at some point in time, the throwaway prototypes, as the name suggests, are discarded once they meet the initial purpose they were created for. Agreed that there may be some cases where throwaway prototypes dont even serve the purpose for which they were created. However, after having spent so much resources and effort on these prototypes, which met initial purpose, is it justifiable to discard them? If so, under what conditions it makes business sense to discard these prototypes?

References:

Willis, T. H., Huston, C. R., & D’Ouville, E. L. (1988). Project manager’s responsibilities in a prototyping systems analysis and design environment. Project Management Journal, 19(1), 5660. Retrieved on January 26, 2020 from https://www.pmi.org/learning/library/prototyping-systems-analysis-design-environment-5461

Singaram, Muthu & Jain, Prathistha (2018, February 08). Types of prototype and their usage. Entrepreneur. Retrieved on January 26, 2020 from https://www.entrepreneur.com/article/308724

2. My post this week will not be too verbose as I have had a perplexing question (that I have some opinions on, but I’d like the thoughts of the class) that has been a theme for these discussion posts throughout this course.  After reading both chapters this week I appreciate the needs for systems requirements and data flow diagrams.  I understand the benefits of both; The outcome of a detailed requirements analysis is that the organization reaps the benefits of selecting best-fit software (Doig, 2015).  However, the thought that has captured my curiosity is what are the costs to an organization for poor systems requirements, and/or data flow diagrams?  For example; An unclear product spec can add millions of dollars in manufacturing costs (Redman, 2013).  Aside from monetary impacts, what other types of impacts does shoddy work do to an organization?

References

Doig, C. (2015, May 18). The benefits of doing a detailed enterprise software requirements analysis. Retrieved from CIO: https://www.cio.com/article/2923225/the-benefits-of-doing-a-detailed-requirements-analysis-before-selecting-enterprise-software.html

Redman, T. C. (2013, December). Datas Credibility Problem. Retrieved from Harvard Business Review: https://hbr.org/2013/12/datas-credibility-problem

 

You can place an order similar to this with us. You are assured of an authentic custom paper delivered within the given deadline besides our 24/7 customer support all through.

 

[order_calculator]