academic - ncc final - worldview

WorldView

A Sales Invoicing Prototype

and the system design of an Inventory & Invoicing package

Victor Diacono

NCC Education Student Number 97798 IADCS

December 2011

WorldView

IADCS Final Project | Victor Diacono – Student No 97798 2

______________

Table of Contents

Introduction Page 3

The WorldView Concept 5

Review of Competition 10

The Graphical User Interface 16

The GUI: Flowcharting 25

Pseudocode 33

Use Case Diagrams 36 Use Case Specifications 41

CRC Cards 69

State Charts 88

Data Dictionary 93

System Schema and Relationships 154

Appendix – The User Manual 155

Bibliography 161 Press CTRL and click the page number to go directly to the linked chapter

18086 words (inclusive of SSADM cards)

WorldView


________________

Part 1 Introduction

This project is being submitted as a Business Management (not Advanced

Programming) assignment as, rather than submitting a software package, it consists of the presentation of an Inventory and Invoicing System concept where the system is conceptually just one node hosted by a wider WorldView system

spread across diverse geographical locations and providing for networking (both professional and social) between users. Furthermore, it employs an innovative

design feature where the front end can be run from the core function of invoice production. This invoicing interface acts as the hub leading to windows, such as Customer and Stock Item, whose maintenance the invoicing GUI draws upon and

can be expanded beyond the submitted GUI functionality to other supporting functions (Receipts, Credit Terms etc).

Implementation of this conceptual ecology does not propose technological

innovation. Rather, it assumes available networking and SAD capabilities at the

service of a wider concept of the global village and effectively redefines this as the global office.

The full scope of this vision is however well outside the remit of this

assignment. What I present here is the overall model as described in Part 2 - The

Worldview Concept. This presentation comprises the following selection of illustrations meant to provide a top level overview for a comprehensive

understanding of both concept and proposed end product.

1. The Sales Invoice GUI prototype as sales is the commercial function the

full WorldView system is intended to support. All other system functions such as the creation and maintenance of stock items and customers, the

recording of sales receipts and maintenance of a debtors‟ ledger are functions enabling and supporting this one principal aim.

2. Documentation of this core GUI‟s algorithm by means of both flowchart

and pseudocode as well as a short user help document. 3. Illustration of the full system schema by means of Use Case diagrams and

specifications, and by a diagram of the database relationships. 4. A Data Dictionary and CRC Cards for the 18 most important files of the full

set of 50. 5. State Charts for the four most critical Use Cases.

The WorldView concept of linking a company‟s geographically detached operations by means of a network, where each location is a node, can address

the organisational interests of international commercial enterprises. In the age of globalisation where the commercial operations of large companies has become geographically far-flung, it is not only logistic and organisational gains that a

company makes when all its disparate software installations operate as one extranet. It also gains from a sense of cohesion and common purpose instilled

when staff feels it is part of one wider global community in the same employ.

WorldView


While the WorldView concept as explained in the Appendices can provide for the routine work-related interaction such as urgent requests for a stock item in which

other geographical locations are over-stocked, it is the possibility of social networking between members that cements the desired feeling of belonging to a

community.

International commercial enterprises who would make for a revealing case

study of requirements addressed by the WorldView Concept are countless but even in Malta there are a few. The Corinthia Group‟s Europe-wide and African

hotel operations would make one case for application of the concept, though not the actual Inventory and Invoicing package as theirs would be Hotels and Financial Control applications. Other possible local target enterprises for

Worldview-driven solutions are the McDonalds franchise owners who are expanding into eastern European cities, the Bortex Group with a manufacturing

point in China and Andrew‟s Feeds in the Middle East. And, though these are the local plant of foreign mother companies, there are also Actavis and Arrow Pharm in the pharmaceutical industry and Dedicated Micros (Malta) Ltd which also sells

on the local market.”

Return to Table of Contents

WorldView


_________________________

Part 2 The WorldView Concept

The Concept This project is a top level presentation of the design of a Sales, Purchases and Stock Control system as one component of a wider application concept of a

WorldView system where the application is configured as an independent cloud bridged to other installations (clouds) hosting the same application at

geographically diverse locations belonging to the same company, its suppliers, clients and competitors. While the benefits of inter-company, client and supplier

interaction are fairly evident, that between competitors takes the form of collaboration on industry-wide issues such as legislation and intelligence on client creditworthiness.

The wider WorldView model arose from the concept of an office system

operating as a standalone installation while interfacing with other installations world-wide. This standalone system could itself be hosted by a local network and by „standalone‟ I mean to say an installation which is not directly linked to others

but one where the interfacing of collaborating installations is driven by third party systems and infrastructure as a global extranet. This model makes no provision

for the possibility of cross-platform interfacing but assumes a uniform platform.

An extranet will of course also immediately raise security issues, and the

need of a setup to address them, but this project does not go into the technology but only offers a logical high level view of how said security can be enforced by

means of switches and parameters on the software side.

A Controlled World

Although the concept is of a world view of the core application and its surrounding clouds and third party hosting, this world view is of course a controlled Universe of Discourse (Paul Benyon-Davies, 2004). It is accessible only

to participants granted access privileges which are also graded according to security clearance for application functions and level of access, as well as with

regards to windows of the outside world which can be viewed and the dates and time in which viewing is permitted.

These outside windows are also controlled by genre or content as to which user level access is granted to whom. An example would be www.bbc.com and

www.facebook.com being made available to all user levels albeit at the time of day in which each individual user level, or sub-levels representing disparate geographical locations and time zones for the same user level, is on its lunch

break. On the other hand, www.standardandpoors.com would be accessible at all times but to upper management user levels only whereas www.ft.com would be

made available at all times to this user group but only during lunch breaks for

http://www.bbc.com/

http://www.facebook.com/

http://www.standardandpoors.com/

http://www.ft.com/

WorldView


user groups not requiring access to The Financial Times as a matter of occupation. In concrete terms, all users would be granted a concatenated

Internet permissions string consisting of the following components:

o User level o Days of week

o Time zone o Time of day

A hypothetical cxms--00002359 permission string assigned to the Standard & Poor‟s website, as an example, would allow access to the site by the Company

Executives user group (cx) from Monday to Sunday (ms) for all Time Zones (--) and between 00:00 and 23:59 hours (00002359), in other words 24/7 worldwide. A u1mf0312001230 privileges string assigned to Facebook and the BBC sites

would signify access to these sites to the User Level 1 group from Monday to Friday in Time Zone 3 between noon and 12:30 pm there. It is a multi-tiered and

hierarchical access privileges structure which can have levels added to it at implementation as well as the possibility of this user level string being over-

ridden by inclusions or exclusions at the individual user level if deemed a necessary function. And the ubiquitous issue of matter deemed objectionable, or dangerous in terms of attached malware, is automatically addressed too as

specific Internet access has to be granted rather than being available by default and requiring specific exclusion.

Apart from the above security genre and the more obvious one of firewalls for

the prevention of outside-world access and the introduction of malware via

attachments to legitimate communications, another genre to be addressed is that of what data is to be made available to the different levels of legitimate

communicants.

This issue is primarily addressed by the operational functions and views (both

as pre-defined groups and individually) being assigned to specific user levels over-ridden by privileges granted or denied at an individual user level. This

levels-based hierarchy and the possibility of individual inclusion or exclusion is a comprehensive privileges solution but data subsets would provide an added layer of protection physically separating data sensitive to individual user levels from

that requiring availability.

The user need only have access to the datasets of a database necessary to his or her occupation within the installation owner company, and those parts can consist of (a) a selection of rows, (b) a selection of columns or (c) a selection of

rows from a subset of columns as illustrated below.

WorldView


This presentation is not the complete core concern of my WorldView concept but a detailed overview of the core application employing a selection of

SSADM methodology tools. The Use Case Specifications cover the full application but system files represented by the Data Dictionary, CRC Cards and State Chart

diagrams are only a subset of the complete system. Apart from serving the purpose of representing that subset, they also demonstrate how the full core system‟s design would be presented as a completed blueprint for the developer.

The Community of Practice The global extranet concept dovetails with the Communities of Practice theory of

