Project Report Writing

Project Report Writing 

Yes!  I know you all are fully excited with completion of your Project work. But before relaxing, ensure to document the report before you forget what's done during the project building. 

The skeleton of any project report would look like: 

1. Introduction

2. Requirements and analysis

3. Design

4. Implementations 

5. Testing

6. References

1. Introduction

The introduction chapter should give an overview of your work. It must include how and why the project title was identified by your team. The story must continue narrating the timeline of your discussions during the title selection. 

2. Requirements and analysis

Then continue your story regarding how the requirements were decided and the importance of these requirements. 

3. Design 

The next part of the document must include how the various modules were visualized and then how each of these modules is given a technical shape. 

4. Implementations 

Here narrate all your stories about how the ideas on paper were converted into reality. This part of the document must include all the work you've done to implement each of the modules, and the challenges faced to integrate them. Make sure to include all the obstacles you came across during this phase and state how did you overcome them all. 

5 Testing 

Chalk out all the experience you had during Testing of the with. Narrate all the experience you had for module Testing, integrating the modules,  Testing the integrated modules and testing the overall project work. 

The best way to report is just follow your timeline of project making and narrate all your experiences in order. Please remember that every batch will have different experiences and hence never try to see what other batch report is looking like. Your report must narrate your experiences rather than some standard format (aka ready made projects). 

The report must highlight all the skills you learnt during your project work. 

Some important skills can be: 

*Understanding the clients

*Collecting the requirements from the clients

*Understanding what are the requirements of the client in detail without any ambiguity. 

*Knowing how to spilt a bigger problem into smaller ones

*How to convert these smaller problems into logical modules

*How to implement each module

*How to integrate the modules

*How to test the modules and the overall project

*How to correct if something is not as per your expectations

*And finally how to document at each stage of the project and its importance. 

Then friends,  now logically, technically, actually your work is over!!!

Well done for successfully completing the project work. 

All the best wishes for your future real-time projects!!!

Project Testing

Project Testing 

Once the project work is implemented, now it's time to test it's performance. It has to be taken up in exhaustive manner for each module- be it hardware, software or firmware. 

Module-wise Testing 

Each module must be tested for all possible conditions or situations. It is ensured that the module is behaving as per the requirements under all situations. 

Integrated Testing 

Now each module is working as per our requirements. The next step is to interconnect the modules one by one and keep testing the performance. The process continues to all the module are integrated and the overall performance is acceptable.

 Improvements needed? 

At any stage, if the performance is unsatisfactory: 

1. Check up whether there is any flaw in implementation. If so, make necessary corrections and proceed to testing phase again. 

2. If flaws couldn't be found in implementations, then the problem maybe with design. Check up the design once more. Any flaws found, then correct them and forward the new design for implementation. 

3. No problems with design? Then verify the requirements analysis. Correct the problems and submit the corrected analysis new design.

That's the V- model.

Everything is working as per requirements!!! 

Great! You have done it! 

Congratulations 👏👏👏

Check everything once more and get ready to close the project work. Should we? No, we still need to create our report on our project work we are proud upon. 

Project Implementation

Project Implementation 

The design provides the technical details on paper. In reality, it has to be either a hardware, a software or a firmware. The conversion of the ideas from the paper to the reality is the process called implementation. 

The process of implementation is highlighted here. 

Hardware module 

For each Hardware module, the most appropriate circuit is identified.

This selection must consider:

-I/O characteristics 

-Frequency range of operation

-Components availability

The inter-module constraints like impedance matching, connectors must be addressed with high priority. 

Then all the Hardware is physically connected module-wise

and the operation is verified. 

Software module 

For each software module, the optimum algorithm must be identified.

The parameters to decide the optimality are: 

- I/O data types

- Data Structures

- Time and space complexities

- Technology availability 

- Coding language

- DBMS

The actual code is written in the selected language onto the machine/ Hardware module.

Each component of the code is verified for its proper working. 

Final Assembly 

Once each module is ready to use, they are interconnected and the overall working is verified. 

Similarly, the software modules are interconnected and the overall working is verified. 

