Development Of Customer Order Processing Systems Computer Science Essay

Published:

Designer Belts Ltd is a leather belt manufacturer which has evolved from the old Boot and Shoe Industry. The management of the Designer Belts Ltd wants to change their manual orders system to the Customer Order Processing System because of the potential for high quality leather belts in the booming consumer market. Currently the customer orders are kept in FB/1 order forms which are uniquely numbered manually. The customer order information has the design number, the belt color, the length belt, the style of the belt and the quantity for each belt ordered. Sales staff needs to confirm the order to meet the required date. And then, final payment demand letter is sent to the customer.

Frequently, the customers do complain because the mistakes are made. Designer Belts Ltd want the Customer Order Processing system to ensure that customer orders are processed efficiently and accurately, also to log customer complaints with information about department and to produce a daily complaints report for each department because customer complaint may be dealt with by more than one department.

2 Requirement Catalogue

2.1 Functional Requirements

Lady using a tablet
Lady using a tablet

Professional

Essay Writers

Lady Using Tablet

Get your grade
or your money back

using our Essay Writing Service!

Essay Writing Service

Source: Ms X

Sign Off: Ms X

Requirement Id: R001

Functional Requirement:

Request new customer account

Non-Functional Requirement(s)

Description:

Target Value:

Acceptable Range:

Comments:

Volume

600 per day

550-650 per day

No Non-Functional Requirements identified at this stage

Source: Ms X

Sign Off: Ms X

Requirement Id: R002

Functional Requirement:

Connect to the main system

Non-Functional Requirement(s)

Description:

Target Value:

Acceptable Range:

Comments:

No Non-Functional Requirements identified at this stage

Source: Ms X

Sign Off: Ms X

Requirement Id: R003

Functional Requirement:

Have a security system at LogOn

Non-Functional Requirement(s)

Description:

Target Value:

Acceptable Range:

Comments:

No Non-Functional Requirements identified at this stage

Source: Ms X

Sign Off: Ms X

Requirement Id: R004

Functional Requirement:

Input customer details

Non-Functional Requirement(s)

Description:

Target Value:

Acceptable Range:

Comments:

Volume

600 per day

550-650 per day

No Non-Functional Requirements identified at this stage

Source: Ms X

Sign Off: Ms X

Requirement Id: R005

Functional Requirement:

Set up customer account

Non-Functional Requirement(s)

Description:

Target Value:

Acceptable Range:

Comments:

Volume

Print Time

600 per day

10 seconds

550-650 per day

8-10 seconds

Account must be printed on the relevant company headed form

Source: Ms X

Sign Off: Ms X

Requirement Id: R006

Functional Requirement:

Update customer details

Non-Functional Requirement(s)

Description:

Target Value:

Acceptable Range:

Comments:

Volume

50 per day

20-50 per day

No Non-Functional Requirements identified at this stage

Source: Ms X

Sign Off: Ms X

Requirement Id: R007

Functional Requirement:

Input Sales Person Details

Non-Functional Requirement(s)

Description:

Target Value:

Acceptable Range:

Comments:

Volume

600 per day

550-650 per day

No Non Functional Requirements identified at this stage.

Source: Ms X

Sign Off: Ms X

Requirement Id: R008

Functional Requirement:

Input Product Details

Non-Functional Requirement(s)

Description:

Target Value:

Acceptable Range:

Comments:

Volume

600 per day

550-650 per day

No Non Functional Requirements identified at this stage.

Source: Ms X

Sign Off: Ms X

Requirement Id: R009

Functional Requirement:

Input Order Information

Non-Functional Requirement(s)

Description:

Target Value:

Acceptable Range:

Comments:

Volume

Not known

Not known

Order Information volume is not identified because the customer can order several different items in the same order

Source: Ms X

Sign Off: Ms X

Requirement Id: R010

Functional Requirement:

Print Out Order Information

Non-Functional Requirement(s)

Description:

Target Value:

Acceptable Range:

