System development approaches

Name
Institution affiliation
Table of Contents

1.0 INTRODUCTION................................................................................................................................3

1.1 Software development methodologies............................................................................................3

1.1.1 Waterfall method.........................................................................................................................3

1.1.2 Agile method................................................................................................................................4
1.1.3 Scrum...........................................................................................................................................4
1.1.4 Feature-Driven Development.........................................................................................................5
1.1.5 Chosen Development method........................................................................................................5
2.0 LITERATURE REVIEW..............................................................................................................................6

3.0 Reference..............................................................................................................................................8

2|Page
1.0 INTRODUCTION

System development approaches have been used in planning and executive software
development. Some different approaches and methodologies can be used for continuous
system development. The first includes a traditional approach, which is structured in system
development. The second approach is the object-oriented system development approach. The
traditional system of approach is based on design techniques and structural analysis. Both are
coordinated with different software development methodologies to facilitate system
development. The difference in software development methodologies includes their waterfall
methods, agile methodology Scrum and feature-driven development.
All the approaches and methodologies for software development are described below and are
furthermore elaborated for system development for Meet fresh easy. Software Engineering
includes software development, development processes that are divided into phases. The
different software development phases include; information and need assessment products,
product management. Product Management. All these phases are also known as the software
development lifecycle. There are different methodologies or approaches for software
development. They include agile development methodology DevOps deployment methodology,
rapid application development, and waterfall development methodology, develop the different
methods are used by different developers, depending on the output required, and the software
project development, being developed (Kevin, 2011). Every methodology has its advantages
and shortcomings, we are going to review the difference. Software methodology methodologies
and deeply analyze their effectiveness in the software development process. Different software
methodologies can be used in software development for meat fresh easily. Other methods are
described below application in software development for meats fresh easy has been explained
satisfactorily.
1.1 Software development methodologies
1.1.1 Waterfall method

Based on Meet fresh easy system requirements. The waterfall methodology can be used in
system development. Because of several software development processes. The software
development processes are described below. The waterfall method for instance is a traditional
and sequential software development process. The waterfall method often referred to as an old
school software is relevant in the project because it is outdated software, methods, and then
whether it is, however, effective in helping developers and us to understand the history and the
structure of waterfall (William & Cashwell, 2012). To appreciate the flexible and modern
software development methodology, the waterfall method was first used in 1970. It was a
prominent methodology that was used for several decades, based on its plan-driven approach.
The waterfall method required plenty of structures and documentation. Before the software
development process, the process was divided into stages and steps.

3|Page
The first stage required developers to understand the client's demands and the scope of work.
This stage was rigid and therefore it required the project developers to assess requirements
and the scope of work and analyzing software requirements. Furthermore, designing the
project, implementing its testing deploying, and maintaining after development. The middle
method was, however, not flexible in software development as the first phase was decided by
the customer and their developers (James & Jim 2015). Any changes or shortcomings that came
from the methods, would be addressed. At the end of the software development process. If
there were any errors made, this will require a full restart of the process.
1.1.2 Agile method
The agile method compared to the waterfall mellowed waterfall method is another method
that can be used in Meet fresh easy system development. Since the waterfall method is an old
system of system development, cannot be efficient. It is therefore necessary to assess the agile
methods and understand its efficiency in delivering the project. For instance, the agile software
development methodology will help system developers avoid the ever-growing frustrations
from the highly structured waterfall method, and was inflexible compared to other methods
(Qusay et al, 2016). The software development method is designed to accommodate the
changes that will facilitate the software development process to be a faster system
development for Meat fresh easy. Included customer collaboration with the developers to
ensure a faster software development process response to changes, was immediate instead of
a response, or the end of the project.
The agile method will focus on presenting a working software for Meet fresh easy and not
software documentation. The agile method will further equip developers with easy handling
variability and complexity in the software development project. The software development
team hunts shorts iterations of software development, which included duration and list of
variables that, what would you achieve in the software development process. Ideally, agile
development, methods, was more powerful because it focused on the team's efficiency and
strengths. Allowing internal feedback from different clients and departments, thereby making
software development, more efficient.
1.1.3 Scrum
Meet fresh easy systems can also be developed through scrum software development
methodology. Scrum is a software development approach that borrows philosophy and believes
from the agile software development methods. In these methods, developers on the project
team are expected to cover collaboratively daily. The approach uses an iterative approach in
which the team focuses on the front and center for an efficient, and experienced software
development process (Nancy et al, 2002). Developers in the methods are expected to be
disciplined, and they are furthermore divided into small teams to ensure high levels of success
and easy self-management and self-organization

