Computing Information System - Research Paper Example

Table of Contents Table of Contents 2 4 Introduction 4 Use Cases 5 Use Case attendance] 5 Introduction 5 Main actors 5 Main operations 5 Success criteria 5 Failure Criteria 6 Diagram 6 Introduction 6 Main actors 7 Main operations 7 Success criteria 7 Failure Criteria 7 Diagram 8 Use Case 3 [Report Generation] 9 Introduction 9 Main actors 9 Main operations 9 Success criteria 9 Failure Criteria 10 Diagram 10 Use Case 4 [Add new Functionalities] 11 Introduction 11 Main actors 11 Main operations 11 Success criteria 11 Failure Criteria 11 Diagram 12 Use Case 5 [Log IN] 12 Introduction 12 Main actors 12 Main operations 13 Success criteria 13 Failure Criteria 13 Diagram 14 Class diagrams 15 Sequence diagram 16 Conclusion 24 Bibliography 24 Abstract This paper presents the detailed system design for the digital student attendance system. This system is an automated system that provides the better and enhanced facility regarding the processing and ministering of the student’s attendance. This system is named as eSAS or electronic Student Attendance System. This paper covers the new electronic Student Attendance System’s use cases, system class model and sequence diagrams. Introduction The utilization of the information technology in every field of life is emerging day by day and it has transformed the working and handling of systems into a more manageable structures. This emergence of technology has inspired all aspects and areas of life. The system I am going to discuss is as well a better depiction of information technology implementation into different living and working sectors. This system will be an automated “Student Attendance System”. This system will provide the better facility regarding the handling, management and monitoring of Student Attendance. This report is aimed at presenting the system design model. Here I will discuss and elaborate the Student Attendance System’s working design. This will include the UML based system design diagrams those are a standards system design model. Use Cases Use Case 1 [Student attendance] Introduction This use case is about the student attendance. This use case describes the system response against the student attendance processing. Here user will insert his card in the special optical mark reader units. After the card reorganization system will mark the attendance of the student in the database. Main actors Primary actors Student Secondary actors Non Main operations Here below given the sequence of main operation system will be performed: Insert card into special optical mark reader unit Press attendance button Attendance conformation lights on Or Attendance failed Retry Exit Success criteria If student inserts a valid card and special optical mark reader units recognize the card in this case the attendance will be marked in the system. Failure Criteria In case of wrong card insertion into special optical mark reader units system will response negatively. Diagram Use Case 2 [Record Analysis] Introduction This use case is about the student attendance record analysis. This use case describes the system response against the student attendance record analysis and processing. After the specified period of time the teacher or any administrator staff will open the student record and analyze the student performance. Main actors Primary actors Administrative staff Teachers Head of department Secondary actors Non Main operations Here below given the sequence of main operation system will perform: Log in to system Log in conformation Login failed Retry Insert student no. Retrieve record Analyze performance Generate Report Exit Success criteria If student number is valid then system will retrieve the record and shows the student attendance data. Failure Criteria In case of wrong student identity number or log failure system will response negatively. Diagram Figure 2- Use Case 2 [Record Analysis] Use Case 3 [Report Generation] Introduction This use case is about the student attendance record report generation. This use case describes the system response against the student attendance record report generation that will be about some specified period of time. Main actors Primary actors Administrative staff Teachers Head of department Secondary actors Non Main operations Here is the sequence of main operation system that will be performed: Log in to system Log in conformation Login failed Retry Insert student no. Retrieve record Assign specific time for reporting Generate Report Exit Success criteria If student number is valid then system will retrieve the record and shows the student attendance data. Then user will inert the reporting dates range. After that system will present the report of specific student or class. Failure Criteria In case of wrong student identity number or log failure system will response negatively. Diagram Figure 3- Use Case 3 [Report Generation] Use Case 4 [Add new Functionalities] Introduction This use case is about the student attendance system adding new functionalities. In this use case I will describe the main working of system against the addition of new working facility and functionalities. Main actors Primary actors Administrative staff Teachers Head of department Secondary actors Non Main operations Here below given the sequence of main operation system will perform: Log in to system Log in conformation Login failed Retry Add new Functionalities Access performance Check for errors Resolve problem Exit Success criteria In case of better system performance against new addition of functionalities Failure Criteria In case of log failure system will response negatively. Diagram Figure 4- Use Case 4 [Add new Functionalities] Use Case 5 [Log IN] Introduction This use case is about the student attendance system log in for the implementation of Better security environment. Main actors Primary actors Administrative staff Teachers Head of department Secondary actors Non Main operations Here below given the sequence of main operation system will perform: Log in to system Log in conformation Login failed Retry Perform functionalities Exit Success criteria In case of correct system password and user name system will allow the user to log in. Failure Criteria In case of log failure system will response negatively. Diagram Figure 5- Use Case 5 [Log IN] Class diagrams Sequence diagram Figure 7- Sequence Diagram 1 Figure 8- Sequence Diagram 2 Figure 9- Sequence Diagram 3 Figure 10- Sequence Diagram 4 Conclusion In this report I have presented a detailed system design and modeling of the eSAS or electronic Student Attendance System. I have presented the UML based system design that includes the system use case diagrams, system class diagram and working sequence diagrams. I have outlined the main system working in a better way so that implementation of the system becomes easier. Better system design always guaranty better system working and development. I hope that this system will offer better working through enhanced system design. Bibliography 1. Alavi. 1984, An Assessment of the Prototyping Approach to Information System Development. Communications of the ACM, (p. 27). 2. Carcone, P. 2008, Information Technology System Implementation. Retrieved 15 07, 2009, from Online Magzine and Writers Network: http://www.suite101.com 3. Enterprise resource planning. 2009, Retrieved 15 07, 2009, from Wikipedia, free encyclopedia: http://en.wikipedia.org 4. Field, M., & Keller, L. 2007, Project Management . Thomson Learning . 5. Hofmeister, C., Nord, L. R., & Soni, A. 1999, Describing software architecture with UML. in Proceedings of the TC2 1st Working IFIP Conference on Software Architecture (WICSA1), (pp. 145-159). San Antonio, TX, USA. 6. Jawadekar, W. S. 2004, Software Engineering: Principles and Practice. New York: McGraw Hill. 7. Laudon, K. C., & Laudon, J. P. 2006, Management Information Systems: Managing the Digital Firm--9th Ed. Prentice Hall . 8. Laudon, K. C., & Laudon, J. P. 1999, Management Information Systems, Sixth Edition. New Jersey: Prentice Hall . 9. Monk, E., & Wagner, B. 2009, Concepts in Enterprise Resource Planning, 3rd.ed. Boston: Course Technology Cengage Learning. 10. Nagen N. Nagarur, T.-s. H. 1994, A Computer-based Inventory Management System for Spare Parts. Industrial Management & Data Systems , 22-28. 11. Pressman, R. S. 2001, Software Engineering: A Practicioners Approach, 5th Edition. London: McGraw Hill. 12. Sage, P., Andrew, & & Palmer, J. D. 1990, Software Systems Engineering. New York: John Wiley & Sons. 13. Sock Hwa Chung, C. A. 2000, ERP adoption: a technological evolution approach. International Journal of Agile Management Systems , 1465-4652. 14. Sommerville, I. 2004, Software Engineering, 7th Edition,. New York: Pearson Education (Addison Wesley). 15. Tecnodiscap, G. 2004, User Modelling in Ambient Intelligence for Elderly and Disabled People. Retrieved 15 07, 2009, from Glyndŵr University: http://www.newi.ac.uk/groutv/papers/umaiedp.pdf Read More