the researcher and management consultant Etienne Wenger who in his homepage (http://www.ewenger.com) states that “the basic idea is that human

knowing is fundamentally a social act. This simple observation has profound implications for the way we think of and attempt to support learning”. Supplant „learning‟ with „commercial organization and cooperation‟, a link not infrequently

made and Wenger is after all also a management consultant, and the WorldView concept has a previously-conceived framework to which it can be applied. And

the “design of more knowledge-oriented organizations” is also one of the aims espoused in his homepage.

Wenger and J.M. Swales (1990, p 22) have an initial common thread

running through their core theories on what constitutes a special interest

community despite divergences appearing a chasm apart at face value. That chasm, however, only develops once Wenger forks out in the direction of a

corporate application boxing underlying theory into a marketable off-the-shelf package, and Swales into a discourse unfettered by the need of moulding a final, clearly defined product for the “crass world of commerce” (Schriver 1997, p94).

Frederick Herzberg (in Swales 1990) supports this view when describing the Discourse Community as a set of unconsolidated ideas “lacking a settled notion”.

Wenger‟s credit lies in remoulding Swales‟ Discourse Community into a commercially-defined Community of Practice.

My WorldView concept can be seen as part of a social learning system in line with Wenger‟s twin criteria for its constitution, namely social competence and

personal experience when seen beyond their strict definition, as these are attributes inherent to effective participation at the workplace and one‟s occupation. The social competence in WorldView arises from the subject

community, i.e. the system‟s users, being active in its particular field of commerce. And personal experience is a product of exposure to the genre‟s world

view, gained from interaction with superiors, collaborators and subordinates.

Wenger identifies three Modes of Belonging - engagement, alignment and

imagination which occasionally interact – and all three are evident in the WorldView concept.

http://www.ewenger.com/

WorldView


Engagement is readily identifiable in the forms of user participation elicited by the wider WorldView system. It amounts to a joint activity between users of

similar or diverse security levels, albeit subject to level restrictions, on the one hand and the system outside the core component on the other. Furthermore, the

wider system outside the core application possesses no “carefully arranged” interaction (Faigley 1986, p530) unlike the core application which is „egocentric‟ (ibid p532) as it describes a mechanical process. Indeed, the core system cannot

be other than egocentric as it has to perform precise mechanical functions such as keeping stock records, issuing sales documentation, recording sales tax

transactions and storing debtor and creditor records.

Imagination, as defined by Wenger for the purposes under review, results

from users constructing an image of themselves performing a common, community-wide task. It concerns the user envisioning predefined document

printouts, mandatory sales tax submissions, and record-keeping functions as the end-result towards which each single transaction starts off with in mind. In other words, imagination focuses the user on the artifact to be produced.

Alignment is the activity which ensures effectiveness of processes outside

the user‟s direct engagement, such as subsequent issuing of debtor statements of account or sales tax submissions by other users, being a correct report or

summary of the related transactions. A clear relation between imagination and alignment is evident in this example.

The dominant attribute in the three Modes of Belonging is interaction between them. And whereas engagement interacts closely with alignment to

instill purpose for the subsequent reporting and summarization tasks, alignment is the dominant mode as users are aware from the outset that their input lays the groundwork for a subsequent task.

WorldView can be also termed a “social container of the competences”

(Wenger 2000, p229) as it is strong on shared repertoire of resources in occupational language, routines and artifacts. It is, by the mechanical nature of the core application, replete with communal artifacts in the shape of tools,

software functions and symbols employed in a sales or distribution environment. Swales defines such artifacts as a “specific lexis of technical terminology” (1990,

p26), albeit with speech communities in mind. He dubs the phenomenon an “inbuilt dynamic… realized through community-specific abbreviations and acronyms” (ibid p26).

Wenger‟s Community of Practice theory may be seen in a facile manner as

a statement of the obvious and what is already in place by accident, and which need only be organized into a unified approach. And this criticism has indeed been leveled at his theory before yet such criticism only helps confirm its validity

as the credit to his Community of Practice lies just there, in turning what was a loose or unidentified system or organization into a cohesive framework of

commercial interaction. Community of Practice is, largely, what should have been a fairly obvious model given the strident progress in information communication,

WorldView


and its merit lies in decomposing the philosophy lying behind a social application to reassemble it in a form which is both effective in its egocentric function as well

as capable of reaping the benefits of communitarian interaction aimed at performing the original function in greater depth and effectiveness.

Ultimately, however, any theory‟s test lies in its profane application which,

with Wenger, lies in the Community of Practice‟s mode of implementation in the

corporate world. Does it fit into this environment like a plug-in operating independently and generating noise? Or does it blend seamlessly beneath other

layers as a bottom tier in the corporate organizational architecture, driving the upper tiers as an effective, silent and invisible system of operation? The test therefore lies in equating visibility with failure and transparency with success.


WorldView


________________________

Part 3 Review of Competition

I have chosen to review a number of the lesser known financial applications as I

felt this would give me the opportunity to evaluate diverging design features „in the raw‟ where any single appealing feature, function or colour scheme in one product can be adopted and enmeshed with features from others. This approach

allows me to review competing GUI features but still come out with original design, as against the top sellers‟ more professionally developed and polished

GUIs which can influence one‟s final design before it is allowed to evolve.

Moreover, the GUI of the betterknown products such as Sage Line 50,

Quicken and MS Money (discontinued in 2009 but still available as freeware) would have had too much of the rigid corporate look-and-feel I have avoided in

my design. Assessment of these established products would however still come in useful were the WorldView system to be fully developed. An inspection of their GUIs‟ labelling would for instance provide an immediate and comprehensive idea

of what the sales invoicing interface and supporting GUIs require in terms of fields, consequently leading to a comprehensive schema covering all the possible

data requiring recording in an inventory and sales system. The reviewed GUIs appear below accompanied by notes and observations

on their features.

WorldView


GST / VAT Invoicing http://gst-vat-invoicing.lastdownload.com/download.html

While I have researched a number of competing products to glean attractive

design elements from which I can adapt my own original interface, this layout was my point of departure from a negative point of view. It personifies the GUI

look-and-feel (and individual bits of design) I intend avoiding, namely that of a bland and unattractive interface designed solely around functionality which, even in its own right, is at times dubious.

Apart from the very bland grey/white colour scheme, the Line Items and

Payments group boxes jar both in their background colour as well as the disproportionate size. Moreover, there is too little information being recorded for the sales items which miss critical data elements such as sales discount,

sales person and credit terms.

There is also the grid-look layout, to the items pane, which my design discards in the itemisation pane in favour of an item-at-a-time display. The grid, since it is admittedly necessary, I have relegated to a dedicated tab page

so it can be brought up for viewing purposes only when necessary, without being the actual data entry pane.

The Totals itemisation pane at bottom right I shall be adopting as an

ergonomically valid display and summary of all relevant amounts and figures. I

http://gst-vat-invoicing.lastdownload.com/download.html

WorldView


have however opted to dedicate a tab page to this element too, so as to create space for the invoice‟s commissions-related information and leave the data-

entry pane uncluttered.

WorldView


SBII – Simple Business Invoicing & Inventory http://www.5star-shareware.com/Windows/Business/InventorySystems/simplebiz-inventory-download.html

While this GUI possesses an appropriate colour scheme, there is the ergonomic drawback of (a) the unattractive feature of blank items rows appearing upon

filling-in of data entry in the previous row and (b) the labels‟ background being too light, in comparison to the textboxes‟ back colour, for clear focus. The

right-hand quarter of the window being left totally blank is another design shortcoming.

This product‟s most functionally valid and useful feature is the adoption of a number of tab pages to enable the availability of as much information

(historical included) as necessary while avoiding on-screen clutter. Tab pages shall be an integral part of my design too.

http://www.5star-shareware.com/Windows/Business/InventorySystems/simplebiz-inventory-download.html



WorldView


SliQ Invoicing & Quoting http://www.sliqtools.co.uk/

This is an attractive layout and the only area of improvement I would have

adopted is in the half-blue and half-white approach. An additional colour or two (with attention against gaudiness) would have made it stand out more for

reasons of visual focus on the window segment in use at any particular time.

WorldView


Financial Accounting – Enterprise Edition http://www.softpedia.com/get/Others/Finances-Business/DRPU-Financial-Accounting-Enterprise-Edition.shtml

This is an attractive layout of all the basic textboxes required for invoice

production. Even the pale-blue colour scheme is right as this colour does not stand out unnecessarily and is gender neutral. My adopted colours shall in fact be sky blue but with light cyan labelling to make the label text stand out.

The button design is however not the one I have in mind as my design

choice is one that discards the staid office feel in favour of a more contemporary look. And while the white backcolor to the panes is not unattractive, my adoption of white shall be less pronounced as the textboxes

in my GUI will not stand adjacent to each other but apart.


http://www.softpedia.com/get/Others/Finances-Business/DRPU-Financial-

http://www.softpedia.com/get/Others/Finances-Business/DRPU-Financial-

WorldView


_____________________________

Part 4 The Graphical User Interface

The design concept of the Sales Invoice interface is built around the idea of a

front end as appealing and user friendly as possible while retaining, by means of verification and validation at the coding level, the high degree of discipline and control at data input level which is a prerequisite for any financial package.

However, while the envisioned application will possess and enforce a level

of control over the user as a financial application can never be a loose collection of functions allowing freedom of operation (for reasons of internal control as well as for legislative obligations), the design concept is one that does not convey a

feeling of a tight application controlled by rigid procedures. This „loose‟ look-and-feel has even been extended to choice of colour scheme and it steers clear of the

staid dark blues, greys and greens generally associated with the financial applications usually found in the office and other commercial environments. It is for this reason too that the „grid look‟ of input panels consisting of cells and rows

has been avoided.

The GUI‟s principal feature, in terms of innovation, is its hub nature in relation to the data maintenance files it draws upon. This feature, already mentioned in the Introduction, operates by bringing a textbox (such as

Customer) in focus with a mouse click, then clicking the Shortcut button to go directly to the related data entry window. The principal benefit lies in the feeling

of compactness of operating an invoicing job without leaving the Sales Invoice window whenever maintenance of supporting data (such as the creation or modification of Customer data) is required. This compactness also saves on time

and lost focus inherent in minimizing the invoicing window, navigating around the main menu to locate the other window and minimizing it once the data

maintenance has been done, and re-maximising Sales Invoice. With the shortcut, the second window need only be exited and onscreen window clutter is avoided. The shortcut feature would however still be subject to the user access restrictions

set into the system by the administrator.

The GUI coding also addresses other security issues such as disallowing the deletion of invoices which have been posted to the „Sales Ledger‟. The sales

ledger is a virtual file as a listing of a customer‟s purchases is derived by sorting and searching the transactions file. This design feature of virtual files has been adopted to eliminate data redundancy with its negative implications. However, it

is accepted that a balance often has to be struck and, where a file is considered to be of such a critical nature as to warrant duplication of data, an element of

redundancy can be inevitable. In fact, the taxtrans file has been introduced into my design, in spite of its effectively being a duplication of a selection of data elements from transactions, to illustrate appreciation of this fact. This being a

system blueprint, the developer will of course still be free to modify at implementation as he or she deem fit.

WorldView


Another design feature introduced in the Sales Invoicing window is that of the tab pages which allow for an abundance of analytical and historical

information not usually present in an invoicing interface (such as full customer details and statistics, and sales commission statistics) without creating an

abundance of clutter. This takes the concept behind the shortcut, that of having all related maintenance just two mouse clicks away, a step further by presenting in the Sales Invoice window all related information that has already been

recorded, thus precluding the use of even the shortcut button itself for existing information.

The tab pages have been designed so as to populate upon clicking of the related data entry pane‟s textbox prior to input. Their background colour is a

uniform pale blue so as to avoid the nuisance of the flashing effect of rapidly-changing screen colour as the user is creating an invoice, the only exception

being the Listing tab because of its grid‟s background. However, the GUI carries an Unsync button in the top righthand corner of the window to disable this feature should the user find it a distraction. Unsynching will also provide

improved system performance in the event of hardware or the hosting system not being sufficiently strong to effect tab population without delays in screen

refresh.

Additional functionality emanating from the fields and their interaction has been designed into the GUI where applicable and of a practical nature. One such function is that of playing a sound, video or image file attached to a stock item.

These files form part of the stock item record only insofar as the filename is recorded as a data element; image, sound or video are only „played‟ upon clicking

as playing these files by default for each stock item would impact on system performance to a very high extent.

The Sales Invoice GUI, consisting of data entry pane and tab pages, appears on the following pages. The working prototype, however, does not

employ the full functionality drawn into the interface design as a number of buttons and one of the tab pages illustrate envisaged functions which have not been coded in the submitted software. The uncoded buttons comprise Delete,

Update, Email, Print and the Shortcut button intended to take the user directly to the primary window related to the textbox currently in focus. The omitted tab is

Media Gallery whose function is that of producing an image, sound or video clip of a stock item when one is attached to the item.

WorldView


The Sales Invoice screen: data entry pane and default Listing tab

page

WorldView


The data entry pane

WorldView


The Listing tab page

WorldView


The Customer tab page

WorldView


The Financials Tab Page

WorldView


The Stock Item tab page

WorldView


The Gallery tab page


WorldView


___________________________________________

Part 5 The GUI Algorithm: Flowchart and Pseudocode

This section presents the flowcharted Sales Invoice algorithm together with a

pseudocode listing. For ease of readability, the flowchart is divided into two with buttons other than Save and Quit on a separate chart, and pseudocode segments are in alternate font colours.

Main Sales Invoice chart page 26

Secondary chart for button clicks 31 Pseudocode listing 33

WorldView


Sales Invoice – Principal Flowchart

Display

Sales Invoicing Window

START

Next_

invoice_no

Found

?

Initialisation

Sales Invoice radio button = enabled

Sales Return radio button = disabled

From Stock radio button = enabled

Free Text radio button = disabled

Date = today

Wholesale radio button = enabled

Consumer radio button = disabled

Line_no = 0

Next_invoice_no = 0

Gdisc = 0

Read Next_invoice_no

Display Next_invoice_no

Input Next_invoice_no

Find Next_invoice_no

Yes

Display & populate

Invoice Type group box

Display & populate

Header group box

Display Add Item group box

& populate it with inovice’s

first line record

No

B

Display & populate

Listing group box

A C

Accept

Next_

invoice_no

?

NoYes

WorldView


A

Display & populate

Customer

group box

Display & populate

Gallery

group box

Display & populate

Stock Item

group box

Display & populate

Financials

group box

Click the required

row in Listing tab

Populate

Add Item group box

with selected row

No

Other

Add Item

line required

?

Yes

Invoice records

marked as ‘posted

to sales’

?

Yes

No

Input Date

Input Customer code

Display customer

name

Input Terms

Input Quotation ref

A

‘No’

E

CB

WorldView


A

Input Sales Person

Input Order Ref

Input Global Discount %

Gdisc = Global Discount

Input Stock Ref

Display stock

description

Free Text

radio button

clicked

?

No

Yes

Make Free Text

multiline textbox

visible

Input free-text item

description

Input Quantity

Consumer

radio button

clicked

?

Yes

Read consumer price

No

Display consumer price

Net =

(consumer_price * Quantity)

Read wholesale price

Display wholesale price

Net =

(wholesale_price * Quantity)

A

‘No’

E

E

D

WorldView


A

Item Discount = Gdisc

Accept Item

Discount

?

Input Item DiscountNo

Yes

Plus Tax =

(Net * (1 – (Item Discount / 100))) * ((Item Tax / 100) = 1)

Add Item

button clicked

?

No

Yes

Line_no = Line_no + 1

Populate first blank row in

Listing tab with this record

Save record to a

temporary transactions file

Save record to a

temporary tax file

Save button

clicked

?

No

E D

Yes

Save Temp_trans

records to

Transactions file

Save Temp_tax

records to

Tax file

A

WorldView


Delete Temp_trans records

Delete Temp_tax records

END

A

WorldView


Sales Invoice – Button Click Flowchart

Email button

clicked

?

No

YesOutput invoice to

PDF format

Attach PDF file

to email

Print button

clicked

?

No

Help button

clicked

?

Output invoice to

line printerYes

YesShow

Help window

Populate window

with Help file

No

Next Invoice

button clicked

?

YesNext_invoice_no =

Next_invoice_no + 1

Clear

Sales Invoice

window

Find

Next_invoice_no

Next_invoice_

no Found

?

Yes

Populate Sales

Invoice window

with next invoice

Display message

‘no more invoices

in this direction’

No

Previous

Invoice button

clicked

?

YesPrev_invoice_no =

Prev_invoice_no - 1

Clear

Sales Invoice

window

Find

Prev_invoice_no

Prev_invoice_

no Found

?

Yes

Populate Sales

Invoice window

with previous

invoice

Display message

‘no more invoices

in this direction’

No

Shortcut

button clicked

?

YesRead name of

object in focus

Find window of

same name

No

Show selected

window

Window

Found

?

No

Display message

‘No database

table for this field’

Accept & Save

input

Quit window and

return to

Sales Invoicing

Yes

A

No

START

Send email

No

WorldView


A

Clear

button clicked

?

YesClear Sales

Invoicing window

No

Delete

button clicked

?

Yes

Display message ‘Invoice

posted to Sales Ledger

and cannot be deleted’

Yes

Transactions

marked as

‘posted’

?

No

Delete records

from Transactions

file

Delete records

from Tax fileNo

No

END

Update button

clicked

?

Transactions

marked as

‘posted’

?

Yes

Display message

‘Invoice is

already posted’Yes

Display message

‘Invoice posted’No

No


WorldView


The Pseudocode

BEGIN

SALES INVOICE = YES

SALES RETURN = NO

FROM STOCK = YES

FREE TEXT = NO

FREE TEXT TEXTBOX = DISABLED

DATE = TODAY

WHOLESALE = YES

CONSUMER = NO

LINE_NO = 0

NEXT_INVOICE_NO = 0

GDISC = 0

READ NEXT_INVOICE_NO

DISPLAY NEXT_INVOICE_NO

ENTER NEXT_INVOICE_NO //allows over-writing of next_invoice_no for viewing purposes

IF NEXT_INVOICE_NO FOUND

THEN BEGIN

POPULATE INVOICE TYPE GROUPBOX

POPULATE HEADER GROUPBOX

POPULATE ADD ITEM GROUPBOX WITH Line_No 1 //selected invoice‟s first record

POPULATE LISTING TAB

IF OTHER LINE_NO REQUIRED THEN BEGIN

CLICK LINE-NO IN LISTING TAB

POPULATE ADD ITEM GROUPBOX WITH

SELECTED LINE_NO

END

POPULATE CUSTOMER TAB

POPULATE FINANCIALS TAB

POPULATE STOCK ITEM TAB

POPULATE GALLERY TAB

END

IF NEXT_INVOICE_NO UPDATED //checks if invoice posted to sales ledger -disallows

modification if True

THEN DISPLAY MESSAGE „This invoice posted to Sales Ledger – it can be viewed but not

modified‟

ELSE BEGIN

REPEAT

SELECT DATE //selection of new date overwrites today‟s default system date

SELECT CUSTOMER

DISPLAY CUSTOMER NAME

SELECT TERMS

SELECT SALES PERSON

ENTER ORDER REF

ENTER GLOBAL DISCOUNT PERCENTAGE

GDISC = GLOBAL DISCOUNT // to assign to individual item discount fields as

default

ENTER STOCK REF

WorldView


DISPLAY STOCK DESCRIPTION

IF FREE TEXT RADIO BUTTON CLICKED

THEN BEGIN

DISABLE STOCK REF BOX

ENABLE FREE TEXT TEXTBOX

ENTER FREE TEXT

END

ENTER QUANTITY

IF CONSUMER RADIO BUTTON CLICKED

THEN BEGIN

READ CONSUMER PRICE

DISPLAY CONSUMER PRICE

NET = (CONSUMER PRICE * QUANTITY)

END

ELSE BEGIN

READ WHOLESALE PRICE

DISPLAY WHOLESALE PRICE

NET = ((RRP – RRP_MARGIN) * QTY)

END

ITEM DISCOUNT = GDISC //assigning the value of the global discount to

this line‟s discount

ENTER ITEM DISCOUNT //allows over-writing of the default global discount

PLUS TAX = (NET * (1 – (ITEM DISCOUNT/100))) * ((ITEM TAX/100) + 1)

IF ADD ITEM BUTTON CLICKED

THEN BEGIN

LINE_NO = LINE_NO + 1

POPULATE LISTING TAB PAGE ROW

SAVE ROW TO TEMP_TRANS FILE

SAVE ROW TO TEMP_TAX FILE

END

UNTIL SAVE BUTTON CLICKED

SAVE TEMP_TRANS RECORDS TO TRANSACTIONS FILE

CLEAR TEMP_TRANS

SAVE TEMP_TAX RECORDS TO TAX FILE

CLEAR TEMP_TAX

END

SELECT CASE BUTTON_CLICKS

CASE UPDATE CLICKED

IF POSTED != „Yes‟

THEN MARK TRANSACTIONS RECORDS AS POSTED

ELSE DISPLAY „This invoice has already been posted to the Sales Ledger‟

CASE EMAIL CLICKED

OUTPUT INVOICE TO PDF FORMAT

SEND PDF FILE AS ATTACHMENT TO EMAIL

CASE HELP CLICKED

BRING UP HELP WINDOW

POPULATE WINDOW WITH HELP FILE

CASE PRINT CLICKED

OUTPUT INVOICE TO LINE PRINTER

CASE NEXT INVOICE CLICKED

NEXT_INVOICE_NO = (NEXT_INVOICE_NO + 1)

CLEAR WINDOW

WorldView


FIND NEXT_INVOICE_NO

IF NOT FOUND

THEN DISPLAY „No more invoices in this direction‟

ELSE POPULATE WINDOW WITH NEXT INVOICE

CASE PREVIOUS INVOICE CLICKED

NEXT_INVOICE_NO = (NEXT_INVOICE_NO - 1)

CLEAR WINDOW

FIND NEXT_INVOICE_NO

IF NOT FOUND

THEN DISPLAY „No more invoices in this direction‟

ELSE POPULATE WINDOW WITH NEXT INVOICE

CASE SHORTCUT CLICKED

READ NAME OF FOCUSED OBJECT

FIND WINDOW WITH SAME NAME

IF FOUND

THEN BEGIN

SHOW WINDOW

ACCEPT INPUT

END

ELSE DISPLAY „No window available for this field‟

END SELECT

CASE CLEAR CLICKED

CLEAR WINDOW

CASE DELETE BUTTON CLICKED

IF POSTED != „Yes‟

THEN BEGIN

CLEAR RECORDS FROM TRANSACTIONS FILE

CLEAR RECORDS FROM TAX FILE

END

ELSE DISPLAY „Invoice posted to Sales Ledger. It can be viewed but not deleted‟

CASE QUIT BUTTON CLICKED

CLEAR WINDOW

RETURN TO PREVIOUS SCREEN

CASE SAVE BUTTON CLICKED

SAVE LISTINGS TAB CONTENT TO TRANSACTIONS & TAX_TRANS FILES

END CASE

END


WorldView


_____________________

Part 6 Use Case Diagrams

The full system Use Case Diagram is being presented in two charts on the

following pages as representation on one diagram would have been too cluttered for easy comprehension.

The first diagram, representing the full system except for the Year End process, appears first. Next comes the year-end diagram representing what is an

optional procedure consisting of the removal of all transactions matched by the end of the financial year. An instance of such matching is where the amount of a sales receipt has been flagged as amounting precisely to the total of any number

of sales invoices (less any sales credits, part-payments and discounts) against which it has been received. Transactions carried forward to the next financial

year would then consist of unmatched, therefore penging, records only. When this option is not chosen, all transactions, both matched and unmatched, are carried forward into the next financial year. This latter option however has the

drawback of ever-growing system files with the attendant deterioration in system performance, more information unnecessarily available for the user‟s perusal and

an increase in the potential for corruption of data as files keep growing in size.

WorldView


Use Case Diagram – Principal Algorithm

Sales RepClerk

Sales Order

Client

Stock

Client Type

Rate of Exch

Currency

Purch Order

Supplier

Supp Type

Image

Sound

Video

Shelf

Warehouse

LocationStock Type

Stock Cat

Stock Class

Transactions

Tax Type

Payment Ref

Trans Type

Tax Trans

Receipt Ref

Purch Ref

Sale Ref

Commission

Sales Rep

Rep Type

Clerk

Admin

Admin

Admin

System

System

continues/...

Clerk

Legend:

Green - principal storage files

Blue - secondary files read by principal files

Brown - parameter files read by secondary files

Arrows point in direction of file being read from

Stock Parent

WorldView


Match Payment

Cancel Trans

Match Receipt

Unmatch Rec

Disc Received

Sale Return

Sale

Payment

Purch Return

Purchase

Unmatch Pyt

Disc Allowed

User

User

Transactions(continued)

Receipt

Legend:

Green - principal storage files

Blue - secondary files read by principal files

Brown - parameter files read by secondary files

Arrow point in direction of file being read from

WorldView


Use Case Diagram – End-of-Year Algorithm

Stock

Sale Ref

Year End Process

Legend:

Red - blank file created in new financial year

Green - only unmatched records copied to new

financial year

Blue - full file copied to new financial year

Brown - only unprocessed records copied to new

financial year

Arrows point in direction of files being read from

continues/...

Sales Order

Supp TypeSales Rep

Stock Type

Rep Type

Commission

Receipt Ref

Rate of Exch

Tax Trans

Transactions

Warehouse

Client

Client Type

Town

Postcode

Country

Purch Ref

Stock ClassPurch Order

Payment Ref

Trans Type

Supplier

Stock Cat

Stock Parent

Shelf

Tax Type

Video

Image

Sound

Currency

Location

WorldView


Year End Process(continued)

ImagePurch Ref

Purch Order

Stock Cat

Stock ParentSupp Type

Supplier

Payment Ref

Stock Type

Stock Class

Country

Post Code

Town

Client

Client Type

Receipt Ref

Tax Type

Trans Type

Shelf

Rep Type

Commission

Sales Rep

Sales Order

Sale Ref

Tax Trans

Transactions

Currency

Sound

Video

Location

Rate of Exch

Warehouse

Stock

Legend:

Red - blank file created in new financial year

Green - only unmatched records copied to new

financial year

Blue - full file copied to new financial year

Brown - only unprocessed records copied to new

financial year

Arrows point in direction of file being read from


WorldView


_________________________

Part 7 Use Case Specifications

This project, as mentioned in the concept essay, is a representation of the final

blueprint and only a subset of the system has been presented. In the case of the Use Case specifications below, however, it has been deemed necessary to present the full system so as to illustrate it in its entirety.

The illustrated files are those conceptualised as a physical file and others,

such as Debtor and Creditor accounts, have not been represented in a physical state as they can be viewed as symbolic „files‟ extractable by coding from the transactions file which records every single event.

The system has been conceptualised in a minimalistic manner and devoid of

any duplication except for the tax transactions file where duplication was deemed necessary as mirrored duplication in this case safeguards against loss of data in a very critical area. However, this blueprint is not intended as one to be followed

religiously and the developer can create redundancy or indeed modify in any other way as deemed appropriate. Indeed, he or she would have to as

functionality such as, for instance, stock batch numbers is not included since this genre of data field does not require relating to other files and is a simple matter of inserting new fields into the design as and where required.

The next pages display the full system Use Case Specifications.

WorldView


Name: Transactions Card No: 001

Actors: None

Goal: Create a transaction

Use-case Relationships

Extend: Tax Transactions, Cancel Transaction, Sales Rep, Stock,

Transaction Type, Tax Type, Commission, Sale Ref, Purchase Ref,

Payment Ref, Receipt Ref

Include: Unmatch Payment, Unmatch Receipt, Sale, Sale Ref, Match Payment,

Match Receipt, Purchase, Purchase Return, Payment, Receipt,

Discount Allowed, Discount Received External Associations: None

Description

Index Actor event

None

1 System creates a transaction record

Alternatives

Index Actor event None

Name: Stock Card No: 002

Actors: User

Goal: Create or maintain a stock item


Extend: Sales Order, Client, Stock Parent, Shelf, Sound, Image, Video,

Transactions, Rate of Exchange

Include: Purchase Order, Supplier External Associations:

None

Description

Index

Actor event

1

System creates a record where a stock code being created or maintained is allocated

as a component (child) or another stock item (parent)

Alternatives

Index

Actor event

None

WorldView


Name: Stock Parent Card No: 003

Actors: None

Goal: Assign a stock code as a component of another stock code


Extend: Include: Stock

External Associations: None

Description

Index

Actor event

None

1

System creates a record where a stock code being created or maintained is allocated as a component (child) or another stock item (parent)

Alternatives

Index

Actor event

None

Name: Stock Class Card No: 004

Actors: Admin

Goal: Create a Stock Class


Extend: None

Include: None External Associations:

None

Description

Index Actor event

1 Admin creates a Stock Class for categorisation of stock items for purposes of

summarisation

Alternatives


WorldView


Name: Stock Cat Card No: 005

Actors: Admin

Goal: Create a Stock Category


Extend: Stock Class

Include: External Associations:

None

Description

Index Actor event

1 Admin creates a Stock Category for categorisation of stock items for purposes of

summarisation 2 Admin allocates the Stock Category to a Stock Class

Alternatives


Name: Stock Type Card No: 006

Actors: Admin

Goal: Create a Stock Type


Extend: None


None

Description

Index Actor event

1 Admin creates a Stock Type for categorisation of stock items for purposes of

summarisation 2 Admin allocates the Stock Type to a Stock Category

Alternatives


WorldView


Name: Location Card No: 007

Actors: Admin

Goal: Create a stock location


Extend: None

Include: None External Associations: None

Description

Index Actor event

1 Admin creates a geographical location to which warehouse/s are to be allocated

Alternatives

Index Actor event

None

Name: Warehouse Card No: 008

Actors: Admin

Goal: Create a warehouse


Extend: Location

Include: External Associations: None

Description

Index Actor event

1 Admin creates a warehouse to which shelf references will be allocated

2 Admin allocates warehouse to a location

Alternatives

Index Actor event

None

WorldView


Name: Shelf Card No:

009

Actors: User

Goal: Creates a shelf reference


Extend: Warehouse


Description

Index Actor event

1 User creates a shelf reference

2 Admin allocates shelf references to a warehouse

Alternatives

Index Actor event

None

Name: Image Card No: 010

Actors: User

Goal: Allocate an image file to a stock item


Extend: Stock


Description

Index Actor event

1 User allocates the filename of an image of the stock item to the stock item record

Alternatives

Index Actor event

None

WorldView


Name: Video Card No: 011

Actors: User

Goal: Allocate a video file to a stock item


Extend: Stock


Description

Index Actor event

1 User allocates the filename of a video file (such as a product presentation) to the

stock item record

Alternatives

Index Actor event

None

Name: Sound Card No: 012

Actors: User

Goal: Allocate a sound file to a stock item


Extend: Stock


Description

Index Actor event 1

User allocates the filename of a sound file (such as a product description) to the stock item record

Alternatives

Index Actor event

None

WorldView


Name: Purchase Order Card No: 013

Actors: User

Goal: Record a sales request


Extend: Supplier

Include: Stock External Associations:

Supplier

Description

Index Actor event

1 User identifies or is advised of stock items for acquisition

2 User issues a Supplier with a Purchase Order for the stock item/s

Alternatives

Index Actor event

A2 Stock item/s out of stock or not sufficient quantity in stock A2.1

Unfulfilled quantity kept on order, if still required, when the Purchase Order is checked against receipt of goods

A2.2 User confirms or rejects unfulfilled quantity when advised of availability by Supplier

A2.3 Stock item balance marked as 'undelivered' if no longer required

Name: Purchase Return Card No: 014

Actors: User

Goal: Create a Purchase Return transaction


Extend:

Include: Transactions External Associations:

Supplier

Description

Index Actor event

1 User creates a Purchase Credit Note both for stock items from a Purchase Order

and from a direct Purchase Invoice

Alternatives


WorldView


Name: Supplier Card No: 015

Actors: User

Goal: Create or maintain a supplier record


Extend: Supplier Type

Include: Stock External Associations:

Supplier

Description

Index Actor event

1 User creates a record for a supplier whose supplies will be recorded in his account

for Creditor Control purposes or for purchase statistics purposes in case of Cash Purchases

2 User maintains Supplier record with changes to static details

Alternatives

Index Actor event

None

Name: Supplier Type Card No: 016

Actors: Admin

Goal: Create a classification type


Extend:


Description

Index Actor event

1 Admin creates a classification Type to which individual suppliers are to be allocated

for purposes of summarisation of purchases by supplier category

Alternatives

Index Actor event

None

WorldView


Name: Purchase Ref Card No: 017

Actors: None

Goal: Provides a reference number for a purchase transaction


Extend: Transactions


None

Description

Index Actor event

None

1 System reads this single-record file to read the stored reference number; 1 is

added to the retrieved number and assigned to a Purchase Invoice or Purchase Credit document

2 System over-writes the read file record with the newly-generated number for the next read

Alternatives


Name: Sales Rep Card No: 018

Actors: Admin

Goal: Create or maintain a Sales Rep record


Extend: Client Type, Stock

Include: External

Associations: Client

Description

Index

Actor event

1

User creates a record for a sales rep whose sales will be recorded in his account for

Sales Commissions purposes 2 User maintains Sales Rep record with changes to static details such as commission

rate

Alternatives

Index

Actor event

None

WorldView


Name: Rep Type Card No: 019

Actors: Admin



Extend: Sales Rep


Description

Index Actor event

1 Admin creates a classification Type to which Sales Reps are to be allocated for

purposes of summarisation of sales by Sales Rep

Alternatives

Index Actor event

None

Name: Sales Order Card No: 020

Actors: Sales Rep, User

Goal: Record a sales request


Extend: Stock


Client, Consumer

Description

Index Actor event

1 Client places a Sales Order with the Sales Rep (via handheld computer) or with

the user (via desktop station) or Consumer places Sales Order with the User (via desktop station)

2 Sales Rep or User record the order

Alternatives

Index Actor event

A2 Stock item out of stock or not sufficient quantity in stock

A2.1 Unfulfilled quantity kept on order when the Sales Order is processed A2.2 Client or Consumer confirm or reject unfulfilled quantity when stock item is

replenished A2.3 Client or Consumer informed of unavailability if stock item not to be

replenished;

unfulfilled quantity marked as 'obsolete' or removed from order

WorldView


Name: Client Card No: 021

Actors: User

Goal: Create or maintain a client record


Extend: Client Type, Stock

Include: External Associations: Client

Description

Index Actor event

1 User creates a record for a client whose purchases will be recorded in his account

for Debtor Control purposes or for sales statistics purposes in the case of Cash Sale

2 User maintains Client record with changes to static details

Alternatives

Index Actor event

None

Name: Client Type Card No: 022

Actors: Admin



Extend: Client

Include: External

Associations: None

Description

Index

Actor event

1

Admin creates a classification Type to which individual clients are to be allocated for

purposes of summarisation of sales by client category

Alternatives

Index

Actor event

None

WorldView


Name: Sales Ref Card No: 023

Actors: None

Goal: Provides a reference number for a sales transaction




Description

Index Actor event

None

1 System reads this single-record file to read the stored reference number; 1 is added to

the retrieved number and assigned to a Sales Invoice or Sales Credit document 2 System over-writes the read file record with the newly-generated number for the next read

Alternatives


Name: Currency Card No: 024

Actors: Admin

Goal: Create a Foreign Currency


Extend: None


None

Description

Index Actor event

1 Admin creates a Currency to be allocated to Rates of Exchange for purposes of

overseas sale or purchase

Alternatives

Index Actor event

None

WorldView


Name: Rate of Exchange Card No: 025

Actors: User

Goal: Create a Rate of Exchange


Extend: Currency


None

Description

Index Actor event

1 User creates a Rate of Exchange, when required, to allocate to a foreign purchase

or foreign sale

Alternatives

Index Actor event

None

Name: Sales Card No: 026

Actors: User

Goal: Create a Sales transaction


Extend:


Client

Description

Index

Actor event

1

User generates a Sales Invoice from a Sales Order

or creates a Sales Invoice directly or enters a Cash Register sale

Alternatives

Index

Actor event A1 Stock item out of stock or not sufficient quantity in stock A1.1 From Sales Order: unfulfilled quantity kept on order when the Sales Order is

processed (see card no. 001) A1.2 From Sales Invoice: Sales Order created for unfulfilled quantity if Client indicates

need A1.3 From Cash Register sale: as in A1.2

WorldView


Name: Purchase Card No: 027

Actors: User

Goal: Create a Purchase transaction


Extend:


Supplier

Description

Index

Actor event

1

User generates a Goods Received Note from a Purchase Order

2

or creates a Purchase Invoice directly into the Creditor account

Alternatives

Index

Actor event A1 Stock item out of stock or not sufficient quantity in stock A1.1 From Purchase Order: unfulfilled quantity kept on order when the Purchase

Order is processed if quantity still required

Name: Trans Type Card No: 028

Actors: Admin

Goal: Create a Transaction Type



Include: External

Associations: None

Description

Index

Actor event

1

Admin creates a Transaction Type for categorisation of transactions for purposes of

recording as debit or credit and summarisation

Alternatives

Index

Actor event None

WorldView


Name: Tax Type Card No: 029

Actors: Admin

Goal: Create a Tax Type



Include: External

Associations: None

Description

Index

Actor event

1

Admin creates a Tax Type for categorisation of transactions for purposes of sales tax

accounting according to different tax rates and as a debit or credit, and for summarisation

Alternatives

Index

Actor event None

Name: Commission Card No: 030

Actors: None

Goal: Create a Sales Commission transaction




Description

Index Actor event

None

1 System creates a record where a commission is computed on a sale brought in by a

Sales Rep according to the commission rate applicable to the individual Sales Rep for a particular stock item

Alternatives


WorldView


Name: Payment Ref Card No: 031

Actors: None

Goal: Provides a reference number for a purchase payment



Include: External

Associations: None

Description

Index

Actor event

None

1

System reads this single-record file to read the stored reference number; 1 is added to

the retrieved number and assigned to a Purchase Payment 2 System over-writes the read file record with the newly-generated number for the

next read

Alternatives

Index

Actor event None

Name: Receipt Ref Card No: 032

Actors: User

Goal: Provides a reference number for a sales receipt


Extend: Include: Transactions

External Associations:

None

Description

Index

Actor event

1

System reads this single-record file to read the stored reference number; 1 is added to

the retrieved number and assigned to a Sales Receipt 2 System over-writes the read file record with the newly-generated number for the

next read

Alternatives

Index

Actor event A1 None

WorldView


Name: Match Payment Card No: 033

Actors: User

Goal: Matches a purchase payment against relevant transactions


Extend:


None

Description

Index Actor event

1 User matches a previously posted purchases payment against the purchase invoices,

purchase credits, payments on account and discounts received settled by the payment

Alternatives

Index Actor event A1 Payment does not match the selected purchase

invoices/credits/payments/discounts A1.1 User re-checks the supplier account's transactions for omitted matches A1.2 If over-payment effected, the unmatched balance is posted as 'payment on

account' A1.3 If under-payment effected, the balance on the transaction/s not fully allocated to

the

purchase payment are marked as 'amount outstanding'

WorldView


Name: Match Receipt Card No: 034

Actors: User

Goal: Matches a sales receipt against relevant transactions


Extend:


None

Description

Index Actor event

1 User matches a previously posted sales receipt against the sales invoices, sales

credits, receipts on account and discounts allowed settled by the receipt

Alternatives

Index Actor event A1 Receipt does not match the selected sales invoices/credits/payments/discounts

A1.1 User re-checks the client account's transactions for omitted matches A1.2 If over-payment received, the unmatched balance is marked as 'receipt on

account' A1.3 If under-payment received, the balance on the transaction/s not fully allocated to

The sales payment are marked as 'amount outstanding'

Name: Unmatch Payment Card No: 035

Actors: User

Goal: Reverses an existing Payment Match


Extend:


None

Description

Index Actor event

1 User unmatched a set of purchase invoices, purchase credits, payments on account and

discounts received previously matched against a purchase payment 2 Relevant matching records unclogged from 'matched'

Alternatives


WorldView


Name: Unmatch Receipt Card No: 036

Actors: User

Goal: Reverses an existing Receipt Match


Extend:


None

Description

Index Actor event

1 User unmatched a set of sales invoices, sales credits, receipts on account and

discounts allowed previously matched against a sales receipt 2 Relevant matching records unclogged from 'matched'

Alternatives


Name: Purchase Card No: 037

Actors: User

Goal: Create a Purchase transaction


Extend:


Supplier

Description

Index

Actor event

1

User generates a Goods Received Note from a Purchase Order

2

or creates a Purchase Invoice directly into the Creditor account

Alternatives

Index

Actor event A1 Stock item out of stock or not sufficient quantity in stock A1.1 From Purchase Order: unfulfilled quantity kept on order when the Purchase

Order is processed if quantity still required

WorldView


Name: Tax Trans Card No: 038

Actors: None

Goal: Create a tax transaction




None

Description

Index Actor event

None

1 System creates a tax transaction from the tax-related elements of a Transactions record

Alternatives


Name: Sales Return Card No: 039

Actors: User

Goal: Create a Sales Return transaction


Extend:


Client

Description

Index Actor event

1 User creates a Sales Credit Note if return is for stock items on a Sales Invoice

or enters a Cash Register refund if return is for stock sold across the counter

Alternatives


WorldView


Name: Payment Card No: 040

Actors: User

Goal: Enter a Purchase Payment


Extend:


Supplier

Description

Index Actor event

1 User enters a Payment for stock purchases into the Supplier's creditor account

Alternatives


Name: Receipt Card No: 041

Actors: User

Goal: Enter a Sales Receipt


Extend:


Client

Description

Index Actor event

1 User enters a Receipt for sales into the Client's debtor account

Alternatives


WorldView


Name: Discount Received Card No: 042

Actors: User

Goal: Enter a Discount Received transaction


Extend:


Supplier

Description

Index Actor event

1 User enters a Discount Received transaction against a Purchase Invoice for supplies

Alternatives


Name: Discount Allowed Card No: 043

Actors: User

Goal: Enter a Discount Allowed transaction


Extend:


Client

Description

Index Actor event

1 User enters a Discount Allowed transaction against a Sales Invoice or Cash

Register sale

Alternatives


WorldView


Name: Process Sales Order Card No: 044

Actors: User

Goal: Process Sales Order/s


Extend:


Client

Description

Index Actor event

1 User processes Sales Orders by batch selection or individually

2 System creates a Transaction for each item of every Sales Order (no check for stock

availability; SO quantity processed as is; ensuing negative Stock balance possible)

3

System computes invoice value, adds it to Debtor's balance and checks if it exceeds

the Debtor's credit limit

4 System decreases relevant stock item quantities in Stock file by sold quantities

Alternatives

Index Actor event A3 Debtor's credit limit exceeded A3.1 System flags transaction as 'credit limit exceeded' A3.2 User accepts credit excess and toggles 'Credit Excess Accepted' A3.3 User rejects credit excess and toggles 'Do Not Process'; Sales Invoice not

created but Sales Order retained

A4.1 System does not decrease Stock file quantities

WorldView


Name: Process Purchase Order Card No: 045

Actors: User

Goal: Process Purchase Order/s


Extend:


Supplier

Description

Index Actor event

1 User processes Purchase Orders by batch selection or individually

2 System creates a Transaction for each item of every Purchase Order 3

System computes purchase value, adds it to Creditor's balance and checks if it exceeds

the Creditor's credit limit

4 System increments relevant stock item quantities in Stock file by purchased quantities

Alternatives

Index Actor event A3 Creditor's credit limit exceeded A3.1 System flags transaction as 'credit limit exceeded' A3.2 User accepts credit excess and toggles 'Credit Excess Accepted' A3.3 User rejects credit excess and toggles 'Do Not Process'; purchase not

processed

but Purchase Order retained

A3.4 Sales orders impacted by rejection of Purchase Order modified accordingly

A4.1 System does not increment Stock file quantities

WorldView


Name: Tax Return Card No: 046

Actors: User

Goal: Issue sales tax submission report




VAT Department

Description

Index Actor event

1 User issues sales tax submission report for all tax transactions for a selected period

2 System flags the reported records in the Tax Trans file as 'submitted'

Alternatives


Name: Year End Card No: 047

Actors: User

Goal: Carry forward static data and unmatched/unallocated transactions to a

new financial year


Extend: Transactions, Tax Trans


None

Description

Index Actor event

1 User triggers the year end process

2 System opens a new folder with new files holding:-

all static data from source files

a Transactions file holding all unmatched transactions from source file

a Tax Trans file holding all transactions not flagged as 'submitted' in source file a Stock file holding only the brought forward quantity balances in the source Stock file

Alternatives


WorldView


Name: Postcode Card No: 048

Actors: Admin+

Goal: Create a postal code


Extend: None


None

Description

Index Actor event

1 Admin creates the post code assigned to a town by the postal authorities

Alternatives


Name: Town Card No: 049

Actors: Admin

Goal: Create a town


Extend: Postcode


Description

Index

Actor event

1

Admin creates a town from the list of towns assigned a postcode by the postal

authorities

Alternatives

Index

Actor event None

WorldView


Name: Country Card No: 050

Actors: Admin

Goal: Create a country


Extend: None


None

Description

Index

Actor event

1

Admin creates a country with which the installation's owner does business

Alternatives

Index

Actor event None


WorldView


______________

Part 8 CRC Cards

The following pages carry the CRC Cards, detailing associated use cases,

responsibilities and attributes of a subset of the system‟s use cases. The subset (18 of 50 files) has been selected on the grounds of hosting files which are both the most critical and among the most illustrative in terms of the fields adopted.

WorldView


Class Name: transactions ID: 1 Type: System-generated

Description: Associated Use Cases:

A record for every transaction whether quantity-related, Stock, Sales Rep, Trans Type, Tax Type,

value-related or both Commission, Sales Ref, Purch Ref, Payment

Ref, Receipt Ref, Tax Trans, Cancel Trans,

Match Pyt, Match Rec, Unmatch Pyt, Unmatch

Rec, Purchase, Purch Return, Sale, Sale

Return, Payment, Disc Received, Receipt,

Disc Allowed.

Responsibilities:

Stores transactions for assignment to the associated use cases, for display or printing from the associated

use case record and for eventual carrying forward of pending (i.e. unmatched) entries to the next financial year

Attributes:

Ty

pe

Pre

cis

ion

Ind

ex

ed

Rela

ted

Du

pli

ca

tes

ref (system-generated sequential unique identifier) Numeric 0 Yes No No

transTypeRef Text(3) Yes Yes Yes

stkRef Text(14) Yes Yes Yes

salesRepRef Text(6) Yes Yes Yes

taxTypeRef Text(3) Yes Yes Yes

soRef Numeric 0 Yes Yes Yes

salesCommRef Numeric 0 Yes Yes No

clientRef Text(6) Yes Yes Yes

saleRef Numeric 0 Yes Yes Yes

purchRef Numeric 0 Yes Yes Yes

pytRef Numeric 0 Yes Yes Yes

recRef Numeric 0 Yes Yes Yes

recMatchRef Numeric 0 Yes Yes Yes

pytMatchRef Numeric 0 Yes Yes Yes

date Date Yes No Yes

amount Currency 4 No No Yes

amountFC Currency 4 No No Yes

WorldView


Class Name: stock ID: 2 Type: Operational


A record of every stock-related transaction Transactions, Sales Order, Client,

Stock Parent, Stock Type, Rate of Exchange,

Purchase Order, Supplier, Shelf, Sound,

Image, Video

Responsibilities:

Records historical stock items and all stock-in and stock-out transactions with the goal of keeping

historical stock records and a running balance of quantity in stock (negative balances allowed)

Attributes:

Ty

pe

Pre

cis

ion

Ind

ex

ed

Rela

ted

Du

pli

ca

tes

ref Text(14) Yes No No

typeRef Text(6) Yes Yes Yes

suppRef Text(6) Yes Yes Yes

poRef Text(6) Yes Yes Yes

shelfRef Text(6) Yes Yes Yes

imgRef Text(6) Yes Yes No

soundRef Text(6) Yes Yes No

vidRef Text(6) Yes Yes No

status Boolean Yes No Yes

roe Decimal 4 No Yes Yes

desc Text(50) No No Yes

cost Currency 4 No No Yes

costFC Currency 4 No No Yes

wsaleMarkup Decimal 4 No No Yes

rrpMarkup Decimal 4 No No Yes

date Date Yes No Yes

qtyIn Decimal 4 No No Yes

qtyOut Decimal 4 No No Yes

qtyBal Decimal 4 No No Yes

WorldView


Class Name: stkType ID: 3 Type: Maintenance


A type for the categorisation of stock items Stock

Responsibilities:

The categorisation of stock items by a type which is assigned to the item when this is created. The

Stock Type can be assigned to a Stock Category which can in turn be assigned to a Stock Class

Attributes:

Ty

pe

Pre

cis

ion

Ind

ex

ed

Rela

ted

Du

pli

ca

tes

ref Text(6) Yes Yes No

catRef Text(6) Yes Yes Yes


comRate Decimal 2 No No Yes

WorldView


Class Name: supplier ID: 4 Type: Maintenance


A unique identifier for each supplier Stock , Supplier Type, Purchase Order

Responsibilities:

Records historical data of each supplier of stock and/or services whether as consumables or for

re-sale

Attributes:

Ty

pe

Pre

cis

ion

Ind

ex

ed

Re

late

d

Du

pli

ca

tes


typeRef Text(3) Yes Yes Yes

name Text(30) Yes No Yes

add1 Text(30) No No Yes



town Text(20) Yes Yes Yes

postcode Text(10) Yes Yes Yes

country Text(15) Yes Yes Yes

creditLimit Decimal 4 No No Yes

tel Text(30) No No Yes

email Text(30) No No Yes

url Text(30) No No Yes

contact1 Text(30) No No Yes

email1 Text(30) No No Yes

tel1 Text(20) No No Yes

mob1 Text(20) No No Yes

contact2 Text(30) No No Yes

email2 Text(30) No No Yes

tel2 Text(20) No No Yes

mob2 Text(20) No No Yes

WorldView


Class Name: purchOrder ID: 5 Type: Operational


A record for each line of a purchase order Stock , Supplier

Responsibilities:

Records all purchase order transactions - every purchase order line is treated as a distinct transaction

Attributes:

Ty

pe

Pre

cis

ion

Ind

ex

ed

Rela

ted

Du

pli

ca

tes

recnum Integer 0 Yes No No

ref Integer 0 Yes No No

date Date No No Yes

qty Decimal 4 No No Yes

cost Currency 4 No No Yes

costFC Currency 4 No No Yes

WorldView


Class Name: stkShelf ID: 6 Type: Maintenance


A location in a warehouse where a stock item is stored Stock, Warehouse

Responsibilities:

The identification of a location in a warehouse where a stock item is held

Attributes:

Ty

pe

Pre

cis

ion

Ind

ex

ed

Rela

ted

Du

pli

ca

tes

ref Text(6) Yes Yes Yes

whRef Text(6) Yes Yes Yes

name Text(30) No No Yes

WorldView


Class Name: stkImage ID: 7 Type: Operational


A picture image of a stock item Stock

Responsibilities:

The visual rendering of a stock item for demonstration and/or identification purposes

Attributes:

Ty

pe

Pre

cis

ion

Ind

ex

ed

Rela

ted

Du

pli

ca

tes


description Text(30) No No Yes

path Text(40) No No Yes

filename Text(20) Yes Yes No

WorldView


Class Name: stkSound ID: 8 Type: Operational


A sound clip of a stock item Stock

Responsibilities:

The aural rendering of a stock item (such as a music CD) for demonstration and/or identification

purposes, or a verbal description of a stock item and/or of its attributes.

Attributes:

Ty

pe

Pre

cis

ion

Ind

ex

ed

Rela

ted

Du

pli

ca

tes





WorldView


Class Name: stkVideo ID: 9 Type: Operational


A video clip of a stock item Stock

Responsibilities:

The visual rendering of a stock item (such as a clip of a movie on DVD or motion-oriented items such

as battery-powered toys) for purposes of demonstration

Attributes:

Ty

pe

Pre

cis

ion

Ind

ex

ed

Rela

ted

Du

pli

ca

tes





WorldView


Class Name: suppType ID: 10 Type: Maintenance


A type for the categorisation of suppliers Supplier

Responsibilities:

The categorisation of suppliers by a type which is assigned to the supplier when it is created

Attributes:

Ty

pe

Pre

cis

ion

Ind

ex

ed

Rela

ted

Du

pli

ca

tes



WorldView


Class Name: stkWarehouse ID: 11 Type: Maintenance


A warehouse for the storage of stock items Shelf, Location

Responsibilities:

Maintaining a warehouse record for purposes of assignment of a stock item to it; warehouse is in turn

assigned to a geographical location held in stkLocation

Attributes:

Ty

pe

Pre

cis

ion

Ind

ex

ed

Rela

ted

Du

pli

ca

tes


locnRef Text(6) Yes Yes Yes


WorldView


Class Name: stkLocation ID: 12 Type: Maintenance


A geographical location hosting a warehouse for the storage of stock items

Warehouse

Responsibilities:

Maintaining a record of a geographical location for assignment to it of a warehouse

Attributes:

Ty

pe

Pre

cis

ion

Ind

ex

ed

Rela

ted

Du

pli

ca

tes



WorldView


Class Name: stkParent ID: 13 Type: Operational


A stock item designated as the receiving item of a stock Stock

component, the component being another regular stock

item

Responsibilities:

The assignment of a stock component to its parent stock item

Attributes:

Ty

pe

Pre

cis

ion

Ind

ex

ed

Rela

ted

Du

pli

ca

tes

childRef Text(14) Yes Yes No

parentRef Text(14) Yes Yes Yes

WorldView


Class Name: taxTrans ID: 14 Type: System-generated


A record for every tax transaction Transactions

Responsibilities:

Stores tax transactions for purposes of sales tax submission and for eventual carrying forward of pending

(i.e. unmatched) entries to the next financial year

Attributes:

Ty

pe

Pre

cis

ion

Ind

ex

ed

Rela

ted

Du

pli

ca

tes

ref (system-generated sequentail unique identifier) Numeric 0 Yes No No

transRef Numeric 0 Yes Yes Yes

date Date No No Yes

amount Currency 4 No No Yes

amountFC Currency 4 No No Yes

WorldView


Class Name: stkCategory ID: 15 Type: Maintenance


A type for the categorisation of stock items Stock Class, Stock Type

Responsibilities:

The categorisation of stock by a category assigned to the stock item when it is created

Attributes:

Ty

pe

Pre

cis

ion

Ind

ex

ed

Rela

ted

Du

pli

ca

tes


classRef Text(6) Yes Yes Yes



WorldView


Class Name: stkClass ID: 16 Type: Maintenance


A class for the categorisation of stock items Stock Category

Responsibilities:

The categorisation of stock by a class assigned to the stock item when it is created

Attributes:

Ty

pe

Pre

cis

ion

Ind

ex

ed

Rela

ted

Du

pli

ca

tes




WorldView


Class Name: roe ID: 17 Type: Operational


A rate of exchange for a foreign currency Stock, Currency

Responsibilities:

Storage of a day's rate of exchange, for a particular currency, for purposes of conversion of a foreign

currency value into a local currency value and vice-versa

Attributes:

Ty

pe

Pre

cis

ion

Ind

ex

ed

Rela

ted

Du

pli

ca

tes

ref Numeric 4 Yes No No

rate Decimal 4 No No Yes

currRef Text(3) Yes Yes Yes

dateRoe Date No No Yes

WorldView


Class Name: currency ID: 18 Type: Maintenance


A currency for the pursuance of sales and purchases Rate of Exchange

Responsibilities:

Storage of a currency, whether foreign or the currency of country of operation, by which sales- and

purchases-related transactions are to be recorded

Attributes:

Ty

pe

Pre

cis

ion

Ind

ex

ed

Rela

ted

Du

pli

ca

tes




WorldView


________________

Part 9 State Charts

State charts are being presented on the following pages for the four most critical

use cases of the selected subset of 18 files. The remaining subset cases are either very straightforward linear operations or do not represent functions of a nature that requires flow illustration.

WorldView


transactions

Transaction Event Occurred

User triggers value-related or quantity-related event

User

issues

Sale

s I

nvoic

e

User

issues

Sale

s R

eceip

t

User

issues

Purc

hase R

etu

rn

User

issues

Purc

hase I

nvoic

e

User

issues

Sale

s O

rder

User

issues

Paym

ent

User

issues

Receip

t

User

Issues

Dis

count

Allow

ed

User

Issues

Dis

count

Receiv

ed

System opensRelevant file/s

Transaction file updated

Stock fileupdated

Tax transactionsfile updated

TransactionsFile updated

System closesall open files

User processes Sales Order into Sales Invoice

WorldView


tax transactions

User triggers a tax-related event

User

issues

Sale

s I

nvoic

e

System opens taxtransaction file

User

issues

Sale

s R

eceip

t

IF transactions.taxType.status = “C” THEN BEGIN taxTrans.amount = (filename.amount – (filename.amount x 2)) x (taxType.rate / 100) taxTrans.amountFc = (filename.amountFc – (filename.amountFc x 2)) x (taxType.rate / 100) END

System updates tax transactions file

System closes all files

User

pro

cesses

Purc

hase O

rder

into

Purc

hase

Invoic

e

User

issues

Purc

hase R

etu

rn

WorldView


stock

Stock event occurredUser triggers a stock event

User

issues

Purc

hase

Ord

er

System writes Purchase Order or Sales Order into transactions file

User

issues

Sale

s O

rder

Stock file updated


Transactionsfile updated


User

issues

Sale

s I

nvoic

e

User

issues

Sale

s R

eceip

t

User

issues

Purc

hase R

etu

rn

WorldView


purchase order

User checks delivery & cost against

Purchase Order

User uploads Purchase

Order into stock

Purchase Order modifiedif discrepancies arise

Stock file updated


Transactionsfile updated


User issues a

Purchase Order

User confirms

Purchase Order


WorldView


___________________

Part 10 Data Dictionary

This section holds the Data Dictionary for the following subset of 18 of the 50

system files.

Transactions page 94

Tax Transactions 104 Stock 107

Stock Parent 117 Stock Class 118 Stock Category 120

Stock Type 122 Stock Location 124

Stock Warehouse 126 Stock Shelf 128 Stock Image 130

Stock Sound 132 Stock Video 134

Supplier 136 Supplier Type 147 Purchase Order 148

Currency 151 Rate of Exchange 152

WorldView


transactions

Entity Name System Sheet


transactions WorldView 1 transactions WorldView 2

Type Name Type Name

Element ref Element transTypeRef

Definition Definition

a unique identifier for every transaction one transaction type for every transaction

Occurrence Occurrence

once per stock transaction once per stock transaction

Picture Picture

Pic 99,999,999 Pic ZZZ

Range 0 - 99,999,999 Range 0 - ZZZ

Note Note

a system-generated sequential number assigned to every reads and writes the event-related transaction type reference

transction

Date Indexing Key: Primary Date Indexing Key: Foreign

15.08.11 Mandatory: Yes Duplicates: No 15.08.11 Mandatory: Yes Duplicates: Yes

WorldView


Entity Name System Sheet Entity Name System Sheet

transactions WorldView 3


Type Name

Type Name

Element stkRef

Element salesRepRef

Definition

Definition

the stock item reference for a stock transaction

the sales rep reference for a rep-generated sale or a sale

return against a rep-generated sale

Occurrence

Occurrence

once per stock-related transaction

once per rep-generated transaction

Picture Picture

Pic ZZZZZZZZZZZZZZ Pic ZZZZZZ

Range 0 - ZZZZZZZZZZZZZZ Range 0 - ZZZZZZ

Note Note

reads and writes the stock item reference if the event is reads and writes the sales rep reference if the event is a

stock related; rep-related sale;

otherwise writes the value XXXXXXXXXXXXXX. otherwise writes the value XXXXXX.

Date Indexing Key: Foreign Date Indexing Key: Foreign

15.08.11 Mandatory: Yes Duplicates: Yes


WorldView





Type Name

Type Name

Element taxTypeRef

Element soRef

Definition

Definition

the tax type reference for a purchase, purchase return,

the sales order reference for a sale recorded at origin by a

sale or sale return

sales order

Occurrence

Occurrence

once per tax-related (i.e. any sale/purchase or return)

once per order-generated sales transaction transaction

Picture Picture

Pic ZZZ Pic 99,999,999

Range 0 - ZZZ Range 0 - 99,999,999

Note Note

reads and writes the tax type reference if the event is sale- this reference identifier is allowed multiple occurences (unlike others

or purchase-related; in this file) as a sales order can comprise many lines each

otherwise writes the value XXX. comprising a distinct transaction; a unique identifier is provided by

a composite key of soRef and a sequential system-generated

record number. The value 00000000 is written if not sales-order-related transaction




WorldView





Type Name

Type Name

Element salesCommRef

Element clientRef

Definition

Definition

the sales commission reference for a sale registered by a

the client reference for client-related transactions being

sales rep or for a sale return against a rep-generated

sale, sale return, receipt and discount allowed

sale

Occurrence

Occurrence

once per commission-related transaction

once per sale-related transaction

Picture Picture

Pic 99,999,999 Pic ZZZZZZ

Range 0 - 99,999,999 Range 0 - ZZZZZZ

Note

Note

Refer Card 6: this reference is not allowed multiple occurrences as

reads and writes the client reference if the event is sale- or

every sales-order/sales-invoice/sales-return line is assigned a

sales-return-related;

separate sequential system-generated record number.

otherwise writes the value XXXXXX.

The value 00000000 is written if not a commission-related

transaction


15.08.11 Mandatory: Yes Duplicates: No


WorldView





Type Name

Type Name

Element suppRef

Element salesRef

Definition

Definition

the supplier reference for supplier-related transactions

the reference number of a sale or sale return

being purchase, purchase return, payment and discount

received

Occurrence

Occurrence

once per purchase-related transaction

once per sale-related transaction

Picture Picture

Pic ZZZZZZ Pic 99,999,999

Range 0 - ZZZZZZ Range 0 - 99,999,999

Note Note

reads and writes the supplier reference if the event is reads and writes the sale or sales-returns reference if the

purchase- or purchase-returns-related; event is sales-related;

otherwise writes the value XXXXXX. otherwise writes the value 00000000.




WorldView





Type Name

Type Name

Element purchRef

Element pytRef

Definition

Definition

the supplier reference for client-related transactions being

the reference number of a purchase payment

sale, sale return, receipt and discount allowed

Occurrence

Occurrence

once per purchase-related transaction

once per purchase payment transaction

Picture Picture

Pic 99,999,999 Pic 99,999,999

Range 0 - 99,999,999 Range 0 - 99,999,999

Note Note

reads and writes the purchase or purchase-returns reads and writes the payment reference if the event is

reference if the event is purchases-related; purchases-payment-related;

otherwise writes the value 00000000. otherwise writes the value 00000000.




WorldView





Type Name

Type Name

Element recRef

Element recMatchRef

Definition

Definition

the reference number of a sales receipt

the reference identifying a sales transaction as having been

settled by a sales-receipt/sales-credit/discount-allowed

also flagged with the same match ref

Occurrence

Occurrence

once per sales receipt transaction

once per matched sales transaction

Picture Picture

Pic 99,999,999 Pic 99,999,999

Range 0 - 99,999,999 Range 0 - 99,999,999

Note Note

reads and writes the receipt reference if the event is reads and writes the receipt matching reference if the event

sales-receipt-related; is related to the matching of sales/sales-return/sales-

otherwise writes the value 00000000. receipt/discount-allowed transactions;

otherwise writes the value 00000000.




WorldView





Type Name

Type Name

Element pytMatchRef

Element date

Definition

Definition

the reference identifying a purchase transaction as having

the system-date on which a transaction has been recorded

been settled by a purchase-payment/purchase-credit/

discount-received also flagged with the same match ref

Occurrence

Occurrence

once per matched purchase transaction

once per transaction

Picture Picture

Pic 99,999,999 Pic dd/mm/yyyy

Range 0 - 99,999,999 Range infinite

Note Note

reads and writes the payment matching reference if the

event is related to the matching of purchases/purchase-

return/purchase-payment/discount-received transactions;

otherwise writes the value 00000000.

Date Indexing Key: Foreign Date Indexing None Key:



WorldView






Type Name

Type Name

Element status

Element amount

Definition

Definition

a value status (debit or credit) assigned to every transaction

an amount (if quantity-related) or value (if finance-related)

assigned to every transaction

Occurrence

Occurrence

once per stock (quantity-related) or financial (amount-

once per quantity- or financial-related transaction

related) transaction

Picture

Picture

Pic Z

Pic 99,999,999.9999

Range D or C

Range 0.0000 - 99,999,999.9999

Note

Note

a boolean flag to distinguish whether figures and values in

reads and writes the quantity or value if the event is stock-

the record are positive or negative; thus no provision

or finance-related;

necessary in the coding to prefix negative figures and

otherwise writes the value 99999999.9999

values with a minus sign

Date Indexing Yes Key:

Date Indexing None Key:



WorldView




Type Name

Element amountFC

Definition

a foreign currency amount assigned to a financial

transaction in a currency other than the selected

installation currency

Occurrence

once per financial-related foreign currency transaction

Picture

Pic 99,999,999.9999

Range 0.0000 - 99,999,999.9999

Note

reads and writes the value if the event is finance-related.

otherwise writes the value 99999999.9999.


15.08.11 Mandatory: No Duplicates: Yes

WorldView


tax transaction



taxTrans WorldView 1 taxTrans WorldView 2

Type Name Type Name

Element ref Element transRef


a unique identifier for every tax transaction a unique identifier for every transaction


once per tax transaction once per transaction

Picture Picture

Pic 99,999,999 Pic 99,999,999

Range 0 - 99,999,999 Range 0 - 99,999,999

Note Note

a system-generated sequential number assigned to every a system-generated sequential number assigned to every

tax transaction transaction


15.08.11 Mandatory: Yes Duplicates: No 15.08.11 Mandatory: Yes Duplicates: No

WorldView



taxTrans WorldView 3


Type Name

Type Name

Element rate

Element amount

Definition

Definition

the day's rate for a foreign currency

a value assigned to every transaction

Occurrence

Occurrence

once per currency per day

once per tax transaction

Picture Picture

Pic 9999.9999 Pic 99,999,999.9999

Range 0.0000 - 9999.9999 Range 0.0000 - 99,999,999.9999

Note Note

records the day's rate of exchange for a currency for records the value of a transaction

purposes of conversion from local currency

Date Indexing None Key: Date Indexing None Key:



WorldView




Type Name

Element amountFC

Definition

a foreign currency value, if any, assigned to every

transaction

Occurrence

once per tax transaction

Picture

Pic 99,999,999.9999

Range 0.0000 - 99,999,999.9999

Note

records the value of a tax transaction



WorldView


stock



stock WorldView 1 stock WorldView 2

Type Name Type Name

Element ref Element typeRef


a unique record number for every stock item one stock type reference assigned to every stock item


once per stock record once per stock record

Picture Picture

Pic ZZZZZZZZZZZZZZ Pic ZZZZZZ

Range 0 - ZZZZZZZZZZZZZZ Range 0 - ZZZZZZ

Note Note

alphanumeric input (no special characters) alphanumeric input (no special characters)

reads an existing stock type reference from stkType



WorldView




stock WorldView 3

stock WorldView 4

Type Name

Type Name

Element suppRef

Element poRef

Definition

Definition

one supplier reference assigned to every stock item

one purchase order reference assigned to every stock item

Occurrence

Occurrence

once per stock record


Picture

Picture

Pic ZZZZZZ

Pic 99,999,999

Range 0 - ZZZZZZ

Range 0.0000 - 99,999,999

Note

Note

alphanumeric input (no special characters)

numeric input

reads an existing supplier reference

reads an existing purchase order reference if stock item

written into stock by means of purchase order processing

same reference can appear in other stock records of the

same stock item as stock:purchOrder is a many:1

relationship

Date Indexing Key: Foreign




WorldView




stock WorldView 5

stock WorldView 6

Type Name

Type Name

Element shelfRef

Element imgRef

Definition

Definition

one storage shelf reference assigned to every stock item

one stock image reference assigned to every stock item

Occurrence

Occurrence



Picture

Picture

Pic ZZZZZZ

Pic ZZZZZZ

Range 0 - ZZZZZZ

Range 0 - ZZZZZZ

Note

Note



reads an existing storage shelf reference

reads an existing stock image reference





WorldView




stock WorldView 7

stock WorldView 8

Type Name

Type Name

Element soundRef

Element vidRef

Definition

Definition

one stock sound clip reference assigned to every stock

one stock video clip reference assigned to every stock item

item

Occurrence

Occurrence



Picture

Picture

Pic ZZZZZZ

Pic ZZZZZZ

Range 0 - ZZZZZZ

Range 0 - ZZZZZZ

Note

Note



reads an existing stock sound clip reference

reads an existing stock video clip reference





WorldView




stock WorldView 9

stock WorldView 10

Type Name

Type Name

Element status

Element roe

Definition

Definition

one value status (debit or credit) assigned to every stock

one rate of exchange figure assigned to every stock item

item

Occurrence

Occurrence



Picture

Picture

Pic Z

Pic 9999.9999

Range D or C

Range 0.0000 - 9999.9999

Note

Note

a boolean switch to distinguish whether figures and values

numeric input masked as nnnn.nnnn

in the record are positive or negative; thus no provision

a rate of exchange by which cost (sheet 12) is computed

necessary in the coding to prefix negative figures and

from the product of this roe multiplied by costFC (sheet 13)

values with a minus sign

in the case of stock purchase/sale with foreign currency




15.08.11 Mandatory: Duplicates: Yes

WorldView




stock WorldView 11

stock WorldView 12

Type Name

Type Name

Element desc

Element cost

Definition

Definition

one description assigned to every stock item

one cost value assigned to every stock item

Occurrence

Occurrence



Picture

Picture

Pic

ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ

Pic 99,999,999.9999

Range 0 - ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ

Range 0.0000 - 99,999,999.9999

Note

Note

alphanumeric input (special characters allowed)

numeric input masked as nn,nnn,nnn.nnnn

either the result of direct input in case of local purchase/sale

or the product of this value multiplied by costFC (sheet 13)



15.08.11 Mandatory: Duplicates:


WorldView




stock WorldView 13

stock WorldView 14

Type Name

Type Name

Element costFC

Element wsaleMarkup

Definition

Definition

one foreign currency cost assigned to every stock item

one wholesale profit markup assigned to every stock item

Occurrence

Occurrence



Picture

Picture

Pic 99,999,999.9999

Pic 999.9999

Range 0.0000 - 99,999,999.9999

Range 0.0000 - 999.9999

Note

Note

numeric input masked as nn,nnn,nnn.nnnn for purchases/

numeric input masked as nnn.nnnn

sales or returns thereof in a foreign currency





WorldView




stock WorldView 15

stock WorldView 16

Type Name

Type Name

Element rrpMarkup

Element date

Definition

Definition

one recommended retail profit markup assigned to every

the system-date on which a transaction has been recorded

stock item

Occurrence

Occurrence


once per transaction

Picture

Picture

Pic 999.9999

Pic dd/mm/yyyy

Range 0.0000 - 999.9999

Range infinite

Note

Note

numeric input masked as nnn.nnnn





WorldView




stock WorldView 17

stock WorldView 18

Type Name

Type Name

Element qtyIn

Element qtyOut

Definition

Definition

one quantity, representing an addition to the stock balance,

one quantity, representing a reduction from the stock

for every stock item

balance, for every stock item

Occurrence

Occurrence



Picture

Picture

Pic 99,999,999.9999

Pic 99,999,999.9999

Range 0.0000 - 99,999,999.9999

Range 0.0000 - 99,999,999.9999

Note

Note

numeric input masked as nn,nnn,nnn.nnnn for purchases or

numeric input masked as nn,nnn,nnn.nnnn for purchase

sales return quantity

returns or sales





WorldView



stock WorldView 19

Type Name

Element qtyBal

Definition

the quantity in stock for this stock item

Occurrence


Picture

Pic 99,999,999.9999

Range 0.0000 - 99,999,999.9999

Note

system-generated product of qtyIn or qtyOut added to or

deducted from the qtyBal of the most recent record in

sequence for the same stock item



WorldView


stock parent



stkParent WorldView 1 stkParent WorldView 2

Type Name Type Name

Element childRef Element parentRef


unique identifier of a stock item deemed to be component stock code of an existing stock item to which childRef is

of another stock item a component


once per parent stock item once per component stock item

Picture Picture

Pic ZZZZZZZZZZZZZZ Pic ZZZZZZZZZZZZZZ

Range 0 - ZZZZZZZZZZZZZZ Range 0 - ZZZZZZZZZZZZZZ

Note Note


reads an existing stock code



WorldView


stock class



stkClass WorldView 1 stkClass WorldView 2

Type Name Type Name

Element ref Element desc


a unique identifier for every stock class a description of the stock class


once per stock class once for every stock class

Picture Picture

Pic ZZZZZZ Pic ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ

Range 0 - ZZZZZZ Range 0 - ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ

Note Note

alphanumeric input (no special characters) alphanumeric input (special characters allowed)

Date Indexing Key: Primary Date Indexing None Key:


WorldView



stkClass WorldView 3

Type Name

Element comRate

Definition

the sales commission rate applicable to a stock class

over-rideable by commission rate assigned to the stock

item, stock type and stock category in that order of

precedence

Occurrence

1 rate per stock type

Picture

99.9999

0 - 99.9999

Note

numeric input gt 0.0000



WorldView


stock category



stkCategory WorldView 1 stkCategory WorldView 2

Type Name Type Name

Element ref Element classRef


a unique identifier for every stock category one class reference assigned to every stock category


once per stock category once per stock category; duplicates allowed

Picture Picture

Pic ZZZZZZ Pic ZZZZZZ

Range 0 - ZZZZZZ Range 0 - ZZZZZZ

Note Note


reads an existing class reference



WorldView



stkCategory WorldView 3

stkCategory WorldView 4

Type Name

Type Name

Element desc

Element comRate

Definition

Definition

a description of the stock category

the sales commission rate applicable to a stock category

over-rideable by commission rate assigned to the stock item

and to the stock type in that order of precedence

Occurrence

Occurrence

once for every stock category

1 rate per stock category

Picture Picture

Pic ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ 99.9999

Range 0 - ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ 0 - 99.9999

Note Note

alphanumeric input (special characters allowed) numeric input gt 0.0000




WorldView


stock type



stkType WorldView 1 stkType WorldView 2

Type Name Type Name

Element ref Element catRef


a unique identifier for every stock type one category reference assigned to every stock type


once per stock type once per stock type; duplicates allowed

Picture Picture



Note Note


reads an existing category reference



WorldView



stkType WorldView 3

stkType WorldView 4

Type Name

Type Name

Element desc

Element comRate

Definition

Definition

a description of the stock type

the sales commission rate applicable to a stock type

(over-rideable by commission rate assigned to the stock item)

Occurrence

Occurrence

once for every stock type

1 rate per stock type

Picture Picture

Pic ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ 99.9999

Range 0 - ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ 0 - 99.9999

Note Note

alphanumeric input (special characters allowed) numeric input gt 0.0000




WorldView


location



stkLocation WorldView 1 stkLocation WorldView 2

Type Element

Name Type Element

Name

Element ref Element locnRef


unique identifier of warehouse code of an existing geographical location to which the

warehouse appertains


once per location once per warehouse

Picture Picture



Note Note


reads an existing location code



WorldView



stkLocation WorldView 3

Type Element

Name

Element name

Definition

description of warehouse

Occurrence

once per warehouse

Picture

Pic ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ

Range 0 - ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ

Note



15.08.11 Mandatory: Yes Duplicates:

WorldView


warehouse



stkWarehouse WorldView 1 stkWarehouse WorldView 2

Type Name Type Name

Element ref Element locnRef


unique identifier of warehouse code of an existing geographical location to which the

warehouse appertains


once per location once per warehouse

Picture Picture



Note Note


reads an existing location code



WorldView



stkWarehouse WorldView 3

Type Name

Element name

Definition

description of warehouse

Occurrence

once per warehouse

Picture



Note




WorldView


stock shelf



stkShelf WorldView 1 stkShelf WorldView 2

Type Name Type Name

Element ref Element stkRef


unique identifier of stores shelf (part of storage rack) code of an existing warehouse to which the storage rack

appertains


once per warehouse once per shelf

Picture Picture



Note Note


reads an existing warehouse code



WorldView



stkShelf WorldView 3

Type Name

Element name

Definition

description of shelf (part of storage rack), if any required

Occurrence

once per shelf

Picture



Note




WorldView


stock image



stkImage WorldView 1 stkImage WorldView 2

Type Name Type Name



unique identifier of stock item image description of the stock item image


once per stock image once per stock image

Picture Picture

Pic ZZZZZZZZZZZZZZ Pic ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ

Range 0 - ZZZZZZZZZZZZZZ Range 0 - ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ

Note Note


by default, reads stock item name from stock.desc

truncated from 50 characters to 30; overwritable

(special characters allowed)



WorldView




stkImage WorldView 3

stkImage WorldView 4

Type Name

Type Name

Element path

Element filename

Definition

Definition

the system path where the image is located on storage

name of file for the image

Occurrence

Occurrence

once per image

once per image

Picture

Picture

Pic ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ

Pic ZZZZZZZZZZZZZZZZZZZZ

Range 0 - ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ

Range 0 - ZZZZZZZZZZZZZZZZZZZZ

Note

Note

alphanumeric input (special characters allowed by MS


Windows only)

Windows only)



