SBTS – Academic Projects Execution Methodology (SAP-EM)

Purpose

The purpose of SAP-EM methodology is

Scope

This methodology shall be used to orient on the activities and work products for each phase.

Each SAP-EM project covers the complete SDLC and different phases – Enrollment, Orientation, SDLC Execution, Documentation, Evaluation, and Certification.

The SAP-EM methodology offers the flexibility of entry and exit through any of the defined phases. The user can use this flexibility by following the Entry Input Task Validation Output Exit (EITVOX) criteria defined for each phase.

Acronyms

Acronym

Explanation

ATP

Acceptance Test Plan

ATR 

Acceptance Test Report 

CDR 

Critical Design Review Report (Review Report for DDD) 

CTQ

Critical To Quality

DDD

Detailed Design Document

ESAD

Embedded System Analysis and Design

HLD

High-Level Design

HLDD

High-Level Design Document

HOQ

House Of Quality

ITP

Integrated Test Plan

ITR

Integrated Test Report

ML

Module Leader

OOAD

Object-Oriented Analysis and Design

PDR

Preliminary Design Review Report (Review Report for HLDD)

PL

Project Leader

PM

Project Manager

PRS

Project Requirements Specifications

QFD

Quality Function Deployment

QMS

Quality Management System

RMP

Risk Management Plan

SDLC

Software Development Life Cycle

SPP

Software Project Plan

SRR

Software Requirements Specifications Review Report

SRS

Software Requirements Specifications

SSAD

Structured Systems Analysis and Design

STP

System Test Plan

STR

System Test Report

TM

Team Member

URD

User’s Requirements Document

URR

User’s Requirements Review Report

UTP

Unit Test Plan

UTR

Unit Test Report

VOC

Voice Of Customer


Overview -

The SBTS SAP-EM comprises of the following phases:

  1. Student Enrollment
  2. Orientation – General and Project Specific
  3. Project Execution
    1. Requirements Gathering
    2. Requirements Specifications
    3. Design
    4. Coding and Unit Testing
    5. System and Acceptance Testing
  4. Documentation
  5. Evaluation and Certification
A.Student Enrollment

In this phase, the student is enrolled for the chosen academic project. The information about theorganization and about the available project would be explained in detail by SBTS Project counselor to each of the students visits us. The project selection questionnaire, followed by a technical discussion with counselor enable the student to choose an appropriate academic project. The student would select the best-suited project based on the inputs from the counselor and other chosen parameters of his or her choice. Discussions shall be held to understand the exact plans of the student and institute’s guidelines.

After project selection, the student would be enrolled, fee collection would take place. The batch details, admit card shall be issued to the student.

Entry

Student’s  requirements/Voice Of Customer/Institute’s guidelines

Inputs

Student’s Expectations, Budgetary and schedule constraints, Student’s technical competency

Tasks

  • Gather student requirements
  • Understand his or her interest/competent area
  • Identify the list of prerequisites (if any )
  • Publish the project schedule and key milestones

Verification / Validation

Entry in the enrollment register
Issued Receipt and Collected fee
Project Traceability Matrix and other artifacts

Outputs

Collected fee
Receipt to student
Entry into enrollment register
Update to identify faculty along with batch details
Scheduled batch along with timings
High-level project plan including key milestones
Update to Director, Admin on the new enrollment

Exit

Plan for Orientation


B.Student Orientation

This phase focuses on dos and don’ts of a project. Also gives orientation on tools, templates, and techniques that are required during project execution.

Entry

Selected Project – scope, timelines, and the required efforts

Inputs

Project abstract document

Tasks

  • Set the in-scope and out-scope activities
  • Help the student to complete any prerequisites
  • Introduce applicable tools, templates, and techniques

Verification / Validation

Multiple-choice exam on orientation / prerequisites
Viva / discussion

Outputs

Project charter and project outlines
Project understanding document

Exit

Complete project execution plan along with work break down structure


C.PROJECT EXECUTION PHASE – further divided into below four sub phases Requirements Gathering

