Miriam Barrera, Han Le, and Ambarish Regmi

ISAM 4635Fall 2006

CUSTOM CLOTHING

Prepared by:

MIRIAM BARRERA, HAN LE, AND AMBARISH REGMI

ISAM 4635SYSTEM ANALYSIS & DESIGN

FALL 2006

NOVEMBER 28, 2006

Dr. MOHAMMAD A. ROB

Project Summary

We are a small custom clothing store located on 2700 Bay AreaBlvd. serving the local Clear Lake Area. Our business is in customclothing, tailor to specific needs. We started with 50 customers thefirst year and are now currently serving about 700 customers (3-years later). We are currently using paper based processing system.

Our main purpose when we opened this custom clothing was toserve the local community. Now, because we are so good at whatwe do, we have growing number of customer everyday. Thisproject has been initiated to establish a computerized system thatwill replace the current system. Our new system will help us tokeep records of the customers. This system will help make it easierfor us to retrieve the information about our existing customers, andto enter information about our new customers. We are hopeful that,with this new system we will be able to provide better platform.This will also assist us in meeting the growing demand and increase sales.

We created a system that will help us do the following things:

Store customer, order, inventory, clothing line, and employee information.
Have user friendly interface
Provide an easy way to update existing and add new information
Aid in managing inventory
Aid in internal order tracking

We are hopeful that this new system will support our business needs and requirements and increase the sales.

System Request

Custom Clothing

“You don’t have to come to us, we’ll come to you!”

Project Sponsor:Ambarish Regmi, Han Le, Miriam Barrera

Background:We are a small custom clothing store located on 2700 Bay Area Blvd. serving the local Clear Lake Area. Our business is in custom clothing, tailor to specific needs. We started with 50 customers the first year and are now currently serving about 700 customers (3-years later). We are currently using paper based processing system.

Business Need:Our main purpose when we opened this custom clothing was to serve the local community. Now, because we are so good at what we do, we have growing number of customer everyday. This project has been initiated to establish a computerized system that will replace the current system. Our new system will help us to keep records of the customers. This system will help make it easier for us to retrieve the information about our existing customers, and to enter information about our new customers. We are hopeful that, with this new system we will be able to provide better platform. This will also assist us in meeting the growing demand and increase sales.

Business Requirements:Since we are currently not storing any information for our business other than sales receipt, this is becoming an inefficient way to serve returning and new customers. We would like to request a system that will help manage customer information in an easy and efficient way. This will allow us to shift our efforts towards improving customer services. The expected functionality of the system is listed below:

Store customer, order, inventory, clothing line, and employee information.
Have user friendly interface
Provide an easy way to update existing and add new information
Aid in managing inventory
Aid in internal order tracking.

Business Value:We expect that the system will make better use of our employees’ time spend progressing customer and order information. This in turn will allow our staff to become more customer oriented and provide excellent services. Our expectations of how this will benefit the business as a whole:

Customized customer services to meet individual needs
Fast and reliable response to orders
More time investing in marketing
Capability to expand the business

Special Issues and Constraints:

The system should be completed and implemented within 12 months from the start date, which is expected to be at the end of October 2006.
Time consideration to convert our current paper-based system into new computerized database.

Feasibility Analysis

Custom Clothing

We have created a feasibility analysis for our new system that includes:

-Technical feasibility

-Economical feasibility

-Organizational feasibility

Technical feasibility:The new system is feasible technically with a moderate to high level of risk due to the following reasons:

Major transition from paper-based system to a computerized system
Requiring considerable internal staff training
This type of computerized system is widely used in variety of businesses.
To gain competitive advantage with the use of this system

Project size:The project size is considered medium.

One Project Manager/ DBA
One database developer
One programmer
Timeframe is expected to be 9 months to a year

Economical feasibility:According to the cost-benefit analysis below, the new system is considered to be economically feasible.

