Operating System : Windows
Software : Visual Studio 2012
Data Base : SQL Server Management Studio
Processor : Intel Pentium-IV
Speed : 1.1GHz
RAM : 1GB
Hard Disk : 50GB
General : Key Board, Monitor, Mouse
• Efficient database functionality
• Time efficient
Efficient Data Storage
• The data collected must be stored in a proper manner that cannot be modified.
• The integrity of data must be maintained.
• In case of a large number of users, it must be properly maintained
• The software must be ON consistently
• Without having to scan the card no one should be allowed to use the system
Functional requirements include:
• Descriptions of data to be entered into the system
• Descriptions of operations performed by each screen
• Descriptions of work-flows performed by the system
• Descriptions of system reports or other outputs
• Who can enter the data into the system
• How the system meets applicable regulatory requirements
The functional specification is designed to be read by a general audience. Readers should understand the system, but no particular technical knowledge should be required to understand the document.
Examples of Functional Requirements
Functional requirements should include functions performed by specific screens, outlines of work-flows performed by the system and other business or compliance requirements the system must meet.
• Field accepts both numeric and string type data entry
• Field only accepts dates before the current date
• Data must be entered before a request is approved
• Clicking the approve button moves the request to the approval workflow
• All personnel using the system will be trained according to internal training strategies
• The database will have a functional audit trail
• The system will limit access to authorized users
• Member of the Data Entry group can enter requests but not approve or delete requests
• Members of the Managers group can enter or approve a request, but not delete requests
• Members of the Administrators group cannot enter or approve requests but can delete requests
• The functional specification describes what the system must do; how the system does it is described in the Design Specification.
If a user requirement specification is written, all requirements outlined in the user requirement specification should be addressed in the functional requirements.
Non Functional Requirements
All the other requirements which do not form a part of the above specification are categorized as Non-Functional Requirements. A system may be required to present the user with a display of the number of records in a database. This is a functional requirement. How up-to-date this number needs to be is a non-functional requirement. If the number needs to be updated in real time, the system architects must ensure that the system is capable of updating the displayed record count within an acceptably short interval of the number of records changing.
• Configuration Management
• Disaster Recovery
• Efficiency (resource consumption for given load)
• Effectiveness (resulting performance in relation to effort)
• Extensibility (adding features, and carry-forward of customizations at next major version upgrade)
• Failure Management
• Quality (e.g. Faults Discovered, Faults Delivered, Fault Removal Efficacy)
• Resource constraints (processor speed, memory, disk space, network bandwidth etc.)
• Response time
• Scalability (horizontal, vertical)
• Software, tools, standards etc.
This system has been successful in providing an easy way to take attendance in colleges. It has provided the necessary interfaces for configuring the attendance. This system can be implemented in any of the present day websites by embedding the necessary code. However, this system would definitely be helpful for the institutions, which has more care for their student’s future.
In the enhanced version of this proposed work, energy saving concepts can also be incorporated to manage the particular classroom intelligently. Mobile application software can be developed in order to track the student using GPS (Global Positioning System) in case of the absence within the institution premises.
Arora, R., Balda, S. Choudhary, P., and Mooli, P. (2014) “Automated attendance system for Guru Nanak institutions.”
Lim, T., Mansor, M., and Sim, S. (2009) “Rfid based attendance system,” in Industrial Electronics ; Applications, 2009. ISIEA 2009. IEEE Symposium on, vol. 2. IEEE, 2009, pp. 778-782.
Mashhood, S (2014) “A Conceptual Model for Automated Marking System Using Facial Recognition” 978-1-4799-5421-6/14 2014 IEEE
Raghu, C. V., and Mohamed, B. K. (2012) “Fingerprint attendance system for classroom needs,” in India Conference (INDICON), 2012 Annual IEEE. IEEE, 201