Mt s2 sdlc

DO NOT DISTRIBUTE – HIGHLY CONFIDENTIAL
Agenda:
• Different Roles in IT
• Bidding
• Kick of Meeting
• PIN
• Software Development Process

2
Software Team – Roles & Responsibilities

3
Software EngineerQA Engineer
Test Engineer
Project Manager
Program Manag erBusiness Analyst
Team Lead
Product Manager
Tech Lead
Architect
Tech Writer
Understanding your role and responsibility and
role and responsibility of others is critical to your success.
Different Roles in IT
Software Team – Roles & Responsibilities

Bidding:
• It is defined as request for
proposal, estimations and
official agreement two parties
i.e., Sign in agreement.
4www.talentsprint.com

Kick-Off-Meeting:
• It is an initial meeting conducted in company soon after the
Project is signed.
• Who?
 High Level Management-Managers(Product, Program,
Technical…)
• Objective: To discuss the over view of the Project & to select
PM.

PIN (Project Initiation Note):
• PIN is a mail prepaid by the project manager and send to
the CEO of the software company in order to get the
permission to start the project development.
• Once the mail is approved from the CEO, PM is going to
prepare one more mail hence this mail is also called as PIN
and is going to share all concern team members in the
project stating that they are about start a project.

PIN (Project Initiation Note):
Project Manager PIN CEO
Team Members

SDLC:
• Software Development Life Cycle
Phases or stages of a project
from inception through
completion and delivery of the
final product… and
maintenance too!

Software Development Stages:
1. Requirement
2. Analysis
3. Design
4. Coding
5. Testing
6. Deployment
7. Maintenance

Requirement Phase:
• Role: BA & EM
• Task: Interacting with the client and gathering the
information.

Requirement Phase:
BA Client BRS EM/PM
SME
URS
PrototypeClientSRS

Requirement Phase:
• Proof: The proof of Requirement Phase is BRS Document.
• BRS- BDD (or) BD.
• SRS (or) FSD (or) FRS.
• URS (or) CRS.

Requirement Phase:
• Business Requirement (BRS)
1. Represent high-level objectives of the organization or
customer requesting the system or product.
2. Objectives captured in a project’s vision and scope
document
Ex.
The Flight Reservation System’s login operations must
provide basic security to access the system.

Requirement Phase:
• User Requirements
1. Describe tasks the user must be able to accomplish
with the product.
Ex.
1. Enter user id in the Agent Name field
2. Enter the password in the Password field
3. Click OK

Requirement Phase:
• Functional Requirements
1. Define the application’s software functionality to
enable users to accomplish their tasks, thereby
satisfying the business requirements
2. Documented in a Software Requirements Specification
(SRS).
Ex.
1. Allow access to authorized user ids and passwords
2. Deny access to invalid user ids and passwords

Analysis Phase:
• The process of identifying requirements, current
problems, constraints, Opportunities for improvement ,
timelines and Resources costs .
• Roles: Managers (Program, Project, Product).

Analysis Phase:
• Process:KT Sessions.
• …used for resolving any problems that need to be addressed.
• determine what attributes and behavior each object should
have, and how the objects should interact or interrelate with
each other.
• “Figuring out what your program should do in the best way
possible”.
• Feasibility study (social, economical etc).
• investigate the need for possible software automation in the
given system.

Analysis Phase:
• Difficulties in conducting requirement
analysis
1. Analyst not prepared
2. Customer has no time/interest
3. Incorrect customer personnel involved
4. Insufficient time allotted in project schedule
• Proof: SRS

Design Phase:
• The business of finding a way to
meet the functional
requirements within the
specified constraints using the
available technology.
• Roles: CA, TL
• Task: HLD, LLD.

Design Phase:
CA (HLD) Tech Lead(LLD) Team
Modules Sub Modules
(DFD,UML)
Pseudo Code GUI

Design Phase:
• Proof: TDD (Technical Design Document)
• Pseudo Code:
• - It is a set of English statements (or) Step by Step
Algorithm which will make the Developers more
comfortable while developing the actual code.

Design Phase:
1. Determine the set of instructions that will lead to a solution that meets
the customer’s requirements.
2. This set of instructions is called an algorithm.
3. Algorithms are usually represented pictorially (by flowcharts or UML
state diagrams)
4. Architecture, including hardware and software, communication,
software design (UML is produced here) are all part of the deliverables
of a design phase

