Shree Ambabai Talim Sanstha’s

SANJAY BHOKARE GROUP OF INSTITUTES, MIRAJ

FACULTY OF POLYTECHNIC
Institute Code: 1552

Department Of Computer Engineering

Micro Project Report
On

Create a Calendar using C Programming

Prepared By

Roll no. Enrolment No. Name

Under the Guidance of

Name Of Faculty

Submitted To

Maharashtra State Board of Technical Education, Mumbai

(Autonomous) (ISO-9001-2008) (ISO/IEC 27001:2013)
Academic Year 2023-2024

1
 MAHARASHTRA STATE
BOARD OF TECHNICAL EDUCATION
Certificate
(Only for individual micro project report)

This is to certify that Mr. Atharv Pradip Shinde Roll No. 22021 of Third emester
of Diploma in Computer Engineering , of Institute ATS Sanjay Bhokare Group
Of Institutes, Faculty Of Polytechnic, Miraj. (Code: 1552) has completed the
Micro-Project work satisfactorily in course Data Structure Using C ( ) for
the academic year 20…….. to 20…….. as prescribed in the curriculum.

Place: Miraj Enrollment No: 2215520032

Date: …………… Exam. Seat No: ……………

Subject Teacher Head of the Department Principal

2
 MAHARASHTRA STATE
BOARD OF TECHNICAL EDUCATION
Certificate
(Only for Micro Project Group report )

This is to certify that following students,

Roll no. Enrolment No. Exam Seat No. Name

of …….. Semester of Diploma in………………….. Engineering , of Institute

ATS Sanjay Bhokare Group Of Institutes, Faculty Of Polytechnic, Miraj.
(Code: 1552) are completed the Micro Project work satisfactorily in course
………………………………. ( ) for the academic year 20…….. to 20……
as prescribed in the curriculum.

Place: ……………
Date: ……………

Subject Teacher Head of the Department Principal

3
 Annexure – I

PART A – Micro-Project Proposal

Create a Calendar using C Programming

1.0 Brief Introduction

Imagine making your own digital calendar using computer magic. That's what we're up to in
our little project at DSU. We're using C, a computer language, to do this.

In our project, we're not aiming for a fancy calendar with all the bells and whistles. Instead,
we want to build a simple one that shows dates, days of the week, and maybe marks some
important stuff on it. It's like a basic calendar you'd hang on your wall.

During this project, you'll see how C programming can create a no-nonsense calendar that's
easy to understand. Join us as we dive into the world of making a Basic Calendar with C,
where we keep things simple and practical.

2.0 Aim of the Micro-Project ( in about 1 to 2 Sentences)

This Micro-Project aims at:
1 Programming Skills: Improve our C programming skills by applying them to a practical
project.
2 Gain hands-on experience with data structures and algorithms necessary for calendar.
functionality, such as arrays and loops.

3.0 Intended Course Outcomes

a) Understanding User Needs: By considering user requirements for a calendar application,

students gain insight into how software development aligns with real-world needs
b) Interface Design: Students will gain experience in creating a simple user interface, promoting
skills related to designing intuitive and user-friendly software.
c) User Needs: By considering user requirements for a calendar application, students gain
insight into how software development aligns with real-world needs.
d) Presentation: Students may be required to present their work, improving their
communication and presentation skills.

4
4.0 Literature Review
Calendar Systems:
- Explore various calendar systems like the Gregorian calendar, Julian calendar, and lunar
calendars. Understand their differences and historical significance.
C Programming Basics**:
- Review introductory C programming resources to refresh your knowledge of fundamental
concepts like variables, loops, and functions.
Data Structures and Algorithms**:
- Study data structures and algorithms relevant to calendar applications, such as arrays for
date storage, algorithms for calculating day-of-the-week, and event management
techniques.
Date Manipulation Libraries**:
- Research existing C libraries or functions that can simplify date manipulation tasks.
Understanding available resources can streamline your project development.

4.0 Proposed Methodology

Certainly, here's a proposed methodology for your microproject on creating a basic

calendar using C programming:

1. Project Planning:
- Define clear project objectives and scope, including the specific features and
functionalities your calendar will have.
- Create a project timeline with milestones and deadlines for each phase of development.
- Allocate roles and responsibilities if you're working in a team.

2. Requirement Gathering:
- Identify user requirements by considering what features the calendar should have, such
as date display, event management, and user interaction.

3. Literature Review:
- Conduct a literature review to gather information on relevant calendar systems, C
programming basics, data structures, and user interface design principles.

4. Design and Architecture:

- Design the overall architecture of your calendar application, including data structures for
date storage and event management.

