PART A
Please I need good and quality answers. Also please I want good citation and good references. I want it in APA format.
Questions:
This week we're talking about Software Development Methodology. I would recommend that you pick one of these questions (that has not been covered already) and focus on it:
Software Development Methodologies
Question:
What is the relationship between business process modeling, and software development (or systems procurement)?
PART B
I need a reply/response to these discussion board answers. Just read the discussion board answers, and respond to the information you read by also adding your own point of information about each topic itself to each discussion board answers not about how to correct the person answers by saying he or she needs to add more information or saying you agreed without stating why. Just three to five Lines response each. Please I need good and quality response to these discussion board answers
Frances Mcmeans
The "Waterfall" method has a long history - what has caused its "fall" from general acceptance? What is the "Waterfall" method and how does it compare with the newer "Agile" development methods that are now in widespread use?
Two very different methods of software development are the Waterfall and Agile models. The Waterfall method is considered the traditional approach to software design. It consists of the completion of 8 steps (conception, initiation, analysis, design, construction, testing, implementation, and maintenance) in sequential order. Once a step is completed, developers cannot return to previous steps to fix any issues they may have encountered. The Agile method, on the other hand, allows developers to work on small parts of the design process in time increments known as sprints. Sprints can be days, weeks, or months. At the end of a sprint, developers are able to run tests and correct any issues which they may come across.
The Waterfall method has "fallen" from general acceptance because does not allow any changes to be made as a software is being developed. Therefore, if the end product does not work, developers have to completely start over. This could be very costly for the client and time consuming for developers. However, the Agile method allows developers to make changes throughout the development process. So, if at the end of a sprint, a client is not satisfied with a certain feature, developers are able to delete or alter the feature before continuing on to the next sprint. The Agile method makes it easier for developers to make a product which the client will be satisfied with upon completion.
Lamin Sesay
What has changed in the software industry that may have rendered the "Waterfall" model obsolete? Or put another way, what has changed to render the "Agile" development methods more practical? But why have many I.T. departments resisted the adoption of "Agile" development methods?
Water fall model is being more effective for software industry, Because this model have accurate plan considered as more powerful it provides appropriate requirement, needs, resources, alternate with cost effectiveness of the particulars projects.
Once this model has developed and put into practical, it will have accurate design as drew in the plan and also giving safety for the developer. Though It is not flexible and required special education as well as not at all handled by all developers.
Agile development has considered as more flexible does not need any special education requirements,developers works the project at two stage, first stage they made a projects in short level and sent for the client approval, once they received approval, developers will develop the projects into full shape, if the client is not approved they remodel the project and sent back to the client for approval.
This method gives more important for client needs, so it is considered as client oriented method. If many developers working in this model it never shows variation to the many developers.
Now a day current market environment is emerging with tough competition so developers needs flexible model as well as gaining a client satisfaction considered as must . So, I.T. departments resisted the adoption of "Agile" development methods
Nikole Ferguson
The "Waterfall" method has a long history -- what has caused its "fall" from general acceptance? What is the "Waterfall" method and how does it compare with the newer "Agile" development methods that are now in widespread use?
Agile and Waterfall are two distinct methods of software development.
The Waterfall model can essentially be described as a linear model of software design. Development flows sequentially from start point to end point, with several different stages: Conception, Initiation, Analysis, Design, Construction, Testing, Implementation, and Maintenance. The emphasis of Waterfall is the project plan and therefore before beginning any kind of development there needs to be a clear plan and a clear vision in order. Because the Waterfall method requires upfront, extensive planning, you can launch software fairly quickly. You can also estimate timetables and budgets more accurately, which definitely tends to please clients.
The Agile method proposes an incremental and iterative approach to software design. It was essentially developed in response to the limitations of Waterfall, as a way to give designers more freedom. The design process is broken into individual models that designers work on. There is no pre-determined course of action or plan with the Agile method. Rather, designers are free to respond to changes in requirements as they arise and make changes as the project progresses. Agile is a pretty new player to the development game. However, it has made substantial gains in use and popularity in the last couple of years. Agile offers an incredibly flexible design model, promoting adaptive planning and evolutionary development. Agile might be described as free-form software design. Software developers work on small modules at a time. Customer feedback occurs simultaneously with development, as does software testing. Retrieved from https://blog.udemy.com/agile-vs-waterfall/
The Waterfall method is incredibly rigid and inflexible. Altering the project design at any stage in the project can be a total nightmare and once a stage has been completed, it is nearly impossible to make changes to it. So, if you're planning to use Waterfall, you will need to gather all of the requirements upfront. In addition, the problem with the Waterfall method is that feedback and testing are deferred until very late into the project. So if there is a problem, it is very difficult to respond to it, requiring a substantial amount of time, effort, and sometimes money.
Elias Vargas
What is the relationship between business process modeling, and software development (or systems procurement)?
Business Process Modeling:
Is a method for improving organizational efficiency and quality. Its beginnings were in capital/profit-led business, but the methodology is applicable to any organized activity.
Software development:
Is the process of developing software through successive phases in an orderly way. This process includes not only the actual writing of code but also the preparation of requirements and objectives, the design of what is to be coded, and confirmation that what is developed has met objectives.
Before systems development methods came into being, the development of new systems or products was often carried out by using the experience and intuition of management and technical personnel. However, the complexity of modern systems and computer products long ago made the need clear for some kind of orderly development process.
Systems development life cycle models include:
• Rapid application development (RAD): This model is based on the concept that better products can be developed more quickly by: using workshops or focus groups to gather system requirements; prototyping and reiterative testing of designs; rigid adherence to schedule; and less formality of team communications such as reviews.
• Joint application development (JAD): This model involves the client or end user in the design and development of an application, through a series of collaborative workshops called JAD sessions.
• The prototyping model: In this model, a prototype (an early approximation of a final system or product) is built, tested, and then reworked as necessary until an acceptable prototype is finally achieved from which the complete system or product can now be developed.
• Synchronize-and-stabilize: This model involves teams working in parallel on individual application modules, frequently synchronizing their code with that of other teams and stabilizing code frequently throughout the development process.
• The spiral model: This model of development combines the features of the prototyping model and the waterfall model. The spiral model is favored for large, expensive, and complicated projects.
Business process modeling is about building a visual scheme of a process which makes it easier for the human eye to look at, find weaknesses and, strategically thinking, improve the processes and optimize them. . IT Procurement Software the process cannot be managed without using strategic procurement and sourcing software solutions. Such software provides a set of planning tools to use the model, organize the sub-processes, related tasks and work flows. The software is what you use after you complete modeling, you hit the ‘execute' button (or whatever button the software has), and the solution starts distributing tasks to your team according to the business model you've put into the solution.