Finishing School .Net Work-Shop (Day2)

Northern Region Finishing School 2009

.NET Workshop (Day2)

Siwawong W.Project Manager

2009.10.11

Get User Requirements & Analysis


Agenda (Day2)

09:00 – 09:15 Course Introduction

09:15 – 10:45 User Requirement Explanation

10:45 – 11:00 Break & Morning Refreshment

11:00 – 12:00 Analysis Requirements (Work Shop)

12:00 – 13:00 Lunch Break

13:00 – 14:30 Design System (Work Shop)

14:30 – 14:45 Break

14:45 – 16:00 Presentation (Work Shop)

16:00 – 17:00 Next Assignment


Course Introduction


About Me

• My Name: Siwawong Wuttipongprasert– Nick-name: Tae

• My Background: – B.Eng (Computer Engineering), Chiang Mai University.

CPE#3, Gear25

• My Career Profile: – 10+ years in IT business– 5+ years with Blue Ball Co., Ltd.– Role: Programmer, System Analysis, Consultant & Project Manager– Working Area: ERP, MRP, Retailing, Banking, Financial, E-Commerce, etc.– Working with multi-cultures: Japanese, German and Vietnamese

• Know Me More..


Pre-Requisition/Background

• Understand on following topics: -– C# Programming– Any R-DMBS (Prefer MS-SQL server 2005 or higher)– OOP (Object Oriented Programming)– MVC (Model-View-Controller)– UML (Unified Modeling Language)

• Required Software for Workshop– Visual Studio 2005 (with Framework 2.0)– MS-SQL server 2005– Crystal Report/MS-Reporting


Working Schedule

Day-2 Day-3 Day-4

• Get User Requirements• Analysis & Design

• Weekly Progress Report• Unit Test Result• Problem/issues(Communicate via e-mail/Wave)

• Code Review• Unit Test Review• SIT Review

• Project Implementation• User Training

• Bug Fixed• Improve System


User Requirement Explanation


Customer Story

HQ in BKK

• Assembly the F/G• Purchase Parts• Get Orders from customer• Send F/G to customer

Warehouse in Chiang Mai

Warehouse in Chon buri

ABC Factory has located in BKK and they has W/H in Chiang Mai & Chon Buri. Only HQ in BKK get Order, Purchase Part & assembly. The W/H outside BKK act as Depot.


Current Problems

• HQ in BKK can’t know Inventory On-hand on each Depot

• Information is not CENTRALIZED!

• Difficult to management Inventory On-hand on each Depot

• Always stored items on wrong places

• Difficult to find inventory item/No stored information.

• Too slow for prepare management report

• Overhead cost for communication between site is too much


Customer Needs

• Web-based system for share Inventory information– Prefer to implement with ASP.NET with MS-SQL server 2005.

• Support Basic Operations– Received Purchased Item from Vendor– Delivery Ordered item to Customer– Move Stock between Warehouse– Able to adjust stock QTY

• Required to finish within 1 month!


Our Solution

Item Master

Zone Master

Category

Goods ReceivingGoods Receiving

Goods Receiving Entry

Shelf-In Entry

Goods Receiving List

Transfer-In Entry

ShipmentShipment

Shipment Entry

Shelf-Out Entry

Shipment List

Transfer-Out Entry

InventoryInventory

In & Out Adjustment

Supplier Customer

Inventory By Category


Technical Requirements

• Web-Based System (ASP.NET & MS-SQL server)– C# is preferred– Implement in MVC concept

• Required to implement ORM– NHibernate is recommended

• Some Common Screens/Models– Share between modules, no need to make it’s duplicated

• General Requirements– No need to login before access the system– Provided simple main menu– Capture user’s login & Computer name from windows and stamp on

transaction


Understand the MVC

Controller

Controller accepts User inputs as parameters to generate the data.

View

View provides result in desired presentation format.

Model

Model queries data-source to retrieve result set for controller.

Model Queries data source based on input parameters specified by the User.

Returns result set to the controller.

Controller Enforces access control.

Accepts input parameters.

Accepts report configuration parameters.

Invokes Model to perform data query operations.

Provides View with result set returned by Model.

View Formats result set to generate report in the format specified by the User:• HTML• Comma Separated Values (CSV)• Adobe Portable Document Format (PDF)


List of Function Names

Module Name SEQ Function Name Page Name Remark

Inventory 1-1 Zone Master Zonemaster.aspx

1-2 Category Category.aspx

1-3 Item Master ItemMaseter.aspx Share Customer/Supplier information from other modules

1-4 In&Out Adjustment StockAdjustment.aspx

1-5 Inventory By Category StockByCat.aspx

Goods Receving

2-1 Goods Receiving Entry GREntry.aspx Share item information from

2-2 Shelf-In Entry ShelfIn.aspx Inventory

2-3 Goods Receiving List GRList.aspx

2-4 Transfer In Entry TrfIn.aspx

2-5 Supplier Data Supplier.aspx


List of Function Names (Con’t)

Module Name SEQ Function Name Page Name Remark

Shipment 3-1 Shipment Entry ShipEntry.aspx Share item information from

3-2 Shelf-Out Entry ShelfOut.aspx Inventory

3-3 Shipment List ShipList.aspx

2-4 Transfer Out Entry TrfOut.aspx

2-5 Customer Data Customer.aspx


User Requirement Specification

• Zone Master– Zone Code– Zone Description– Shelf Structure

