Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Page 1
Page 3
Workload Matrix
Criteria Introduction Individual Component Client-Server Three-Tier Model-Control-View 33% 33% 33% 100% 33% 33% 33% 33% 33% 33% How Chee Weng Chang Tzyy Haw Yong Hong Man
100% 100%
Signature
Page 4
(Figure from ibm.com) There are 3 layers of tiers which are: Presentation tier Application tier Data tier
Page 5
Application Server
Office Database
Mail Database
User Database
Sample of above is the graphical view of 3 tiers architecture. In this architecture it is include 3 tiers which are presentation tier, application tier and data tier. From the diagram above, the presentation tier will the topmost level of application which is the Laptop and Computer. The application tier is the application server where it controls and application functionality by performing detailed processing. Last but not lease is the data tier which will be the database server. Page 6
Register
Download
Maintain
Member
rent
delete
Admin/ Staff
buy
update
Guest
Scenario Diagram The figure above has shown the basic scenario of the case study. It shows that job and ability task to perform by each of the users. The scenario diagram on above show the process and the overall story of how the system progress.
Page 7
The logical view is concerned with the functionality that the system could provide to the user. The diagram above is the logical view of diagram which using UML pattern to represent the logical view.
Page 8
Database
Respon
Register
confirm
Respon
Verify
Log in
respon
On the diagram above show one of the processes of the system which will be the register. Process view will explain how the system process and how they communicate.
Physical view
The physical view of the architecture is concerned with the topology of software components on the physical layer. The following is the steps where the process of the physical layer. 1. User Send Data using COMPUTER (presentation tier) 2. Data pass though firewall 3. Data goes is web server (Application tier) 4. Data goes to application server (Application tier) 5. Finally data will store into database.
Page 9
Online Chatsubsystem
The development view illustrates a system from a programmer's perspective and is concerned with software management. On the diagram above it will show how the sub system
integrates with the main system. On the diagram above its show that a web server needed to pass through when the main system need to integrate with its subsystem.
Page 10
Page 11
Above is an example of view of the current selected architectures, the database it will install at one of the firms bunches is it not necessary to be at a central place. In this firm, high security is high demanded due to there might have unauthorized people access to the product of this firm. Page 12
The elements in the four views are shown to work together seamlessly by the use of a small set of important scenarios instances of more general use cases. The scenarios address the overall story of the case and whole picture of the system. For example that above scenarios diagram shown that there are three users that interact with the system.
Page 13
The logical view mainly addresses the functional requirements of the system. The system is decomposed into a set of component and transforms it in object classes. For example above views have shown that there are three function of the system, able login and etc. All the function can be interact from the users.
Page 14
The process view focus on non-functional requirements, such as performance and availability. It addresses the designs concurrency and synchronization aspects of the architecture. For example the procedure of the one function that is undertaken and it wont let the user know what it happening inside. All the sub activity is executing during the function.
The physical view mainly focus on non-functional requirements of the system such as availability, reliability (fault-tolerance), performance (throughput), and scalability. It also addresses of the software onto hardware and show dynamic aspect of the system and explains the Page 15
The development architecture focuses on the actual software functions hierarchy chart on the software development environment. The software is packaged in small chunksprogram libraries, or subsystems that can be developed by one or a small number of developers. For example, it shown all the sub system have cooperate to work together as a whole system and it can serve independently without executing same with the all the system. From all the above views, it generalizes the few software criteria demanded there are: Higher security. All data is stored on the server, which generally offers a greater control of security than client machines.For example, in this system the purchasing of product need highly security in the purchasing part because it involve transaction of money and it is a big issue of this firm. The matter of gaining trust of the customer is here. Centralized data access. Because data is stored only on the server, access and updates to the data are far easier to administer than in other architectural styles. For example this firm is having one central server that everyone able to access to it, the database is install in one of the brunches in the firm.
Page 16
Database
Page 17
User Interface, the junction between a user and computer program. A good user interface design can be user-friendly and speed up the user's work. For example, user can easily and intuitions use this system without any training e.g. user can search the product information by type the keyword on the search box.
Convenient, this system is online distributed system. Therefore, user can access this online system with their smart phone, laptop or mobile table anytime thru internet. Security and privacy, this system provides member function, different user type have different permission. All personal record will be store on the online database and only authenticate user can access they record on the database. For example, in this system only registered member can purchasing product thru credit card that has high security on the payment side.
Page 18
Page 19
Login
Download trailer
View
Page 20
Client
Server
Database
View Menu
Request
Response
Send Info
Page 21
Staff
0
Updated Product Data Order Amount
Processed Order
SuperVideo System
branches
Delivery order
Page 22
Database User
Page 23
SuperVideo System
Purchase & rent <<uses>> <<uses>> <<uses>> View Member Report <<uses>>
Update catalog
Page 24
Page 25
Page 26
Page 27
(Diagram 1 from SAT lecture slide) The diagram on above has shown several steps that will be involved in SAAM. The SAAM has 6 main steps in order to complete the whole SAAM process. Step1- Develop Scenarios Step2- Describe/ explain the architecture Step3- Classify/Prioritize scenarios Step4- Individually evaluate indirect scenarios Step5- Assess Scenario interaction Step6- Create overall evaluation
Page 28
Page 29
Page 30
Page 31
Figure 2 The figure above is an example of super video business system where the evaluation of them mapped into a table with categorized of direct and indirect.
Page 32
Page 33
Page 34
This assignment will follow the step in ARID will used to evaluate the SuperVideo System
Step 1-Identify Reviewers
In this step we had to identify the stakeholders or reviewer of the system. Such as the software engineers, programmers, database administrator, manager. Stakeholders/ Reviewer Software Engineers/ Programmers Task Development the database and SuperVideo System. Database Administrator Deal with the database system. Who need to be involved in and to judge the reviews Manager In charge in the system, there need to understand what is the system do and done.
Page 35
Designer had to prepare a brief explanation of the SuperVideo System to all the reviewers, and gather all the information of the system by illustrated context diagram of the SuperVideo System to increase the understanding from every one of the reviewers. After gathered all the information, presenter will do a small questioning session to the reviewers, by asking all types of question to the reviewers. Below was the diagram that prepares for the presentation:
Page 36
This scenario will be used to illustrate the work of the system, from the scenarios so that the stakeholder will get a better understand how the system works. Scenarios: Several of Customer and member are using the system for downloading product, rent / purchasing product. Each time the service is provided to the Customer/Member, once the product is not available then it will notify to the client.
Step 4- Prepare for the review meeting
Prepare all the details and information relate to the presentation, example like hardcopy about the Agenda of meeting, seed scenarios, system detail and other relate information. Below show the example of list of participants and Agenda of meeting. List of participants: No: 1. 2. 3. 4. 5. 7. 8. Name: James Lee Albert Chua Vincent Leong Jennifer Nick Chua Justin Ng Jess Chan Position: Software Engineer Database Administrator Software Engineer Database Administrator Manager Conversion System Developer Conversion System Developer
Page 37
10.40
11.10 11.30
12.00 12.30
The review facilitators briefly explain the steps of ARID to the participants. Briefly explain how the conversion system architecture evaluation process works with the step of ARID method. Let the participants understanding the flow of meeting.
Step 6- Present Design
Presenter presents the detail of the distribution system that had prepared earlier to the participants. Presenter had to explain about the conversion system in this section to the participants. The presentation covers on the conversion system architecture where includes what is the system, why using this system, how the system works and etc. After this section, the participants should clearly understand the architecture of the system.
Page 38
In this section, stakeholders had to brainstorm the systems architecture, discuss with other people about the system base on their opinion. There need to brainstorm the question or some scenarios for the design, example like which part the system most important, like performance part or security part. Think about the system which part can do the improvement, weakness of the system, or adding new feature inside the system and etc to make a better system and together solve the problem of the system. Below show a scenario that stakeholder brainstorm during the section: Several of Customer and member are using the system for downloading product, rent / purchasing product. Each time the service is provided to the Customer/Member, the speed of system is reduce. Therefore have to limit the number of Customer/Member login to the system implementing the FIFO concept.
Step 8- Perform review
This section all participants need to review back the first scenario till the end. Thru all the step of ARID method and scenarios to gather all information and detail of the system, then finalize the system and get the final design of the conversion system. In the brainstorm section, some stakeholders have some arguments but in the end they have decide to do the changing of the system. That is the final review of the system thru the meeting end.
Step 9 Present Conclusions
At the end, from going through the step of the ARID method, the list of issues with the conversion system architecture is recounted, the participants shared their opinion and thru efficacy of the discussion section and they are thanked for their participation in the meeting.
Page 39
Phase 2: Investigation and Analysis 4. Identify architectural approaches 5. Generate quality attribute utility tree 6. Analyze architectural approaches
Phase 3: Testing 7. Brainstorm and prioritize scenarios 8. Analyze architectural approaches 9. Reporting
Page 40
Page 41
For the example with the case study of super video business system, this system is used to sell and rents videos, music, and games. So for the functional requirements on this system, this system needs a database to record the data which member purchase or rent the videos, music, and games. The stakeholders are the register member, product owner and the SuperVideo owner. Functional requirements are the proclamations of services the system should deliver. It includes how the system should react to particular inputs and how the system should behave in particular situations. (Sommerville, 2007). The functional requirements of the system for SuperVideo are listed as below: 1. An online portal which shall allow customers to view product info, purchase product that available on SuperVideo. Information of the product will be displayed in the online portal to allow customer choose and compare. Customer also can view or try the trailer when they interest about that product. 2. Customers purchase detail shall be saving in the database. Detail of the purchase record will be store in online database after customer purchase the related product. 3. Monthly report shall be generated by the system. A report that generated by the system will list out the monthly sales. Page 42
Page 43
Page 44
Database
As the diagram show, the product record and register member detail will be store on the database. This system is the web application system so users only can access by internet. When user request download the trailer from SuperVideo system, the controller will request the model to get it from database after this, system sends the trailer to the user.
Page 45
(M,L)Update new product Modifiability New product categories (L,M)comment of the product Change COTS
Utility
Availability
Hardware failure
(H,M) Credit card transcation are secure all the time Client database authorizzation work 99% of the time
Data confidentiality
Scenario of SuperVideo 1. A manager requests a database report via the Web during peak period and receives it no more than 10 seconds. 2. Detail of purchase record should encrypt when store on database. 3. Half of the servers go down during normal operation without effecting overall system availability.
Page 46
Page 47
Page 48
Page 49
Page 50
Students Names 1 2 3 Yong Hong Man Chang Tzyy Haw How Chee Weng
Students Signature
Student 1- Yong Hong Man: Criteria Presentation of Software Architecture 20 marks Discussion on Evaluation Criteria 20 marks Individual Total TOTAL (Individual + Group) Marks awarded Comment
Student 2 - Chang Tzyy Haw: Criteria Presentation of Software Architecture 20 marks Discussion on Evaluation Criteria 20 marks Individual Total TOTAL (Individual + Group) Marks awarded Comment
Page 51
Marks given
Comments
Page 52