Note: all current annual, monthly, and bi-monthly figures are based on FY 2005 * Sept 1 2005 - Aug 30 2006
Cost:
Item / Current Cost
Bi-Monthly / Current Cost
Monthly / Current Annual Cost / Projected Annual Cost with System Development Cost / Projected Annual Cost after System Implementation
Staffing:
1 project manager / n/a / n/a / n/a / 45,600.00 / n/a
1 database developer / n/a / n/a / n/a / 40,800.00 / n/a
1 programmer / n/a / n/a / n/a / 40,800.00 / n/a
System Maintenance / n/a / n/a / n/a / 0.00 / 24,000.00
Sub-totals / 0.00 / 0.00 / 127,200.00 / 24,000.00
1 Store Manager / 1,500.00 / 3,000.00 / 36,000.00 / 36,000.00 / 36,000.00
10 Tailors / 13,000.00 / 26,000.00 / 312,000.00 / 312,000.00 / 312,000.00
12 Assistant Tailors / 13,200.00 / 26,400.00 / 316,800.00 / 316,800.00 / 316,800.00
Sub-totals / 27,700.00 / 55,400.00 / 664,800.00 / 664,800.00 / 664,800.00
Total Staff Expense: / 27,700.00 / 55,400.00 / 664,800.00 / 792,000.00 / 688,800.00
Inventory:
Fabrics / n/a / 5,000.00 / 60,000.00 / 60,000.00 / 60,000.00
Threads / n/a / 400.00 / 4,800.00 / 4,800.00 / 4,800.00
Other Equipment / n/a / 1,500.00 / 18,000.00 / 20,000.00 / 20,000.00
Sub-total / 6,900.00 / 82,800.00 / 84,800.00 / 84,800.00
Utilities:
Rent / n/a / 1,000.00 / 12,000.00 / 12,000.00 / 12,000.00
Insurance / n/a / 1,000.00 / 12,000.00 / 12,000.00 / 12,000.00
Other utilities / n/a / 1,600.00 / 19,200.00 / 19,200.00 / 19,200.00
Sub-total / 3,600.00 / 43,200.00 / 43,200.00 / 43,200.00
Total Operational Cost: / 27,700.00 / 65,900.00 / 790,800.00 / 920,000.00 / 816,800.00
Sales Revenue:
Item / Current Monthly Sales Revenue / Current Annual Sales Revenue / Expected
Growth Rate / Expected Annual Sales Revenue Growth / Projected Annual Sales Revenue
Sales
Returning Customers / 59,062.50 / 708,750.00 / 0.35 / 248,062.50 / 956,812.50
New Customers / 19,687.50 / 236,250.00 / 0.30 / 70,875.00 / 307,125.00
Total Sales Revenue / 78,750.00 / 945,000.00 / 318,937.50 / 1,263,937.50
*Currant Annual Profits / **Projected Annual Profits including System Development Cost / ***Current Annual Profits after System Development Cost / ****Projected Annual Profits after System Development Cost
Profits: / 154,200.00 / 25,000.00 / 128,200.00 / 447,137.50
*Currant Annual Profits = Current Annual Sales Revenue - Current Total Operational costs
**Projected Annual Profits including System Development Cost = Current Annual Sales Revenue - Total Projected Annual Cost with System Development Cost
***Current Annual Profits after System Development Cost = Current Annual Sales - Total Projected Annual Cost after System Development Cost
****Projected Annual Profits after System Development Cost = Projected Annual Sales Revenue - Total Projected Annual Cost after System Implementation

Tangible Benefits:

Increase annual sales by at least 30% from new customers.
Increase annual sales by at least 35% from existing customers.
Lower inventory cost by 30% with JIT
Lower operational cost by 10%

Intangible Benefits:

Customer satisfaction
Fast and reliable services for a reasonable price
Not limited to local community anymore
On-sight service (if desired)
Reduction in customer complaints

Organizational feasibility:Our new system has a low level of risk from the organizational perspective. The goals of our system are to increase sales and customer satisfaction, which are well aligned with our business’s goals.

Cost Benefit Analysis

