ssadm

CS2E23N Page no. 1/64 17/01/2008

London Metropolitan UniversityDepartment of Computing, Information Systems & Mathematics

Coursework Assignment Header:STUDENT REFERENCE NUMBER_______________06022698____________________________________

FAMILY NAMEAND INITIALS (Please print):____DAVID G MAHONY_____________________________________________

GRADE POINT ALLOCATED (0 - 16):____________________ N.B. All grades are provisional until confirmed by the Board of Examiners.

ASSESSOR'S INITIALS:________________________________

Unit number : CS2E23C/N

Unit name : Structured Systems Analysis

Unit Organiser : Tony Royce

Assignment no. Resit Weighting : 50%: Week beginning 5th November,2007 (Week6)(% of unit assessment total, incl. exam)

Date and time due : Thursday 17th January 2008 (Week 13)

Note that assignments will NOT be accepted by the Unit Organiser after this date. If you have valid mitigating circumstances, and have supporting documentary evidence, then obtain and complete a mitigating cirucmstances form and have it authorised. YOU SHOULD NOT DELAY SUBMISSION OF THIS GROUP ASSIGNMENT BECAUSE ONE MEMBER HAS A SHORT PERIOD OF ABSENCE. Longer periods of absence should be discussed with Tony.

PLAGIARISM

You are reminded that there exist regulations concerning plagiarism. Extracts from these regulations are printed overleaf. Please sign below to say that you have read and understand these extracts:

(signature:)_________________________________________________________________________________

This header sheet should be attached to the assignment specification and to the work you submit. No work will be accepted without it.

D.Mahony R.Tye T. Black Y.Mangela

ASSESSOR’S COMMENTS

CS2E23N Page no. 2/64 17/01/2008


Coursework Assignment Header:STUDENT REFERENCE NUMBER_____________05041673______________________________________

FAMILY NAMEAND INITIALS (Please print):_____RUTH TYE____________________________________________









PLAGIARISM


(signature:)_________________________________________________________________________________




CS2E23N Page no. 3/64 17/01/2008


Coursework Assignment Header:STUDENT REFERENCE NUMBER_____________ 06000239______________________________________

FAMILY NAMEAND INITIALS (Please print):__OLUWATOBILOBA BLACK __









PLAGIARISM


(signature:)_________________________________________________________________________________




CS2E23N Page no. 4/64 17/01/2008


Coursework Assignment Header:STUDENT REFERENCE NUMBER__________06002585

FAMILY NAMEAND INITIALS (Please print):_______ YOGESH .S. MANGELA ____









PLAGIARISM


(signature:)_________________________________________________________________________________




CS2E23N Page no. 5/64 17/01/2008

CS2E23NCoursework Assignment[SSADM Stage 3 and 4]

By ,David Mahony - 06022698Ruth Tye - 05041673OLUWATOBILOBA BLACK - 06000239Yogesh Mangela - 06002585

17th January 2008


CS2E23N Page no. 6/64 17/01/2008

Contents Page

STEP - 310 Define Required System processing.............................................................................7Requirements Catalogue....................................................................................................................7Required Logical DFM....................................................................................................................11Level 1 diagram................................................................................................................................12Elementary Process Descriptions....................................................................................................13I/O Description.................................................................................................................................14Logical Data Store/ Entity Cross Reference..................................................................................17User Catalogue..................................................................................................................................18STEP- 320 Develop Required Data Model.....................................................................................19Data Catalogue.................................................................................................................................19STEP - 330 Derive system functions...............................................................................................22Update function definitions.............................................................................................................22User Catalogue..................................................................................................................................27I/O structures....................................................................................................................................28Requirements Catalogue..................................................................................................................31STEP - 340 Enhance Required Data Model...................................................................................35Relational data analysis model........................................................................................................35Logical Data Model..........................................................................................................................38STEP - 360 DEVELOP PROCESSING SPECIFICATION.........................................................39Entity access Matrix.........................................................................................................................39E.A.P (Enquiry Access Path)...........................................................................................................40E.L.H (Entity Life History).............................................................................................................42E.C.D..................................................................................................................................................46STAGE 4 TSO..................................................................................................................................53Technical system options.................................................................................................................53Meetings............................................................................................................................................60Bibliography......................................................................................................................................64


CS2E23N Page no. 7/64 17/01/2008

STAGE – 3 SPECIFICATIONS OF REQUIREMENTS

STEP - 310 Define Required System processing

Requirements Catalogue

Source: Senior management

Priority: AUser Responsible: Dpt Mgr

Req.ID: 1

Functional Requirement: handle payment and produce receipted bill within the department (using POS)Non-Functional considerations:

Description Target Value Acceptable Range Comments

Response time5 seconds Up to 10 seconds Available all the

time.

Benefits: Save time in handling paymentsComments/Suggested solutions:

Related Documents:

Related Requirements:

Resolution:

Source: Senior Management

Priority: AUser Responsible: Sales manager

Req.ID: 2

Functional Requirement: Produce sales report for the whole store – showing daily sales of each type and daily total for store.Non-Functional considerations:


Report rundaily

Benefits: Improve timeliness and accuracy of sales information for managmentComments/Suggested solutions:

Related Documents:


Resolution:


CS2E23N Page no. 8/64 17/01/2008

Source: Sales manager

Priority: BUser Responsible: Sales manager

Req.ID: 3

Functional Requirement: handle on-line stock enquiries availability and priceNon-Functional considerations:


