Professional Documents
Culture Documents
09BCE049
Supervisor: Akila Victor
Software Design
Specification
Version 1.0
Page i
CCS
Table of Contents
Table of Contents .......................................................................................................................... ii
1. Introduction ..............................................................................................................................1
1.1
1.2
1.3
1.4
Purpose ........................................................................................................................................ 1
System Overview......................................................................................................................... 1
Design Map ................................................................................................................................. 2
Definitions and Acronyms ........................................................................................................... 2
Assumptions ................................................................................................................................ 3
Constraints ................................................................................................................................... 4
System Environment ................................................................................................................... 5
Risks and Volatile Areas ............................................................................................................. 5
3. Architecture ..............................................................................................................................6
3.1
3.2
3.3
Overview ..................................................................................................................................... 6
Subsystem, Component, or Module 1 N.................................................................................. 6
Strategy 1N .............................................................................................................................. 7
Page ii
CCS
1. Introduction
1.1 Purpose
This design will detail the implementation of the requirements as defined in the Software Requirements
Specification.It describes the design constraints that are to be considered when the system is to be designed,
and other factors necessary to provide a complete and comprehensive description of the design for the
software. The SDS captures the complete software requirements for the system, or a portion of the system.
2. Design Considerations
All design considerations were handled in SRS.
Page 1
CCS
2.1 Assumptions
2.2 Constraints
We only have about two months to finish all documentation, software creation and enhancements.
We have a lot of ideas but cannot implement them due to time constraint. One of the major ones is
to move the application to be completely browser based.
Page 2
CCS
De
3. Architecture
3.1 Overview
Competitive councelling system supports various user functions like
Register an account.
Browse the college database.
Browse the question bank database
Mail subscription for exam alerts
Query posting
Query Response
Other than these functions, administrators have the privilege to manage the content of the system,
view traffic statistics and user details.
Page 3
CCS
Content Management
View as Guest
Traffic Details
3.3 Strategy
The basic strategy followed in the division and implementation of the module is to group the similar
functions together into the same module. This avoids redundancy on part of implementation and
thus makes the system highly extensible and reusable. The main objective was to make the system
highly readable such that altering a part of the module is affected at all occurrences in the system.
4. Database Schema
4.1 Tables, Fields and Relationships
The database contain five tables holding the data for the system categorized into relevant tables with
their primary keys and constraint relationships to have a centralized and optimized storage of the
system data. In our system. The database is created using MySQL for integrated web development
with php and apache. The databse name is CCS.
Based on the requirements, five tables seem sufficient for the system. The proposed tables along
with their attributes are:
Admin
Username varchar(20)
Password varchar(20)
Email varchar(50)
Query
Timestamp date
Userid char(5)
Content varchar(160)
Qid number(3)
Status char(1)
Page
Id number(2)
Name varchar(20)
Position number(1)
Content varchar(500)
Comment
Qid number(3)
Userid char(5)
Timestamp date
Comment varchar(160)
User
Id char(5)
Page 4
CCS
Name varchar(40)
Email varchar(50)
Password varchar(20)
Mobile number(10)
Sex char(1)
Address varchar(80)
Subscription char(1)
The Query, Comments and User tables are inter-related. Each Query is posted by a User. Also
each of the comment is posted by some user and a query has multiple comments. Queries have
comments. These relationships are depicted in the ER model diagram in the high level design.
4.1.1 Databases
CCS database on server. CCStest database for testing purposes.
4.1.2 Tables
No new Tables required.
Page 5
CCS
Page 6
CCS
Page 7
CCS
Page 8
CCS
Page 9
CCS
Page 10
CCS
Page 11
CCS
Page 12
CCS
Hower effects have been added to make the GUI interactive and more pleasing to the eye.
Page 13
CCS
Page 14
CCS
Some pages are still under construction. This screen shows the status.
Page 15
CCS
Page 16
CCS