15.08.11 Mandatory: Yes Duplicates:


WorldView


stock sound



stkSound WorldView 1 stkSound WorldView 2

Type Name Type Name



unique identifier of stock item sound clip description of the stock item sound clip


once per stock sound clip once per stock sound clip

Picture Picture



Note Note







WorldView




stkSound WorldView 3

stkSound WorldView 4

Type Name

Type Name

Element path

Element filename

Definition

Definition

the system path where the sound clip is located on storage

name of file for the sound clip

Occurrence

Occurrence

once per sound clip

once per sound clip

Picture

Picture





Note

Note



Windows only)

Windows only)





WorldView


stock video



stkVideo WorldView 1 stkVideo WorldView 2

Type Name Type Name



unique identifier of stock video clip description of the stock item video


once per stock video once per stock video

Picture Picture



Note Note







WorldView




stkVideo WorldView 3

stkVideo WorldView 4

Type Name

Type Name

Element path

Element filename

Definition

Definition

the system path where the video is located on storage

name of file for the video

Occurrence

Occurrence

once per video

once per video

Picture

Picture





Note

Note



Windows only)

Windows only)





WorldView


supplier



supplier WorldView 1 supplier WorldView 2

Type Name Type Name

Element ref Element typeRef


unique identifier for supplier a supplier category assigned to this supplier