Time of availabilityResponse time

8am- 10pm daily15 seconds

Maximum 1 min

Benefits: Allow staff up-to-date information on stock heldComments/Suggested solutions:

Related Documents:


Resolution:

Source: Accounts manager

Priority: BUser Responsible: Accounts manager

Req.ID: 4

Functional Requirement: Handle on-line enquiry regarding a particular billNon-Functional considerations:




Maximum 2 min

Benefits: Will enable dept mgrs to check information quickly when dealing with returns.Comments/Suggested solutions:

Related Documents:


Resolution:


CS2E23N Page no. 9/64 17/01/2008

Source: Dept manager

Priority: AUser Responsible: Dept manager

Req.ID: 5

Functional Requirement: Produce a report listing all returned goods each monthNon-Functional considerations:

Description Target Value Acceptable Range CommentsReport run Monthly Maximum 2 min Report produced

monthly – showing for each item returned item code, description and reason for return. Stock should be in order of stock code with totals for quantity of each type of item returned during to month

Benefits: Allow monitoring of satisfaction levels with stock items.Comments/Suggested solutions:

Related Documents:


Resolution:


CS2E23N Page no. 10/64 17/01/2008

Source: Dept managers


Req.ID: 6

Functional Requirement: Produce a report listing value of goods sold by individual salepeople – broken down into type of goodsNon-Functional considerations:


Report runweekly Report produced

weekly – showing total sales for salesperson. Sub-totals should be produced showing value of each type of item sold

Benefits: Allow monitoring of satisfaction levels with stock items

Comments/Suggested solutions:

Related Documents:


Resolution:


CS2E23N Page no. 11/64 17/01/2008

Required Logical DFMContext diagram

Entities have been added to the DFD here.

ALSO ON A3 PAPER (SEE APENDIX)


CS2E23N Page no. 12/64 17/01/2008

Level 1 diagram

ALSO ON A3 PAPER (SEE APENDIX)


CS2E23N Page no. 13/64 17/01/2008

Elementary Process Descriptions

Process ID: 4.1Process Name: Point of SaleDescription: Customer payments details are collected and stored. the customer then the customer receives a receipt for his/her transaction. At the ond of every day a collection of payment details are sent te the account department.

Process ID: 1Process Name: Administer SaleDescription: Stock and sales person details are combined to form a report for the department manager.

Process ID: 6Process Name: Enquiry (sales person, customer, dept mgr)Description: An individual can make an enquiry into an itm which availability and other stock attributs are retuened, ie price and stock quantity

Process ID: 4.2Process Name: Point of SaleDescription: Dept mganager requested a particular bill ( for instance using a recieopt id or customer name). He is then returned the sales details.

Process ID: 5Process Name: Daily sales reportDescription: At the end of every working day a sales report is produced and given to the senior manager.


CS2E23N Page no. 14/64 17/01/2008

I/O Description

DATA FLOW NAME

FROM TO ATTRIBUTE NOTES

customerdetails for bill

b 1.1 cust_idcust_surnamecust_firstnamecust_bankdetailpurchase_datecust_addressitem_iditem_quantitytransaction_iditem_price

When a customer makes a purchase his detail must me taken or logged..

Receipt bill

1.1 b cust_idpurchase_dateitem_codeitem_quantitytransaction_iditem_price

When a customer makes a purchase he receives a receipt to confirm his order/payment.

bill 1.1 c cust_idcust_surnamecust_firstnamecust_bankdetailpurchase_datecust_addressitem_codeitem_quantitytransaction_iditem_price

At the end of every working day , payment details are sent to the accounts dept.

Report of stock sold

1.4 f quantity_solditem_priceitem_code

This daily report contains details of what was sold and the quantity and the price. This is produced for the senior mgr.


CS2E23N Page no. 15/64 17/01/2008

Sales person code and customer purchase details

a 1.1 salesperson_namesalesperson_codesalesperson_qtysolditem_code

Details are sent to build a report

Sales report for individualsales person

1.1 e salesperson_namesalesperson_codesalesperson_qtysolditem_code

A report is created and sent to dept mgr. weekly

request stock info (salesperson)

a 1.5 Item_nameItem_codeItem_priceItem_quantityavailable

request doc info (customer)

b 1.5 Item_nameItem_codeItem_priceItem_quantityavailable

Available ( Boolean yes or no)

Stock item info (customer)

1.5 b Item_nameItem_codeItem_priceItem_quantityavailability

stock item info(salesperson)

1.5 a Item_nameItem_codeItem_priceItem_quantityavailability

stock item info(department)

1.5 e Item_nameItem_codeItem_priceItem_quantityavailability

request stock info(dept mgr)

e 1.5 Item_nameItem_codeItem_priceItem_quantityavailable

customer return details

b 1.3 cust_idItem_nameItem_codeItem_priceItem_quantity


CS2E23N Page no. 16/64 17/01/2008

revised stock price

e 1.2Item_codeItem_nameItem_price

department manager can change the price

Authorisation for return goods

e 1.3 cust_idItem_codeItem_name

department manager decision to whether the good should be accepted or not

receipted bill c 1.1 cust_idItem_nameItem_codeItem_priceItem_quantity

returns information

1.3 c cust_id

returns information(faulty goods)

1.3 d cust_idcust_surnamecust_firstnamecust_bankdetailpurchase_datecust_addressitem_codeitem_quantitytransaction_iditem_price

