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

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

《图书管理系统需求说明书英文版.docx》由会员分享，可在线阅读，更多相关《图书管理系统需求说明书英文版.docx（23页珍藏版）》请在冰豆网上搜索。

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

RequirementsSpecification

CollegeLibraryManagementSystem

Version1.1（final）

TableofContents

1.ProjectDrivers3

1.1Purpose3

1.2Scope3

1.3Abbreviations4

1.4Client,CustomerandotherStakeholders4

1.5UsersoftheProduct7

1.5.1TheUsersoftheProduct7

1.5.2Viewpoints7

2.ProjectConstraints11

2.1MandatedConstraints11

2.2Implementationenvironmentofthecurrentsystem11

2.2.1SystemInterface11

2.2.2UserInterface14

2.3Partnerapplications15

2.4Schedule16

2.5Budget16

3.FUNCTIONALREQUIREMENTS16

3.1TheScopeoftheWork16

3.2TheScopeoftheProduct17

3.3Functionalrequirements18

4.Non-FunctionalRequirements19

4.1LookandFeelRequirements19

4.2UsabilityRequirements19

4.3PerformanceRequirements19

4.4OperationalRequirements19

4.5MaintainabilityandPortabilityRequirements20

4.6SecurityRequirements20

4.7LegalRequirements20

5.ProjectIssues20

5.1OpenIssues20

5.2User’sDocumentationandTraining20

5.3WaitingRoom20

6.References:

21

7.Appendix1.SystemModels22

1.ProjectDrivers

1.1Purpose

Thepurposeofthisdocumentistofamiliarizereaderwithsoftware,whichisdevelopedbyDreamTeamCorporation.Specificationdescribesallhardwareandsoftwarerequirementsforproduct,behaviorofitanditscomponents.SoftwareRequirementsSpecification（SRS）allowstoverifythecustomerthatallhisrequirementsareobservedandimplementedcorrectlybydeveloper.

TheintendedaudiencefortheSRSreadingconsistsofsystemend-users（patrons）,customerengineers,softwaredevelopers（definedbyIanSommervilleforsystemrequirements）[1].

1.2Scope

TheDreamTeamCorporationwasinvitedtodevelopCollegeLibraryManagementSystemforNationalInnovationFoundation（N.I.F）.Thesoftwarewillreflectalltherequirementsdefinedbythecustomer.

CollegeLibraryManagementSystemwillallowtoperformallnecessaryproceduresforlibrariansandpatrons.Accordingtocustomerrequirementsthesoftwaretobedevelopedwillconsistofthreedatabases:

✓Item’sdatabase（books,journals,magazines,newspapers,diplomathesis,etc）

✓Patron’sdatabase

✓asmallAccess-baseddatabasewithinformationaboutdigitalitems,thatCollegehas（software,music）integratedwithItem’sdatabase

LMSwillalsoprovideallnecessaryservicesfordatabasessuchascreating,deleting,updatingandsearchinginformation.Patronswillbeabletoaccesstothelibrarysite（web-based）throughtheInternetorthroughthelibrary’sLAN-connectedcomputers,scatteredthroughoutthelibraryforsendingrequest,receivinginformationaboutcurrentstatusofthebooksorrenewingthem.ThedesignofproductinterfacetobedevelopedwillbesupportedbyMicrosoftIE,NetscapeNavigatorandOperabrowsers.Userinterfaceswillbeergonomicalandeasy-to-use.

1.3Abbreviations

∙LMS–Librarymanagementsystem

∙SRS–Softwarerequirementsspecification

∙PC–PersonalComputer

∙HDD-HardDiscDrive

∙RAM–RandomAccessMemory

∙LUT–LappeenrantaUniversityofTechnology

∙IE–MicrosoftInternetExplorer

1.4Client,CustomerandotherStakeholders

1.4.1Theclientistheperson/swhopayforthedevelopment,andownerofthedeliveredsystem.

NationalInnovationFoundationbecametheDreamTeamCorporation’sclientinthisproject.TheN.I.Fwillreceivethefinalacceptanceofthesystem,andthusmustbesatisfiedwiththedevelopedsystemornot.

Allclientremarkswillbeimprovedimmediately.Productdeliverableshaveappropriatedprojectschedule,approvedbytheclient.

1.4.2Thecustomeristheperson/swhowillbuytheproductfromtheclient.

Inourcase,therolesoftheclientandthecustomerarefilledbythesamecompany.

1.4.3Stakeholdersinclude:

✓End-Users（detailedinsection1.5）

✓Customer

✓ProjectManager

✓RequirementsEngineer

✓SystemDesigner

✓SystemTester

✓SystemAdministrator

✓ConfigurationManager

SRSidentifieseachtypeofstakeholder:

Table1.End-Users

StakeholderIdentification

End-Users（librarians,patrons）,CollegeLibrary

Knowledgeneededbytheproject

BasicknowledgeofMicrosoftWindows-basedinterfaces,Internetbrowser’sinterfaces.

Necessarydegreeofstakeholder’sinvolvement

Low.End–Usersarenotinvolvedinsoftwaredevelopment,justinsomekindsofsociologicalsurveys

Degreeofinfluenceforthatstakeholder

High.SoftwaretobedevelopedtosatisfyfirstofalltheEnd-Users.

Table2.Customer

StakeholderIdentification

Customer（NationalInnovationFoundation）

Knowledgeneededbytheproject

Customer’srequirements,Projectplan,businessmodelingandforecasting.

