Software Architectural Design & Evaluation
Table of Contents
Software Architectural Design & Evaluation 1
1 Introduction 3
2 Design part 6
2.1 Object-Oriented Architectural Style: Alaa Alqallaf (10079858) 7
2.2 WWW Client-Server: Brazilo Gonsalves (10071310) 11
2.3 Main program and subroutine: Nadine Robb (10026063) 16
2.4 Pipe-and-filter: Naveed Sabir (08075782): 19
3 Evaluation part 20
3.1 Object-Oriented Architectural Style: 21
3.2 WWW Client-Server: 23
3.3 Main program and subroutine: 25
3.4 Pipe-and-filter: Evaluated by ( Naveed Sabir) 27
4 Overall Evaluation 28
1 Introduction
Design problem definition:
- The problem which is needed to be designed in this project is all about design software for a petrol filling station. There will be two software needed to be designed; software system running on the computers of the pumps and the cashier’s consoles to process the transactions. However, we can optionally add third software the server computer.
- Functional requirements:
• Requirements for pumps:
1. The pumps should provide a facility to display the type of the fuel, which is used by customer (Diesel/Unleaded). (high quality) 2. The pumps should provide the volume of the specific used fuel. (high quality) 3. The pumps should calculate the amount to be paid. (high quality) 4. The pumps should display the amount to be paid. (high quality) 5. The pumps should send a record to the cashiers’ console, which contains details (pump identity, fuels’ type, fuels’ volume, amount of money to be paid). (high quality) 6. The pump must be initialised after paying the amount. (low quality) • Requirements for console: 1. The console should contain a display screen, keyboard, credit card reader and receipt printer. (high quality) 2. More than one cashiers’ console may be provided. (medium quality) 3. If there is more than one cashier, then the customer can
Software Architectural Design & Evaluation 1
1 Introduction 3
2 Design part 6
2.1 Object-Oriented Architectural Style: Alaa Alqallaf (10079858) 7
2.2 WWW Client-Server: Brazilo Gonsalves (10071310) 11
2.3 Main program and subroutine: Nadine Robb (10026063) 16
2.4 Pipe-and-filter: Naveed Sabir (08075782): 19
3 Evaluation part 20
3.1 Object-Oriented Architectural Style: 21
3.2 WWW Client-Server: 23
3.3 Main program and subroutine: 25
3.4 Pipe-and-filter: Evaluated by ( Naveed Sabir) 27
4 Overall Evaluation 28
1 Introduction
Design problem definition:
- The problem which is needed to be designed in this project is all about design software for a petrol filling station. There will be two software needed to be designed; software system running on the computers of the pumps and the cashier’s consoles to process the transactions. However, we can optionally add third software the server computer.
- Functional requirements:
• Requirements for pumps:
1. The pumps should provide a facility to display the type of the fuel, which is used by customer (Diesel/Unleaded). (high quality) 2. The pumps should provide the volume of the specific used fuel. (high quality) 3. The pumps should calculate the amount to be paid. (high quality) 4. The pumps should display the amount to be paid. (high quality) 5. The pumps should send a record to the cashiers’ console, which contains details (pump identity, fuels’ type, fuels’ volume, amount of money to be paid). (high quality) 6. The pump must be initialised after paying the amount. (low quality) • Requirements for console: 1. The console should contain a display screen, keyboard, credit card reader and receipt printer. (high quality) 2. More than one cashiers’ console may be provided. (medium quality) 3. If there is more than one cashier, then the customer can