1. LOGO Team Assignment 1 Software Architectures

2. LOGO K15T2- Group21 Contents Introduce to Sale system 1 Architecture Drivers 2 Minimal Acceptable Delivery 3 4

3. LOGO Document 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

4. LOGO Project 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

5. LOGO Project 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

6. LOGO Project 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

7. LOGO K15T2- Group21 Contents Introduce to Sale system 1 Architecture Drivers 2 Minimal Acceptable Delivery 3 4

8. LOGO Architecture Drivers K15T2- Group21 High level functionality Requirement Entity Table Entity ID Entity Name SS.ET01 Administrator SS.ET02 Staff SS.ET03 Cashier SS.ET04 Member SS.ET05 Manager SS.ET06 Timer List of entity

9. LOGO Architecture Drivers K15T2- Group21 High level functionality Requirement

10. LOGO Architecture Drivers K15T2- Group21 High level functionality Requirement List of use case NumberUse case Name 1View detail member info 2Sales goods 3Statistics 4Batch process the sales operation 5View detail member info

11. LOGO Architecture Drivers K15T2- Group21 Use case IDUse case Name 6Add new member 7Search/view member info 8View detail member info 9Update member info 10Remove member 11Add goods 12Search/view goods info 13View detail goods info 14Update goods info 15Remove goods 16Classify goods List of use case

12. LOGO Architecture Drivers Use case IDUse case Name 17 Establish actual price 18 Add new retail store 19 Search/view retail store info 20 View detail retail store info 21 Update retail store info 22 Remove retail store 23 Add new user 24 Search/view user info 25 View detail user info 26 Update user info 27 Remove user List of use case

13. LOGO Architecture Drivers Use case detail

14. LOGO Architecture Drivers K15T2- Group21 Quality Attribute Number ID Quality attribute Stakeholder Priority Difficulty Ranking Involved use cases QA.PPerformanceHighDifficult Sales goods, Batch process the sales operation QA.AAvailabilityHighDifficult Sales goods, Batch process the sales operation QA.SSecurityMediumChallenging QA.UUsabilityMediumChallenging

15. LOGO Architecture Drivers K15T2- Group21 Quality Attribute Scenario tittle:Scenario ID:QA.P.01 Raw quality attribute description Check out performance when an order was sold Stimulus Type code ( scan code ) Source of the stimulusCashier EnvironmentNormal operation Artifact stimulatedSystem ResponseDisplay price of product Response measureResponse time: 1s

16. LOGO Architecture Drivers K15T2- Group21 Quality Attribute Scenario tittle:Scenario ID:QA.A.01 Raw quality attribute description Availability StimulusOmission – crash Source of the stimulus Head office server EnvironmentNormal operation Artifact stimulatedHead office server, POS terminals Response The POST terminals can carry out the sales operation efficiently using locally stored data as much as possible. Response measureNo down time

17. LOGO Architecture Drivers Constraint IDDescription TC.01 System will use SQL Server TC.02 System includes hardware components such as a computer and a bar code scanner, and software to run the system. K15T2- Group21 Constraint Technical Constraint Business Constraint Time : within 6 weeks Cost: unidentified

18. LOGO Architecture Drivers DifficultyImportant LowMediumHigh EasyLow Medium ChallengingLowMediumHigh DifficultMediumHigh K15T2- Group21 Prioritization

19. LOGO Architecture Drivers K15T2- Group21 Prioritization of function requirement High Function Requirement IDName Sale goods Batch process the sales operation Classify goods Establish actual price Medium Function Requirement Statistics Remove member Remove goods Remove retail store

20. LOGO K15T2- Group21 Contents Introduce to Sale system 1 Architecture Drivers 2 Minimal Acceptable Delivery 3 4

21. LOGO K15T2- Group21 Process Waterfall Model

22. LOGO K15T2- Group21 Process Reason 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

23. LOGO Roles & Responsibilities K15T2- Group21 MemberRole for this project An HaProject Manager Tho NguyenTechnical Lead Hoang TranDesigner Duc NguyenDeveloper & Tester Quyen ThoiDeveloper & Tester Tuan LaiDeveloper & Tester

24. LOGO K15T2- Group21 Project delivery and Mile stone

25. LOGO K15T2- Group21 Project delivery and Mile stone

26. LOGO K15T2- Group21 Project delivery and Mile stone

27. LOGO K15T2- Group21 Project delivery and Mile stone

28. LOGO Project delivery and Mile stone

29. LOGO K15T2- Group21 Top risk of the project IDTop 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 2Lack of human resources while doing projects. 3There 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.

30. LOGO