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

2. Introduction to the Team Name Duty ContactE-mail Mohammed Abdul Jabbar Zeeshan Project Manager / Technical Head +61 410793218majabbarzeeshan@yahoo.com Chandran Johanan Programmer / Design Architect +61 450614011chandranjohanan@gmail.com Kanwaljeetsingh Dhaliwal System Analyst / Quality Analyst +61 450452488Kanwaljeet14@gmail.com Kavitha PoolaRisk Manager / Database Administrator +61 432432849Kavitha.poola@gmail.com P.I.C.S - 2013

3. Responsibilities 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. P.I.C.S - 2013

4. Responsibilities 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. P.I.C.S - 2013

5. Responsibilities System Analyst Kanwaljeet Singh 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. P.I.C.S - 2013

6. Responsibilities 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. P.I.C.S - 2013

7. Introduction to the client RoleNamePhoneE-mail Sponsor Michael Forth61410793218Michael_Fourth@yahoo.com ClientJake Robinson61455442392Jake_Robinson@yahoo.com. Project SupervisorKT Lau61421122628ktlau@tafesa.com.au P.I.C.S - 2013

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

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

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

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

12. Project Scope 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. P.I.C.S - 2013

13. Project Scope 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. P.I.C.S - 2013

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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