软件工程（英文版）课程设计

Wuchang University of Technology

Software Engineering curriculum design

班级：计科1101班 姓名：屈方柳

学号：20114221011

2014年6月22日

Chap 1 Fix the project

1.1 Discuss to fix a project Library Management System 1.2 Feasibility analysis

You can use the Java language to carry on the system design, the use of MyEclipse10 to develop the system, MySQL database development background. Technically speaking, the project is feasible. Because of the scale of the project is not too large, team development is feasible. 1.3Team building

Development team members: Fangliu Qu, Sheng Chen, Chang Dai, Qiaoqiao Zhu, Bowen Wang 1.4Project arrangement

Fangliu Qu: set up the framework of the system Sheng Chen: database development Chang Dai: the system data interface Qiaoqiao Zhu: basic data maintenance Bowen Wang: Library and system maintenance

Chap2 Requirement analysis

2.1 Basic conception

Borrowing and management system for Library's mission. System

should be able to manage books and readers info, and record lending and charging information of reader, as well as new book order and management. 2.2 Workflow

2.2.1 Confirm scope

The system framework of the system interface design, log on to the system design, data in the foreground and background frame display design; database development needs to be analyzed to build tables used in the system data; data layer interface needs to connect the data with the database, can be used for data access operations; basic data maintenance the need for readers' information, books category, book information management; part includes the administrator to add and modify the system maintenance, books are books to borrow, return, search and record lending information

2.2.2 Detailed requirements discussion E-R chart:

System flowchart:

beginloginNpass?Ybasic data maintenancebook order managementBorrow managementsystem maintenance reader info managementbook type managementbook info managementnew book ordernew book acceptance checkbook searchbook orderbook backchange passworduser managementYexit?Nend 2.2.3 Confirm the final requirement functional requirements:

1. To add ,delete or modify info of reader. 2. To add ,delete or modify info of type of book.

3.To add ,delete or modify info of book.

4. Create order for new book. 5. Acceptance of new book.

6. To record borrow and read info of reader. 7. To manage book back info. 8. To search a certain book.

9. Manager can modify their own password. 10. Manager can add new user of this system.

Non-functional requirements:

1. System starts time less than 10 seconds. 2. Manager can modify amount of money of reader. 3. System failure not more than 3 times a day.

4.Recovery time after a system failure less than 30 seconds. 5.The system can be ported to windowsXP or later operating system.

6.Tips must be clear that the requirements of the operation 7. Validate the input information to ensure that does not

affect system security.

8.After the system starts,it’s uptime not less than 72 hours.

2.3 Requirements documentation

Project Name: Library Management System

Project Description: A borrowing and management system for Library's mission .The system can be used to manage book info, reader info and borrow information.

Development Environment: Windows7, MyEclipse10, Java1.6, MySQL, Microsoft Visio, Photoshop CS5. Development time: 5 days. Functional Modules:

1. Basic data maintenance

1.1. Reader info management 1.2. Book type management 1.3. Book info management 1.4. Exit the system

2. Book order management

2.1. New book order

2.2. New book acceptance check

3. Borrow management

3.1. Book search 3.2. Book order 3.3. Book back

4. System maintenance

4.1. Change password

4.2. User management

Chap 3 Software Design

3.1 Basic conception

The use of incremental development model to develop the system, the completion of system development framework and the database first. Then the development of user and library data browsing module, the formation of the first version. Development of the login module, and the development of data crud part, forming the development version. Finally, system details and interface changes, the formation of the final version.

3.2 Workflow

3.2.1 Module design

System framework design in order to integrate other modules, and provide a platform for other parts’ running together. And is convenient for the user to use the system to call functions of each module .The login window should be popped up when users start the system, show system functions to users by menus and toolbars in the main window of the system.

3.2.2 System design

The layered system as data layer, control layer, presentation layer. The data layer is mainly for processing data, modify and

query including books, readers, books, orders, the user information, communicate with the database; control the logic control layer, including user to user input data processing, control, data operation process such as: login process, borrowing books process, as well as borrowing charges; display output layer mainly processing system, the data is displayed in the proper format, and the user operation tips.

3.3 System design documentation First, the administrator login

① When a user name and password is incorrect, an error should be displayed.

② Only administrators can log in, other users can not login. ③ After landing, the main screen displays

Second, to add, delete and modify the book type ,and display all the books category information

① When adding and modifying books category, the input data is incorrect, display proper error.

② When the input is no error, add or modify the display success. Third, to add, delete, modify, and query the book information ①When add and modify library information, and when you make a mistake, an error should display.

② Check book information, you can follow book title and book au

thor search, display all book information .

Fourth, increase, delete, and modify reader information ① When readers add and modify the information, when the input is incorrect, the error should be displayed. When you add the same user should also have tips. Fifth, the book order management

① When ordering new books, books you want to add the information in the book exists, if you add the data is incorrect, there must be a corresponding tips .

② Acceptance books, if books have been accepted, then the appropriate error .

Sixth, loan management

① Borrow books, the reader number must already existing readers, books Number of books also exist. ② Books returned.

Seventh, system management