Lady using a tablet
Lady using a tablet

Comprehensive

Writing Services

Lady Using Tablet

Plagiarism-free
Always on Time

Marked to Standard

Order Now

Comments:

Volume

Print Time

Not known

10 seconds

Not known

8-10 seconds

Order Information must be printed on the relevant company headed form

Source: Ms X

Sign Off: Ms X

Requirement Id: R011

Functional Requirement:

Input Invoice Information

Non-Functional Requirement(s)

Description:

Target Value:

Acceptable Range:

Comments:

Volume

Not known

Not known

Invoice information volume is not identified because it depend on the customer

Source: Ms X

Sign Off: Ms X

Requirement Id: R012

Functional Requirement:

Print Out Invoice Information

Non-Functional Requirement(s)

Description:

Target Value:

Acceptable Range:

Comments:

Volume

Print Time

Not known

10 seconds

Not known

8-10 seconds

Invoice Information must be printed on the relevant company headed form

Source: Ms X

Sign Off: Ms X

Requirement Id: R013

Functional Requirement:

Print Out Final Demand Letter

Non-Functional Requirement(s)

Description:

Target Value:

Acceptable Range:

Comments:

Volume

Print Time

35 per day

10 seconds

25-35 per day

8-10 seconds

Final demand letter Information must be printed on the relevant company headed form

Source: Ms X

Sign Off: Ms X

Requirement Id: R014

Functional Requirement:

Print out a list of all customers that made a purchase in a particular month

Non-Functional Requirement(s)

Description:

Target Value:

Acceptable Range:

Comments:

Volume

Print Time

Not known

10 seconds

Not known

8-10 seconds

Purchased customer details must be printed on the relevant company headed form

2.2 Non-Functional Requirements

Source: Ms X

Sign Off: Ms X

Requirement Id: R001

Non Functional Requirement:

The new system should have the following levels of access:

Report only

Update only

Complete System Access

Update and delete

All data should be encrypted

3 Categories of prototype to be developed

Prototypes can be used as an information gathering tool, a communication device and an alternative to system development life cycle. It is necessary in seeking user reactions, suggestions, innovations and revision plans. If users see prototype similar to actual system and get to use it, they know what they want and what they don’t. So, building a prototype is very useful to system development life cycle. Anything from a paper-based storyboard to complex software and from a cardboard mockup to a molded or pressed piece of metal can be a prototype. Prototypes are useful to answer questions and support designers in choosing between alternatives. In general, there are two kinds of prototypes. They are low-fidelity prototyping(one that does not look very much like the final product but they support the exploring of alternative designs and ideas because they are simple, cheap, and quick to modify) and high-fidelity prototyping(one that looks very much like the final product and uses the exact materials as the final product to support testing out technical issues.). Low-fidelity prototypes are important in early stages of development and don’t integrated into the final product. High-fidelity prototypes are used to sell ideas to people because they very much like the final product and have the complete functionality.

Prototypes usually involve compromises. It is intended to test an aspect of the product. Tow common compromises that often must be traded against each other are horizontal prototyping (providing a wide range of functions but with little detail) and vertical prototyping(providing a lot of detail for only a few functions). There are two different prototype development approaches. They are evolutionary prototyping(one that evolve a prototype into the final product) and throwaway prototyping(one that uses the prototypes as stepping stones towards the final design). In our case, software development, we can categorize the prototype into four categories. They are patched-up prototype, nonoperational scale model, first-of-a-series and selected features prototype that contains some of the essential features. Patched-up prototype is a working model with all the basic features but storage and retrieval of data is inefficient and users can interact with the system. Non-operational scale model is one that is not operational, except for input and output features to be tested. First-of-a-series prototype is an operation model to be installed, tested and modified as necessary in one location, and later implemented in other locations. Selected features prototype is an operational model and built in modules with the acceptance of the some features, later essential features are added and these are part of the actual system.

Lady using a tablet
Lady using a tablet