stock clerk deal with the return goods before refunding it.


CS2E23N Page no. 17/64 17/01/2008

Logical Data Store/ Entity Cross Reference

Data Store Entity


CUSTOMER

BILL

BILL LINE

STOCK ITEM

D1 SALES

D2 STOCK

CS2E23N Page no. 18/64 17/01/2008

User Catalogue

Job Title Responsibility

Department Manager Authorise refund and exchanges. Liaise with customer. Inspect goods. Reach decision on whether to offer a refund/exchange.Track individual sales people, for instance How many and what type of product they have sold.Check availability and price of individual stock item. Check particular bill; Payment method etc.

Senior Manager Checks the sales report daily for whole store, checks what types of stock sold and total values.

Sales person Check available stock item and its price.

Customer sales. Assist customer in choosing purchases. Carry out sales and payment procedures where applicable.

Return Goods Complete return form when authorised by Manager

Buyers (Customers) Check available stock item and price of stock item so then can select which product they would like to buy

Stock Clerk (Sales and Return)

Update Stock record cards to take account of sales. Collect tickets (from sold items) from departments each evening. Update Stock cards to take account of sales for the day.

Update Stock record cards to take account of return goods. When a Stock Returns form is received for good that have been brought back because they are unsuitable, update stock cards to take account of the return.

Modify price tickets Change price tickets on garments in accordance with the instruction of the Department Managers

Accountant Responsible for issuing refund.

Responsibilities in Blue are updated *


CS2E23N Page no. 19/64 17/01/2008

STEP- 320 Develop Required Data Model

Required System Logical Data Model


BILLCUSTOMER

STOCK ITEMSALES PERSON

BILL LINE

MANAGER

DEPARTMENT

DATE

ORDER

CS2E23N Page no. 20/64 17/01/2008

Data Catalogue

CUSTOMER

Attributes Type Length

Customer_id Text 15

Customer surname Text 25

First name Text 25

Address Text 60

BILL


Bill_no numeric 20

Bill_date date Dd/mm/yyyy

Salesperson code Numeric 4

Cumstomer_id Text 15

BILL LINE


Bill_no Numeric 20

Item_code Text 10

Bill item quantity Numeric Max

Bill item price currency £12345.10

STOCK ITEM


Item_code Text 10

item description Text 50

Current price Currency £12345.10

Quantity in stock Numeric Max

Reorder level Numeric Max

Reorder quantity Numeric Max

On order Boolean Yes/no


CS2E23N Page no. 21/64 17/01/2008

SALES PERSON


Salesperon code Numeric 4

Salesperson name Text 25

Salseperson surname Text 25

MANAGER


Manager code Numeric 4

Manager name Text 25

Manager surname Text 25

Manager contact detail Text 50

Date


Date Date dd/mm/yyyy

Qty Sold Numeric Max

Qty in stock Numeric Max

Qty ordered Numeric Max

Qty delivered Numeric Max

Stock code Text 10

ORDER


Stock Code Text 10

Date date dd/mm/yyyy

DEPARTMENT


Dept Code Text 10

Manager Code Text 10


CS2E23N Page no. 22/64 17/01/2008

STEP - 330 Derive system functions

Update function definitions

Function Name: Customer makes a purchase Function Id: 1

Function Type: on-line

