You are on page 1of 65

CS2E23N Page no.

1/64 17/01/2008
London Metropolitan University
Department of Computing, Information Systems & Mathematics

Coursework Assignment Header:
STUDENT REFERENCE
NUMBER_______________06022698____________________________________

FAMILY NAME
AND 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:________________________________

ASSESSOR’S COMMENTS

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

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

London Metropolitan University
Department of Computing, Information Systems & Mathematics

Coursework Assignment Header:
STUDENT REFERENCE
NUMBER_____________05041673______________________________________

FAMILY NAME
AND INITIALS (Please print):_____RUTH TYE____________________________________________

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

ASSESSOR’S COMMENTS

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

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

London Metropolitan University
Department of Computing, Information Systems & Mathematics

Coursework Assignment Header:
STUDENT REFERENCE
NUMBER_____________ 06000239______________________________________

FAMILY NAME
AND INITIALS (Please print):__OLUWATOBILOBA BLACK __

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

ASSESSOR’S COMMENTS

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

YOU SHOULD NOT DELAY SUBMISSION OF THIS GROUP ASSIGNMENT BECAUSE ONE MEMBER HAS A SHORT PERIOD OF ABSENCE. and have supporting documentary evidence. incl. 4/64 17/01/2008 London Metropolitan University Department of Computing.Mangela . All grades are provisional until confirmed by the Board of Examiners. Please sign below to say that you have read and understand these extracts: (signature:)_________________________________________________________________________________ D. Longer periods of absence should be discussed with Tony. Resit Weighting : 50%: Week beginning 5th November.16):____________________ N. PLAGIARISM You are reminded that there exist regulations concerning plagiarism. If you have valid mitigating circumstances.Mahony R. ASSESSOR'S INITIALS:________________________________ ASSESSOR’S COMMENTS Unit number : CS2E23C/N Unit name : Structured Systems Analysis Unit Organiser : Tony Royce Assignment no.CS2E23N Page no. Information Systems & Mathematics Coursework Assignment Header: STUDENT REFERENCE NUMBER__________06002585 FAMILY NAME AND INITIALS (Please print):_______ YOGESH . Extracts from these regulations are printed overleaf. then obtain and complete a mitigating cirucmstances form and have it authorised.Tye T. Black Y.S. 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.B.2007 (Week6) (% of unit assessment total. MANGELA ____ GRADE POINT ALLOCATED (0 .

CS2E23N Page no.Tye T. Black Y. D. No work will be accepted without it.Mangela .Mahony R. 5/64 17/01/2008 This header sheet should be attached to the assignment specification and to the work you submit.

05041673 OLUWATOBILOBA BLACK . David Mahony .Tye T. Black Y.CS2E23N Page no.06002585 17th January 2008 D. 6/64 17/01/2008 CS2E23N Coursework Assignment [SSADM Stage 3 and 4] By .Mahony R.Mangela .06022698 Ruth Tye .06000239 Yogesh Mangela .

.............................43 E.................57 Meetings.................54 Technical system options....................................64 D................................................................47 STAGE 4 TSO.............................................................................................40 Entity access Matrix........................................................................................28 I/O structures.................................................................54 Three servers running Red Hat Enterprise Linux Advanced Platform with support for more than two servers..............................................................................................................................................................................................8 Required Logical DFM...........................................................20 Data Catalogue..............................18 User Catalogue.....................................................................................................................................................................................D.........................................................................................................................................................................................................................................8 Requirements Catalogue......................................................................... around £50.....................................................................................................................14 I/O Description................................................................................................21 STEP ................................................................................................................................. around £1000............................................................................................... and mySQL database softwear.............................................................................29 Requirements Catalogue...........................................L....................................65 Bibliography..........H (Entity Life History)..... Black Y....................................39 STEP ............................................................................................................................................................................................................................................................A.............................. are free for commercial use.......................................................................................................................................................................................................310 Define Required System processing...........................................................19 STEP.............................57 The OpenPOS epos software is also available free for commercial users..............................C.57 OpenOffice for the PCs and reports............................................................................................................................................................320 Develop Required Data Model................. 7/64 17/01/2008 Contents Page STEP ........................13 Elementary Process Descriptions.....................................................................................................................................57 Red Hat Enterprise Linux Desktop for unlimited users.............................................36 Logical Data Model..23 Update function definitions.......................360 DEVELOP PROCESSING SPECIFICATION...................................40 E......................................61 Bibliography.............................................................P (Enquiry Access Path).. and standard support..............15 Logical Data Store/ Entity Cross Reference.........................32 STEP ...........................................................................Mangela ...........Tye T.............................12 Level 1 diagram.......................................................................................340 Enhance Required Data Model.................................................................330 Derive system functions............................................................................................36 Relational data analysis model.......................................................................23 User Catalogue................41 E.......................................................................CS2E23N Page no.............Mahony R.......................