① Change your password, you can only change the password of the current user, and the right to enter the old password, the new password and confirm the password to be the same, not the same as on the output of the corresponding tips.

② Add and modify user information when the input is incorrect, the display proper error. When you add the same user should also

have tips.

Chap 4 Detailed Design

4.1 Basic conception

The books management system is designed for library manager ,only the library manager is allowed to use it ,so ,when they start the system ,they will be asked to login . According to the functions of each module ,the following menus will be set in the main window of the system: basic data maintenance (including reader info management, book type management, book info management), book order management (including new book order, new book acceptance check), borrow management (including book search, book order, book back),system maintenance (including change password, user management). 4.2 Workflow

4.2.1 Program code File: BookLoginIFrame.java

public class BookLoginIFrame extends JFrame { private JPasswordField password; private JTextField username; private JButton login; private JButton reset;

private static Operater user;

private class BookResetAction implements ActionListener { public void actionPerformed(final ActionEvent e){ } }

}

class BookLoginAction implements ActionListener {

public void actionPerformed(final ActionEvent e) { }

public BookLoginIFrame() { }

public static Operater getUser() { }

public static void setUser(Operater user) { }

File: MenuAction.java

public class MenuActions {

private static Map frames; // 子窗体集合

public static PasswordModiAction MODIFY_PASSWORD; // 修改密码窗体动作

public static UserModiAction USER_MODIFY; // 修改用户资料窗体动作

public static UserAddAction USER_ADD; // 用户添加窗体动作 public static BookSearchAction BOOK_SEARCH; // 图书搜索窗体动作

public static GiveBackAction GIVE_BACK; // 图书归还窗体动作 public static BorrowAction BORROW; // 图书借阅窗体动作 public static CheckAndAcceptNewBookAction NEWBOOK_CHECK_ACCEPT;// 修改密码动作

public static BoodOrderAction NEWBOOK_ORDER; // 新书定购窗体动作

public static BookTypeModiAction BOOKTYPE_MODIFY; // 图书类型修改窗体动作

public static BookTypeAddAction BOOKTYPE_ADD; // 图书类型添加窗体动作

public static ReaderModiAction READER_MODIFY; // 读者信息修改窗体动作

public static ReaderAddAction READER_ADD; // 读者信息添加窗体动作

public static BookModiAction BOOK_MODIFY; // 图书信息修改窗体动作

public static BookAddAction BOOK_ADD; // 图书信息添加窗体动作 public static ExitAction EXIT; // 系统退出动作 static{

frames = new HashMap(); MODIFY_PASSWORD = new PasswordModiAction(); USER_MODIFY = new UserModiAction();

USER_ADD = new UserAddAction();

BOOK_SEARCH = new BookSearchAction(); GIVE_BACK = new GiveBackAction(); BORROW = new BorrowAction();

NEWBOOK_CHECK_ACCEPT = new CheckAndAcceptNewBookAction(); NEWBOOK_ORDER = new BoodOrderAction();

BOOKTYPE_MODIFY = new BookTypeModiAction(); BOOKTYPE_ADD = new BookTypeAddAction(); READER_MODIFY = new ReaderModiAction(); READER_ADD = new ReaderAddAction(); BOOK_MODIFY = new BookModiAction(); BOOK_ADD = new BookAddAction(); EXIT = new ExitAction(); }

private static class PasswordModiAction extends AbstractAction {

PasswordModiAction() {}

public void actionPerformed(ActionEvent e) {} }

private static class UserModiAction extends AbstractAction { UserModiAction() {}

public void actionPerformed(ActionEvent e) {} }

private static class UserAddAction extends AbstractAction { UserAddAction() {}

public void actionPerformed(ActionEvent e) {} }

private static class BookSearchAction extends AbstractAction {

BookSearchAction() {}

public void actionPerformed(ActionEvent e) {} }

private static class GiveBackAction extends AbstractAction { GiveBackAction() {}

public void actionPerformed(ActionEvent e) {} }

private static class BorrowAction extends AbstractAction { BorrowAction() {}

public void actionPerformed(ActionEvent e) {} }

private static class CheckAndAcceptNewBookAction extends AbstractAction {

CheckAndAcceptNewBookAction() {}

public void actionPerformed(ActionEvent e) {}

{ { {

}

private static class BoodOrderAction extends AbstractAction { BoodOrderAction() {}

public void actionPerformed(ActionEvent e) {} }

private static class BookTypeModiAction extends AbstractAction BookTypeModiAction() {}

public void actionPerformed(ActionEvent e) {} }

private static class BookTypeAddAction extends AbstractAction BookTypeAddAction() {}

public void actionPerformed(ActionEvent e) {} }

private static class ReaderModiAction extends AbstractAction ReaderModiAction() {}

public void actionPerformed(ActionEvent e) {} }

private static class ReaderAddAction extends AbstractAction { ReaderAddAction() {}

public void actionPerformed(ActionEvent e) {} }

private static class BookModiAction extends AbstractAction { BookModiAction() {}

public void actionPerformed(ActionEvent e) {} }

private static class BookAddAction extends AbstractAction { BookAddAction() {}

public void actionPerformed(ActionEvent e) {} }

private static class ExitAction extends AbstractAction { public ExitAction() {}

public void actionPerformed(final ActionEvent e) {} }

private MenuActions() {}

}File: Library.java

