SOFTWARE REQUIREMENT SPECIFICATION

ASSIGNMENT SUBMISSION SYSTEM IIBIT, ADELAIDE NANG TRI TRAN, RAJAT SHARMA, SABRINDER KAUR, GHAJAR AMIR NEZAMI PAYMAN

REPORT

Software Requirement Specification

EXECUTIVE SUMMARY
This Software Requirements Specification paper is written by the NRSPs group for the web-based assignment submission system which is being developed for IIBIT Adelaide. The main aim of this project is to build an online submission system for assignment handling system for the entire purposed user including student, lecturer, admin and coordinator. This project is aimed at downloading and uploading online assignments for students and lecturer, with each assignment should have information about the instructions, description, deadline, and submission details. The required deliverables are Login System (with three types of users: Admin, staff and students). We do this project through 5 steps of Systems Development Life Cycle: Project Planning phase, Analysis phase, Design phase, Implementation phase, and Support phase. Time needed for this project is nearly 3 months (from the mid of July to beginning of October); besides, the allocated budget for this project is $6000.

Version History:
Date 23/08/2012 24/08/2012 Person Sabrinder Dhaliwal Payman Version 1.1 1.2 Description Create SRS Functional and nonFunctional equirement paper Compile all members Part and Update PMP Use case model, Acivity diagram and ER Diagram, Data flow diagram and data dictionary Update summary and Finalized Document

24/08/2012

Rajat Sharma

1.3

27/08/2012

Rajat Sharma, Nang

1.4

31/08/2012

Nang/Payman / Rajat 1.5 / Sabrinder

Table of Contents
EXECUTIVE SUMMARY ............................................................................................................. 2 Version History ........................................................................................................................... 3 INTRODUCTION ........................................................................................................................... 6 Project name ................................................................................................................................ 6 Project description ....................................................................................................................... 6 Objectives .................................................................................................................................... 6 Acceptance criteria ...................................................................................................................... 6 Sponsors name ........................................................................................................................... 7 Project manager and team details ................................................................................................ 7 Definitions ................................................................................................................................... 8 Overview of the Proposed System .................................................................................................. 9 Description .................................................................................................................................. 9 Requirements ................................................................................................................................. 10 System Context Diagram........................................................................................................... 10 ................................................................................................................................................... 11 Use case Scenario ...................................................................................................................... 12 Use case Diagram for Student and Lecturer .......................................................................... 13 Use case model for Admin .................................................................................................... 14 Use case model for coordinator ............................................................................................. 15 High level storyboards ........................................................................................................... 16 Database requirements............................................................................................................... 17 Activity Diagram ....................................................................................................................... 17 Activity diagram for students ................................................................................................ 17 Activity diagram for lecturer ................................................................................................. 19 Data Flow Diagram (DFD) ........................................................................................................ 20 Data Flow Diagram (System Layout) .................................................................................... 20 ............................................................................................................................................... 20 User Interface (GUI) ................................................................................................................. 21 System Layout1 ..................................................................................................................... 21 System Layout2 ..................................................................................................................... 21 System Layout3 ..................................................................................................................... 22

5
System Layout4 ..................................................................................................................... 22 System Layout5 ..................................................................................................................... 23 System Layout6 ..................................................................................................................... 23 System Layout7 ..................................................................................................................... 24 Data Dictionary ......................................................................................................................... 24 Entity-Relationship Diagram ..................................................................................................... 26 Functional Requirements ........................................................................................................... 26 Non Functional Requirements ................................................................................................... 28 Approvals ...................................................................................................................................... 28 References ................................................................................................................................. 30

INTRODUCTION
Project name
Assignment Submission System (ASS)

Project description
The purpose of this Project is to develop an assignment submission system for IIBIT, Adelaide which will include many functions for submit the assignments online. Before that institute was using old paper based system to manage the assignments but the paper based system is so old and with some disadvantages that are unacceptable in this technology age. For example the students do not know if an assignment has been received to the tutor or not. Second big issue is tutor might lose paper assignment, and a student may not have photocopied their work as advised. So the university realize to modernization it, so they want to build a web based base system for their student so that student can able to submit their assignment online even lecturer can mark their assignment online, grade them and student should able to check their grade. This will provide enhanced student feedback and administrative cost savings across the University. The budget for this project is $6000 and allocated time is within 3 months. This is a webapplication therefore it can run on popular browsers like Internet Explorer, Firefox, Chrome, Safari, and Opera.