5
5.0 Resources Required (major resources like raw material, tools, software etc.)
S. No. Name of Resource/material Specifications Qty Remarks
1 Development Environment Windows, Linux 1
2 C programming Blocks, Visual Studio 2
Code, or Dev-C++.
3 C Compiler running your C code 1
4 Library Documentation functions related to 3
date and time
5 Learning Resources textbooks 2

6.0 Action Plan (Sequence and time required for major activities for 8 Weeks)
S. No. Details of activity Planned Planned Name of Responsible
Start date Finish date Team Members
1
2

6
 Annexure – II
PART B – Micro-Project Report

Title of Micro-Project
1.0 Rationale
Imagine making your own digital calendar using computer magic. That's what we're
up to in our little project at DSU. We're using C, a computer language, to do this.

In our project, we're not aiming for a fancy calendar with all the bells and whistles. Instead,
we want to build a simple one that shows dates, days of the week, and maybe marks some
important stuff on it. It's like a basic calendar you'd hang on your wall.

During this project, you'll see how C programming can create a no-nonsense calendar that's
easy to understand. Join us as we dive into the world of making a Basic Calendar with C,
where we keep things simple and practical.
2.0 Course Outcomes Addressed
(Add to the earlier list if more COs are addressed)
a) Debugging and Testing: Ensures code reliability.
b) Project Management: Plans and adheres to timelines.
c) Programming Proficiency: Demonstrates C programming skills.
d) Data Structures and Algorithms: Applies them for date handling.
e) Software Development: Engages in full project lifecycle.
f) User Interface Design; Creates a user-friendly calendar.
g) Documentation Skills: Maintains project documentation.
h) Problem Solving: Tackles coding challenges.

3.0 Literature Review

In the process of developing a basic calendar using C programming, it is essential to draw

upon existing knowledge and research related to calendar systems, programming languages,
and user interface design. This literature review provides an overview of key concepts and
resources that inform the project.

Calendar Systems:
The foundation of any calendar application lies in understanding calendar systems. The
Gregorian calendar, introduced by Pope Gregory XIII in 1582, is the most widely used
calendar globally. It divides the year into 12 months with varying numbers of days and
adjusts for leap years. Understanding this calendar system is crucial for accurate date
calculations.

7
 C Programming Basics:
C programming serves as the primary language for this project. Resources such as "C
Programming Absolute Beginner's Guide" by Perry and Miller provide foundational
knowledge. Understanding data types, variables, loops, and functions in C is essential for
implementing the calendar's logic and functionality.

Date and Time Handling in C:

To work with dates and times effectively, we rely on the "time.h" library in C. The library
offers functions for obtaining the current time, date manipulation, and time conversions.
Understanding and utilizing these functions will be vital in managing and displaying dates
within the calendar application.

User Interface Design:

Creating an intuitive user interface is paramount for user interaction with the calendar.
Resources like "Don't Make Me Think" by Krug emphasize usability principles. Keeping the
interface simple and user-friendly aligns with the project's objectives.

Version Control with Git:

While not mandatory, employing version control with Git can streamline collaborative
development and code management. Resources like "Pro Git" by Chacon and Straub provide
guidance on Git usage.

Project Management and Documentation:

Project management practices, including milestone setting, project planning, and issue
tracking, are essential for project organization. Tools like Trello or Asana can facilitate this
process. Additionally, maintaining comprehensive project documentation, following
standards like IEEE documentation style, ensures clarity for future development and
understanding.

4.0 Actual Methodology Followed

Step 1: Project Planning and Objectives

- **Objective**: Define the project's objectives, including creating a simple calendar
application in C.
- **Team**: The team collectively outlined the project's scope and goals.

**Step 2: Requirement Gathering and Design**

8
 - **Objective**: Identify user requirements for the calendar and design its basic structure.
- **Team**: The team brainstormed user requirements and collaborated on the calendar's
initial design.

**Step 3: Implementation**

- **Objective**: Code the calendar application according to the design.

- **Roles**:
- Team Member A: Worked on date calculations and event management functions.
- Team Member B: Focused on the user interface, including date display and interaction.
- **Collaboration**: Regular code reviews and discussions ensured seamless integration of
individual components.

**Step 4: Testing and Debugging**

- **Objective**: Rigorously test the calendar for functionality and fix any issues.
- **Roles**:
- Team Member A: Conducted unit tests on date-related functions.
- Team Member B: Conducted user interface tests and ensured usability.
- **Collaboration**: Both team members worked together to address bugs and errors.

**Step 5: Documentation**

- **Objective**: Create comprehensive project documentation, including code comments

and user manuals.
- **Roles**:
- Team Member A: Wrote code comments and documented date calculation algorithms.
- Team Member B: Prepared a user manual explaining how to use the calendar application.
- **Collabor
5.0 Actual Resources Used (Mention the actual resources used).

