样例 - 用户需求用例

XXX XXX System

User Requirement - Use Cases V1.0

ProjectXXX Reporting SystemDocumentUser Requirement – Use casesVersion1.0Author Date Supervisor Date Table of ContentsReferenceIntroduction to XXX:Part I: Understandings and Description of the System1. Data Definition2. Work Flow of Report generation3. Functions List3.1 Multiple Currency3.2 Geographical Organization3.3 Purchase Classification3.4 Data Entry3.5 Purchase Data Searching3.6 Account Management3.7 Audit Trail and Log3.8 Message Center3.9 Online Help and FAQ3.10 Multiple Language Support3.11 Date/Time Format management3.12 Code Table managementPart II: Use CasesUC1. Access ControlUC1 .1 Password PolicyUC2. Account ManagementUC2 .1 Manage User AccountUC2 .2 Manage User GroupUC2 .3 Self Account ManagementUC2 .4 Manage User FunctionUC3. Project ManagementUC4. Input ReportsUC4 .1 Write/ Import Input ReportsReferenceThis document is referred to the following documents:XXX_Project_CharterXXX-SpecIntroduction to XXX:In YYY, purchase procedures, systems and organizations are currentlyheterogeneous. Different projects submit their reports in different formats,and considerable work is done manually to gather (usually by assistant ofpurchase director) the purchasing data which result in difficulties to gatherinformation from all projects (suppliers, purchases, volumes) and assesssuppliers.XXX is a reporting system which aims to centralize information from YYY’ssubsidiaries and to generate reports to determine how purchases can beoptimized. This system will provide following functions:

Data entry: Input Reports (data) in pre-defined formats will besubmitted to the system quarterly by users from different countriesas well as projects.

Data storage: The data will be stored in SQL Server 2005 andprocessed in the system using .Net technology.

Report generation: The system will produce on-demand OutputReports from consolidated data in accordance with the predefinedreport format.Part I: Understandings and Description of the System1. Data DefinitionIn this section, the object data as well as the main attributes used in thissystem are defined.

ClassAttributes

UserUsernamePasswordLast nameFirst nameDepartmentTitleProjectCompanyZoneCountryEmailLanguageTelephoneUser groupsRights on report

User groupNameUsersUser functionsProjectDescriptionZoneCountryProjectNameStart DateEnd DateActive DateInactive DateCompaniesZoneCountryServicesPurchaserValidator

Input ReportStatusPurchaserValidatorSubmit DateStart DateValidate DateIntegrate DateCancel DateWrite or ImportQuarter of reportMessages

Output ReportReport TypeCreate DateCurrencyLanguage(s)Create UserExport filesCurrencyNameShort formSymbolExchange rate

MessageSend userReceive userSend dateRead dateReply date

CountryNameLanguageCurrencyZoneProjects

ZoneNameCountryProjects 2. Work Flow of Report generation1) Write/Import Input reportsPurchasers write their draft versions of the Input Reports.They can1) Write data value directly: There will be no default values onany field of the Input Reports. All data has to be entered bythe user explicitly.2) Select the following value from listSupplier NameSupplier CitySupplier CountrySupplier Province

Purchaser can import the input report in Excel / XML formatwhich mostly comes from third party external system likeSAP or UFIDA.

External System prepares the files to import in accordancewith the predefined format.

Administrator can import the input report on behalf of anypurchaser.3. Functions List.1 Multiple Currency .1.1 Add, update, delete currency.1.2 Maintain the exchange rate .1.3 Auto-extend Exchange Rate .1.4 Send message to admin .2 Geographical Organization.2.1 Create, Update, Delete Projects .2.2 Create, Update, Delete Zones .2.3 Create, Update, Delete Countries.2.4 Maintain the relationships between Project, Zone andCountry. .2.5 Create, Update, Delete Services.2.6 Maintain project-service relationships.2.7 Enable Multiple Language values for zone/country/project..3 Purchase Classification .3.1 Create, Update, Delete Categories.3.2 Set Category Attributes.3.3 Export the definition of the classification in XML and Excelformats.3.4 Define the Classification Mapping Mechanism.3.5 Enable multiple languages for purchase item description..3.6 Enable multiple languages for the field name(s) of a compositedata structure. .4 Data Entry.4.1 Write, Import, Submit input reports.4.2 Validate input reports.5 Purchase Data Searching