Scribd
Upload
21 views4 pages

Mc5513 Mini Project Manual

Uploaded by

Arajashekar Raja
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
21 views4 pages

Mc5513 Mini Project Manual

Uploaded by

Arajashekar Raja
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/ 4

MC5513 MINI PROJECT LTPC

0 0 4 2
GUIDELINES:
Contents
1. Syllabus
2. Project committee with list of panel members
3. Guidance
4. Report Format ( as per Final Project Rules – get it from MINI-
PROJECT Manual)
5. Instructions
6. Schedule

1. SYLLABUS
 Team Project with a maximum of four in a team
 Students shall select a domain and develop an application with social relevance
 Documentation is to be based on the standards
 Evaluation pattern is like Lab examination
 Need to submit a report, presentation with demo.
 User Based Testing and feedback from the benefited society required
TOTAL: 60 PERIODS
2. PROJECT COMMITTEE
Overall Project Coordinator:
Asst. Prof. K. Khaja Mohideen, Assistant Professor

Mini-Project Guide:
Asst. Prof. XXXXXXXXXXXXXXXX, Assistant Professor

Panel Members:
1. Asst. Prof. K.Khaja Mohideen, Assistant Professor & Head
2. Asst. Prof. Afshia Nasrin, Assistant Professor
3. Asst. Prof. MLM. Mohammed Rafeek, Assistant Professor
4. Asst. Prof. Syed Younus Ahmed, Assistant Professor
5. Asst. Prof. Y. Rabik, Assistant Professor
6. Asst. Prof. F. Habib Mohammed Afzal Bijli, Assistant Professor
7. Asst. Prof. A.Shalini, Assistant Professor
8. Asst. Prof. A.Jawahar Sathik, Assistant Professor
1
9. Asst. Prof. S.Seetha Kalavani, Assistant Professor

3. GUIDANCE

MINIPROJECT DESIGN AND DEVELOPMENT GUIDELINES


1. The Mini-project is an application that should be formally initiated and should be
developed and to be implemented by the respective team.
2. The team coordination and proper communication should be promptly
maintained by the team leader.
3. The acceptance test is to be completed by appropriate norms suggested by the
panel members of the project committee.

The major steps in the Mini-project development are as follows:


Step 1: Form a team (maximum 3 per team – 10 teams & 1 team with 4 members)
- Over all – 34 Students.
Step 2: Select a domain.
Sample Probable Domain areas are:
a) On-line business initiatives Portal (legal guidance and fund raising) for
Socially, economically weaken Society
b) Free Govt Training and VAT( Value Added Training) welfare societies portal
for Socially, economically weakened Society
c) Social portal for Scholarship guidance
d) Social portal for Blood donation activities
e) Social portal for Fund Donation drives for Education for Socially,
economically weaken Society
f) Social portal Rural Health camps
g) Online legal Assistance portal such as crime, Non-crime type of legal issues
guidance, corporate legal rules guidance, etc
h) Public welfare portal for Political entry and administrative practices guidance
i) Public welfare portal for Govt Schemes and guidance
j) Social Marketing Management Portal
k) Social Networking Portal
l) Social Media Management Portal
m) welfare societies Management portal
Step 3: Develop an application with social relevance.
Step 4: Present the same (with progress or developments of your project. as per
the review schedule.)
Step 4: Prepare documentation (as per the given format) and submit within the
due date (will be given start of semester)

2
Step 5: Attend the Mock – viva voce (Probable schedule will be at end of
Semester)
Step 6: Prepare Final presentation and attend the final Viva-voce (as per the
University confirmed schedule day and time)
Note: A formal feedback should be collected from benefited society and
should be attached with the final document.

4. REPORT FORMAT ( as per Final Project Rules – get it from MINI-


PROJECT Manual)

5. INSTRUCTIONS

1. Once the Team is framed and a team leader should be identified by the
members of that team ( if needed project committee influence is to be utilized) ,
no change or drop from the team is allowed. Each team member role (such as
Documenter, System Analyst, Programmer, Tester, etc) is decided in the
team’s first FTR (Formal Technical Review) meet ( if needed project committee
influence is to be utilized).
2. Once the domain / Topic is selected, no change or drop is allowed.
3. A long size note for the Whole Team and another long size note one for each
team member should be maintained to overlook the progress of the Miniproject.
4. For every review meet, the entire team member’s Long size note (with guide
and Overall project Coordinator and HOD signature) should be submitted.
5. Pre-review evaluation and follow ups by Guide (in the previous lab(s)) and
panel members (if needed) are must for Review that follows.
6. Recommended to utilize the Saturdays for Company visits and other relevant
meets related to Mini-project.
7. Out of 10 lab sessions (4 hours) few lab sessions will be used for FTR (Formal
Technical Review) Meetings, Experts presentation, Expert’s Guidance meet.
8. Additional Lab sessions ( 3 hours) will given for Technology enhancement by
Self learning and for Reviews (Internal).

3
9. Each review evaluation is based on maximum 25 marks and in total your Final
Internal marks will be out of 100 marks.
10. Final pass /fail is based on your continuous and consistent progress
throughout the semester and each reviews performance.
11. Mock Viva-voce is compulsory for each team and make sure that each
member should given turn to present a part of the presentation content.
12. The Panel member’s decision is final in all type of evaluations.

6. SCHEDULE

1. Formal Introductory talk by HOD and Project Coordinator and Guide on


__________. (First working day)
2. First Review is on : ____________________
3. Second Review is on : __________________
4. Third Review is on: ____________________
5. Forth Review is on: ____________________
6. Final Consolidation / Presentation (before project Documentation
preparation) is on
7. Mini-Project Documentation without binding submission is on:
______________
8. Mini-project Documentation with binding submission is on:
________________
9. Mock Viva-voce is:
Day 1: ( Date: ) : - Teams : - X, X, X, X, X
Day 2: ( Date: ) : - Teams : - X, X, X X, X

Final Review ( as per the University Schedule – to be announced after some


time)

You might also like