Sales Revenue:
Item / Current Monthly Sales Revenue / Current Annual Sales Revenue / Expected
Growth Rate / Expected Annual Sales Revenue Growth / Projected Annual Sales Revenue
Sales
Returning Customers / 59,062.50 / 708,750.00 / 0.35 / 248,062.50 / 956,812.50
New Customers / 19,687.50 / 236,250.00 / 0.30 / 70,875.00 / 307,125.00
Total Sales Revenue / 78,750.00 / 945,000.00 / 318,937.50 / 1,263,937.50
*Currant Annual Profits / **Projected Annual Profits including System Development Cost / ***Current Annual Profits after System Development Cost / ****Projected Annual Profits after System Development Cost
Profits: / 154,200.00 / 25,000.00 / 128,200.00 / 447,137.50
*Currant Annual Profits = Current Annual Sales Revenue - Current Total Operational costs
**Projected Annual Profits including System Development Cost = Current Annual Sales Revenue - Total Projected Annual Cost with System Development Cost
***Current Annual Profits after System Development Cost = Current Annual Sales - Total Projected Annual Cost after System Development Cost
****Projected Annual Profits after System Development Cost = Projected Annual Sales Revenue - Total Projected Annual Cost after System Implementation

Current Vs Projected Sales

Revenue Trend

Project Plan Estimation

Size Estimation

Function Point Approach
Complexity
Description / Total Number / Low / Medium / High / Total
Inputs / 6 / 3 / x / 3 / 2 / x / 4 / 1 / x / 6 / 23
Outputs / 7 / 4 / x / 4 / 2 / x / 5 / 1 / x / 7 / 33
Queries / 10 / 5 / x / 3 / 5 / x / 4 / 0 / x / 6 / 35
Files / 2 / 2 / x / 7 / 0 / x / 10 / 0 / x / 15 / 14
Program Interfaces / 3 / 1 / x / 5 / 2 / x / 7 / 0 / x / 10 / 19
Total Unadjusted Function Points (TUFP): / 124
Overall System:
Data Communications / 3 / Adjusted Project Complexity (APC):
Heavy use configuration / 0
Transaction Rate / 0 / 0.65 + (0.01 * PC) = / 0.74 / APC
End-user efficiency / 1
Complex processing / 1 / Total Adjusted Function Points (TAFP):
Installation ease / 2
Multiple sites / 0 / APC * TUFP = / 91.8 / TAFP
Performance / 0
Distributed functions / 1
Online data entry / 0
Online update / 0
Reusability / 0
Operational ease / 1
Extensibility / 0
Total Processing Complexity (PC): / 9
Lines of Code:
(0.60 * TAFP * 30) + (0.30 * TAFP * 25) + (0.10 * TAFP * 15) = / 2478 / Thousands of lines of code
Estimate Effort Required:
1.4 * Thousands of lines of code = / 3469 / Effort (in person-months)
Effort (in person-months) /1000 = / 3.47 / Person-months
Estimate Time Required:
3.0 * (person-months) ^ (1/3) ) = / 4.54 / Schedule time (months)

Work Breakdown Structure

Gantt Chart

Task Name / Duration / Start / Finish / Predecessors
Project Summary / 171 days / 9/1/2006 8:00 / 4/27/2007 17:00
System Planning / 46 days / 9/1/2006 8:00 / 11/3/2006 17:00
Identify Problems / 10 days / 9/1/2006 8:00 / 9/14/2006 17:00
System Request / 10 days / 9/15/2006 8:00 / 9/28/2006 17:00 / 3
Feasibility Analysis / 14 days / 9/29/2006 8:00 / 10/18/2006 17:00 / 4
Size Estimation / 5 days / 10/19/2006 8:00 / 10/25/2006 17:00 / 5
Work Plan / 7 days / 10/26/2006 8:00 / 11/3/2006 17:00 / 6
Staffing Plan / 5 days / 10/26/2006 8:00 / 11/1/2006 17:00 / 6
Standards List / 5 days / 10/26/2006 8:00 / 11/1/2006 17:00
Risk Assessment / 7 days / 10/26/2006 8:00 / 11/3/2006 17:00 / 6
System Analysis / 26 days / 11/6/2006 8:00 / 12/11/2006 17:00
Requirements Definition / 7 days / 11/6/2006 8:00 / 11/14/2006 17:00 / 10
Use Cases / 7 days / 11/15/2006 8:00 / 11/23/2006 17:00 / 12
Data Flow Diagram / 7 days / 11/24/2006 8:00 / 12/4/2006 17:00 / 13
Process Description / 5 days / 12/5/2006 8:00 / 12/11/2006 17:00 / 14
System Design / 56 days / 12/12/2006 8:00 / 2/27/2007 17:00
Data Modeling / 5 days / 12/12/2006 8:00 / 12/18/2006 17:00 / 15
Architecture Design / 16 days / 12/19/2006 8:00 / 1/9/2007 17:00 / 17
User Interface Design / 14 days / 1/10/2007 8:00 / 1/29/2007 17:00 / 18
Program Design / 14 days / 1/30/2007 8:00 / 2/16/2007 17:00 / 19
Data storage Design / 7 days / 2/19/2007 8:00 / 2/27/2007 17:00 / 20
System Implementation / 43 days / 2/28/2007 8:00 / 4/27/2007 17:00
System Architecture / 7 days / 2/28/2007 8:00 / 3/8/2007 17:00 / 21
Database development / 10 days / 3/9/2007 8:00 / 3/22/2007 17:00 / 23
Program codes / 14 days / 3/23/2007 8:00 / 4/11/2007 17:00 / 24
Program testing / 7 days / 4/12/2007 8:00 / 4/20/2007 17:00 / 25
System Installation / 5 days / 4/23/2007 8:00 / 4/27/2007 17:00 / 26