Design Phase:
HLDS (High Level Design Specifications) From User Point
of view:
1. List of modules and a brief description of each.
2. Brief functionality of each module.
3. Interface relationship among modules.
4. Dependencies between modules.
5. Database tables identified with key elements.
6. Overall architecture diagrams along.

Design Phase:
LLDS (Low Level Design Specifications) / Detailed Design
1. Detailed functional logic of the module, in pseudo code.
2. Database tables, with all elements, including their type
and size.
3. All interface details.
4. All dependency issues.
5. Error MSG listing.
6. Complete input and output format of a module

Coding Phase:
Roles: Programmers/Developers
Task: Programming/Coding
Process:
1. Indentation
2. Proper color
coding
3. Commenting
TDD
Developer SCD Coding Standards
Proof: SCD

Coding Phase:
1. The specifications from the detailed design phase are converted into
programs.
2. Code is produced from the deliverables of the design phase during
implementation, and this is the longest phase of the software
development life cycle.
3. Design must be translated into a machine-readable form taking input
as SRS.
1. Done by Team of developers.
2. Reviews after every 500 lines of code
1. Code Inspection
2. Code Walkthrough

Testing Phase:
• Role: Test Engineer
• Task: Testing the System (or) Product.

Testing Phase:
Test Cases (Review) Build Defect Report Dev Team

Testing Phase:
1. Finding the hidden defects in developed Product.
2. During testing, the implementation is tested against the requirements
to make sure that the product is actually solving the needs addressed
and gathered during the requirements phase.
3. Unit, Integration, system and acceptance tests are done during this
phase. Unit tests act on a specific component of the system, while
system tests act on the system as a whole.

Testing Phase:
• Proof: The proof of the testing phase is Quality Product
i.e., Error Free Product (or) System.
• Note:
• Test Case: It is an idea of a Test Engineer to test something
of an application based requirements.
• GUI: It is an interface between the user and something
developed with graphics in-order to make the user
comfortable to interact with that something.

Deployment Phase:
• Task: Delivering the Software
• Roles: Deployment Engineer (or) Installation Engineer
• Process:
DEPLOY
Installation Engineer Client

Deployment Phase:
Deploying the product at client side.
Installation and setup of software application at
the customer site.
Proof: After delivering the Product the official
agreement will be signed off. This document will
be the proof for delivery phase.

Maintenance Phase:
1. Maintaining the software application
1. Fixing bugs
2. Integrate new features requested by customers
3. Provide support
2. Maintenance can be provided in 2 ways
1. Normal
2. Continuous
3. On Going Process

Summary:
• In this session we have discussed
 Different Roles in IT
 Phases of SDLC
 Sequence and flow of SDLC phases

Review Questions:
1. Which of the following requirements will provide the information
about the aspects what the user must able to accomplish?
1. User Requirements
2. System Requirements
3. Business Requirements
4. Non-functional Requirements
2. In the High-level design the database tables will be created with all
the columns in it defined.
1.TRUE
2.FALSE

Review Questions:
3. In which of the following stages of SDLC, the need for implementing the
automation for Testing is decided?
1. Requirements
2. Analysis
3. Design
4. Coding
4. Which of the Following is the last stage of SDLC ?
1. Analysis
2. Deployment
3. Maintenance
4. Coding

Assignments:
1.Suppose you are involved in a team which is enhancing the
“www.newtours.demoaut.com”, with the new “Hotels” functionalities.
List-out what are the:
a) Business Requirements
b) User Requirements
c) Functional Requirements
2. Suppose you are involved in a team which is adding a new module to the
“www.newtours.demoaut.com”, which is nothing but the “Hotels”, where
customers can book the Hotels also.
List-out the activities involved here as per the SDLC.

Mt s2 sdlc

Empfohlen

Empfohlen

Weitere ähnliche Inhalte

Was ist angesagt?

Was ist angesagt? (19)

Ähnlich wie Mt s2 sdlc

Ähnlich wie Mt s2 sdlc (20)

Mehr von TestingGeeks

Mehr von TestingGeeks (20)

Mt s2 sdlc