30
LOGO Team Assignment 1 Software Architectures

Team Assignment 1

  • Upload
    kamil

  • View
    34

  • Download
    0

Embed Size (px)

DESCRIPTION

Software Architectures. Team Assignment 1. Contents. Introduce to Sale system. 1. Architecture Drivers. 2. Minimal Acceptable Delivery. 3. 4. Document purpose. - PowerPoint PPT Presentation

Citation preview

Page 1: Team Assignment 1

LOGO

Team Assignment 1Software Architectures

Page 2: Team Assignment 1

LOGO

K15T2- Group21

Contents

Introduce to Sale system1

Architecture Drivers2

Minimal Acceptable Delivery34

Page 3: Team Assignment 1

LOGODocument purpose

The purpose of this document is to provide a more detailed description of the nature and role of the architecture drivers specification and what it will be used for in later stages

K15T2- Group21

Page 4: Team Assignment 1

LOGOProject Over view

Company A, a retail chain, has decided to develop a sales system (hereinafter, the system) in conjunction with its launch of a point service.

K15T2- Group21

Project context

Page 5: Team Assignment 1

LOGOProject Over view

In general the goal is increase check out automation, to support faster, better services and business processes. More specifically, these include: Quick checkout for the customer, Fast and accurate sales analysis, Automatic inventory control. Support better customer service.

K15T2- Group21

Goals

Page 6: Team Assignment 1

LOGOProject Over view

The system consists of a head office server, located at the head office, and the POS terminals placed at store cashiers. The head office server and the POS terminals are connected to each other via a network. Products sold at stores have bar codes attached which indicate the product codes. These bar codes can be read with bar code readers of POS terminals.

K15T2- Group21

System description

Page 7: Team Assignment 1

LOGO

K15T2- Group21

Contents

Introduce to Sale system1

Architecture Drivers2

Minimal Acceptable Delivery34

Page 8: Team Assignment 1

LOGO Architecture Drivers

K15T2- Group21

High level functionality Requirement

Entity TableEntity ID Entity Name

SS.ET01 AdministratorSS.ET02 StaffSS.ET03 CashierSS.ET04 MemberSS.ET05 ManagerSS.ET06 Timer

List of entity

Page 9: Team Assignment 1

LOGO Architecture Drivers

K15T2- Group21

High level functionality Requirement

Page 10: Team Assignment 1

LOGO Architecture Drivers

K15T2- Group21

High level functionality RequirementList of use case

Number Use case Name   1 View detail member info2 Sales goods3 Statistics4 Batch process the sales operation5 View detail member info

Page 11: Team Assignment 1

LOGO Architecture Drivers

K15T2- Group21

Use case ID Use case Name6 Add new member7 Search/view member info8 View detail member info9 Update member info10 Remove member11 Add goods12 Search/view goods info13 View detail goods info14 Update goods info15 Remove goods16 Classify goods

List of use case

Page 12: Team Assignment 1

LOGO Architecture Drivers

Use case ID Use case Name17 Establish actual price18 Add new retail store19 Search/view retail store info20 View detail retail store info21 Update retail store info22 Remove retail store23 Add new user24 Search/view user info 25 View detail user info26 Update user info27 Remove user

List of use case

Page 13: Team Assignment 1

LOGO Architecture Drivers

Use case detail

Page 14: Team Assignment 1

LOGO Architecture Drivers

K15T2- Group21

Quality AttributeNumber

IDQuality attribute Stakeholder

PriorityDifficultyRanking

Involved use cases

QA.P Performance High Difficult Sales goods, Batch

process the sales

operationQA.A Availability High Difficult Sales goods,

Batch process the

sales operation

QA.S Security Medium Challenging  QA.U Usability Medium Challenging  

Page 15: Team Assignment 1

LOGO Architecture Drivers

K15T2- Group21

Quality Attribute

Scenario tittle: Scenario ID:QA.P.01Raw quality attribute description

Check out performance when an order was sold

Stimulus Type code ( scan code )Source of the stimulus CashierEnvironment Normal operationArtifact stimulated SystemResponse Display price of productResponse measure Response time: 1s

Page 16: Team Assignment 1

LOGO Architecture Drivers

K15T2- Group21

Quality Attribute

Scenario tittle: Scenario ID:QA.A.01Raw quality attribute description

Availability

Stimulus Omission – crashSource of the stimulus

Head office server

Environment Normal operationArtifact stimulated Head office server, POS terminalsResponse The POST terminals can carry out the

sales operation efficiently using locally stored data as much as possible.

Response measure No down time

Page 17: Team Assignment 1

LOGO Architecture Drivers

Constraint ID DescriptionTC.01 System will use SQL Server

TC.02System includes hardware components such as a computer and a bar code scanner, and software to run the system.

K15T2- Group21

ConstraintTechnical Constraint

Business Constraint

Time : within 6 weeksCost: unidentified

Page 18: Team Assignment 1

LOGO Architecture Drivers

Difficulty Important

Low Medium High

Easy Low Low Medium

Challenging Low Medium High

Difficult Medium High High

K15T2- Group21

Prioritization

Page 19: Team Assignment 1

LOGO Architecture Drivers

K15T2- Group21

Prioritization of function requirement

High Function RequirementID Name  Sale goods  Batch process the sales operation  Classify goods  Establish actual price

Medium Function Requirement  Statistics  Remove member  Remove goods  Remove retail store

Page 20: Team Assignment 1

LOGO

K15T2- Group21

Contents

Introduce to Sale system1

Architecture Drivers2

Minimal Acceptable Delivery34

Page 21: Team Assignment 1

LOGO

K15T2- Group21

ProcessWaterfall Model

Page 22: Team Assignment 1

LOGO

K15T2- Group21

ProcessReason for using this methodology

Needless to mention, it is a linear model and of course, linear models are the most simple to be implemented

Easy to manage due to the rigidity of the model – each phase has specific

Works well for smaller projects where requirement are very well understood

Page 23: Team Assignment 1

LOGORoles & Responsibilities

K15T2- Group21

Member Role for this project

An Ha Project Manager

Tho Nguyen Technical Lead

Hoang Tran Designer

Duc Nguyen Developer & Tester

Quyen Thoi Developer & Tester

Tuan Lai Developer & Tester

Page 24: Team Assignment 1

LOGO

K15T2- Group21

Project delivery and Mile stone

Page 25: Team Assignment 1

LOGO

K15T2- Group21

Project delivery and Mile stone

Page 26: Team Assignment 1

LOGO

K15T2- Group21

Project delivery and Mile stone

Page 27: Team Assignment 1

LOGO

K15T2- Group21

Project delivery and Mile stone

Page 28: Team Assignment 1

LOGO Project delivery and Mile stone

Page 29: Team Assignment 1

LOGO

K15T2- Group21

Top risk of the project

ID Top risk

1 We are behind schedule, and people are not spending enough time and dependencies are not defined. We don't finish on time everything that we have planned

2 Lack of human resources while doing projects.

3 There are lots of uncertainties in estimates; Estimates might be too large, and people might not work enough hours, or people spent more time than necessary.

Page 30: Team Assignment 1

LOGO