Staffing Plan

Item / Current Cost
Bi-Monthly / Current Cost
Monthly / Current Annual Cost / Projected Annual Cost with System Development Cost / Projected Annual Cost after System Implementation
Staffing:
1 project manager / n/a / n/a / n/a / 45,600.00 / n/a
1 database developer / n/a / n/a / n/a / 40,800.00 / n/a
1 programmer / n/a / n/a / n/a / 40,800.00 / n/a
System Maintanance / n/a / n/a / n/a / 0.00 / 24,000.00
Sub-totals / 0.00 / 0.00 / 127,200.00 / 24,000.00
1 Store Manager / 1,500.00 / 3,000.00 / 36,000.00 / 36,000.00 / 36,000.00
10 Tailors / 13,000.00 / 26,000.00 / 312,000.00 / 312,000.00 / 312,000.00
12 Assistant Tailors / 13,200.00 / 26,400.00 / 316,800.00 / 316,800.00 / 316,800.00
Sub-totals / 27,700.00 / 55,400.00 / 664,800.00 / 664,800.00 / 664,800.00
Total Staff Expense: / 27,700.00 / 55,400.00 / 664,800.00 / 792,000.00 / 688,800.00

Standards:

Our standards are created to ensure that team members are performing tasks in the same way and following the same procedures.

Types of Standards / Standard Practices
Documentation Standards /

Date and project name should appear on all documentation.
Margins should be 1 inch for all documents.
Every order/delivery should be recorded in the system.

Programming and Coding Standards /

Programs should include comment lines after each 12 lines of code.
Indentation should be used for the conditions.
Should contain the programmer’s name in each page of the program.

Dress Codes /

All employees must wear the uniform at all time at work.
Uniform must bear the company’s logo
Employees and their dress should be neat and clean
All employees must wear a name tag at all time at work.

Risk Assessment

We have created a risk assessment document to track potential risks and best solution(s) for it.

Risk #1:Likelihood of our system getting hacked

Solution:These days hackers seem to be interested in all sorts of business. To avoid our information from getting hacked, we are planning on using two different computers. The first computer will be used to check the email orders, which will be hooked to the internet. The second computer’s sole purpose is data storage and we will not hook this up to the internet, making it impossible for the hackers to get to our information.

Risk #2:Loss of data due to system failure.

Solution:There is always a chance for a system to crash. In order to minimize the loss from this kind of information, we are planning on storing all or data in a separate storage device in a different location.

Risk #3:There is a likelihood that our employees are not getting comfortable with our new system.

Solution:Provide extended hours of training and provide enough time for all the employees to get familiar with the system.

PRESENTATION 1: SYSTEMS REQUEST

Data Flow Diagrams

PRESENTATION 2: PROCESS MODELING

Data Dictionary

Data Flow

The data flow description gives more details about the flow of data from one entity to a process or from a data store to a process and vice versa. The form describes and exemplifies the pieces of data and their source/ destination. Additionally, data description includes the type of data flow in which the information goes from one to another entity/process/data store. The form may also include volume and frequency depending on the type of data flow in question.

