Practical work: Practice Architectural Skills

code

1. Online functionality

Create the architecture (paper drawing) for an application. Also think of ways of testing the implementation. (put them on paper)

The application should contain a database and a server.

Functional requirements (Features):

  • Access to the functionality is restricted unless the user is logged in. In case it is denied access, or it is not logged in, a message should be displayed to him with such information.
  • The user can search for fuel, weather, and parking
  • The results are received from a 3rd party application
  • The following data should be persisted: User, password, server to log in
  • The persistent data should not be stored in clear.

Quality attributes required:

  • Performance
  • Availability

Non-Functional requirements:

  • Feedback should be provided to the user in all cases, in less than 2 seconds.

2. Upload and Security

Create the architecture (paper drawing) for an application.
Also think of ways of testing the implementation. (put them on paper)

The application should contain a database, a server, and a GUI.

Functional requirements (Features):

  • The user can log in
  • Logged users can upload files and they have personal profile that can be updated.
  • Logged users can add or remove friends
  • The uploaded files and parts of their profiles can have different security levels, meaning that they can choose what can be seen only by them, by their friends, or by everyone.
  • Everyone (even users that are not logged in) can search for the files that were uploaded by other users. They should see only the files that they are allowed to see, based on the security level selected by the uploader.

Quality attributes required:

  • Usability
  • Interoperability
  • Security
  • Scalability

Non-Functional requirements:

  • The files are limited to 100Mb per file and 1GB per user.



Leave a comment

Your email address will not be published.