Software Summary Design Manual

1. Introduction

1.1 Purpose of writing

Based on the embarrassing situation I encountered when borrowing books, our team decided to develop the book Search Assistant software. Whenever I go to the library to borrow books, will be very bug found that the book has been borrowed, I feel sad, it is difficult to think of running such a long way, wasting so much time, but also empty-handed back, my heart was pierced, I think can have a software can let me no longer so waste valuable time, Could there be a software that allows me to get the information I want from thousands of miles away, so the idea of the book assistant was born.

1.2 background

A. The software developed by our team is a app--"campus book assistant" based on Andriod's book query.

B. Members of our team are: Wang Dongbo, Shi, Yanya, Li Haisu.

User: Iron big hard gardener and students.

1.3 definition

[List the definitions of the terminology used in this document and the original phrase of the foreign-language first letter group.] ]

1.4 References

[Lists the relevant references.] ]

2. Overall design

2.1 Requirement Requirements

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

2.1.1 System functions

2.1.2 System Performance
2.1.2.1 Accuracy
2.1.2.2 Time Characteristic requirements
2.1.2.4 Reliability
2.1.2.5 Flexibility

2.1.3 Input/Output requirements

2.1.4 Data Management capability requirements

2.1.5 Fault Handling requirements

2.1.6 Other special requirements

2.2 Operating Environment

The software is an Android-based app that uses Eclipse development tools to control database modifications through WebService.

2.2.1 Equipment
The software must be running on an Android machine with a system above Android4.0.

2.2.2 Support Software
On an Android machine above Android4.0

　　

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

2.5 the relationship between 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]
[Book Search]	√
[Borrowing enquiry]		√

2.6 Manual Processing Process

user Input related information

2.7 Unresolved issues

The timeout reminder feature is not implemented.

3. Interface design

3.1 user Interface

Graphical interface

3.2 external Interface

WebService interface

3.3 Internal Interface

With the Android system

4. Run the design

4.1 Running module Combinations

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

5.1 key points of logical structure design

　

5.2 Essentials of Physical Structure design

Get data parsing from WebService and display it in the ListView.

5.3 the relationship between 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. Technology for reduction of efficiency C. Recovery and re-start technologies

6.3 System Maintenance Design

Feedback, timely to the information, and to make corrections, database maintenance by the Library is responsible for.

Software Summary Design Manual