样例用户需求用例.docx

样例用户需求用例.docx

《样例用户需求用例.docx》由会员分享，可在线阅读，更多相关《样例用户需求用例.docx（24页珍藏版）》请在冰点文库上搜索。

样例用户需求用例

XXX

XXXSystem

UserRequirement

-

UseCases

V1.0

Project

XXXReportingSystem

Document

UserRequirement–Usecases

Version

1.0

Author

Date

Supervisor

Date

TableofContents

Reference3

IntroductiontoXXX:

4

PartI:

UnderstandingsandDescriptionoftheSystem5

1.DataDefinition5

2.WorkFlowofReportgeneration7

3.FunctionsList8

3.1MultipleCurrency8

3.2GeographicalOrganization8

3.3PurchaseClassification8

3.4DataEntry8

3.5PurchaseDataSearching8

3.6AccountManagement8

3.7AuditTrailandLog9

3.8MessageCenter9

3.9OnlineHelpandFAQ9

3.10MultipleLanguageSupport9

3.11Date/TimeFormatmanagement9

3.12CodeTablemanagement9

PartII:

UseCases10

UC1.AccessControl10

UC1.1PasswordPolicy11

UC2.AccountManagement12

UC2.1ManageUserAccount14

UC2.2ManageUserGroup15

UC2.3SelfAccountManagement16

UC2.4ManageUserFunction17

UC3.ProjectManagement18

UC4.InputReports19

UC4.1Write/ImportInputReports21

Reference

Thisdocumentisreferredtothefollowingdocuments:

XXX_Project_Charter

XXX-Spec

IntroductiontoXXX:

InYYY,purchaseprocedures,systemsandorganizationsarecurrentlyheterogeneous.Differentprojectssubmittheirreportsindifferentformats,andconsiderableworkisdonemanuallytogather（usuallybyassistantofpurchasedirector）thepurchasingdatawhichresultindifficultiestogatherinformationfromallprojects（suppliers,purchases,volumes）andassesssuppliers.

XXXisareportingsystemwhichaimstocentralizeinformationfromYYY’ssubsidiariesandtogeneratereportstodeterminehowpurchasescanbeoptimized.Thissystemwillprovidefollowingfunctions:

▪Dataentry:

InputReports（data）inpre-definedformatswillbesubmittedtothesystemquarterlybyusersfromdifferentcountriesaswellasprojects.

▪Datastorage:

ThedatawillbestoredinSQLServer2005andprocessedinthesystemusing.Nettechnology.

▪Reportgeneration:

Thesystemwillproduceon-demandOutputReportsfromconsolidateddatainaccordancewiththepredefinedreportformat.

PartI:

UnderstandingsandDescriptionoftheSystem

1.DataDefinition

Inthissection,theobjectdataaswellasthemainattributesusedinthissystemaredefined.

Class

Attributes

User

Username

Password

Lastname

Firstname

Department

Title

Project

Company

Zone

Country

Email

Language

Telephone

Usergroups

Rightsonreport

Usergroup

Name

Users

Userfunctions

Project

Description

Zone

Country

Project

Name

StartDate

EndDate

ActiveDate

InactiveDate

Companies

Zone

Country

Services

Purchaser

Validator

InputReport

Status

Purchaser

Validator

SubmitDate

StartDate

ValidateDate

IntegrateDate

CancelDate

WriteorImport

Quarterofreport

Messages

OutputReport

ReportType

CreateDate

Currency

Language（s）

CreateUser

Exportfiles

Currency

Name

Shortform

Symbol

Exchangerate

Message

Senduser

Receiveuser

Senddate

Readdate

Replydate

Country

Name

Language

Currency

Zone

Projects

Zone

Name

Country

Projects

2.WorkFlowofReportgeneration

1）Write/ImportInputreports

▪PurchaserswritetheirdraftversionsoftheInputReports.Theycan

1）Writedatavaluedirectly:

TherewillbenodefaultvaluesonanyfieldoftheInputReports.Alldatahastobeenteredbytheuserexplicitly.

2）Selectthefollowingvaluefromlist

▪SupplierName

▪SupplierCity

▪SupplierCountry

▪SupplierProvince

▪PurchasercanimporttheinputreportinExcel/XMLformatwhichmostlycomesfromthirdpartyexternalsystemlikeSAPorUFIDA.

▪ExternalSystempreparesthefilestoimportinaccordancewiththepredefinedformat.

▪Administratorcanimporttheinputreportonbehalfofanypurchaser.

3.FunctionsList

3.1MultipleCurrency

3.1.1Add,update,deletecurrency

3.1.2Maintaintheexchangerate

3.1.3Auto-extendExchangeRate

3.1.4Sendmessagetoadmin

3.2GeographicalOrganization

3.2.1Create,Update,DeleteProjects

3.2.2Create,Update,DeleteZones

3.2.3Create,Update,DeleteCountries

3.2.4MaintaintherelationshipsbetweenProject,ZoneandCountry.

3.2.5Create,Update,DeleteServices

3.2.6Maintainproject-servicerelationships

3.2.7EnableMultipleLanguagevaluesforzone/country/project.

3.3PurchaseClassification

3.3.1Create,Update,DeleteCategories

3.3.2SetCategoryAttributes

3.3.3ExportthedefinitionoftheclassificationinXMLandExcelformats

3.3.4DefinetheClassificationMappingMechanism

3.3.5Enablemultiplelanguagesforpurchaseitemdescription.

3.3.6Enablemultiplelanguagesforthefieldname（s）ofacompositedatastructure.

3.4DataEntry

3.4.1Write,Import,Submitinputreports

3.4.2Validateinputreports

