Professional Documents
Culture Documents
FTSM
TITLE:
SUPERVISOR:
GROUP: 1
1
Software Design Document
Table of contents
1 Introduction 3
1.1 Purpose 3
1.2 Scope 3
1.4 References 3
1.5 Overview 3
2 System Overview 3
3 Design Considerations 4
3.2 Constraints 4
4 User Interface 5
2
Soft wa re Design Document
1. Introduction
This is the system design document for Bacalah android mobile application.
1.1. Purpose
The software design document captures the design constraints and assumptions
as well as the design details of the subsystems and components of the
application.
1.2. Scope
This design document pertains to the mobile application of Read, with a specific
focus on the features and capabilities being implemented.
1.4. Overview
This design document gives an overview of the application and its primary functionality,
identifies the assumptions and constraints followed during the design of the software,
documents the overall system architecture and provides the detailed design information
for each subsystem and component in the current delivery.
3
Software Design Document
2. System Overview
Android is the first complete, open and free mobile platform. It is developed and
supported by Google and this project uses a Google Android Mobile SDK 1.0 for
testing an application. The software development kit contains the emulator and
advanced debugging tools to run and test the applications.
The aim of our project is to develop a mobile application on the android which
can be used in the real world. The application allows the user to reading,
listening and move from page to other for help the children with special need.
The mobile application is supposed to be installed on the mobile phone
3. Design Considerations
This section contains all of the assumptions, dependencies, and constraints that
were considered during the design of each subsystem and component.
3.2 Constraints
The application will have no sensitive data and not make any internet
interactions.
Not allowed the user to enter any data.
4
Software Design Document
4. User Interface
Figure 1 Figure 2
Figure 3 Figure 4