Blue Cut Fashions Software Requirements Specification

8/12/2019 Blue Cut Fashions Software Requirements Specification

1/68

]i

Blue Cut FashionsSoftware Requirements Specification

Author

Sharon Culhane - S3163667 Ida Johansen - S3225651

Ivette Miglis - S3104495 Darren Hart - S3198830

Hula Kahlal - S3236327


2/68


3/68


Page 3 of 68 Monday Group 1 Report

4.12.4. Data Flow Diagram Fulfil Inventory ........................................................... ...................................... 474.12.5. Use Case Check Inventory ................................................................ ................................................ 474.12.6. Extended Use Case - Check Inventory ........................................................... ...................................... 484.12.7. Use Case - Order Inventory ................................................................................................................. 484.12.8. Extended Use Case Order Inventory ........................................................... ...................................... 494.12.9. Flow Chart Order Inventory ............................................................. ................................................. 50

5. Soft Systems Model ..................................................................................... ........................................................... 516.

Requirements .......................................................................................................................................................... 59

6.1. Functional Requirements ......................................................... ................................................................. ..... 596.1.1. Online Sales - External .................................................................................................. ........................... 596.1.2. Online Sales Internal ........................................................ ................................................................. ..... 596.1.3. Store Sales Internal .......................................................... ................................................................. ..... 596.1.4. Stock - Internal ......................................................................................................................................... 596.1.5. Supplier - External .............................................................. ................................................................. ..... 606.1.6. Supplier Internal .................................................................................................................................... 60

6.2. Non Functional Requirements ............................................................ ........................................................... 616.2.1. Design Constraints .............................................................. ................................................................. ..... 646.2.2. Cloud Computing...................................................................................................................................... 64

7. Bibliography ........................................................................................................................................................... 658. Appendix .......................................................... ................................................................. ...................................... 65

8.1. Project Plan ........................................................ ................................................................. ........................... 658.2. Experience Report ......................................................................................................................................... 668.2.1. Activities Log ........................................................................................................................................... 668.2.2. Problems & Solutions ......................................................... ................................................................. ..... 66


4/68



1. Executive Summary

Blue Cut Fashions is a clothing chain that has 3 stores located in Melbournes majorshopping centres. Blue Cut Fashions specialise in blue cotton products that are popularwith teenagers and young adults. Currently the business has a number of issues relatingto its technology and their integration into the current operations. Namely, the core issuesrelate to an inadequate inventory management system, a non existent online orderingsystem, poor store to store communication regarding supplier information and stockavailability and limited information accessibility for senior stakeholders like James Frost(CEO), Jane Fry (Sales manager and buyer) and Franca De Lorenzo (Technical officer).

This report analyses the main issues highlighted by reviewing the information provided byBlue Cut and the stakeholders and applying relevant Business Analysis techniques inorder to deliver a solution that address the problems and enhances the effectiveness ofBlue Cuts operations. The solution systems will attempt to both address the currentexisting issues while building a platform for future growth and viability of the company.

From the research undertaken, a number of solutions were designed. In order to come upfeasible and relevant model systems, a number of key business analysis techniques wereutilised.

This involved the creation of Dataflow diagrams to show the flow of data within a system,flow charts to illustrate the process within the system, use cases to show the key usersand how they will interact with the particular sub-system. Part of this system requirementspecification includes both functional and non-functional requirements and some softsystems methodology components. The soft systems research was necessary as therewas a small disagreement between two of the major stakeholders, James being the CEO

and Jane being the Sales Manager as to what the new solution should entail andaccomplish.

The created solutions in this report were fundamentally designed and created in order toovercome deficiencies in the existing Blue Cut operations. The solutions themselvesaddress the problems at hand and also provide a basis for better customer service andefficiency in the future.


5/68



2. Analysis Current Situation

2.1. Formal Systems Model

The Formal Systems Model looks at the three main areas of the business;

1. Operationsactions performed on a daily basis

2. Decision Making - decisions that need to be made i.e. when to order more inventory3. Performancecan advise how well your business is performing

By identifying these areas, this will help assist the client in determining what it is that theywant to improve. The boundary defines the purpose of the system.

Figure 1.1 Blue Cut Fashions Formal Systems Model

Black circles - Operational sub-systems

Green Circles - Decision-making systems

Purple Circles - Performance monitoring systems

The main sub-systems in the Blue Cut Fashion business are;Salesa new online sales system will enable customers to order via the internet 24/7from anywhere in the world and their order delivered to anywhere in the world.

Inventorythe inventory system should allow all stores to be able to see whatinventory is in stock and at which stores to be able to fulfil a customers order,


6/68



whether it is online or in store, with real-time updates be able to report on stockinventory levels.Supplierthe supplier system will allow better ordering on inventory required, abilityto track where stock is at and supplier information.

3. Blue Cut Fashions Context Diagram

Blue Cut fashions have identified the following system showing the system boundaries,external agents and the major information flows between the agents and the system fortheir business.

Customer

0

Blue Cut fashion

system

Reports

Stock

supply

Management

Supplier

Order Receipt

Store staff

Inventory

information

Inventory

update

Inventory

Information

The following sections will detail each sub-system with use cases, process flows and dataflows.


7/68



4. Supplier

4.1. Overview

Blue Cut Fashion has identified the requirement to maintain efficient and effectiveinformation pertaining to their suppliers. It has been identified that the following criteria isessential:

Orders placed

Orders in transit

Order delivery (when and where)

Information has to be live and accessible by mobile devices

The above criteria are essential in the automation of the following supplier reports1:

Observation 7. Which of our suppliers handles the most product sales?

Observation 8. Who is our best supplier?

Observation 9. What country or state is the source of our best trading partners?

In order to support and collate the above criteria, the following processes must beconsidered:

Login to Blue Cut System (Predefined Process for all Blue Cut System interactions)

Enter New Supplier Contract Information

Edit Supplier Contract Information

Archive Supplier Information

Coordinate Supplier/Stock Management

Report Stock Movement (supports Observation 7.)

Report Best Supplier (supports Observation 8.) Report Best Trading Partner (supports Observation 9.)

Throughout the Supplier analysis, Lean Six Sigma for Service2 Waste Eliminationprinciples was taken into consideration. By eliminating the following, ensures an efficientprocess:

1. Waiting. the time wasted by operators of a system waiting for an outcome2. Over-productionexcess resources such as stock, time, costs towards the

development of an outcome3. Reworkthe cost of labour that could be best used elsewhere4. Motionwalking, stretching, bending

5. Over Processingdoing more work than is required6. Inventoryholding more inventory than is necessary7. Transportationmoving goods from A to B adds cost

1Brief Executive Report, Franca DeLorenzo (20 December 2009)

2Business Improvement methodology


8/68



4.2. Supplier - Data Flow Diagram

The Data Flow Diagram illustrates the External Entities who will interact with the Blue CutFashions Supplier System and what source of information they will be transmitting throughthe system.Level 0

Data Dictionary

Supplier Information - Contact details (address, phone numbers etc)- Products supplied (jeans, t-shirts, jumpers, shoes, accessories

etc)- Service Level Agreements (agreed delivery time, out of stock

notifications, sales margin, supply freezes3)- Other (preferred courier, comments, feedback from Blue Cut

Fashion stores and customers)

