Title : Grapevine Vineyard Winery New Enterprise System

Author : Judy Hallal-Murray

Student # :000455658

Course : COMP 1429 System Modelling

Course Centre : School of Business and Computer Science

Date : 9th April 2008

Note: Smart Draw 7 was used instead of Oracle 11g because in my attempt in installing oracle 10g or
11g on my Vista machine, I've noticed that Windows keeps reporting that nmefwmi.exe keeps stopping
and pops up less than a minute. My system eventually crash, thus resulting to using Smart Draw 7
 Grapevine Vineyard Winery New Enterprise System
__________________________________________________________________________________________________________________________________________________________________________________________________________________________________________
___________________________________________________________________________________________________________________________________________________ _______________________________________________________________________________________

Table of content
TABLE OF CONTENT ............................................................................................................................................... 2

TABLE OF FIGURE ...........................................................................................................................................................2

1.0 INDUCTION ...................................................................................................................................................... 4

2.0 THE RATIONALE OF THE DESIGN....................................................................................................................... 5

2.1 SYSTEM REQUIREMENTS ............................................................................................................................................7

3.0 THE METHODOLOGY, THE PROBLEMS ENCOUNTERED AND METHODS USED TO SOLVE THESE PROBLEMS .... 10

3.1 RAPID APPLICATION DEVELOPMENT (RAD) .................................................................................................................10

3.1.1 Requirements Planning ..............................................................................................................................10
3.1.2 User Design ................................................................................................................................................11
3.1.3 Construction ...............................................................................................................................................11
3.1.4 Implementation..........................................................................................................................................12
3.2 THE PROBLEMS ENCOUNTERED .................................................................................................................................13
3.3 THE RAD SOLUTION ...............................................................................................................................................13

4.0 THE SMART DRAW DESIGNER CASE TOOL 7 ................................................................................................... 15

4.1 THE PROCESS MODEL OF THE SYSTEM:.........................................................................................................................15

4.2 A FUNCTIONAL MODEL OF THE SYSTEM SHOWING ALL FUNCTIONS AND THE SUB FUNCTIONS. .................................................18
4.3 A DATA MODEL FOR THE PROPOSED SYSTEM WHICH RESULTS FROM FUNCTIONAL MODEL. .....................................................21
4.4 A FUNCTION ENTITY MATRIX FOR AT LEAST 4 PROCESSES .................................................................................................24
4.5 A STATE TRANSITION DIAGRAM FOR ENTITIES WITH INTERESTING BEHAVIOUR ......................................................................26
4.6 A SCREENSHOT OF ANY FORMS OR REPORTS THAT YOU HAVE DESIGN. ................................................................................27

5.0 CONCLUSION.................................................................................................................................................. 29

6.0 APPENDICES ................................................................................................................................................... 30

7.0 REFERENCES: .................................................................................................................................................. 32

Table of Figure
Figure 1 : illustrates the stages of the RAD ....................................................................................................................6
Figure 2 : illustrates Grapevine Vineyard and winery New Enterprise System .............................................................8
Figure 3: Functional Decomposition of New Enterprise Information System for GVW ..................................................9
Figure 4: identify the function, processes and data entities of GVW ..........................................................................13
Figure 5 : Content Diagram ..........................................................................................................................................15
Figure 6: Level 0 Data flow Diagram ............................................................................................................................16
Figure 7: Level 1 Data Flow diagram ............................................................................................................................17
Figure 8: Object tree ....................................................................................................................................................18
Figure 9: illustrates the Class Diagram.........................................................................................................................19
Figure 10: illustrates the Communication Diagram – Database and order Creation ...................................................20
Figure 11: Activity diagram ..........................................................................................................................................21

2
 Grapevine Vineyard Winery New Enterprise System
__________________________________________________________________________________________________________________________________________________________________________________________________________________________________________
___________________________________________________________________________________________________________________________________________________ _______________________________________________________________________________________

Figure 12: illustrates the Use Case Diagram ................................................................................................................22

Figure 13: (Illustrates the sequence of tracking the customer product through shipment) .......................................23
Figure 14: Illustrates the functional matrix for four Departments ..............................................................................24
Figure 15: illustrates the entity relation diagram ........................................................................................................25
Figure 16: illustrates the State of a customer who is tracking the order online .........................................................26
Figure 17: illustrates the form that a customer would see when querying a delivery ................................................27
Figure 18: illustrates the reports view of a delivery query ..........................................................................................28

3
 Grapevine Vineyard Winery New Enterprise System
__________________________________________________________________________________________________________________________________________________________________________________________________________________________________________
___________________________________________________________________________________________________________________________________________________ _______________________________________________________________________________________

1.0 Induction

Grapevine Vineyard Winery (GVW) focuses on selling wines and cultivating grapevines. Grapevine
Vineyard Winery focuses heavenly on customer’s interface and experience. They would like to offer
their customers a tracking shipment order and supportive communication through e-mail on the sales
and products. They would like to enhance their customers experience by introducing a New Enterprise
system. They currently use an Oracle DBMS and development tools. This report attempt to evaluate the
Rapid Application Development as a methodology use for developing a quick application on a small scale
bases. Criteria such as quickly, accuracy and reliability were used to select the methodology.