Necessarydegreeofstakeholder’sinvolvement

Middle.Customersupervisesproject,establishesbudget

Degreeofinfluenceforthatstakeholder

High.SoftwaredevelopmentprocessmaybecanceledbyCustomer.

Table3.ProjectManager

StakeholderIdentification

ProjectManager（FabianGARRIDO-MARTINEZ）,TheDreamTeamCorporation

Knowledgeneededbytheproject

Projectplancreating,computerskills.

Necessarydegreeofstakeholder’sinvolvement

High.ProjectManagersupervisesproject,establishesteam,providesdeadlines,negotiateswithcustomer.

Degreeofinfluenceforthatstakeholder

High.AlldevelopmentprocessrequiresconstantcontrolanddecisionmakingfromProjectManager,

Table4.RequirementsEngineer

StakeholderIdentification

RequirementsEngineer（AndreyPaklin）,TheDreamTeamCorporation

Knowledgeneededbytheproject

SRScreating,computerskills.

Necessarydegreeofstakeholder’sinvolvement

High.RequirementsEngineersummarizesrequirementsprovidedbycustomer,updatesthem.

Degreeofinfluenceforthatstakeholder

Middle.RequirementsEngineerdefinesSRSunderstrictCustomerandProjectManagercontrol

Table5.SystemDesigner

StakeholderIdentification

SystemDesigner（KonstantinVlasenko）,TheDreamTeamCorporation

Knowledgeneededbytheproject

Computer-basedDesigntools,Internettechnologies

Necessarydegreeofstakeholder’sinvolvement

High.SystemDesignerdefinesallsoftwareinterfaces,howtheproductwilllooklike,providingsuccessofproductfromtheEnd–Userspointofview.

Degreeofinfluenceforthatstakeholder

Low.SystemDesignerwillnotuseproducttobedevelopedinappropriateway.

Table6.SystemTester

StakeholderIdentification

SystemTester（AlexKanavin）,TheDreamTeamCorporation

Knowledgeneededbytheproject

Computer-basedTestingtools,Internettechnologies,Testingrequirementsandspecifications.

Necessarydegreeofstakeholder’sinvolvement

Middle.SystemTesterislookingformistakesinsoftwareandverifyproduct’spossibilities.

Degreeofinfluenceforthatstakeholder

Low.SystemTesterwillnotuseproducttobedevelopedinappropriateway.

Table7.SystemAdministrator

StakeholderIdentification

SystemAdministrator,Collegestaff

Knowledgeneededbytheproject

Strongcomputerskills,Internetandnetworktechnologies.

Necessarydegreeofstakeholder’sinvolvement

Low.SystemAdministratorisnotinvolvedinsoftwaredevelopmentprocess.

Degreeofinfluenceforthatstakeholder

Middle.SystemAdministratorwillmaintainandinstallproduct.

Table8.ConfigurationManager

StakeholderIdentification

ConfigurationManager（AlexKanavin）,TheDreamTeamCorporation

Knowledgeneededbytheproject

Computer-basedTestingtools,Internettechnologies,Testingrequirementsandspecifications.

Necessarydegreeofstakeholder’sinvolvement

High.ConfigurationManagerresponsibleforprojectrepository,projectwebpages.

Degreeofinfluenceforthatstakeholder

Middle.ConfigurationManagermustfollowjobdescriptionanddeadlines,toprovehis/herquality.

1.5UsersoftheProduct

1.5.1TheUsersoftheProduct

PotentialUsersoftheCollegeLMSarelibrariansandpatrons.

Table8.Librarians

Username

CollegeLibrarians

Userrole

TomaintainCollegeLMS（add,delete,renewitemsandupdatedatabases）

Subjectmatterexperience

Master.Collegehadthesamemanagementsystemincard-basedform.Allfeaturesoftheolddatabasearepresentedinnewsoftwareproduct

Technologicalexperience

Journeyman*,asless.Basiccomputerskillsareobligatory.

Intellectualabilities/disabilities

Middleintellectualabilities

Agegroup

Adultage25-65（65yearsold-isapensionage）

Table9.Patrons

Username

Librarypatrons

Userrole

TousetheCollegeLMSinpractice（fromlibraryoranyplace,whereInternetconnectionisavailable）

Subjectmatterexperience

Mayrangesfromnovicetomaster.

Technologicalexperience

Mayrangesfromnovicetomaster,butbasiccomputerskillsandInternetworkingexperienceareobligatory.

Intellectualabilities/disabilities

Mayrangeinwideband

Agegroup

16-65（Collegestudents,professors,teachers,otherstaff）

*）-journeyman,somekindofhumanexperiencedegree,it’ssituatedbetweennoviceandmaster

1.5.2Viewpoints

Thisprojectconsistsofseveralstakeholders,whichweredefinedabove.AccordingtoIanSommerville’sarticle‘Viewpointsforrequirementselicitation:

apracticalapproach’[2]softwarerequirementscanbedescribedbyusingPREviewmodel.Theviewpointmodelisdeliberatelyflexibleandinformal.Viewpointscanbeadaptedtospecificorganizationalpracticeandstandardsascanthenotationsusedtodescribesystemrequirements.Viewpointsmaybeusedduringtheearlystagesofarequirementsengineeringprocessasastructuringmechanismforrequirementselicitationandanalysis.Identifyingviewpointsandorganizinginformationaroundthematthisstagereducesthepossibilitythatcriticalinformationwillbemissedduringrequirementselicitatio