Objectives
Provide an electronic assignment handling solution for university.

Provide robust administrative tools for the creation, modification, marking and moderation of assignments.

Acceptance criteria
We used unified process methodology because we found this methodology best suited for us because of time shorten and quick development. We worked on VB.net frame to build the system because we are good in VB.net. VB.net is powerful tool, flexible, simplified deployment, and full object oriented constructs.

Sponsors name
Shenika Chabraal (Managing director of IIBIT, Adelaide).

Project manager and team details

Role Sponsor Project Manager Name Shenika Chabraal Nang Tri Trang Position Sponsor/ Consultant Project Manager/ web developer Sponsor IT Specialists IT Specialists IT Specialists

Stakeholder Team Member Team Member Team Member

IIBIT Rajat Sharma Sabrinder Kaur GHAJAR AMIR NEZAMI Payman

Definitions
Terms SRS Definitions Software Requirements Specification

WBS ER CRM DFD Scope

Work breakdown Structure Entity Relational Diagram Customer relationship management Data Flow Diagram All the work involved in creating this booking system and the processes used to create them. Software development life cycle

SDLC

Client Sign off

Please see on page 29.

Overview of the Proposed System

Our system will interact with University of Ballarat database to retrieve students and lecturers information; therefore we decided to use interfaces to be easier in changing in the future. Besides, we use GRASP (General Responsibility Assignment Software Patterns/Principles) to assign responsibility to classes and objects in our object-oriented design (Cotroneo et al., 2000). The different patterns and principles used in GRASP are: Controller, Creator, Indirection, Information Expert, High Cohesion, Low Coupling, Polymorphism, Protected Variations, and Pure Fabrication. Our system context diagram shows the interactions between the system and other actors with which the system is designed to interface. Our system context diagram can be helpful in understanding the context which the system is part of. We use this context diagram early in our project to get agreement on the scope under investigation (Cotroneo et al., 2000). This context diagram is also included in the requirement document. Besides, this diagram was written in plain language thus the stakeholders can understand items within the document.

Description
The purpose of this Project is to develop a web-based assignment submission system which will include many functions for IIBIT Adelaides users (students, admin, lecturer and coordinator). The budget for this project $6000 and allocated time is within 3 months. This is a web-application therefore it can run on popular browsers like Internet Explorer, Firefox, Chrome, Safari, and Opera.

The system will focus on following functions Managing data: allowing admin to enter and update data about courses and users. Managing account: allowing users to update their personal information. Login System: allowing the users and admin to log in to the system with the username and password. Uploading System: allowing students and lecture to upload assignment into the system. Grading System: lecturer should able to update grade for assignments and also add comments according to students performance.

10

Requirements
class Domain Model

EA 9.2 Unregistered Trial Version EA 9.2 Unregistered Trial Version EA 9.2 Unregist System Context Diagram EA 9.2 Unregistered Trial Version EA 9.2 Unregistered Trial Version
IUBallarat

EA 9.2 Unregistered Trial Version

Univ ersityOfBallarat Subsystem

EA 9.2 Unregist

EA 9.2 Unregistered Trial Version EA 9.2 Unregistered Trial Version EA 9.2 Unregistered Trial Version EA 9.2 Unregistered Trial Version
AssignmentSubmissionSystem

EA 9.2 Unregist

EA 9.2 Unregistered Trial Version EA 9.2 Unregistered Trial Version EA 9.2 Unregistered Trial Version EA 9.2 Unregistered Trial Version EAIAssignmentSubmisionSystem 9.2 Unregistered Trial Version EA 9.2 Unregistered Trial Version EA 9.2 Unregistered Trial Version EA 9.2 Unregistered Trial Version EA 9.2 Unregistered Trial Version EA 9.2 Unregistered Trial Version
IDatabase

EA 9.2 Unregist

EA 9.2 Unregist

EA 9.2 Unregist

EA 9.2 Unregistered Trial Version EA 9.2 Unregistered Trial Version EA 9.2 Unregistered Trial Version EA 9.2 Unregistered Trial Version EA 9.2 Unregistered Trial Version EA 9.2 Unregistered Trial Version EA 9.2 Unregistered Trial Version EA 9.2 Unregistered Trial Version EA 9.2 Unregistered Trial Version EA 9.2 Unregistered Trial Version EA 9.2 Unregistered Trial Version EA 9.2 Unregistered Trial Version EA 9.2 Unregistered Trial Version EA 9.2 Unregistered Trial Version EA 9.2 Unregistered Trial Version EA 9.2 Unregistered Trial Version EA 9.2 Unregistered Trial Version EA 9.2 Unregistered Trial Version EA 9.2 Unregistered Trial Version EA 9.2 Unregistered Trial Version
Database Subsystem