once per supplier once per supplier

Picture Picture

Pic ZZZZZZ Pic ZZZ

Range 0 - ZZZZZZ Range 0 – ZZZ

Note Note




WorldView




supplier WorldView 3


Type Name

Type Name

Element name

Element add1

Definition

Definition

supplier name

line 1 of supplier address

Occurrence

Occurrence

once per supplier

once per supplier

Picture

Picture





Note

Note







WorldView






Type Name

Type Name

Element add2

Element add3

Definition

Definition



Occurrence

Occurrence

once per supplier

once per supplier

Picture

Picture





Note

Note





15.08.11 Mandatory: No Duplicates:


WorldView






Type Name

Type Name

Element town

Element postcode

Definition

Definition

town from where supplier operates

postcode assigned by the postal authorities to the town

Occurrence

Occurrence

once per supplier

once per supplier

Picture

Picture


Pic ZZZZZZZZZZ


Range 0 - ZZZZZZZZZZ

Note

Note







WorldView






Type Name

Type Name

Element country

Element creditLimit

Definition

Definition

country from where supplier operates

maximum credit received from supplier

Occurrence

Occurrence

once per supplier

once per supplier

Picture

Picture

Pic ZZZZZZZZZZZZZZZ

Pic 99,999,999.9999

Range 0 - ZZZZZZZZZZZZZZZ

