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

Software Testing Life Cycle – STLC

  Software Testing Life Cycle defines the various phases in the testing of software. In this, each activity is carried out in a planned and a systematic way. Each phase has different goals and deliverables. Below are the phases of STLC Requirement Analysis Test Planning Test Case Development Test Environment set up Test Execution Test Reporting/ Test Cycle Closure Phases and activities in STLC Phase   Entry Criteria Activities Performed Deliverable Requirement Analysis Software Requirement  Design Document User Acceptance Criteria Brainstorming of requirements Understand the feasibility of the requirements Do automation of feasibility study Testing Feasibility Report Test Planning Updated requirement document Test Feasibility Report Define the scope of the project Identify the risks of the project Determine the test approach, techniques, covera...
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

Use Cases and Test Cases

  What is a Use Case In Software Development Environment Use Case is identified as the list of actions or steps typically defining the interactions between actors and the system in order to perform a feature of the software. The actor can be a human or an external system.  What is a Test Case A Test Case is a document which consists of a set of conditions or actions which needs to perform on the software in order to verify expected functionality of the feature. When comparing these two terms we can see a few clear differences between these two as below Use Case   Test Case Components - Use Case name, Actors, Pre Conditions, Assumptions, Post Conditions, Business Rules, Normal Process flow, Alternative process flow Components - Test Case ID, Test Case Title, Pre-Conditions, Test Case Description, Expected Results, Actual Results, Priority, Complexity, Bug ID Describes the overview of the software functio...
Post a Comment
Read more