This Essay is

a Student's Work

Lady Using Tablet

This essay has been submitted by a student. This is not an example of the work written by our professional essay writers.

Examples of our work

Advantages of the prototype model

Enable good communication between user and developer

Requirement changes can be made at early stage

Possibility of developing a system that closely addresses user needs and expectations because of feedbacks from users

Reducing development time, system testing, debugging and modification because user is kept close to the project all the time

Disadvantages of the prototype model

Lack of standard procedures

Use of prototype as a production system

Incomplete prototype may be regarded as complete system

Prototyping can lead to the wrong problem being focused on

Neglects integration and architecture issues

De-motivates people not involved in development

Problems in estimation and resource planning

The four categories of prototypes as recommended by DSDM are:

Business prototypes(focus on business processes being automated)

Usability prototypes(focus on user interface usability, accessibility)

Performance and capacity prototypes(focus on how system will perform under the peak loads)

Capability/ technique prototypes(focus on design approach or concept)

Developing Customer Order Processing System(COPS) for Designer Belts Ltd, we can use throwaway approach and evolutionary approach for prototype development. I choose evolutionary approach because we are developing software and it is best to evolve the prototype into the final product in software developing.

The categories of prototypes to be developed for Customer Order Processing System of Designer Belts Ltd

Request new customer account

Input customer details

Create Customer account

Connect to the main system

Have a security system at LogOn

Input Sales Person Details

Input Product Details

Update customer details

Input Order Information

Print Out Order Information

Input Invoice Information

Print Out Invoice Information

Print Out Final Demand Letter

Print out a list of all customers that made a purchase in a particular month

3.1 The classes of users to be involved in development

Customer

Sales Staff

System Administrators

Project Managers

Finance Managers

Management of Designer Belts Ltd

Project Sponsor

4 Class Diagram for Customer Order Processing System

5 Use Case Diagram for Customer Order Processing System

6 Conclusion

Designer Belts Ltd wanted their manual order processing system into a computerized system(Customer Order Processing System) because to compete with other companies in the booming consumer market, the company need to satisfy customer with better service such as lowering order time, no late delivery service, etc. Currently, the manual system used by Designer Belts Ltd has many disadvantages for the modern competing market. They are

The same data can be repeated because tracking sales record is hard for the employee.

The sales record is stored in files and files cabinet can be accessed by anyone. If information goes into the wrong hands, it can be used against company and customer.

The sales information is written by hand and it can lead to accidentally switched data with other sales.

Needs many employees to record the manual information.

The sales information record can be misplaced during manual filing and cannot be available for future use.

If the sales record need to update, there will be a lot of information to enter again and the employees can forget to enter some information and can forget that they already enter it and might redo it. So, it will consume a lot of time.

There will be too much paper work because the order information, customer information, the sales information and everything is recorded in paper.

A lot of space will be needed for storing sales records because the sales record files will be increased as time goes by.

Retrieving of data can be slow because the sales information is stored in manual files and hard to search information about customer. As a result, the delivery will be late and it leads to customer unsatisfying and bad impression on company.

After changing manual order processing system into a computerized system, Designer Belts Ltd has many benefits to satisfy customers and compete with other companies. Computerized system is faster than manual system in storing, recording, searching and updating data. It can also provide better customer services, better billing and easier administration to persuade customer. It is worth to use computerized system although development cost can be higher than manual system. But investment in computerized system can return within a year. The advantages of computerized system are

Tracking sales records will be easy for employees because the sales information is stored in computer and can search it easily and effectively.

The computerized system has a security logon system for employees and the sales information cannot be accessed by wrong person.

There cannot be accidentally switched data with other sales since it is recorded by computer.

The sales information can be available for future use because computerized system can organize files effectively.

If there are any changes to be made on sales information, the employees can enter information easily with the help of computerized system.

There will be less space for storing sales record and less paper work.

The sales information can be accessed quickly in case of delivery and the delivery cannot be late for misinformation.