Mahony R. Non-Functional considerations: Description Target Value Acceptable Range Comments daily Report run Benefits: Improve timeliness and accuracy of sales information for managment Comments/Suggested solutions: D.CS2E23N Page no. 8/64 17/01/2008 STAGE – 3 SPECIFICATIONS OF REQUIREMENTS STEP .Mangela .ID: 2 Management User Responsible: Sales manager Functional Requirement: Produce sales report for the whole store – showing daily sales of each type and daily total for store.Tye T.310 Define Required System processing Requirements Catalogue Source: Senior Priority: A Req. Benefits: Save time in handling payments Comments/Suggested solutions: Related Documents: Related Requirements: Resolution: Source: Senior Priority: A Req. Black Y.ID: 1 management User Responsible: Dpt Mgr Functional Requirement: handle payment and produce receipted bill within the department (using POS) Non-Functional considerations: Description Target Value Acceptable Range Comments 5 seconds Up to 10 seconds Available all the Response time time.

Tye T. Black Y.Mangela . Comments/Suggested solutions: Related Documents: Related Requirements: Resolution: D.10pm daily Maximum 2 min Time of availability 30 seconds Response time Benefits: Will enable dept mgrs to check information quickly when dealing with returns.10pm daily Maximum 1 min Time of availability 15 seconds Response time Benefits: Allow staff up-to-date information on stock held Comments/Suggested solutions: Related Documents: Related Requirements: Resolution: Source: Accounts Priority: B Req.ID: 3 manager User Responsible: Sales manager Functional Requirement: handle on-line stock enquiries availability and price Non-Functional considerations: Description Target Value Acceptable Range Comments 8am.ID: 4 manager User Responsible: Accounts manager Functional Requirement: Handle on-line enquiry regarding a particular bill Non-Functional considerations: Description Target Value Acceptable Range Comments 8am.Mahony R. 9/64 17/01/2008 Related Documents: Related Requirements: Resolution: Source: Sales Priority: B Req.CS2E23N Page no.

ID: 5 manager User Responsible: Dept manager Functional Requirement: Produce a report listing all returned goods each month Non-Functional considerations: Description Target Value Acceptable Range Comments Report run Monthly Maximum 2 min Report produced monthly – showing for each item returned item code. 10/64 17/01/2008 Source: Dept Priority: A Req. description and reason for return. Comments/Suggested solutions: Related Documents: Related Requirements: Resolution: D.Tye T.Mahony R.Mangela . 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.CS2E23N Page no. Black Y.

Mangela .Mahony R.Tye T.ID: 6 managers User Responsible: Dept manager Functional Requirement: Produce a report listing value of goods sold by individual salepeople – broken down into type of goods Non-Functional considerations: Description Target Value Acceptable Range Comments weekly Report produced Report run weekly – showing total sales for salesperson. Black Y. 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: Related Requirements: Resolution: D.CS2E23N Page no. 11/64 17/01/2008 Source: Dept Priority: A Req.

Black Y. ALSO ON A3 PAPER (SEE APENDIX) D.CS2E23N Page no.Mangela .Tye T.Mahony R. 12/64 17/01/2008 Required Logical DFM Context diagram Entities have been added to the DFD here.

Tye T.CS2E23N Page no.Mangela . 13/64 17/01/2008 Level 1 diagram ALSO ON A3 PAPER (SEE APENDIX) D.Mahony R. Black Y.

CS2E23N Page no. Black Y. dept mgr) Description: An individual can make an enquiry into an itm which availability and other stock attributs are retuened. Process ID: 5 Process Name: Daily sales report Description: At the end of every working day a sales report is produced and given to the senior manager. D. He is then returned the sales details.Mangela . customer. 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: 1 Process Name: Administer Sale Description: Stock and sales person details are combined to form a report for the department manager.1 Process Name: Point of Sale Description: Customer payments details are collected and stored. ie price and stock quantity Process ID: 4. 14/64 17/01/2008 Elementary Process Descriptions Process ID: 4.2 Process Name: Point of Sale Description: Dept mganager requested a particular bill ( for instance using a recieopt id or customer name). Process ID: 6 Process Name: Enquiry (sales person.Mahony R.Tye T.

15/64 17/01/2008 I/O Description DATA FLOW FROM TO ATTRIBUTE NOTES NAME b 1. item_quantity transaction_id item_price 1. Black Y.. item_code item_quantity transaction_id item_price D. bill 1.Mahony R.CS2E23N Page no.1 cust_id When a customer cust_surname customer details for bill cust_firstname makes a cust_bankdetail purchase his purchase_date detail must me cust_address taken or item_id logged.1 c cust_id At the end of cust_surname every working cust_firstname day . payment cust_bankdetail details are sent purchase_date to the accounts cust_address dept.Tye T.Mangela .1 b cust_id When a purchase_date customer Receipt bill item_code makes a item_quantity purchase he transaction_id receives a item_price receipt to confirm his order/payment.

1 e salesperson_name A report is individual salesperson_code created and sales person salesperson_qtysold sent to dept item_code mgr.5 Item_name Available (customer) Item_code ( Boolean yes Item_price or no) Item_quantity available Stock item info 1.Tye T.Mahony R. This is produced for the senior mgr.5 a Item_name info(salesperson) Item_code Item_price Item_quantity availability stock item info 1. weekly request stock a 1.5 Item_name info Item_code (salesperson) Item_price Item_quantity available request doc info b 1. Sales person a 1.5 b Item_name (customer) Item_code Item_price Item_quantity availability stock item 1.5 e Item_name (department) Item_code Item_price Item_quantity availability D.CS2E23N Page no.4 f quantity_sold This daily sold item_price report contains item_code details of what was sold and the quantity and the price. 16/64 17/01/2008 Report of stock 1. Black Y.1 salesperson_name code and salesperson_code Details are sent customer salesperson_qtysold to build a purchase details item_code report Sales report for 1.Mangela .

3 cust_id department for return goods Item_code manager Item_name decision to whether the good should be accepted or not receipted bill c 1.CS2E23N Page no.3 c cust_id information returns 1.1 cust_id Item_name Item_code Item_price Item_quantity returns 1.Mahony R. Black Y.Tye T.2 department price Item_code manager can Item_name change the Item_price price Authorisation e 1. purchase_date cust_address item_code item_quantity transaction_id item_price D. 17/64 17/01/2008 request stock e 1.3 d cust_id stock clerk deal information cust_surname with the return (faulty goods) cust_firstname goods before cust_bankdetail refunding it.Mangela .3 cust_id details Item_name Item_code Item_price Item_quantity revised stock e 1.5 Item_name info(dept mgr) Item_code Item_price Item_quantity available customer return b 1.

CS2E23N Page no.Mahony R.Tye T. 18/64 17/01/2008 Logical Data Store/ Entity Cross Reference Data Store Entity CUSTOMER D1 SALES BILL BILL LINE STOCK ITEM D2 STOCK D.Mangela . Black Y.

Inspect goods. 19/64 17/01/2008 User Catalogue Job Title Responsibility Department Manager Authorise refund and exchanges.Mangela . Customer sales. Black Y.Tye T. Carry out sales and payment procedures where applicable. Update Stock record cards to take account of return goods.Mahony R.CS2E23N Page no. Track individual sales people. for instance How many and what type of product they have sold. Payment method etc. Check availability and price of individual stock item. Modify price tickets Change price tickets on garments in accordance with the instruction of the Department Managers Accountant Responsible for issuing refund. D. Liaise with customer. checks what types of stock sold and total values. Senior Manager Checks the sales report daily for whole store. Assist customer in choosing purchases. Reach decision on whether to offer a refund/exchange. Update Stock cards to take account of sales for the day. Sales person Check available stock item and its price. 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 Update Stock record cards to take account of sales. 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. Collect Return) tickets (from sold items) from departments each evening. Check particular bill.