EA 9.2 Unregist

EA 9.2 Unregist

EA 9.2 Unregist

EA 9.2 Unregist

EA 9.2 Unregist

EA 9.2 Unregist

EA 9.2 Unregist

EA 9.2 Unregistered Trial Version EA 9.2 Unregistered Trial Version EA 9.2 Unregistered Trial Version EA 9.2 Unregistered Trial Version EA 9.2 Unregistered Trial Version EA 9.2 Unregistered Trial Version EA 9.2 Unregistered Trial Version EA 9.2 Unregistered Trial Version EA 9.2 Unregistered Trial Version EA 9.2 Unregistered Trial Version EA 9.2 Unregistered Trial Version EA 9.2 Unregistered Trial Version EA 9.2 Unregistered Trial Version

EA 9.2 Unregist

EA 9.2 Unregist

EA 9.2 Unregist

EA 9.2 Unregist

EA 9.2 Unregist

EA 9.2 Unregist

EA 9.2 Unregist

EA 9.2 Unregist

EA 9.2 Unregist

EA 9.2 Unregist

EA 9.2 Unregist

EA 9.2 Unregist

EA 9.2 Unregist

11

Admin

Login Update personal information

Login

Update personal information Choose course Choose assignment

Lecturer

Mark assignment

Assignment Submission System

Choose course

Student

Choose assignment

Update assignment date

Submit assignment

View results

View results

Coordinator, Office staff

12

Use case Scenario

This section demonstrates certain functions of the designed solution using high level use case diagrams. Use case diagrams tells you how the particular user will interact with the system. Actors: User (Students, Tutor), Coordinator and Admin.
Procedure: Users have their own id and password which they are currently using to access university website. User enters username and password to login. The system verifies this information and if correct and matches the right level of access for a user, then it takes user to the assignment page. Student enters course information Students can view assignment schedule, when its due. Lecturer can update their personal information. After choose the course lecturer select assignment and can download particular students assignment. Lecturer can upload marked assignment back to the system as a marked assignment and can grade students. Lecturer can also give valuable feedback to student based on their assignment. Coordinator can update users information and can check the result of student. Admin can update users information. Admin can update courses and assignment information.

Exceptions:
If the User has entered wrong username or password. If this happens, user will have to try again.

13
Use case Diagram for Student and Lecturer

14
Use case model for Admin

15
Use case model for coordinator

16
High level storyboards

#Head { font-family : Tahoma ; font-size: 14px; color: #999999; font-weight: bold; } #Head1 { font-family : Tahoma; font-size: 13px; color: #999999; } #Head2 { font-family : Tahoma; font-size: 12px; color: #999999; }

17 #Content { font-family : Tahoma ; font-size: 12px; color: #000000; } #ttnlink { font-family : Tahoma; font-size: 12px; color: #666666; } #ttnnotice { font-family : Tahoma ; font-size: 12px; color: Red; }

Database requirements
User table will be accessed. Username and password will be read. Course table will be accessed. Assignment table will be accessed.

Activity Diagram
The activity diagram shows the basic flow of the main processes.
Activity diagram for students

18

19 Activity diagram for lecturer

20

Data Flow Diagram (DFD)

DFD is a graphical representation of the "flow" of data through an information system, as well as its process aspects.
Data Flow Diagram (System Layout)
Login data

Student

Login Login data Login

Profile
Update personal information
User data

Login

Lecturer
Login

User data

User

Coordinator and office staff Administrator

Login

Choose course

Submit assignment

Assignment data

Choose assignment
Update data

Assignment data

Submission

Mark assignment

Assignment data

View results Update user Update course Update assignment

Assignment data

Update assignment information

Assignment data Assignment data User data Course data

Assignment properties

User

Course

Assignment

21

User Interface (GUI)

Sign in System Layout1

Sign in
System Layout2

22
System Layout3

Choose course

System Layout4

Choose assignment

23
System Layout5

Submit assignment

System Layout6

View result

24
System Layout7

Mark assignment

25

Data Dictionary

Table Name Student

Fields ID First name Last name

