compusell entry screen program hamilton setende 207063303 compusell order entry program project...

7/27/2019 Compusell Entry Screen program Hamilton Setende 207063303 CompuSell Order Entry Program Project document…

http://slidepdf.com/reader/full/compusell-entry-screen-program-hamilton-setende-207063303-compusell-order-entry 1/18

Compusell Entry Screen program Hamilton Setende 207063303

CompuSell Order Entry Program

Project documentation

For

Business Analysis 3.2

30 November 2010

Prepared

for

Prepared

byHamilton Francisco de Fatima Setende

207063303





TABLE OF CONTENTS

Page #

1.0 Overview

1.1 Company profile……………………………………………………... 3

1.2 Mission..........................……………………………………………………. 3

1.3 Organizational structure........................…………………………….. 3

1.4 Problem statement ……………………………………………………….... 4

1.5 Pieces framework.....…………………………………...........…........ 5

1.5.1 Performance............................................................................ 5

1.5.2 Information.......................................................................................... 5

1.5.3 Economics........................................................................................... 61.5.4 Control(and Security)......................................................................... 6

1.5.5 Efficiency............................................................................................ 7

1.5.6 Service................................................................................................. 7

2.0 Business Rules2.1

2.2 Data dictionary………………..………………………………………….. 8

2.3 ERD......................…………………………………………………… 9

2.4 Normalization.................................…………………………………. 9

2.5 Data flow diagram...…………………………………………………….. 10

3.0 Project overview

3.1 Project overview…………………..........................................………….. 11

3.2 project deliverables……............……………………………………. 11

3.3 Evolution of the CompuSell Order Entry program….….………….. 12

4.0 Project Organization.

4.1Process Model....................................................................................... 12

5.0 Technical Process

5.1 Tools.................................................................................................. 13

5.2 Software documentation................................................................... 13

6.0 Resource Requirements6.1 Resource Requirements............................................................................. 14

7.0 References





Overview

Of

1.1 Company Profile

CompuSell is a relative small, but rapidly expanding Computer Company, it specializes, in

supply of computers, computer equipment, components and software, to a variety of customers’

country wide.

1.2. Mission

CompuSell, aims to be you one stop, computer store, the place were, anyone, who requires, a

computer, accessories, and expert assistance can come, and find whatever they require, good quality

products at an affordable price.

1.3. Organizational Structure

CompuSells structure is that of a Line structure, this is the kind of structure that has a very specific line

of command. The approvals and orders in this kind of structure come from top to bottom in a line.

Hence the name line structure. This kind of structure is suitable for smaller organizations. This is the sort

of structure that allows for easy decision making, and also very informal in nature. They have fewer

departments, which makes the entire organization a very decentralized one.





1.4 Problem Statement and System analysis

In recent times, CompuSell's business activities have been expanding, and the need arouse to, make

changes in its infrastructure, and modernize its, operation in order to keep up with, the growing

demand, for its products.

One of the fields where CompuSell, needed urgent change, was its, ordering system.

CompuSell, although, a computer company on top, of the latest, technological advances, still, had a

backward system, and if they wanted to continue being a successful business in the 21st century, they

needed urgent change.

Compusell still, kept a lot of it’s, customer order records, on a manual file system, which, cause a lot of,

problems, when it came to record keeping, and also, cause a lot of workload for, the people responsible





of managing the system, since they had to manually, look for the records, through a pile of paper files,

and although the records were sorted by alphabetical order, it was still unorganized, and caused a lot of

problems, for the company and its customers.

1.5 Pieces Frame Work

1.5.1 Performance

A) Throughput

Allot, of effort and hard work is required from the employees, in order to manage the current.

B) Response time

The current system, has a very slow response time, and in many cases, slows down, the business,

activities, because, it takes, along of time, for the employees, to search, though, the files, to find, a

specific, customer record.

1.5.2 Information

a) Output

Information Overload

Information is not in standard format

Information Difficult to produce

Information is not timely to its subsequent use

b) Inputs





Data is not accurately captured, it contains errors.

Data is not captured in time to be useful.

Too much data is captured.

Same data is captured more than once.

C) Stored Data

Data is stored redundantly in multiple files.

Data is no secure from accident or vandalism.

Data is not well organized.

1.5.3 Economics

a) Costs

Costs are untraceable.

B) Profit

New Markets cannot be explored.

Current marketing can be improved, once new system is in place.

1.5.4 Control (and Security)

A) Too little control or security

input data is not adequately edited

anyone can have access to the data

Crimes, such as fraud can be committed against the data.

b) Too much control or Security

Red rape and too much security can slow down the system.

Controls can inconvenience customers or employees.

Excessive control cause processing delays.





1.5.5 Efficiency

a) People, machines or computers

Data is redundantly input or copied

Staff members waste a lot of effort to access data and that reduces productivity.

Information is redundantly generated

Effort required for tasks is excessive

1.5.6 Service

The system produces inaccurate results

The system produces inconsistent results

The system produces unreliable results





2.0 Business Rules

2.1 Business Rules

a) A customer can place one or many orders.

b) An Order can be placed by one customer only.