Finally, the firmware modules are interconnected and the overall working is verified. 

The next phase is thorough inspection and testing of hardware, software and firmware. 

Project Design

Project Design

Now the engineering activities begin. The team now looks carefully the requirements and develops a rough plan of how to proceed. It then selects the resources needed to build the project. 

Modular building 

The whole project is divided into sequence of modules, each with specific goal. Block diagrams for hardware

and flowchart

or url diagrams for software are

some choices for modular representation. Then decide the appropriate hardware and/or software for each of these modules.  

In case of hardware, select the circuit that best fits the module requirements. 

For software, select the suitable algorithm best for the module. 

Outcomes

The outcomes of this phase is the list of circuits and algorithms for each of the modules of the project and their interconnections. 

This list is forwarded to the implementation of the project.

Requirements Analysis

Requirements Analysis 

Once the requirements of the project are collected and documented,  the documents proceed to the Analysis team. Here the requirements are analysed and are segregated into various groups depending upon the complexity of the requirements, knowledge availability, expertise needed etc into simple, medium and complex. 

Process

Divide the team into two groups: 

Now the first group acts as the requirements collection team and the second work as analysis group. 

Discussions and arrangements are continued to have greater insight of the problems. 

Prioritise 

Now set priorities of each of the requirements. 

This process must consider 

-Seriousness of the problem: the more serious, the higher the priority

- Possibility of implementation: look for the availability of resources, technology required to proceed to the design stage. The higher the availability the higher will the priority. 

Documentation 

The various lists as per their priority are created.  Care must be taken to ensure to document the list accurately with no ambiguity. 

These documents are forwarded to the design team. 

Requirements collection

Requirements Collection 

Once the project title is decided, now its time to decide what actually to be done. It must include the two end points: 

-where to begin and 

-where to finish. 

This means, we need to decide what is the situation when we begin and what the final product should look like. 

The path to take from this beginning point to the ending point should not bother the team at this stage. The path is what we need to design and implement. Hence it is the time to create the questions and surely not trying to find answers. 

Divide your batch into two groups: 

One plays the role of the clients and the other group plays the role of requirements gathering team. 

Collection 

The process must include interviews, discussions. The two teams must interact in all possible ways to exchange the needs and ideas. The whole process must concentrate only on finding the problems of the clients and never try to look for the ways to reach the solutions here. At every act, make sure to document. 

Understand

The next step is to understand these questions/ problems listed in the Collection phase. 

-Let each member of the team list the requirements they have understood.

- Now all members sit together and look at each one list and discuss.  Arguments provide good opportunities for getting best.

A final list of requirements is now prepared with each member's participation. 

Document 

Now document all the requirements listed.  This list must be complete and unambiguous. It must be well documented. 

This document will proceed further to design phase.
 

How to select Project Title

Hi friends! I, Sandeep V.M., back to help you in making the project building an enjoyable journey. Today let us solve the problem of selecting the project work title.

The first major problems any batch faces is deciding the title of their project work. In this blog I would like to share some ideas that simplifies the process of title selection. Its a sequential process. 

The very first step is to discuss with all teammates and chalk down the ideas of each one at a common place.

The further process can be taken up as follows: 

• Subjects of Interest:  Let each of the teammates wire down the most interesting subjects. Anything one does with interest will yield best results. Comparing all the lists, decide the subject that is most common in these lists. That way we can narrow down the search process. 
• Topic of Interest:  The next step please do list out individually the topics of their interest from the the selected subject.  The topic of interest here may be the chapter of the selected subject each team member is convenient with. Then the team members discuss and finalize the common topic of interest. 
• Tasks of Interest: Then from this common topic of interest, each member must list out possible tasks that can be taken up as the project work. Then with the common consent one task maybe selected for the project work. 
  
  
  

This all activity is only limited to narrowing down to the common task of interest from an infinite possibilities. However, in the next phases, the knowledge derived from all the subjects play their vital role in completing the project work. 

Now we are through with the Title, it's time to list out all the requirements. That's what I will discuss in my next blog.

See you!