S. No. Name of Resource/material Specifications Qty Remarks

1
2

6.0 Outputs of the Micro-Project

(Drawings of the prototype, drawings of survey, presentation of collected data, findings etc.)

7.0 Skill Developed / learning out of this Micro-Project

9
 (in about 50 to 100 words)

8.0 Applications of this Micro-Project

(in about 50 to 100 words)
9.0 Area of Future Improvement
(in about 50 to 100 words)
**************

10
 Annexure – III

Teacher Evaluation Sheet

Name of Student: ………………………………………………………… Enrollment No. ……………………………………

Name of Programme………………………………………………… Semester: ………………………………………… Course Title
……………………………………………………………….. Code:………………………………………………………………

Title of the Micro-Project: …………………………………………………………………………………………………….

(For Office Use Only)

Course Outcomes Achieved
………………………………………………………………………………………………………………………………………………..
…………………………………………………………………………………………………………………………………………………
………………………………………………………………………………………………………………………………………………….
Evaluation as per Suggested Rubric for Assessment of Micro Project
 (Please tick in appropriate cell for each characteristic)
S. Characteristic to Poor Average Good Excellent
No be assessed ( Marks 1-3 ) ( Marks 4 - 5 ) ( Marks 6 - 8 ) ( Marks 9- 10 )
.
1 Relevance to the Relate to very Related to some Take care of at- Take care of more
course few LOs Los least one CO than one CO
 ..
2 Literature Not more than At-least 5 relevant At –least 7 About 10 relevant
Survey two sources sources, at least 2 relevant sources, sources, most
/information (primary and latest most latest latest
collection secondary), very
old reference

3 Completion of Completed less Completed 50 to Completed 60 to Completed more

the Target as per than 50% 60% 80% than 80 %
project proposal
4 Analysis of Data Sample Size Sufficient and Sufficient and Enough data
and small, data appropriate appropriate collected by
representation neither sample, enough sample, enough sufficient and
organized nor data generated data generated appropriate
presented well but not organized which is organized sample size.
and not presented and presented Proper inferences
well. No or poor well but poor drawn by
inferences drawn inferences drawn organising and
presenting data
through tables,
charts and graphs.

5 Quality of Incomplete Just Well Well

Prototype/Mode fabrication/asse assembled/fabrica assembled/fabrica assembled/fabrica
l mbly. ted and parts are ted with proper ted with proper

11
S. Characteristic to Poor Average Good Excellent
No be assessed ( Marks 1-3 ) ( Marks 4 - 5 ) ( Marks 6 - 8 ) ( Marks 9- 10 )
.
not functioning functioning parts. functioning parts.
well. Not in proper In proper shape, In proper shape,
shape, dimensions within tolerance within tolerance
beyond tolerance dimensions and dimensions and
limit. good good
Appearance/finish finish/appearance. finish/appearance.
is shabby. But no creativity in Creativity in
design and use of design and use of
material material

6 Report Very short, poor Nearly sufficient Detailed, correct Very detailed,
Preparation quality sketches, and correct details and clear correct, clear
Details about about methods, description of description of
methods, material, methods, methods,
material, precautions and materials, materials,
precaution and conclusion, but precautions and precautions and
conclusions clarity is not there Conclusions. conclusions.
omitted, some in presentation. Sufficient Graphic Enough tables,
details are But not enough Description. charts and
wrong graphic sketches
description.

7 Presentation Major Includes major Includes major Well organized,

information is information but information and includes major
not included, not well organized well organized but information ,well
information is and not presented not presented well presented
not well well
organized .
8 Any other
(depending upon
nature of
project: please
write indicators
by pen)
Defense Could not reply Replied to Replied properly Replied most of
9 to considerable considerable to considerable the questions
number of number of number of properly
question. questions but not question.
very properly

12
 MIcro-Project Evaluation Sheet

Process Assessment Product Assessment Total

Part A - Project Project Methodology Part B - Project individual Marks
Proposal (2 marks) Report/Working Model Presentation/Viva 10
(2 marks) (2 marks) (4 marks)

Note:
Every course teacher is expected to assign marks for group evolution for each group of students in first 3
columns as per rubrics & individual evaluation in 4 TH column for each group of students as per rubrics based
on viva.

Comments/Suggestions about team work/leadership/inter-personal communication (if any)

………………………………………………………………………………………………
……………………………………………………………………………………………..
……………………………………………………………………………………………..
……………………………………………………………………………………………..

Any Other Comment:

……………………………………………………………………………………………
……………………………………………………………………………………………
……………………………………………………………………………………………
………………………………………………………………………………………………

Name and designation of the Faculty Member…………………………………….

Signature………………………………………………………………………………

Date:………………………..

13