Developers in teams will be expected to break down the tasks into smaller goals. In the
beginning, And through the project, thereby facilitating fixed iterations Sprint's and building
software's and showcasing the end product. Meetings play a vital role in this Scrum approach.

4|Page
Since there are daily meetings and demos on the project progress and the client also gives
feedback based on the demos that have been provided. This method often promotes faster
developments and changes for Complex methods. The method entirely depends on discipline
and structures for the efficient software development process.
1.1.4 Feature-Driven Development
Developing a system from scratch, developers and system development teams have the option
of developing a system from an existing system and through making changes on developments
from the existing system, application. The feature-driven development approach methodology
is based on an iterative and incremental approach in software development. This works by
improving the existing system through looking for a system better that meets the client’s
system requirement. The feature-driven development methodology is a software development
approach that is based on an iterative and incremental approach for software development
(Nancy et al, 2002). The method is derived from agile development methodology and is
considered an efficient way of software development, implementation, that method is,
however, similar to the waterfall. Since it is also viewed as an old software methodology
concept, they have met the FTD method that focuses on the goals of developing working
software. An approach is a cloud-centric approach, thereby making it suitable for small
development teams, which are working on a project.
In this case, there are several important features of the FTD method. That makes it's our
enabling method. First, the approach includes the project team will deliver the software, every
two weeks. The client should be able to see tangible Pro software development progress. There
are several steps of the method which includes tracking every step of designing and building
features for the software tracking progress tracking results and possible errors in the software
development process. There are efficient responses to change the FDD, for better attributes
and provide a better understanding of a Clancy requirement on the overall Model, from the
beginning of our software project, and reducing surprises during the software development
process.

1.1.5 Chosen Development method

Based on the assessment we can conclude the agile methodology is the most appropriate
software development methodology. The agile method is appropriate because it is reliable and
efficient in the project. Meet fresh easy requires a method that will facilitate the process and
ensure it is approachable and usable in the development process. There are different software
methods, however, the agile approach provides effective and efficient processes in software
development.

5|Page
 2.0 LITERATURE REVIEW

Different software development methodologies have been used, over the last several decade’s
software developers and system, analysts have been researching the most effective software
development approach. The first query. They have been dealing with is assessing whether the
system development methodologies are used for system development. This without literature
my methodology has been addressing two issues, which include the extent of the system as a
dodgy use under the nature of adopting the model or the model system methodology approach
to adapt and meet organizational needs.
There is a general assumption that an organization should use the methodology in all projects
to ensure the projects from the first phase to the last phase is done efficiently. Even though
there is limited research that indicates that surrounding conditions in an organization. Prevent
effective use of development practice practicalities from being used this literature study has
therefore examined organizations that have been adhering to methodology students and
determining organization in using and adopting system methodology approaches (Nancy et al,
2002). While they are executing a project. Additionally, a single system development
methodology, have been found to fit specific situations. However, there has been a challenge in
that one approach has not been able to meet the needs of our system in development. It is
therefore necessary to integrate different system development approaches and ensure they
can be used collaboratively in meeting a customer system development needs.
System analyst and software development have analyzed system development processes, and
thereby come up with a review on the most recent reliable system developments approach and
methodology. The first step to analyzing and finding enough to create methods includes
assessing the organizational needs and assessing the different approaches and the techniques
used in different approaches and analyzing the techniques used in different approaches
facilitates developers, and the clients in understanding the system needs, and evaluating the
different methods. They have by making a proper decision on the most appropriate method
System requirements and the different approaches should be collaborated to ensure the
system development lifecycle is effectively executed. Additionally, in stipulated timelines. For
instance, explained that methodology standards are necessary for determining the
organization's system development success. If an organization after assessing the methodology
is unable to adopt a specific methodology (Nancy et al, 2002). The methods can be
incorporated and Coppola collaborated to meet and facilitate system development previous
system developers and experts have been evaluating this issue and addressing the technique
used in analyzing the different system approaches and methodology. The approach is entirely
used in bits and pieces to ensure all methods are assessed effectively under the most
appropriate approach is using the system development lifecycle.
Several principles guide system development, a purchase system analyst, and developers have
gathered and listed several principles that facilitate developers and guide them in system
development. They include interaction and individual processes and tools, comprehensive