c) An order can have one or many products.

2.2 Data Dictionary

Entity Alternative Acronym

Customer Client C

Order Purchase O

Order line None I

Product Inventory O





2.3 ERD

2.4 Normalization

1) CUSTOMER(CustNo, First Name, Last Name, Address, City,

State, Phone#)

2) ORDER(OrderNo, OrderDate, AmtPaid, OrderTotal, CustNo)

3) PRODUCT(ProdNo, Desc, Weight)

4) ORDERLINE(CustNo, ProdNo, QtyOrdered)





2.5 Data flow diagram

customer infoCustomer File

Customer verification Customer data

Product Order detailsProduct list

Process

Payment

Invoice

Print Order Customer Order

Customer





3.0 Project Overview

3.1 Project Overview

After careful, analysis, of the problems faced by Compusell, and their needs,

I have undertaken to provide the Compusell with an Order entry screen system that delivers a

scalable, secure, and reliable tracking and reporting of all orders made by the company’s customers,

and record keeping of all compusell business transactions.

It has also been decided, that the project will, be based on an IBM I AS400, being that it is probably,

the most advanced and secure system, in the market right now, and its programming language,

RPG, is by far the best business programming language out there.

3.2 Project Deliverables

The project deliverables of the project and the delivery dates are as follows:

Project Deliverables

Item Delivery Date Delivery Location QTY

CompuSell Order Entry

screen System11/30/2010 Vaal University 1

User Documentation 11/30/2010 Vaal University 1

CompuSell Order Entry Screen will be a Software, program, run on an IBM I server .It will





Include all programs and files that will be needed to install and run the Order Entry Screen

System.

The User Documentation is an overview of the features and capabilities of the CompuSell Order

Entry Screen. This will be in the form of a soft copy or file delivered to representative of

CompuSell.

3.3 Evolution of the Compusell Order Entry program.

The typical evolution of software would include plans for future versions and upgrades of the

software.

As of the present, the current evolution for the CompuSell Order Entry Screen is to research,

plan and develop the program. The current evolution for the CompuSell Order Entry Screen

only accounts for its development through implementation and deployment. The CompuSell

Order Entry Screen as of right now is planning for the analysis, design, development, coding,

testing, and implementation of the CompuSell Order Entry Screen for CompuSell.

Future evolution of the CompuSell Order Entry Screen in terms of upgrades can still be

evaluated and implemented at a later date if the need arises.





4. PROJECT ORGANIZATION

4.1 Process Model

The main milestones identified in the project are:

Project Initiation Date: 15/12/2010

The project was initiated on November 15, 2010 . At that time, an overview of the project time

line and project requirements was covered.

The project initiation task is mainly identifying the specific system that will be developed for the

CompuSell Order Entry Screen.

Testing: 22/12/2010

Testing of the Order Entry Screen System, began on November 22 2010, and due to end on the

29 of November 2010.

Presentation: 30/12/2010

Presentation of both the completed CompuSell Order Entry Screen and all applicable documents

pertaining to the project has been set for Tuesday, November 30, 2010. All parties involved in





the CompuSell Order Entry Screen project including the client, and the project team will be in

attendance.

Implementation:

Implementation of the CompuSell Order Entry Screen involves the process of

successfully installing the software into the IBM I Server and get it running on the date of

the presentation.

Project Termination Date:

The project termination activities would be the successful presentation of the CompuSell

Order Entry Screen and successful implementation CompuSell Order Entry Screen.





5. TECHNICAL PROCESS

5.1 Tools

For the tools utilized in the development process, please reference Section 5.2, the

Resource Requirements portion of this document.

5.2 Software Documentation

The following is a list of the documents that are required and developed

1. Program Documentation: Outlines the project analysis process, what problems exist,

and the solution, to the problem.

2. Software User’s Documentation: This document identifies the features and

capabilities of the CompuSell Order Entry Program. It also contains user specific

information. Document that contains the user manual and all information that

prospective users would find useful in regards to their use of the CompuSell Order Entry

Screen program.





6. Resource Requirements

6.1 Resource Requirements

The hardware resources identified to be required on this project include:

Computer/workstation/notebook :

The software resources required for the project are:

Microsoft Office: Documents associated with this project are created as Word documents. Also,

diagrams, etc can be created using Visio.

Open Office: Open Office is a free software application suite developed by Sun Microsystems.

Open Office has the capability of opening and changing Microsoft Office documents. Since

Microsoft Office requires a license to use it can be used as an alternative to Microsoft Office in

working with project documents.

RPGIV: Report programming generator, an High-level programming procedural language, that

provides, a quick solution to a common business task: generating reports needed within the

business.

i5/OS: Is an operating system used on IBM power systems( a unified server platform from the

former IBM system I and IBM system p servers) formerly known as Os/400, As/400.





7.0 References

1. Jeffrey A.hoffer , Mary B. Prescott,Heikki Topi. 9th

Edition Modern Database management:

2. Meyers, B. & Buck, J. 4th Ed. Programming in RPG IV.

3. Bentley, D. & Whitten, L. 8th Ed. System Analysis & Design.