Scribd Logo
Upload

Welcome to Scribd!

  • 203 views

    SBTS - Mini Project Execution Methodology

    Uploaded by

    Prashant Arra
    The document outlines the phases of the MPEM (Mini Project Execution Methodology) used at SBTS. The phases include: student enrollment, orientation, project execution involving requirements gathering, specifications, design, coding/testing, and documentation. Project execution follows a structured process with requirements documented and approved at each stage prior to proceeding. The goal is to define the project execution process and provide flexibility to enter/exit phases based on defined criteria.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as DOC, PDF, TXT or read online from Scribd

    SBTS - Mini Project Execution Methodology

    Uploaded by

    Prashant Arra
    203 views6 pages
    The document outlines the phases of the MPEM (Mini Project Execution Methodology) used at SBTS. The phases include: student enrollment, orientation, project execution involving requirements gathering, specifications, design, coding/testing, and documentation. Project execution follows a structured process with requirements documented and approved at each stage prior to proceeding. The goal is to define the project execution process and provide flexibility to enter/exit phases based on defined criteria.

    Copyright

    © Attribution Non-Commercial (BY-NC)

    Available Formats

    DOC, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    The document outlines the phases of the MPEM (Mini Project Execution Methodology) used at SBTS. The phases include: student enrollment, orientation, project execution involving requirements gathering, specifications, design, coding/testing, and documentation. Project execution follows a structured process with requirements documented and approved at each stage prior to proceeding. The goal is to define the project execution process and provide flexibility to enter/exit phases based on defined criteria.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as DOC, PDF, TXT or read online from Scribd
    Download as doc, pdf, or txt
    203 views6 pages

    SBTS - Mini Project Execution Methodology

    Uploaded by

    Prashant Arra
    The document outlines the phases of the MPEM (Mini Project Execution Methodology) used at SBTS. The phases include: student enrollment, orientation, project execution involving requirements gathering, specifications, design, coding/testing, and documentation. Project execution follows a structured process with requirements documented and approved at each stage prior to proceeding. The goal is to define the project execution process and provide flexibility to enter/exit phases based on defined criteria.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as DOC, PDF, TXT or read online from Scribd
    Download as doc, pdf, or txt
    You are on page 1of 6

    SBTS – Academic (Mini) Project Execution Methodology - MPEM

    Version. 1.0 July 21, 2010

    Purpose
    The purpose of MPEM methodology is
    • To define how MPEM projects are executed and
    • To serve as a basis for different phases in a MPEM project starting from enrollment until
    certification.

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

    Each MPEM project, which is taken up may go through all the phases – Enrollment, Orientation, SDLC
    Execution, Documentation, Evaluation and Certification.

    The MPEM 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.

    Overview -
    The SBTS MPEM comprises of the following phases:
    A. Student Enrollment
    B. Orientation – General and Project Specific
    C. Project Execution
    1. Requirements Gathering
    2. Requirements Specifications
    3. Design
    4. Coding and Unit Testing
    5. System and Acceptance Testing
    D. Documentation
    E. Evaluation and Certification

    A. Student Enrollment
    In this phase, student is enrolled for chosen mini project. The information about the organization and
    about the available project would be explained in detail by SBTS Project counselor to each of the
    student visits us. The VOC (Voice of the customer) would be noted down based on the student
    requirements; institution guidance and value add to the student, the appropriate projects would be
    shown to the student. 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
    •<Please list down each and every step>

    Verification / Entry in the enrollment register


    Validation Issued Receipt and Collected fee
    <fill remaining>
    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
    <fill remaining>
    Exit Plan for Orientation

    B. Student Orientation
    <fill>

    < fill the below table with right entries; below is ONLY illustrative>
    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
    •<Please list down each and every step>

    Verification / Entry in the enrollment register


    Validation Issued Receipt and Collected fee
    <fill remaining>
    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
    <fill remaining>
    Exit Plan for Orientation
    C. PROJECT EXECUTION PHASE – further divided into below four sub phases

    C1. 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 Customer’s requirements


    Inputs Proposal from customer
    Tasks Gather customer needs

    <fill>
    Verification / URD
    Validation <fill>
    Outputs URD
    <fill>
    FMEA
    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 <fill>
    Verification / Software Requirements Specification
    Validation Updated project plan
    <fill>
    Outputs Software Requirements Specification
    Review Reports
    Review Checklist
    Exit Approval of Software Requirements 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:
     Structured System Analysis and Design (SSAD)
     Object Oriented Analysis and Design (OOAD)

    Entry Approval of SRS, completed


    Inputs Baselined SRS
    Updated Project plan
    Tollgate Review Report
    Tasks <fill>
    Verification / Design Document
    Validation Test Plan and Test cases

    Outputs Design Document


    Test Plan and Test cases
    Review Reports
    <fill>
    Exit Design Document

    C4. Coding and Unit Testing


    In this phase, coding shall be done following the programming standards. The coding shall be carried
    out at each Design Document section level. Code review shall be done and the code shall be unit
    tested. The programming standards to be used shall be identified. GUI standards, if applicable, shall
    be indicated. Programmers, Code Reviewers and Unit Testing team shall be aware of the relevant
    Design document specifications.

    Entry Approval of Design Document


    Inputs Baselined DDDs, UTP and UTRs
    Coding Standards
    Updated Project plan

    Tasks <fill>
    Verification / Code Review/Inspection against programming standards and DDR
    Validation Review of UTR against DDD
    Traceability Matrix
    Testing Review

    Additional verification/validation for six sigma projects:


    Project Charter
    Outputs Source Code
    Code review report
    Unit Test Report and Test Results
    Review Reports

    Exit Unit tested and base lined Source Code


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

    Entry Completion of Coding and Unit Testing


    Inputs Unit tested and baselined source code
    Reviewed and approved ATPs and STPs
    Updated Project Plan

    Tasks <fill>
    Verification / System Test Reports (STRs) and Acceptance Test Reports (ATRs)
    Validation against SRS

    Outputs System Test Reports (STRs)


    Test Results
    Updated Project Plan
    Tollgate Review Report

    Exit Tested and approved system

    D. Documentation
    <fill>

    < fill the below table with right entries; below is ONLY the illustrative>
    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
    •<Please list down each and every step>

    Verification / Entry in the enrollment register


    Validation Issued Receipt and Collected fee
    <fill remaining>
    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
    <fill remaining>
    Exit Plan for Orientation
    E. Evaluation and Certification
    <fill>

    < fill the below table with right entries; below is ONLY illustrative>
    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
    •<Please list down each and every step>

    Verification / Entry in the enrollment register


    Validation Issued Receipt and Collected fee
    <fill remaining>
    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
    <fill remaining>
    Exit Plan for Orientation

    You might also like

    pFad - Phonifier reborn

    Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

    Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


    Alternative Proxies:

    Alternative Proxy

    pFad Proxy

    pFad v3 Proxy

    pFad v4 Proxy