You are on page 1of 9

OUM

AN.100 ANALYSIS SPECIFICATION
<Company Long Name>
<Subject>

Author:

<Author>

Creation Date:

November 22, 2010

Last Updated:

December 20, 2011

Document Ref:

<Document Reference Number>

Version:

DRAFT 1A

Approvals:
<Approver 1>
<Approver 2>

AN. DRAFT 1A ) 9 of 11 .doc Position Open and Closed Issues (v.2 Reviewers Name <Subject> File Ref: 214777267. 2011 1 DOCUMENT CONTROL 1.100 Analysis Specification Doc Ref: <Document Reference Number> December 20.1 Change Record 2 Date Author Version Change Reference 22-Nov-10 <Author> Draft 1a No Previous Document 1.

...... 2011 Contents 1 Document Control................................................................................................................................. 6 6.....................1 Open Issues...... 1 2....................................... ii 1......................................................... 6 <Subject> File Ref: 214777267............... ii 1................................................................................................................................................................................................................. ii 2 Overview...................................................................1 Surface Feature Descriptions............................... 4 4.........................................2 Reviewers. 3 4 Data and Behavior Analysis................................................... 4 4.................................................100 Analysis Specification Doc Ref: <Document Reference Number> December 20.....1 Change Record............................................................................................5 Examples.......... 4 5 Interface Analysis........................................................................................... 3 3................... 1 2........... 2 3 User Interface Descriptions....................................................................................................................... 1 2...............................2 User Interface Flow Descriptions.......................................doc Open and Closed Issues (v........ 1 2..............................................................................................................................................AN.......................................................................................................................................1 Data Analysis...........................4 Scenarios............................ 3 3............... DRAFT 1A ) 9 of 11 ............................................. 2 2.........................................6 Business Rules......................................................... 5 6 Open and Closed Issues............................................................. 2 2.................................................2 Major Features.........................................................................1 Business Objectives..............................................2 Behavior Analysis................................................................................................... 6 6.................................................................................................................................................................................................................................................... 2 2...........................................................................................................................2 Closed Issues...........................................................................................7 Assumptions...................................3 Definitions................................................

You will be able to address the following: 2. <Term 2>. <Term 3> Open and Closed Issues File Ref: 214777267.3 Definitions <Unique Term> <Term 1>.doc (v.2 • <Business objective 1> • <Business objective 2> Major Features <Use Case Name 1> <Use Case Brief Description> <Use Case Name 2> <Use Case Brief Description> 2. <Use Case Package> contains: • <Use Case Name> • <Use Case Name> Human Actors • <Actor1> • <Actor2> System Actors • <External System1> • <External System2> 2.1 Business Objectives <Use Case Package> provides you with the features you need to satisfy the following basic business objectives... ) 9 of 11 .Doc Ref: 2 OVERVIEW <Use Case Package> allows you to.

7 Assumptions • <Assumption1> • <Assumption2> • Open and Closed Issues File Ref: 214777267.024) for UC 2> • 2.6 Business Rules Business Rules inventory for this use case package: • <Business Rule name/number> • 2.Doc Ref: 2.5 Examples 2. ) 9 of 11 .4 Scenarios The following Use Cases Specifications contain scenarios that describe the sequence of steps and the collaborating actors participating to accomplish the functions within this package: • <Reference to Use Case Specification (RA.024) for UC 1> • <Reference to Use Case Specification (RA.doc (v.

1 Surface Feature Descriptions The following define the surface feature elements required to support this Use Case Package <UC Package Name>: <UC Name>: • <Form Description 1> • <Form Description 2> • <Report Description 1> <UC Name>: • <Form Description 3> • <Report Description 2> • <Report Description 3> • <Report Description 4> 3.doc (v.Doc Ref: 3 USER INTERFACE DESCRIPTIONS The following defines the user interface elements of <Use Case Package>… 3. ) 9 of 11 .2 User Interface Flow Descriptions The following defines the user interface flows that are required to support this Use Case Package <UC Package Name>: <UC Name>: • <Storyboard 1> • <Storyboard 2> <UC Name>: • <Storyboard 2> • Open and Closed Issues File Ref: 214777267.

) 9 of 11 .doc (v.1 Entity (Class) Data Analysis Attribute (Data Field) 4.2 Minimum Value Maximum Value Default Value Comments Behavior Analysis Open and Closed Issues File Ref: 214777267.Doc Ref: 4 DATA AND BEHAVIOR ANALYSIS 4.

Doc Ref: 5 INTERFACE ANALYSIS The <Use Case Package Name> is dependent on the following components and external systems. Use Case Name External System Name. amount. Component Name. UC 2 Open and Closed Issues File Ref: 214777267. Must comply with interface standard 6. Vendor UC Package 3 Create invoice An invoice message is sent for multiple products for the same vendor. or Service Name Messages Frequency Interface Requirements Message Parameters (data exchanged) UC 1 A/P system Voucher update This message is sent once per day.3 Voucher date.2.doc (v. ) 9 of 11 .

doc (v.2 ID Open Issues Responsibility Target Date Impact Date Responsibility Target Date Impact Date Closed Issues Issue Resolution Open and Closed Issues File Ref: 214777267.Doc Ref: 6 OPEN AND CLOSED ISSUES 6. ) 9 of 11 .1 ID Issue Resolution 6.