Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Scribd Logo
Upload

Welcome to Scribd!

  • 229 views

    Student Result Generation

    Uploaded by

    premait92

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd

    Student Result Generation

    Uploaded by

    premait92
    229 views6 pages

    Copyright

    © © All Rights Reserved

    Available Formats

    PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Download as pdf or txt
    229 views6 pages

    Student Result Generation

    Uploaded by

    premait92

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Download as pdf or txt
    of 6

    Student Result Generation

    Process Design Document

    Process Design Document – Student Result Generation 1


    Process Design Document History

    Date Version Role Name Organization Function Comments


    16.06.2024 1.0 Draft Jobin T J Naan Muthalvan FDP Trainer Creation v1.0

    Process Design Document – Student Result Generation 2


    1. Introduction
    1.1 Purpose of the document
    The Process Design Document describes the business processes chosen for automation using the
    UiPath Robotic Process Automation (RPA) technology.

    This document describes the sequence of steps performed as part of the process, as well as the
    conditions and requirements prior to its automation. This design document serves as a base
    documentation for developers to collect the details required for robotic automation of the
    same business process.

    1.2 Objectives
    The objective of this process automation is linked to the project business case and is mainly intended
    to:

    ➢ Deliver faster processing


    ➢ Reduce redundant activities
    ➢ Improve overall performance and reliability

    Process Design Document – Student Result Generation 3


    2. Detailed Process Map
    This chapter presents the chosen process in detail, which enables the developer to build the automated process.

    Read each student record Create a new excel


    from excel file file named
    ‘StudentReport’

    Fill the excel sheet with


    calculated values as Save the excel and rename the same
    such Total and Overall with below the naming conversion.
    Percentage StudentReport_DDMMYYYY

    Step Short Description

    1.1 Open the student records excel file from specific location.

    1.2 Read each student records from the excel file for further calculations.

    1.3 Calculate Total by adding each subject marks. Sum Columns Physics, Chemistry, Mathematics and
    ComputerScience.
    Example:67+65+89+97=318
    1.4 Calculate Overall Percentage by dividing Total mark with number of subjects.
    Example: 318/4=79.50
    1.5 Create a new excel file named ‘StudentReport’.

    1.6 Add 2 new columns named ‘Total’ and ‘OverallPercentage’ along with existing columns from source
    excel.
    Example:
    StudentID,StudentName,Physics,Chemistry,Mathematics,ComputerScience,Total,OverallPercentage
    1.7 Fill the excel sheet with calculated values such as Total and Overall Percentage along with existing
    columns from source excel.
    1.8 Save the excel file and rename the same with below the naming conversion.
    StudentReport_DDMMYYYY

    Process Design Document – Student Result Generation 4


    3. Generic Best Practices to follow:
    • Exception handling and logging are done, throwing of exceptions and logging of custom messages.
    • Use the Retry Scope for fragile parts in the workflow.
    • Use of appropriate delays between navigation (should not be hardcoded).
    • Easy to add enhancements with minimal changes to the existing workflow.
    • Use a data type that best suits the needs such as data tables, lists etc.
    • Are all required configurable values are in (XML file, database table, Excel, txt ) so that no code changes
    are required?
    • Are there deeply nested if-else or sequence blocks?
    • Are there redundant comments? Commenting on your code is fantastic; however, it can be overdone or
    just be plain redundant.
    • Process is organized to show the complete flow by invoking feature/functionality/user story .xaml
    • Naming convention and other best practices being followed.
    • Workflow analyzer errors and warnings are cleared.
    • Variables and argument should be named as per UiPath naming conversion guidelines.
    https://docs.uipath.com/studio/docs/naming-rules
    • Passwords, API access token etc should be hardcoded even if it is for test purpose.

    4. Project Evaluation Metrics:


    S.No Rule Score
    1. For adhere to UiPath best practices 35
    2. For accurate Total and Overall Percentage calculation in the final excel student report 35
    3. For final excel report generation with proper naming conversion 30
    TOTAL 100

    Process Design Document – Student Result Generation 5

    You might also like