1 / 29

September 3, 2013

Project on Inventory Control System (PICS). September 3, 2013. Introduction to the Team. Project manager Mohammed Abdul Jabbar Zeeshan To distribute tasks amongst group members and record tasks allocated at the regular meetings. To provide regular feedback to supervisors and team members.

haig
Download Presentation

September 3, 2013

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Project on Inventory Control System (PICS) September 3, 2013 P.I.C.S - 2013

  2. Introduction to the Team P.I.C.S - 2013

  3. Project manager • Mohammed Abdul Jabbar Zeeshan • To distribute tasks amongst group members and record tasks allocated at the regular meetings. • To provide regular feedback to supervisors and team members. • To be available for team members to see when there is a problem within the group. • To ensure that the project keeps to the schedule. Responsibilities P.I.C.S - 2013

  4. Programmer • Chandran Johanan • Prepare programs and codes for the running the project programs. • Write the test cases earlier to avoid the errors in the programs. • Write proper program and define all codes perfectly to understand others. • Divide the task in to the programming team. • Run the program before implement it and solve the errors. Responsibilities P.I.C.S - 2013

  5. System Analyst • KanwaljeetSingh Dhaliwal • Collect the requirements from the user or clients. • Prepare well defined specifications for all the requirements. • Analyze the system properly for the project requirements. • Check that all the requirements should be met in the project. Responsibilities P.I.C.S - 2013

  6. Database Administrator • Kavitha Poola • Collect all the data needed for the project. • Manage the database system. • Define all the entities and objects for the project. • Prepare use case diagrams, ER diagrams, network diagrams for the project. • Distribute the task in to the database team. Responsibilities P.I.C.S - 2013

  7. Introduction to the client P.I.C.S - 2013

  8. Project Detail: • Creating an application in order to control the inventory system of the client “Rundle bistro bar”. • Budget: $12,000 • Time: 3 months Introduction to the Project P.I.C.S - 2013

  9. Dynamic inventory control management application. • Manage stock, order stock and request the stock • Add/delete product(s) • Update Client requirements P.I.C.S - 2013

  10. Login • View Products • Add/Remove product(s) • Place Order • Generate Invoice • Update Stock • Request Stock User requirements P.I.C.S - 2013

  11. Project name- Project on inventory control system (PICS) • Project Justification • Product Characteristics and Requirements • Project/Product Deliverables • Risk Management • Success Criteria • Assumptions Project Scope P.I.C.S - 2013

  12. Project Title:Project on inventory control system (PICS) • Project Justification: • Interactive system to order , verify and request new stock. • An application for inventory management which allows user to put entries database. • Verification and validation of stock. easy access to request the stock. Project Scope P.I.C.S - 2013

  13. Product Characteristics and Requirements: • Application with login ID at front page. • Second page, user categories selection. • Drop down list of products of category and quantity required. • Final page , item list , quantity with unique product ID. • Invoice to order required products. Project Scope P.I.C.S - 2013

  14. Risk • Absence of team members. • Lack of communication. • Conflict with client. • System failure. Project Scope P.I.C.S - 2013

  15. Success Criteria: • Weekly report. • Proper communication. • Kick off meetings. • Responsibility and help each other. • Contingency plan • Avoid absentism which leads to the failure. Project Scope P.I.C.S - 2013

  16. SPMP • WBS • Status Reports • Milestone Reports • SRS • SADD • SDD • Test Plan • Quality Assurance Plan • Risk Management Plan • Source and Object code Project Deliverables P.I.C.S - 2013

  17. Agile methodology • Active user involvement • Decisions making • Requirements evolve • Capture requirements at a high level; lightweight & visual • Incremental releases • Frequent delivery of products • Complete each feature before moving on to the next • Apply the 80/20 rule • Integrated Testing • Collaborative & cooperative approach Development Methodology P.I.C.S - 2013

  18. E-R Diagram Requirements and Architecture P.I.C.S - 2013

  19. Database Schema Requirements data dictionary P.I.C.S - 2013

  20. Story Board P.I.C.S - 2013

  21. Story Board P.I.C.S - 2013

  22. MS SQL 2008 • Visual Studio 2012 • TortoiseSVN • Araxis Merge • Ultra Edit • Enterprise Architect Tools and Technologies P.I.C.S - 2013

  23. Business Process Diagram P.I.C.S - 2013

  24. Use case Model Requirements and Architecture P.I.C.S - 2013

  25. Sequence Diagram Requirements and Architecture P.I.C.S - 2013

  26. Activity Diagram 1 Requirements and Architecture P.I.C.S - 2013

  27. Data Flow Diagram Requirements and Architecture P.I.C.S - 2013

  28. Internal review • Spell check and functionality. • IEEE Standards-Documents. • Coding • Testing • Unit testing- methods • Test case scenario – done on each module Quality Control P.I.C.S - 2013

  29. Any Questions ? Thanks for attending the Presentation Team PICS P.I.C.S - 2013

More Related