Row, Column, Bin Defined R/C/B in Zone : Start RCB – End

RCB

• Category Master– Item Category Code & Description

• Item Master– Item Code & Item Description– UoM or Unit Of Measurement (text

description)– Supplier– Zone Code

Row/Col/Bin (under Zone Code)

• Supplier Master– Supplier Code & Supplier Name– Supplier Short Name (for search

purpose)– Address (long text is enough)– Tel.No.

• Customer Master– Customer Code & Customer Name– Customer Short Name (for search

purpose)– Address (long text is enough)– Tel.No.



• Goods Receiving Entry – Input Supplier Code (manual input or search supplier)– Invoice No./Delivery No. (text input, following document from Supplier)– Input Receiving Date & Receiving Time– If above inputs are not existing in DB, system will allow user to add

new receiving items. Else, load existing data for user to edit

[Detail, multi-lines input]– Input following these information

Item Code (manual input or search item code) If found input item code Display item Description, UoM Then input, serial number & QTY

– Press save for whole document (not save line-by-line) After save complete, need to display Transaction No for further use.

(Cont’)



• Shelf-In Entry – Input Transaction No of Goods Receiving (manual input or

search)– If above inputs are existing in DB, system will allow user to

input location of receiving items. Else, display error message


Display item code, item Description, UoM, Default Zone Code, R/C/B (refer from master data)

Try to change Zone Code, R/C/B (if user want)

– Press save for whole document (not save line-by-line) Mark flag on each line to show that user has stored in shelf.

(Cont’)



• Goods Receiving List – Input criteria to print

Supplier Code (manual or search) Period of Date (default is today date until today date) Status (Just Receiving or Stored in Shelf already)

– Output List following data to display

– Receiving Date (1st Group)– Zone Code (2nd Group)– Supplier (3rd Group)– R/C/B (Suppress if duplicated)– Item Code, Description, Delivery No., Serial No, QTY, Status

(Cont’)



• Transfer-In Entry – Input Transaction No of Transfer-Out (manual input or search)– If above inputs are existing in DB, system will allow user to

input location of receiving items. Else, display error message Output


Display item code, item Description, UoM, Default Zone Code, R/C/B

(refer from Transfer-Out Entry) Try to change Zone Code, R/C/B (if user want)

– Press save for whole document (not save line-by-line)

(Cont’)



• Shipment Entry – Input Customer Code (manual input or search customer)– Delivery No. (text input, following document from Sales Person)– Input Shipment Date & Shipment Time– If above inputs are not existing in DB, system will allow user to add

new shipping items. Else, load existing data for user to edit


Item Code (manual input or search item code) If found input item code Display item Description, UoM Then input, serial number & QTY

– Press save for whole document (not save line-by-line) After save complete, need to display Transaction No for further use.

(Cont’)



• Shelf-Out Entry – Input Transaction No of Shipment (manual input or search)– If above inputs are existing in DB, system will allow user to

input location of receiving items. Else, display error message


Display item code, item Description, UoM, Default Zone Code, R/C/B (refer from master data)

Try to change Zone Code, R/C/B (if user want)

– Press save for whole document (not save line-by-line) Mark flag on each line to show that user has stored in shelf.

(Cont’)



• Shipment List – Input criteria to print

Customer Code (manual or search) Period of Date (default is today date until today date) Status (Preparation or take-out from Shelf already)

– Output List following data to display

– Shipment Date (1st Group)– Zone Code (2nd Group)– Customer (3rd Group)– R/C/B (Suppress if duplicated)– Item Code, Description, Delivery No., Serial No, QTY, Status

(Cont’)



• Transfer-Out Entry – Input these information

Transfer-Out Date (default is today date) Source : Zone Code, R/C/B Destination: Zone Code, R/C/B

– If above inputs are existing in DB, system will allow user to transfer out QTY. Else, display error message Output

[Detail, multi-lines input]

– Input following these information Display item code, item Description, UoM, Default Zone Code, R/C/B Input Transfer-Out QTY

– Press save for whole document (not save line-by-line) Display transaction no for further use.

(Cont’)



• In & Out Adjustment Entry– Input these information

Item Code (manual input or search) Specified period Date Type: In or Out

– In : Goods Receiving or Transfer-In Operation– Out: Shipment or Transfer-Out Operation

– If above inputs are existing in DB, system will allow user to input new QTY. Else, display error message Output


Display item code, item Description, UoM, Default Zone Code, R/C/B Input New QTY

– Press save for whole document (not save line-by-line)

(Cont’)


Analysis User Requirement


Expected Result from Analysis Phase

• Team Organization– Tree View– Roles & Responsible

• UML diagram– Use Case Diagram– Activities Diagram– GUI design

• Micro-Plan Schedule– Until 9-Jan-10


Design System


Expected Result from Design Phase

• E-R diagram– Table structure

• Class Diagram– Controller– Model– View


Presentation


Schedule for Present

• 30 mins/Team– Display overview in Analysis Phase– Submit Design document

• Q&A– Comments


Next Assignment


Next Assignment

• Progress report on every Friday– Update progress in schedule

• Submit Unit Test Result every Friday– Tested By Tools: NUnit– Manual Test: input in result form


Thank you for your attention!

[email protected] [email protected]

www.blueballgroup.com

Finishing School .Net Work-Shop (Day2)

Technology

entry inventory

entry goods

shipment entry function

entry shipment list

share inventory information

zone master function

supplier data

remark customer data