public class Library extends JFrame {

private static final JDesktopPane DESKTOP_PANE = new JDesktopPane();

public static void main(String[] args) {} // 添加子窗体的方法

}

public static void addIFame(JInternalFrame iframe) {} public Library() {} // 创建工具栏的方法

private JToolBar createToolBar() {} // 创建菜单栏的方法

private JMenuBar createMenu() {}

Chap 5 Software Testing

1.3 Basic conception

Software testing is to ensure that we have developed software to meet user requirements. So the test need according to the demand to. In the development process

we will carry on the debugging of each stage, after completion of the development will also carry on the overall system test.

5.2 Workflow

5.2.1 Test preparation

The database table to add associated data, can the module testing. The modules of the system are combined, ready for system testing.

5.2.2 Component testing

start the system:

main window:

toolbar:

menu of basic data maintenance:

menu of book order management:

menu of borrow management:

menu of system maintenance:

5.2.3 Integration testing Demand content The user can use to login system Interface display, menu display all function For readers' information to add, delete and modify Book information to add, delete and modify Book categories to add, delete and modify To generate new order For the book acceptance and book information input Part System framework System framework Basic data maintenance Basic data maintenance Basic data maintenance Basic data maintenance Basic data maintenance Is complete? Complete Complete Complete Complete Complete Complete Complete Loan management Loan management Loan management User management User management According to the conditions of library search Register the readers to borrow books Record the reader return the books information, and automatically charge for borrowing The currently logged in user can change the password For the registration of new users Complete Complete Complete Complete Complete 5.2.4 System testing

1.1 writing purpose

This project aims to develop a library management system, to achieve the library information management. Borrow books in the convenience of the reader at the same time, convenient library administrators to manage the books

1.2 Project background

System name: library management system. 1.3 System introduction

Borrowing and management system for Library's mission. Need to be able to manage the books and readers, record lending and charging information reader, as well as new order and management.

2.1 The test environment and configuration

The test environment is briefly introduced and its configuration.

The database server configuration

CPU:Intel i3 2.4 GHz memory: 512M hard drive: 20G Operating system: Window7 and higher application software: Eclipse MySQL 2.2 landing interface System login interface:

When not the administrator landing:

When the administrator landing:

The interface of the system:

Add the interface type of books:

Displays the following error when input is incorrect:

Only when all is filled correctly, show added successfully:

Book category change interface:

When the modified data is not legitimate, the prompt and add.

Book information to add interface:

When the data is incorrect, will appear the following tips:

When all the data is correct, there will be the following interface:

Book information to modify the interface:

When data is modified in error, prompts appear identical and books to add.

Readers information add interface:

When the data add a mistake, can appear the following tips:

When all the data are added properly, there will be the following tips:

Readers information modify and delete interface:

When the user to modify the data, if the data is not legitimate,

tips and add the same reader information.

When the input data is not lawful, will have the following tips:

When the data is legitimate, will have the following tips:

If the same data add data and database, will have the following tips:

Here is the book acceptance interface:

Library management:

Book search information:

Library management:

Borrowing borrowing information:

Book return management:

Book return information:

Book Search and query

Display all the information of books:

Change the password:

The user information to add:

The user information, modify and delete:

3.1Test conclusion

Test execution is fully (can increase the safety, reliability, maintainability and functional description)

Control measures and effectiveness of testing risk satisfaction

The goal is to complete the test

Can enter the next phase of the project objectives 3.2Suggestions

The system has some defects.

Chap 6 Project Management

2.1 Plan and Change Development order:

1.Build the system background frame 2.The database design

3.The data layer interface function design 4.Module development and data browsing 5.The system interface design

6.The data layer interface detailed design 7.Module development, basic data maintenance 8.The book order module

9.The system user management module 10.The books management module

6.2 Schedule Management

Day Fangliu Qu Sheng Chen Chang Dai Sheng Chen Fangliu Qu 1 ① ② ③ ④ ⑤ 2 3 4 Chang Dai Qiaoqiao Zhu Chang Dai Bowen Wang Bowen Wang ⑥ ⑦ ⑧ ⑨ ⑩

Chap 7 User manual

7.1 User Manual of System Framework

①. The login window will be popped up when users start the system. Input correct username and password, then, click the ”Login” button ,user can begin to use the system. If user click the “Reset” button, contents in input boxes will be cleared.

②.After user login the system, the main window will be displayed. The main interface is made up by menu, toolbars, and LOGO of this system. There will display certain tips when your mouse move over the menu or toolbar.

③.In the main interface, there is 4 menus: Basic data maintenance, Book order management, Borrow management, System maintenance. When you click any menu, it’s sub-menu will be display.

④.Toolbar of the system include adding book information, updating book information, borrowing book, ordering new book, acceptance

of

new

book,

adding

reader

information,

updating&deleting reader information, and exit the system.

本文来源：https://www.bwwdw.com/article/ipn3.html