2. 1. Introduction
1.1 Purpose
This Software Design Document provides the design details of Academic (A Campus based
Android Application).The expected audience is administrator (care taker and maintainer of
application), Students & faculty of the target university.
1.2 Scope
The Academic is a campus based android application for Banasthali University. The
application offers various operations like viewing marks, exam notification, and events within
the university for the faculty, staff & student. These services are conveniently grouped and
developed specifically for use on your Android device. All the operations can be performed
when an internet connection is available. Admin of the application can register prospective
Banasthali University Students, faculty & staff to fully experience all services provided.
1.3 Definitions, Acronyms, and Abbreviations.
Academic: The android application being developed
SDS: Software design is the process by which an agent creates a specification of a software
artifact, intended to accomplish goals, using a set of primitive components and subject to
constraints.
DFD: Data flow diagram is graphical representation of flow of data in an information system. It
is capable of depicting incoming data flow, outgoing data flow and stored data
ER Diagram: ER-modeling is a data modeling technique used in software engineering to produce
a conceptual data model of a information system. Diagrams created using this ER-modeling
technique are called Entity-Relationship Diagrams, or ER diagrams or ERDs
Android: Developed by Google, a popular operating system for smart phones
GUI: Graphical User Interface. An interface that receives and reacts to the user input with a
graphical display.

3. Disk Storage: May be any storage medium mapped to the root file system.
IDE: Integrated Development Environment. A tool to aid programmers in writing code, usually
used for graphical applications.
Java: Java is a programming language. Java is a general-purpose, concurrent, class-based,
object-oriented language that is specifically designed to have as few implementation
dependencies as possible.
RAM: Volatile memory used by the CPU for storing data too large to fit in a register along with
execution code of the running programs.
1.4 Overview
The remaining sections and their contents are listed below.
Section 2 is the Architectural Design that specifies the design through which subsystems
collaborate to perform all the functions included in the system. Each of these subsystems has
an abstract description concerning the services that it provides to the rest of the system. In
turn, each subsystemis expanded into a set of lower-level design operations that collaborate to
perform its services.
Section 3 concerns the Data Structure Design.
Section 4 discusses the Human Interface Design, which displays Screen shots showing interface
from User’s perspective.
Section 5 contains the Testing Issues which deals with the points related to testing.
2. System Architectural Design
2.1 Architecture Design
Introducing the various components of the systems at a high conceptual level A.

4. 2.1.1 Overall Software architecture
Pictorial representation of the overall system architecture

5. 2.1.2 Work Break down Design
ADMINISTRATOR:-
STUDENT

6. HOD:
STAFF:

7. 2.2 Decomposition Description
2.2.1 ER Diagram

8. 2.2.2 Context Diagram

9. 2.2.3 Data Flow Diagram
ADMINISTRATOR:

10. STUDENT:
HOD:

11. STAFF
3. Structure and relationships
3.1 Data design
A description of all data structures including internal, global, and temporary data structures.
3.2 Database Description
Tables in the system:

12. Structure of Administrator Table
Structure of Student Table
Structure of HOD Table

13. Structure of Staff Table
Structure of Fee Table
Structure of Marks Table
Structure of Event Table

14. Structure of Exam Time Table
Structure of Message Table

15. 4. User Interface Design
4.1 Description of the user interface
A detailed description of user interface including screen images or prototype of the software is
presented.
4.2 Screen images
HOMEPAGE
LOGIN PAGE

16. 5. TYPES OF TESTS(WITHIMPLEMENTATION)
The following type of testing has been used in our project:
1. Unit Testing:-This test is applied on each of the module to find whether or not each
module is properly working or not
2. Integration Testing:-After each module cleared the unit testing then modules is
tested for their working all together in the integrated testing phase.
3. Acceptance Testing:-This testing provides the final assurance that the application
needed all behavioral and performance requirements.
7. REFERENCES
 Android SDK reference
http://developer.android.com/reference/packages.html
 Java documentation
http://docs.oracle.com/javase/6/docs/api/
 Software Engineering and Techniques. By Pressman
 Location based services on Android
http://blogs.itemis.de/frey/2009/04/04/location-based-services-on-android-part-1/
 Code snippets for Android development
http://stackoverflow.com/
 Google Projects for Android: Google APIs
http://code.google.com/android/add-ons/google-apis/maps-overview.html
 Connection between PHP (server) and Android (client) Using HTTP and JSON Connection
http://fahmirahman.wordpress.com/2011/04/21/connection-between-php-server-and-android-
client-using-http-and-json/