Name: Customer information
Description: Customer information includes new customer information as well as updated information of existing customer. This information will be provided by customers and will be stored in customer information table.
Source Destination
Customer (external entity) Manage Customer Information process
Type of Data Flow
Data volume and frequency
Frequently during the day.
Comments:
Name: Order information
Description: Order information from customer.
Source Destination
Customer (external entity) Place Orders
Type of Data Flow
Data volume and frequency
Approximately 10 to 20 per day
Comments:
Name: Update Order Info
Description: Updated order information is stored in order information database.
Source Destination
Process Order Order Information table
Type of Data Flow
Internal
Data volume and frequency
Frequently during the day
Comments:
Name: Order Approval
Description: Orders approved by management are transfer to process orders.
Source Destination
Management Process Orders
Type of Data Flow
Internal
Data volume and frequency
Frequently during the day
Comments:
Name: Finished Order Info
Description: Finished order information is transfer to billing process for preparing invoices.
Source Destination
Order Information table Bill Customers
Type of Data Flow
Internal
Data volume and frequency
Frequently during the day
Comments:
Name: Update billing Info
Description: Billing information updated in billing storage.
Source Destination
Bill Customers Billing table
Type of Data Flow
Internal
Data volume and frequency
Frequently during the day
Comments:
Name: Available Tailor
Description: After orders have been approved by management, a list of available tailors is retrieved.
Source Destination
Employee Information table Process Orders
Type of Data Flow
Internal
Data volume and frequency
Frequently during the day
Comments:
Name: Updated Inventory
Description: Inventory is updated after order has been processed and saved in inventory information table.
Source Destination
Process Orders Inventory Information table
Type of Data Flow
Internal
Data volume and frequency
Frequently during the day
Comments:
Name: Available Inventory
Description: A list of available inventory is retrieved.
Source Destination
Inventory Information table Process Orders
Type of Data Flow
Internal
Data volume and frequency
Frequently during the day
Comments:
Name: Order Assignment
Description: After orders have been assigned to tailors, they will be transferred to factory.
Source Destination
Manage Orders Factory
Type of Data Flow
Internal
Data volume and frequency
Frequently during the day
Comments:
Name: Raw Material Orders
Description: Raw material orders sent to vendors.
Source Destination
Manage Inventory Information Vendors/Suppliers
Type of Data Flow
External
Data volume and frequency
Frequently during the day
Comments:
Name: Order Status
Description: Order status will be updated by tailors and stored in order information storage.
Source Destination
Factory Manage Order
Type of Data Flow
Internal
Data volume and frequency
Frequently during the day
Comments:
Name: Order Assignment
Description: After orders have been approved by management, they will be assigned to available tailors.
Source Destination
Manage Orders Factory
Type of Data Flow
Internal
Data volume and frequency
Frequently during the day
Comments:
Name: Inventory Info
Description: Inventory information includes vendor information, available quantity, and price. This information is stored in Inventory Information table.
Source Destination
Inventory Information table Process Reports
Type of Data Flow
Internal
Data volume and frequency
Frequently during the day
Comments:
Name: Employee Info
Description: Employee information is stored in employee information table.
Source Destination
Employee Information table Process Reports
Type of Data Flow
Internal
Data volume and frequency
Frequently during the day
Comments:
Name: Customer Report
Description: A list of customers and their information and order history retrieved by management.
Source Destination
Process Reports Management
Type of Data Flow
Internal
Data volume and frequency
Once or twice a month or when necessary.
Comments:
Name: Inventory Report
Description: A list of inventory information retrieved by management.
Source Destination
Process Reports Management
Type of Data Flow
Internal
Data volume and frequency
Once or twice a month or when necessary.
Comments:
Name: Order Report
Description: A list of order information retrieved by management.
Source Destination
Process Reports Management
Type of Data Flow
Internal
Data volume and frequency
Once or twice a month or when necessary.
Comments:
Name: Employee Report
Description: A list of employees and their information retrieved by management.
Source Destination
Process Reports Management
Type of Data Flow
Internal
Data volume and frequency
Once or twice a month or when necessary.
Comments:

Data Dictionary