One of the primary objectives of the Rapid Application Development methodology was to take
advantage of the latest technology available to speed development.

It were recommended that Grapevine Vineyard Winery (UK) is a unique organisation and should
consider special Business objectives will need to be well defined before the project can begin, so
projects that use RAD should not have a broad or poorly defined scope. Furthermore, in order to keep
the project within a short time frame, decisions must be able to be made quickly, so it imperative that
there be very few client decision makers, preferably only one, and they must be clearly identified up
front. Client decision makers need to understand and agree to a RAD approach and ideally should be
willing to accept a product that is less full featured and/or be willing to accept higher development cost
(due to the emphasis on purchasing reusable components over building them) in exchange for increases
in speed.

4
 Grapevine Vineyard Winery New Enterprise System
__________________________________________________________________________________________________________________________________________________________________________________________________________________________________________
___________________________________________________________________________________________________________________________________________________ _______________________________________________________________________________________

2.0 The rationale of the design

The International Sales Director has requested the New Enterprise system should be an integrated
system that would manage the Sales Administration and Shipment of orders to customers. The New
Enterprise System should have workflow from Production to Sales to Account to Warehouse and to
shipment departments. Tracking the status of shipment order and communication with customers
through email on sales and products. View information on sales by product and customer. The New
enterprise system should be compatible with the existing Oracle DBMS

Hence the New Enterprise system should include the following:

1. Some elements of Transaction Processing Systems (TPS) that would have

a. Automate handling of data about business activities (transactions).
b. Process orientation for the Sales and Shipment department.
2. Management Information Systems (MIS)
a. Converts raw data from transaction processing system into meaningful form.
b. Data orientation from the Production Department.
3. Decision Support Systems (DSS)
a. Designed to help decision makers like the IT Manage and the International Sales
Director;
b. Provides interactive environment for decision making;
c. Involves data warehouses, executive information systems (EIS);
d. Database, model base, user dialogue.

The Phases in the new Enterprise System Development Life Cycle are:

a. Planning (identify, analyze, prioritize and arrange IS needs.);

b. Analysis (Study and structure system requirements);

c. Design (convert recommended solution to system specification. Logical design:

functional features described independently of computer platform. Physical design:
logical specifications transformed to technology- specific details);

d. Implementation (code, test, install and support the information system);

e. Maintenance (systematically repairs and improves the information system).

5
 Grapevine Vineyard Winery New Enterprise System
__________________________________________________________________________________________________________________________________________________________________________________________________________________________________________
___________________________________________________________________________________________________________________________________________________ _______________________________________________________________________________________

Rapid Application Development is not appropriate for all projects. The methodology works best for
projects where the scope is small or work can be broken down into manageable chunks. Along these
lines project teams must also be small, preferably two to six people, and the team must have experience
with all technologies that are to be used. Rapid Application development (RAD) Methodology should be
used by Grapevine Vineyard and Winery (GVW). This methodology should have time period for twenty
days and included the following

1. This methodology decrease design and implementation time and

2. Involves: prototyping, Joint Application Design(JAD), CASE tools, and code generators

The stages of the RAD are

Requirement
Planning

User Design
Construction
(Analysis)

Implementation

Figure 1 : illustrates the stages of the RAD

A key aspect of RAD is the construction of a prototype for the purpose of jumpstarting design and
flushing out user requirements. The objective is to build a feature light version of the finished product in
as short an amount of time as possible, preferably days. The initial prototype serves as a proof of
concept for the client, but more importantly serves as a talking point and tool for refining requirements.

Developing prototypes quickly is accomplished with Computer Aided Software Engineering CASE tools
that focus on capturing requirements, converting them to a data model, converting the data model to a
database, and generating code all in one tool.

Iterative development (JAD) means creating increasingly functional versions of a system in short
development cycles. Each version is reviewed with the GVW to produce requirements that feed the next
version. The process is repeated until all functionality has been developed. Each development cycle

6
 Grapevine Vineyard Winery New Enterprise System
__________________________________________________________________________________________________________________________________________________________________________________________________________________________________________
___________________________________________________________________________________________________________________________________________________ _______________________________________________________________________________________

provides the user an opportunity to provide feedback, refine requirements, and view progress (in focus
group session meetings).

Some good criteria for selecting a code generator include:

 Supports existing technologies, architectures, and best practices

 Produces enterprise level code (i.e. n-tier code)
 Generates prototype applications without having to write a line of code (do not accept a code
generator that does not at least attempt to generate a presentation layer code)
 Uses templates or a technology that allows complete control over outputted code
 Provides a flexible meta-data mechanism
 Can be used throughout the entire development process, and specifically will not overwrite your
code

It is importance to manage the project. Project management may be the most important aspect of
systems development. Effective project management helps ensure (Meeting customer expectations,
Satisfying budget and time constraints).