Type VARCHAR(50) VARCHAR(50) VARCHAR(50) VARCHAR(50) VARCHAR(50) VARCHAR(50) VARCHAR(50) VARCHAR(50) VARCHAR(50) VARCHAR(50) VARCHAR(50) VARCHAR(50) VARCHAR(50) VARCHAR(50) VARCHAR(2000) VARCHAR(50) VARCHAR(50) VARCHAR(2000) VARCHAR(50) VARCHAR(50) VARCHAR(50) DATETIME DATETIME VARCHAR(50) VARCHAR(50) VARCHAR(50) VARCHAR(50) VARCHAR(50) VARCHAR(50) DATETIME VARCHAR(50) VARCHAR(500) VARCHAR(50)

Description
PK

Lecturer

ID First name Last name

PK

Staff

ID First name Last name

PK

Coordinator

ID First name Last name

PK

Course

ID Name Description

PK

Assignment

ID Name Description

PK

Assignment-Properties

Course-ID Assignment-ID Lecturer-ID Due-date Lock-date

PK, FK references Course(id) PK, FK references Assignment(id)

Profile

ID Password Role

PK

Submission

Student-ID Course-ID Assignment-ID Submission-Date Grade Comment Status

PK, FK references Student(id) PK, FK references Course(id) PK, FK references Assignment(id)

26

Entity-Relationship Diagram
The Entity-Relationship (ER) diagram for the database component of the solution is shown below. This diagram may change during the design, build and testing phases to suit the final design of the application.

Functional Requirements

27
Functional Requirement ID Requirement Title Requirement detail Priority

FR01

Authentication

The system will provide functionality to allow the Students, lecturer, coordinator, office staff and admin to log in to the system with the username and password. On successful entry of username and password they will be guided to the appropriate page. If the details provided are for a student they will be directed to the submission page and result page. If the details entered match a lecturer, they will be directed to the marking page. If the user enters wrong information they we be denied access to the system. If the user forgets password, he/she will have to enter email address to receive new password. As the student account cannot perform lecturer functions, all two types of accounts need the ability to log out from the system and login with a different username and password. This function allows admin to enter new data about course, submission due time, user information and create new user account for new students. This function allows admin to update data about students details, submission time (when extension time is necessary) and course information. This function allows students to submit their assignments during submission time. The submission page will allow lecturers to mark and comment and upload the feedback to the system. A new student will have the ability to register a new account of the website to be able to submit and check the result online. The Manage Account screen will allow users to update their personal information from the system. This Feedback function will allow the lecturer to give feedback information to the student. This function will allow a student to view their own result and they cannot see other students result, this function also permits lecturer, coordinator and office

Essential

FR02 FR03

Validation Password recovery Log out

Essential Essential

FR04

Essential

FR05

Enter new data

Essential

FR06

Update data

Essential

FR07

Submit assignment Manage Submission Register

FR08

Essential

FR09

Essential

FR10 FR11 FR12

Manage account Feedback View Result

Essential Essential Essential

28
staffs to view the result of all students in the particular course.

Non Functional Requirements

NonFunctional Requirement ID

NonRequirement Title Usability

Non-Requirement detail

Priority
Essential / Conditional / Optional

NFR01

Due to the diversity of the users, the system needs to be as simply as information technology system can be The look of the site should be simple and use highly contrasting colors for text. As this application is trying to reach the widest audience possible the system needs to be as bandwidth friendly as possible. The submission system needs to meet all the security requirements of an online submission system. The privacy of all the users of the site should be safe and secured. The submission system should be extended in the future when the amount of users is increased.

Essential

NFR02

Friendliness

Essential

NFR03

Loading time

Essential

NFR04

Security

Essential

NFR05

Privacy

Essential

NFR06

Extensibility

Approvals
Sign-off Sheet

29

I have read the above Project Plan and will abide by its terms and conditions and pledge my full commitment and support for the Project Plan.

Project Sponsor: Date Project Manager: Date

30

References
1. Cotroneo, D., Nixon, P., Russo, S. & Vele, D. (2000). Object-oriented Design of

an Intelligent Building Management System. Orlando : Deputy Vice Chancellor. 2. Lair, R. & Lefebvre, J. (2002). Pure Asp.Net. USA : Sams Publishing. 3. Babu, R. (n.d.). Advantages of ASP.NET. Retrieved September 21, 2012, from http://www.java-samples.com/showtutorial.php?tutorialid=973