Detailed Project Report
Of
Attendance Management System
For
JNTU
Revision Number 1.0
Author: NSIC, Govt. of INDIA
INDEX
1. scope of work
2. MileStones and Estimates
3. PROJECT PRICING ESTIMATE/COST FOR SERVICES OUTLINED
4. technical architecture and technology proposed
5. execution team
6. project Development Approach
Scope of work for the current Project Attendance Management System includes meet the JNTU Board members, Requirements gathering, analyze the requirements and prepare Functional/Technical Requirements Specification documents.
1.scope of work
1 / Masters Registration1.1 / College Registration
1.2 / Professor Registration
1.3 / Student Registration
1.4 / Biometric Device Registration
2 / Central Administration
2.1 / College Registration Approvals
2.2 / Creation of College Level Administrators
2.3 / Alert Centre for common and specific alerts to the colleges
2.4 / Daily monitoring of college level activities
3 / College Level Administration
3.1 / Student Enrolment
3.2 / Biometric device and student mapping
3.3 / Department level authorization
3.4 / Daily monitoring of class level activities.
3.5 / Year end student class upgradation
3.6 / Mapping biometric device for labs and any other special events
4 / Biometric Data Processing
4.1 / Defining the device specific student data
4.2 / Capturing Biometric Data
4.3 / Data Synch up with central server
5 / Rules Engine
5.1 / Defining the attendance rules like per class/lab/day/in & out etc
5.2 / Offline data synch-up with central server following adequate approvals
5.3 / Data storage limits and history requirement for active and archival data maintenance
5.4 / Hall ticket issue rules
5.5 / De-duplication rules
6 / Reporting
6.1 / Professor Attendance Report
6.2 / Student Attendance Report
6.3 / Overall college level summaries against different dimensions like students, classes, professors etc
6.4 / Cross college metrics in adhering to the rules of the attendance system and its associated business flows
6.5 / Ranking of the colleges as per the rules defined
6.6 / Historical data reporting for auditing
7 / Decision Support System
7.1 / Identify and alert the mismatch records as per rules defined
7.2 / Decline the particles or hall ticket
2. MileStones and Estimates
S.NO / Functional Point / Specifications Preparation / Effort(Days) / Total Effort
(Days)
Functional / Technical / Functional / Technical
1 / Masters Registration / Week1 / Week2 / 2 / 2 / 4
1.1 / College Registration / 0.25 / 0.25
1.2 / Professor Registration / 0.25 / 0.25
1.3 / Student Registration / 0.25 / 0.25
1.4 / Biometric Device Registration / 0.25 / 0.25
2 / Central Administration / Week1 / Week2 / 2 / 2 / 4
2.1 / College Registration Approvals / 0.5 / 0.5
2.2 / Creation of College Level Administrators / 0.5 / 0.5
2.3 / Alert Centre for common and specific alerts to the colleges / 0.5 / 0.5
2.4 / Daily monitoring of college level activities / 0.5 / 0.5
3 / College Level Administration / Week1 / Week2 / 3.5 / 3 / 6.5
3.1 / Student Enrolment / 1 / 0.5
3.2 / Biometric device and student mapping / 0.5 / 0.5
3.3 / Department level authorization / 0.5 / 0.5
3.4 / Daily monitoring of class level activities. / 0.5 / 0.5
3.5 / Year end student class upgradation / 0.5 / 0.5
3.6 / Mapping biometric device for labs and any other special events / 0.5 / 0.5
4 / Biometric Data Processing / Week2 / Week3 / 1.5 / 1.5 / 3
4.1 / Defining the device specific student data / 0.5 / 0.5
4.2 / Capturing Biometric Data / 0.5 / 0.5
4.3 / Data Synch up with central server / 0.5 / 0.5
5 / Rules Engine / Week2 / Week3 / 4 / 2 / 6
5.1 / Defining the attendance rules like per class/lab/day/in & out etc / 0.5 / 0.5
5.2 / Offline data synch-up with central server following adequate approvals / 1 / 0.5
5.3 / Data storage limits and history requirement for active and archival data maintenance / 1 / 0.5
5.4 / Hall ticket issue rules / 1 / 0.5
5.5 / De-duplication rules / 0.5 / 0.5
6 / Reporting / Week2 / Week3 / 3 / 3 / 6
6.1 / Professor Attendance Report / 0.5 / 0.5
6.2 / Student Attendance Report / 0.5 / 0.5
6.3 / Overall college level summaries against different dimensions like students, classes, professors etc / 0.5 / 0.5
6.4 / Cross college metrics in adhering to the rules of the attendance system and its associated business flows / 0.5 / 0.5
6.5 / Ranking of the colleges as per the rules defined / 0.5 / 0.5
6.6 / Historical data reporting for auditing / 0.5 / 0.5
7 / Decision Support System / Week3 / Week3 / 1 / 1 / 2
7.1 / Identify and alert the mismatch records as per rules defined / 0.5 / 0.5
7.2 / Decline the particles or hall ticket / 0.5 / 0.5
Total / 17 / 14.5 / 31.5
3. PROJECT PRICING ESTIMATE/COST FOR SERVICES OUTLINED
S.NO / Functional Point / Specifications Preparation / Effort(Days) / Total Effort
(Days) / Cost (Rs)
Functional / Technical / Functional / Technical
1 / Masters Registration / Week1 / Week2 / 2 / 2 / 4 / 52800
1.1 / College Registration / 0.25 / 0.25
1.2 / Professor Registration / 0.25 / 0.25
1.3 / Student Registration / 0.25 / 0.25
1.4 / Biometric Device Registration / 0.25 / 0.25
2 / Central Administration / Week1 / Week2 / 2 / 2 / 4 / 52800
2.1 / College Registration Approvals / 0.5 / 0.5
2.2 / Creation of College Level Administrators / 0.5 / 0.5
2.3 / Alert Centre for common and specific alerts to the colleges / 0.5 / 0.5
2.4 / Daily monitoring of college level activities / 0.5 / 0.5
3 / College Level Administration / Week1 / Week2 / 3.5 / 3 / 6.5 / 85800
3.1 / Student Enrolment / 1 / 0.5
3.2 / Biometric device and student mapping / 0.5 / 0.5
3.3 / Department level authorization / 0.5 / 0.5
3.4 / Daily monitoring of class level activities. / 0.5 / 0.5
3.5 / Year end student class upgradation / 0.5 / 0.5
3.6 / Mapping biometric device for labs and any other special events / 0.5 / 0.5
4 / Biometric Data Processing / Week2 / Week3 / 1.5 / 1.5 / 3 / 39600
4.1 / Defining the device specific student data / 0.5 / 0.5
4.2 / Capturing Biometric Data / 0.5 / 0.5
4.3 / Data Synch up with central server / 0.5 / 0.5
5 / Rules Engine / Week2 / Week3 / 4 / 2 / 6 / 79200
5.1 / Defining the attendance rules like per class/lab/day/in & out etc / 0.5 / 0.5
5.2 / Offline data synch-up with central server following adequate approvals / 1 / 0.5
5.3 / Data storage limits and history requirement for active and archival data maintenance / 1 / 0.5
5.4 / Hall ticket issue rules / 1 / 0.5
5.5 / De-duplication rules / 0.5 / 0.5
6 / Reporting / Week2 / Week3 / 3 / 3 / 6 / 79200
6.1 / Professor Attendance Report / 0.5 / 0.5
6.2 / Student Attendance Report / 0.5 / 0.5
6.3 / Overall college level summaries against different dimensions like students, classes, professors etc / 0.5 / 0.5
6.4 / Cross college metrics in adhering to the rules of the attendance system and its associated business flows / 0.5 / 0.5
6.5 / Ranking of the colleges as per the rules defined / 0.5 / 0.5
6.6 / Historical data reporting for auditing / 0.5 / 0.5
7 / Decision Support System / Week3 / Week3 / 1 / 1 / 2 / 26400
7.1 / Identify and alert the mismatch records as per rules defined / 0.5 / 0.5
7.2 / Decline the particles or hall ticket / 0.5 / 0.5
Total / 17 / 14.5 / 31.5 / 415800
4. technical architecture and technology proposed
Technology / Version / DescriptionJava / 1.8 / Platform
Spring Framework / 4.2.0 / Application framework
Spring Security / 4.2.0 / Security
Hibernate / 5.0 / Persistence
Dozer Bean Mapping / 5.5.1 / Generic Mapping and Type conversion
EHCache / 3.0 / Data Caching
Quartz / 1.6 / Schedular
Pentaho / 5.2 / Reporting
Jasypt / 1.9.2 / Data Encryption
joda-time / 2.5 / Standard date and time library
jUnit (Not part of deployment) / 4.11 / Unit Testing
Angular JS / 1.5 / UI Library
c3p0 / 0.9.1.2 / Connection Pooling
5. execution team
Below Team members will directly interact with the JNTU board members, takes inputs from JNTU members and prepares the Functional and Technical requirements documents.
- Mr. Suresh Kavili, Project Management, Project Manager
[Education: Master Of Computer Applications (MCA), Experience: 15+ Years of experience with Apache, Linux, Windows, HTML5, CSS3, JQuery, Bootstrap, PHP, WordPress, MySQL and .Net technology sets]
- Mr. Ganesh, Development, Sr. Software Developer
[Education: B.Tech (IT), Experience: 5.7 years of experience in analysis, design and development using technologies like .NET, MVC, SQL, Entity Frame work, Java script and Jquery.]
- Mr. Mahendar Edla, Design, Sr. Software Designer,
[Education: B.Com (Computer Science), Experience: 4+ Years of experience with Apache, Linux, HTML5, CSS3, JQuery and Bootstrap technology set]
- Mr. Durga Rao D, Testing, Sr. Software Test Engineer
[Education: M.Sc. (Computer Science), Years of experience: 6+ Years in Manual & Automation Testing Tools]
Team below will review and approve the Functional and Technical requirements documents prepared by above team members, without interactingdirectly with the JNTU board members.
- Mr. RamaChandra Rao Sunkara, Founder & CEO
[Education:Bachelor’s degree in Electrical and Electronics Engineering and MBA in Technology Management, Experience:He is extremely well versed in not only the technologies which exist today, but the complex business processes which comprise the IT services industry. He is directly involved in all aspects of the business, Prior to starting of company he is working as a high level technical consultant at various leading technology companies, including Intel and Hewlett Packard.]
- Mr. Krishna Mohan, CTO
[Education:Master of Technology, Experience: 20+ years of Information Technology experience, helping companies from startups to Fortune50 on various technology projects. He is Responsible for the overall technical direction and processes for the organization and has multiple certifications including Project Management.]
- Mr. Srinivas Paruchuri, CTO
[Education: Master of Technology, Experience: 20+ years of Information Technology experience.]
6. project Development Approach
Our Team project manager and developers communicate with the JNTU Board members and gathers requirements of the proposed system.
After requirements gathering, our Team along with the Business Analyst starts preparing the software requirements document, which covers both the business environment’s current situation and the desired objective of the proposed system.
The functional specification is further development of the software requirements document and also contains the technical details for implementation. This precise, factual requirements description ensures a systematic and successful development process.
The SOW is prepared at the project’s start. It contains all relevant information on the project workflow:
- A list of documents that serve as the basis for project implementation
- Function and area of activity for all project team members (customer and Specific-Group)
- Regulates communication processes (who communicates how with whom)
- Description of the infrastructure (hardware & software, access to the customer’s systems, if required)
- Description of project risks
- Optional: a schedule for project meetings
- Overview of the deadlines (milestones, etc.)
- Overview of the quality characteristics
- Timetable for the delivery of releases
- Description of handling change requests
- Criteria for software’s use in production
- Definition of the approval process
We look forward to receive the positive advice and working with you.
NSIC
Detailed Project Report of Attendance Management System for JNTU Page 1 of 10