Skip to main content

Stakeholders of SDLC

 

The different stake holders involved in different phases of SDLC:

  • Clients/Customers
  • Business Analysts
  • Architects
  • Project Managers
  • Developers
  • Testers
  • Customer Support Officers  

Role of Business Analyst in different phase of SDLC

Requirements Analysis and Planning:

  • Makes appointments with the clients and start interviewing about the requirements of the project which is called Requirement Gathering or Requirement Elicitation.
  • Interviewed information is documented using documented prepare Use Cases, Use case Diagrams, Activity Diagrams, Data Flow Diagram

Designing

  • Review the solution documents and wok closely with designer and architects to ensure requirements are clear
  • Manage the changes to requirements both from the business and from the designer’s point of view through the change control process.

Developing

  • Conductus frequent meetings with development team in case of clarifications to e=make sure the project is in the right track.

Testing

  • Makes an appointment with clients and guide them throughout the Acceptance Testing Stage.

Implementation and Maintenance

  • Documenting and managing the Change Requests by client after the application is deployed in the Live environment.

Role of Developer in different phase of SDLC

Requirement Analysis and Planning

  • Participation in requirement analysis meetings
  • Identify system architecture

Design

  • Understand system requirements

Development

  • Develop the application infrastructure
  • Coding the application

Testing

  • Fixing bugs reported by testing team
  • Provide the different versions of the application

Deployment and Maintenance

  • Deploy the application in the live environment
  • Attend the client’s queries

Role of Test Analyst in different phase of SDLC

Requirement Analysis and Planning

  • Feasibility study of requirements
  • Identified the type of testing to be carried out in the project
  • Prepare the higher level of test plan and tools used in the project

Design

  • Review the design, check the testability
  • Assuring architecture covers all functional requirements
  • Prepare low level test plan including scope, risks, tools, environments etc.

Development

  • Design and develop the test cases
  • Preparation of environment for testing

Testing

  • Verify all the tests are run according to the test plan
  • Execution of test cases
  • Find defects and report them as early as possible
  • Verify bugs and make sure every functionality is working fine after new fixes
  • Perform various types of tests to make sure there are no defects in the application

Deployment and Maintenance

  • Prepare the user guide/manual of the product and ensure that there is no problem with the software deployment
  • Working on production issues (if any).

Comments

Post a Comment

Popular posts from this blog

Defect Management Process

Importance of the defect management process in software development teams Provide developers and other parties with feedback about the problem to enable identification, isolation and correction as necessary; Provide test leaders means of tracking the quality of the system under test and the progress of the testing; Provide ideas for test process improvement Fields in a bug report Bug ID: A bug number or an identification number makes bug reporting and referring to a bug much easier Bug Title: A bug title is read more often than any other part of the bug report. It should say all about what comes in the bug. Also, the bug title should be suggestive enough that the reader can understand it. Priority: Based on the severity of the bug, a priority can be set for it. A bug can be a Blocker, Critical, Major, Minor, Trivial, or a suggestion. A bug priority from P1 to P5 can be given so that the important ones are viewed first. Platform/ Environment: The OS and browser configuration is nece...
Post a Comment
Read more

End to End Test vs Component Test

E2E Test E2E - End to End Tests help verify high value paths in an application. In other words, they help verify user stories as they often represent in the application. The main purpose of E2E testing is to test from the end user’s experience by simulating the real user scenario and validating the system under test. Basically these tests check the complete end-to-end process flow - The one happy scenario   Below are the E2E test cases we can write for the Graph feature Scenario 1 : User can add a Graph Scenario 2 : User can rename the Graph Scenario 3: User can add data to the Graph Scenario 4: User can remove the data from the Graph Scenario 5: User can manage the time zone Scenario 6: User can delete the Graph As an example, let’s say we need to write E2E test for Rename Graph scenario. Below is the flow we should cover. Log in as an Admin → Navigate to the Data Studio → Click on a Dashboard → Click on the graph ellipsis menu → Click on “Rename Graph” → Ent...
Post a Comment
Read more

SDLC – Software Development Life Cycle

  Software Development Life Cycle is a process used by software development industry to develop high quality software. This consists of a detailed plan describing how to develop, maintain, replace and enhance specific software. The following figure is a graphical representation of the stages of a typical SDLC. Requirement Analysis Phase: This is the most important and the fundamental stage of the SDLC, performed by the most senior members (Project Manager, Business Analyst, Designer, Test Lead, Subject Matter expert) of the team with inputs from the customers, market surveys and domain experts in the industry. This information is then used to plan the basic project approach and to conduct product feasibility study in the economical, operational and technical areas. Requirement Analysis phase completes when the client signs of the SRS - Software Requirement Specification. Design Phase: Based on the requirements specified in SRS design approach for the product architectur...
Post a Comment
Read more