Submitted By

Name sayed Faisal

Submitted to
Zartasha Saeed
Major assignment
Department of computer science

INTRODUCTION
The project e-Administration of computer labs is an automated system for lab management. It
eases the tasks of the administrator, instructors, and head of the department of various
departments, technical staff and students.
The main Objective of this project is to provide the solution for an organization which involve
computing facilities such as Computers, Printers, LCDs, Digital Boards, and ACs etc. on a 24×7
basis to carry out academic experiments for all the branches with all the equipment in good
working conditions and also with all the necessary software installed and configured. This
software also helps the administrator and instructor(s) to maintain proper documentation of the
computing systems.
This is both web and app based.

1) Purpose/ Vision:
The purpose of this project is to provide the solution for an organization to help in monitoring
working condition of computing facilities such as Computers, Printers, LCDs, Digital Boards,
and ACs etc. on a 24×7 basis. 

2) Scope:
 Helps the administrator and instructor to keep track of the detailed information of the
labs.
 Assists in the smooth interaction between different users.
 Proper maintenance of available Resources.
 Speed up the Activities to overcome the problems associated with the lab.
 Helps Technical staff/instructor to lodge complaints.
 Automate the task of assigning complaints to specific technical staff based on the nature
of the problem.
 Helps the HODs of various departments to send an extra lab request to the administrator.
3) User classes:
There are two type User in this software.

i. administrator
In this software the administrator is superior. He mainly control all the management of system.
Admin can create, delete, permanently store, revise and update data or task.

ii. User

The User are of two types. Teacher or lecturer and student. They will have separate data log,
their data flow diagram and functallity is different according to condition.

5) Elicitation Technique:
i. Observation
During Observation I collect that student and all the teaching staff who managing with
organization data. How they use the computer source for their projects. How student staff is
depend on electronics machine for their studies. How teaching staff is varies computer to convey
the lectures to student.

ii. Interview
In interview I asked the user for what possible functionality they want in this software. How that
will help them. Will this be a step up? I listed down all the the object of stakeholder. On the basic
required data I list down the top priorities the divided those into basic ascending order. After the
interview, I reviewed these sites to analyze the expectations and available features of the
interviewers in these shopping sites and I discovered several features that I can implement in my
project.
 Shortly, I can say that I really benefited from this interview session. It gave me confidence in
the practical requirements I had discovered during the observation phase and understood
them more clearly.

6) Use Cases:

User

Administrator
 Our system has two types of accessing modes,

1. Administrator

2. User

2.1 Teacher

2.2 Student

i) Administrator:

SMS is managed by Administrator. Administrator has to update and monitor the registered
student details, add a new student, provide register number for all students, assign each
student a course etc., Administrator can update his profile, and also can give help to the
teachers and students.

ii) User:

There are two users:

a. Student:

User can only view their personal details, course assigned, and edit their assigned
course and can view their attendance.

b. Teacher:

User can add them onto the portal and view their schedules, marks attendance of the
students, also can view the students details in graphical order, also of a single student
and about the views from the students.
 7) Quality attributes:

Reliability
This software is high reliabity. As it will bought web and app based. This software is design to
work in any condition. The reliability is concern in every aspect. This work mostly with
electronics like printing, LCD, etc., so the basic functionality is in view of developer.

Maintainability
This software is although with very long listed in code but due to expert indolent and
Effect full documentation this software is very maintainable. The code area which we prefer
Will be java. JavaScript, web design etc. But still it would be quite tough to analyze.

Usability
This can be measured in terms of ease of use. The application should be user-friendly. Should be
easy to learn. Navigation should be simple.

 Easy to use for input preparation, operation, and interpretation of the output.
 Provide consistent user interface standards or conventions with our other frequently used
systems.
 Easy for new or infrequent users to learn to use the system.

Correctness
This application is correct in terms of its functionality, calculations used internally and the
navigation should be correct. This means that application should adhere to functional
requirements.

Efficiency
The system quality attribute. Measured in terms of time required to complete any task given to
the system. For example, the system should utilize processor capacity, disk space, and memory
efficiently.
This system is using all the available resources then the user will get degraded performance
failing the system for efficiency. If the system is not efficient then it cannot be used in real-time
applications.

Learnability
 Learnability of this software system which make it different from other is due to:
– The design of user interfaces of system
– The clarity and the simplicity of the user instructions.
The user interface should develop in such way that information as close to reality as possible and
permit efficient utilization of the software’s failures.
The user manual is structured clearly and simply and be free of all dead weight. It is explain to
the user what the software system should do, how the individual functions are activated, what
relationships exist between functions, and which exceptions might arise and how they can be
corrected.

8) Functional Requirements:

 It should provide schedule/timetable without any of clashes among faculties, day, time
and room that must be visible to all.
 It should generate a report about the registered complaint to the admin and response
report to the user who has submitted his queries.
 Secure registration and profile management facilities for different users.
 It should provide details like e-learning facilities, server room details, software
installation procedures etc. to students.
 It should generate alerts via SMS.
8.1) LOGIN

Actors

 Administrator
 Student
 Teachers

Introduction
This use case documents the steps that must be followed in order to log into the
University Registration System.

Login
Pre-condition: The user must have valid login Id and password.
Post-condition: If the use case is successful,
Then actor is logged into the system. If not, the System State remains unchanged.

Basic Flow

Starts when actor wishes to login onto the URS

Process

 Admin of lab system have access over all the system. It can access all even the other
actors’ portal. Admin can have access to updating, deletion, removing, adding, and
Technical control of system. Admin do also have access to other basic function like
printing, documentation, re-entering.
  Teacher or Lecturer can update the current data like adding new lecture removing and
basic function. But cannot assess other portal.

 Student can received all the data. They do basic function but cannot access like deletion,
update, add etc. but can have own save portal.
 Admin can have direct access the other system.
 There must a space share common among all the actor which can be used in case if the
data share is required

Use Cases:

User