Stock Movement - The number of the Suppliers goods that sold (and returned)- Feedback and comments from staff and customers as to the

quality of the product)

Purchase Records - Purchase Orders (cost, goods, returns, credits)- Goods Received (receipt of good date, overall condition of

stock)

Purchase Reports - Account Reconciliations- End of Financial Year- Stocktake

PerformanceReports

- Sales by Supplier (profits, goods, stock movement, country)- Performance by Supplier (within agreed Service Level

Agreement, positive and negative feedback)

3Due to stocktake, suppliers cannot distribute goods throughout certain periods of the year.

0

Blue Cut Fashion

Supplier System

Supplier

AdministratorSupplier Manager

Performance Reports

Procurement

Purchase

Records

Purchase

Report

Supplier Information

Sales

Stock Movement


9/68



4.3. Predefined Process: Login to Supplier System

Throughout each of the following Supplier processes, the following steps are required,Login and Validation. Each time the External Entities need Supplier data, they must loginto the system and the system must validate their credentials (do they have the appropriateaccess to engage with the system for a given activity).

These instances will be defined and identified as Login & Validate process. This actiontakes place throughout each Use Case, Extended Use Case, Data Flow Diagram andFlow Chart for Supplier information interaction within Blue Cut Fashion System.

4.3.1. Data Flow DiagramLogin

Level 1

1.0

Login to Blue Cut

Fashion System

End User

Open

Request

2.0

Select Supplier

Options

Level 21.2

Open SupplierAccess Credentials

1.1

Enter User Name &

Password

OptionsOpen

Request

Data Dictionary

Open Request - Trigger to open System

Access Credentials - Unique identifiers4to ascertain appropriate levels of access tosystem

Options - Selection of Supplier Activity can be accessed

4Also referred to as Primary Key. This identifier allows information to connect to the right Supplier whenever

changes or records are retrieved.


10/68



4.3.2. Use Case Login

Supplier

Administrator

Log In

Navigate to

Suppliers

Select

Supplier

4.3.3. Use Case Extended - Login

Actor/Action System Response

1. This Use Case begins when theSupplier Administrator receives a newSupplier contract and opens the BlueCut Fashion System

2. Requests User login and password

3. Supplier Administrator enters uniqueID and password

4. Validates login and opens newwindow with menu options

5. Supplier Administrator selectsSuppliers

6. Displays a list of Supplier options

7. Supplier Administrator selects NewContract

8. Opens new window generating aunique Supplier ID5

9. Supplier Administrator selects

Supplier10. Opens new window

Alternative Courses For Login & Validate

3. Incorrect unique ID and/or Password

4. System recognises Actor is not authorised to complete event


9. Activity required may not be accessible.

5Primary key. Unique ID for database functionality


11/68



4.3.4. Flow Chart Login

Start

Login to

Blue Cut

Fashion

System

Validate User

Name & Password

Correct

Credentials?

No

Present Menu

Options

Yes

Select

Suppliers

Select

Display Supplier

Action Options

Display

window

No

End

Valid

Credentials?

Yes


12/68



4.4. Enter New Supplier Contract Inform at ion

When a new Supplier has been sourced by Blue Cut Fashions, key information pertainingto that Supplier is entered into the system. The input of contractual data provides SupplierManager with reporting capability.It is assumed that Predefined Process: Login has been completed and External

Entity/Actor can access Blue Cut Fashions Supplier sub-system

4.4.1. Data Flow Diagram - Enter Supplier Contract Information

Level 1

Supplier

Administrator

Contract Details

1.0

Enter Supplier

Contract Information

D

1Supplier File


2.0

Upload Supplier

Contract

Supplier Identifier

D

2

Scanned Contract

File

Softcopy hyperlink3.0

Report Supplier

Performance

Supplier ManagerSupplier

Information

Supplier

statistics

Data Dictionary

Contract Details - Physical document in hand



