1. Define what Continuous build and integration systems mean.2. Describe what a continuous build and integration system would look like for the management system provided in the class diagram below. You should cover :What systems need to be set up?How users (developers) of the system would interact with them? andWhat the outputs would look like ? The image displays a UML class diagram for a parking management system. It consists of several interconnected classes, each representing different components of the system. Here’s a detailed breakdown:### Classes and Attributes:1. **ParkingOffice** - **Attributes:** - `parkingOfficeName: String` - `listOfCustomers: List` - `listOfParkingLots: List` - `parkingOfficeAddress: Address` - **Methods:** - `getParkingOfficeName(): String` - `register(Customer): void` - `register(Car): ParkingPermit` - `park(Date, ParkingPermit, ParkingLot): ParkingTransaction` - `getParkingCharges(ParkingPermit): Money` - `getParkingCharges(Customer): Money`2. **ParkingLot** - **Attributes:** - `id: String` - `name: String` - `address: Address` - **Methods:** - `getDailyRate(CarType): Money`3. **Customer** - **Attributes:** - `id: String` - `firstName: String` - `lastName: String` - `phoneNumber: String` - `address: Address` - **Methods:** - `getCustomerName(): String`4. **Car** - **Attributes:** - `type: CarType` - `licensePlate: String` - `owner: Customer` - **Methods:** - `getType(): CarType` - `getLicensePlate(): String` - `getOwner(): Customer`5. **ParkingPermit** - **Attributes:** - `id: String` - `car: Car` - `expiration: Date` - **Methods:** - `getCar(): Car`6. **ParkingTransaction** - **Attributes:** - `date: Date` - `permit: ParkingPermit` - `parkingLot: ParkingLot` - `chargedAmount: Money` - **Methods:** - `getChargedAmount(): Money` - `getPermit(): ParkingPermit`7. **TransactionManager** - **Attributes:** - `transactions: List` - **Methods:** - `park(Date, ParkingPermit, ParkingLot): ParkingTransaction

Answered: 1. Define what Continuous build and…

Database System Concepts

7th Edition

ISBN:9780078022159

Author:Abraham Silberschatz Professor, Henry F. Korth, S. Sudarshan

Publisher:Abraham Silberschatz Professor, Henry F. Korth, S. Sudarshan

Chapter1: Introduction

Section: Chapter Questions

Problem 1PE

See similar textbooks

Related questions

Concept explainers

Question

1. Define what Continuous build and integration systems mean.

2. Describe what a continuous build and integration system would look like for the management system provided in the class diagram below. You should cover :

- What systems need to be set up?
- How users (developers) of the system would interact with them? and
- What the outputs would look like ?

The image displays a UML class diagram for a parking management system. It consists of several interconnected classes, each representing different components of the system. Here’s a detailed breakdown:

### Classes and Attributes:

1. **ParkingOffice**
- **Attributes:**
- `parkingOfficeName: String`
- `listOfCustomers: List<Customer>`
- `listOfParkingLots: List<ParkingLot>`
- `parkingOfficeAddress: Address`
- **Methods:**
- `getParkingOfficeName(): String`
- `register(Customer): void`
- `register(Car): ParkingPermit`
- `park(Date, ParkingPermit, ParkingLot): ParkingTransaction`
- `getParkingCharges(ParkingPermit): Money`
- `getParkingCharges(Customer): Money`

2. **ParkingLot**
- **Attributes:**
- `id: String`
- `name: String`
- `address: Address`
- **Methods:**
- `getDailyRate(CarType): Money`

3. **Customer**
- **Attributes:**
- `id: String`
- `firstName: String`
- `lastName: String`
- `phoneNumber: String`
- `address: Address`
- **Methods:**
- `getCustomerName(): String`

4. **Car**
- **Attributes:**
- `type: CarType`
- `licensePlate: String`
- `owner: Customer`
- **Methods:**
- `getType(): CarType`
- `getLicensePlate(): String`
- `getOwner(): Customer`

5. **ParkingPermit**
- **Attributes:**
- `id: String`
- `car: Car`
- `expiration: Date`
- **Methods:**
- `getCar(): Car`

6. **ParkingTransaction**
- **Attributes:**
- `date: Date`
- `permit: ParkingPermit`
- `parkingLot: ParkingLot`
- `chargedAmount: Money`
- **Methods:**
- `getChargedAmount(): Money`
- `getPermit(): ParkingPermit`

7. **TransactionManager**
- **Attributes:**
- `transactions: List<ParkingTransaction>`
- **Methods:**
- `park(Date, ParkingPermit, ParkingLot): ParkingTransaction

Expert Solution

Continuous Development and Integration

Continuous Development and integration means that the developers have to integrate the code into a single shared repository multiple times in a day. Then the each check-in is verified through an automated build which allows the team members to counter or detect a problem early.

The main reason to use integration is to find errors easily and locate them quickly. Continuous Integration doesn't help to get rid of bugs, but it makes it way more easy to detect and eliminate them.

Trending now

This is a popular solution!

Step by step

Solved in 2 steps

SEE SOLUTION Check out a sample Q&A here

Knowledge Booster

Learn more about

Need a deep-dive on the concept behind this application? Look no further. Learn more about this topic, computer-science and related others by exploring similar questions and additional content below.

Similar questions