Software Development Life Cycle (SDLC)

-
Software Development Life Cycle is a step by step structure in software engineering to develop the software product. The aim of an SDLC process is helping to develop a software with cost- efficient, effective and high quality.

There are six phases in SDLC.



Feasibility – This is not including to SDLC but this is very important to develop a project. After defining the problem, we must check the feasibility. In this, we check whether the system is feasibility to technical, operational and economical.

1.Requirement gathering and analysis

In this phase, we collect all the possible requirements for developing the project and documented in a requirement specification doc.

2.System Design

In this phase, we study the requirement specification doc and design the system. This helps us to define overall system architecture.

3.Implementation

In this phase, we code the software as small units. Each unit is developed and tested in this.

4.Integration a testing

In this phase, we test the software using the system.

5.Development of System

In this phase, we deploy the software in the customer environment or released into the market.

6.Maintenance

In this phase, we fix issues that come up in the customer environment and develop better versions and publish them.





     




Comments

Post a Comment

Popular posts from this blog

C# Analog Clock

-
Image
Today we are going to design analog clock as the first post in 2017. We can add digital clock to C# form very easily using “DateTimePicker”. Analog Clock cannot add like that. We must design it for our form. Let’s design an analog clock. First of all add a new form (Analog Clock) to your application. Next add a “pictureBox” and a “timer” to the form. As the next step write the following code. using System; using System.Collections.Generic; using System.ComponentModel; using System.Data; using System.Drawing; using System.Linq; using System.Text; using System.Windows.Forms; using System.Drawing.Printing; using System.Globalization; using System.IO; namespace Clock {     public partial class Form1 : Form     {         Bitmap bmp;         Graphics g;         Timer t = new Timer ();      int WIDTH = 100, HEIGHT = 100, secHAND = 50, minHAND = 50, hrHAND =  25;       int cx, cy;         public Form1()  
Read more

Basic Prolog (List)

-
1.       How to find last element from a list Code: lastelement([A],A). lastelement([_|A],B):- lastelement(A,B). Output: lastelement([a,b,c,d],X). X = d . 2.       How to find n th element of a list Code: element_at(X,[X|_],1). element_at(X,[_|T],Y):- element_at(X,T,Y1), Y is Y1+1. Output: element_at(X,[a,b,c,d],2). X = b . 3.       How to check whether the element available or not Code: mem([X|_],X). mem([_|T],X):- mem(T,X). Output: mem([a,b,c,d],a). true .  4.       How to print all members Code: mem([X|_],X). mem([_|T],X):- mem(T,X). Output: mem([a,b,c,d],X). X = a ; X = b ; X = c ; X = d ; false. There is a “Prolog” keyword to find member of list. We can use it directly. 4.1. ?- member(X,[a,b,c,d]). X = a ; X = b ; X = c ; X = d. 4.2. ?- member(b,[a,b,c,d]). True 5.       How to find the length of the list Code: list_length([],0). list_length([_|T],X):- list_length(T,X1),X is X1+1. O
Read more

SOLID Principles

-
Image
In Object-Oriented Programming (OOP) Concept, SOLID principles are the acronym for five Object-Oriented Design (OOD) principles. These SOLID principles are used to improve the understand-ability, flexibility and maintainability of the code.   S.O.L.I.D. Stands For? 1.      S - Single-responsibility principle 2.      O - Open-closed principle 3.      L - Liskov substitution principle 4.      I - Interface segregation principle 5.      D - Dependency Inversion Principle   Let’s see what is the exact meaning of each principle using an example. Ex: There is an online store. A registered customer can place an order and purchase them using the card or make payment when delivering the order. Let’s move to the principles again.   1.      Single-Responsibility Principle The common definition of this principle is “A class should have one and only one reason to change, meaning that a class should have only one job.” When we consider the above online store, there is a class
Read more