SDLC (Software Development life cycle) :-
- SDLC is process which consist of set of particular stages start from requirement gathering to the maintenance of product.
- SDLC has two types :-
Stages in SDLC:-
1. Information Gathering:
- Business Analyst (BA) is responsible for information gathering.
- Information gathering is nothing but collecting information requirements from customer.
- Business Analyst will collect all requirements and creates one document called as BRS (Business Requirement Specification).
- BRS is nothing but bridge between customer to Developer and Testers.
- Domain of Project get identified.
- So, for BRS document responsible person is Business Analyst.
2. Analysis:
- Here also is Business Analyst involve.
- Analysis is the detail representation in the form of documents.
- It include Main Module, Sub Module, Functionality, Desire input, Desire output, Relationship between Module.
- Here Business Analyst will creates SRS (Software requirement specification) document with help of BRS.
- Business Analyst will prepare SRS document after BRS document.
- In SRS document all requirements are mention in detail level.
- SRS is also called as FRS (Functional Requirement Specification)
- SRS document includes:
- Functional Flow Diagram
- Functional Requirement
- Use Cases
- Snap Shots
- Functional Flow Diagram:
- FDD is nothing but flow of the application or module.
- This flow shows relationship between the task and pages.
- It will help us to show the proper sequence of the task.
- Relationship is nothing but dependency of functionality.
- ex.
- Functional Requirement:
- Functional Requirement is nothing but attributes which are required to complete the specific function.
- Now we have signup page or functionality than
- for sign up page requirement are like
- First name,
- Last name,
- Email Id,
- Phone number,
- Password, etc.
- So, suppose we have first name in sign up page.
- For First name requirements are like:
- Name should be in Character.
- Name doesn’t contain any number.
- It should not accept any blank spaces.
- It should not have any special symbols.
- Use Cases :
- Use case are nothing but functionality in terms of input and output (operation).
- Snap shot :
- Snap Shot are nothing but visualization of functionalities before development of product.
- Snap shots are created by Business Analyst.
- Business Analyst can create snap shots by using different tools.
- EX: IRISE
- Snapshots gives idea to developer that how to software support to look like.
3. Design :-
- Design is having 2 types :-
- High Level Design:
- High Leve Design contain design of working of main module.
- It include relation and dependency (flow) of main module.
- It includes what and how any module works.
- High Level Design is created by DESIGN ARCHITECTURE.
- Low Level Design:
- Low Level Design include static logic of every sub modules. (Develop functionality of module)
- it is design for working of sub modules.
- In sign up page is main module and name, email, password, number are the sub module.
- Proper working means number field should accept any numbers.
- Low Level Design is created by FRONT END DEVELOPER
4. Coding :
- Coding is nothing but programming.
- If developer writes a single line than also it’s a code.
- Multiple line is called as Program.
- Collection of program or set of program written by developer creates the software
- There are 2 types of Developer.
NOTE: The Developer /person who works as Front End Developer as well as Back End Developer is called as FULL STACK DEVELOPER.
5. Testing :
- Testing is the process of checking completeness and correctness of software.
- There are 3 Types of Testing.
- White Box Testing :-
- It is done by Developer (Coder).
- It is also called as Unit Testing / Code Level Testing / Clare Box Testing / Glass Box Testing / Transparent Testing .
- Whenever DEVELOPER complete his code than he will cross verify or compile (run) the code, at that time of compilation if any bug found than developer have to solve it.
- Developer can not send the code to the tester without White Box Testing.
- Developer will test only positive scenarios.
- The purpose of White Box Testing is to check correctness and completeness of code.
- Black Box Testing :
- Black Box Testing is also called as System Testing or Function Testing.
- This Testing is done by Tester.
- Overall functionality of the application get checked in this testing.
- Tester will check Internal functionality and External functionality of application.
- Tester has to check Positive as well as Negative testing.
- Positive Testing :-
- Positive testing is nothing but we have to provide correct input to the application.
- Ex. If there is mobile field, in india mobile number are of 10 digit, then tester check the functionality by entering 10 digits number, whether it works or not.
- Negative Testing :-
- Negative testing is nothing but we have to provide incorrect things or we have to perform negative operations on the functionality.
- Ex.If there is mobile field, the number should not accept 9 digit or less and more than 10 digites. Tester checkes system by entering less or more than 10 number in field.
- Grey Box Testing :
- Grey Box Testing is the combination of White Box Testing and Black Box Testing.
- Tester is involved in this testing.
- To do Grey Box Testing tester need some programming knowledge.
- So, at the time of testing of any defect occurs than instead of sending that defect to the developer he will change in the code and resolve that defect.
6. Maintenance :
- Is nothing but we have to provide some service after delivery of the product.
- In Maintenance part Technical support as well as non-technical support is involved.
- Technical support is called as KPO (Knowledge Process Outsourcing).
- Non-technical support called as BPO (Business Process Outsourcing)
0 Comments