notifications, sales margin, supply freezes)- Other (preferred courier, comments, feedback from Blue Cut


Supplier Identifier - Unique Identifier for supplier

Softcopy hyperlink - Access link to scanned copy of contract

Supplier Statistics - Supplier Information collated, calculated to gaugeperformance


13/68



4.4.2. Use Case Enter New Supplier Contract Information

Supplier

Administrator

Log In

Navigate to

Suppliers

Select New

Supplier

Save SupplierData

Log Out

Upload Supplier

Data

Scan Contract

4.4.3. Extended Use Case Enter New Supplier Contract Information


1. This Use Case begins when theSupplier Administrator receives a newSupplier contract and opens the BlueCut Fashion System






7. Supplier Administrator selects NewContract

8. Opens new window generating aunique Supplier ID

9. Supplier Administrator enters data intotext fields6

6Empty boxes for Actor to type data


14/68



10. Stores data in RAM7

11. Supplier Administrator uploadsscanned copy of original contract

12. Files scanned copy onto server

13. Supplier Administrator clicks Save.14. Validates mandatory text fields are

completed before saving data ontodatabase

15.Supplier Administrator exits NewSupplier window

16. Displays Supplier menu options

17. Supplier Administrator logs out

18. Confirms if Actor wants to log out

19.Supplier Administrator confirms Yes

20. Close Blue Cut Fashion System

Alternative Courses For Enter New Contract Information




10. Power surges and unsaved changes will be lost

11. No scanned contract to upload

14. Not all mandatory fields completed or noisy data8has been inserted9

17. Supplier Administrator may wish to select another Supplier option or uploadanother new contract

7

Random Access Memory. Temporary storage of data on the computer8Information manually typed (or copied and pasted) into text fields that is incorrectly spelt or irrelevant to meet

sufficient requirements (search capabilities and incorrect referencing)9Consider use of Dropdown menus where required to reduce noisy data


15/68



4.4.4. Flow Chart - Enter Supplier Contract Information

Start

SelectEnter New

Supplier

Enter

Supplier

Information

Display Blank

Supplier text fields

Save Supplier

Information

Confirm

Save

No

Display SalesOrder details

End

All mandatoryfields complete?

Yes

4.5. Edit Supp lier Contract Inform at ionThere will be instances whereby a current Supplier has changes to their contact details orSupplier Manager has re-negotiated the contract and therefore information needs to be


16/68



edited. This process also applies to any feedback and updates that pertain to the Supplierthroughout operations. The input of Supplier changes data provides Supplier Managerwith up to date reporting capability.

4.5.1. Data Flow Diagram - Edit Supplier Contract Information

Level 1Supplier

Administrator


1.0

Locate Supplier

D

1Supplier File


2.0

Edit Supplier Contract

Supplier Identifier

3.0

Report SupplierPerformance

Supplier Manager

Supplier

Information

Supplier

statistics

D

2 Supplier File

Altered Supplier Information

Data Dictionary





Supplier Identifier - Unique Identifier for supplier

Altered SupplierInformation

- Any changes made to existing data

Supplier Statistics - Supplier Information collated, calculated to gaugeperformance


17/68



4.5.2. Use Case Edit Supplier Contract Information

Supplier

Administrator

Log In

Navigate to

Suppliers

Select Existing

Supplier

Save Supplier

Data

Log Out

Edit Supplier Data

4.5.3. Extended Use Case Edit Supplier Contract Information


1. This Use Case begins when theSupplier Administrator receives arequest to edit key contract informationfor Supplier contract and opens theBlue Cut Fashion System






7. Supplier Administrator selects EditContract

8. Opens new window requesting aSearch for unique Supplier ID andSupplier name options

9. Supplier Administrator enters uniqueSupplier ID and/or Supplier Name intorelevant text field, clicks Search

10. Searches database to match unique

Supplier ID and/or Supplier Namethen displays all key data plushyperlink to scanned copy of original


18/68



contract

11. Supplier Administrator edits requiredtext field(s)

12. Stores edited text field(s) data in RAM

13.Supplier Administrator clicks Save.

14. Validates all mandatory text fields arecomplete and displays Click Ok toconfirm changes.

15.Supplier Administrator clicks Ok.

16. Inserts changes onto database

17.Supplier Administrator exits NewSupplier window

18. Displays Supplier menu options




22. Blue Cut Fashion System closes

Alternative Courses for Edit Supplier Contract Information




10. Supplier name given may not be in database

12. Power surge and changes not saved

15. Supplier Administrator selects Do not Save changes

19. Supplier Administrator may wish to select another Supplier option or uploadanother new contract


19/68



4.5.4. Flow Chart - Edit Supplier Contract Information

Start

Enter nameof Supplier

Display

Supplier(s)

Confirm

Changes

Update SupplierInformation

End

Save Changes?

Yes

Is SupplierLlisted?

No

ConfirmSupplier

Display Supplier

details

EditSupplier

Yes

No


20/68



4.6. Arc hive Supplier Inform at ion

A Suppliers contract information may need tobe archived due to a recent takeover orSupplier Manager has identified the need to no longer continue relationships with a currentsupplier. Instead of permanently removing Supplier data, it is recommended that data isstored in accordance with current best practice under AS ISO 15489 (The Australian andinternational standard for records management10). The input of archiving a Supplier

provides Supplier Manager with historical records should they are required for legal orother regulatory review.

4.6.1. Data Flow Diagram - Archive Supplier Contract Information

Level 1

Supplier

Administrator

Archive Request

1.0

Locate Supplier

D

1Supplier File


2.0

Archive Supplier

Supplier Identifier

3.0

Retrieve Archived

Supplier


Information

Supplier

information

D

2Archives File

Archived Supplier Information

Data Dictionary

Archive Request - Supplier Administrator has received a request to archive agiven supplier

Supplier Information - Contact details (address, phone numbers etc)- Products supplied (jeans, t-shirts, jumpers, shoes, accessoriesetc)

- Service Level Agreements (agreed delivery time, out of stocknotifications, sales margin, supply freezes)

- Other (preferred courier, comments, feedback from Blue CutFashion stores and customers)

Supplier Identifier - Unique Identifier* for supplier

Archived SupplierInformation

- Supplier information stored into library and not to be displayedas current supplier from selection of Suppliers

10Reference: http://www.naa.gov.au/records-management/IM-framework/requirements/Standards/AS-ISO-

15489.aspx
http://www.naa.gov.au/records-management/IM-framework/requirements/Standards/AS-ISO-15489.aspxhttp://www.naa.gov.au/records-management/IM-framework/requirements/Standards/AS-ISO-15489.aspxhttp://www.naa.gov.au/records-management/IM-framework/requirements/Standards/AS-ISO-15489.aspxhttp://www.naa.gov.au/records-management/IM-framework/requirements/Standards/AS-ISO-15489.aspxhttp://www.naa.gov.au/records-management/IM-framework/requirements/Standards/AS-ISO-15489.aspx


21/68


22/68



Now

12.Displays Are you sure you want toarchive ?dialog box

13.Supplier Administrator clicks Yes.

14. Opens new window requestingValidation data (Date, AuthorisingSupplier Manager, Reason)

15. Supplier Administrator completesmandatory fields.

16. Validates all text fields* are complete

17.Supplier Administrator clicks Save.

18.Displays Are you sure you want toarchive ?dialog box

19.Supplier Administrator clicks Yes.

20. Transfers selected Supplier data ontodatabase11and displays has successfullybeen archived dialog box

21.Supplier Administrator exits ArchiveSupplier window

22. Displays Supplier menu options23. Supplier Administrator logs out




Alternative Courses for Archive Supplier Information




10. Supplier name given may not be in database

14. Validation data may not be fully provided to Supplier Administrator

15. Power surge and changes not saved

19. Supplier Administrator selects No

23. Supplier Administrator may wish to select another Supplier option or archiveanother new contract

11Consideration for cloud computing


23/68



4.6.4. Flow Chart - Archive Supplier Contract Information

Start

Enter name

of Supplier

Display

Supplier(s)

ConfirmArchive

Transfer Supplier

Information to

Library

End

Proceed to

Archive?

Yes

Is Supplier

Llisted?

No

ConfirmSupplier

Display Supplierdetails

Select

ArchiveSupplier

Yes

No


24/68



4.7. Coord inate Supp lier/ Stock Management

Requests for moving stock from store to store, from online store to customer and fromBlue Cut Fashions will occur throughout trading hours and 24/7 as online sales increase.The Supplier Administrator is required to oversee stock levels and coordinatetransportation between store/ customer (sales goods) and supplier (returned goods).

Sales staff will identify that a requested good is not available in store and will check otherstores for this item. If the stock is available from another store, a transport request is sentto the Supplier Administrator. If a good is faulty, Sales staff (and online customers) willarrange a request to return the goods. The Supplier Administrator verifies all requests,reviews any online sale requests and arranges the couriers to deliver/receive the goodslogistically. In instances where a customer wants the item delivered on the day and iswilling to accept the courier costs, the Supplier Administrator receives a pop-up emailnotification and SMS text message to their mobile device to ensure efficient stock delivery.

To ensure that in the event whereby stock is low and a customer in store and a customeronline request the same low stocked item, the first customer to secure the item(s) on hold,is entitled to the good. In-store this is done by the sales assistant as they hold the itemfor the customer. Online customers secure the item(s) when adding the good to theirshopping cart.

Where no stock is available in store, both sales staff and online customers can contact theSupplier Administrator. The Supplier Administrator will liaise with Supplier to secure moregoods.

4.7.1. Data Flow DiagramCoordinate Supplier/ Stock Management

Level 1

Sales Support

D1 Inventory file

Order

Request

Supplier

Administrator

1.0

Request Inventory

Online

Customer

Purchase

Request

Request Inventory

Inventory Data

D2 Store locality fileInventory

Availabilty

Location

Data

3.0

Coordinate

Courier

StoreDelivery

Details

SupplierDeliveryDetails2.0

Receipt Request

Request

Inventory

Data Dictionary

Order Request - Requirement to deliver desired stock from another store.

Purchase Request - Requirement to deliver desired stock to secured sale

Inventory Data - Number of item(s) available for sale

Request Data - Order Request and/or Purchase RequestInventoryAvailability

- Inventory Data- Name of Store suburb only


25/68



Location Data - Store location details (address, map reference, phone number,courier rates, pick up schedules by courier)

Delivery Details - Location Data- Courier detailso Pick up addresso

Delivery suburbo Urgency (based on customer specification, i.e. today or

within 5 days)o Dimension (weight x height x depth), quantity, weight of

item(s) transportedo Pick up timeo Delivery timeo Name of consignee and consignoro ATL (Authority To Leave). Consignee/Consignor agrees for

goods to be left unsecured at a collection or drop off pointo Declaration of Dangerous Goods (if applicable)

o Mechanical device availability (forklifts at receiving end tolift bulk items from truck.

4.7.2. Use Case Coordinate Supplier/ Stock Management

Prior to processing Coordinate Supplier/ Stock Management; where stock may be limited,there is the potential of an online customer and sales staff conflict in securing an item topurchase. This is where real time data feeds are necessary to ensure that the first actorto guarantee the order request locks out the visibility of the other actor to see that theitem is still available. This occurrence is illustrated by a lightning bolt in the below UseCase.

Sales

Support

Sales

Support

Log In

Check Inventory

Order Inventory

Log Out

Online

Customer

Online

Customer

Log In

Check Inventory

Purchase

Inventory

Log Out

Failure to deflect this potential issue can misguide the Supplier Administrator tocommence Coordinate Supplier/ Stock Management and incur waste12.

If no conflict has occurred, the order is received by Supplier Administrator and can

proceed to Coordinate Supplier/ Stock Management.

12Refer to Lean Six Sigma for Service, Eliminate Waste


26/68



Supplier

Administrator

Supplier

Administrator

Log In

Receive Request

Inventory

Confirm

Courier

Log Out

Coordinate

Courier

4.7.3. Extended Use Case

Coordinate Supplier/ Stock Management


1. This Use Case begins when theSupplier Administrator receives anInventory Requestfrom Blue CutFashion store or online customer andopens the Blue Cut Fashion System

2. Requests user login and password



5. Supplier Administrator selectsInventory Requests

6. Displays a list of new inventoryrequests

7. Supplier Administrator selects top

(earliest) Inventory Request

8. Opens new window displaying itemrequest (the requesting store andinventory availability)

9. Supplier Administrator clicks Confirm

10. Searches database to match uniqueInventory ID then displays the on-holdstock from available store

11.Supplier Administrator clicks Add to

Courier

12. Holds pick up and delivery location in


27/68



temporary file and displays NextInventory Request dialog box

13.Supplier Administrator clicks No

14. Calculates courier route and displaysReview Courier Options dialog box

13.Supplier Administrator clicks Ok.

14. Displays courier route options tooptimize transport efficiency ofdelivery pick up and drop offs.

15. Supplier Administrator reviews thelogistic display and clicks Proceed.

16. Validates all text fields are completeand places Order Request andDelivery Details into form format

17. Supplier Administrator reviews thedelivery forms and clicks Print.

18. Prints respective Courier DeliveryForm(s)





Alternative Courses for Archive Supplier Information



5. Pop-Up Notification for urgent13Inventory Request received

10. Stock not available in any store and Supplier Name is returned

13. More Inventory Requests exist

15. Supplier Administrator edits routes selected as display data option is not efficient

17. Supplier Administrator edits Delivery form if display data is not efficient

19. Supplier Administrator may wish to select another Supplier option or archiveanother new contract

13Customer requires item today and is willing to borne the cost of courier


28/68



4.7.4. Data Flow Chart Coordinate Supplier/ Stock Management

Start

Select

Inventory

Request

Display Inventory

Requests

Retrieve and

Display Data

Open

Inventory

Request

Confirm

Inventory

Availability

Validate item is in

stock at requested

store

Stock is

on-hold at

selected

Store?

Display Supplier

contact details

End

Display DeliveryDetails

Request

Item from

Supplier

Item Available

from Supplier?Order ItemYes

No

More InventoryRequests?

Yes

Calculate DeliveryRoute

Add toDelivery

Request

Yes

Display Delivery

Route(s)

Close

Inventory

Request

Is Route(s)

Logistical?Open Edit Mode

Delivery RoutesNo

No

Finalise (all)Delivery Routes

Request

Courier

DeliveryForms

Print CourierDelivery Routes

No

Yes

Call

Courier(s)

Informstore that

stock is not

available


29/68



4.8. Report Stock Movement

The Supplier Manager monitors the success of a supplier based on the amount of thegoods sold. Other information may also be reviewed, such as both negative and positivefeedback from sales staff and customers as to the quality of goods. The overall reportrelies on input from stores to produce a reliable output report to Supplier Manager.

4.8.1. Data Flow Diagram - Manage Stock Movement

Level 1

Sales

Customer Order

1.0

Process Sale

D

1Inventory File

Item Data

Inventory Data

3.0

Report Supplier

Product Sales


volume

Data Dictionary

Customer Order - Customer selects item(s) to purchase

Item Data - At point of sale, information is collated from scanned price tag(product type e.g. t-shirt, colour, style, cost, sales margin,supplier)

Inventory Data - Number of item(s) available for sale

Supplier Volume - Number of stock moved by each Supplier


30/68


31/68



4.8.4. Flow Chart Manage Stock Movement

Start

Select Item

Display Item

Details

Update Inventory

End

Proceed to

purchase

Yes

No

Does Item match

display?


32/68



4.8.5. Use Case Report Stock Movement

Once historical data is collected in system, Supplier Manager can produce a report asrequired to monitor stock movement from Suppliers.

Supplier

Manager

Log In

Request Supplier

Good Movement

Report

Log Out

4.8.6. Extended Use Case

Report Stock Movement


1. This Use Case begins when SupplierManager requires Stock Movementreport.


3. Supplier Manager enters unique IDand password


5. Supplier Manager selects ReportStock Movement

6. Displays criteria options (date rangeand other filters14)

7. Supplier Manager selects criteria

8. Retrieves and totals stock sold (andreturned) by Supplier offering mode of

display

9. Supplier Manager selects preferreddisplay

10. Exports to selected display

11. Supplier Manager logs out

Alternative Courses for Report Stock Movement



10. Too much data to display on selected format (e.g. MS Excel spreadsheet, html or

14Range of options available by which to select data, e.g. date range, product type, State, Country


33/68



mobile device restriction)

4.8.7. Flow Chart - Report Stock Movement

Start

SelectReportStock

Movement

Display SelectionCriteria

Retrieve data

End

Select filtercriteria

Selectexport file

Export data

Is data file too bigfor selected

output

No

Proceed to ExportData

Yes


34/68



4.9. Repor t Bes t Supplier

The Supplier Manager monitors the success of a supplier based on the highest profitsgenerated by a Supplier. Other information may also be reviewed, such as both negativeand positive feedback from sales staff and customers as to the quality of goods. Theoverall report relies on the sales input from stores (in-store and online) to produce a

reliable output report to Supplier Manager.

4.9.1. Data Flow Diagram - Report Best Supplier

Level 1

Sales

Customer Order

1.0

Manage Sales

Revenue

D

1Sales File

Sales Data

Profit Margin

Supplier Manager

Supplier result

2.0

Report Best Supplier

Data Dictionary


Sales Data - Date and time of sale

- At point of sale, information is collated from scanned price tag(product type e.g. t-shirt, colour, style, cost, sales margin,supplier)

Profit Margin - From Sales Data, profit margin is determined by calculatingthe difference from cost price by Blue Fashion Cost to theSupplier and what the cost was on charged to the customer.

Supplier Result - Total profit generated from Supplier


35/68



4.9.2. Use Case Report Best Supplier

Once historical data is collected in system, Supplier Manager can produce a report asrequired to determine the Best Supplier.

Supplier

Manager

Log In

Request Best

Supplier Report

Log Out

4.9.3. Extended Use Case Report Best Supplier


1. This Use Case begins when SupplierManager requires Best Supplier report.




5. Supplier Manager selects Report BestSupplier

6. Displays criteria options (date rangeand other filters*)

7. Supplier Manager selects criteria

8. Retrieves and totals profit by Supplieroffering mode of display







10. Too much data to display on selected format (e.g. MS Excel spreadsheet, html ormobile device restriction)


36/68



4.9.4. Flow Chart - Report Best Supplier

Start

Select

Report Best

Supplier

Display Selection

Criteria

Retrieve data

End

Select filter

criteria

Selectexport file

Export data


output

No

Proceed to Export

Data

Yes


37/68



4.10. Repor t Trading Partner

The Supplier Manager monitors which Suppliers country offers better trading partners.The volume and profit from a Supplier reflects an understanding of the local knowledge inthe textile industry. The overall report relies on input from Manage Stock Movement salesto produce an output report based on the Suppliers country of origin to the Supplier

Manager.

4.10.1. Data Flow Diagram - Report Trade Partners

Level 1

Sales

Customer Order

1.0

Manage Stock

Movement

D

1Inventory File

Item Data

Inventory Data

2.0

Identify Supplier

Country


volume

D

2Supplier File

Supplier Information3.0

Report Best Trading

Partner

Country

of Origin

Data Dictionary


Item Data - At point of sale, information is collated from scanned price tag(product type e.g. t-shirt, colour, style, cost, sales margin,supplier)




Fashion stores and customers)Inventory Data - Number of item(s) available for sale


38/68



Country of Origin - Filter on Suppliers country

Supplier Volume - Number of stock moved by each Supplier

4.10.2. Use Case

Report Trading PartnerOnce historical data is collected in system, Supplier Manager can produce a report asrequired to identify the best trading partners.

SupplierManager

Log In

Request Best

Trading Partner

Report

Log Out

4.10.3. Extended Use Case Report Trading Partner


1. This Use Case begins when SupplierManager requires Best Trading report.




5. Supplier Manager selects ReportTrading Partner

6. Displays country criteria options (allcountry or selected country filters*)

7. Supplier Manager selects required

country criteria8. Retrieves total stock as percentage

and dollar value sold (and returned) bySupplier filtered on country and offersmode of display







39/68




6. Country of choice not displayed

10. Too much data to display on selected format (e.g. MS Excel spreadsheet, html ormobile device restriction)


40/68



4.10.4. Flow Chart - Report Trade Partners

Start

SelectReportStock

Movement

Display SelectionCriteria

Retrieve data

End

Select filtercriteria

Selectexport file

Export data


output

No

Proceed to ExportData

Yes


41/68



4.11. Onlin e Order System

The Online Order will allow customers the ability to purchase and order Blue Cut fashionsstock via the internet 24hours a day. This will broadened the companys customer baseand enable them to fulfill customer orders via existing store stock. Other information suchas number of online sales, success of online marketing campaigns can also be tracked.

4.11.1. Online Order System Data Flow Diagram

The Data Flow Diagram illustrates the External Entities who will interact with the Blue CutFashions Ordering System and what source of information they will be transmittingthrough the systemLevel 0

CustomerSales

1

OrderingDatabase

Stock Request

Sales Order Data

Stores

Manager

Sales Order request Order Data

Sales Order Data

Inventory Update


42/68



4.11.2. Data Flow DiagramOnline Order

Level 1

D1Customer

Identity File

Customer

Sales

1

Receive & show

Online Cataloguecontent

Stores

Customer Order

3

Authenticate &AuthoriseCustomer

2

Update InventoryFile

4

AuthenticateCustomer

Payment Method

6

Update OrderDistribution File

D2 Inventory F ile

D3Customer Details

File

D4Order Distribution

File

Customer Logs In

CustomerVerified

Order detailsVerify Payment

Method

Store fororder distribution

Verify CustomerDetails

Order details

Inventory Data

5

Update Order File

Inventory

Verify Customer7

ProduceManagement

Reports

Daily Inventory

D5Store distribution

File

Order confirmedOrderconfirmation

Manager

Daily distributionreport

Online Sales Report

Data Dictionary

Customer Order Customer order information

Inventory Data Number and type of Inventory requested

Customer Logs In Customer username & password information isentered in

Verify Customer Customers information is verified against informationstored in database

Customer Verified Customers information is verified as correct andallows customer to proceed

Verify Payment Method Customers payment method is verified againstexternal payment systems, i.e. paypal etc

Verify Customer Details All Customer information is passed through

Order details Customer Order information with shipping detailsOrder confirmed Completed customer order information

Store for order distribution Customer Order routed to correct store for distribution

Order confirmation Order distribution information

Order details Customer Order details

Daily distribution report Daily order distribution information

Online Sales Report Information on Customer Online Orders / Sale

Inventory Number and type of inventory processed

Daily Inventory Daily file of inventory requested for online sales


43/68



4.11.3. Use Case Online Order

CustomerCustomer

Search Catalogue

Select Item

Log In

Enter PaymentDetails

Receive OrderConfirmation

Log Out

4.11.4. Extended Use Case Online Order


1. Search Catalogue / Select Item(s)

2. Item(s) are added to the shopping cart

3. Select more items or finalise purchase

4. Prompt for registration/log in

5. Register / Log in

6. Prompt for payment details

7. Enter Payment information

8. Payment information presented

9. Edit / Accept Payment Information

10. Shipping information is presented

11. Edit / Accept Shipping Information

12. Order details are confirmed

13. Receive Order Details Confirmation

Alternative Courses Online Sales


44/68



1. Item out of stock

5. Log in invalid

11. Payment details invalid


45/68



4.11.5. Flow Chart Online Order

Start

Register/ Log

Validate

registration/

Log in

Details

Correct?

Select clothing

category

Return search

items

Validate/edit

order details

Present Catalogue(s)

Present order

details with cost

Add to Shopping

Cart

Buy more?

Verify payment/

shipping details

Validate/edit

shipping details

Present and send

order confirmation

Prompt user to

log out

End

Yes

No

Yes

No


46/68


47/68



4.12.3. Data Flow DiagramManage Inventory

Level 1

1.2

Order Inventory

Item Data

1.1

Check Inventory

Inventory Data Order Data

4.12.4. Data Flow DiagramFulfil Inventory

Level 1

Order Data

2.1

Receive Order

Request

2.2

Validate Order

Data

Item Data

2.3

Process Order

Request

Inventory Data Order Request

2.4

Goods Receipt

Order

Inventory Data

2.5

Upload Inventory

File

2.6

Distribute

Inventory

Item Data

Order Data

4.12.5. Use Case Check Inventory

Supplier

Administrator

Supplier

Administrator

Receive Order

Request

ValidateAvailability

Request

Authorisation

Log Out

Place Order with

Supplier


48/68



4.12.6. Extended Use Case - Check Inventory


1. Enter product Query

2. Results for the query is presented

3. Select item requested

4. Information about the item is presentedwith number of items in all stores

5. Request is sent to another store ifneeded

6. Request is sent to another store throughthe system

Alternative courses check inventory

5. Item is in store and sold

4.12.7. Use Case - Order Inventory

Shop

Assistant

Shop

Assistant

Log In

Search Catalogue

Locate item

Check Inventory

Order Inventory

Log Out


49/68



4.12.8. Extended Use Case Order Inventory


1. This use case starts when new products

are needed in the store 2. Request for user details and password

3. The shop assistant enters unique IDand password

4. Validates login and opens new windowto search the catalogue

5. Enter product query

6. Results for the query is presented

7. Select item wanted and check inventory

8. Item is added to an order template

9. Select more items or finalise order

10. Order is saved in an order databaseand sent to supplier administrator

11. The shop assistant logs out of thesystem


50/68



4.12.9. Flow Chart Order Inventory

Return Stock

items

Stock Inventory

displayed

Start

Quantity

available

instore?

Select Stock items

Prompt for

quantity of

stock

Fulfil Customer

Order

Check courier

database

Check other

stores

Prompt log out

Stock

available?Order stock

Request Courier

No

Yes

Search Stock

Inventory

End

Prompt for

quantity of

stock

Stock Request

sent to Head

Quarters

Update Stock

Inventory

Supplier receives

stock request

Update Stock

Inventory

Supplier fulfils

stock order

No

Yes


51/68



5. Soft Systems ModelA Soft Systems Model is a framework for collecting and interpreting information about theoverall system and the issues and constraints of the Human Activity System.

There are four stages in developing a Soft Systems Model;

Stage 1Unstructured Problem Situation. Identifies different views and stories thatthe various stakeholders hold about a particular problem

Stage 2Rich Picture. Presents a pictorial caricature of Blue Cut Fashionsoperations in an easy to understand format

Stage 3Root Definition, CATWOE, developed to express each stakeholdersviewpoint,CCustomers, AActors, TTransformation, WWeltanschauung (world-viewof the actors), OOwners, E - Environment

Stage 4Conceptual Modelling, builds an abstract alternative view of the presentsituation in the form of an ideal system and compare it to reality.

Blue Cut Fashions:

Overview:

Blue Cut Fashion is a clothing chain that has 3 stores located in Melbournes majorshopping centres. Specialising in blue cotton products predominantly but isexpanding its range of clothing that is popular among teenagers and young adults.

Sales Manager Jane Fry has identified 2 main components being an e-commerceweb site, which would allow online sales of our selected stock. The second, beingan e-business site, which would allow sharing of stock and supplier informationbetween our stores.

CEO, James Fry, agrees with the first; online sales system, and that the second e-

business site, should solving current problems is one issue that needs to beresolved as part of on-going business and I T development.

Presently, issues exist to a number of areas such as item returns, productavailability and pricing however a political issue in the organisation may existbetween James and Jane on what the future online system will do.

Stakeholders:

James Frost CEO of Blue Cut Fashions.

Jane Fry Sales Manager of Blue Cut Fashions.

Franca De Lorenzo Technical officer of Blue Cut Fashions.

Employees (sales staff) Customers: both in store and online browsing/purchasing.

Problem/Political Issue:Conflict or difference of ideas between Jane Fry and James Frost on what thefinished online system will do. (Documented below).

*********************************************************************Sales Manager, Jane Fry sees the new system having two main components, an e-commerce web site, allowing online sales of our selected stock and the second, being ane-business site, which would allow sharing of stock and supplier information between our

stores. However the CEO James Frost, agrees that there should be an online

e-commerce site and that is pivotal for future business planning and development. James


52/68



sees that solving current problems is one issue that needs to be resolved as part of on-going business and I T development.

Stages of SSM:

Stage 1: Unstructured problem situationFact finding Study

Hard (factual) data:

Blue Cut Fashions is under pressure following poor sales performances and jobcuts to staff.

There is no formal system linking the 3 stores inventory located in major Melbourneshopping centres.

A clear division between Jane (the sales manager & buyer) who feels that the newsystem will enhance current operations and James (the CEO) who feels that thenew system will resolve existing issues. (See transcript excerpt above).

The current systems and processes used in Blue Cut Fashions are inadequate ornon existent for returns management, inventory management, online purchasesand receipt handling.

Supplier information is currently held in Francas spreadsheet, James Blackberryand Janes PDA.

Soft data: (Assumptions and Opinions)There is a possibility that the issues identified are not shared equally by James and Jane.This is due to them both listing different issues to the otherthis indicative of varyingawareness to issues that exist in the organisation.

The conclusion that James is feeling pressure as the CEO of a dropping sales andrecently downsized clothing retailer is possible as he stated that I am responsible for theoperation of the entire chain of our stores, the finances, and the planning of its future. Inother words - the buck stops with me. This could explain why he is so adamant of the newsystem being the basis for the future success.

Consumers expect quality service when querying a prospective purchase with sales staff.Consumers also expect a safe online ordering system that is easy to use.

As the CEO, James has set targets to deliver high profits and tangible objectives such asmarket share. Intangible objectives include providing quality service and brandrecognition.

The sales staff is also expected to not fully embrace organisational change as generally,people prefer to stick to proven, tested and normal processes that they are familiar with.However, it is possible that they may feel embarrassed when they cannot adequatelyassist customers due to technological restraints and therefore may welcome a new system

that can alleviate this concern.


53/68



Franca De Lorenzo has stated that she believes the electronic supplier information isGrossly inadequate.

James Frost feels that the supplier information spreadsheet is a work of art contradictsFranca.

Stage 2

Analysis: Structuring a problem situation.Rich picture:

The above rich picture is made up of 4 different items.

Pictures represent a unique stakeholder for Blue Cut Fashions.

Thought clouds represent opinions, thoughts or ideas of that particular stakeholder.

Rectangular boxes connected to a stakeholder represent the role of the stakeholderin the Blue Cut Fashions operations system.

Speech bubbles describe the stakeholder in detaili.e. who they are specifically.

Stage 3: Root definition:CATWOE: James Frost CEO of Blue Cut Fashions

Customers:

Teens and Young adultsbetter in store operations and online sales capabilities.

Suppliersbetter information quality.

Blue Cut Fashion employeesbeneficiaries of better systems.Actors:

Franca De Lorenzotechnical officer, most likely to oversee operation andmaintenance.

Jane FrySales Managerlikely to oversee facets of the system.


54/68



Sales Staffthose who use the system in Blue Cut Fashion stores.Transformation:

System addresses existing IT and business issues and also provides a platform forfuture performance improvements.

Weltanschauung(world-views):

Online system will solve current problems whilst also allowing the online sales

section to be a pivotal aspect of our future planning and development.Owners:

Blue Cut Fashion Board of directors, Shareholders (if any), Owners.Environment:

Competitors, time needed before operational is scarce and technologicalconstraints.

CATWOE: Jane Fry Sales Manager of Blue Cut Fashions.Customers:



Blue Cut Fashion employeesbeneficiaries of better systems.Actors:

Franca De Lorenzotechnical officer, most likely to oversee operation andmaintenance.

Jane Fry (Herself)Sales Managerlikely to oversee facets of the system.

Sales Staffthose who use the system in Blue Cut Fashion stores.Transformation:

Customer needs clothing information (online) such as product availability. Systemturns queries into processed orders.

Blue Cut Fashion Staff take a customer director query in store and find an accurate

answer via the system, they also place order requests.Weltanschauung(world-views):

2 components, e-commerce website for online sales; e-business site to allowsharing of stock and supplier info between stores. Current set up is poor.

Owners:

Blue Cut Fashion Board of directors, James Frost (CEO) Shareholders (if any),Owners (if applicable)

Environment:Competitors, time needed before operational is scarce and technological constraints

CATWOE:Franca De Lorenzo Technical officer of Blue Cut Fashions.Customers:



Blue Cut Fashion employees (Board/James Frost/Jane Fry/Sales staff)beneficiaries of a better system as can make more informed decisions.

Actors:

Franca De Lorenzo (Herself)technical officer, most likely to oversee operationand maintenance.

Jane FrySales Managerlikely to oversee facets of the system and report to

James Frost. Sales Staffthose who use the system in Blue Cut Fashion stores.

Transformation:


55/68



Will receive large numbers of input data relating to sales, customer details,suppliers, stock and process it into a meaningful output that satisfies technologicalrequirements and improves Blue Cut Fashion performance.

Weltanschauung(world-views):

New system is grossly needed; current system is by far inadequate. Myspreadsheet is not effective enough to deal with current issues.

Better communication technology links between James, Jane and myself.Owners:

Blue Cut Fashion Board of directors, James Frost (CEO) Shareholders (if any),Owners (if applicable)

Environment:Competitors, time needed before operational is scarce and technological constraints

Root Definitions (Current system):

The Blue Cut Fashions stock and supplier information system is owned by the Board

of Blue Cut Fashions and operated by Franca De Lorenzo and the Blue Cut Fashionstaff. It adequately handles stock and supplier information while providing basicintegration to devices owned by key stakeholders such as Jane Fry and James Frost.The system is perhaps insufficient to meet the current and future needs as it isrestricted by technological capabilities of the system, the cost (time and money) andthe culture of the business.

Root definitions (future system):

The Blue Cut Fashions stock management, supplier information and online ordersystem owned by the Board of Blue Cut Fashions, operated by Jane Fry, Franca DeLorenzo and Blue Cut Fashion sales staff provides a system that deals with customerqueries, customer orders and employee requests for information in an efficient andprofessional manner. The system is safe and secure, easy to use and provides a basisfor future development while addressing existing issues. It is perhaps restricted by thelack of unity between some key stakeholders,time and money constraints.


56/68



Stage 4: Conceptual models.

CEO


57/68



Sales Manager


58/68



Combined


59/68



6. Requirements

6.1. Funct ion al Requirements

A functional requirement defines a function of a software system its component. A functionis described as a set of inputs, the behavior, outputs and defines what the system is meantto accomplish.

6.1.1. Online Sales - External

Easy to select items for purchase to add to shopping cart Simple payment processmultiple payment options, paypal, credit card Order confirmation number displayed Option to sign up to newsletters Username and Password login

6.1.2. Online Sales Internal

Displays catalogue of inventory

Online registration system for customers Storage of customer information Customer Identity and Authorisation methodusername / password Order workflow capability, ability to route to store which has available stock Order history information Allow different payment methodspaypal, credit cardsvisa, mastercard,

American express, Diners Verify credit card details to allow purchase of order Update stock inventory in real-time to display potential delays in order

fulfillment Marketing capabilitywebsite display of specials

Ability to retrieve all customer email addresses for marketing campaigns Capability for links to other websites

6.1.3. Store Sales Internal

Flexible price tagging systemto allow for easy updates Ability to scan & display price of item in store Cash register sales updates inventory system in real-time Sales docket to contain information on item purchase, description of item,

size, style,colour, price, total of goods, item reference number Access to inventory systemto see stock availability in other stores

Ability to code faulty goods in the inventory system for return to supplier Ability to code returned goods in the inventory system to update stock that

item is available

6.1.4. Stock - Internal

Real time inventory. The system should automatically be updated when anorder is completed and when a sale is made either that be online or in store.

Details about every item are stored in a database. The details shouldinclude; name, barcode, price inn, price out, description, size and number ofitems in every store.

The inventory database should be accessed by all Blue Cut stores and

possible to access when not in store. IT staff at head quarter will enter stock information into the database. Orders to suppliers are sent to head quarter


60/68



If an item out of stock is available in another store a request can be made totransfer the item.

6.1.5. Supplier - External

Correct Supplier stock codes on Purchase Orders

Forward upcoming promotions and other communications via one emailaddress ([email protected])

Notification of stock being returned and when, by what courier Fast, reliable and efficient delivery of goods

6.1.6. Supplier Internal

Display catalogue of active Suppliers Daily upload of Inventory Request received from Blue Cut Fashion Stores

and online customers Online capability for authorised personnel to approve and release Supplier

purchase orders Automated notification if a given supplier has had no order activity within

months Online registration system for new suppliers Storage of supplier information Supplier order history information Real time stock availability View supplier upcoming promotions and events Ability to retrieve all supplier email addresses for marketing campaigns Capability for links to supplier websites Ability to display cost price and margin per item, per store of items currently

in stock Access to all store inventory systems to identify stock availability in all stores Ability to report details of faulty goods against supplier records Track stock movement between Customer, Supplier and all Blue Cut

Fashion stores Preloaded Courier forms to ensure all relevant specifications are complete Remote access to Blue Cut Fashion when working out of office Choice of report format (spreadsheet, html, csv, pdf)
mailto:[email protected]:[email protected]


61/68



6.2. Non Funct io nal Requirements

Non Functional Requirements (NFRs) are defined as a requirement that specifies criteriathat can be used to judge the operation of a system, rather than specific behaviours.Typically, Non-Functional Requirements can be called quality of the system, what are thequality goals of the system, for example updates in real-time or batch updates overnight,

how many concurrent users will the system allow at the same time, what type of securitycontrols are in place.

The following NonFunctional Requirements apply to the whole Blue Cut Fashionsystem, with specific non-functional requirements per sub-system stipulated.

Usability internal Training times:

Store staff1-2 hours on new system Office staff2-3 hours on new system, including how to update

inventory etc IT staff1-2 days on the technical aspects of the system, how load

new information, file types, regular maintenance on the system,upgrade potential on the system, architectural diagram on how thesystem interacts and flows between the different sub-systems.

Measurable task times: typical order customer online order should take no more than 3-5mins

with logging in, authentication, authorisation, verification of payment typical in store customer transaction response time on inventory file to

cash register should take no more than 1 minute. Comparing usability with other state-art-systems Online help systems should be available to customers, easy to navigation

and understand Frequently Asked Questions, Interactive help textwhenmouse hovers over text, online wizards, tool tips Follows consistent standards throughout the whole system, that is the

consistent use of terminology, formats, etc

Usability external - website Use of mock-up wire frames for website design Easy navigation Complies with minimum W3C standardsfor disability usability standards Use of Dublin Core standards for metadata User Friendly error messages

Reliability Availabilityonline system should be available 24/7, internal system should

be available 23/7, allowing hour per day for back-ups Accuracydescribes how close the measurement is to real value while

precision is the units which is used to measure the data in. Bugs per typethere are four different severity levels of system bugs and

production problems, they are defined as follows: Severity 1 - Production server or other mission critical system(s) are

down and no workaround is immediately available.

All or a substantial portion of mission critical data is at asignificant risk of loss or corruption.

There is a substantial loss of service.


62/68



Business operations have been severely disrupted. Severity 1 support requires you to have dedicated resources

available to work on the issue on an ongoing basis during yourcontractual hours

There is no workaround to the disruption

Severity 2 - Major functionality is severely impaired.

Operations can continue in a restricted fashion, although long-term productivity might be adversely affected.

A major milestone is at risk. Ongoing and incrementalinstallations are affected.

A temporary workaround is available. There is no workaround to the disruption

Severity 3 - Partial, non-critical loss of functionality of the software. Impaired operations of some components, but allows the user

to continue using the software. Initial installation milestones are at minimal risk There is a workaround available.

Severity 4General usage questions.

Cosmetic issues, including errors in the documentation.

Mean time between failures / repair timethe response time betweensystem failures will depend upon the type of support agreement in place withvendor, the below table is typical response times

Severity Production

Critical / Severity 1 4 business hours, 24 x 7

Major / Severity 2 8 business hours

Minor / Severity 3 12 business hours

Cosmetic / Severity 4 24 business hours

Priority Definition

Priority 1immediate Blocks further testing Currently visible and / or detrimental to customers Possible immediate detrimental to revenue or

reputation Needed for time critical deadline

Priority 2High Fixed before next release Numerous customer complaints about the issue Critical area of the system Will be very visible and / or detrimental when

released (Dev) Does not conform to what was stated as a

requirement for the release

Priority 3Medium Should be fixed if time permits, not a critical area

of the system Some Customers impacted by it but there is a

workaround


63/68



Very few customer complaints logged about theissue

Priority 4 - Low Would like to be fixed but can be released as it iscosmetic

Few customers even notice it or are impacted byit

Performance Response timesexternal website to comply with standards of no more than

10-20 second page load times Throughputability to hand multiple transactions via online orderings and

stores Capacityability to handled 1000 concurrent users external users via online

website during peak times and 400 concurrent internal users during peaktimes

Degradation modesdegradation of service should only occur oncecapacity thresholds have been reached

Supportability Ability to be able to upgrade system requirements Ability to fix system issues

Security Secure online ordering system Secure online customer registration process Secure online payment method Secure access to the internal systemsinventory, reporting Secure remote access to internal systemsvia PDA, Blackberry, Computer

Reporting System

Reporting capability Online salesnumber, revenue, items Store Salesnumber, revenue, items Number of orders fulfilled Turnaround time on order fulfillment

Number of faulty items Inventory of stock levels

per stock number, product, by store stock number, supplier information, product/stock category,

style, sizes, colour, cost price and purchase price Supplier informationdetails, unique supplier ID, Number of returns due to Suppliers providing wrong stock items Accountsoutstanding, paid Customer Demographic information


64/68



6.2.1. Design Constraints

There are a number of design constraints in the overall system. There is a need to ensurethat the system complies with the standards for useability from both an internal andexternal perspective. External useability needs to comply with the minimum W3Cstandards to ensure that people with disabilities can still use the online ordering system,otherwise Blue Cut Fashions could missing out on a potential customer base.

The system also needs to scalable and have appropriate systems support in place duringtesting and once it is deployed into production.

6.2.2. Cloud Computing

Cloud Computing has been heralded as the next big thing in the IT space. CloudComputing according to Daugherty et el, is also known by other names, such as on-demand computing, elastic computing, utility computing, grid computing, everything-as-a-service and software-as-a-service. To understand how a company can use cloudcomputing, we need to understand what cloud computing is which is basically the dynamicprovisioning of IT capabilities like hardware, software or services from third partycompanies over a network into a companys organisation.

Cloud Computing companies offer a number of services, that fall into different categories,Customer Relationship Management (CRM), human capital, financial management,procurement, content management, word processing applications, spreadsheets, e-mailand web conferencing. Companies can also subscribe to cloud based solutions forbusiness processes which can be managed for the company externally like claims

processes, expense management, or procurement.

To use the services offered by these companies, companies subscribe by the number ofusers or seats. Depending on the number of user or seats will depend on the cost to thecompany.

Some of the companies who are involved the Cloud Computing phenomenon, offeringservices are;Amazons Infrastructure Cloud, Google Apps Engine, IBM Blue Cloud,Microsoft Windows Azure and Salesforce Force.com.

Blue Cut Fashions could for instance outsource its procurement with suppliers for their

fashion business to one of these companies and let them handle the process, without theneed to integrate their systems, or Blue Cut could outsource its returns or claimsprocesses.


65/68



7. Bibliography

Daugherty, P, Swaminathan. K.S., Tobolsko, J, What the Enterprise Needs to Know about

Cloud Computing,SMS Management and TechnologyWeb and InformationManagement Capability Group, 2009.

Geelan, J, The Future of Cloud Computing, SOA World Magazine, Jan 2009

8. Appendix

8.1. Pro ject Plan
https://magellan.smsmt.com/Topics/ServiceOfferings/Web%20and%20Information%20Management/Pages/default.aspxhttps://magellan.smsmt.com/Topics/ServiceOfferings/Web%20and%20Information%20Management/Pages/default.aspxhttp://in.sys-con.com/node/771947http://in.sys-con.com/node/771947https://magellan.smsmt.com/Topics/ServiceOfferings/Web%20and%20Information%20Management/Pages/default.aspxhttps://magellan.smsmt.com/Topics/ServiceOfferings/Web%20and%20Information%20Management/Pages/default.aspx


66/68



8.2. Experi ence Report

8.2.1. Activities Log

Group Member StudentNumber

Activities Performed

Sharon Lea Culhane S3163667 Project Plan

Formal Systems Model

FlowchartStock

DFDSales

Data DictionarySales

Functional RequirementsSales

Non-FunctionalRequirements

Draft Report

Final ReportIvette Dionne S3104495 Supplier Overview

Use CaseSupplier

FlowchartSupplier

DFDs Supplier

Data DictionarySupplier

Functional Requirements

Presentation Design

Presenter

Ida Marie Gaarder

Johansen

S3225651 Use CaseSales

Use CaseStock DFDStock

Data DictionaryStock

Functional Requireme

Documents

Blue Cut Fashions Software Requirements Specification