Black Y.Mangela DEPARTMENT DATE .CS2E23N Page no.Tye T.Mahony R. 20/64 17/01/2008 Responsibilities in Blue are updated * STEP.320 Develop Required Data Model Required System Logical Data Model CUSTOMER BILL BILL LINE SALES PERSON STOCK ITEM ORDER MANAGER D.

Black Y.Mahony R.Tye T. 21/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 Attributes Type Length Bill_no numeric 20 Bill_date date Dd/mm/yyyy Salesperson code Numeric 4 Cumstomer_id Text 15 BILL LINE Attributes Type Length Bill_no Numeric 20 Item_code Text 10 Bill item quantity Numeric Max Bill item price currency £12345.CS2E23N Page no.Mangela .10 Quantity in stock Numeric Max Reorder level Numeric Max Reorder quantity Numeric Max On order Boolean Yes/no D.10 STOCK ITEM Attributes Type Length Item_code Text 10 item description Text 50 Current price Currency £12345.

22/64 17/01/2008 SALES PERSON Attributes Type Length Salesperon code Numeric 4 Salesperson name Text 25 Salseperson surname Text 25 MANAGER Attributes Type Length Manager code Numeric 4 Manager name Text 25 Manager surname Text 25 Manager contact detail Text 50 Date Attributes Type Length 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 Attributes Type Length Stock Code Text 10 Date date dd/mm/yyyy DEPARTMENT Attributes Type Length Dept Code Text 10 Manager Code Text 10 D.CS2E23N Page no.Tye T. Black Y.Mahony R.Mangela .

1 Events: produce receipt Event Frequency: 1 I/O Structures: 2 I/O Descriptions: b-1.Tye T.CS2E23N Page no.Mangela . a-1.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-b Related Functions: None Enquiries: Price Enquiry Frequency: 1 sec Common Processing: None D.Mahony R.1.1. 1. Black Y. 23/64 17/01/2008 STEP .

5 Related Functions: none Enquiries: Quantity Stock amount.5 Events: display stock details Event Frequency: 1000 per day I/O Structures: I/O Descriptions:e-1. 24/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. Black Y. a-1. Enquiry Frequency: 1 sec Common Processing: None D.Mangela .CS2E23N Page no.5.Mahony R.5.Tye T. price etc. b-1.

Enquiry Frequency: 1 sec Common Processing: None D. Black Y.2 Related Functions: none Enquiries: Quantity Stock amount. and Currency DFD Processes: 1.Tye T.Mangela . price etc.2 Events: Stock price is changed Event Frequency: 50 per day I/O Structures: none I/O Descriptions: e-1. 25/64 17/01/2008 Function Name: Revised Stock Price Function Id: 3 Function Type: On-Line Function Description: Stock price changed Error Handling: Feasible price.CS2E23N Page no.Mahony R.

customer id. Black Y.Mangela .3-d.3.CS2E23N Page no.3.Mahony R.3 Events: A refund may or may not be given Event Frequency: 40 per day I/O Structures: 3 I/O Descriptions: b-1. item name. e-1. 26/64 17/01/2008 Function Name: Refunds Function Id: 4 Function Type: On-Line Function Description: Customer refunds Error Handling: to stock clerks discretion DFD Processes: 1.3-c Related Functions: Enquiry (1. 1. customer payment details Enquiry Frequency: 1 sec Common Processing: None D.Tye T. 1.5) Enquiries: item price.

