1 / 30

Team Assignment 1

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

kamil
Download Presentation

Team Assignment 1

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Software Architectures Team Assignment 1

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

  3. 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. Project Over view Project context 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

  5. 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. Goals K15T2- Group21

  6. 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. System description K15T2- Group21

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

  8. Architecture Drivers High level functionality Requirement List of entity K15T2- Group21

  9. Architecture Drivers High level functionality Requirement K15T2- Group21

  10. Architecture Drivers High level functionality Requirement List of use case K15T2- Group21

  11. Architecture Drivers List of use case K15T2- Group21

  12. Architecture Drivers List of use case

  13. Architecture Drivers Use case detail

  14. Architecture Drivers Quality Attribute K15T2- Group21

  15. Architecture Drivers Quality Attribute K15T2- Group21

  16. Architecture Drivers Quality Attribute K15T2- Group21

  17. Architecture Drivers Constraint Technical Constraint Business Constraint • Time : within 6 weeks • Cost: unidentified K15T2- Group21

  18. Architecture Drivers Prioritization K15T2- Group21

  19. Architecture Drivers Prioritization of function requirement K15T2- Group21

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

  21. Process • Waterfall Model K15T2- Group21

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

  23. Roles & Responsibilities K15T2- Group21

  24. Project delivery and Mile stone K15T2- Group21

  25. Project delivery and Mile stone K15T2- Group21

  26. Project delivery and Mile stone K15T2- Group21

  27. Project delivery and Mile stone K15T2- Group21

  28. Project delivery and Mile stone

  29. Top risk of the project K15T2- Group21

  30. Thank You !

More Related