2.1 System Requirements

1. A new enterprise-wide information system using their newly acquired Oracle DBMS and
development tools.
2. Applications to meet them quickly, accurately and reliably.
3. A small rapid application development project that can be accomplished in about 20
days.

4. Sales and Shipping have to interact with Production when an order is received.
5. The sales information has also to be sent to Accounts Receivable.
6. The International Sales Director has requested an integrated system that will manage
the sales administration and shipment of orders to customers and will keep him
informed on – stock levels, current outstanding orders and how much money people
owe.
7. The system should organise the flow and storage of sales related information, especially
when it relates to shipping orders.
8. It should also support communicating with customers about sales and products.
9. It should allow for the status of a shipping order to be tracked and for an invoice to be
produced for a customer for a shipping order.
10. The management would also like to view information on sales by product and by customer.

7
 Grapevine Vineyard Winery New Enterprise System
__________________________________________________________________________________________________________________________________________________________________________________________________________________________________________
___________________________________________________________________________________________________________________________________________________ _______________________________________________________________________________________

Production Department Sales Department Shipment Department Accounting Department

Special Retail Special Retail Special Retail Special Retail

Customers Customers Customers Customers Customers Customers Customers Customers

Ordering and Tracking and

Inventory System Filing System Payment System
Status System

Master Order ,
Master Master Master
Stock and
Inventory File Tracking File Payment File
Customer File

Output Information:
 Type of Customers, Output information:
Output Information:
Output :   Type of Special Customer (Distributors,
Name of Customer,  Type of customer,
 Type of Wines and  Restaurants, Off License ), and Retail
Delivery address,  Name of customer,
grape Cultivation Customer
 Billing Address,  Delivery Address
Production  Method of Payment :Special customers
 Payment Plan,  Status of Order
Allowable payment terms and Retail
 Quantity of Wines
customers paid advance.

Grapevine Vineyard and Winery New Enterprise system

3/31/2008 All computer application system must be

Figure 2
intergated
Figure 2 : illustrates Grapevine Vineyard and winery New Enterprise System

8
 Grapevine Vineyard Winery New Enterprise System
__________________________________________________________________________________________________________________________________________________________________________________________________________________________________________
___________________________________________________________________________________________________________________________________________________ _______________________________________________________________________________________

Grapevine Vineyard and Winery Organizational Business Functions

Business
Planning

Sale Forecast Market Analysis

Development
Production

Fine Wines
Inventory analysis Stock taking Raw material
finishing
Sales and
Marketing

Marketing
Order Fullfillment Distribution Stock level
Research
Accounting and
Finance

Special Customers Retail Customers

Accounts
Accounts Payable (Allowable (Payment in
Receivable
payment terms) advance)
Warehouse /
Shipment

Order Status Order Tracking Delivery

Resources

Recruitment Training
Human

Figure 3: Functional Decomposition of New Enterprise Information System for GVW

9
 Grapevine Vineyard Winery New Enterprise System
__________________________________________________________________________________________________________________________________________________________________________________________________________________________________________
___________________________________________________________________________________________________________________________________________________ _______________________________________________________________________________________

3.0 The methodology, the problems encountered and methods used to

solve these problems

3.1 Rapid Application Development (RAD)

Rapid Application Development (RAD) is a software development methodology that focuses on building
applications in a very short amount of time. It is an Application Development technique that uses
Prototypes, Iterative Customization (JAD), and CASE Tools.

As the name suggests, Rapid Application Development's primary advantage lies in an application's
increased development speed and decreased time to delivery. The goal of delivering applications quickly
is addressed through the use of Computer Aided Software Engineering or CASE tools, which focus on
converting requirements to code as quickly as possible, as well as Time Boxing, in which features are
pushed out to future releases in order to complete a feature light version quickly.

Increased quality is a primary focus of the Rapid Application Development methodology. RAD quality in
development has both the degree to which an application conforms to specifications and a lack of
defects once the application is delivered. According to RAD, quality is defined as both the degree to
which a delivered application meets the needs of users as well as the degree to which a delivered
system has low maintenance costs. Rapid Application Development attempts to deliver on quality
through the heavy involving of users in the analysis and particularly the design stages.

3.1.1 Requirements Planning

Refer to Figure 1

The Requirements Planning stage (also known as the Concept Definition Stage) consists of meetings
between requirements planning team and key GVW users. Meetings focus on both developing a high
level list of initial requirements as well as setting the project scope. The requirements planning team
identifies primary business functions and initially breaks them down into business entities (such as
Production, Sales, Account, Shipment). The Requirements Planning stage should result in a list of entities
as well as DFDs and action diagrams that define the interactions between processes and data elements
and should take between one and four weeks. Ideally requirements should be captured in a structured
tool. At the end of the Requirements Planning stage project estimation should be considered.

10
 Grapevine Vineyard Winery New Enterprise System
__________________________________________________________________________________________________________________________________________________________________________________________________________________________________________
___________________________________________________________________________________________________________________________________________________ _______________________________________________________________________________________

