0% found this document useful (0 votes)
2 views2 pages

SPMS_Assignment

Uploaded by

mamoon
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
0% found this document useful (0 votes)
2 views2 pages

SPMS_Assignment

Uploaded by

mamoon
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
You are on page 1/ 2

Student Performance Management System (SPMS) Assignment

Assignment: Requirements Modeling (CLO3) and Requirements Engineering


(CLO4)

Question 01: Requirements Modeling (CLO3)

Part A: Modeling Tasks

Context-Level DFD
The context-level DFD represents the interaction between SPMS and external entities like
students, teachers, and administrators. It captures key data flows, such as grade entry,
performance reports, feedback, and analytics.

Level 1 DFD
The Level 1 DFD breaks down the system into subsystems such as:

 1. Grade Management: Input, update, and store grades.


 2. Attendance Tracking: Record and view attendance data.
 3. Performance Analytics: Generate performance reports and trends.

Swimlane Diagram
The Swimlane Diagram includes actors like Student, Teacher, and Administrator, illustrating
their roles in processes like login, entering grades, viewing analytics, and providing
feedback.

State-Transition Diagram
This diagram outlines the transitions between states, such as Logged Out, Logged In,
Viewing Dashboard, and Viewing Reports. For example, the system transitions from 'Logged
Out' to 'Logged In' upon a successful login.

State Table
Current State Event Next State Action
Logged Out Login Attempt Logged In Show Dashboard
Logged In Logout Logged Out Clear Session
Logged In View Report Viewing Reports Display Report

Dialog Map
The Dialog Map represents the navigation flow between key screens such as Registration,
Login, Dashboard, Grade Entry, and Report Viewing. For example:

 • Login → Dashboard
 • Dashboard → Performance Report

Part B: Requirements Engineering for Agile Methodologies (CLO4)


User Stories
 • As a teacher, I want to upload student grades so that I can track their progress.
 • As a student, I want to view my performance trends so that I can identify areas of
improvement.
 • As an administrator, I want to generate class performance reports so that I can identify
overall trends.
 • As a teacher, I want to update attendance records so that I can maintain accurate
tracking.
 • As a student, I want to receive feedback on my assignments so that I can improve my
academic performance.

Collaborative Requirements Engineering


During sprint reviews, the team will:

1. 1. Present prototypes and completed features to stakeholders.


2. 2. Gather feedback through discussion or surveys.
3. 3. Prioritize changes or refinements in the product backlog for the next sprint.
4. 4. Collaborate with teachers and students to validate system usability and efficiency.

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy