Online Solution for Small Shop Supervisor Phan Truong

  • Slides: 31
Download presentation
Online Solution for Small Shop Supervisor: Phan Truong Lam TEAM MEMBERS: Le Huy Bui

Online Solution for Small Shop Supervisor: Phan Truong Lam TEAM MEMBERS: Le Huy Bui Duc Manh Le Thanh Hai Pham Van Nguyen Dinh Dong

Agenda • Introduction • Project management plan • Software Requirement Specifications • Software Architecture

Agenda • Introduction • Project management plan • Software Requirement Specifications • Software Architecture Design • Testing • Summary • Demo • Q&A

Introduction q. Project information: § Project name: Online Solution for Small Shop § Project

Introduction q. Project information: § Project name: Online Solution for Small Shop § Project code: O 3 S § Project type: Website

Roles & Responsibilities § § § Supervisor: Phan Truong Lam Project Manager: Huy. L

Roles & Responsibilities § § § Supervisor: Phan Truong Lam Project Manager: Huy. L Developer & Designer team: § Huy. L § Nguyen. PV § Manh. BD § Hai. LT Test team: Nguyen. PV, Huy. L, Manh. BD Document & QA: Dong. ND, Hai. LT

Project management plan Using Waterfall Model

Project management plan Using Waterfall Model

Task Sheet

Task Sheet

Metrics Committed Actual Start Date 8 -Sep-2014 End Date 9 -Dec-2014 Duration 93 93

Metrics Committed Actual Start Date 8 -Sep-2014 End Date 9 -Dec-2014 Duration 93 93 Team member 5 5

RISK v Miscommunication v Time shortage v Design Errors v Requirement v Scope changed

RISK v Miscommunication v Time shortage v Design Errors v Requirement v Scope changed

Tools and Techniques v Programming languages: C#, HTML, CSS, Java. Script. v Software Architecture:

Tools and Techniques v Programming languages: C#, HTML, CSS, Java. Script. v Software Architecture: MVC. v Process Model: Waterfall process model. v IDEs: Visual Studio 2013. v DBMS: Microsoft access 2010. v UML Tools: Astah Professional. v Web Server: IIS 8. 0.

Functional Requirements Non-Functional Requirements Entity-Relationship Diagram

Functional Requirements Non-Functional Requirements Entity-Relationship Diagram

Functional Requirement

Functional Requirement

Use case diagram for customer

Use case diagram for customer

Use case diagram for Category management

Use case diagram for Category management

Use case diagram for Product management

Use case diagram for Product management

Use case diagram for Order management

Use case diagram for Order management

Non-Functional Requirement q Reliability Restrict error in system. q Security The system should provide

Non-Functional Requirement q Reliability Restrict error in system. q Security The system should provide methods to prevent common. Using SSL, MD 5 to encrypt transferred sensitive information. q Maintainability System will be designed high cohesive and loosely coupling to easy change and not affected to other components q Portability Support multiple screen resolutions (1024 x 768, 1366 x 788)

Entity-Relationship Diagram

Entity-Relationship Diagram

System Overview

System Overview

System Architectural Design

System Architectural Design

Component Diagram

Component Diagram

Class Diagram

Class Diagram

Sequence Diagram

Sequence Diagram

Database Design

Database Design

Testing Strategy

Testing Strategy

Testing Process

Testing Process

Test Stages Stage of test Type of test Function test Security test Unit test

Test Stages Stage of test Type of test Function test Security test Unit test Integration test System test X X

TEST CASE

TEST CASE

TEST RESULT No Module code Pass Fail Unteste d N/A Number of test cases

TEST RESULT No Module code Pass Fail Unteste d N/A Number of test cases 1 Seller Functio n 52 10 0 0 62 2 Custom er Functio n 6 2 0 0 8 3 Security Test 3 0 0 0 3 0 0 73 Total

DEMO

DEMO

Q&A

Q&A

THANK FOR LISTENING

THANK FOR LISTENING