Scribd
Upload
1 views8 pages

Software Requirement Specification

The document outlines the Software Requirement Specification (SRS) for an Attendance System at the MC Lab of the University of Barishal, emphasizing the use of the Agile Model for development. Key requirements include user authentication, real-time attendance recording, and performance assessment capabilities for the chairman. Various diagrams such as use case, data flow, activity, class, and swimlane diagrams are included to illustrate system interactions and workflows.

Uploaded by

Asad Asad
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
1 views8 pages

Software Requirement Specification

The document outlines the Software Requirement Specification (SRS) for an Attendance System at the MC Lab of the University of Barishal, emphasizing the use of the Agile Model for development. Key requirements include user authentication, real-time attendance recording, and performance assessment capabilities for the chairman. Various diagrams such as use case, data flow, activity, class, and swimlane diagrams are included to illustrate system interactions and workflows.

Uploaded by

Asad Asad
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 8

Page |1

SOFTWARE REQUIREMENT SPECIFICATION(SRS)


ON

ATTENDANCE SYSTEM OF MC LAB


Md. Asad Mondall [20CSE006]

1. SCENARIO

The Department of Computer Science & Engineering at the University of Barishal operates a
computer lab named "MC Lab." This lab serves as a facility for students to engage in academic
and research activities. Access to the lab is regulated, and the department maintains real-time
records of student attendance and behavior. Additionally, the chairman assesses student
performance based on attendance and time spent in the MC Lab.

2. THE MODEL WE CHOOSE


The Agile Model is chosen for the MC Lab system development. This model is well-suited for
projects that require flexibility and adaptability to changing requirements. Given the dynamic
nature of student needs and potential updates to lab functionalities, the Agile Model allows for
incremental development and continuous feedback.
Agile Principles:
1. User Involvement: Continuous collaboration with students and faculty for regular
feedback.
2. Iterative Development: Incremental releases for quick adaptation to changing
requirements.
3. Flexible Response to Change: Ability to incorporate new features or modifications as
needed.
4. Collaborative Approach: Regular communication among developers, users, and the
chairman for effective project management.
Application to MC Lab System:
The Agile Model will be implemented through short development cycles, known as "sprints,"
focusing on specific features or improvements. Regular meetings with stakeholders will ensure
that the system aligns with user expectations, allowing for adjustments based on real-time
feedback.
Page |2

3. REQUIREMENT ANALYSIS (Updated)


Normal Requirements:
• User Authentication: Users must be authorized to enter the MC Lab.
• Attendance System: A system to record real-time student attendance.
• Time Management: Define and manage the duration of student access to the lab.
• Permission Request: Mechanism for students to request and obtain additional time
with approval from the chairman.
Expected Requirements:
• Performance Assessment: The chairman should have the ability to analyze attendance
and time spent for performance evaluation.
• Notification System: Automated notifications for approved and denied permission
requests.
• Logging: Maintain logs of user activities and permissions for auditing purposes.
Agile Approach:
• User Stories: Develop user stories for each feature, allowing for prioritization and
iterative development.
• Sprint Planning: Break down tasks into manageable units for each sprint.
• Continuous Integration: Regularly integrate and test new features for immediate
feedback.
By adopting the Agile Model, the MC Lab system can be more responsive to evolving
requirements and user expectations, enhancing overall project adaptability and stakeholder
satisfaction.
3. REQUIREMENT ANALYSIS
Normal Requirements:
• User Authentication: Users must be authorized to enter the MC Lab.
• Attendance System: A system to record real-time student attendance.
• Time Management: Define and manage the duration of student access to the lab.
• Permission Request: Mechanism for students to request and obtain additional time with
approval from the chairman.
Expected Requirements:
Page |3

• Performance Assessment: The chairman should have the ability to analyze attendance
and time spent for performance evaluation.
• Notification System: Automated notifications for approved and denied permission
requests.
• Logging: Maintain logs of user activities and permissions for auditing purposes.
Existing Requirements:
• High-Configured PCs: Ensure the availability of high-performance computers.
• Modern Facilities: Ensure the lab is equipped with modern amenities for academic and
research purposes.
4. USE CASE DIAGRAM
Actor: Student, Admin, Chairman

The Use Case Diagram illustrates the interactions between users and the MC Lab system,
including actions such as logging in, requesting permission, and performance assessment.
Page |4

5. DATA FLOW DIAGRAM (DFD)


Zero Level DFD:

First Level DFD:


Page |5

Second Level DFD:


Page |6

The Data Flow Diagrams depict the flow of data within the MC Lab system. The zero level
provides an overview, while subsequent levels offer detailed insights into processes and
interactions.

6. ACTIVITY DIAGRAM

The Activity Diagram outlines the workflow within the MC Lab system, depicting activities such
as user authentication, attendance recording, and permission request processing.
Page |7

7. CLASS DIAGRAM

The Class Diagram represents the structure of the MC Lab system, showcasing classes like User,
Chairman, and Permission, along with their attributes and relationships.
Page |8

8. SWIMLANE DIAGRAM

The Swimlane Diagram illustrates the responsibilities of different entities (users, chairman,
system) in the MC Lab processes, providing a visual representation of the workflow and
interactions between stakeholders.

You might also like