3.1.2 User Design

During the User Design stage (also known as the Functional Design Stage) the analysis team meets with
end users in Joint Application Development (JAD) Workshops. During the workshops the analysis team
flushes out the requirements in more detail, develops the entities developed in the Requirements
Planning into a data model (Entity Relationship Diagram), formalizes business rules, develops test plans,
and creates screen flows and layouts for essential parts of the system. During the latter half of the User
Design stage the development team (also known as the SWAT or Skilled Workers with Advanced Tools
team) aids the analysis team in activities such as creating a working data model that can be converted to
a functional database, and in identifying reusable components (such as Oracle DBMS). As mentioned in
the Requirements Planning stage, all requirements should be captured in a tool.

Before moving to the Construction Stage the analysis team should focus on next steps by flushing out
the project plan and focusing on effort estimates. Focusing on next steps is an important element of the
User Design phase, because the initial iteration of the Construction Phase should focus on a feature light
prototype. In order to keep development iterations as short as possible, and to gain the maximum
benefit of RAD's agile nature, core requirements should be identified and targeted for the initial
prototype, and secondary requirements should be identified and targeted for future development
iterations. Beyond a vertical limiting of scope, such as removing entities or use cases from the initial
scope, a horizontal type limiting of scope should be considered as well, such as not developing field
validation, not developing file upload/download capabilities, or focusing on just the strengths of the
particular CASE tool being used without manually adding much developer customization.

The User Design stage should last between three and five weeks.

3.1.3 Construction

During the Construction Phase the Design Team develops the application in iterative cycles of
development, testing, requirements refining, and development again, until the application is complete.
Development iterations should last between one day and three weeks. The development team should
convert the Data Model that was developed during the User Design Stage into a functional database (all
data modelling tools have this ability). The CASE tool used (which may be the same as the data modeller
or a separate tool) should now generate large sections of the application, at a minimum data access
code, but preferably business functions and user interface as well.

11
 Grapevine Vineyard Winery New Enterprise System
__________________________________________________________________________________________________________________________________________________________________________________________________________________________________________
___________________________________________________________________________________________________________________________________________________ _______________________________________________________________________________________

It is vital to keep each development iteration on track, and functionality may need to be dropped to
keep development within the time box. GVW management plays a vital part in ensuring everything is
progressing according to schedule, keeping the Special and Retail customer in the loop regarding
changes in the functionality, and keeping the team motivated.

Once the prototype has been developed (within its time box), the construction team tests the initial
prototype using test scripts developed during the User Design stage, the design team reviews the
application, the customer reviews the application and finally the construction team, design team, and
customer meet in Focus Group meetings in order to determine the requirements for the next iteration.
Focus group meetings consist of facilitated sessions that last about two hours. The facilitator should
know ahead of time the areas that require discussion and should ensure that each issue receives enough
attention, keeping a list of issues that require additional attention in a separate meeting as appropriate.

After the meeting (additional meetings may be necessary), the development team and design team
should update the requirements, data model, test scripts, and project plan as during the User Design
stage. Again the teams should identify core and secondary requirements, plan out the next development
iteration, keep the user in the loop regarding what will be done, and then start the next iteration of
development over again. As the New Enterprise system approaches a sufficient state the development
team should focus on the system as a finished application rather than a prototype.

During the final iterations of development the design team should update user documentation, perform
User Acceptance Testing and define the steps necessary for deployment/implementation.

3.1.4 Implementation

The Implementation Stage (also known as the Deployment Stage) consists of integrating the new system
into the business. The Development Team prepares data and implements interfaces to other systems.
The Design Team trains the New Enterprise system users while the users perform acceptance testing
and are trained by the Design Team. The Design Team helps the users transfer from their old procedures
to new ones that involve the New Enterprise system; trouble shoots after the deployment, and identifies
and tracks potential enhancements. The amount of time required to complete the Implementation
Stage varies with the project.

12
 Grapevine Vineyard Winery New Enterprise System
__________________________________________________________________________________________________________________________________________________________________________________________________________________________________________
___________________________________________________________________________________________________________________________________________________ _______________________________________________________________________________________

Functions Data Entries Information Systems

 Business Planning,  Special Customers,  Accounts Management:
 Product Development,  Retail Customers, Accounts payable and
 Sales and Marketing,  Raw material, Accounts receivable,
 Production and  Order,  Inventory Management
operations,  Invoice  Shipment (Tracking
 Accounting and and status )
Finance, Management,
 Shipment,  Sales and Marketing
 Human Resource. Management
Figure 4: identify the function, processes and data entities of GVW

3.2 The Problems encountered

Processes development methodology, often resulted in the development of applications that did not
meet client needs because applications did not have a clear understanding of the users requirements.
Thus, for projects implemented on a phase base, the stages is not aligned with each other and
frequently resulted in complete, but unusable, systems. The cause of the problems and be identified in
the strict adherence to completion of one lifecycle stage before moving on to the next lifecycle stage.
Specifically, building an application based on requirements that have been frozen at a point in time
means that the longer development takes, the more likely that GVW needs will change and invalidate
the requirements that the New Enterprise System being developed is based upon.

