Finishing School .Net Work-Shop (Day2)

634 views

Published on

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
634
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
20
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Finishing School .Net Work-Shop (Day2)

  1. 1. .NET Workshop (Day2) Siwawong W. Project Manager 2009.10.11 Get User Requirements & Analysis
  2. 2. Agenda (Day2) Presentation (Work Shop) 14:45 – 16:00 Next Assignment 16:00 – 17:00 Break 14:30 – 14:45 Design System (Work Shop) 13:00 – 14:30 Lunch Break 12:00 – 13:00 Analysis Requirements (Work Shop) 11:00 – 12:00 Break & Morning Refreshment 10:45 – 11:00 User Requirement Explanation 09:15 – 10:45 Course Introduction 09:00 – 09:15
  3. 3. Course Introduction
  4. 4. About Me <ul><li>My Name: Siwawong Wuttipongprasert </li></ul><ul><ul><li>Nick-name: Tae </li></ul></ul><ul><li>My Background: </li></ul><ul><ul><li>B.Eng (Computer Engineering), Chiang Mai University. </li></ul></ul><ul><ul><li>CPE#3, Gear25 </li></ul></ul><ul><li>My Career Profile: </li></ul><ul><ul><li>10+ years in IT business </li></ul></ul><ul><ul><li>5+ years with Blue Ball Co., Ltd. </li></ul></ul><ul><ul><li>Role: Programmer, System Analysis, Consultant & Project Manager </li></ul></ul><ul><ul><li>Working Area: ERP, MRP, Retailing, Banking, Financial, E-Commerce, etc. </li></ul></ul><ul><ul><li>Working with multi-cultures: Japanese, German and Vietnamese </li></ul></ul><ul><li>Know Me More.. </li></ul>
  5. 5. Pre-Requisition/Background <ul><li>Understand on following topics: - </li></ul><ul><ul><li>C# Programming </li></ul></ul><ul><ul><li>Any R-DMBS (Prefer MS-SQL server 2005 or higher) </li></ul></ul><ul><ul><li>OOP (Object Oriented Programming) </li></ul></ul><ul><ul><li>MVC (Model-View-Controller) </li></ul></ul><ul><ul><li>UML (Unified Modeling Language) </li></ul></ul><ul><li>Required Software for Workshop </li></ul><ul><ul><li>Visual Studio 2005 (with Framework 2.0) </li></ul></ul><ul><ul><li>MS-SQL server 2005 </li></ul></ul><ul><ul><li>Crystal Report/MS-Reporting </li></ul></ul>
  6. 6. Working Schedule Day-2 Day-3 Day-4 <ul><li>Get User Requirements </li></ul><ul><li>Analysis & Design </li></ul><ul><li>Weekly Progress Report </li></ul><ul><li>Unit Test Result </li></ul><ul><li>Problem/issues </li></ul><ul><li>(Communicate via e-mail/Wave) </li></ul><ul><li>Code Review </li></ul><ul><li>Unit Test Review </li></ul><ul><li>SIT Review </li></ul><ul><li>Project Implementation </li></ul><ul><li>User Training </li></ul><ul><li>Bug Fixed </li></ul><ul><li>Improve System </li></ul>
  7. 7. User Requirement Explanation
  8. 8. Customer Story HQ in BKK <ul><li>Assembly the F/G </li></ul><ul><li>Purchase Parts </li></ul><ul><li>Get Orders from customer </li></ul><ul><li>Send F/G to customer </li></ul>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.
  9. 9. Current Problems <ul><li>HQ in BKK can’t know Inventory On-hand on each Depot </li></ul><ul><li>Information is not CENTRALIZED! </li></ul><ul><li>Difficult to management Inventory On-hand on each Depot </li></ul><ul><li>Always stored items on wrong places </li></ul><ul><li>Difficult to find inventory item/No stored information. </li></ul><ul><li>Too slow for prepare management report </li></ul><ul><li>Overhead cost for communication between site is too much </li></ul>
  10. 10. Customer Needs <ul><li>Web-based system for share Inventory information </li></ul><ul><ul><li>Prefer to implement with ASP.NET with MS-SQL server 2005. </li></ul></ul><ul><li>Support Basic Operations </li></ul><ul><ul><li>Received Purchased Item from Vendor </li></ul></ul><ul><ul><li>Delivery Ordered item to Customer </li></ul></ul><ul><ul><li>Move Stock between Warehouse </li></ul></ul><ul><ul><li>Able to adjust stock QTY </li></ul></ul><ul><li>Required to finish within 1 month! </li></ul>
  11. 11. Our Solution Item Master Zone Master Category Goods Receiving Goods Receiving Entry Shelf-In Entry Goods Receiving List Transfer-In Entry Shipment Shipment Entry Shelf-Out Entry Shipment List Transfer-Out Entry Inventory In & Out Adjustment Supplier Customer Inventory By Category
  12. 12. Technical Requirements <ul><li>Web-Based System (ASP.NET & MS-SQL server) </li></ul><ul><ul><li>C# is preferred </li></ul></ul><ul><ul><li>Implement in MVC concept </li></ul></ul><ul><li>Required to implement ORM </li></ul><ul><ul><li>NHibernate is recommended </li></ul></ul><ul><li>Some Common Screens/Models </li></ul><ul><ul><li>Share between modules, no need to make it’s duplicated </li></ul></ul><ul><li>General Requirements </li></ul><ul><ul><li>No need to login before access the system </li></ul></ul><ul><ul><li>Provided simple main menu </li></ul></ul><ul><ul><li>Capture user’s login & Computer name from windows and stamp on transaction </li></ul></ul>
  13. 13. 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. <ul><li>Formats result set to generate report in the format specified by the User: </li></ul><ul><li>HTML </li></ul><ul><li>Comma Separated Values (CSV) </li></ul><ul><li>Adobe Portable Document Format (PDF) </li></ul>View 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 . Controller Queries data source based on input parameters specified by the User. Returns result set to the controller. Model
  14. 14. List of Function Names Supplier.aspx Supplier Data 2-5 TrfIn.aspx Transfer In Entry 2-4 Share item information from GREntry.aspx Goods Receiving Entry 2-1 Goods Receving Inventory ShelfIn.aspx Shelf-In Entry 2-2 GRList.aspx Goods Receiving List 2-3 StockAdjustment.aspx In&Out Adjustment 1-4 StockByCat.aspx ItemMaseter.aspx Category.aspx Zonemaster.aspx Page Name Share Customer/Supplier information from other modules Remark Inventory By Category 1-5 Item Master 1-3 Category 1-2 Zone Master Function Name 1-1 SEQ Inventory Module Name
  15. 15. List of Function Names (Con’t) TrfOut.aspx Transfer Out Entry 2-4 Customer.aspx ShipList.aspx ShelfOut.aspx ShipEntry.aspx Page Name Inventory Share item information from Remark Customer Data 2-5 Shipment List 3-3 Shelf-Out Entry 3-2 Shipment Entry Function Name 3-1 SEQ Shipment Module Name
  16. 16. User Requirement Specification <ul><li>Zone Master </li></ul><ul><ul><li>Zone Code </li></ul></ul><ul><ul><li>Zone Description </li></ul></ul><ul><ul><li>Shelf Structure </li></ul></ul><ul><ul><ul><li>Row, Column, Bin </li></ul></ul></ul><ul><ul><ul><li>Defined R/C/B in Zone : Start RCB – End RCB </li></ul></ul></ul><ul><li>Category Master </li></ul><ul><ul><li>Item Category Code & Description </li></ul></ul><ul><li>Item Master </li></ul><ul><ul><li>Item Code & Item Description </li></ul></ul><ul><ul><li>UoM or Unit Of Measurement (text description) </li></ul></ul><ul><ul><li>Supplier </li></ul></ul><ul><ul><li>Zone Code </li></ul></ul><ul><ul><ul><li>Row/Col/Bin (under Zone Code) </li></ul></ul></ul><ul><li>Supplier Master </li></ul><ul><ul><li>Supplier Code & Supplier Name </li></ul></ul><ul><ul><li>Supplier Short Name (for search purpose) </li></ul></ul><ul><ul><li>Address (long text is enough) </li></ul></ul><ul><ul><li>Tel.No. </li></ul></ul><ul><li>Customer Master </li></ul><ul><ul><li>Customer Code & Customer Name </li></ul></ul><ul><ul><li>Customer Short Name (for search purpose) </li></ul></ul><ul><ul><li>Address (long text is enough) </li></ul></ul><ul><ul><li>Tel.No. </li></ul></ul>
  17. 17. User Requirement Specification <ul><li>Goods Receiving Entry </li></ul><ul><ul><li>Input Supplier Code (manual input or search supplier) </li></ul></ul><ul><ul><li>Invoice No./Delivery No. (text input, following document from Supplier) </li></ul></ul><ul><ul><li>Input Receiving Date & Receiving Time </li></ul></ul><ul><ul><li>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 </li></ul></ul><ul><ul><li>[Detail, multi-lines input] </li></ul></ul><ul><ul><li>Input following these information </li></ul></ul><ul><ul><ul><li>Item Code (manual input or search item code) </li></ul></ul></ul><ul><ul><ul><li>If found input item code  Display item Description, UoM </li></ul></ul></ul><ul><ul><ul><li>Then input, serial number & QTY </li></ul></ul></ul><ul><ul><li>Press save for whole document (not save line-by-line) </li></ul></ul><ul><ul><ul><li>After save complete, need to display Transaction No for further use. </li></ul></ul></ul>(Cont’)
  18. 18. User Requirement Specification <ul><li>Shelf-In Entry </li></ul><ul><ul><li>Input Transaction No of Goods Receiving (manual input or search) </li></ul></ul><ul><ul><li>If above inputs are existing in DB, system will allow user to input location of receiving items. Else, display error message </li></ul></ul><ul><ul><li>[Detail, multi-lines input] </li></ul></ul><ul><ul><li>Input following these information </li></ul></ul><ul><ul><ul><li>Display item code, item Description, UoM, Default Zone Code, R/C/B (refer from master data) </li></ul></ul></ul><ul><ul><ul><li>Try to change Zone Code, R/C/B (if user want) </li></ul></ul></ul><ul><ul><li>Press save for whole document (not save line-by-line) </li></ul></ul><ul><ul><ul><li>Mark flag on each line to show that user has stored in shelf. </li></ul></ul></ul>(Cont’)
  19. 19. User Requirement Specification <ul><li>Goods Receiving List </li></ul><ul><ul><li>Input criteria to print </li></ul></ul><ul><ul><ul><li>Supplier Code (manual or search) </li></ul></ul></ul><ul><ul><ul><li>Period of Date (default is today date until today date) </li></ul></ul></ul><ul><ul><ul><li>Status (Just Receiving or Stored in Shelf already) </li></ul></ul></ul><ul><ul><li>Output </li></ul></ul><ul><ul><ul><li>List following data to display </li></ul></ul></ul><ul><ul><ul><ul><li>Receiving Date (1 st Group) </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Zone Code (2 nd Group) </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Supplier (3 rd Group) </li></ul></ul></ul></ul><ul><ul><ul><ul><li>R/C/B (Suppress if duplicated) </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Item Code, Description, Delivery No., Serial No, QTY, Status </li></ul></ul></ul></ul>(Cont’)
  20. 20. User Requirement Specification <ul><li>Transfer-In Entry </li></ul><ul><ul><li>Input Transaction No of Transfer-Out (manual input or search) </li></ul></ul><ul><ul><li>If above inputs are existing in DB, system will allow user to input location of receiving items. Else, display error message Output </li></ul></ul><ul><ul><li>[Detail, multi-lines input] </li></ul></ul><ul><ul><li>Input following these information </li></ul></ul><ul><ul><ul><li>Display item code, item Description, UoM, Default Zone Code, R/C/B </li></ul></ul></ul><ul><ul><ul><li>(refer from Transfer-Out Entry) </li></ul></ul></ul><ul><ul><ul><li>Try to change Zone Code, R/C/B (if user want) </li></ul></ul></ul><ul><ul><li>Press save for whole document (not save line-by-line) </li></ul></ul>(Cont’)
  21. 21. User Requirement Specification <ul><li>Shipment Entry </li></ul><ul><ul><li>Input Customer Code (manual input or search customer) </li></ul></ul><ul><ul><li>Delivery No. (text input, following document from Sales Person) </li></ul></ul><ul><ul><li>Input Shipment Date & Shipment Time </li></ul></ul><ul><ul><li>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 </li></ul></ul><ul><ul><li>[Detail, multi-lines input] </li></ul></ul><ul><ul><li>Input following these information </li></ul></ul><ul><ul><ul><li>Item Code (manual input or search item code) </li></ul></ul></ul><ul><ul><ul><li>If found input item code  Display item Description, UoM </li></ul></ul></ul><ul><ul><ul><li>Then input, serial number & QTY </li></ul></ul></ul><ul><ul><li>Press save for whole document (not save line-by-line) </li></ul></ul><ul><ul><ul><li>After save complete, need to display Transaction No for further use. </li></ul></ul></ul>(Cont’)
  22. 22. User Requirement Specification <ul><li>Shelf-Out Entry </li></ul><ul><ul><li>Input Transaction No of Shipment (manual input or search) </li></ul></ul><ul><ul><li>If above inputs are existing in DB, system will allow user to input location of receiving items. Else, display error message </li></ul></ul><ul><ul><li>[Detail, multi-lines input] </li></ul></ul><ul><ul><li>Input following these information </li></ul></ul><ul><ul><ul><li>Display item code, item Description, UoM, Default Zone Code, R/C/B (refer from master data) </li></ul></ul></ul><ul><ul><ul><li>Try to change Zone Code, R/C/B (if user want) </li></ul></ul></ul><ul><ul><li>Press save for whole document (not save line-by-line) </li></ul></ul><ul><ul><ul><li>Mark flag on each line to show that user has stored in shelf. </li></ul></ul></ul>(Cont’)
  23. 23. User Requirement Specification <ul><li>Shipment List </li></ul><ul><ul><li>Input criteria to print </li></ul></ul><ul><ul><ul><li>Customer Code (manual or search) </li></ul></ul></ul><ul><ul><ul><li>Period of Date (default is today date until today date) </li></ul></ul></ul><ul><ul><ul><li>Status (Preparation or take-out from Shelf already) </li></ul></ul></ul><ul><ul><li>Output </li></ul></ul><ul><ul><ul><li>List following data to display </li></ul></ul></ul><ul><ul><ul><ul><li>Shipment Date (1 st Group) </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Zone Code (2 nd Group) </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Customer (3 rd Group) </li></ul></ul></ul></ul><ul><ul><ul><ul><li>R/C/B (Suppress if duplicated) </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Item Code, Description, Delivery No., Serial No, QTY, Status </li></ul></ul></ul></ul>(Cont’)
  24. 24. User Requirement Specification <ul><li>Transfer-Out Entry </li></ul><ul><ul><li>Input these information </li></ul></ul><ul><ul><ul><li>Transfer-Out Date (default is today date) </li></ul></ul></ul><ul><ul><ul><li>Source : Zone Code, R/C/B </li></ul></ul></ul><ul><ul><ul><li>Destination: Zone Code, R/C/B </li></ul></ul></ul><ul><ul><li>If above inputs are existing in DB, system will allow user to transfer out QTY. Else, display error message Output </li></ul></ul><ul><ul><li>[Detail, multi-lines input] </li></ul></ul><ul><ul><li>Input following these information </li></ul></ul><ul><ul><ul><li>Display item code, item Description, UoM, Default Zone Code, R/C/B </li></ul></ul></ul><ul><ul><ul><li>Input Transfer-Out QTY </li></ul></ul></ul><ul><ul><li>Press save for whole document (not save line-by-line) </li></ul></ul><ul><ul><ul><li>Display transaction no for further use. </li></ul></ul></ul>(Cont’)
  25. 25. User Requirement Specification <ul><li>In & Out Adjustment Entry </li></ul><ul><ul><li>Input these information </li></ul></ul><ul><ul><ul><li>Item Code (manual input or search) </li></ul></ul></ul><ul><ul><ul><li>Specified period Date </li></ul></ul></ul><ul><ul><ul><li>Type: In or Out </li></ul></ul></ul><ul><ul><ul><ul><li>In : Goods Receiving or Transfer-In Operation </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Out: Shipment or Transfer-Out Operation </li></ul></ul></ul></ul><ul><ul><li>If above inputs are existing in DB, system will allow user to input new QTY. Else, display error message Output </li></ul></ul><ul><ul><li>[Detail, multi-lines input] </li></ul></ul><ul><ul><li>Input following these information </li></ul></ul><ul><ul><ul><li>Display item code, item Description, UoM, Default Zone Code, R/C/B </li></ul></ul></ul><ul><ul><ul><li>Input New QTY </li></ul></ul></ul><ul><ul><li>Press save for whole document (not save line-by-line) </li></ul></ul>(Cont’)
  26. 26. Analysis User Requirement
  27. 27. Expected Result from Analysis Phase <ul><li>Team Organization </li></ul><ul><ul><li>Tree View </li></ul></ul><ul><ul><li>Roles & Responsible </li></ul></ul><ul><li>UML diagram </li></ul><ul><ul><li>Use Case Diagram </li></ul></ul><ul><ul><li>Activities Diagram </li></ul></ul><ul><ul><li>GUI design </li></ul></ul><ul><li>Micro-Plan Schedule </li></ul><ul><ul><li>Until 9-Jan-10 </li></ul></ul>
  28. 28. Design System
  29. 29. Expected Result from Design Phase <ul><li>E-R diagram </li></ul><ul><ul><li>Table structure </li></ul></ul><ul><li>Class Diagram </li></ul><ul><ul><li>Controller </li></ul></ul><ul><ul><li>Model </li></ul></ul><ul><ul><li>View </li></ul></ul>
  30. 30. Presentation
  31. 31. Schedule for Present <ul><li>30 mins/Team </li></ul><ul><ul><li>Display overview in Analysis Phase </li></ul></ul><ul><ul><li>Submit Design document </li></ul></ul><ul><li>Q&A </li></ul><ul><ul><li>Comments </li></ul></ul>
  32. 32. Next Assignment
  33. 33. Next Assignment <ul><li>Progress report on every Friday </li></ul><ul><ul><li>Update progress in schedule </li></ul></ul><ul><li>Submit Unit Test Result every Friday </li></ul><ul><ul><li>Tested By Tools: NUnit </li></ul></ul><ul><ul><li>Manual Test: input in result form </li></ul></ul>
  34. 34. Thank you for your attention! [email_address] [email_address] www.blueballgroup.com

×