Blog #5: First Post of 2019: Software Development Methodologies

 · 3 mins read

First Post of 2019


A new year, a new software technology out of nowhere to learn! What a day to start a new year by learning what new tech is going on now and into the future!! especially in the industry where a lot of technology is being implemented each and every day regardless what kind of background you or your peers come from. In my department, software development plays a significant role in today’s face paced environment especially when methodologies are chosen by the higher-ups from what method is best use for the company. In this blog, I will explain what today’s startups and enterprise companies use each day to catch up in the game for software development.

What are Software Development Methodologies and how many kind are there in the industry/market?


In a professional development, many developers ponder what kind of operation the team should approach in order to meet the client’s expectations and needs for a particular software they desired. Lets take Apple for example! Apple has a lot of teams that operate the ecosystem of the iPhone and Mac operating system such as Mojave OS(10.14), the successor after High Sierra OS(10.13). Apple use the MVC to make an app suited for them and their customers. In this case, the project is followed by the Agile development methodology with Behavior Driven Development. What is Agile you say? Sounds like Fast? Not just fast! Agile requires a significant amount of collaborative effort to organize to promote adaptive planning, voluntary development, and continual improvement on the project given by the client. Basically, it is the methodology to adapt to change and to deal with uncertainty yet uniqueness of a particular framework by collaborative teamwork.


What exactly is Agile Methodology?


Agile methods attempt to minimize risk (such as bugs, cost overruns, and changing requirements) by implementing new functionality and developing the software that are mini-increments of the new functionality. The benefit of multiple iterations is to improve efficiency by finding and fixing defects and expectation mismatches early on. The problems with this kind of methodology is the ongoing real-time communication with the client if he or she needed for a improvement on the application. It is important to make haste with time and investment on management in order to make a documentation on the software’s features. Agile can be a hassle for developers, management teams, and executive organizations who are accustomed to the waterfall method, thus may have difficulty in adjusting to agile. So a hybrid approach often works well for them to deliver the software on time and sometimes later debugging if it doesn’t work out for the client afterwards.

What is the Waterfall Methodology?


The waterfall method is considered the traditional software development method. It is considered a rigid linear model that is made of sequential phases(requirements, design, implementation, verification, and maintenance). Each phase has to be 100% complete before the next phase, otherwise there is no process for going back to modify the project. The linear nature of this method helps us understand the process better and how we can manage our project comprehensively. Using the Waterfall method is beneficial with projects with clear objectives and stable requirements. It can also apply with inexperienced project managers and developers who are accustomed to composition changes frequently. However, it can be often slow and cost inefficiency due to rigid structure and drawbacks to migrate to another software development methodology if the project fails within this method.

What is the Rapid Application Development Methodology?

Video on Software Development Life Cycle (SDLC)