Scribd
Upload
9 views5 pages

Project Report Template

The document outlines the submission process for a student project, divided into three main parts: Initial Submission, Interim Submission, and Final Submission. It details the requirements for each submission, including project objectives, architecture diagrams, test cases, code, and results. Students are instructed to provide necessary documentation, diagrams, and links to their final project code and media for validation.

Uploaded by

tpaswin2006
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
9 views5 pages

Project Report Template

The document outlines the submission process for a student project, divided into three main parts: Initial Submission, Interim Submission, and Final Submission. It details the requirements for each submission, including project objectives, architecture diagrams, test cases, code, and results. Students are instructed to provide necessary documentation, diagrams, and links to their final project code and media for validation.

Uploaded by

tpaswin2006
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 5

//Initial Submission part.

This part is submitted by the student


to ensure they have understood the project and the
requirements.//

<All the important points which are mandatory are marked in Blue>

TEAM MEMBERS

1 <Project Title>

1.1 Objectives

1.2 Description

1.3 Scope & Features

1.4 System Requirements


Inputs:
Outputs:

1.5 Hardware Requirements

1.6 Software Requirements

1.7 Knowledge Required

1.8 Skill Required

Project Requirements
//Initerim Submission part. This part is submitted by the
student to ensure they have correctly formulated the
solution. This ensures they have planned correctly for all the
logic and hardware connections.//

2 Project Architecture Submission:


2.1. Hardware Architecture:

2.1.1 Block Diagram: (This is the simplest and most powerful project description tool. Following this
approach, Try and depict your overall system with a number of different blocks. E.g. If your system has 1
temperature sensor, 1 servo motor, a microcontroller and Thingspeak IoT channel, your block diagram will
consist of 4 components)

Take care to make the blocks all same sizes. If you want your project to look professional, instead of blocks,
you may also use IEEE defined symbols for Servo, motors, sensors, etc.

2.1.2 Circuit Diagram: (This is the descriptive tool for defining all electronic circuits used in the project.
Students from the Electronics Discipline are already familiar with this concept. Please note the sample
diagram shown below. Please note that this type of diagram is known as circuit schematic diagram, which
does not show the component package details, only their overall functionalities. The below diagram shows a
battery, an LED, a resistor and a switch)
2.2. Software Architecture

2.2.1 Flowchart: (This is the descriptive tool utilized for defining a software code flow, or execution flow.
Every flowchart has the following few components. Please refer to the sample )

Please note that for flowcharts, there are different symbols for if/else input/ output, data. Please make your
flowchart according to convention.

2.2.2 State Machine Diagram: (This is an advanced form of representation, where it is possible to
describe a real-time system more efficiently. If you want to describe a system which turns on an led at a button
press, blinks it and switches it off after subsequent button presses and a timeout, you may do so by the
following state model.)
2.3. Test Cases:

All tests needed by the project to ensure correct operation are sketched out by the students here.
They can input a weekwise / daywise test planning required for validating the project. Or they can
simply put as test 1 test 2 etc.

Week / Day Test No Description


1 1 Test robot hardware
2 2 Test software output
3 3 Calibrate hardware output

//Final Submission part. This part is submitted by the student


to ensure the real world implementation of the solution is
also correct.//

3 Code and Results Submission:

3.1. Code Submission:


Students must submit all of their final codes for their embedded / technical systems in here. Students
should use text and not pictures of the interface.
3.2. Github Link of the code:
Students must submit the github repository link where they have kept their final project code. It will be
cross verified with the code submitted with this document.
3.3. Test case wise results:
Students must submit the test case wise results here according to the test cases they have formulated
previously.
3.4. Final Project Pictures:
Students must submit the pictures of the final working model in here. Students are advises to use a web
repository or the github itself to keep the pictures.
3.5. Final Project Videos:
Students must submit the video of the final working model in here. Students are advises to use a web
repository or the github itself to keep the video.
3.6. Setup Steps:
Students must submit the total process they went through to setup this project. This is used to cross
check and validate the video and results.

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