Scribd
Upload
40 views

Weekly Diary of CPP

Weekly diary format for final project

Uploaded by

Om Patil
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
40 views

Weekly Diary of CPP

Weekly diary format for final project

Uploaded by

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

Weekly diary of CPP

Week No 1: Date:20/07/2024

Activities Planned:
• Firstly we all discuss about the so many topics based on IOT.
• We Discuss about 5 to 10 topics and collect their Information.
• This 5 to 10 topics we explain this to our project guide.
• Sir suggests some more information and topics related to this.

Activities Executed:
• In this 5 to 10 topics are discussed with sir and doubts related to that.
• Sir asked some questions regarding to topic and asked this will use in
real time?

Reason For Delay if any: No Delay

Corrective Measure adopted:


• Regular Check-ins : Schedules daily or weekly Standup meetings to
discuss progress,challenges and take immediate next steps.
• By adopting these corrective measures sir asked us to think about some
topics.

Remarks or Signature of Guide:


Week No 2: Date:03/08/2024

Activities Planned:
• In this week, we planned to collect detailed information of Hostel
security Management Based on IOT.
• The objective was to analyze the features, functionality, and user
interface of these apps.
• We aimed to prepare a comparative report to present the pros and cons
of each app.
• We also planned to discuss potential improvements and new features
with sir.

Activities Executed:
• We gathered information on the Hostel security Management Based on
IOT as planned and presented the data to sir.
• Sir discussed some doubts and clarified the functionalities of these
apps.
• Sir posed some key questions to us, such as:
- What specific tasks are performed in these project?
- What are the unique selling points (USP) of each Hostel security
Management Based on IOT compared to competitors in the market?

Reason For Delay if any: No Delay

Corrective Measure adopted:


• Regular Check-ins: Scheduled daily or weekly standup meetings to
ensure continuous progress tracking and early identification of any
bottlenecks.
• Clear Documentation: We ensured that all discussions were
documented, outlining roles, responsibilities, and any changes to
project timelines or features.
• Feedback Integration: Incorporated feedback from sir and peers into
the analysis report, enhancing the overall quality of the project
deliverables.
• Task Prioritization: We prioritized urgent tasks to meet deadlines
while maintaining quality, ensuring no delays in subsequent weeks.

Remarks or Signature of Guide:


Week No 3: Date:17/08/2024

Activities Planned:
• Getting discussions on a few more topics, studying basic features,
objectives, advantages, and disadvantages through projects.

Activities Executed:
• While surveying these projects, we finally came across the topic of
"Hostel Security Management based on IOT."
• We might focus on several key activities to advance the project. Sir
discussed the key activities with us.

Reason For Delay if any: No Delay

Corrective Measure adopted:


• Regular Security Audits:
- Audit Process: Identify vulnerabilities and weaknesses.
- Assess risk levels.
- Develop remediation plans.
- Implement corrective measures.
• Corrective Measures:
- Network Security
- Database Security
- Application Security, etc.
• By implementing these corrective measures, the Vendor Connect
application will maintain a robust security posture, protecting sensitive
data.

Remarks or Signature of Guide:


Week No 4: Date:31/08/2024

Activities Planned:
• In the 4th week of the Capstone project, we gathered overall
information about the personal Hostel Security Management based on
IOT and its application and presented it in front of our guide.
• By discussing the project, finally, our project got selected on the date
31st August.

Activities Executed:
• Once our project was selected, several key activities were executed to
ensure a smooth transition into the next phase.
• Allocate resources, including team members, budget, and tools, to
support the project moving forward.
• Define and communicate specific roles and responsibilities for each
team member to ensure clarity.

Reason For Delay if any: No Delay

Corrective Measure adopted:


• Conduct thorough compliance checks to ensure all aspects of the
project meet legal and regulatory requirements, making adjustments as
necessary.

Remarks or Signature of Guide:


Week No 5: Date:21/09/2024

Activities Planned:
• We shared our key features and core concepts of the project with the
guide.
• We explained our key features to the guide, which we will implement
in our project.
• Discussed the integration of user feedback and how it will shape the
next iterations of the project.

Activities Executed:
• We finalized our key features and core concepts from the guide, and we
are going to execute them in our project.
• Conducted a brainstorming session with the team to identify potential
challenges in the development and find solutions ahead of time.
• Established a timeline for the next phase of implementation, ensuring
every team member understands their responsibilities.

Reason For Delay if any: No Delay

Corrective Measure adopted:


• Patch Releases: Scheduled regular updates to fix identified bugs and
improve our ideas.
• Reviewed the project’s architecture to ensure scalability and security.
• Implemented a feedback mechanism for early testing, aiming to
identify issues before they affect project milestones.

Remarks or Signature of Guide:


Week No 6: Date:05/10/2024

Activities Planned:
• We displayed the soft copy of our synopsis to the guide.
• The guide suggested extra modifications that could enhance our
project.
• Planned a discussion to incorporate feedback on document structure
and the project's overall technical approach.

Activities Executed:
• According to our guide, we modified our synopsis file.
• Modifications included changes in font size, font name, and layout for
better readability.
• Additional refinements were made to the structure of the document,
making it more concise and clear.

Reason For Delay if any: No Delay

Corrective Measure adopted:


• Our guide recommended including detailed information about each key
feature in the synopsis.
• Advanced key features were reviewed and expanded in more detail,
making the project more comprehensive.
• Further improvements were suggested in documentation style and
formatting for future updates.
• We also added a section focusing on project testing and quality
assurance, which was missing earlier.

Remarks or Signature of Guide:


Week No 7: Date:19/10/2024

Activities Planned:
• As per our guide's instruction, we planned to recheck our synopsis file
Submitted.

Activities Executed:
• Finally, we submitted our hard copy of the synopsis file to the guide.

Reason For Delay if any: No Delay

Corrective Measure adopted:


• The team worked extra hours to finalize the revisions and conducted a
thorough check to ensure that all the feedback provided by the guide
was incorporated before submission.

Remarks or Signature of Guide:

You might also like