Function Description: customer gives purchase details ( product and payment details

Error Handling: if details incorrect display error

DFD Processes: 1.1

Events: produce receipt Event Frequency: 1

I/O Structures: 2

I/O Descriptions: b-1.1, a-1.1, 1.1-b

Related Functions: None

Enquiries: Price Enquiry Frequency: 1 sec

Common Processing: None


CS2E23N Page no. 23/64 17/01/2008

Function Name: Request stock information Function Id: 2

Function Type: On-Line

Function Description: A user request details of any particular stock

Error Handling: stock code must be correct or error is displayed

DFD Processes: 1.5

Events: display stock details Event Frequency: 1000 per day

I/O Structures:

I/O Descriptions:e-1.5, b-1.5, a-1.5

Related Functions: none

Enquiries: Quantity Stock amount, price etc, Enquiry Frequency: 1 sec



CS2E23N Page no. 24/64 17/01/2008

Function Name: Revised Stock Price Function Id: 3


Function Description: Stock price changed

Error Handling: Feasible price, and Currency

DFD Processes: 1.2

Events: Stock price is changed Event Frequency: 50 per day

I/O Structures: none

I/O Descriptions: e-1.2

Related Functions: none

Enquiries: Quantity Stock amount, price etc, Enquiry Frequency: 1 sec



CS2E23N Page no. 25/64 17/01/2008

Function Name: Refunds Function Id: 4


Function Description: Customer refunds

Error Handling: to stock clerks discretion

DFD Processes: 1.3

Events: A refund may or may not be given Event Frequency: 40 per day

I/O Structures: 3

I/O Descriptions: b-1.3, e-1.3, 1.3-d, 1.3-c

Related Functions: Enquiry (1.5)

Enquiries: item price, item name, customer id, customer payment details Enquiry Frequency: 1 sec



CS2E23N Page no. 26/64 17/01/2008

Function Name: Sales report Function Id: 5

Function Type: Off-Line/On-Line

Function Description: A sales report is produced

Error Handling: n/a

DFD Processes: 1.4

Events: A report is built Event Frequency: 1 per week/1 per month

I/O Structures: 1

I/O Descriptions: 1.4-f

Related Functions: Enquiry (1.5)

Enquiries: stock quantity, item price, item code, Sales person id, Enquiry Frequency: 1 sec



CS2E23N Page no. 27/64 17/01/2008

User Catalogue

Job Title Responsibility

Department Manager Authorise refund and exchanges. Liaise with customer. Inspect goods. Reach decision on whether to offer a refund/exchange.Track individual sales people, for instance How many and what type of product they have sold.Check availability and price of individual stock item. Check particular bill; Payment method etc.

Senior Manager Checks the sales report daily for whole store, checks what types of stock sold and total values.

Sales person Check available stock item and its price.

Customer sales. Assist customer in choosing purchases. Carry out sales and payment procedures where applicable.

Return Goods Complete return form when authorised by Manager

Buyers (Customers) Check available stock item and price of stock item so then can select which product they would like to buy

Stock Clerk (Sales and Return)

Update Stock record cards to take account of sales. Collect tickets (from sold items) from departments each evening. Update Stock cards to take account of sales for the day.

Update Stock record cards to take account of return goods. When a Stock Returns form is received for good that have been brought back because they are unsuitable, update stock cards to take account of the return.

Modify price tickets Change price tickets on garments in accordance with the instruction of the Department Managers

Accountant Responsible for issuing refund.


CS2E23N Page no. 28/64 17/01/2008

I/O structures

1. Sales Reports

I/O Structure Description – Sales Reports

Structure Element Attributes

Daily report Report details

Weekly report Report details

Build daily report Items sold, Total of each item sold, Total sold

Build weekly report Sales persons’ names, Items sold, Total of each item sold, Total sold

Send to senior managers Recipient names

Send to department managers Recipient names


CS2E23N Page no. 29/64 17/01/2008

2. New Purchase

I/O Structure Description - New Purchases

Structure Element Attribute

Item details (input) Item code, Item description, Current price

Item details (output) Item code, Item description, Current price

Scan items Item code

Payment method Payment details

Cash payment Item price, Amount given, Change given

Pay Cash Amount given, Item price, Amount of change

Card payment details Card details

Customer card details Card no, Account no, Sort code, Card holder name, Expiry date, Card name

Cash/card mixed payment Card details, Cash details

Pay cash and card details Card details, Cash details

Give receipt Receipt no, Payment details


CS2E23N Page no. 30/64 17/01/2008

3. Return Goods

I/O Structure Description – Return Goods

Structure Element Attributes

Item description Item code, Item description

Item is faulty item code, Return reason

Item is resalable Item code, Return reason

Give refund Item code, Bill no, Item price, Bill date, Customer id, Sales person code, Amount paid

Make new purchase Item code


CS2E23N Page no. 31/64 17/01/2008

Requirements Catalogue

Source: Senior management

Priority: AUser Responsible: Dept Manager

Req.ID: 1

Functional Requirement: handle payment and produce receipted bill within the department (using POS)Non-Functional considerations:


Response time5 seconds Up to 10 seconds Available all the

time.

Benefits: Save time in handling paymentsComments/Suggested solutions:

Related Documents:


Resolution:

Source: Senior Management

Priority: AUser Responsible: Sales manager

Req.ID: 2

Functional Requirement: Produce sales report for the whole store – showing daily sales of each type and daily total for store.Non-Functional considerations:


Report rundaily

Benefits: Improve timeliness and accuracy of sales information for managmentComments/Suggested solutions:

Related Documents:


Resolution:


CS2E23N Page no. 32/64 17/01/2008

Source: Sales manager

Priority: BUser Responsible: Sales manager

Req.ID: 3

Functional Requirement: handle on-line stock enquiries availability and priceNon-Functional considerations:




Maximum 1 min

Benefits: Allow staff up-to-date information on stock heldComments/Suggested solutions:

Related Documents:


Resolution:

Source: Accounts manager

Priority: BUser Responsible: Accounts manager

Req.ID: 4

Functional Requirement: Handle on-line enquiry regarding a particular billNon-Functional considerations:




Maximum 2 min

Benefits: Will enable dept mgrs to check information quickly when dealing with returns.Comments/Suggested solutions:

Related Documents:


Resolution:


CS2E23N Page no. 33/64 17/01/2008

Source: Dept manager


Req.ID: 5

Functional Requirement: Produce a report listing all returned goods each monthNon-Functional considerations:

Description Target Value Acceptable Range CommentsReport run Monthly Maximum 2 min Report produced

monthly – showing for each item returned item code, description and reason for return. Stock should be in order of stock code with totals for quantity of each type of item returned during to month

Benefits: Allow monitoring of satisfaction levels with stock items.Comments/Suggested solutions:

Related Documents:


Resolution:


CS2E23N Page no. 34/64 17/01/2008

Source: Dept managers


Req.ID: 6

Functional Requirement: Produce a report listing value of goods sold by individual salepeople – broken down into type of goodsNon-Functional considerations:


Report runweekly Report produced

weekly – showing total sales for salesperson. Sub-totals should be produced showing value of each type of item sold

Benefits: Allow monitoring of satisfaction levels with stock items

Comments/Suggested solutions:

Related Documents:


Resolution:


CS2E23N Page no. 35/64 17/01/2008

STEP - 340 Enhance Required Data Model

Relational data analysis model

Customer Bill

UNF Bill (Bill number, Date of Sale, Salesperson Code, Customer id, Customer Name, Customer Delivery Address , stock code, Description, Price, Quantity, Amount, Total).

1.N.F Customer (Customer id, Customer Name, Customer Delivery Address)

Bill (Bill Number, Customer id* Date of Sale, Sales Personcode, Item Description, Price, Quantity, Amount, Total)

2.N.F Customer (Customer id, Customer Name, Customer Delivery Address)

Bill (Bill Number, Customer id* Date of Sale, Sales Personcode, Amount ,Total)

Item (Item Code, Description, Price, Quantity,) //note item merged with stock for 3NF

3.N.F

Customer (Customer id, Customer Name, Customer Delivery Address)

Bill (Bill Number, Customer id* Date of Sale, Amount, Total)

Bill Line (Bill Number*, Stock code*)

*Assumption: A bill can have many Items and Item can have Many Bills*

Stock Item (Description, Price, Quantity, Stock Code , Description, Size, Reorder Level, Reorder Qty, Adjustment, date*)

Sales Person(Sales Personcode, Bill Number*)

Note: assumption. Stock code and item code are the same.


CS2E23N Page no. 36/64 17/01/2008

Stock card

UNF

Stock Code, Description, Size, Qty in stock, Date, Qty Sold, Qty ordered, Qty delivered, Adjustment, Reorder Level, Reorder Qty

1NF

Stock( Stock Code , Description, Size, Reorder Level, Reorder Qty, Adjustment, )

Stock Code*, Description, Size, Qty in stock, Date, Qty Sold, Qty ordered, Qty delivered, Adjustment, Reorder Level, Reorder Qty

2NF

Stock Item( Stock Code , Description, Size, Reorder Level, Reorder Qty, Adjustment, date* )

Date ( Date, Qty Sold, Qty in stock, Qty ordered, Qty delivered, Stock code*

3NF // merging stock and item codes and attributes

Stock Item (Description, Price, Quantity, Stock Code , Description, Size, Reorder Level, Reorder Qty, Adjustment, date*)

Date ( Date, Qty Sold, Qty in stock, Qty ordered, Qty delivered, Stock code*

Order(Stock Code* , Date* )


Customer

Salesperson Stock Item

Bill LineBill

STOCK ITEM

ORDER

DATE

CS2E23N Page no. 37/64 17/01/2008

Returned Goods

UNF

Bill number, Stock description, Stock Code, Price paid, Quantity, Total for refund, Return date, customer id, customer name, customer address, reason for return, action, return to stock, faulty return to supply

1NF

Bill ( bill number, price paid, quantity, total for refund, return date, reason for return, action)

Stock description, Stock Code, customer id, customer name, customer address, return to stock, faulty return to supply, bill number*,

2NF

Bill ( bill number, price paid, quantity, total for refund, return date, reason for return, Amount, action, customer id *)

//stock item attributes same as those in stock card and customer bill.Stock Item (Description, Price, Quantity, Stock Code , Description, Size, Reorder Level, Reorder Qty, Adjustment, date*)

Customer ( customer id, customer name, customer address)


BILL

CUSTOMER STOCK ITEM

CS2E23N Page no. 38/64 17/01/2008

Logical Data Model


BILLCUSTOMER

STOCK ITEMSALES PERSON

BILL LINE

MANAGER

DEPARTMENT

DATE

ORDER

CS2E23N Page no. 39/64 17/01/2008

STEP - 360 DEVELOP PROCESSING SPECIFICATION

Entity access Matrix


CS2E23N Page no. 40/64 17/01/2008

E.A.P (Enquiry Access Path)

EAP for The total value of individual types of stock sold and the total value.

Stock_code 1. Get input Stock_code2. Read Stock by Stock _code3. Output Stock_code

E.A.P For Sale person report

Salesperson_code 1. Get input Salesperson_code2. Read Salesperson by Salesperson _code3. Output Salesperson_code


StockItem

Salesperson

1 2

321

3

CS2E23N Page no. 41/64 17/01/2008

E.A.P For Ad Hoc Inquiry report

Stock_code, Stock_name 1. Get input Stock_code, Stock_name2. Read Stock by Stock _code and stock_name3. Output Stock _Availibility, Stock_price

E.A.P For Facility to check details for a particular bill

Bill_no, Date 1. Get input Bill_no2. Read Bill by Bill_no and Date3. Output Bill_no, payment _method


StockItem

321

Bill

321

CS2E23N Page no. 42/64 17/01/2008

E.L.H (Entity Life History)

- / 1 1,2,3/2 1,2,3/-

1 Create Bill2. Set Bill_number = System3. Set Bill_date = System4. Set Salespeson = System5. Set Customer id= System

- / 1 1,2,3/2 1,2,3/23 1,2,3/-

1 Create StockItem2. Set Stock code = Input3. Set Description = input4. Set Reorder level = Input5. Set size = input6. Set reorder qty = input


Bill

Customer Make new purchase

Refund oGranted

Bill

StockItem

New Stock Change Stock o price

Refund Granted (quantity changed)

Delete Stock

4

CS2E23N Page no. 43/64 17/01/2008

7. Set Adjustment = input8. Set date= system9 .set price = input

- / 1 1,2 /-

1 Create Manager2. Set Manager_id = input3. Set Manager_address = input4. Set Manager_contact=input

- / 1 1,2 /-

1 Create Department2. Set Department _code = input3. Set Manager_code = input


Manager

Manager Employed

Managerretire2, 3, 4

Department

Department created

Department shutdown

3, 4

CS2E23N Page no. 44/64 17/01/2008

- / 1 1,2 /-

1 Create Manager2. Set Manager_id = input3. Set Manager_address = input 4. Set Manager_contact=input

- / 1 1,2/2 1,2 /-

1 Create Date2. Set StockItem_code = input3. Set Qty in stock = input 4. Set set Qty sold = System5. Set qty delivered = Input


Salesperson

SalespersonEmployed

Salespersonretire

2, 3, 4

Start of day Refund granted

Date

Customer makes a purchase

4

CS2E23N Page no. 45/64 17/01/2008

- / 11,2,3 / -

1,2,3 / 2

1 Create Customer2. Set customer_id = system3. Set customer_surname= input 4. Set Firstname = input5. Set address = Input


New Customer

Customer membership removed

Customer

*

Customer makes a purchase

2,3,4,5

CS2E23N Page no. 46/64 17/01/2008

E.C.D

Effect Correspondence Diagram for Customer makes new purchase

1. Inset Customer2.Tie Customer to Bill3. Tie Bill to Salesperson4. Set Customer_id,5 Set Customer surname6 Set First name,7. Set Address8. Set SI of Customer = 19 Write Customer

10. Insert Bill11. Set Bill_no,12.Bill_date13. Set Salesperson code14. Set Cumstomer_id15. Set SI of Bill = 116. Write Bill

17.read Salesperson by Salesperson code18 fail if SI of Salesperson code <> 119. Set Salesperon code20.Salesperson name21.Salseperson surname


Customer

Customer_id,Customer surnameFirst name, Address

1,2,3,4,5,6,7 8,9,10,11,12,13,14

Bill Sales person

Bill_no,Bill_dateSalesperson codeCumstomer_id

Salesperon codeSalesperson nameSalseperson surname

17,18,19,20,21

CS2E23N Page no. 47/64 17/01/2008

Effect Correspondence Diagram for Customer membership removed

1. read Customer by Customer_id2. Fail if SI of Customer <> 1,2,33. delete Customer

Effect Correspondence Diagram for Refund Granted

1. read Bill by Bill_no.2 Fail if SI of Bill <> 1,2,33. Set Bill_date = Input4. Set Salesperson_code = 25. Write Bill


Customer


1,2,3,4,5,6,7

Bill

Bill_no, Bill item PriceBill item quntity

1,2,3,4,5

Set of Bill line

Bill line

CS2E23N Page no. 48/64 17/01/2008

Effect Correspondence Diagram for New Stock

1. read Bill by Bill_no2.2 Fail if SI of Bill <> 1,2,33. Set Bill_date = Input4. Set Salesperson_code = 25. Write Bill

Effect Correspondence Diagram for change stock price

1. read StockItem by Item_code2 Fail if SI of StockIteml <> 1,2,33. Set Item_code = Input4. Set Current_price = input5. Write StockItem


Bill


1,2,3,4,5

Stock Item

Item_codeCurrent_price

1,2,3,4,5

CS2E23N Page no. 49/64 17/01/2008

Effect Correspondence Diagram for Delete stock price

1. read StockItem by Item_code2 Fail if SI of StockIteml <> 1,2,33. Delete StockItem

Effect Correspondence Diagram for Salesperson Employed

1. Insert Salesperson 2. Set Salesperson code = System3. Set Salesperson name = Input4. Set Salesperson surname = input5. Set SI of Salesperson = 16 Write Salesperson


Stock Item

Item_code

1,2,3

Salesperson

Salesperon codeSalesperson nameSalseperson surname

1,2,3,4,5,6

CS2E23N Page no. 50/64 17/01/2008

Effect Correspondence Diagram for Salesperson retire

1. read Salesperson by Salesperson code2 Fail if SI of Salesperson <> 1,23. Delete Salesperson

Effect Correspondence Diagram for Manager Employed

1. Insert Manager2. Set Manager code = System3. Set Manager name = Input4. Set Manager surname = input5. Set Manager Contact detail = Input5. Set SI of Manager = 1,26 Write Manager


Salesperson

Salesperson code

1,2,3

Manager

Manager codeManager nameManager surnameManager contact detail

1,2,3,4,5,6

CS2E23N Page no. 51/64 17/01/2008

Effect Correspondence Diagram for Manager retire

1. read Manager by Manager code2 Fail if SI of Salesperson <> 1,23. Delete Manager

Effect Correspondence Diagram for Department Created

1. Insert Manager2. Set Dept code = System3. Set Manager code = Input4. Set SI of Manager = 1,25 Write Depaertment


Manager

Manager code

1,2,3

Department

Department codeManager name

1,2,3,4,5

CS2E23N Page no. 52/64 17/01/2008

Effect Correspondence Diagram for Manager Shutdown

1. read Department by Dept code2 Fail if SI of Department <> 1,23. Delete Department


Department

Dept code

1,2,3

CS2E23N Page no. 53/64 17/01/2008

STAGE 4 TSO

Technical system options

TSO PROPOSITION 1

EPOS

EPOS terminals will be made up of skeleton Pc’s. Similar to a low spec home PC but without the CD drive, redundant usb slots. The PC will be fitted out with a second hard drive and configured to RAID 0 for internal backup. An EPOS system will run

on top of windows 2000 professional and for offsite backupVERITAS Backup will be used. A connection to a router will be made with 10/100 Ethernet and from there to offsite backup location we will use a dedicated 100Mb high speed line. Each terminal will also have a card reader and a small receipt printer along with a touch screen LCD so no keyboard. For every 5 terminals a shared back and white laser printer will be available.

ONSITE SERVER

For each store the onsite server containing details for the customers that are local to the area and will also act as a gateway firewall for credit card processing. This server will be running windows server 2003. Hardware will be headless will 8 quad core processors and 16GB ram. F secure firewall will be used.

OFFSITE BACKUP AND STORAGE

This main server will run on high level mainframe hardware and a robust customized version of Linux. It will store details of all transactions for reports and other programs to be run against. All POS terminals at the end of every day will be backed up to here. Managers and Departments will have access to certain areas o f the file system remotely

Managerial and Departmental computers

These computers will be running fully loaded office spec hardware and software. Report generation and office packages will be installed on top of windows XP. Access to the mainframe will be available by a 10Mb internet connection over a VPN. Each computer will have a 17 inch LCD monitor, a colour laser printer shared between 3 computers and will be connected to a similar spec headless file server computer by 10/100 Ethernet


CS2E23N Page no. 54/64 17/01/2008

HARDWARE SOFTWARE PRICE( per month) paid off in 3 years

EPOS http://www.firstepos.co.uk/

EPOS premium startup package

25

Skeleton pc 8.50

Windows 2000 pro licence (1000 users)

3

ONSITE SERVER

Windows 2003 server 55

Dell Blade Server 80

OFFSITE MAINFRAME

IBM System z9 enterprise class 1400

Linux customized Free

Manager PC’s

Dell inspiron 530 desktop with windows XP

10

PRINTER COLOUR

HP Colour Laser 5

PRINTER BLACK AND WHITE

HP Laser 2.50

HUBS and ROUTERS

10

ISP 130

TOTAL 200 EPOS TERMINALS and 15 MANAGERS PCS and Servers and software

290,000


http://www.firstepos.co.uk/

CS2E23N Page no. 55/64 17/01/2008


MAINFRAME

EPOS EPOS EPOS EPOS EPOS

PRINTER B/W

PCPCPC

PRINTER COLOUR

SERVER

HUB

HUB

ROUTERFILESERVER

CS2E23N Page no. 56/64 17/01/2008

TSO PROPOSITION 2

Notes and Assumptions:

A store wide WIFI is used to link the system. Lines in the diagram represent normal operations, other situations are possible in case of mainframe failure and power loss.

"Transactions" refers to all sales and returns. As well as being able to store data for around a day of transactions independantly, the EPOS server provides Online Transaction Processing between the tills and the storage server. In exceptional circumstances sales and returns but not stock enquiries can operate with out the storage and main server or any other services except the network router.

Ordering replenishment goods will also be imposible with out access to at least the storage software, however this is batch processing and will not effect the main shop floor operations.

The Chip and Pin readers are part of a of the shelf package including all card readers and a main unit with a direct internet connection to the banking system, linked to the card readers via the WIFI LAN which covers the store.

The storage server contains all the stack and sales databases as well as accounts internal storage, necessary to run the system. It does have copies of all programs necessary to run the whole system in exceptional circumstances. Data is sent for offsite back up perodicaly through out the trading day and at system close down each night.

The main server has software the manage the store wide LAN, companywide wan and general internet use. Using UNIX o/s.

The PCs used by managers and accountants do most of their own processing and access data bases and printing via the server. OpenOffice is used for back office processing, it also interfaces directly with the mySQL database on the storage servers for generation of reports.

Costings:

Training for all office staff will be around £800 each

For the first 6 months or so it is recomended that each store has a dedicated IT support person who will train floor staff and deal with teathing problems. Estimated cost £15,000

Three servers running Red Hat Enterprise Linux Advanced Platform with support for more than two servers, and standard support, around £1000.

OpenOffice for the PCs and reports, and mySQL database softwear, are free for commercial use.

The OpenPOS epos software is also available free for commercial users.

Red Hat Enterprise Linux Desktop for unlimited users, around £50.

200 Users and 15 managers;

70000 Approximately


CS2E23N Page no. 57/64 17/01/2008


CS2E23N Page no. 58/64 17/01/2008

Technical System Option 3

Peripheral Equipment Input device: Keyboard, touch sensitive screen, Barcode Reader

Keyboard: Will be used for Input records, Modify recordsTouch Sensitive Screen: for quick lookup (Search) what items are available. (Customer, salesperson, manager)

Barcode Reader: to read barcode of an Item when customer makes a purchase.

Output Device: Laser printer, Small laser receipt printer

Laser printer: To print Daily and weekly reports for the department managers.Small Laser receipt printer: To print receipt when customer purchases an item.

Storage Device: Magnetic tape for backup purpose, UPS (uninterruptable Power Supply) Disk storage for temporary purpose

System Configuration:Multiuser System: 200 customers can access to the server at the same times. UNIX O/S will be appropriate. (L.A.N)

Software: bespoke software will provide what business requirements are.

Data storage organisation:

Sequential files: Every time customer makes a new purchase the system will generate ID by itself hence, it is convenient to have sequential files.

Database Management system:Multiuser database system more than 200 customers can access to the system at the same time.

Process model: Transaction processing: because it will output response to customer for example; a customer search’s for an item and that item has sold out then the system will display massage that item sold out “would you like to order it?”

Finance:

Printer 100*15 = 1500

Epos Touch screen = 200 * 100 = 20000, 15*100 = 1500

Keyboard = 15*20 = 300

Mouse = 15*10 =150

(LAN) = 200 = 700

Bespoke software= 20000

Data storage = 50000


CS2E23N Page no. 59/64 17/01/2008

TOTAL COST =100450

ALL NUMBER FOR FINACE ARE IN POUNDS


CS2E23N Page no. 60/64 17/01/2008

Meetings

12/11/2007

NAMES OF GROUP MEMBERS:Oluwatobiloba BlackDavid MahonyRuth TyeYogesh.S MangelaFormed a group of four members with the above names and decided to meet every Mondays at 12.00pm and Thursdays at 11.30am. On the first day of the meeting, one of the group members (Oluwatobiloba Black) was ill and couldn’t attend the meeting, the other group members started the coursework.We started by doing the Requirement catalogue.

15/11/2007

Attended by all

We started by going through the Requirement catalogue that was done in the first meeting, also did the Required Logical Data Flow Model. There was a disagreement about if the coursework should be broken into different parts with each group member assigned to do one part each. Concluded it was better to all do it together.

19/11/2007

Attended by all

Did the User role and more of the requirement catalogue.

22/11/2007

Attended by all

Did the Required system Logical data model.

26/11/2007


CS2E23N Page no. 61/64 17/01/2008

Attended by all

Did the Data catalogue and there was a disagreement about how the data catalogue was meant to be done. Concluded and agreed to review it in the next meeting.

29/11/2007

Attended by all

Checked and updated all the steps that’s been done. Made a few changes to the Requirement catalogue, reviewed the Data catalogue and updated it.

3/12/2007

Attended by three of the group members.

One of the group member (David Mahony) missed the meeting due to illness. The rest of the group members did step 360 and agreed to finish it up in the next meeting.

6/12/2007

Attended by all

Explained what the group did in the last meeting to the group member that missed the meeting and updated step 36o. Also updated the Requirement catalogue.

10/12/2007

Attended by three of the group members.

One of the group member (Ruth Tye) missed the meeting due to illness. The rest of the group members did step 340 Normalisation and updated the Requirement catalogue.

13/12/2007

Attended by all

The group disagreed about if exchanging goods should have its own process while working on the Current Logical Data Flow Model.

17/12/2007 11am

Attended by all


CS2E23N Page no. 62/64 17/01/2008

The group worked on the customer purchases and returned goods Current Logical Data Flow Model. The group continued to disagree about whether the Department Managers decision on accepting returned goods should be represented as a process box or as text and arrow format. After agreeing to spend the weekend considering last Thursday’s disagreement on how to represent exchanging goods, the group decided to represent it as a return and new sale rather than as a separate exchange process.

18/12/2007 11am - 3pm

Attended by all

The group updated the Required Logical Data Flow Model. The data stores were reduced to stock and sales only, removing departmental storage in line with decisions taken in the previous meeting. While updating the requirements catalogue, some of the group did not agree that the requirements catalogue should be updated. We settled this by referring to Weaver 1993

Practical SSADM4.

19/12/2007

Attended by all

The group worked on the Logical Data Store, Entity Cross References and Elementary Process Descriptions, after discussing data storage we decided to remove departmental storage and use two data stores, stock and sales. We checked that the Required Logical Data Flow Diagram was consistent with the requirements catalogue.

9/01/2008

While revising all the work done so far, the group agreed that any differences between the attributes of the "Stock" and "Stock Item" were not necessary for the system to function. The Logical Data Flow Model was revised to merge the stock and stock item entities. Input/Output Structure Diagrams and Description Tables were derived from the Requirements Catalogue.

The group gained a good understanding of this technique during the course of the module and it was completed with out problems.


CS2E23N Page no. 63/64 17/01/2008

10 & 11/01/2008

The Relational Data Analysis Model was revised in response to discrepancies between it and the Data Flow Model. the new RDAM reflected changes to the entities and their attributes which arose during updates of the requirements catalogue and such like as recommended in the blue thing yog has.

14/01/2008

The group started work on the Entity Access Matrix. The fist draft had very few birth, death and modification events, it was agreed that this would be improved by changing the contents of the events axis. The functions definitions were drafted prematurely to assist with this. This demonstrated one advantage of SSADM's discrete modular steps, whose order can be altered slightly to respond to difficulties in other areas.

16/01/2008The Function Definitions were created with reference to the Input/Output Structure Diagrams and Description Tables, these were used to help complete the Entity Access Matrix. Entity Life History Diagrams were also completed today


CS2E23N Page no. 64/64 17/01/2008

Bibliography

Books - Practical SSADM version 4 / Philip L. Weaver Weaver, Philip L.

SSADM Version 4 : a user's guide / Malcolm Eva Eva, Malcolm,

SSADM models and methods version 4 / S. Skidmore, G Mills and R Farmer Skidmore, Steve

Introducing SSADM (version 4) Longworth, G. (Gordon)

Other – Various web sites accessed from www.google.com

Lecture notes week3- week10


http://www.google.com/

http://catalogue.londonmet.ac.uk/search?/Yssadm&SORT=D&searchscope=1/Yssadm&SORT=D&searchscope=1&SUBKEY=ssadm/1%2C21%2C21%2CB/frameset&FF=Yssadm&SORT=D&searchscope=1&15%2C15%2C




ssadm

Documents

unit organiser assignment

unit assessment total

group assignment

assignment specification

assessors initials

tony royce

header sheet

structured systems analysis