没有合适的资源?快使用搜索试试~ 我知道了~
图书管理系统需求说明书英文版借鉴.pdf
1.该资源内容由用户上传,如若侵权请联系客服进行举报
2.虚拟产品一经售出概不退款(资源遇到问题,请及时私信上传者)
2.虚拟产品一经售出概不退款(资源遇到问题,请及时私信上传者)
版权申诉
0 下载量 30 浏览量
2021-11-28
05:54:14
上传
评论
收藏 686KB PDF 举报
温馨提示
试读
28页
图书管理系统需求说明书英文版借鉴.pdf
资源详情
资源评论
资源推荐
Requirements Specification
College Library Management System
Version 1.1 (final)
2
Table of Contents
1. PROJECT DRIVERS ....................................................................................................................... 3
1.1 Purpose ....................................................................................................................................... 3
1.2 Scope ........................................................................................................................................... 3
1.3 Abbreviations ............................................................................................................................ 4
1.4 Client, Customer and other Stakeholders ...................................................................... 4
1.5 Users of the Product ................................................................................................................ 7
1.5.1 The Users of the Product ..................................................................................................................7
1.5.2 Viewpoints ...........................................................................................................................................8
2. PROJECT CONSTRAINTS .......................................................................................................... 13
2.1 Mandated Constraints ........................................................................................................... 13
2.2 Implementation environment of the current system .................................................... 13
2.2.1 System Interface ..............................................................................................................................14
2.2.2 User Interface ...................................................................................................................................16
2.3 Partner applications ....................................................................................................... 18
2.4 Schedule ................................................................................................................................... 18
2.5 Budget ....................................................................................................................................... 19
3. FUNCTIONAL REQUIREMENTS ................................................................................................ 19
3.1 The Scope of the Work .......................................................................................................... 19
3.2 The Scope of the Product .................................................................................................... 20
3.3 Functional requirements ...................................................................................................... 21
4. NON - FUNCTIONAL REQUIREMENTS ................................................................................... 22
4.1 Look and Feel Requirements .............................................................................................. 22
4.2 Usability Requirements ........................................................................................................ 22
4.3 Performance Requirements ................................................................................................. 23
4.4 Operational Requirements ................................................................................................... 23
4.5 Maintainability and Portability Requirements ................................................................ 23
4.6 Security Requirements ......................................................................................................... 24
4.7 Legal Requirements ............................................................................................................... 24
5. PROJECT ISSUES ..................................................................................................................... 24
5.1 Open Issues ............................................................................................................................. 24
5.2 User ’s Documentation and Training ................................................................................. 24
5.3 Waiting Room .......................................................................................................................... 24
6. REFERENCES: .............................................................................................. 错误!未定义书签。
7. APPENDIX 1. SYSTEM MODELS .............................................................................................. 25
3
1. Project Drivers
1.1 Purpose
The purpose of this document is to familiarize reader with software, which is developed by
Dream Team Corporation. Specification describes all hardware and software requirements for
product, behavior of it and its components. Software Requirements Specification (SRS)
allows to verify the customer that all his requirements are observed and implemented
correctly by developer.
The intended audience for the SRS reading consists of system end-users (patrons), customer
engineers, software developers (defined by Ian Sommerville for system requirements)[1].
1.2 Scope
The Dream Team Corporation was invited to develop College Library Management System
for National Innovation Foundation (N.I.F). The software will reflect all the requirements
defined by the customer.
College Library Management System will allow to perform all necessary procedures for
librarians and patrons. According to customer requirements the software to be developed will
consist of three databases:
Item?s database (books, journals, magazines, newspapers, diploma thesis, etc)
Patron?s database
a small Access-based database with information about digital items, that College has
(software, music) integrated with Item?s database
LMS will also provide all necessary services for databases such as creating, deleting,
updating and searching information. Patrons will be able to access to the library site
(web- based) through the Internet or through the library?s LAN-connected computers,
4
scattered throughout the library for sending request, receiving information about current
status of the books or renewing them. The design of product interface to be developed will
be supported by Microsoft IE, Netscape Navigator and Opera browsers. User interfaces
will be ergonomical and easy-to-use.
1.3 Abbreviations
LMS – Library management system
SRS – Software requirements specification
PC – Personal Computer
HDD - Hard Disc Drive
RAM – Random Access Memory
LUT – Lappeenranta University of Technology
IE – Microsoft Internet Explorer
1.4 Client, Customer and other Stakeholders
1.4.1 The client is the person/s who pay for the development, and owner of the delivered
system.
National Innovation Foundation became the Dream Team Corporation?s client in this project.
The N.I.F will receive the final acceptance of the system, and thus must be satisfied with the
developed system or not.
All client remarks will be improved immediately. Product deliverables have appropriated
project schedule, approved by the client.
1.4.2 The customer is the person/s who will buy the product from the client.
In our case, the roles of the client and the customer are filled by the same company.
1.4.3 Stakeholders include:
End - Users (detailed in section 1.5)
5
Customer
Project Manager
Requirements Engineer
System Designer
System Tester
System Administrator
Configuration Manager
SRS identifies each type of stakeholder:
Table 1. End - Users
Stakeholder Identification End - Users (librarians, patrons), College Library
Knowledge needed by the
project
Basic knowledge of Microsoft Windows-based interfaces, Internet
browser ’s interfaces.
Necessary degree of
stakeholder ’s involvement
Low. End – Users are not involved in software development, just in
some kinds of sociological surveys
Degree of influence for that
stakeholder
High. Software to be developed to satisfy first of all the End-Users.
Table 2. Customer
Stakeholder Identification Customer (National Innovation Foundation)
Knowledge needed by the
project
Customer ’s requirements, Project plan, business modeling and
forecasting.
Necessary degree of
stakeholder ’s involvement
Middle. Customer supervises project, establishes budget
Degree of influence for that
stakeholder
High. Software development process may be canceled by Customer.
Table 3. Project Manager
Stakeholder Identification Project Manager (Fabian GARRIDO-MARTINEZ), The Dream Team
Corporation
Knowledge needed by the Project plan creating, computer skills.
剩余27页未读,继续阅读
hyj15659071652
- 粉丝: 0
- 资源: 7万+
下载权益
C知道特权
VIP文章
课程特权
开通VIP
上传资源 快速赚钱
- 我的内容管理 展开
- 我的资源 快来上传第一个资源
- 我的收益 登录查看自己的收益
- 我的积分 登录查看自己的积分
- 我的C币 登录后查看C币余额
- 我的收藏
- 我的下载
- 下载帮助
安全验证
文档复制为VIP权益,开通VIP直接复制
信息提交成功
评论0