item code.Mangela . 27/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.5) Enquiries: stock quantity. Sales person id. Enquiry Frequency: 1 sec Common Processing: None D.Tye T.Mahony R. item price.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. Black Y.CS2E23N Page no.

Reach decision on whether to offer a refund/exchange. Check availability and price of individual stock item. Senior Manager Checks the sales report daily for whole store. Inspect goods. Customer sales. Liaise with customer.Mahony R. checks what types of stock sold and total values. Assist customer in choosing purchases. for instance How many and what type of product they have sold.Tye T. 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 sales for the day.Mangela . 28/64 17/01/2008 User Catalogue Job Title Responsibility Department Manager Authorise refund and exchanges. Collect Return) tickets (from sold items) from departments each evening. Modify price tickets Change price tickets on garments in accordance with the instruction of the Department Managers Accountant Responsible for issuing refund. Sales person Check available stock item and its price. Update Stock record cards to take account of return goods. Track individual sales people. 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 Update Stock record cards to take account of sales. Carry out sales and payment procedures where applicable. Check particular bill. Payment method etc. Black Y. update stock cards to take account of the return. D.CS2E23N Page no.

Total sold Build weekly report Sales persons’ names. Total of each item sold.Tye T.CS2E23N Page no. 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 sold Send to senior managers Recipient names Send to department managers Recipient names D. Black Y.Mangela . Total of each item sold.Mahony R. 29/64 17/01/2008 I/O structures 1. Items sold.

Payment details D. Card name Cash/card mixed payment Card details. Sort code. Card holder name.New Purchases Structure Element Attribute Item details (input) Item code. 30/64 17/01/2008 2. New Purchase I/O Structure Description . Item price. Expiry date. Amount given. Item description. Change given Pay Cash Amount given.CS2E23N Page no. Current price Item details (output) Item code.Mahony R.Mangela . Cash details Give receipt Receipt no. Black Y. Account no. Current price Scan items Item code Payment method Payment details Cash payment Item price. Cash details Pay cash and card details Card details. Amount of change Card payment details Card details Customer card details Card no.Tye T. Item description.

Item price. Amount paid Make new purchase Item code D. Item description Item is faulty item code. 31/64 17/01/2008 3.Mahony R. Bill no. Sales person code. Return reason Item is resalable Item code. Customer id. Return Goods I/O Structure Description – Return Goods Structure Element Attributes Item description Item code.Mangela . Black Y.Tye T. Bill date.CS2E23N Page no. Return reason Give refund Item code.

Mangela .ID: 2 Management User Responsible: Sales manager Functional Requirement: Produce sales report for the whole store – showing daily sales of each type and daily total for store. Non-Functional considerations: Description Target Value Acceptable Range Comments daily Report run Benefits: Improve timeliness and accuracy of sales information for managment Comments/Suggested solutions: Related Documents: Related Requirements: Resolution: D. 32/64 17/01/2008 Requirements Catalogue Source: Senior Priority: A Req.CS2E23N Page no. Benefits: Save time in handling payments Comments/Suggested solutions: Related Documents: Related Requirements: Resolution: Source: Senior Priority: A Req.ID: 1 management User Responsible: Dept Manager Functional Requirement: handle payment and produce receipted bill within the department (using POS) Non-Functional considerations: Description Target Value Acceptable Range Comments 5 seconds Up to 10 seconds Available all the Response time time.Tye T. Black Y.Mahony R.

ID: 4 manager User Responsible: Accounts manager Functional Requirement: Handle on-line enquiry regarding a particular bill Non-Functional considerations: Description Target Value Acceptable Range Comments 8am.10pm daily Maximum 2 min Time of availability 30 seconds Response time Benefits: Will enable dept mgrs to check information quickly when dealing with returns.CS2E23N Page no.Mangela . Black Y.Mahony R. 33/64 17/01/2008 Source: Sales Priority: B Req.Tye T.10pm daily Maximum 1 min Time of availability 15 seconds Response time Benefits: Allow staff up-to-date information on stock held Comments/Suggested solutions: Related Documents: Related Requirements: Resolution: Source: Accounts Priority: B Req. Comments/Suggested solutions: Related Documents: Related Requirements: Resolution: D.ID: 3 manager User Responsible: Sales manager Functional Requirement: handle on-line stock enquiries availability and price Non-Functional considerations: Description Target Value Acceptable Range Comments 8am.

Black Y. Comments/Suggested solutions: Related Documents: Related Requirements: Resolution: D.CS2E23N Page no.Tye T.Mahony R.ID: 5 manager User Responsible: Dept manager Functional Requirement: Produce a report listing all returned goods each month Non-Functional considerations: Description Target Value Acceptable Range Comments Report run Monthly Maximum 2 min Report produced monthly – showing for each item returned item code. description and reason for return. 34/64 17/01/2008 Source: Dept Priority: A Req. 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.Mangela .

