Skip to main content

Advanced SDLC Models

Advanced SDLC models mainly includes 

•         Fish Model
•         V-Model
•         Agile Model
•         DevOps Model

a) Fish Model: (Mr.Pulusuri Nageshwar Rao)
Fish Model is one of the advanced SDLC Model but it is time taking as well as expensive model. But this model can release quality guarantee software.
Due to these reasons, Fish model is famous for artificial intelligence like it can be used in satellite, aeronautical, health equipments fields.
Fish Model Diagram
where, SRS - Software Requirment Specification, HLD - High Level Design, LLD - Low Level Design, BA - Business Analyst, SA - System Analyst, TA -Technical Architect, CCB - Change Control Board, PIN - Project/Product Initiation Note
PM---Project Manager is responsible to prepare PIN and PIN can provide overall blueprint.
BA----Business Analyst can gather customer requirements and prepare BRS (Business Requirement Specification) or CRS (Customer Requirement Specifications) or URS (User Requirement Specifications)
Other BA can review BRS/CRS/URS for completeness and correctness.
SA----System Analyst can analyze customer requirements and prepare SRS
          (Software Requirement Specification)
Other SA can review SRS for completeness and correctness.
TA----Technical Architect can design software as diagram in HLD (High Level Design) and LLD (Low Level Design)
Other TA can review those designs for completeness and correctness. 
Programmers can develop programs.
Other programmers can test every program called as unit testing.
Programmers can integrate or interconnect programs to build software.
Other programmers can test those integration or interconnection called as Integration testing.
A separate software testing team can test software with respect to client requirement and expectations.
Programmers and testers can take feedback on software from client side people, called as Acceptance testing. If feedback is not good then, programmer can perform immediate changes in that software and tester can test those changes.
Few programmers and testers can go to client side for software release testing.
CCB---Change Control Board is a team of fresher’s are responsible to receive changes request from client side and they can handle those changes, called as maintenance/support/service.

b) V Model: (W.E.Perry)
V Model is one of the advanced SDLC Model and it is neither time taking nor expensive model. But this model can release less quality guarantee software as compared to fish model.
V model is famous for commercial domains like it can be used in banking sector, health care, E-commerce, logistics etc fields.
V Model Diagramwhere, SRS - Software Requirment Specification, HLD - High Level Design, LLD - Low Level Design, BA - Business Analyst, SA - System Analyst, TA -Technical Architect
PM---Project Manager is responsible to prepare PIN and PIN can provide overall blueprint.
BA----Business Analyst can gather customer requirements and prepare BRS (Business Requirement Specification) or CRS (Customer Requirement Specifications) or URS (User Requirement Specifications)
Same BA can review BRS/CRS/URS for completeness and correctness.
SA----System Analyst can analyze customer requirements and prepare SRS
          (Software Requirement Specification)
Same SA can review SRS for completeness and correctness.
TA----Technical Architect can design software as diagram in HLD (High Level Design) and LLD (Low Level Design)
Same TA can review those designs for completeness and correctness. 
Programmers can develop programs.
Same programmers can test every program called as unit testing.
Programmers can integrate or interconnect programs to build software.
Same programmers can test those integration or interconnection called as Integration testing.
A separate software testing team can test software with respect to client requirement and expectations.
Programmers and testers can take feedback on software from client side people, called as Acceptance testing. If feedback is not good then, programmer can perform immediate changes in that software and tester can test those changes.
Few programmers and testers can go to client side for software release testing.
CCB---Change Control Board is a team of fresher’s are responsible to receive changes request from client side and they can handle those changes, called as maintenance/support/service.

c) Agile Model: (Agile Group)
•         Agile model is different because, it is manifesto based model.
•         From agile manifesto:
•         Individuals and interaction over process and tools.
•         Working software over comprehensive documentation.
•         Customer collaboration over contract negotiation.
•         Responding to the change over following plan.
In agile model, we can get some sub models like shown below.
•         Scrum
•         Extreme Programming
•         Adaptive Software Development(ASD)
•         Dynamic System Development Method(DSDM)
In above all agile models, agile scrum is most popular one.

d) DevOps Model: (Development Operation)
This model is extension to agile scrum. In this model, one single team can involve from requirement gathering to maintenance.
In this process, corresponding team can use set of management tools, called as DevOps tools.
Devops Model Diagram












Labels:

Comments

Post a Comment

Popular posts from this blog

Test Initiation

STLC process can start with test initiation. In this stage, PO can prepare a test strategy document for current sprint or software testing. Test strategy is also called as test methodology or test approach. In sprint or software testing, strategies have three types of testing such as exhaustive testing, optimal testing, Ad-hoc testing. In general, Exhaustive testing is not at all possible and ad-hoc testing is not reasonable. Due to these reasons, ST is following optimal testing strategy to conduct better testing. • Optimal test strategy document format in IEEE 829 standards i) Test strategy document ID - Unique name or number as title. ii) Scope and Objective - Importance of testing in current sprint or software. iii) Business issues – Budget allocation for testing. iv) TRM (Test Responsibility Matrix) – List of tests to be conducted. v) Roles and Responsibilities – PO can specify the roles in ST testers and specifies responsibilities for each other. vi)Test autom...
1 comment
Read more

STLC - Software Testing Life Cycle

Sprint / Software Testing Life Cycle) Where, PO - Product Owner, SM - Scrum Master, ST -Scrum Team From Agile Scrum Terminology: ERROR : When a developer finds a problem in coding called as ERROR. DEFECT/ISSUES/INCIDENT/TICKET : When a tester finds a problem in sprint or software called as DEFECT/ISSUES/INCIDENT/TICKET. BUG : When a developer accepts testers reported defect called as BUG. FAILURE : When a client people face problem in sprint or software called as FAILURE. SDLC vs. STLC in agile scrum where, CEO - Chief Executive Officer, PO - Product Owner, SM - Scrum Master, ST - Scrum Team, DR - Defect Report, MS - Modified Sprint, UT - Unit Testing, IT - Integration Testing, SH - StakeHolder
1 comment
Read more

Agile Scrum Process

Agile scrum is one of the famous as well as advanced model used nowadays in software testing. The dictionary meaning of scrum is a team of various people who are having their own special skill sets. In this field of software testing, scrum is a team which includes developers as well as testers. •            It is the famous and advanced SDLC model to develop the project based and product based software. •          It develops the software as increment by increment , called as Sprint . •          It releases the sprints to client or market in incremental spiral process. •          Actually, one sprint is a combination of previous sprint and some other extra features . •          Here, Sprint means piece of software which is potentially shippable (release) to the client  ...
Post a Comment
Read more