Software Development Methodologies: Waterfall, Spiral, and Agile, Study Guides, Projects, Research of Computer science

assignment of software engineering

Typology: Study Guides, Projects, Research

2021/2022

Uploaded on 12/19/2023

ridma-ramanayaka
ridma-ramanayaka 🇱🇰

5 documents

1 / 13

Toggle sidebar

This page cannot be seen from the preview

Don't miss anything!

bg1
Java Institute for Advanced Technology
UNIT NAME :- Object Oriented Systems
Analysis And Design
UNIT ID :- H7DV 04
ASSIGNMENT ID :- H7DV 04/AS/01
NAME :- R.A.R.R.Ramanayaka.
SCN NO :- 187328276
NIC :- 977770963V
BRANCH :- Colombo
0 | P a g e
pf3
pf4
pf5
pf8
pf9
pfa
pfd

Partial preview of the text

Download Software Development Methodologies: Waterfall, Spiral, and Agile and more Study Guides, Projects, Research Computer science in PDF only on Docsity!

Java Institute for Advanced Technology

UNIT NAME :- Object Oriented Systems

Analysis And Design

UNIT ID :- H7DV 04

ASSIGNMENT ID :- H7DV 04/AS/

NAME :- R.A.R.R.Ramanayaka. SCN NO :- 187328276 NIC :- 977770963V BRANCH :- Colombo

Introduction of Methodologies

Methodologies improvement approaches are advanced as a method for enhancing the administration and control of the product improvement handle, organizing and disentangling. that procedure and institutionalizing the advancement procedure and item by indicating exercises to be done and systems to be utilised. It is frequently implicitly accepted that the utilization of a methodologies advancement procedure will enhance methodologies improvement efficiency and quality. Be that as it may, there is minimal observational proof to bolster this supposition. There is a developing assortment of writing which addresses the adequacy of formal advancement systems. Specifically, existing philosophies may not viable bolster the changing way of both the procedure and result of methodologies improvement. Most research to date has concentrated on the improvement of new philosophies and structures for the determination and examination of techniques, as opposed to on their assessment or use by and by. In spite of the fact that quantity of procedures has multiplied, they are to a great extent untested. It is not known whether or how they are utilised, how adequately they are utilised, or whether they are valuable. Much IS improvement examine verifiably expect that techniques are utilised and that they are valuable and viable. The reason for this exploration is to find how improvement procedures are being utilised as a part of associations. Particular issues tended to are what sorts of procedures are being utilised, what level of adherence is there to the particulars of the system, and how fulfilled are associations with their strategies.

Waterfall system is one of the well-known strategies that it streams down from a higher point and achieved the end without reverse psychology. Same as the genuine waterfall the reel or virtual model called as waterfall Development display too has similar highlights that it streams down from the beginning stage and covers down six stages known as stages. These six stages can't be rehashed once till is finished till the cycle pivots and gets its possibility for the second turn. This pivot is called as the lifecycle of the waterfall improvement display. The beneath chart demonstrates the means or periods of the waterfall Development display.

The benefit of waterfall Model is that it takes into account departmentalization

and administrative control. A timetable can be set with due dates for each phase of improvement and an item can continue through the advancement procedure like an auto in a carwash, and hypothetically, be conveyed on time. Advancement moves from an idea, through plan, usage, testing, establishment, investigating, and winds up at operation and upkeep. Each period of advancement continues in a strict request, with no covering or iterative advances.  This model is simple and easy to understand and use.  It is easy to manage due to the rigidity of the model – each phase has specific deliverables and a review process.  In this model phases are processed and completed one at a time. Phases do not overlap.  Waterfall model works well for smaller projects where requirements are very well understood. (istqbexamcertification, 2017)

The disadvantages of waterfall Model are that it doesn't take into consideration