35/64 17/01/2008 Source: Dept Priority: A Req. 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: Related Requirements: Resolution: D.Mahony R. Black Y.Tye T.Mangela .ID: 6 managers User Responsible: Dept manager Functional Requirement: Produce a report listing value of goods sold by individual salepeople – broken down into type of goods Non-Functional considerations: Description Target Value Acceptable Range Comments weekly Report produced Report run weekly – showing total sales for salesperson.CS2E23N Page no.

Quantity. Reorder Level. Customer id* Date of Sale. Price. Customer Delivery Address) Bill (Bill Number.Total) Item (Item Code. Customer id* Date of Sale. Total) 2.N. Sales Personcode. 1. Amount. Stock code*) *Assumption: A bill can have many Items and Item can have Many Bills* Stock Item (Description. Quantity.Mahony R. Description. Salesperson Code.N. Quantity. Price. Black Y.F Customer (Customer id. date*) Sales Person(Sales Personcode.) //note item merged with stock for 3NF 3. Customer Name. 36/64 17/01/2008 STEP . stock code.F Customer (Customer id. Customer Delivery Address) Bill (Bill Number. Size. Total) Bill Line (Bill Number*. Adjustment. Customer Delivery Address) Bill (Bill Number. Customer Name. Quantity. D. Amount. Stock Code. Customer Name.F Customer (Customer id.340 Enhance Required Data Model Relational data analysis model Customer Bill UNF Bill (Bill number.Mangela . Customer id. Sales Personcode. Item Description. Description.CS2E23N Page no.N. Bill Number*) Note: assumption. Amount . Customer Name.Description. Date of Sale. Customer Delivery Address . Amount. Total). Reorder Qty. Customer id* Date of Sale.Tye T. Stock code and item code are the same. Price. Price.

Description. Description. Size. Adjustment. date* ) Date ( Date. Stock code* Order(Stock Code* . Qty ordered. Stock code* 3NF // merging stock and item codes and attributes Stock Item (Description. Qty delivered. 37/64 17/01/2008 Bill Bill Line Customer Stock Item Salesperson Stock card UNF Stock Code. Size. Size. Qty ordered. Adjustment. Reorder Level. Reorder Qty. Size. Qty in stock. Adjustment. Qty in stock. Reorder Qty. Date. Adjustment. Description. Qty delivered. Qty delivered. Date* ) STOCK ITEM DATE ORDER D.Mahony R. Adjustment. Qty Sold. Qty ordered. Qty Sold. Date. Reorder Qty. Qty ordered. Reorder Level. Qty in stock.Mangela . Reorder Level.CS2E23N Page no. Reorder Level. Reorder Qty 1NF Stock( Stock Code. date*) Date ( Date. Qty Sold. Price.Tye T. Reorder Level. Reorder Qty 2NF Stock Item( Stock Code. Description. Stock Code. Qty Sold. Black Y. ) Stock Code*. Qty delivered. Qty in stock. Quantity. Size. Description.

price paid. return date. date*) Customer ( customer id. Stock Item (Description. Black Y. Description. Quantity. customer name. quantity. Stock Code. price paid.CS2E23N Page no. customer address.Mahony R. Quantity. Reorder Level.Tye T. faulty return to supply. return date. action. reason for return. Price paid. 2NF Bill ( bill number. reason for return. Reorder Qty. customer address. Return date.Mangela . customer id. return to stock. Adjustment. action) Stock description. Stock Code. Price. Stock description. quantity. return to stock. customer name. customer id *) //stock item attributes same as those in stock card and customer bill. Amount. action. total for refund. Total for refund. 38/64 17/01/2008 Returned Goods UNF Bill number. customer id. customer name. customer address) CUSTOMER STOCK ITEM BILL D. total for refund. reason for return. Stock Code. bill number*. faulty return to supply 1NF Bill ( bill number. Size.

39/64 17/01/2008 Logical Data Model CUSTOMER BILL BILL LINE SALES PERSON STOCK ITEM ORDER MANAGER DATE DEPARTMENT D.CS2E23N Page no.Tye T.Mahony R.Mangela . Black Y.

Tye T. 40/64 17/01/2008 STEP .Mahony R.360 DEVELOP PROCESSING SPECIFICATION Entity access Matrix D.Mangela . Black Y.CS2E23N Page no.

Black Y. Stock_code 1. 41/64 17/01/2008 E.Tye T. Get input Salesperson_code 2.P (Enquiry Access Path) EAP for The total value of individual types of stock sold and the total value. Output Stock_code StockItem 1 2 3 E.P For Sale person report Salesperson_code 1. Read Stock by Stock _code 3.A.CS2E23N Page no.Mahony R. Output Salesperson_code Salesperson 1 2 3 D.Mangela . Get input Stock_code 2.A. Read Salesperson by Salesperson _code 3.

Get input Bill_no 2. Get input Stock_code.Mahony R.P For Facility to check details for a particular bill Bill_no. Output Bill_no. Read Bill by Bill_no and Date 3. Stock_price StockItem 1 2 3 E.P For Ad Hoc Inquiry report Stock_code.Tye T.A.Mangela .A. Output Stock _Availibility. Read Stock by Stock _code and stock_name 3. Date 1. Black Y. Stock_name 1. payment _method Bill 1 2 3 D. 42/64 17/01/2008 E.CS2E23N Page no. Stock_name 2.

2.H (Entity Life History) Bill Customer Make Refund o Bill new purchase Granted . Set Bill_date = System 4. /1 1.Tye T.Mahony R.CS2E23N Page no.2. Set Stock code = Input 3.2.L. Set Customer id= System StockItem New Stock Change Stock o Refund Delete price Granted Stock (quantity changed) 4 .3/2 1.3/23 1.3/2 1.3/- 1 Create StockItem 2. Set Description = input 4.3/- 1 Create Bill 2. Set Reorder level = Input 5.2. Set reorder qty = input D. Set Bill_number = System 3. Black Y. Set Salespeson = System 5. Set size = input 6.Mangela . /1 1.2. 43/64 17/01/2008 E.

3.2 /- 1 Create Department 2.Mangela . Set Manager_code = input D.2 /- 1 Create Manager 2.Tye T. 4 created shutdown . /1 1. 44/64 17/01/2008 7. Set Manager_contact=input Department Department Department 3. Black Y.set price = input Manager Manager Manager Employed 2. 4 retire . Set date= system 9 .Mahony R. Set Adjustment = input 8. /1 1. Set Manager_id = input 3. Set Manager_address = input 4.CS2E23N Page no. Set Department _code = input 3.

Set set Qty sold = System 5. Set StockItem_code = input 3. 3.2/2 1. Set Qty in stock = input 4. /1 1.2 /- 1 Create Manager 2.Mahony R. /1 1. 45/64 17/01/2008 Salesperson Salesperson Salesperson 2. Set Manager_contact=input Date Start of day Customer makes Refund a purchase granted . Black Y. Set Manager_address = input 4. Set qty delivered = Input D.Mangela .Tye T. Set Manager_id = input 3.CS2E23N Page no.2 /- 4 1 Create Date 2. 4 Employed retire .

Mangela .3 / 2 1 Create Customer 2. Set customer_surname= input 4. Set address = Input D.2.4.3 / - 2.3. Set customer_id = system 3. Black Y. Set Firstname = input 5.2.Tye T.5 Customer makes a purchase 1. 46/64 17/01/2008 Customer New Customer Customer membership removed . /1 * 1.CS2E23N Page no.Mahony R.

3. 12.21 1. Black Y.Salesperson name 21. Write Bill 17.7 8.13.CS2E23N Page no.Mangela .Tye T. 5 Set Customer surname 6 Set First name.5. Salesperson name Bill_no. Set SI of Bill = 1 16. 12.Bill_date 13. 47/64 17/01/2008 E.Salseperson surname D. Set Salesperson code 14. Set Bill_no. Set Salesperon code 20.Mahony R.D Effect Correspondence Diagram for Customer makes new purchase Salesperon code Customer_id.4.14 19. Set Cumstomer_id 15.6.10.Bill_date Salseperson surname Customer surname First name.9.C.2. Set Customer_id.20. 7.read Salesperson by Salesperson code 18 fail if SI of Salesperson code <> 1 19.18. Salesperson code Address Cumstomer_id Customer Bill Sales person 1. Inset Customer 2. Set Address 8. 17. Set SI of Customer = 1 9 Write Customer 10. Tie Bill to Salesperson 4.Tie Customer to Bill 3. Insert Bill 11.11.

Mahony R.2. delete Customer Effect Correspondence Diagram for Refund Granted Bill_no.3. Customer surname First name. Black Y.7 1.6.2.3 3.3 3.4.5. Address Customer 1.3. Set Salesperson_code = 2 5. Write Bill D.4. Fail if SI of Customer <> 1. 48/64 17/01/2008 Effect Correspondence Diagram for Customer membership removed Customer_id. read Customer by Customer_id 2.2. Bill item Price Bill item quntity Bill Set of Bill line Bill line 1.5 1.Tye T.CS2E23N Page no. read Bill by Bill_no.Mangela . 2 Fail if SI of Bill <> 1.2. Set Bill_date = Input 4.

Set Current_price = input 5. read StockItem by Item_code 2 Fail if SI of StockIteml <> 1. Set Salesperson_code = 2 5. Address Bill 1. 2 Fail if SI of Bill <> 1. Customer surname First name.2.3.4.Mangela .2.5 1.4. Black Y.2.Tye T. Write Bill Effect Correspondence Diagram for change stock price Item_code Current_price Stock Item 1.CS2E23N Page no. 49/64 17/01/2008 Effect Correspondence Diagram for New Stock Customer_id.3 3.5 1. Set Bill_date = Input 4.3.3 3. read Bill by Bill_no2.Mahony R.2. Set Item_code = Input 4. Write StockItem D.

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

Effect Correspondence Diagram for Delete stock price

Item_code

Stock Item

1,2,3
1. read StockItem by Item_code
2 Fail if SI of StockIteml <> 1,2,3
3. Delete StockItem

Effect Correspondence Diagram for Salesperson Employed

Salesperon code
Salesperson name
Salseperson surname

Salesperson

1,2,3,4,5,6

1. Insert Salesperson
2. Set Salesperson code = System
3. Set Salesperson name = Input
4. Set Salesperson surname = input
5. Set SI of Salesperson = 1
6 Write Salesperson

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

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

Effect Correspondence Diagram for Salesperson retire

Salesperson code

Salesperson

1,2,3
1. read Salesperson by Salesperson code
2 Fail if SI of Salesperson <> 1,2
3. Delete Salesperson

Effect Correspondence Diagram for Manager Employed

Manager code
Manager name
Manager surname
Manager contact detail

Manager

1,2,3,4,5,6
1. Insert Manager
2. Set Manager code = System
3. Set Manager name = Input
4. Set Manager surname = input
5. Set Manager Contact detail = Input
5. Set SI of Manager = 1,2
6 Write Manager

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

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

Effect Correspondence Diagram for Manager retire

Manager code

Manager

1,2,3
1. read Manager by Manager code
2 Fail if SI of Salesperson <> 1,2
3. Delete Manager

Effect Correspondence Diagram for Department Created

Department code
Manager name

Department

1,2,3,4,5
1. Insert Manager
2. Set Dept code = System
3. Set Manager code = Input
4. Set SI of Manager = 1,2
5 Write Depaertment

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

2 3. Delete Department D.Mahony R. 53/64 17/01/2008 Effect Correspondence Diagram for Manager Shutdown Dept code Department 1.Mangela .3 1. Black Y.Tye T.2. read Department by Dept code 2 Fail if SI of Department <> 1.CS2E23N Page no.

CS2E23N Page no. F secure firewall will be used. This server will be running windows server 2003. 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.Mangela . Report generation and office packages will be installed on top of windows XP. a colour laser printer shared between 3 computers and will be connected to a similar spec headless file server computer by 10/100 Ethernet D. Similar to a low spec home PC but without the CD drive.Tye T. OFFSITE BACKUP AND STORAGE This main server will run on high level mainframe hardware and a robust customized version of Linux. 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. Each computer will have a 17 inch LCD monitor. The PC will be fitted out with a second hard drive and configured to RAID 0 for internal backup. It will store details of all transactions for reports and other programs to be run against. 54/64 17/01/2008 STAGE 4 TSO Technical system options TSO PROPOSITION 1 EPOS EPOS terminals will be made up of skeleton Pc’s. An EPOS system will run on top of windows 2000 professional and for offsite backupVERITAS Backup will be used. Access to the mainframe will be available by a 10Mb internet connection over a VPN. Hardware will be headless will 8 quad core processors and 16GB ram. Black Y. 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. redundant usb slots.Mahony R. All POS terminals at the end of every day will be backed up to here. 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.

50 BLACK AND WHITE HUBS and 10 ROUTERS ISP 130 TOTAL 200 EPOS 290. 55/64 17/01/2008 HARDWARE SOFTWARE PRICE( per month) paid off in 3 years EPOS http://www.Tye T.CS2E23N Page no.Mahony R.Mangela .uk/ 25 EPOS premium startup package Skeleton pc 8.co.000 TERMINALS and 15 MANAGERS PCS and Servers and software D. Black Y.firstepos.50 Windows 2000 pro licence 3 (1000 users) ONSITE Windows 2003 server 55 SERVER Dell Blade Server 80 OFFSITE IBM System z9 enterprise class 1400 MAINFRAME Linux customized Free Manager Dell inspiron 530 desktop with 10 PC’s windows XP PRINTER HP Colour Laser 5 COLOUR PRINTER HP Laser 2.

Tye T.Mahony R. 56/64 17/01/2008 PRINTER B/W EPOS EPOS EPOS EPOS EPOS HUB SERVER MAINFRAME FILE SERV ROUTER ER HUB PC PC PC PRINTER COLOUR D. Black Y.Mangela . CS2E23N Page no.

57/64 17/01/2008 TSO PROPOSITION 2 Notes and Assumptions: A store wide WIFI is used to link the system. As well as being able to store data for around a day of transactions independantly. around £50. and standard support. Using UNIX o/s. The OpenPOS epos software is also available free for commercial users. companywide wan and general internet use. 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. "Transactions" refers to all sales and returns. 70000 Approximately D. around £1000. It does have copies of all programs necessary to run the whole system in exceptional circumstances. 200 Users and 15 managers. 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. OpenOffice is used for back office processing.Mangela . however this is batch processing and will not effect the main shop floor operations. other situations are possible in case of mainframe failure and power loss. linked to the card readers via the WIFI LAN which covers the store. Black Y. OpenOffice for the PCs and reports. Red Hat Enterprise Linux Desktop for unlimited users. The storage server contains all the stack and sales databases as well as accounts internal storage. 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. Data is sent for offsite back up perodicaly through out the trading day and at system close down each night. The PCs used by managers and accountants do most of their own processing and access data bases and printing via the server. the EPOS server provides Online Transaction Processing between the tills and the storage server. The main server has software the manage the store wide LAN. are free for commercial use.000 Three servers running Red Hat Enterprise Linux Advanced Platform with support for more than two servers.Mahony R. it also interfaces directly with the mySQL database on the storage servers for generation of reports. Lines in the diagram represent normal operations.CS2E23N Page no. Ordering replenishment goods will also be imposible with out access to at least the storage software. and mySQL database softwear.Tye T. Estimated cost £15. necessary to run the system.

Mahony R.Tye T. 58/64 17/01/2008 D.CS2E23N Page no.Mangela . Black Y.

Barcode Reader Keyboard: Will be used for Input records. Storage Device: Magnetic tape for backup purpose.Mahony R. UNIX O/S will be appropriate. Database Management system: Multiuser database system more than 200 customers can access to the system at the same time. (Customer. salesperson.A.Mangela . Data storage organisation: Sequential files: Every time customer makes a new purchase the system will generate ID by itself hence. Small Laser receipt printer: To print receipt when customer purchases an item. UPS (uninterruptable Power Supply) Disk storage for temporary purpose System Configuration: Multiuser System: 200 customers can access to the server at the same times. (L. 59/64 17/01/2008 Technical System Option 3 Peripheral Equipment Input device: Keyboard. Output Device: Laser printer.Tye T. Black Y.CS2E23N Page no. it is convenient to have sequential files. 15*100 = 1500 Keyboard = 15*20 = 300 Mouse = 15*10 =150 (LAN) = 200 = 700 Bespoke software= 20000 Data storage = 50000 D.N) Software: bespoke software will provide what business requirements are. manager) Barcode Reader: to read barcode of an Item when customer makes a purchase. Small laser receipt printer Laser printer: To print Daily and weekly reports for the department managers. touch sensitive screen. Modify records Touch Sensitive Screen: for quick lookup (Search) what items are available. 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. Process model: Transaction processing: because it will output response to customer for example.

Tye T. 60/64 17/01/2008 TOTAL COST =100450 ALL NUMBER FOR FINACE ARE IN POUNDS D.CS2E23N Page no.Mangela . Black Y.Mahony R.

15/11/2007 Attended by all We started by going through the Requirement catalogue that was done in the first meeting. We started by doing the Requirement catalogue. 26/11/2007 D. also did the Required Logical Data Flow Model. one of the group members (Oluwatobiloba Black) was ill and couldn’t attend the meeting.30am. 22/11/2007 Attended by all Did the Required system Logical data model.Tye T.00pm and Thursdays at 11. On the first day of the meeting. Concluded it was better to all do it together.S Mangela Formed a group of four members with the above names and decided to meet every Mondays at 12.Mahony R.Mangela . There was a disagreement about if the coursework should be broken into different parts with each group member assigned to do one part each. 61/64 17/01/2008 Meetings 12/11/2007 NAMES OF GROUP MEMBERS: Oluwatobiloba Black David Mahony Ruth Tye Yogesh. the other group members started the coursework. 19/11/2007 Attended by all Did the User role and more of the requirement catalogue. Black Y.CS2E23N Page no.

Made a few changes to the Requirement catalogue. 3/12/2007 Attended by three of the group members. One of the group member (Ruth Tye) missed the meeting due to illness.Tye T. The rest of the group members did step 340 Normalisation and updated the Requirement catalogue. One of the group member (David Mahony) missed the meeting due to illness.Mahony R. 29/11/2007 Attended by all Checked and updated all the steps that’s been done. Black Y. The rest of the group members did step 360 and agreed to finish it up in the next meeting. reviewed the Data catalogue and updated it. Concluded and agreed to review it in the next meeting. 10/12/2007 Attended by three of the group members. Also updated the Requirement catalogue.CS2E23N Page no. 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. 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.Mangela . 62/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. 17/12/2007 11am Attended by all D.

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. after discussing data storage we decided to remove departmental storage and use two data stores. The Logical Data Flow Model was revised to merge the stock and stock item entities. 18/12/2007 11am .Mahony R. We settled this by referring to Weaver 1993 Practical SSADM4. D. 19/12/2007 Attended by all The group worked on the Logical Data Store.Tye T. 63/64 17/01/2008 The group worked on the customer purchases and returned goods Current Logical Data Flow Model. Entity Cross References and Elementary Process Descriptions. the group agreed that any differences between the attributes of the "Stock" and "Stock Item" were not necessary for the system to function. While updating the requirements catalogue. some of the group did not agree that the requirements catalogue should be updated.CS2E23N Page no. The data stores were reduced to stock and sales only. 9/01/2008 While revising all the work done so far. After agreeing to spend the weekend considering last Thursday’s disagreement on how to represent exchanging goods.Mangela . We checked that the Required Logical Data Flow Diagram was consistent with the requirements catalogue. the group decided to represent it as a return and new sale rather than as a separate exchange process. removing departmental storage in line with decisions taken in the previous meeting.3pm Attended by all The group updated the Required 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. Black Y. stock and sales.

Black Y. 16/01/2008 The Function Definitions were created with reference to the Input/Output Structure Diagrams and Description Tables. 14/01/2008 The group started work on the Entity Access Matrix.CS2E23N Page no. Entity Life History Diagrams were also completed today D. 64/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.Mahony R. The fist draft had very few birth. death and modification events. This demonstrated one advantage of SSADM's discrete modular steps.Mangela . whose order can be altered slightly to respond to difficulties in other areas. these were used to help complete the Entity Access Matrix. 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. it was agreed that this would be improved by changing the contents of the events axis.Tye T. The functions definitions were drafted prematurely to assist with this.

(Gordon) Other – Various web sites accessed from www. G Mills and R Farmer Skidmore.Mangela .week10 D.CS2E23N Page no. SSADM Version 4 : a user's guide / Malcolm Eva Eva. Malcolm. Skidmore. G. Weaver Weaver. Philip L. 65/64 17/01/2008 Bibliography Books . Black Y.com Lecture notes week3.Mahony R.Practical SSADM version 4 / Philip L.google.Tye T. Steve Introducing SSADM (version 4) Longworth. SSADM models and methods version 4 / S.