Requirements

Wire Framing
The wire framing link of the Teacher parent interaction is :
http://lumzy.com/access/?id=EA04F91070EEA785E4619C28574A1349

The requirements of all the users, description and how they will be handled are given below:

Related Requirements:
Initiating actor: Teacher
Actor’s Goal: Make a Report
Participating Actors: System, Student
Pre-conditions: Teacher is logged in.
Success End Condition: Marks are entered and report is made
Failed End Condition: Report is not made.
Extension Points:
Flow of Events for Main Success Scenario:
Include:: Login (UC-1)

1. Actor selects Make Report option.
2. System Displays list of Sections/classes of Actor.
3. Actor selects the specific section/class.
4. System displays list of students of this specific section/class
5. Actor enter marks of students and Press OK.
6. System makes report and Notify Actor.

Alternative Path:
5A- System prompts that marks are not entered correctly or marks are not entered.
1-Step 5 again of Main Scenario

Related Requirements:
Initiating actor: Teacher
Actor’s Goal: Edit a Report
Participating Actors: System, Student
Pre-conditions: Teacher is logged in.
Success End Condition: report is edited successfully
Failed End Condition: Report is not edited correctly
Extension Points:
Flow of Events for Main Success Scenario:
Include:: Login (UC-1)

1. Actor selects Reports option.
2. System Displays list of Sections/classes of Actor.
3. Actor selects the specific section/class.
4. System displays report of this specific section/class
5. Actor edit the required entry/marks and Press OK.
6. System gives an overview of edit report to actor.
7. Actor check the entries and press Save.
8. System update the report and Notify Actor.
9. Alternative Path:
   7A- Actor check the entries and Want a change.
   1-Actor press cancel.
   2-System again open report.
   3- Actor make changes and press OK.
   4-Back to step 6 of Main Scenario.

Initiating actor: Parents
Actor’s Goal: Check report
Pre-conditions: parent has logged in.
Success End Conditions: parents check the report card.
Failed End Condition: Parent cannot check the report card.
Extension Points:
Flow of Events for Main Success Scenario:

1. System displays all the children of the user.
2. Select the child.
3. System displays the information of the student.
4. Parent selects the view report option.
5. System displays the report of the student.
   Alternative path:
   4A. User selects the cancel option.
   4B. use case ends with failed condition.

Initiating actor: student
Actor’s Goal: Mark In
Participating Actors: RFID reader, timer
Pre-conditions:
• student has the card
• System always displays the available functions at the door.
Success End Conditions: RFID reader has approved and auto-timer has started countdown.
Failed End Condition: RFID reader has not approved and timer didn’t start.
Extension Points:
Flow of Events for Main Success Scenario:

1. Student arrives at the door and selects the menu item “Mark In”.
2. Student swipes the card.
3. System (a)RfID reader approves the student. (b) System signals to the student the status like “You can enter”.
4. System signals to the timerto start the auto time countdown.
5. Student opens the door and enters the room.

Initiating actor: Student
Actor’s Goal: Mark Out
Participating Actors: RFID reader, timer
Pre-conditions:
• student has entered the room
• System always displays the available functions at the door.
Success End Conditions: RFID reader has approved and auto-timer is reset.
Failed End Condition: RFID reader has not approved and timer isn’t reset.
Extension Points:
Flow of Events for Main Success Scenario:

1. Student arrives at the door and selects the menu item “Mark out”.
2. Student swipes the card.
3. System (a)RfID reader approves the student. (b) Signals to the student the status like “You can exit”.
4. System signals to the timerto reset the time.
5. Student opens the door and exits the room.

The estimation according to their complexity, technicality and environment are give below

Unadjusted Use Case Weight:

Name of the Use Case | User Interface |No of Steps | No of Actors | Weight
------------- |--------------|------|----------------|----------------|--------------
Make a Report | Complex (GUI) | 7 | 1 (Teacher) | 10 (Average)
Edit a Report | Complex (GUI) | 10 | 1 (Teacher) | 15 (Complex)
Save Report | Complex (GUI) | 9 | 1 (Teacher) | 15 (Complex)
Mark In Simple | (No GUI) | 5 | 3 (Student ,RF-ID ,Timer) | 10 (Average)
Mark Out | Simple (No GUI) | 5 | 3 (Student ,RF-ID ,Timer) | 10 (Average)
Check Report | Complex (GUI) | 3 | 1 (Parent) | 10 (Average)
Assign Account | Complex (GUI) | 16 | 4 (Parent, Teacher, Admin, Database ) | 15 (Complex)
Unadjusted use case weight total |||| 85

Unadjusted Actor Weight:

Actor Name	Description of relevant characteristics	Complexity	Weight
Teacher	Have to handle all the work related to report making by a GUI interface	Complex	3
Parent	They will only check the report and have the lowest rights to make any change but still working with a GUI interface	Complex	3
Admin	He will be the in charge of all the accounts types and their working and record managements. All the work is done in GUI interface	Complex	3
Database	Database is another system interacting through a protocol	Simple	1
Timer	Timer to keep a check on the time limit of student entrance and exit	Simple	1
RF-ID reader	The system used to read the RFID of a student and by that it will mark the student	Simple	1
Unadjusted actor weight Total			12

UUCP = UUAW + UUCW **
= 12 + 85 = 97**

**Technical Complexity Factor: **

Technical Factor	Description	Weight Perceived	Complexity	Calculated Factor (Weight * Perceived Complexity)
T1	Distributed, web based system	2	5	2*5=10
T2	User expects good performance but nothing exceptional	1	3	1*3=3
T3	End user expects efficiency but there are no exceptional demands	1	3	1*3=3
T4	Internal processing is relatively moderate	1	4	1*4=4
T5	No Re usability required	1	0	1*0=0
T6	Ease of install is moderately important (will be installed by one of our worker)	0.5	3	0.5*3=1.5
T7	Ease of Use is important	0.5	5	0.5 *5=2.5
T8	No Portability concerns beyond a desire to keep database open	2	3	2*3=6
T9	Ease of change minimally required	1	1	1*1=1
T10	Concurrent use is required	1	4	1*4=4
T11	Security is an important concern	1	5	1*5=5
T12	Direct access of the third party (system will be used from different organizations at a time)	1	2	1*2=2
T13	A bit of training is required	1	3	1*3=3
Technical Factor Total				45

TCP = 0.6 +0.01 *45 = 1.05
** = 2 % reduction **

Environmental Complexity Factor:

Environmental Factor	Description	Weight Perceived Impact	Calculated Factor (Weight * Perceived Impact)
E1	Beginner familiarity with UML based development	1.5	3
E2	Some familiarity with application problem	0.5	3
E3	Some knowledge of object oriented approach	1	4
E4	Beginner lead analyst	0.5	1
E5	Highly Motivated	1	4
E6	Stable Requirements expected	2	5
E7	No Part time staff involved	-1	0
E8	Difficult Programming Language	-1	2
Environmental Factor Total			22.5

ECP = 1.4 -0.03 *22.5 = 0.725 = 72.5 %
= 12.5 % reduction

[previous project]
Size = 0.77 * 1.125 * 204
=176
Effort = 225 person-hrs (1 month = 25 days & per day = 3 hrs & Members = 3)
Productivity = 225/176 = 1.27 person-hrs / UCP

Size= 0.725* 1.05 * 97 = 84.026 ~ 84 UCP
Effort= 1.27 * 84 = 107.38