Software Development Life Cycle

-

Different Phases Of Software Development Life Cycle






THERE ARE TOTAL 6 PHASE IN (SDLC) MODEL :


  1. RGA(Requirement Gathering Analysis):  This process shows the function of the software that needs to provide for gaining the client’s needs. This phase is essential for developing software.
The requirement specifies the need of the client.

BA (Business Analyst): The BA creates BRS document (Business Requirement 
Specification) will be mentioning functional requirements.

SA (Senior Analyst): The SA creates an SRS document (Software Requirement Specification) that will be mentioning the functional requirement and non-functional requirement.

2. DESIGN: The design reference for product architects to come out with the best architecture for the product to be developed. In this, they will prepare the document that is detailed. 
Design document (DDD).





3. CODING: The goal of the coding phase is to translate the design of the system into code in a given programming language. The aim of this phase is to implement the design in the best possible manner. A developer has to follow the coding guidelines defined by their organization. 

4.TESTING: Tester will do testing the software. In the testing phase, the software test life cycle (STLC) is being followed. During the testing phase, developers find out whether their code and programming work according to customer requirements. 

There are two types of Testing: 

1. Black-box Testing
2. White-box Testing 

5. Installation/deployment: This phase is initiated after the system has been tasted. 
The goal of the installation phase is to place the application in a live environment. 

6. Maintenance: This process where the care is taken for the developed product is known as maintenance. In this phase the software in under warranty phase if any requirement comes or any changes or any defect it will be resolved in maintenance.

Comments

Post a Comment

Popular posts from this blog

Implicit and Explicit requirements

-
Implicit and Explicit requirements Explicit Requirements​ :    ● The Things business analyst Wrote Down.  ● These are the requirements explicitly stated or mentioned by the customer.  ● Explicit requirements are most commonly found in documents communicated by stakeholders to the development team.   ● This is the simplest type and the easiest to test.  ● The development team might take the form of an elaborate design specification, a set of acceptance criteria.  ● Explicit requirements in the form of claims that is, communications to end-users about things the software can do.   Implicit Requirements​ :  ● The Things client Will Expect  ● These are the requirements that are not explicitly stated by the customer, but implied or derived from the requirement stated by the customer.  ● These are all the things that users are going to expect that were not captured explicitly.  ● Examples include performance...
Read more

Software Configuration Management (SCM)

-
Software configuration management (SC) is a software engineering discipline consisting of standard processes and techniques often used by organizations to manage the changes introduced to its software products. SC helps in identifying individual elements and configurations tracing changes and version selection control and baselining.   SC is also known as software control management. SC aims to control changes introduced to large complex software systems through reliable version selection and version control.   Software Configuration Management does​ ​   ● Introduction to Software Configuration management and Configuration management for software Testers.  ● Software configuration management (SC) is the discipline for systematically controlling the changes that tae place during Software evelopment.  ● Software development software consists of a collection of items (such as program documents etc..) that can easily be changed. uring software...
Read more

Identified for Configuration Management

-
The term configuration item (CI) refers to the fundamental structural unit of a configuration management system. Examples of CIs include individual requirements documents software models and plans. The configuration-management system oversees the life of the CIs through a combination of processes and tools by implementing and enabling the fundamental elements of identification change management status accounting and audits. This system aims to avoid the introduction of errors related to lack of testing as well as incompatibilities with other CIs.     Configuration Management Activities ​:     1. ​Configuration Item Identification ​:  ​In this phase, the item will be identified for making changes.  Example: ​Requirement document design document source code etc    2. ​Change Control ​: ​ Controlling the release and changes of the product throw out the software life cycle here CCB team will approve or disapprove changes prioritize the change...
Read more