1. sportsgoodies.com.au

2.  Hunain Aslam - Project Manager / Programmer  Derin Mark -  Derin Mark - Programmer  Navdeep Singh-  Navdeep Singh- System Analyst  Rishu-  Rishu- Tester/QA  Mukesh-  Mukesh- Technical Writer Roles & Responsibilities

3.   Project Purpose and scope   Methodology   Tools   Cost/budget   WBS   Requirement Traceability Matrix (RTM)   ER-Diagram   DFD (Data flow diagram) Overview   Structured Chart   3-tier Architecture of your System   USE-Case diagram   Class diagram   Website Layout   Conclusion   References   Q & A

4.   The purpose of this project is to deliver an ecommerce website   Customers can create their profiles   Customers can purchase products which are to be delivered to them. Purpose

5.  Streamlined Business Processes  Easy Accessibility  World Wide Access  More Diverse Products  Global Market Scope

6.  SCRUM Methodology is used for this project.  Iterative & Incremental Approach  Client Interaction  Change in Project Development Methodology

7.  PHP  HTML  Java Script  CSS  Dreamweaver  MySQL  PhotoShop  J Query  AJAX Tools & Technologies

8. Task nameCost Requirements Analysis And Project Planning $35,000 Object and System Design$33,718 Implementing Testing$9,128 System Testing$6,000 Training and Set Up$3,000 Backup for any ongoing Change$10,000 Total: $100,000 Cost & Budgeting

9.  Work Breakdown Structure (WBS) is designed to break the project into steps and identify the project duration.  It also contains the process of Project management including  Project Initiation  Project Closure  Meetings WBS

10. Sports Goodies Requirement Gathering System Design Development Testing Deployment Sequence Diagram Traceability Matrix Activity Diagram DB Design DFD UC SRS DB Design GUI Design Web pages Design DB Interface Integration Website Testing Unit Testing Domain Creation Website Hosting Integrate Database

11.  Traceability Matrix correlates customer & functional requirements  It’s purpose is to see if the project requirements are being met  Also helps in project task planning. Traceability Matrix

12. No. Customer RequirementsForward Traceability U1Customer Registration / LoginS1 U2 Customer / Administrator uses his/her login and password to access the website S2 U3 If Customer enters a wrong Customer name and password S3 U4 To logout the webpage user need to click logout S4 U5To View in wish listS5 U6To Select the Item in Shopping CartS6 U7To CheckoutS7 U8To insert / update / Delete Shopping CartS8 U9To verify address detailsS9 U10To change or update System settingS10 U11Admin DashboardS11

13. NoFunctional RequirementsBackward Traceability S1Need to open signup page for new customerU1 S2 Existing customer can sign in by giving a username and password that they already have. U2 S3 If unable to login, Customer needs to get a message to change the password or click on forget password to get new password U3 S4After logout it need to show user logout messageU4 S5 Brows in Catalogues to add in Customer wish list and show those Designs there in wish list. U5 S6Need to add the Designs in the shopping cartU6 S7 Need to pay the amount by credit card or PayPal account information U7 S8 Admin can insert/ Update/Delete Designs from admin panel in category U8 S9Admin can create or edit/ update category from admin panelU9 S10Admin can change or update System setting from admin panelU10 S11Need to login as Admin and the Admin home page is DashboardU11 S12Cross Browser compatibility is necessary.N/A

14.   Gantt charts illustrate the start and finish dates of the terminal elements and summary elements of a project. Gantt Chart

16.  The purpose of ER Diagram is to clarify the database structure and relationship of the database entities.  It also has primary and foreign Key.  Relations can be many-to-many, one-to-one or one-to-many. ER Diagram

18.   Data flow diagram helps us in identifying the business processes.   It is a technique which gives the idea before we go through any process.   A data flow diagram tells us that how data flows through a system. DFD

20. Activity Diagram

21.  Three-tier or multi-tier architecture are often used when describing how clients connect to servers.  Presentation Layer  GUI / Front End  Business logic Layer  Development Logic  Data Access layer  Database 3 Tier

22.   Use case diagram shows a set of use cases and actors and their relationships.   Use cases represent system functionality, the requirements of the system from the user’s perspective. Use Case Diagram

24.  A class diagram is a type of static structure diagram that describes the structure of a system by showing the system's  classes  attributes  Operations / functions  and the relationships among objects. Class Diagram

26. Website layout

29.  Within Time Completion  Within Specified Budget  Client Satisfaction  Secure and bug free project  Easily Upgradeable  User Friendly  Easy to Understand & Manage Conclusion

30.   [IEEE 1074] IEEE Standard for Developing Software Life Cycle Processes, ANSI/IEEE Std. 1074-1991.   "New New Product Development Game". Harvard Business Review 86116:137–146, 1986. January 1, 1986. Retrieved Dec 10, 2013 "New New Product Development Game"   Cho, L (2009). "Adopting an Agile Culture A User Experience Team's Journey". Agile Conference: 416. doi:10.1109/AGILE.2009.76. ISBN 978-0-7695-3768-9 doi10.1109/AGILE.2009.76ISBN   Leansoftwareengineering.com". Leansoftwareengineering.com. October 27, 2007. Retrieved December 01, 2013. Leansoftwareengineering.com" Reference

31. Thank You

32. Q & A