Business Information Systems Project: Artisans Cooperative Analysis

This document presents a comprehensive project solution for a Business Information Systems course, focusing on the Artisans Cooperative. The project encompasses several key areas including requirements gathering, domain analysis, behavioral modeling, and structural and dynamic modeling. The solution begins with an overview of the system owners' perspective, identifying stakeholders such as cooperative members, customers, and website service providers. Domain analysis is then conducted, outlining the scope of the Artisans Cooperative and defining core objects like members, items, and customers. Behavioral modeling is addressed through use case summaries, illustrating scenarios such as online ordering and inventory management. Detailed use cases, including manual inventory updates, are provided, specifying actors, scope, priority, and both normal and alternate flows. Finally, the project delves into structural and dynamic modeling, identifying class candidates and their responsibilities, along with relationships like aggregation. This project offers a complete analysis of a business information system.

Business Information Systems 1
BUSINESS INFORMATION SYSTEMS
Student’s Name
Course
Lecturer
University
Date

Business Information Systems 2
Requirements Gathering
Question 1
System owners’ view is concerned with the communication scope of the management system. It
focuses on the stakeholders who interact with the system. These stakeholders include cooperative
members with accounts on the system, customers who order from the site, members of the
management committee, and website service provider. The scope incorporates the location of
these stakeholders. That is, where the stakeholders access the system and how they use it.
Question 2
System users
Business system users
 Website service provider
 Administrator
 Members of the cooperative
Information system users
 Customers
 Members of the cooperative
Domain Analysis
Question 3
Artists Cooperative
Domain Scope

Business Information Systems 3
Domain Scope Outline
Administration Managing system functions and processes at
the admin level
Operations System functions that rely on interaction
between stakeholders and the system
Question 4
Artists Cooperative
Domain Scope
Name Type Description
Member Object Registered as a system user
Items Object Item details stored in the
database and showcased to
the public
Customer Object Purchases items from the
members
Registration Process Customers and members have
to register to use the system
Order Function Customers order the items
they want to purchase
Validate details Function Payment details are validated
for the purchase to be
confirmed

Business Information Systems 4
Report generation Process Sales are generated weekly
by the sales service
Behavioral Modelling
Question 5
Artisans Cooperative
Stakeholders & Actors
Name Description
Customer Customer interacts with the system to
purchase items from the vendors
Member Members create profile and post the items
they are selling
Manager Manager requests creation of member
accounts and manage system operations
Website service provider Registers a member account once requested
by the manager
Question 6
Artisans Cooperative
Online Ordering: Use Case Summary
ID: UC_001 Name Description Actors
Make Order Customer views the
item available. He
selects one item and
Members
Managers

Business Information Systems 5
orders it. Purchase is
confirmed when
payment is made.
Customer
Artisans Cooperative
Inventory Management: Use Case Summary
ID: UC_002 Name Description Actors
Manage online
inventory
Once an order is made,
managers/members
manually update the
online inventory
following market stall
sales.
Members
Manager
Question 7
Use Case: Manual inventory update
ID: UC_002
Scope: Inventory management
Priority: High
Summary: The member of the cooperative manually update their online
inventory after selling items to customers at the market stalls.
If a member is not available, managers fulfill orders and
manually update the online inventory.
Primary Actor: Member

Business Information Systems 6
Supporting Actors: Manager, Customer
Stakeholders: Members and Managers
Generalization: Inventory update
Include: Record the units sold
Extend: Customer purchases a product
Precondition: No sales have been at the market stall.
Trigger: Member makes a sale at the market stall.
Normal Flow: Inventory updated after sales are made
Sub-flows: Sales made at the market stalls are recorded
Member access the system
Inventory levels are updated
Alternate Flow/Exceptions: Manager updates the inventory on behalf of the absent member
Post-Condition: Inventory updated to indicate the items remaining after sales at
the market stall.
Non-Behavioral
Requirements:
A sale has to be made for the inventory to be updated.
Open Issues: System fails to update the inventory.
Source: N/A
Author: N/A
Revision & Date: 10th October 2017
Question 8

Business Information Systems 7
Question 9

Business Information Systems 8
Structural and Dynamic Modelling
Question 10
Artisans Cooperative
Online Ordering: Preliminary Class Candidates
Class Responsibilities Use Cases
Display items available
Allow customer to select and
add item to cart
Allow online payment and
validation of purchase details
Make Order
Artisans Cooperative
Inventory Management: Preliminary Class Candidates

Business Information Systems 9
Class Responsibilities Use Cases
Allow member to access the
system
Update records based on the
data supplied
Manual Inventory Update
Question 11
There are several relationships in the diagram that can be described by aggregation. For example,
aggregation can describe the relationship between order and item. This is because orders are
made up of several items that customers purchase. However, there are no generalized classes as
there is no class which is a child of another.
Question 12