6|Page
documentation for customer collaboration, and contracts negotiation. Lastly responding to
change, have a plan aside from the four values that have been discussed above.
There are additional principles, such as the highest principle required in satisfying the customer.
From a lead to the continuous development of our software accommodating the changing
environment, and tackling the changes for customer’s competitive advantages. The other
principle is delivering working software frequently every week, and ensuring the review meets
the customer needs developers and clients need to work together throughout the project
(Nancy et al, 2002). There is a principle of coordination between the client and the software
developers. The other principle is developing projects around motivated individuals. This
principle is based on a working environment under support that is necessary for project
delivery effective and efficient methods are necessary for conveying information in the system
development plan and overseeing the plan throughout the project and ensuring. It is properly
executed, or working software is another principle because it is the measure of progress on the.
System analysts and developers have been explaining that the effective and efficient method of
communication that facilitates coordination between the client and developers are necessary
for ensuring organizational success. Other, the other principles include continuous attention to
the technical excellence of the design work and enhancing agility in the project (Nancy et al,
2002). Simplicity is another aspect. Under simplicity, developers are supposed to make sure the
project is simple, and the project processes are also simple for the client to understand the best
architects should ensure the design and requirements are easy for the client and the
development for the development team to understand. Software architects must, therefore,
ensure project simplicity, to facilitate an easy understanding of the project in all its phases. The
last principle is the regular interval reflection. The regular interval reflection includes reflecting
every face and task of the project and ensuring predictive requirements have been met.

7|Page
 3.0 Reference

Kevin, R. (2011). Systems Development Life Cycle (SDLC): High-impact Strategies - What You

Need to Know. Retrieved from:

https://books.google.co.ke/books/about/Systems_Development_Life_Cycle_SDLC_High.html?

id=Cb2BZwEACAAJ&redir_esc=y

William S. Turner, Cashwell, F. (2012). System Development Methodology: Data conversion and

system implementation. Retrieved from:

https://books.google.co.ke/books/about/System_Development_Methodology.html?

id=GotRAAAAMAAJ&redir_esc=y

James A, Jim H. (2015). Agile Software Development Ecosystems: Traditional software

development methods. Retrieved from:

https://books.google.co.ke/books/about/Agile_Software_Development_Ecosystems.html?

id=uE4FGFOHs2EC&redir_esc=y

Qusay F. Hassan, Atta ur Rehman Khan, Sajjad A. (2016). Internet of Things: Challenges,

Advances, and Applications. Retrieved from:

https://www.taylorfrancis.com/books/e/9781315155005/chapters/10.1201/9781315155005-7

Nancy L. Russo, Brian F, Erik S. (2002). Information Systems Development: Methods in Action.

Retrieved from:

https://books.google.co.ke/books/about/Information_Systems_Development.html?

id=5mUTNAAACAAJ&redir_esc=y

8|Page