Range 0.0000 - 99,999,999.9999

Note

Note


numeric input => 0.0000

masked as nn,nnn,nnn.nnnn





WorldView






Type Name

Type Name

Element tel

Element email

Definition

Definition

supplier's fixed line telephone number/s

supplier's principal email address

Occurrence

Occurrence

once per supplier

once per supplier

Picture

Picture





Note

Note







WorldView






Type Name

Type Name

Element url

Element contact1

Definition

Definition

the url name of the supplier's website

the name of the supplier's first contact

Occurrence

Occurrence

once per supplier

once per supplier

Picture

Picture





Note

Note

alphanumeric input (cross-browser acceptable characters


only)





WorldView






Type Name

Type Name

Element email1

Element tel1

Definition

Definition

the email address of the supplier's first contact

fixed telephone number (and extension suffix if any) of

supplier's first contact

Occurrence

Occurrence

once per supplier

once per supplier

Picture

Picture





Note

Note

alphanumeric input (special characters allowed: @ - _ .)






WorldView






Type Name

Type Name

Element mob1

Element contact2

Definition

Definition

mobile phone number of supplier's first contact

the name of the supplier's second contact

Occurrence

Occurrence

once per supplier

once per supplier

Picture

Picture





Note

Note







WorldView






Type Name

Type Name

