Software Summary Design Manual

Software Summary Design manual 1. Introduction

1.1 Purpose of writing

Our team decided to develop class PIE software based on the embarrassing situation we found in class. Whenever I go to class to find a classroom, will be very unable to find the classroom, resulting in late, or go to the wrong classroom, I feel sad, it is difficult to think of running so far away, wasting so much time, also affect the normal study, my heart was pierced, I think can have a software can let me no longer so waste valuable time, Can have a software let me in the busy schedule can also see the classroom information, so the idea of class Pie was born.

1.2 Background

A. The software developed by our team is a app--" class Pie" based on andriod 's book Query .

B. our team members are: Wang Gancheng, He Jianxun, Su-Moon

Users: Students in school, including pupils, middle school students and college students.

1.3 Terminology definition

MIS: Management Information System

Srs:software Requirement Specification ( Software Requirements Description )

Dfd:data Flow Diagram ( streaming diagram ) DD:

Data Dictionary ( database dictionary )

Curriculum schedule (curriculum);

1.4 Reference

"JAva Development Combat Classic" is the year of Tsinghua University Press published books, the author is Li Xinghua.

"Android Development Combat Classic" is the year of Tsinghua University Press published books, the author is Li Xinghua.

"android interface Design"

From getting started to being familiar with android

Software Outline Design Description:http://wenku.baidu.com/link?url= Wsbv6j21qa8b-1b2dk3ax9mkh-mih0xo3pjoxq7rbdqfhonod5wmevvvsnvni-hg-bw-goki4wpj5qmfpdsxbermwmobm2g_nuhlwq27emi

Student Selection Database SQL statement exercises -- class schedule :

Http://www.cnblogs.com/jakeasd/p/5567358.html

2. Overall design

2.1 Requirements Regulations

[ Description of the system's main input and output items, processing of functional performance requirements.] ]

1, the curriculum can be a common, can be added to the schedule of the check function

2. Notepad function, you can change the Notepad and delete

　　2.1.1 system Functions

　　2.1.2 System Performance
　　　　2.1.2.1 accuracy
　　　　2.1.2.2 Time Characteristics Requirements
　　　　2.1.2.4 Reliability
　　　　2.1.2.5 Flexibility

　　2.1.3 input/Output requirements

　　2.1.4 Data Management Competency Requirements

　　2.1.5 Fault Handling requirements

　　2.1.6 Other special requirements

2.2 Operating Environment

The software is an Android -based Appthat uses Eclipse Development tools to WebService to control the modification of the database.

　　2.2.1 Equipment
Running the software must be on a system on Android 3.0 or above on the android™ machine.

2.2.2 Support Software
On Android 3.0 more than on Android

　　

2.3 basic design concepts and process flow

Log in first, then complete each function module.

Pass data to the WebService side, get data from it using SOAP, and parse the json.

2.4 Structure

Login

entry notes, borrowing information, search, feedback

the relationship between 2.5 functional requirements and system modules

　　[ This article uses a matrix diagram to illustrate the functional requirements of the implementation of the distribution of the various modules.] ]

	[ System module 1]	[ system Module 2]
Timetable function	√
Notepad features		X

2.6 Manual Treatment process

user Input related information

2.7 Unresolved issues

The timeout reminder feature is not implemented.

3. Interface Design

Interface not designed in this release

3.1 User Interface

graphical interface and text

3.2 External interface

　　Webservice Interface

3.3 Internal Interface

Android system

4. Run the design

4.1 running module combination

mainly for login and personal inquiry and search

4.2 Operation Control

finger lightly.

4.3 run time

Need to accept network data, depending on the network environment.

5. System Data Structure Design

No

key points of 5.1 logical structure design

　

Essentials of Physical structure design of 5.2

Get data parsing from the local database and display it in the ListView .

the relationship between 5.3 data structure and program

　

	[ program 1]	[ program 2]
[ Data structure 1]	√
[ Data structure 2]		√

6. System error Handling Design

6.1 error message

Log on due to network reasons will not be logged up.

Query speed is slow due to excessive number of books queried

6.2 Remedial measures

　A. Backup Technology B. Drop Efficiency Technology c. Recovery and re-start technology

6.3 System Maintenance Design

Feedback, timely to the information, and make corrections.

Software Summary Design Manual