much reflection or correction. Once an application is in the testing stage, it is exceptionally hard to backpedal and change something that was not well-thoroughly considered in the idea organize. Other options to the waterfall display incorporate joint application improvement (JAD), fast application advancement (RAD), sync and balance out, form and settle.

 Once an application is in the testing stage, it is very difficult to go back and change something that was not well-thought out in the concept stage.  No working software is produced until late during the life cycle.  High amounts of risk and uncertainty.  Not a good model for complex and object-oriented projects.  Poor model for long and ongoing projects.  Not suitable for the projects where requirements are at a moderate to high risk of changing.

Phases

Planning

Primarily knowing or distinguishing the issue or the necessity is an imperative undertaking that will be satisfied with no commitment. Once the issue or the prerequisite is characterized it simple for the following level of tests to be finished.

Analysis

The term examination unmistakably characterizes the parts covered here, the investigating some portion of the necessities accumulated are altogether broke down and subscripted in which the second period of the Waterfall Development Model is finished. The principle part here must be finished with no error as the up and coming stages will have the substance cleared or amended here.

Design

This is a vital stage as it must proceed onward before an execution stage brings down the task. The outlining process is directed here as an unpleasant content, reasonable System for an arranging.

Maintenance

Maintaining the made software is similarly imperative of making a software as troubleshoots and issues may emerge even in the wake of testing while at the same time working so to keep up and stay away from mistakes support is considerably more essential.

Spiral Methodology

The Spiral model is one of the primary approach utilized as a part of the improvement procedure of a product. Winding advancement demonstrate is likewise called as a Meta display as it accentuations alternate lifecycles. The Spiral model is made with a mix of the models and the waterfall advancement model's highlights. This system is primarily utilized for basic, substantial and costly undertakings as long-haul testing is made here, will have the capacity to

be managed by vast and costly firm tasks. A number of testing is made here before the execution as huge and basic activities overcome. The piece of testing is done different stages as to dodge places for blunders and questions. The Spiral model has four distinct stages for its recuperation and testing of the venture. These stages cause the work to be led effectively maintaining a strategic distance from issues when undertaking vast and basic activities. The premature birth of the undertaking should be possible as per the client's assessment if the hazard appears to be extraordinary to reclaim. Hazard factors, for the most part, take care of the expense of advancement, working or miscounts to be secured. These might be the explanation behind a disappointment of a venture.

The Spiral Development Model has four phases of testing as to make a value

programming according to the long-haul spending plan and prerequisites.  Planning  Risk Analyzing  Engineering  Evaluation

Phases

Planning

Here, the winding model uses the gauge winding for its assistance as to assemble the data or the essential prerequisite of the need. Every data ought to be all around arranged and sorted out according to the winding approach for improvement reason.

Risk Analyzing

Identifying the subtle elements accumulated is implied by breaking down here. Specifying the assembled little measure of data and reporting them in the wake of investigating them for the procedure of improvement.

Agile Methodology

Agile is one of the main method in the world of IT used by many developers for the success of the project. This methodology of Agile is also known as incremental model as the delivery of this project is done incremental, simply saying the project is divided in parts and developed. It is delivered to the end-users or the Customers in portions. Implementing new ideas even after a portion is completed can only be done in the methodology of Agile/Incremental Development Model as changes can be easily made without much cost. When taking the cost into consideration, it can be managed as the project creation and delivery is in short process and will be more useful for small scale developers. When compared to waterfall development model, the Agile Development or Incremental model has an advantage of interaction between the customers and developers. This interaction stands ahead in incremental model when compared to waterfall development model.

When starting a new project much idea is not needed as it can be corrected in future planning as per the creation of the project and even the developers can start the project with less amount of plan and cost. This is beneficent for both the developers and the investors as the project can be stopped at the earliest stage if it is recognized as unsuitable for development and implementation. This methodology of Agile is an alternative process to other traditional management of projects.

Advantages of AGIIE Model

 Generates working software quickly and early during the software life cycle.  More flexible less costly to change scope and requirement  Easier to test debug during a smaller iteration  Customer can respond to each built  Lower initial delivery cost  Easier to manage risk because risky pieces are identified and handle a during its iteration

Disadvantages of incremental AGIIE Model

 Needs good planning and design  Needs a clear and complete definition of the whole system before it can be broken down and built incrementally.

Rapid Application Development (RAD) Methodology