Element email2

Element tel2

Definition

Definition

the email address of the supplier's second contact

fixed telephone number (and extension suffix if any) of

supplier's second contact

Occurrence

Occurrence

once per supplier

once per supplier

Picture

Picture





Note

Note

alphanumeric input (special characters allowed: @ - _ .)






WorldView




Type Name

Element mob2

Definition

mobile phone number of supplier's second contact

Occurrence

once per supplier

Picture



Note




WorldView


supplier type



suppType WorldView 1 suppType WorldView 2

Type Name Type Name



unique identifier of a type for purposes of supplier a description of the supplier type

categorisation


once per supplier once per supplier

Picture Picture

Pic ZZZZZZ Pic ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ

Range 0 - ZZZZZZ Range 0 - ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ

Note Note




WorldView


purchase order



purchOrder WorldView 1 purchOrder WorldView 2

Type Name Type Name

Element recnum Element ref


a unique record number for every Purchase Order line a unique reference number for every Purchase Order


1 unique number per line of every Purchase Order 1 unique number per Purchase Order

Picture Picture

99999999

0 - 99999999

Note Note

no input no input

system-generated sequential number system-generated sequential number

forms a composite primary key together with ref same number for all elements of a Purchase Order

forms a composite primary key together with recnum

Date Indexing Key: Composite (Primary)

