Scribd
Upload
5 views3 pages

Requirements Engineering Mini Project

The document outlines a mini project on Requirements Engineering for an Online Student Attendance Management System, detailing the systematic process of identifying and managing stakeholder needs. It includes stakeholder identification, goals for automation, requirements gathering techniques, and use cases for faculty and students. The project also covers requirements modeling, analysis, and validation, demonstrating the complete Requirements Engineering process in a software context.

Uploaded by

manojmj0501
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
5 views3 pages

Requirements Engineering Mini Project

The document outlines a mini project on Requirements Engineering for an Online Student Attendance Management System, detailing the systematic process of identifying and managing stakeholder needs. It includes stakeholder identification, goals for automation, requirements gathering techniques, and use cases for faculty and students. The project also covers requirements modeling, analysis, and validation, demonstrating the complete Requirements Engineering process in a software context.

Uploaded by

manojmj0501
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

Mini Project on Requirements Engineering

Project Title: Online Student Attendance Management System


Course: Software Engineering
Prepared For: Academic Submission

1. Understanding Requirements

1.1 Requirements Engineering


Requirements Engineering is the systematic process of identifying, documenting,
analyzing, validating, and managing the needs and constraints of stakeholders for a
software system.

1.2 Establishing the Groundwork


Stakeholders Identified:
- Students
- Faculty
- Administrator
- Institution Management

Goals:
- Automate attendance tracking
- Reduce manual errors
- Provide real-time attendance reports

1.3 Requirements Gathering


Techniques Used:
- Interviews with faculty
- Survey of students
- Observation of current manual process

Key Requirements Collected:


- Faculty should mark attendance digitally
- Students should view attendance percentage
- Admin should generate reports

1.4 Developing Use Cases


Use Case 1: Mark Attendance
Actor: Faculty
Description: Faculty logs in, selects class, marks attendance, and saves.

Use Case 2: View Attendance


Actor: Student
Description: Student logs in and checks attendance percentage.

1.5 Building the Analysis Model


The analysis model includes:
- Use Case Diagram
- Class Diagram
- Data Flow Diagram
- State Diagram

1.6 Negotiating Requirements


Some faculty requested biometric integration. Due to budget constraints, the initial
version will use manual digital entry. Biometric feature is planned for future release.

1.7 Requirements Monitoring


Changes will be tracked using a version-controlled SRS document. Regular stakeholder
meetings will review requirement updates.

1.8 Validating Requirements


Requirements were validated through stakeholder review meetings and prototype
demonstrations.

2. Requirements Modelling

2.1 Requirements Analysis


Functional Requirements:
- User login and authentication
- Mark attendance
- View attendance reports

Non-Functional Requirements:
- System should respond within 3 seconds
- Secure login with encryption
- System availability of 99%

2.2 Scenario-Based Modeling


Scenario: A faculty member logs in, selects the subject, marks attendance for students,
and submits the record. The system stores the data and updates attendance percentage.
2.3 Class-Based Modeling
Main Classes:
- Student (StudentID, Name, AttendancePercentage)
- Faculty (FacultyID, Name, Subject)
- Attendance (Date, Status)
- Admin (AdminID, Role)

2.4 Functional Modeling


Data Flow:
Faculty Input → Attendance Processing → Database Storage → Report Generation →
Student/Admin Output

2.5 Behavioural Modeling


State Diagram (Student Attendance):
Initial State → Present/Absent Marked → Attendance Updated → Report Generated

3. Conclusion
This project demonstrates the complete Requirements Engineering process including
gathering, analysis, modeling, validation, and monitoring using a simple academic system
example.

You might also like