3.5PurchaseDataSearching

3.5.1Searchinputreport

3.5.2View,Modify,Deleteinputreports

3.6AccountManagement

3.6.1Create,Update,DeleteUserGroup

3.6.2Create,Update,DeleteUserFunction

3.6.3AssociateUserFunctiontousergroup

3.6.4AssociateReportAccessRighttoUserGroup

3.6.5AssociateusertoUserGroup

3.6.6Add/Update/Suspend/Deleteuseraccount,

3.6.7DefinePasswordpolicy

3.6.8PasswordstoredinDatabaseshouldbeencrypted.

3.6.9Lock,unlockuseraccount

3.7AuditTrailandLog

3.7.1WriteAuditLog,ApplicationLogandActivityLog

3.7.2Review,Search,DeleteLog

3.7.3BackupandRestoreLog

3.8MessageCenter

3.8.1SendandReceivemessages

3.8.2ReadandReplymessages

3.8.3Deletemessages

3.8.4ManageandHousekeepmessages

3.9OnlineHelpandFAQ

3.9.1ReadonlinehelpandFAQ

3.9.2Add/UpdateonlinehelpandFAQcontent

3.9.3SetUseraccessrightsonhelpandFAQcontent

3.10MultipleLanguageSupport

3.11Date/TimeFormatmanagement

3.12CodeTablemanagement

3.12.1Add/Update/DeleteCompany

3.12.2Add/Update/DeleteDepartment

3.12.3Add/Update/DeleteCity

PartII:

UseCases

UC1.AccessControl

FunctionalRequirement

1.Passwordcontrolshouldbeprovidedinrestrictingunauthorizedaccesstothesystem

2.Limitednumberoflogonfailuretrialshouldbeprovidedtopreventaccountpasswordguessing.

3.Logoutfunctionshouldbeprovidedforusertoexitthesystem

4.XXXusercanbeauthenticatedthrougheitherbuilt-insystemauthenticationoradedicatedActiveDirectory（AD）

Non-FunctionalRequirement

1.Usershouldbeabletoaccessthesystematanytime.

ProposedSolution

1.Passwordwillbestoredindatabaseinencryptedformat.

2.Maximumnumberoflogonfailuretrialcanbeconfiguredbysystemadministrator.Onceexceeded,theaccountwillbelockedforacertainperiodwhichisalsoconfigurablebysystemadministrator.

3.Uponidletimeoutwhichtheidleperiodisconfigurablebysystemadministrator,apromptingwillbepoppedtotheuserandinformingabouttobekickedoutfromthesystem.Ifstillnotreplyfromtheuser,say30seconds,theuserwillbekickedout.

4.Itwillhavesameeffectoflogoutiftheuseriskickedoutfromthesystembyidletimeoutorsessionlostdetected.

UC1.1PasswordPolicy

FunctionalRequirement

1.Systemadministratorisresponsibleforsettingpasswordpolicy,including:

•Theacceptablepasswordformat

•Thepasswordchangenotification

•Passwordstoredindatabasewillbeencrypted.

•Numberofretryforlogonfailure

•Accountlockoutperiod

2.AlockedaccountwillbeunlockeduponlockingperiodexpiredormanuallyunlockedbySystemAdministrator.

Non-FunctionalRequirement

Nil

ProposedSolution

TBD

UC2.AccountManagement

FunctionalRequirement

1.Systemadministratorcandefineusergroupandtheaccessfunctionsofeachusergroup.

2.Systemadministratorcancreate/update/deleteuseraccount,associateuseraccountintousergroup

3.Systemadministratorcanmanageuserfunctionsandassociatethemtousergroupstodefineuserfunctions.

4.Otherusercanmanagethefollowinginformationifitsown

a.ContactTelnumber

b.Additionale-mailaddress

Non-FunctionalRequirement

1.SystemadministratorshouldconsultHRdepartmentforuserinformation.

ProposedSolution

TBD

Class

Attributes

User

Username

Password

Lastname

Firstname

Department

Title

Project

Company

Zone

Country

Email

Language

Telephone

Usergroups

Rightsonreport

Usergroup

Name

Users

Userfunctions

Project

Zone

Country

UC2.1ManageUserAccount

FunctionalRequirement

1.SystemAdmincan

a）createuseraccounttoaddnewusers.

b）defineuserattributesafterhecreatestheuser.

c）associateusertousergroup（s）,andassociateusergrouptouserfunction（s）.

d）associateusertoproject（s）,thentheusercanworkontheprojectaccordingtohisrole.

e）associateusertozoneaswellastocountry.

2.SystemAdminmaymodifyuseraccountwhennecessary.

3.SystemAdminmaydeleteuseraccountifitisnotused.

Non-FunctionalRequirement

Nil

ProposedSolution

TBD

UC2.2ManageUserGroup

FunctionalRequirement

1.SystemAdmincan

a）createusergrouptocontainusers.

b）defineattributesaftercreatestheusergroup.

c）associateusergrouptouserfunction（s）.

d）updateusergroupwhennecessarytodefineuserattributes.

e）deleteusergroupifitisnotused.

Non-FunctionalRequirement

Nil

ProposedSolution

TBD

UC2.3SelfAccountManagement

FunctionalRequirement

1.UsermayaskSystemAdmintoupdatehislogin,andtheusernamewillbedefinedandupdatedbytheAdministrator.

2.UserwillgetinitialpasswordfromSystemAdminbyemail.

3.Usermaychangehispasswordafterhelogsin.

4.SystemAdmincansetandchangeuser’s

a）FamilyName（compulsory）andFirstName（compulsory）.

b）Department（compulsory）.

c）Title（compulsory）

5.U