josperrod9 / acme-toolkits Goto Github PK

Please, realise that we’re asking you to report on what you know thanks to the previous subjects, not the architecture to be taught in this subject. The structure of the contents is up to you

Instantiate and customise your starter project so that you can work on your deliverables.

Read the annexes in the Group deriverables document to do it.

A system currency, which must be “EUR” by default.
A list of accepted currencies, which must be initialised to “EUR”, “USD”, and “GBP”.
A list of strong spam terms, which must include “sex”, “hard core”, “viagra”, “cialis”, and their Spanish translations by default.
A strong spam threshold, which must be 10% by default.
A list of weak spam terms, which must include “sexy”, “nigeria", “you’ve won”, “one million”, and their corresponding Spanish translations by default.
A weak spam threshold, which must be 25% by default.

List their own toolkits.
Show their own toolkits, including their prices, their components, and their tools.

List the patronage reports associated with their patronages.
Show the patronage reports that they can list.

List their own tools.
Show their own tools.

The system must store the following data about them: a creation moment, a title (not blank, shorter than 101 characters), an author (not blank, shorter than 101 characters), a body (not blank, shorter than 256 characters), and an optional email address. The author is not required to be the name of an actual principal.

Show the system configuration.

List them grouped by project-specific role, excepting accounts that are disabled or have the anonymous or the administrator roles.
Show the identity and profiles of the user accounts that they can list, excepting the credentials and the enablement status.

Show their patron dashboards.

The system must store the following data about them: a status (proposed, accepted, or denied), a code (pattern “^[A-Z]{3}-[0-9]{3}(-[A-Z])?$”, unique), legal stuff (not blank, shorter than 256 characters), a budget (positive), a period of time (at least one month long, starting at least one month after the patronage is created), and an optional link with further information.

List the tools that have been published.
Show the details of a tool that he or she can list.

The system must store the following data about them: a code (pattern “^[A-Z]{3}-[0-9]{3}(-[A-Z])?$”, unique), title (not blank, shorter than 101 characters), description (not blank, shorter than 256 characters), assembly notes (not blank, shorter than 256 characters), and an optional link with further information. A toolkit may have several instances of the same component, but only one instance of a given tool.

The system must be internationalised in English and Spanish. Other mainstream languages are welcome, but not required.

List the chirps that are not older than one month.

average, deviation, minimum, and maximum retail price of components, grouped by technology and currency; total number of tools; average, deviation, minimum, and maximum retail price of tools, grouped by currency; total number of proposed/accepted/denied patronages; average, deviation, minimum, and maximum budget of proposed/accepted/denied patronages.

Please, realise that we’re asking you to report on what you know thanks to the previous subjects, not on the approach to testing to be taught in this subject. The structure of the contents is up to you.

Upload the "Hello-World-22.0" starter project so as to initialise the Acme One repository

The system must store the following data about them: a name (not blank, shorter than 101 characters), a code (pattern “^[A-Z]{3}-[0-9]{3}(-[A-Z])?$”, unique), a technology (not blank, shorter than 101 characters), a description (not blank, shorter than 256 characters), a retail price (positive), and an optional link with further information.

Show the administrator dashboard.

The report must have the followings reports:

• A description of how the members of your workgroup were recruited.
• For every member of your workgroup provide: contact data (surnames, names, corporate email address, and recent picture – no avatars or old pictures, please).
• A formal agreement in which you all commit to working together in this subject, declare that you have understood its syllabus, with a special emphasis on the grading procedure, and commit to achieving a particular mark.
• A formal agreement regarding how the performance of your workgroup members will be measured. The agreement must make it explicit what “performing well” and “performing badly” means.
• A formal agreement regarding how workgroup members who perform well will be rewarded.
• A formal agreement regarding how workgroup members who perform badly will be punished.
• A formal statement that describes the conditions in which a workgroup member may be fired. Recall that firing a workgroup member means that he or she will fail the subject in the corresponding evaluation call.
• The report must be dated and signed by every member of your team.

The system must store the following data about them: a creation moment (in the past), a title (not blank, shorter than 101 characters), a body (not blank, shorter than 256 characters), a flag to indicate whether they are critical or not, and an optional link with further information.

List the components that have been published.
Show the details of a component that he or she can list.

List the toolkits that that have been published.
List the toolkits that have been published and include a particular component or tool.
Show the details of the toolkits that they can list, including their prices, navigating to their components and tools, as well showing their details.

Show the information regarding the accepted currencies, and the system currency. If applicable, show information about the service used to perform money exchanges.

The system must store the following data about them: a name (not blank, shorter than 101 characters), a code (pattern “^[A-Z]{3}-[0-9]{3}(-[A-Z])?$”, unique), a technology (not blank, shorter than 101 characters), a description (not blank, shorter than 256 characters), a retail price (zero or positive), and an optional link with further information.

List the patronage reports associated with their patronages.
Show the patronage reports that they can list.

List their patronages.
Show their patronages, including the profile of the corresponding patron.

Modify the anonymous menu so that every member of your workgroup adds a sub-option that takes the browser to their favourite link. The text in the sub-options must match the following pattern: “〈id-number〉: 〈surname〉, 〈name〉”, where “〈id-number〉” denotes a workgroup member’s DNI, NIE, or passport number, “〈surname〉” denotes that member’s surname/s, and “〈name〉” denotes his or her name.

The system must store the following data about them: an automatic sequence number (not blank, matches pattern “〈patronage-code〉:〈serial-number〉”, where “〈patronage-code〉” denotes the code of corresponding patronage and “〈serial-number〉” denotes a sequential number that starts at “0001” and gets increased with every new patronage report), a creation moment (in the past), a memorandum (not blank, shorter than 256 characters), and an optional link with further information.

List the announcements that are not older than one month.
Show the details of the announcements that they can list.

total number of proposed/accepted/denied patronages; average, deviation, minimum, and maximum budget of proposed /accepted/denied patronages grouped by currency.

List their patronages.
Show their patronages, including the profile of the corresponding inventor.

Please, note that we are not asking you to reproduce the guidelines to set it up; we are asking you for a report in which you make it clear that you’ve followed the guidelines and have your develop-ment configuration ready to work. The structure of the contents is up to you.

List their own components.
Show their own components.

Read the annexes in the Group deliverables document to do it.

Inventor and/or patron (in addition to the default anonymous, authenticated, and administrator roles provided by the development framework). The project-specific roles must have a profile with the following data: a company (not blank, shorter than 101 characters), a statement (not blank, shorter than 256 characters), and an optional link with further information. The system must be delivered with an account for an administrator principal with credentials “administrator/administrator”.