what is SDLC?

By -
SDLC ( Software Development Life Cycle ):

         SDLC represents the overall system development process by which a software system is defined and realized.It is used to  develop the software systematically. It is made up of a series of phases.

1) Information Gathering
2) Requirement Analysis
3) Design
4) Coding
5) Testing
6) Implementation & Maintenance.

1) Information Gathering :
            In this phase; information is gathered from the customer , if some information are missing then we need to go to customer and take the required information. Mainly this is done by the Business  Analyst as they are the one who are completely involved in Software Development life Cycle.

The Document Prepared during this phase is : Business Requirement Specification (BRS)or Customer Required Specification( CRS) Or User Requirement Specification(URS).

2)  Requirement Analysis :
            The Features and the functions that need to be put in the project are determined.

3) Design :
            The actually flow of the project is done  here.Deciding upto logical functionality ,ER diagram , Data Flow etc are made. These activities would be executed by team lead , technical Specialist and depending upon the work appropriate decisions are made.

Document prepared during this phase are HLD(high-level-design), LLD(low-level-design)
HLD : Defines the overall Hierarchy of the function. Example : Login into Net Banking. From the root level to  the least level is defines in HLD.
LLD: Internal logic of the project is defined. Focuses on  their internal functionality of the program. Each and every  module logic is defined.

4) Coding :
            Based on the design document , small-small modules are prepared . This phase is done by the developer

5) Testing :
           Actual system testing take place here. This phase is done by Test Engineers

6) Implementing & Maintenance :
           Deployment of the final product in the customer environment. Through Maintenance, the product is maintained or changed to satisfy the customer

Comments

Post a Comment

Popular posts from this blog

what is Modified Waterfall Model?

By -
Image
In response to the perceived problems with the "pure" waterfall model, many modified waterfall models have been introduced. These models may address some or all of the criticisms of the "pure"  waterfall model. In Water fall method , there is no VALIDATION OR VERIFICATION between the phases , so the customer will finally get unsatisfied product. This Modified Waterfall Model Involves VALIDATION or VERIFICATION between the phases , so any deviations can be corrected immediately , providing the customer satisfaction, so this is preferred.
Read more

what is Prototype Model?

By -
Image
The goal of prototyping based development is to counter the first two limitations of the waterfall model. This prototype is developed based on the currently known requirements. Development of the prototype obviously undergoes design, coding and testing. But each of these phases is not done very formally or thoroughly. By using this prototype, the client can get an "actual feel" of the system. Advantages It could serve as the first system. Prototyping is an attractive idea for complicated and large systems for which there is no manual  process or existing system to help determining the requirements. The customer doesn’t need to wait long as in the Linear Model. Feedback from customers are received periodically and the changes don’t come as a last minute surprise. Users are actively involved in the development It provides a better system to users, as users have natural tendency to change their mind in specifying requirements and this method of developing systems s
Read more

What is User Documentation Testing

By -
User Documentation  covers all the manuals, user guides, installation guides, setup guides, read me files,software release notes, and online help that are provided along with the software to help the end user to understand the software system. User Documentation Testing should have two objectives:- To check if what is  stated in the document is available in the software To check if what is there in the product is explained correctly in the document This testing is plays a vital role as the users will refer this document when they start using the software at their location.a badly written document can put off a user and bias them against the product even the product offers rich functionality. Defects found in the user documentation need to be tracked to closure like any regular software defect.Because these documents are the first interactions the users have with the product. A good User Documentation  aids in reducing customer support calls.The effort and money spend on this effort
Read more