heman4t / eduis Goto Github PK

Module : Academics

Model : Sessional 

Requirement Specification (Scenario):
The model should represent the entity and should provide the basic save and 
fetch interface with help of corresponding mapper class.

Expected Input:
1. Array of Sessional Schedule Information. 

Expected Output:
1. Confirmation of successful commit or relevant message if any error occurs.  

Remarks (if any):
Refer Issue 6 for details of end user scenario.

URL of page: http://academic.aceambala.com/timetable

What steps will reproduce the problem?
1. Click search button
2. enter data.
3.No effect

What is the expected output? What do you see instead?
Search result. Not effect

On what operating system? Which Browser and browser version?
Firefox

Please provide any additional information below.

Module : Academics

Scope: Department

Stakeholders:
1. Sessional In-charge
2. Faculty and Student


Requirement Specification (Scenario):
Sessional Incharge can create/update sessional/unit/internal test schedule. 
Faculty and Students can view datesheet.

Procedure:
  For: Sessional in-charge
    Step 1: Select semester no./class
        Effect : List of all subjects in a grid.

    Step 2: Select date and time for each subject.

    Step 3: Submit

  Repeat steps for each concerned semesters.

Remarks (if any):

Module : Library


Requirement Specification (Scenario):
List of all books in grid form with their status and issue date

Expected Input:
1. ISBN
2. Title
3. Author
4. Edition
5. Acc. no.
6. Issue date

Expected Output:
Grid list of books

Remarks (if any):

Module : Attendance


Requirement Specification (Scenario):


Expected Input:
1. Subject Code
2. Department (optional)

Expected Output:
1. Number of periods delivered (modewise).
2. Number of students enrolled.
3. Average attendance of students.
4. Concerned faculty with attendance count.
5. Period Delivery pattern.
6. Student attendance chart.

Remarks (if any):

Module : Library
Requirement Specification (Scenario):
[Gate Check] At gate, we need to check a book if it is issued or not.

Expected Input:
1.Book Accession Number

Expected Output:
If issued, Status along-with member information

Remarks (if any):

Module : Academics

Controller : Sessional

Requirement Specification (Scenario):
  1. Should provide application logic for controller layer. 
  2. Should contain relevant actions for handling requests(http/ajax).

Expected Input:
  Request may occur for managing the sessionals or for fetching informtion.


Expected Output:
1. Corresponding views should be rendered with relevant data.

Remarks (if any):
Refer issue 6 for end user scenario.

Module : Library

Requirement Specification (Scenario):
Correction/amendments of book information

Expected Input:
1. Updated information

Expected Output:
Changes should reflect in all books of same ISBN.

Remarks (if any):

Module: Library

URL: "http://[SERVER]/book/rcirculation"

Intended For (Specify Roles): Library Staff

Expected Input:
1. Same as book circulation
2. Date range

Expected Output:
1. Same as book circulation
2. include dates also

Requirement Specification (Scenario):


Remarks (if any):

Module : Library


Requirement Specification (Scenario):
Facility to enter new books.

Expected Input:
1.Book's Complete Details (e.g. acc.no, author, title, isbn)

Expected Output:
Book in database.

Remarks (if any):