RAD may produce applications that are less full featured than traditionally developed applications. This
concern should be addressed as soon as possible through clear communication with the GVW users as
to what will be delivered and when.

Because RAD focuses on development of a prototype that is iteratively developed into a full system, the
delivered solution may lack the scalability of a solution that was designed as a full application from the
start.

3.3 The RAD Solution

There have been many responses to this problem from the 1980's through today. In 1986 Barry Boehm
wrote A Spiral Model of Software Development and Enhancement, which initially defined the concepts
of prototyping and iterative development and had a focus on risk reduction. During the late 1980's Scott
Shultz and James Martin refined the ideas of prototyping and iterative development into a methodology
called Rapid Iterative Production Prototyping (RIPP) that focused on developing systems in a short

13
 Grapevine Vineyard Winery New Enterprise System
__________________________________________________________________________________________________________________________________________________________________________________________________________________________________________
___________________________________________________________________________________________________________________________________________________ _______________________________________________________________________________________

timeframe with small teams of highly qualified, motivated, and experienced staff. James Martin (who
was nominated for a Pulitzer Prize and is frequently called "the Guru of the Information Age") further
expanded and formalized Rapid Iterative Production Prototyping. Other solutions have arisen out of the
need for adaptable development techniques, most notably the agile methodologies developed during
early 2000's, the most popular of which is Extreme Programming. Extreme programming is a somewhat
controversial methodology that deemphasizes formalized requirements gathering and instead puts a
heavy focus on developing programming code in short development cycles with constant feedback from
the user.

At Automated Architecture our Just-In-Time Application Generation methodology provides the benefits
of Rapid Application Development while minimizing many of the disadvantages, such as reduced
scalability, through the generation of an enterprise level "prototype" that provides as a starting point a
scalable, efficient, and well designed application.

14
 Grapevine Vineyard Winery New Enterprise System
__________________________________________________________________________________________________________________________________________________________________________________________________________________________________________
___________________________________________________________________________________________________________________________________________________ _______________________________________________________________________________________

4.0 The Smart draw designer case tool 7

4.1 The process model of the system:

1. Context data flow diagram (DFD)

Figure 5 : Content Diagram

Content Diagram
For Grapevine 4/20/2008 Figure 5
Vineyard Winery

0 Sale Data
Special Customer
Production
Order Inventory Data

Invoice

Invoice Wine Order Sales

Retail Customer Customer Order New Enterprise IS

ordering System Delivery
Inventory Data Warehouse / Shipment

Customer Data Accounts

Account balance

Management Reports

International
Sales Director

The content diagram in figure 5 illustrates the New Enterprise Ordering System where a
customer can view the wine catalogue and choose a wine product

2. DFDs of current physical and logical system :Enables analysts to understand current system

15
 Grapevine Vineyard Winery New Enterprise System
__________________________________________________________________________________________________________________________________________________________________________________________________________________________________________
___________________________________________________________________________________________________________________________________________________ _______________________________________________________________________________________

Figure 6: Level 0 Data flow Diagram

DFD Level 0
For Grapevine 4/20/2008 Figure 6
Vineyard winery

Special 1.0 Production

Customer order Inventory Data
customer
Invoice
Receive and Sales and
Customer order Wine Order
Retail Transform Marketing
Invoice
customer customer
Wine Orders

2.0 3.0 4.0

Update
Update Wine Update
customer
Sold file Inventory File
Order File

Formatted Wine Sold data Formatted Inventory Data Formatted customer Order data

D3. Customer Order

D1. Wine Sold file D2. Inventory File File

Daily Inventory Amount

Daily Wine sold amount 5.0 Daily customer order amount

Sales and Warehouse

Inventory Reports Integrated Inventory Reports
Marketing and Shipment
management Order reports
Reports

Management Reports

International
Accounts
Sales Director

The Data flow diagram illustrated in figure 6 a more comprehensive look at the New Enterprise
System, showing the processes of how the system works. A customer makes any order; the sales
representative query the system stock level; the sales rep place the order once the query is
satisfied.

16
 Grapevine Vineyard Winery New Enterprise System
__________________________________________________________________________________________________________________________________________________________________________________________________________________________________________
___________________________________________________________________________________________________________________________________________________ _______________________________________________________________________________________

3. DFDs of new logical system :

DFD Level 1
For Grapevine 4/21/2008 Figure 7
Vineyard Winery

Daily Inventory depletion amount

5.1

Access Wine sold,

Daily wine sold amount Daily customer order amount
inventory data and
customer order
data

Wine sold Data Customer order Data

Inventory Data

5.2

Summary wine sold, Inventory and

customer order data

5.3 5.4 5.5

Prepare Prepare Prepare
Inventory and customer order inventory
sales report Report report

Inventory and sales report Customer order report Inventory report

Figure 7: Level 1 Data Flow diagram

