Software Design Specification

(SDS)

Version 1.0
Prepared by

Muhammad Qasim
Ahmed Obaid
Muhammad Salman Ahmed
NUST-SEECS
1. Introduction
1.1 System Purpose
This document is the next step work after the completion of Software Requirements
Specification (SRS). The purpose of this document is to describe the detail architecture
and design specifications for the project entitled “University Management System”.
--------------------------------------------------------------------------------------------------------
--------------------------------------------------------------------------

1.2 System Scope

The scope of this framework is to provide “University Management for Administrative
staff, teachers and students. This framework will ensure authorized service
provisioning to all users of the web application (…………..

1.3 Acronyms, and Abbreviations

ORM Object relational model

MVT Model View Template

……………………………………………
.

2. System Overview
This product is implemented as a web application which provides authorized
access to features including fee generation, exam results allocation, and
attendance views along with quick and efficient user registration to collect data
and enroll students into the university. ………………………………………………………….

3. Analysis Model
3.1 Interface Objects
The interface objects represent the main interfaces of the system. Given below is the
list of different interface objects used in our system.

Login Interface Home Page Interface Attendance Interface

Exam Results interface Facility Interface Fee Interface

Registration Interface Entry Test Interface Logout Interface

3.1.2 Acquaintance Association interface objects

Registration:
In Add-X-interface, Delete-X-interface and Update-X-Interface, X can be
Teacher, Student, Administrative Employee or Database Engineer.
Exam Results:
In Add-Y-Interface, Delete-Y-Interface and Update-Y-Interface, Y represents
Course, Student, Marks and Obtained Marks.
Fee Generation:
In Generate-Z-Interface, the Z represents Start Date, End Date, UMS and
Amount.

Attendance:
In Add-A-Interface, Delete-A-Interface and Update-A-Interface, A represents
Course, Student, Present or Absent.
Entry Test:
In Add-B-Interface, Delete-B-Interface and Update-B-Interface, B represents
Type, Student, Marks and Obtained Marks.

3.1.3 Containership

INITIAL-INTERFACE

BUTTON[1]

HOMEPAGE-INTERFACE

X-INTERFACE

BUTTON[2]

LOGIN-INTERFACE ADD X-INTERFACE

HOMEPAGE-INTERFACE

BUTTON[1]
ADD B-INTERFACE
BUTTON[2]

HOMEPAGE-INTERFACE GENERATE Z-INTERFACE

BUTTON[3]
 ADD/UPDATE A-INTERFACE
BUTTON[4]

HOMEPAGE-INTERFACE VIEW A-INTERFACE

BUTTON[5]

HOMEPAGE-INTERFACE ADD/UPDATE B-INTERFACE

BUTTON[6]

VIEW B-INTERFACE
ADD X-INTERFACE

BUTTON[1]

BUTTON

TEXTBOX[1]

ADD X-INTERFACE TEXTBOX

LABEL[1]

LABEL
 REGISTRATION
INTERFACE

ENTRY TEST
INTERFACE
ADD/UPDATE
INTERFACE
ATTENDACE
INTERFACE
INTIAL INTERFACE

EXAM RESULTS
INTERFACE
DETAILS INTERFACE

FEE GENERATION
HOMEPAGE INTERFACE
INTERFACE

LOGOUT
INTERFACE

3.2 Sub System Diagram

 3.3 Control Objects

Attendance Fee Processor User Processor Result

Processor Processor

4. System Detailed design

5. Design Model
4.1 Use case diagram

4.2 Class diagram

4.3 Sequence Diagrams
4.3 Communication Diagrams
4.4 Activity Diagrams
4.5 State machine diagram
4.6 Deployment Diagram

4.7 Component Diagram

4.9 System architecture diagram