hifsa shaukat for you

305 week 4 response needed:

*A 4-6 (paragraph) reponse is needed for each discussion(POST), may include reference:

Post:

Jillette Cook posted Nov 12, 2015 8:54 PM

I feel that one strength of using an Agile iterative development approach is that in developing and designing prototypes of the Health Information System, the developer can refine any prototypes to be of the best and highest quality before the final product is complete. I think that this is a great option, because it gives the developer a chance to get feedback from the users or potential users of the HIS and continuously redefine the product. One weakness of the design however, is that it can be costly due to the constant redesign of the HIS.

A strength of the incremental design approach is that the HIS can be implemented and in actual use early. Forwardly, the constant adding of system components in pieces, throughout the design and development process, creates a system that is built on functionality for the users.

I think that both developmental approaches are appropriate in different processes of HIS’s development and should be used in combined form to produce the best results.

 Cohn, M.  (Nov. 2014). Agile Needs to be Both Iterative and Incremental. Mountain Goat Software. Retrieved from https://www.mountaingoatsoftware.com/blog/agile-needs-to-be-both-iterative-and-incremental

· Post

Pil Kim posted Nov 10, 2015 9:28 AM

The iterative and incremental development is any combination of both iterative design or iterative method and incremental build model for software development. The basic idea is develop a system through repeated cycles (iterative) and in smaller portions at a time (incremental). 

The advantages of iterative model are only create a high – level design of the application before actually begin to build the product and define the design solution for the entire product. Later on we can design and built a skeleton version of that and evolved the design based on what had been bulit.

Disadvantages of iterative is each phase of iteration is rigid with no overlaps. 

The advantages of incremental model is generates working software quickly and early during the software life cycle.

The disadvantages of incremental model is needs good planning and design.

   Ref:

https://en.wikipedia.org/wiki/Iterative_and_incremental_development

http://istqbexamcertification.com/what-is-iterative-model-advantages-disadvantages-and-when-to-use-it/ http://istqbexamcertification.com/what-is-incremental-model-advantages-disadvantages-and-when-to-use-it/

· Post:

Regina Wofford posted Nov 12, 2015 7:44 PM

Agile provides rapid software development to clients. The repeated process of each cycle of agile including the testing produces the end product  that clients favor over methodologies like the waterfall methodology. When working with the agile iterative and incremental development approach, professionals should be aware of the strengths and weaknesses.  Having everything in an open forum is one of the strengths of working with agile. This means that all resources are made known up front  and everything gets communicated out in the open. This includes human resources as well as the dedication of those resources. It also means that the clients are included when discussing requirements definitions within the lifecycle. The discussions are open to all and the team works in a way that is united making communication between client and provider more effect. Clients are required to actively participate in the project, improving communication overall between the client and the provider. Clients are more in the loop and informed as to what goes on with the projects. Costs are strength of agile, because of the way regular installments of work is completed. With agile, costs are made known as it associates to the functionality before programming starts. Clients also have a choice to reduce costs by not preceding with portions of the project if they choose. (Dawson, 2015)

On the downside, there are weaknesses to agile.  Cost can be a weakness as well, because there is no fixed pricing with agile. This means there is no clarity on the total costs until the end of the project. Only estimates are provided throughout the process. There is a downfall to having the clients participate as part of the project requirement. Low availability by clients can slow down the process of getting things completed on time with projects. "Lack of participation will affect the software quality and therefore reflect on the software development company"(Dawson, 2015). Also, the jargon used during the meetings or throughout the process can be confusing or a bit too much on the technical side for the client's understanding. The process of learning for clients requires time because it goes beyond the scope of what the client's skillsets are. Lastly, when it comes to maintenance and projects that are small, another disadvantage to using agile is that it is not always the best approach to take (Dawson, 2015).

Reference:

Dawson, C. (2015, January 22). Agile Methodology - Advantages and Disadvantages.

     Retrieved November   13, 2015,  http://www.nearshoreamericas.com/agile-methodology-advantages disadvantages/