1

SOFTWARE ARCHITECTURE AND DESIGN

Final project – POST system

TEAM 3 – K15T1Hanh Luong – Leader – T095095

Hao Tran – T094442

Huy Nguyen – T094016

Hieu Le – T093798

Quang Nguyen – T094193

2

CONTENT

1. Project context and business case

2. Architectural drivers1. Key functionality

2. Quality attribute requirement

3. Business and technical constraint

3. Proposed architecture and analysis of the architectural design1. Module view

2. C&C View

3. Allocation view

4. Issue recording

5. Demo

3

PROJECT CONTEXT AND BUSINESS CASE

Reference to Architectural driver – Part I: Project description

4

ARCHITECTURAL DRIVERS

Key functionality

Overview of use case in Sale system of a retail chain using loyalty card point system

5

ARCHITECTURAL DRIVERS

Key functionality

Manage company statistic

6

ARCHITECTURAL DRIVERSQuality attribute

ID Qualityattribute

Reference to

use case

Concern Quality attribute Scenario

ID

QP Performance

UC2.1 Member manager view member list QP1

UC3.1Show member point when cashier implement payment for member by point

QP2

UC11.1 Company manager view statistic QP3

QA AvailabilityUC3.1

Cashier implement sale operation when network at 1 store is failed

QA1

UC11.1Company manager statistic revenue when 1 web server is failed

QA2

QS SecurityUC1.1

POST User log in fail 3 times within 5 minutes QS1

POST User uses 1 account to log in with many web browsers in 1 computer or many computers

QS2

UC4.12System prevents POST user access to un-assign right

QS3

7

ARCHITECTURAL DRIVERSPrioritized list of quality attribute requirement

Title: Quality attribute scenario

ID Stakeholder Priority Difficulty Ranking Comments

QP01 Low Easy No prototype

QP02 High Challenging Team does not have equipment to prototype 

QP03 High Challenging Team does not have equipment to prototype

QA01 High Challenging Prototype

QA02 High Challenging Prototype

QS01 Low Easy No prototype

QS02 Low Challenging Prototype

QS03 Low Challenging No prototype

8

ARCHITECTURAL DRIVERSQuality attribute scenario - Availability

Context: Company manager still statistic revenue by external web browser when 1 web server is failed. Response time within 3s

Title of scenario: Statistic revenue

ID: QA01

Quality attribute: Availability

Characterization ID: QA

Describe stakeholder role proposing the description: Company manager

Source(s) of the stimulus Company manager demand

Stimulus Statistic revenueRelevant environmental conditions

Degrade mode (1 web server is failed)

Architectural elements External web browser

System response Analyze data and display revenue statistic

Response measure(s) Within 3s

Associated risks If 2 web servers are failed or connection from external web browser to server is failed, result about revenue statistic will not be presented.If external network is slow, response time can be longer than 3s.

9

ARCHITECTURAL DRIVERSQuality attribute scenario - Availability

Context: When network of 1 store is failed, cashier at other store still implements sale operation normally and no downtime.

Title of scenario: Sale operation

ID: QA02

Quality attribute: Availability

Characterization ID: QA

Describe stakeholder role proposing the description: Cashier

Source(s) of the stimulus

Cashier demand

Stimulus Implement sale operation Relevant environmental conditions

Degrade mode (network of 1 store is failed)

Architectural elements Internal web browser

System response Cashier at other store still implement sale operation normallyResponse measure(s) No downtime

Associated risks If network at store is failed, all sale operation at that store will not operate.

10

ARCHITECTURAL DRIVERSQuality attribute scenario - SecurityContext: When user tries to log in the system by 1 account with many web browser in 1 computer or many computers in normal mode, the system show error message within 2s.Title of scenario: Prevent log in twice by 1 account

ID: QS02

Quality attribute: Security

Characterization ID: QS

Describe stakeholder role proposing the description: member manager, head office administrator, cashier, company manager, product manager. General name for all stakeholder: POST user

Source(s) of the stimulus POST user demand

Stimulus Log in the systemRelevant environmental conditions

Normal modePOST user log in the system by 1 account with many web browser in 1 computer or many computers

Architectural elements Internal web browser External web browser

System response Show error messageResponse measure(s) Within 2sAssociated risks If Head office’s network is failed, all access to Head office is stopped.

If external network is slow, response time can be longer than 2s.

11

ARCHITECTURAL DRIVERSBusiness constraint

Technical constraint

ID Business constraint

B1 Deploy the architecture system in 10 weeks (Draft report: June-25-2012 and Final report: July-5-2012)

B2 Human resource: 5 team members

ID Technical constraint

T1 The system consists of a head office server, located at the head office, and the POS terminals placed at store cashiers

T2 The head office server and the store are connected to each other via a network

T3 Company A decided to choose the Web solution using ASP.NET MVC 3 framework, only Web browser, no local Database needed for any POS terminal.

12

PROPOSED ARCHITECTURE AND ANALYSIS OF THE ARCHITECTURAL DESIGN

Module view

- Layered style combine with decomposition style

- Data model

C&C view

- Multi tier

Allocation view

- Deployment view

13

ISSUE RECORDING

Reference to Issue recording document

14

DEMO

15

???? ?

16

THANKS FOR YOUR LISTENING

(>_^)