4. Viewpoints Descriptions - Software-Design-2022/DFMPC-Student-Placement-System GitHub Wiki

Logical View

Circle - initial state

  • Rectangle - state
  • Arrow - transition between states, labeled with text
  • Circle with outer circle - termination state Composite Box on top of both diagrams represents the Login procedure:
  • Once the application is open the user would have to insert login credentials which will be communicated with the database. If the credentials inserted exist in the database then the user will be given access to the application, if not then the user will be rejected and required to try again.

App State UML drawio (1)

Student Placement System App

  • The states and transitions that follow are based on the usage of the app once the user has logged in.
  • user can move between states swiftly as indicated in the diagram after logging in with each button leading to a new state without any rejections until the user logs out.

Admin State UML drawio

Admin Website

  • The states and transitions above are based on the usage of the admin website once the admin has logged in.
  • The admin can move between states swiftly as indicated in the diagram after logging in through the usage of buttons, without rejections until the user logs out

Development View

DFMPC Component Diagram

  • The diagram above describes the implementation of our software and shows the interactions between the different components in the system. As shown in the diagram, we have our database which stores and provide data to the student applications and admin website. The student applications and admin website have the ability to create, read, update and delete data from the database once user data has been validated.

Process View

Student Placement System App

student sequence drawio

Admin Website App

admin sequence drawio

  • A diagram that explains the communication between the computer and the database/server
  • Box on top represents an object/component
  • Dotted vertical line represents the lifeline of the system
  • Blocks along lifeline represent processes
  • Solid arrows represent communications
  • Dotted arrows represent returns
  • Black circle represents initial state/access to the compute by the user
  1. Admin Sequence diagram
  • the computer has to confirm credentials with the server upon logging into the application
  • The computer can thereafter make changes to the server as the user sees fit
  • Upon requests, the server will provide responses to the computer
  1. Student App Sequence diagram -the computer has to confirm credentials with the server upon logging into the application
  • The computer can thereafter make changes to the server as the user sees fit
  • Upon requests, the server will provide responses to the computer

Physical View

DFMPC Deployment Diagram

  • The above diagram describes the physical architecture of the system and describes the relationship between software and hardware components of the system.
  • There are four components in our physical view, namely the web browser, which is used for admin access, the IOS and Android apps which will be used for student applications, and the server.

Scenarios

Use Case drawio

  • The diagram above describes the interactions between the system and its actors. We can see above that the two actors for the DFMPC Student Placement System are the student and the admin users. The admin is able to login to the website and makes changes to the database tables (users, student schedules, protocols, and events) and subsequently, make changes to the information displayed in the app. The student is able to log in, view their placement schedule, general calendar, emergency protocols, and make changes to their account settings. The student can also add their own events to the general calendar.