The DFD level 1 Diagram illustrates the final stage of the ordering process. The New Enterprise
System would produce several reports. Some of the reports would integrate the sales of product
and to whom that product was sold to. Other report would be on the inventory of the most
frequent wine sold.

17
 Grapevine Vineyard Winery New Enterprise System
__________________________________________________________________________________________________________________________________________________________________________________________________________________________________________
___________________________________________________________________________________________________________________________________________________ _______________________________________________________________________________________

4.2 A functional model of the system showing all functions and the sub
functions.
Company : GVW Company

d1: Dept d2 : Dept d3 : Dept d4 : Dept

name = "Production" name = "Warehouse/ name = "Accounts"

name = "Sales" shipment"

c1 : Customer o1 : Order p1 : Product

customer ID = '01' OrderID = '001' ProductID = '0001' sp1 : ShipPerson p3 : Person
CustomerType = 'Special' OderDescription = ProductDescription = name = "Bob" FirstName = "Bob"
'Wine' 'Wine' CustomerType = CustomerType =
FirstName = 'Bob'
CustometID = '01' StockID = '00001' "Special" "Special"
e-mail = 'bob@yahoo.com' OrderID = "V001"
Quantity = '200' Quantity = '40000' OrderDescription =
ProductID = "001" "Wine"
Payment = "$"
s1 : Inventory : Contact Info
StockID = '00001' Address: : Contact Info
StockLevel = Phone: Address:
'4000000' e-mail: Phone:
StockDescription = e-mail:
'Wine'
Anonymou
Attribute type =
s Object
'Value'

Object Diagram - GVW Company Ordering Tree

Figure 8: Object tree

