Professional Documents
Culture Documents
SE BCS-7B Team 4 SPD V2
SE BCS-7B Team 4 SPD V2
SE BCS-7B Team 4 SPD V2
Software Project
Documentation
Version 2
Virtual Classroom
Client: FIVERIVERS
TECHNOLOGIES
Team 4
Member Name Member Roll # Primary Responsibility
M. Abdul Mateen L21-7411 Component Diagram, Risk
Report, Updated Project
Plan, Activity time sheet
Muhammad L18-2151 Use Case Diagram, Analysis
Usama Yousaf Class Diagram
Haseeb Ur L16-5405 ERD, DFD
Rehman
Moazzam Qureshi L18-1248 IV & V
Hammad Ahmed L18-1063 GUI Design
Important Note: This template has been adapted from the SRS Template by Karl E. Wiegers which is available for
download at http://www.processimpact.com/.
Virtual
Classroom
Table of Contents
Table of Contents...........................................................................................................................1
Revision History.............................................................................................................................2
Glossary..........................................................................................................................................3
The following are the list of abbreviation and acronyms used in this document:...........................3
1. Introduction..............................................................................................................................4
1.1 Product.......................................................................................................................................4
1.2 Scope..........................................................................................................................................4
1.3 Business Goals...........................................................................................................................4
1.4 Document Conventions..............................................................................................................4
1.5 References..................................................................................................................................5
2. Overall Description..................................................................................................................6
2.1 Product Features.........................................................................................................................6
2.1.1 Student Details.......................................................................................................................6
2.1.2 Faculty Details.......................................................................................................................6
2.1.3 Administrator Details.............................................................................................................6
2.2 User Classes and Characteristics................................................................................................7
2.2.1 Student...................................................................................................................................7
2.2.2 Teacher...................................................................................................................................7
2.2.3 Administrator.........................................................................................................................7
2.3 Operating Environment..............................................................................................................7
2.4 Design and Implementation Constraints.....................................................................................7
2.4.1 Hardware Constraints.............................................................................................................7
2.4.2 Business Constraints..............................................................................................................8
2.4.3 Design Constraints.................................................................................................................8
2.4.4 Product Constraints................................................................................................................8
2.5 Assumptions and Dependencies.................................................................................................8
3. Functional Requirements........................................................................................................9
4. Nonfunctional Requirements................................................................................................10
4.1 Performance Requirements.......................................................................................................10
4.2 Security Requirements..............................................................................................................10
5. Other Requirements..............................................................................................................11
6. Analysis Models......................................................................................................................12
6.1 Use Case Diagram (UCD)........................................................................................................12
6.2 Entity Relationship Diagram (ERD).........................................................................................13
6.3 Analysis Class Diagram (ACD)................................................................................................13
6.4 Data Flow Diagram (DFD).......................................................................................................14
7. Architectural Design..............................................................................................................15
7.1 Component Diagram.................................................................................................................15
8. GUI Design.............................................................................................................................16
9. Test Cases...............................................................................................................................20
10. IV & V Report........................................................................................................................21
11. Risk Report.............................................................................................................................22
12. Activity Timesheet.................................................................................................................23
13. Updated Project Plan.............................................................................................................24
13.1 Individual Screen Shot..............................................................................................................25
Important Note: This template has been adapted from the SRS Template by Karl E. Wiegers which is available for
download at http://www.processimpact.com/.
Revision History
Name(s) Date Reason(s) For Change(s) Version
Hammad Ahmed 04-10-2021 Overall Description 0.1
Haseeb ur Rehman 14-10-2021 NFRs 0.2
Abdul Mateen 15-10-2021 Introduction, Updated Project Plan 0.3
Moazam Qureshi 15-10-2021 FRs 0.4
Usama Yousaf 19-10-2021 IV&V 0.5
Mateen,Hammad, 20-10-2021 Compiling of overall Software 1.0
Haseeb,Usama, Project Document
Moazam
Mateen,Hammad, 01-11-2021 Updated SPD as suggested by Instructor 1.1
Haseeb,Usama,
Moazam
Usama Yousaf 05-11-2021 Use Case Diagram 1.2
Haseeb ur Rehman 06-11-2021 ERD , DFD 1.3
Usama Yousaf 16-11-2021 Class Diagram 1.4
Abdul Mateen 15-11-2021 Component Diagram 1.5
Hammad Ahmed 17-11-2021 GUI Design 1.6
Haseeb ur Rehman 16-11-2021 DFD level 2 1.7
Abdul Mateen 16-11-2021 Updated Project Plan, Updated Risk Report 1.8
IV&V 17-11-2021 IV&V report 1.9
M Abdul Mateen 17-11-2021 Activity Time Sheet, Compiling of SPD Ver-2 2.0
Important Note: This template has been adapted from the SRS Template by Karl E. Wiegers which is available for
download at http://www.processimpact.com/.
Glossary
The following are the list of abbreviation and acronyms used in this document:
Important Note: This template has been adapted from the SRS Template by Karl E. Wiegers which is available for
download at http://www.processimpact.com/.
1. Introduction
1.1 Product
A virtual classroom (VCR) is a digital learning environment that enables teachers and students to
interact online in real time environment. Moreover, this product is more beneficial in Corona
episode where students and teachers are barred to attend the schools / universities. VCR allows
users to communicate by making posts and comments. Virtual classrooms are meant to replicate the
experience of physical classrooms, with the added benefits of file sharing, instant feedback and
interaction, in addition to that, VCRs are ideal in distance learning situations. They are highly
customizable and are accessible to users on a variety of devices which supports browsing.
1.2 Scope
The project “Virtual Classroom” is being developed by FAST NUCES students for FIVERIVER
TECHNOLOGIES. The purpose of this project is distance learning in situations like corona or any
other pandemic. By using the VCR, teacher can more effectively communicate with whole class of
students at a time instead of addressing the individual student in personal chat. The proposed system
will have audio and video capabilities, where students and teachers can interact with each other just
like physical classroom. Moreover, following is the list of scope for this project.
Students can attend lectures, view and submit assignments, view attendance record and
comment in the classroom.
Teacher / Admin can create classroom, upload assignments, class work sheets, and other
important material.
Teacher can upload lectures and announcements, evaluate answer sheets.
Important Note: This template has been adapted from the SRS Template by Karl E. Wiegers which is available for
download at http://www.processimpact.com/.
Font Size: 12
Font Face: Times
Text: Justify
Body text in blue color represents the links
1.5 References
[ 1 ] IEEE SRS-template std 830-1998
http://cse.msu.edu/~cse870/IEEEXplore-SRS-
template.pdf
[2].Software Engineering: A Practitioner’s Approach, Roger S. Pressman, 6th Edition,
McGraw- Hill, 2005.
[3].Software Engineering, Ian Sommerville, 8th Edition, Pearson, 2007.
Important Note: This template has been adapted from the SRS Template by Karl E. Wiegers which is available for
download at http://www.processimpact.com/.
2. Overall Description
2.1 Product Features
The digital learning web environment, virtual classroom, being created is aimed at connecting
teachers and students online in real time, especially in this time of the COVID-19 pandemic.
Our virtual learning website shall provide a number of features, each is listed below:
Allow users to update their profiles.
Allow Teachers to create classes.
Allow Students to join classes.
Allow users to create a post and comment it.
Allow Teachers to upload assignments.
Show submissions to the users.
Show to-do lists to the users.
Allow users to access shared folders.
Allow users to join Google Meet.
Allow Teachers to grade the assignments.
Allow Teachers to mark attendance.
Important Note: This template has been adapted from the SRS Template by Karl E. Wiegers which is available for
download at http://www.processimpact.com/.
2.2 User Classes and Characteristics
Following are the anticipated user classes with their characteristics.
2.2.1 Student
Familiar with a computer
Have workable knowledge of a web browser
Has access to the Internet
Most important to satisfy
2.2.2 Teacher
Familiar with a computer
Have workable knowledge of a web browser
Has access to the Internet
Most important to satisfy
2.2.3 Administrator
Familiar with a computer
Have workable knowledge of a web browser
Have pretty-good knowledge of the virtual platform
Has access to the Internet
Important to satisfy
Important Note: This template has been adapted from the SRS Template by Karl E. Wiegers which is available for
download at http://www.processimpact.com/.
Almost 80% of the developers use Hard Disk as their storage medium instead of SSD. It
results in more startup time for the developing software to run and also sometimes cause
non-responsiveness in the applications.
The software will require a fast DSL Internet connection and Windows 10 or 11 to operate
to its full capacity.
Important Note: This template has been adapted from the SRS Template by Karl E. Wiegers which is available for
download at http://www.processimpact.com/.
3.1 Admin Login
Identifier UC-1
Purpose Login to the system by providing a user name and password
Priority medium
Actors Admin
Pre-conditions User is not logged in the classroom
Post-
conditions User is logged in the classroom
Typical Course of Action
S# Actor Action System Response
1 User shall open classroom
2 User shall click on login
3 Displays login interface
4 User shall enter username
5 User shall enter password
6 User is logged in the system
Alternate Course of Action
S# Actor Action System Response
1 User shall enter username
2 User shall enter password
Display Error “Invalid
3 Credentials”
3.2 Add Users
Identifier UC-2
Adding users of any type (Administrators, Instructors,
Purpose and students) to the system
Priority high
Actors Admin
Pre-conditions User is logged in the classroom
Post- User(Administrator, Instructor, and student) is added to the
conditions system
Typical Course of Action
S# Actor Action System Response
1 User shall open classroom
User shall click on Manage users
2 option
User shall click on add new
3 users
Displays Interface for adding a
4 new user
6 User shall enter new user type
6 User shall enter new user name
7 User shall assign password
New user is added to
8 the system
Alternate Course of Action
S# Actor Action System Response
1 User shall click on close button
2 Interface will be closed
3.3 Add Classes
Identifier UC-3
Adding Classes to the system and specify the name of class, the
Purpose lecturer for this class and time of the class
Priority high
Actors Admin
Pre-conditions User is logged in the classroom
Post- User(Administrator, Instructor, and student) is added to the
conditions system
Typical Course of Action
S# Actor Action System Response
1 User shall open classroom
User shall click on Manage
2 Classes option
3 User shall click on add new Class
Displays Interface for adding a
4 new class
5 User shall enter class name
6 User shall enter lecturer name
7 User shall enter time of the class
User shall save the details and
8 create class
New class is added to
9 the system
Alternate Course of Action
S# Actor Action System Response
1 User shall click on close button
2 Interface will be closed
3.4 Remove Users
Identifier UC-4
Purpose Removing Users from the system
Priority medium
Actors Admin
Pre-conditions User is logged in the classroom
Post-
conditions Required User is removed from the system
Typical Course of Action
S# Actor Action System Response
1 User shall open classroom
User shall click on Manage Users
2 option
User shall click on remove user
3 option
Displays interface for removing
4 a user
5 User shall enter username name
6 User shall click on delete user
User is removed from the
7 system
Alternate Course of Action
S# Actor Action System Response
1 User shall click on close button
2 Interface will be closed
3.5 Modify System Users
Identifier UC-5
Purpose Modifying system users
Priority medium
Actors Admin
Pre-conditions User is logged in the classroom
Post-
conditions Details of system user’s are modified
Typical Course of Action
S# Actor Action System Response
1 User shall open classroom
User shall click on Manage Users
2 option
User shall click on modify user
3 option
Displays interface for modifying
4 details of the user
5 User shall enter username name
6 Displays the profile of the User
User shall modify the required
7 user details
User shall click on modify user
8 option
User profile is modified
Alternate Course of Action
S# Actor Action System Response
1 User shall click on close button
2 Interface will be closed
3.6 Remove Classes
Identifier UC-6
Purpose Removing classes from the system
Priority high
Actors Admin
Pre-conditions User is logged in the classroom
Post-
conditions Required Class is removed from the system
Typical Course of Action
S# Actor Action System Response
1 User shall open classroom
User shall click on Manage
2 Classes option
User shall click on remove
3 Class option
Displays interface for removing
4 a user
5 User shall enter Class code
Displays the class that
6 matches the code
7 User shall click on delete class
Class is removed from the
8 system
Alternate Course of Action
S# Actor Action System Response
1 User shall click on close button
2 Interface will be closed
3.7 Modify Classes
Identifier UC-7
Purpose Modifying system classes
Priority medium
Actors Admin
Pre-conditions User is logged in the classroom
Post-
conditions Details of required class are modified
Typical Course of Action
S# Actor Action System Response
1 User shall open classroom
User shall click on Manage
2 Classes option
User shall click on modify
3 class option
Displays interface for modifying
4 details of the class
5 User shall enter class code
6 Displays the details of the class
User shall modify the required
7 class details
User shall click on modify
8 class button
9 Class details are modified
Alternate Course of Action
S# Actor Action System Response
1 User shall click on close button
2 Interface will be closed
3.8 Admin Logout
Identifier UC-8
Purpose Logout from the system
Priority low
Actors Admin
Pre-conditions User logged in the classroom
Post-
conditions User is not logged in the classroom
Typical Course of Action
S# Actor Action System Response
1 User shall click on log out
Displays Message ‘Are you sure
2 you want to log out ?’ in a
Confirmation dialogue box
3 User shall click on ‘yes’ option
User is logged out of
4 the system
Alternate Course of Action
S# Actor Action System Response
1 User shall click on ‘no’ option
Closes the Dialogue box and
2 user remains logged in.
3.9 Teacher Login
Identifier UC-9
Purpose Login to the system by providing a user name and password
Priority medium
Actors Teacher
Pre-conditions User is not logged in the classroom
Post-
conditions User is logged in the classroom
Typical Course of Action
S# Actor Action System Response
1 User shall open classroom
2 User shall click on login
3 Displays login interface
4 User shall enter username
5 User shall enter password
6 User is logged in the system
Alternate Course of Action
S# Actor Action System Response
1 User shall enter username
2 User shall enter password
Display Error “Invalid
3 Credentials”
3.10 View Class Details
Identifier UC-10
Display information about his own classes like starting time,
Purpose duration, days, and registered students
Priority high
Actors Teacher
Pre-conditions User is logged in the classroom
Post-
conditions Displays the details for the respective class
Typical Course of Action
S# Actor Action System Response
1 User shall open classroom
2 User shall click on required class
3 Displays class stream
4 User shall click on options
5 User shall click on view details
Displays information about
6 the class and registered
students
Alternate Course of Action
S# Actor Action System Response
3.11 Start lecture
Identifier UC-11
Purpose Start the lecture
Priority high
Actors Teacher
Pre-conditions User is logged in the classroom
Post-
conditions Starts the lecture session for the class
Typical Course of Action
S# Actor Action System Response
1 User shall open classroom
2 User shall click on required class
3 Displays class stream
4 User shall click on options
User shall click on start
5 lecture session
Initiates the meet session and
6 user is made the host
Alternate Course of Action
S# Actor Action System Response
1 User shall enter username
2 User shall enter password
Display Error “Invalid
3 Credentials”
3.12 Upload Assignment
Identifier UC-12
Purpose Upload Assignment
Priority high
Actors Teacher
Pre-conditions User is logged in the classroom
Post- Respective Assignment is uploaded on the
conditions class stream
Typical Course of Action
S# Actor Action System Response
1 User shall open classroom
2 User shall click on required class
3 Displays class stream
4 User shall click on options
User shall click on
5 upload assignment
Displays Interface for
6 uploading the assignment
User shall upload the required
7 document
User shall Enter deadline
8 for assignment
9 User shall click on upload button
Assignment gets uploaded on
10 the class stream
Alternate Course of Action
S# Actor Action System Response
1 User shall click on close option
Closes the interface for
2 assignment upload
3.13 End Lecture
Identifier UC-13
Purpose End the Lecture
Priority medium
Actors Teacher
Pre-conditions User is in the lecture session
Post- Lecture session is terminated and users
conditions are removed from the session
Typical Course of Action
S# Actor Action System Response
1 User shall click on options
User shall click on end
2 lecture session
Displays confirmation dialogue
box with message ‘Are you sure
3 you want to end the lecture
session’
4 User shall click on ‘yes’
5 Lecture session is terminated
Alternate Course of Action
S# Actor Action System Response
1 User shall click on ‘no’
Dialogue box closes and
2 lecture session
continues
3.14 Post on class
Identifier UC-14
Purpose Post on the class stream
Priority medium
Actors Teacher
Pre-conditions User is logged in the classroom
Post-
conditions Post is uploaded on the class stream
Typical Course of Action
S# Actor Action System Response
1 User shall open classroom
2 User shall click on required class
3 Displays class stream
4 User shall click on options
5 User shall click on create post
Displays Interface for
6 uploading the assignment
User shall upload the required
7 document
User shall Enter deadline
8 for assignment
9 User shall click on upload button
Assignment gets uploaded on
10 the class stream
Alternate Course of Action
S# Actor Action System Response
1 User shall click on close option
Closes the interface for post
2 upload
3.15 Grade Assignment
Identifier UC-15
Purpose Grade Assignment
Priority high
Actors Teacher
Pre-conditions User is logged in the classroom
Post-
conditions Post is uploaded on the class stream
Typical Course of Action
S# Actor Action System Response
1 User shall open classroom
2 User shall click on required class
3 Displays class stream
4 User shall click on options
User shall click on an
5 assignment
6 Displays assignment details
7 User shall click on submissions
Displays list of submitted work
8 by each student
User shall click on submitted
9 work
Displays details of
10 submitted work (submitted
solutions)
11 User shall click on add grade
Displays interface for adding
12 grade
13 User shall add grade and save it
Grade gets assigned to
14 the submission and stored
in database
Alternate Course of Action
S# Actor Action System Response
1 User shall click on close option
Closes the interface for post
2 upload
3.16 Student Login
Identifier UC-16
Purpose Login to the system by providing a user name and password
Priority medium
Actors Student
Pre-conditions User is not logged in the classroom
Post-
conditions User is logged in the classroom
Typical Course of Action
S# Actor Action System Response
1 User shall open classroom
2 User shall click on login
3 Displays login interface
4 User shall enter username
5 User shall enter password
6 User is logged in the system
Alternate Course of Action
S# Actor Action System Response
1 User shall enter username
2 User shall enter password
Display Error “Invalid
3 Credentials”
3.17 Post on Class stream
Identifier UC-17
Purpose Post on the class stream
Priority medium
Actors Student
Pre-conditions User is logged in the classroom
Post-
conditions Post is uploaded on the class stream
Typical Course of Action
S# Actor Action System Response
1 User shall open classroom
2 User shall click on required class
3 Displays class stream
4 User shall click on options
5 User shall click on create post
Displays Interface for
6 uploading the assignment
User shall upload the required
7 document
User shall Enter deadline
8 for assignment
9 User shall click on upload button
Assignment gets uploaded on
10 the class stream
Alternate Course of Action
S# Actor Action System Response
1 User shall click on close option
Closes the interface for post
2 upload
3.18 Join Class
Identifier UC-18
Purpose Join classes that have been registered by the instructor
Priority high
Actors Student
Pre-conditions User is logged in the classroom
Post-
conditions User is enrolled in the required class
Typical Course of Action
S# Actor Action System Response
1 User shall open classroom
2 User shall click on options
3 Displays lists of options
4 User shall click on join class
5 Asks for code of the class
6 User shall provide class code
7 User is enrolled in the class
Alternate Course of Action
S# Actor Action System Response
1 User shall provide class code
2 Display Error “Invalid Code”
3.19 Mark Attendance
Identifier UC-19
Purpose Mark attendance of a class
Priority high
Actors Teacher
Pre-conditions User is logged in the classroom
Post-
conditions Attendance of the class gets updated
Typical Course of Action
S# Actor Action System Response
1 User shall open classroom
2 User shall click on desired class
Displays class stream
User shall click on options
3 Displays lists of options
User shall click on Manage
4 attendance
Displays interface for adding
5 attendance for a class
User shall enter date and
6 click proceed
Displays list of student in the
7 class and corresponding
attendance check box
User shall mark attendance
8 of each student and save it
Attendance gets updated and
9 stored in the database
Alternate Course of Action
S# Actor Action System Response
1 User shall click on close option
Closes the interface for post
2 upload
3.20 View due Assignments
Identifier UC-20
Purpose See all due assignments
Priority Medium
Actors Student/Teacher
The student is already logged in and has enrolled and joined the
Pre-conditions
class.
Post- If there are no assignments due then an empty list is displayed
conditions with the message “Yoohoo no work left”
Typical Course of Action
S# Actor Action System Response
1 User shall open To-do list
Displays the upcoming
2 due assignments
Alternate Course of Action
S# Actor Action System Response
Requests to display
1 upcoming assignments
2 Displays “Yoohoo no work left”
Identifier UC-21
Purpose Edit Profile
Priority Medium
Actors Student/Teacher/Admin
Pre-conditions The user is already logged in
Post-
conditions Updated changes to the profile are saved in the database
Typical Course of Action
S# Actor Action System Response
1 User shall open options
2 Displays the option menu
3 User shall click on profile
Shows the details of user
4 profile
5 User shall click on edit profile
User shall update the required
6 fields
7 User shall save the changes
Changes are saved to the
8 database and profile is updated
Alternate Course of Action
S# Actor Action System Response
1 User shall click on close option
Closes the interface for post
2 upload
Virtual
Classroom
4. Nonfunctional Requirements
4.1 Performance Requirements
The web conferencing features shall require the minimum capacity of the machine to be
used for this very project:
Min. 500 MHz
256 MB of available memory
Internet access (wired or wireless)
The system shall have the software like Microsoft Excel (.XLS) and Adobe Reader
(.PDF) to utilize the reporting functionality.
The system shall ask users for program updates for compatibility with the software.
Important Note: This template has been adapted from the SRS Template by Karl E. Wiegers which is available for
download at http://www.processimpact.com/.
5. Other Requirements
The user shall comply with the state and federal law. Any violation regarding
unauthorized use of software may notify to authorities.
The software shall adapt to changes
The user shall be responsible for backup of all uploaded data in case of any
malfunctioning of system
Important Note: This template has been adapted from the SRS Template by Karl E. Wiegers which is available for
download at http://www.processimpact.com/.
6. Analysis Models
6.1 Use Case Diagram (UCD)
Important Note: This template has been adapted from the SRS Template by Karl E. Wiegers which is available for
download at http://www.processimpact.com/.
6.2 Entity Relationship Diagram (ERD)
6.3 Analysis Class Diagram (ACD)
Important Note: This template has been adapted from the SRS Template by Karl E. Wiegers which isavailable for
download at http://www.processimpact.com/.
6.4 Data Flow Diagram (DFD)
Important Note: This template has been adapted from the SRS Template by Karl E. Wiegers which isavailable for
download at http://www.processimpact.com/.
7. Architectural Design
7.1 Component Diagram
Important Note: This template has been adapted from the SRS Template by Karl E. Wiegers which is available for
download at http://www.processimpact.com/.
8. GUI Design
Important Note: This template has been adapted from the SRS Template by Karl E. Wiegers which is available for
download at http://www.processimpact.com/.
Login to your account
username
password
LOGIN
Sign out
Classes To-do List
Hammad Ahmed
@hammadahmed
Gender Male
Edit Profile
Classes To-do
Edit Profile
Username *
Save
Classes To-do Sign out
List
Assignment 1
16 Nov 2021
Due
Hammad Naveed 100 21 Nov 2021 Submission Assigned
Add comment...
Bioinformatics My Classes Worksheet Sign out
BCS-7F
Assignment 1
Due
16 Nov 2021
100 marks 21 Nov 2021 Status Assigned
Assignment 1.docx
Add comment...
Bioinformatics Classes To-do
BCS-7E
List
Bioinformatics BCS-7E
Instructor:Hammad Naveed
Join
Upcoming
Assignment 3 - Due in 2 days
Hammad Naveed
12 Nov 2021
LecLteucrteur1e4 14
Lec14-SequenceDatabaseSearching.pdf
Add comment...
Bioinformatics Classes To-do
List
BCS-7E
Make a Post
Google Meet
Post something in your class Upload File(s)
Upcoming
HammadHammad NavNaveedeed
Assignment 3 - Due in 2 days
1122 NoNov v 20220211
LecturLecture 14e 14
Lec14-SequenceDatabLec14-SequenceDatabaseSearaseSearching.pdfching.pdf
Bioinformatics Classes To-do Sign out
BCS-7E List
Assigned
Thursday, 11:00 AM
Assignment 3 18 November 2021
Missed
Thursday, 11:00 AM
Assignment 2
11 November 2021
Done
Instructors
Classmates
Amna
DanishTariq
Irfan
Faheem
Ahmad Fatima
l 2198@lhr.nu.edu.pk
1
8
2
1
9
8 l182198@lhr.nu.edu.pk
@
l
h l182198@lhr nu edu
r
.
n pk
u
.
e
d
u
.
p
k
l
1
8
Sign out
My Classes Worksheet
Bioinformatics Bioinformatics
BCS-7D BCS-7E
Hammad Naveed Hammad Naveed
Create a class
Assignment 3 - Due in 2 days Assignment 3 - Due in 2 days
Class name *
Section *
Color:
Create
Bioinformatics Sign out
BCS-7F My Classes Worksheet
Bioinformatics BCS-7F
Instructor:Hammad Naveed
Create
Upcoming
Bioinformatics My Classes Worksheet
BCS-7F
Google Meet
Task Title * Post something in your class
Upcoming
Post
Bioinformatics My Classes Worksheet
BCS-7F
Make a Post
Instructor: Hammad Naveed
Google Meet
Post something in your
Post something class
in your class
Upcoming
Task Upload File(s)
Post
Bioinformatics Classes To-do Sign out
BCS-7F List
Bioinformatics BCS-7F
Instructor:Hammad Naveed
Join
Upcoming
Assignment 1 - Due in 5 days
Hammad Naveed posted a task: Assignment 1
Open
16 Nov 2021
Bioinformatics My Classes Worksheet Sign out
BCS-7F
Bioinformatics BCS-7F
Instructor:Hammad Naveed
Create
Upcoming
Assignment 1 - Due in 5 days
You posted a task: Assignment 1
Open
16 Nov 2021
Virtual Classroom
9. Test Cases
<Write at least one test case for each scenario/course of action of every use case.
Furthermore, write one test case for each non-functional requirement.Use the following
template to document each test case.>
Identifier TC-1
Priority <Choose one from {High, Medium, Low}>
<Include use-case identifier(s) for functional
Related
requirements(s) requirement(s) and SRS section/sub-section
number(s) for other requirement(s).>
Short description …
Pre-condition(s) …
Input data …
Detailed steps …
Expected result(s) …
Post-condition(s) …
Table 1: TC-1
Important Note: This template has been adapted from the SRS Template by Karl E. Wiegers which is available for
download at http://www.processimpact.com/.
1. IV & V Report
IV & V Resource
Fix Time
S# Defect Description Origin Stage Status Hours Minutes
1 Use cases (UC-2,UC-3,UC-4,UC- Use Case Closed 0 35
5,UC-6,UC-7) were not added
1
Project Risks
1
Risks should be sorted in descending order of risk exposure.
2
Risk Exposure = Risk Impact x Risk Probability
Important Note: This template has been adapted from the SRS Template by Karl E. Wiegers which is available for
download at http://www.processimpact.com/.
12. Activity Timesheet
Time
Activity Hours Minutes
Requirements Engineering 16 0
Implementation
Testing
Deployment
Project Management 10 0
IV & V 4 30
Important Note: This template has been adapted from the SRS Template by Karl E. Wiegers which is available for
download at http://www.processimpact.com/.
13. Updated Project Plan
Important Note: This template has been adapted from the SRS Template by Karl E. Wiegers which is available for
download at http://www.processimpact.com/.
13.1 Individual Screen Shot
Important Note: This template has been adapted from the SRS Template by Karl E. Wiegers which is available for
download at http://www.processimpact.com/.
Important Note: This template has been adapted from the SRS Template by Karl E. Wiegers which is available for
download at http://www.processimpact.com/.
Project Manager
Muhammad Abdul
Mateen 21L-7411
Name Roll # Signature
Important Note: This template has been adapted from the SRS Template by Karl E. Wiegers which is available for
download at http://www.processimpact.com/.