In this phase, the information about the user’s software requirements shall be gathered and documented in SBTS standard format. Discussions shall be held to make the student understand the user’s requirements.

Entry

Identified functional and non-functional requirements

Inputs

Proof of concept / Project Scope Document / Formal Proposal or inputs

Tasks

Gather customer needs and prioritize the needs as per Kano model
Transfer customer needs into critical to quality parameters
Prepare a basic risk management plan and classify the identified risks
Identify the critical acceptance test cases along with the test data

Verification / Validation

User Requirement Document
Risk Management Plan

Outputs

URD
Risk Management Plan
Tollgate Review Report

Exit

Base lining of URD


C2.Requirements Specifications

During this phase, the user’s software requirements shall be thoroughly understood to convert to System specifications. The software requirements shall be documented in SB Technology’s standard format. The documentation shall use the implementation specific terms for the ease of understanding for the designers and developers.

Entry

Baselined URD

Inputs

URD
Project Plan
Tollgate Review Report

Tasks

Group the requirements into different categories
Map the requirements to corresponding system specifications
Following an appropriate traceability matrix, define the specifications

Verification / Validation

Project Requirements Specification
Updated project plan

Outputs

Project  Requirements Specification
Review Reports
Review Checklist

Exit

Approved Project Requirement Specifications


C3.Design

During this phase, the major modules shall be identified based on the functionality and design documents shall be prepared for each of the modules. Based on the project requirements, one of the following design paradigms may be chosen:

 Embedded System Analysis and Design (ESAD)  Object-Oriented Analysis and Design (OOAD)

Entry

Approval of PRS, completed  

Inputs

Baselined SRS / PRS  (as applicable)
Updated Project plan
Tollgate Review Report

Tasks

Identify the different sub modules / functional blocks
Convert the system specifications to corresponding design elements for each block
Finalize the design elements and parameters

Verification / Validation

Design Document
Test Plan and Test cases

Outputs

Design Document
Test Plan and Test cases
Review Reports

Exit

Design Document


C4.Assembling, Coding, and Testing

In this phase, components / functional blocks assembling, coding shall be done as per the defined standards.

Entry

Approval of Design Document  

Inputs

Baselined DDDs, UTP, and UTRs
Components as per BOM – Bill of Material
Coding Standards
Updated Project plan

Tasks

Soldering the components
Assembling the sub systems
Completing the applicable coding
Unit, Functional, and Non-functional testing

Verification / Validation

Project Result/outcome as per the defined tests cases and test data

Outputs

Assembled Unit
Source Code
Testing Reports
Review Reports

Exit

Unit tested and base lined Source Code and the assembled unit


C5. Final Testing – Burn-in and Acceptance Testing

In this phase, the functionality of the built product shall be tested as a whole. The STRs and ATRs that are drafted at the Project Requirements Specifications phase shall be reviewed and approved before this phase begins.

Entry

Assembled unit along with the completion of Coding and Unit Testing

Inputs

Assembled unit
Unit specifications
Test Reports

Tasks

Run the burn-in test cases and acceptance test cases in an appropriate environment – temperature, voltage, and the duration

Verification / Validation

System Test Reports (STRs)  and Acceptance Test Reports (ATRs) against PRS

Outputs

System Test Reports (STRs)
Test Results
Tollgate Review Report

Exit

Tested and approved system


D. Documentation

Structural documentation of any project is extremely important. In this phase, student will learn on how to fill the applicable documents as per the standard templates – that include recording the minutes of the meetings, observations, potential risks, faced challenges, and lessons learned. This phase is a continua phase starting from student enrollment to final testing. This phase goes in concurrence with the other project phases.

E. Evaluation and Certification

In this phase, student’s performance will be evaluated as per SB Technologies evaluation criteria focusing on quality of work, followed timelines, documentation quality, and the gained knowledge. The evaluation is based on the weighted averages. The student has to score minimum cut-off mark in each segment to get certified. The cut-off mark and evaluation criteria change from project to project based on the scope, complexity, and timelines.