Date Indexing Key: Composite (Primary)

15.08.11 Mandatory: Yes Duplicates: No 15.08.11 Mandatory: Yes Duplicates: No

WorldView



purchOrder WorldView 3


Type Name

Type Name

Element date

Element quantity

Definition

Definition

date denoting creation of Purchase Order

quantity of Stock item

Occurrence

Occurrence

once for every element of a Purchase Order

1 quantity per element of a Purchase Order

Picture Picture

dd/mm/yyyy 99,999,999.9999

0 - 99,999,999.9999

Note Note

date input masked as nn/nn/nnnn numeric input gt 0.0000




WorldView






Type Name

Type Name

Element amount

Element amountFC

Definition

Definition

unit purchase value of Stock item

unit purchase value of Stock item in foreign currency

Occurrence

Occurrence

1 value per element of a Purchase Order

1 value per element of a Purchase Order

Picture

Picture

99,999,999.9999

99,999,999.9999

0 - 99,999,999.9999

0 - 99,999,999.9999

Note

Note

system-generated computation of element's total value:-

system-generated computation of element's total foreign

purchOrder.quantity * ((stock.markup/100+1) * stock.cost)

currency value:-

numeric input >0.0000

(purchOrder.quantity * ((stock.markup/100+1) * stock.cost)) * roe.rate

