图书管理系统需求说明书英文版.docx

1、图书管理系统需求说明书英文版Requirements SpecificationCollege Library Management SystemVersion 1.1 (final)Table of Contents1. Project Drivers 31.1 Purpose 31.2 Scope 31.3 Abbreviations 41.4 Client, Customer and other Stakeholders 41.5 Users of the Product 71.5.1 The Users of the Product 71.5.2 Viewpoints 72. Proj

2、ect Constraints 112.1 Mandated Constraints 112.2 Implementation environment of the current system 112.2.1 System Interface 112.2.2 User Interface 142.3 Partner applications 152.4 Schedule 162.5 Budget 163. FUNCTIONAL REQUIREMENTS 163.1 The Scope of the Work 163.2 The Scope of the Product 173.3 Funct

3、ional requirements 184. Non - Functional Requirements 194.1 Look and Feel Requirements 194.2 Usability Requirements 194.3 Performance Requirements 194.4 Operational Requirements 194.5 Maintainability and Portability Requirements 204.6 Security Requirements 204.7 Legal Requirements 205. Project Issue

4、s 205.1 Open Issues 205.2 Users Documentation and Training 205.3 Waiting Room 206. References: 217. Appendix 1. System Models 221. Project Drivers1.1 PurposeThe purpose of this document is to familiarize reader with software, which is developed by Dream Team Corporation. Specification describes all

5、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-u

6、sers (patrons), customer engineers, software developers (defined by Ian Sommerville for system requirements)1.1.2 ScopeThe 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 define

7、d 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: Items database (books, journals, magazines, newspapers, diploma thesis, etc

8、) Patrons database a small Access-based database with information about digital items, that College has (software, music) integrated with Items databaseLMS will also provide all necessary services for databases such as creating, deleting, updating and searching information. Patrons will be able to a

9、ccess to the library site (web-based) through the Internet or through the librarys LAN-connected computers, 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 supporte

10、d 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 Tec

11、hnology IE Microsoft Internet Explorer1.4 Client, Customer and other Stakeholders1.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 Corporations client in this project. The N.I.F will receive the final

12、 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

13、 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) Customer Project Manager Requirements Engineer System Designer System Tester System Administrator Configuration ManagerSRS identifies each type of stakehol

14、der:Table 1. End - UsersStakeholder IdentificationEnd - Users (librarians, patrons), College LibraryKnowledge needed by the projectBasic knowledge of Microsoft Windows-based interfaces, Internet browsers interfaces.Necessary degree of stakeholders involvementLow. End Users are not involved in softwa

15、re development, just in some kinds of sociological surveys Degree of influence for that stakeholderHigh. Software to be developed to satisfy first of all the End-Users.Table 2. CustomerStakeholder IdentificationCustomer (National Innovation Foundation)Knowledge needed by the projectCustomers require

16、ments, Project plan, business modeling and forecasting. Necessary degree of stakeholders involvementMiddle. Customer supervises project, establishes budget Degree of influence for that stakeholderHigh. Software development process may be canceled by Customer.Table 3. Project ManagerStakeholder Ident

17、ificationProject Manager (Fabian GARRIDO-MARTINEZ), The Dream Team CorporationKnowledge needed by the projectProject plan creating, computer skills. Necessary degree of stakeholders involvementHigh. Project Manager supervises project, establishes team, provides deadlines, negotiates with customer. D

18、egree of influence for that stakeholderHigh. All development process requires constant control and decision making from Project Manager, Table 4. Requirements EngineerStakeholder Identification Requirements Engineer (Andrey Paklin), The Dream Team CorporationKnowledge needed by the projectSRS creati

19、ng, computer skills. Necessary degree of stakeholders involvementHigh. Requirements Engineer summarizes requirements provided by customer, updates them. Degree of influence for that stakeholderMiddle. Requirements Engineer defines SRS under strict Customer and Project Manager controlTable 5. System

20、DesignerStakeholder IdentificationSystem Designer (Konstantin Vlasenko), The Dream Team CorporationKnowledge needed by the projectComputer-based Design tools, Internet technologies Necessary degree of stakeholders involvementHigh. System Designer defines all software interfaces, how the product will

21、 look like, providing success of product from the End Users point of view. Degree of influence for that stakeholderLow. System Designer will not use product to be developed in appropriate way.Table 6. System TesterStakeholder IdentificationSystem Tester (Alex Kanavin), The Dream Team CorporationKnow

22、ledge needed by the projectComputer-based Testing tools, Internet technologies, Testing requirements and specifications. Necessary degree of stakeholders involvementMiddle. System Tester is looking for mistakes in software and verify products possibilities. Degree of influence for that stakeholderLo

23、w. System Tester will not use product to be developed in appropriate way.Table 7. System AdministratorStakeholder IdentificationSystem Administrator, College staffKnowledge needed by the projectStrong computer skills, Internet and network technologies. Necessary degree of stakeholders involvementLow

24、. System Administrator is not involved in software development process. Degree of influence for that stakeholderMiddle. System Administrator will maintain and install product.Table 8. Configuration ManagerStakeholder IdentificationConfiguration Manager (Alex Kanavin), The Dream Team CorporationKnowl

25、edge needed by the projectComputer-based Testing tools, Internet technologies, Testing requirements and specifications. Necessary degree of stakeholders involvementHigh. Configuration Manager responsible for project repository, project web pages. Degree of influence for that stakeholderMiddle. Confi

26、guration Manager must follow job description and deadlines, to prove his/her quality.1.5 Users of the Product1.5.1 The Users of the ProductPotential Users of the College LMS are librarians and patrons. Table 8. LibrariansUser nameCollege Librarians User roleTo maintain College LMS (add, delete, rene

27、w items and update databases) Subject matter experienceMaster. College had the same management system in card-based form. All features of the old database are presented in new software product Technological experienceJourneyman*, as less. Basic computer skills are obligatory. Intellectual abilities/

28、disabilitiesMiddle intellectual abilitiesAge groupAdult age 25-65 (65 years old- is a pension age)Table 9. PatronsUser nameLibrary patronsUser roleTo use the College LMS in practice (from library or any place, where Internet connection is available)Subject matter experienceMay ranges from novice to

29、master.Technological experienceMay ranges from novice to master, but basic computer skills and Internet working experience are obligatory.Intellectual abilities/disabilitiesMay range in wide bandAge group16-65 (College students, professors, teachers, other staff)*) - journeyman, some kind of human e

30、xperience degree, its situated between novice and master1.5.2 ViewpointsThis project consists of several stakeholders, which were defined above. According to Ian Sommervilles article Viewpoints for requirements elicitation: a practical approach 2 software requirements can be described by using PREvi

31、ew model. The viewpoint model is deliberately flexible and informal. Viewpoints can be adapted to specific organizational practice and standards as can the notations used to describe system requirements. Viewpoints may be used during the early stages of a requirements engineering process as a structuring mechanism for requirements elicitation and analysis. Identifying viewpoints and organizing information around them at this stage reduces the possibility that critical information will be missed during requirements elicitatio