The functional object Diagram in figure 8 illustrated four main departments (Sale, Production,
Warehouse / shipment and Accounts. Each department is required to input data in the New Enterprise
System. For instance the sales Department is required to input data that is related to the customer and
their order while Production is required to input data about wine and inventory. Accounts and
Warehouse / shipment would pull the necessary data that is relevant to their department.

18
 Grapevine Vineyard Winery New Enterprise System
__________________________________________________________________________________________________________________________________________________________________________________________________________________________________________
___________________________________________________________________________________________________________________________________________________ _______________________________________________________________________________________

Sales Representitive

Initiates
DOMAIN MODEL FOR
Sales Representitive command
GVW
Initiates
NEW ENTERPRISE
ORDERING
SYSTEM
(class diagram)
Add Customer

Track status of Serach for

Advanced
order customer

Add Order

<<Captured On>>
Library Command

New Enterprise Ordering

LogOn GVW web site Retail of special
System
customer

<<Captured On>> Customer Database Wine Inventory Database

Wine Database

Search by type of Search by age of Track status of

wine wine Delivery
Initiates

Customer Data Stock Data

progress of
delivery

Secure customer command

Secure customer

Figure 9: illustrates the Class Diagram

Figure 9 illustrates the Class Diagram of the New Enterprise System. The customer can log in to view the
order and track the process of that order delivery.

19
 Grapevine Vineyard Winery New Enterprise System
__________________________________________________________________________________________________________________________________________________________________________________________________________________________________________
___________________________________________________________________________________________________________________________________________________ _______________________________________________________________________________________

UML Communication Diagram - Database & Order Creation

create() create(fileOrder);
dB : CustomerDataBase inFile : Buffered Order
RefreshDB();

3: new OrderRec(currentString);
4: [while inDeliveryStatus, readLine!= null]: 1: create(DeliveryStatusDBFile);
new OrderRec(currentString)
5*: read(inFile);

cr:CustomerRec CustomerRec fileDeliveryStatus:FileDe liveryStatus

create() create(fileSotck);
dB : InventoryDataBase inFile : Buffered Stock
RefreshDB();

3: new BookRec(currentString);
4: [while inStock, readLine!= null]: 1: create(InventoryDBFile);
new InventoryRec(currentString)
5*: read(inFile);

cr:CustomerRec CustomerRec fileStock :FileStock

Figure 10: illustrates the Communication Diagram – Database and order Creation

The communication and collaboration diagram feature in figure 10 illustrates that there are a customer
database and inventory database. The customer dataset hold all information pertaining to a customer
and inventory database hold information pertaining to wine stock. Once a customer is created and
order wine , these two databases would be updated according.

20
 Grapevine Vineyard Winery New Enterprise System
__________________________________________________________________________________________________________________________________________________________________________________________________________________________________________
___________________________________________________________________________________________________________________________________________________ _______________________________________________________________________________________

4.3 A data model for the proposed system which results from functional
model.
UML Activity Diagram: Special / retail customer order processing
Customer Sales Accounts shipment Production

Place order
Send Inventory
Take order
Informtion

Give credit Take credit

card number info Process order

Process Credit
Pack in box
Card info

Add in
shipping log

track order

Deliver to
carrier

Record Notify
shipping Accounting

Receive Send shipping

order notification

Figure 11: Activity diagram

The data model activity diagram show how data flow from the customer placing an order and going
throughout the system to the point of delivery. Once the customer receives the package the account
department would be notified. The data can be record form the point of sale to the point of delivery.
The customer has the option to track their order as it goes from warehouse to their delivery address.

21
 Grapevine Vineyard Winery New Enterprise System
__________________________________________________________________________________________________________________________________________________________________________________________________________________________________________
___________________________________________________________________________________________________________________________________________________ _______________________________________________________________________________________

Order wine
products

Retail Customer

<<
Sales Representitive

inc
lud
e>>
Monitor
Stock level
Bill
Production Inventory clerk
customer <<
ex
ten
<<u ds
<<actor>> >>
ses>
> Name

Track the
Delivery of <<include>> order/ product
order
Warehouse/ Shipment Clerk

Pay in
advance
Accountant

AUse Case Diagram for s retail customer orderingsytem

(for special customer no payment in advance is required however a credit of 1000 ponud is extended)

Figure 12: illustrates the Use Case Diagram

The customer initiated the process, however the customer is outside the boundary. The major players
are the Customer, the Sales Representative, Production Inventory Clerk and Warehouse / shipment
clerk. The method of payment depends on the type of Customer. There are two type of customer the
Retail customer and the Special customer. The retail customer pays in advance while the Special
Customer is extended a line of credit of £1,000. The Special Customer is restaurant owners, wholesalers
and distributors.

22
 Grapevine Vineyard Winery New Enterprise System
__________________________________________________________________________________________________________________________________________________________________________________________________________________________________________
___________________________________________________________________________________________________________________________________________________ _______________________________________________________________________________________

Warehouse /
Sales Production Shipment Accounts
Customer

[Order wine ]
ordering process
[Do it have wine in stock]
Inventory Process

Stock
[If paid deliver product] Le ve l
Shipment process

Track
[Paid in full or Credit] De live ry
Method of Payment

paid in
advance
[Paid in full]
Account Settle
Exte nd
line of
[Credit T erms outstanding] cre dit
Credit Payments

Track
[did not receive product] orde r
message name

Track
de live ry
[Receive product]
Status of Delivery

validate
[payment outstanding for Retail customer] orde r
message name

Q ue ry
[If not paid query]
payment Query
place a
hold on
[Settle outstanding payment] de live ry
Release product

Re le ase
[status of delivery] orde r
T rack order

De live r
[Stock T aking]
Product
Inventory

Inve ntory

Figure 13: (Illustrates the sequence of tracking the customer product through shipment)

The sequence diagram shows when a customer has a query with undelivered package. The customer can
login with a tracking number to query the status of the undelivered package. Shipment and Accounts
would be notified amount the package which never reach its’ final destination.

23
 Grapevine Vineyard Winery New Enterprise System
__________________________________________________________________________________________________________________________________________________________________________________________________________________________________________
___________________________________________________________________________________________________________________________________________________ _______________________________________________________________________________________

4.4 A function entity matrix for at least 4 processes

er

er
m

m
to

to
us

us

y
lC

or
lC

ce
nt
ia

us
r
e
i

de

i
ec

ta

vo
ve
in

at
Re
Sp

Or
W

St
In

In
Sales and Marketing
Ma rketi ng Res ea rch × ×
Order ful l fi l ment × × × × ×
Di s tri buti on ×
Production
Producti on Level × ×
Inventory of Stock × ×
Warehouse and Shipment
Inventory of Stock × ×
Open Del i very × ×
Regi s ter Del i very ×
Tra ck Del i very ×
Cl os ed Del i very × ×
Accounts
Credi t × ×
Pa yment i n a dva nce × ×
Acounts Reci evi a bl e × ×
Accounts Pa ya bl e × ×

Figure 14: Illustrates the functional matrix for four Departments

(Sale, Production, Warehouse / shipment and Accounts)

Each Department have their processes involve fulfilling an order from a customer. The whole objectives
is to get the Wine product from Production to the warehouse, administrative transparency for payment
in advance involve Accounts and to the customer in the shortest time period. X represents the flow of
information as the transactions occur.

24
 Grapevine Vineyard Winery New Enterprise System
__________________________________________________________________________________________________________________________________________________________________________________________________________________________________________
___________________________________________________________________________________________________________________________________________________ _______________________________________________________________________________________

GVW ORDERING SYSTEM (Entity Relationship Diagram)

Track

Name /
Custome rID #

Customer has Custome r account

Ord
er
Cre dit Card
custome r
Name

Sales and
Marketing

inventory

ProductID
has
Product
Stock Le ve l

Sent to

Product Billing se nt to
quantity Accounts Warehouse /
Shipment

Me thods of Addre ss
Name
payme nt
Name
status
number

Figure 15: illustrates the entity relation diagram

25
 Grapevine Vineyard Winery New Enterprise System
__________________________________________________________________________________________________________________________________________________________________________________________________________________________________________
___________________________________________________________________________________________________________________________________________________ _______________________________________________________________________________________

4.5 A state transition diagram for entities with interesting behaviour

Browse
customer browse
Web site

Internet access

Searching Denying
Unknown
search wine catalog
Cancel database for a product Incorrect value

Deny access
Wine Found Not Found

Verifying
Repeat up to
Log in using Track
three times
Number
do/ask for Tracking
number

Track Number Found

Prompting Searching

enter customer name for status on

and delivery address delivery

Verifying Prompting
do/verify tracking the do/prompt for another
status of delivery track of delivery
availability

Idle
waiting for next
activation

Figure 16: illustrates the State of a customer who is tracking the order online

The customer is required to enter their tracking number. Upon entering their tracking number the
Enterprise System user for their name and Delivery address, then and only the system can track the
status of the order. If the customer fails to enter the correct tracking number the system will prompt
them to the login for three times. After the third attempt the customer did not enter the correct
tracking number the system would deny the customer access to even the basic pages

26
 Grapevine Vineyard Winery New Enterprise System
__________________________________________________________________________________________________________________________________________________________________________________________________________________________________________
___________________________________________________________________________________________________________________________________________________ _______________________________________________________________________________________

4.6 A screenshot of any forms or reports that you have design.

Figure 17: illustrates the form that a customer would see when querying a delivery

The design tool use is visual studio 2005. The form runs in the web browser, once a customer know his/
her tracking number the below form will appear on screen, requesting them to enter their Name
delivery address, track number and delivery date. The current status field will generate the status of the
delivery. The next two field can be used a response to the query.

27
 Grapevine Vineyard Winery New Enterprise System
__________________________________________________________________________________________________________________________________________________________________________________________________________________________________________
___________________________________________________________________________________________________________________________________________________ _______________________________________________________________________________________

Figure 18: illustrates the reports view of a delivery query

28
 Grapevine Vineyard Winery New Enterprise System
__________________________________________________________________________________________________________________________________________________________________________________________________________________________________________
___________________________________________________________________________________________________________________________________________________ _______________________________________________________________________________________

5.0 Conclusion
The New Enterprise System provides many new opportunities for Grapevine Vineyard and Winery
(GVW) business in terms of cost savings, wider markets with no geographical boundaries and a
competitive advantage. GVW can use the New Enterprise System as a marketing tool, an information
channel or an e-commerce to integrate their entire business. The New Enterprise System has major
influences on the industry structure in terms of increased competition, reduced barriers to entry and a
shift of bargaining power towards consumers. By incorporating elements such as the ability to order/
quotes of different types of wines and wine by-product online model, it will be possible for GVW to
analyse the development of the wine industry in terms of utilising the opportunities provided by the
New Enterprise System.

Clearly Rapid Application Development (RAD) to implement the New Enterprise System is about more
than just delivering applications as quickly as possible. It defines an approach to application
development involving short, iterative development cycles; timeboxing; prototyping; and the use of
modern technology.

The RAD methodology recommends the use of small teams that consist of experienced, versatile, and
motivated members that are able to perform multiple roles. As the client plays a vital role in the
development process, dedicated client resources must be available during the initial Joint Application
Development (JAD) sessions as well as Focus Group Sessions conducted at the end of development
cycles. Development teams (also known as SWAT or Skilled Workers with Advanced Tools) should ideally
have experience in Rapid Application Development and should have experience with the Computer
Aided Software Engineering tools. However the project takes approximately six week (36 working days)
to implement because some of the stages would required being redesign and revisiting to capture the
logical scenarios.

29
 Grapevine Vineyard Winery New Enterprise System
__________________________________________________________________________________________________________________________________________________________________________________________________________________________________________
___________________________________________________________________________________________________________________________________________________ _______________________________________________________________________________________

6.0 Appendices
Appendix A illustrates the Gantt chart, tasks and the critical path involve in the implementation of the
New Enterprise System.

30
 Grapevine Vineyard Winery New Enterprise System
__________________________________________________________________________________________________________________________________________________________________________________________________________________________________________
___________________________________________________________________________________________________________________________________________________ _______________________________________________________________________________________

31
 Grapevine Vineyard Winery New Enterprise System
__________________________________________________________________________________________________________________________________________________________________________________________________________________________________________
___________________________________________________________________________________________________________________________________________________ _______________________________________________________________________________________

7.0 References:

Morrison, Mike., 2007. Duchlock, 3 Jan. pp.27-32. Available at

http://publib.boulder.ibm.com/infocenter/wchelp/v5r6/index.jsp?topic=/com.ibm.commerce.admin.doc/
concepts/csdb2bdirectmodel.htm

Chaffey, D. and Wood, S., 2004. E Business and EcommerceManagement. 3rd ed. New York: USA
Prentice Hall.

Grönroos, C. 2000. Service Management and Marketing - A Customer Relationship Management

Approach 2nd Edition. Wiley and Sons.

Hanson, W. 2000. Principles of Internet Marketing. S-Western College Publishing.

Humby, C. and Hunt, T. 2003. Scoring points. How Tesco is Winning Customer Loyalty. Kogan Page,
London, UK.

32