numeric value gt 0.0000





WorldView


currency



currency WorldView 1 currency WorldView 2

Type Name Type Name



a unique identifier for every transaction a description of the currency


once per currency once per currency

Picture Picture

Pic ZZZ Pic ZZZZZZZZZZZZZZZZZZZZ

Range 0 - ZZZ Range 0 - ZZZZZZZZZZZZZZZZZZZZ

Note Note




WorldView


rate of exchange



roe WorldView 1 roe WorldView 2

Type Name Type Name

Element ref Element rate


a unique identifier for every rate of exchange record the day's rate of exchange for a currency


once per rate of exchange once per date per currency

Picture Picture

Pic 99,999,999 Pic 9999.9999

Rnage 0 - 99,999,999 Range 0.0000 - 9999.9999

Note Note

a system-generated sequential number assigned to every records the day's rate of exchange, if required, for a

rate of exchange record currency



WorldView




roe WorldView 3 roe WorldView 4

Type Name Type Name

Element currRef Element dateRoe


a currency to which the rate is assigned system date representing date of rate


once per rate of exchange once per currency per day

Picture Picture

Pic ZZZ Pic dd/mm/yyyy

Range 0 - ZZZ Range infinite

Note Note

alphanumeric input checked against currency file records the date of a currency rate

Date Indexing Key: Foreign Date Indexing None Key:

15.08.11 Mandatory: Yes Duplicates: Yes 15.08.11 Mandatory: Yes Duplicates: Yes


WorldView


________________________________ Part 11 System Schema & Relationships

The full systema schema and file relationships are being presented on the next page as a top level illustration of the system, for the easy assimilation of the

preceding lower-level diagrams and cards. This schema has been compiled with Microsoft Access 2007 for its superior visual presentation attributes.


WorldView


_______________________

Appendix – The User Manual The following pages hold the User Manual for the submitted prototype.

This manual describes all the functionality drawn into the interface design, even for those buttons which appear on the GUI to illustrate the full envisaged

functionality but are not coded. The uncoded buttons are listed below.

Removes a displayed invoice or return note after checking that it has not yet been flagged as updated to the Sales Ledger and Sales Tax files.

Updates this invoice or return note, meaning that transactions and tax transactions file records are flagged as having been updated to the Sales Ledger and Sales Tax file.

Sends an invoice or return note printout to the customer as an emailed attachment.

Sends a printout of the invoice or return note to the line printer.

Sends the user to the window related to the field in focus which is deemed as

such when the user clicks on it with the left mouse button.

WorldView


Creating a Sales Invoice & Return

_________________________________

When the Sales Invoicing window appears on screen, the Invoice Type settings are pre-selected for the entry of a sales invoice of items from stock.

Any one, or both, of these default settings can be changed.

o Tick the Sales Return radio button if you wish to issue a credit for items

returned by the customer.

o Tick the Free Text radio button to invoice an item not in stock such as a

service.

_______________________________

The Header box groups all data items required only once for every invoice or credit created. The following values are present by default:

Invoice Ref displays the next available invoice number

Date consists of today‟s system date

Terms lists Cash on Delivery from a list of five methods of customer

payment, the other four consisting of 30 Days credit, 60 Days, 90 Days and

120+ Days.

Sales Rep displays the first sales person on an alphabetically-sorted list of

company reps.

WorldView


o Invoice Ref can be over-written by any preceding number to view previously

created invoices.

Alternatively, you can click the Previous or Next buttons to

navigate backwards and forward through existing invoices or sales returns.

The Financials tab page is populated and displayed once an existing reference

number has been selected. This tab displays a breakdown of the invoice or return‟s totals as well as commission-related information consisting of Sales

Person‟s name and commission Amount This Invoice. Another two fields consisting of commission Rate This Item and Amount This Item display the commission rate and commission amount accruable or deductible to individual

stock items when an invoice or return is being created. No information for individual items is displayed when an existing invoice or return is being

displayed. The Listing and other tab pages populate automatically upon clicking the

related field in the Add Item group box.

o Click the Unsync Tabs button at the top right-hand corner of the

window if you do not wish the tab pages to populate automatically but only

when clicked upon. Click a second time to reactivate tab page

synchronization.

o Date: this field automatically displays today‟s system date but can be changed

by means of a popup calendar produced by ticking the down arrow.

o Customer: click the down arrow to select a customer code from the drop down

list; the full customer name is displayed in the textbox to the right.

The Customer tab page appears, displaying static customer information such

as invoice and delivery address together with the financial information on the

amount owed by this customer, by how much the credit limit has been

exceeded and the total sales for the year to date. This last figure represents

all the customer‟s sales from the start of the company‟s current financial

period if the End of Year process has been run. If the company chooses to

keep running the system without bringing financial accounting years to a

close, a total for all customer sales from the start of their trading is displayed.

o Terms: click the down arrow to select payment terms from a drop down list of

available terms.

o Sales Rep: click the down arrow to select the relevant sales person from a

drop down list of reps.

WorldView


o Order Ref: key in a sales order reference or, if this is not a sales order

brought in by a sales rep, any other reference note necessary; it can also be

left blank.

o Global Discount: key in a percentage discount figure to be deducted from the

invoice‟s gross value. This discount figure will appear in all Item Discount

fields in the Add Item group box below, and any single item‟s discount can be

modified there.

_________________________________

o Stock Ref: if you have selected the From Stock radio button in the Invoice

Type group box, click the down arrow to select a stock code from an

alphanumerically-sorted list of stock items. The stock description appears in

the textbox to the right.

If Free Text has been selected, type in a descriptive note of the service in the

textbox beneath. Once a stock item has been selected, the Stock Item tab appears on the

window‟s right-hand side displaying item-related information.

o Quantity: insert the stock or service quantity required.

o The Price radio button is by default set on Wholesale. Click the Consumer

button if this is a direct consumer sale.

o Item Discount: this field displays the percentage figure, if any, keyed into the

Global Discount field in the Header box. Click the textbox to overwrite this

value with a new one for this item.

The Net item total field is populated with the value of the selected price

multiplied by the quantity. Total sales tax for this item is calculated, added to the net value and displayed in the Plus Tax field.

WorldView


o Click the Add Item button to add this stock item to the first available

row in the Listing grid which is now the displayed tab page.

o Click the Clear Item button if you wish to have this stock item entry

removed.

_____________________________

The tab pages are populated by clicking the relevant tab. Customer, Financials and Stock Item also populated automatically once you click inside a related field

if the Sync Tabs function is on. Even when tab synchronization is on, other tabs can still be brought up over the currently synchronized tab by clicking them. Synchronization can be enabled or disabled any number of times by clicking the

Sync Tabs or Desync Tabs button at the top right-hand corner of the window. This button changes its text to the opposite of the current synchronization

status, i.e. Sync when the status is desynchronized and Desync when it is synchronized.

o This is the default tab page when the Sales Invoice window is opened.

It displays an invoice or return note‟s item rows. Double-click any row to

populate the Add Item group box with that row‟s data for modification

purposes.

o Click any of these tab pages if you wish to view

them. Tab pages can be viewed even when tab synchronization is displaying

another tab page; the user-selected page is substitutes the previously

synchronized one..

o Click to view a menu strip of an image, sound or video file

attached to the stock item when available.

Click any of these media buttons when the adjoining textbox holds an image filename. The image, video or

sound will play in the pane beneath.

__________________________________

Clear the invoice or return being created without saving

Save this invoice or return

WorldView


Delete a displayed invoice or return that has not yet been updated to the Sales Ledger

Update this invoice or return to the Sales Ledger

Exit the Sales Invoice window

Send an invoice or return to the customer as an emailed attachment

Print a copy of the invoice or return

Go to the window related to the field in focus. A field is in focus when

you left click your mouse button on it


WorldView


__________ Bibliography

NCC Education Ltd (2007) Business Systems Analysis, 2nd edition. Manchester. NCC Education Ltd (2007) Systems Design, 2nd edition. Manchester.

Microsoft Press (2006) .NET Framework 2.0, Windows Based Client Development Benyon-Davies, Paul (2004). Chapter 1: Database Systems as Abstract

Machines. In: Database Systems. 3rd ed., Basingstoke, Palgrave

Macmillan, 3–5. Faigley, Lester (1986). Competing Theories of Process: A Critique and a

Proposal. College English, 48(6), 527–542. Schriver, Karen A. (1997). Chapter 2: Evolution of the Field: Contextual

Dynamics. In: Dynamics in Document Design. New York, Wiley, 94.

Wenger, Etienne (1998). Chapter 1: Meaning. In: Communities of practice: learning, meaning, and identity. Cambridge, Cambridge University Press,

51-71. Swales, J.M., (1990). 'Research articles in English'. In: Genre analysis: English in

academic and research settings, 127-166, Cambridge: Cambridge

University Press


academic - ncc final - worldview

Documents

worldview concept

invoicing system concept

wider worldview system

system functions

system schema

system design

invoicing gui

wider concept