CSE401- Software Engineering

Department of Computer Science and Engineering

Spring - 2014
Assignment 1
For this assignment, you have to gather requirements from a client, and write a Software
Requirements Specification (SRS) document based on the requirements. The client has provided an
initial brief about what he wants, which is given below. Please note that this is an initial version, and
this text has plenty of ambiguities, mistakes, and some possible contradictions.
You will be given one chance to interview the client. Your tasks are to
Get the real requirements from the client from the interview.
o Please note that there are additional requirements, which are not mentioned in the
initial brief. (These have already been decided upon and written. It is expected that
you will extract these requirements from the client during the interview. Failure to
include these new requirements in your SRS will cost marks.)
Get clarification on issues which require it.
Make sure you leave the interview with a clear idea of what the client wants. This
opportunity will not be given to you again for this assignment.

Once you have gathered the requirements, you will have to write a Software Requirements
Specification (SRS), based on the template (srs_template.doc) given in the `Assignment 1 folder. I
have also included a draft marking scheme in the folder. Please consult it to understand what areas
you are being evaluated on.

Submission instructions

This assignment is worth 10% of your total semester marks. It is due by 10:30 AM, 08/06/2014.
Please email a soft copy of your SRS to nabeel.mohammed@uap-bd.edu, with the subject line
`CSE401 Assignment 1'. You also have to submit a hard copy of the SRS in class, on the due date
(08/05/2014). Late submissions will incur a penalty of 10% per day at a geometric rate.







Clients initial brief:
We, University of Asia Pacific, require an attendance taking system. The system is intended to be
used by teachers on portable/mobile devices. Currently teachers have to take attendance on paper,
and then submit the attendance information to a central system. This workflow is becoming
problematic as it is quite easy to make mistakes while entering the attendance. The current system
also has a difficult user interface, and the provider, NotSoCooperative Inc., is currently understaffed,
and has expressed their inability to deliver a new interface in the next 5 years. Most of our teachers
are not technically competent, so we need all user interfaces to be easy to use, with plenty of help
documentation.
The new system should provide mobile applications (for multiple common platforms). The
application should prompt a user to log-in, and verify the authentication details from the university's
central LDAP server. Once logged in, the application will show a list of classes for the teacher. After
selecting a class, the teacher will be presented with a list of contact-events (a contact-event can be a
lecture, a tutorial, a seminar -- essentially anywhere an attendance needs to be taken). The teacher
will choose a contact-event, and the system should automatically load the student list for that
contact-event, from the (currently deployed) enrolment system. Teachers should be presented with
an easy to use interface, which should handle large number of students in a suitable manner, where
he/she selects the attendance-status (present/absent) of the students. Once the teacher has
finished taking attendance, the application should store the attendance record to the previously
mentioned central attendance system. We do not have a clear idea about the user interface of this
application, and we expect the software developers to workshop it with us.
We want our administrators to be able to configure what are the contact-events for each subject.
We have a scheduling system -- some data should come from that. But administrators should
definitely be allowed to override that information.
Another issue with the current attendance logging system is that it does not provide any reports to
the teachers, except a final spreadsheet at the end of the semester. Teachers have requested that
the system help them identify students who:
Are missing classes frequently
Have missed more than 5 classes in any running semester.
These reports should be automatically sent to the teachers in an email, without any user
intervention.
Furthermore the system should communicate with the guardian/parent of every student who has
missed more than 5 classes in a running semester. The modes of communication are as follows:

An SMS to the guardian's/parent's mobile phone number. The number should be retrieved
from the central student records system.
An email to the guardian's/parent's email address. The email address should be retrieved
from the central student records system.
A printed letter posted to the guardian's/parent's postal address. The postal address should
be retrieved from the central student records system.

As we engage more with you, we hope to divulge further details of our requirements.