Processes involved in Software development

I will be talking on the processes involved in software development but before i proceed, what do you understand by the phrase "processes in software development"?

it is the steps that a developer takes to bring an idea from conception to reality
algorithm or flow chat needed to adopt before developing a software
it's the skeletal output of the program

all are right depending to your perspectives, but i will say that software development process is a set of steps that a software program goes through when being developed just like it pointed out above.
from the point we get the idea to the time we start thinking of how to bring it to reality. then to the point cit finally comes to reality.
it takes differentr processes to finally get our idea into reality and we would be getting to know those process in this tutorial.
Stay put
you will all agree with me that we have reach a situation where one has control over virtually everything at the tip of the fingers. Technology has developed beyond imagination, Thanks to all the software development industry
Software development is gradually becoming a serious necessity and virtually every process now is getting automated, and all this automation is with the help of software that run at the background.
there era different approaches to software development. We have different methodologisies but the main one i will try to explain is the waterfall methodology
Its considered the traditional method of explaining the software development process in software engineering, waterfall model happens to clarify the process into a linear flow with a specified sequence to let the user understand that further level is made progressive on completion of the previous one.
The waterfall model is a sequential (non-iterative) design process, used in software development process, in which progress is seen as flowing steadily downwards (like a waterfall) through the phase of conception, initiation, analysis, design, construction, testing, production/implementation and maintenance
The waterfall development model originated from the manufacturing and construction industries: highly structured physical environment inwhich after the fact changes are phohibitively costly, if not impossible. Because it was created in a time when no formal software development methodologies existed, this hardware-oriented model was simply adapted for software development.
The processes in this model are:

Requirements for the development of the software
design implementation
testing/verification
maintainance

These are the basic steps in the waterfall model, let talk brieflly on this steps starting from the first step

The requirements are the things needed to be able to implement the software. what and what is needed to be able to fully implement what is wanted in the software and get it working, during this prtocess the design is also made, with that one can find out everything that is needed for it to be achieved
the second step is design implementation, this is where you decide the kind of design you want to implement on your project

after this process the next is testing of what has been done so far to be sure that it works as planned, and documentating things about the software to enable anyone use it without much issues

then after this comes the maintenance process

The waterfall model provides a structured approach; the model itself progresses linearly through discrete, easily understandable and explainable phases and thus is easy to understand; it also provides easily identifiable milestones in the development process. It is perhaps for this reason that the waterfall model is used as a beginning example of a development model in many software engineering texts and courses.
It is argued that the waterfall model can be suited to projects where requirements and scope are fixed, the product itself is firm and stable, and the technology is clearly understood.
The problem with this methodology is that Clients may not know exactly what their requirements are before they see the working software and so change their requirements, leading to redesign, redevelopment, and retesting, and increased costs, But after all this long grammar about methodology one may not really grab the essential thing which one should not miss for any reason during the software development process and that is the UX..(User experience)

Ux is everything one needs to know, think about and do to make sure that you are launching the right product for the right people

The fundamentals of UX

Focus on the user of the software: Design for them, not for yourself . understand their needs motivations and constraints . Put them at the center of your decision making. Reward their engagement and earn their trust
Do your research : Understand your product area and what the strength and weaknesses of those possibly in competition are, and Validate your assumptions with friends relatives and likely users. Adapt your plans based on what u learn: adapt in the sense that as you plan on how to build the software. do that having in mind things u found out through the research you did ur relative probably gave you a hint on how it would be better if u do it. another friend may have given u his own view too. so as make your plans try to adapt to what you got from your research
strive for simplicity: Make sure your proposition and benefits are clear and can be championed by your users, priotize what is best for your users and work hard to remove roadblocks from their path and make it as simple as u can make it . in a way that anyone can easily use it without much problem.
solve real problems: look around you and think about how application of the technology could change things for the better, then the iterative process is also there where you build test. get feedback from people and improve on it.
Thanks for following all through, I believe you'v learnt something new in this post, please do not forget to use our comment box to ask any questions.
Dont forget to Get your Free App it's 100% free