- Posted By: freeproject
- Comments: 0
- Posted By: freeproject
- Comments: 0
Course Registration System Activity Diagram
This is the Activity UML diagram of Course Registration System which shows the flows between the activity of Students, Course, Syllabus, Trainers, Registration. The main activity involved in this UML Activity Diagram of Course Registration System are as follows:
- Students Activity
- Course Activity
- Syllabus Activity
- Trainers Activity
- Registration Activity
Features of the Activity UML diagram of Course Registration System
- Admin User can search Students, view description of a selected Students, add Students, update Students and delete Students.
- Its shows the activity flow of editing, adding and updating of Course
- User will be able to search and generate report of Syllabus, Trainers, Registration
- All objects such as ( Students, Course, Registration) are interlinked
- Its shows the full description and flow of Students, Trainers, Registration, Syllabus, Course
Login Activity Diagram of Course Registration System:
This is the Login Activity Diagram of Course Registration System, which shows the flows of Login Activity, where admin will be able to login using their username and password. After login user can manage all the operations on Syllabus, Students, Course, Registration, Trainers. All the pages such as Course, Registration, Trainers are secure and user can access these page after login. The diagram below helps demonstrate how the login page works in a Course Registration System. The various objects in the Registration, Syllabus, Students, Course, and Trainers page—interact over the course of the Activity, and user will not be able to access this page without verifying their identity.
- Posted By: freeproject
- Comments: 0
Course Registration System Class Diagram
Course Registration System Class Diagram describes the structure of a Course Registration System classes, their attributes, operations (or methods), and the relationships among objects. The main classes of the Course Registration System are Course, Fees, Syllabus, Students, Registrations, Trainers.
Classes of Course Registration System Class Diagram:
- Course Class : Manage all the operations of Course
- Fees Class : Manage all the operations of Fees
- Syllabus Class : Manage all the operations of Syllabus
- Students Class : Manage all the operations of Students
- Registrations Class : Manage all the operations of Registrations
- Trainers Class : Manage all the operations of Trainers
Classes and their attributes of Course Registration System Class Diagram:
- Course Attributes : course_id, course_student_id, course_registration, course_name, course_type, course_year, course_description
- Fees Attributes : fees_id, fees_amount, fees_type, fees_description
- Syllabus Attributes : syllabus_id, syllabus_course_id, syllabus_name, syllabus_type, syllabus_description
- Students Attributes : student_id, student_college_id, student_name, student_mobile, student_email, student_username, student_password, student_address
- Registrations Attributes : registration_id, registration_student_id, registration_name, registration_type, registration_number, registration_date, registration_description
- Trainers Attributes : trainer_id, trainer_course_id, trainer_name, trainer_mobile, trainer_email, trainer_username, trainer_password, trainer_address
Classes and their methods of Course Registration System Class Diagram:
- Course Methods : addCourse(), editCourse(), deleteCourse(), updateCourse(), saveCourse(), searchCourse()
- Fees Methods : addFees(), editFees(), deleteFees(), updateFees(), saveFees(), searchFees()
- Syllabus Methods : addSyllabus(), editSyllabus(), deleteSyllabus(), updateSyllabus(), saveSyllabus(), searchSyllabus()
- Students Methods : addStudents(), editStudents(), deleteStudents(), updateStudents(), saveStudents(), searchStudents()
- Registrations Methods : addRegistrations(), editRegistrations(), deleteRegistrations(), updateRegistrations(), saveRegistrations(), searchRegistrations()
- Trainers Methods : addTrainers(), editTrainers(), deleteTrainers(), updateTrainers(), saveTrainers(), searchTrainers()
Class Diagram of Course Registration System :
- Posted By: freeproject
- Comments: 0
Credit Card Approval System Component Diagram
This is a Component diagram of Credit Card Approval System which shows components, provided and required interfaces, ports, and relationships between the Limits, Credit Card, Consumer, Document and Application. This type of diagrams is used in Component-Based Development (CBD) to describe systems with Service-Oriented Architecture (SOA). Credit Card Approval System UML component diagram, describes the organization and wiring of the physical components in a system.
Components of UML Component Diagram of Credit Card Approval System:
- Limits Component
- Credit Card Component
- Consumer Component
- Document Component
- Application Component
Featues of Credit Card Approval System Component Diagram:
- You can show the models the components of Credit Card Approval System.
- Model the database schema of Credit Card Approval System
- Model the executables of an application of Credit Card Approval System
- Model the system's source code of Credit Card Approval System
- Posted By: freeproject
- Comments: 0
Credit Card Approval System ER Diagram
This ER (Entity Relationship) Diagram represents the model of Credit Card Approval System Entity. The entity-relationship diagram of Credit Card Approval System shows all the visual instrument of database tables and the relations between Application, Limits, Credit Card, Document etc. It used structure data and to define the relationships between structured data groups of Credit Card Approval System functionalities. The main entities of the Credit Card Approval System are Credit Card, Application, Consumer, Limits, Cibil Reports and Document.
Credit Card Approval System entities and their attributes :
- Credit Card Entity : Attributes of Credit Card are credit_card_id, credit_card_customer_id, credit_card_balance, credit_card_name, credit_card_type, credit_card_description
- Application Entity : Attributes of Application are application_id, application_name, application_number, application_type, application_description
- Consumer Entity : Attributes of Consumer are consumer_id, consumer_name, consumer_type, consumer_description
- Limits Entity : Attributes of Limits are limit_id, limit_balance, limit_type, limit_description
- Cibil Reports Entity : Attributes of Cibil Reports are cibil_report__id, cibil_report__score, cibil_report__type, cibil_report__description
- Document Entity : Attributes of Document are document_id, document_name, document_type, document_description
Description of Credit Card Approval System Database :
- The details of Credit Card is store into the Credit Card tables respective with all tables
- Each entity (Document, Consumer, Cibil Reports, Application, Credit Card) contains primary key and unique keys.
- The entity Consumer, Cibil Reports has binded with Credit Card, Application entities with foreign key
- There is one-to-one and one-to-many relationships available between Cibil Reports, Limits, Document, Credit Card
- All the entities Credit Card, Cibil Reports, Consumer, Document are normalized and reduce duplicacy of records
- We have implemented indexing on each tables of Credit Card Approval System tables for fast query execution.
- Posted By: freeproject
- Comments: 0
Credit Card Approval System Sequence Diagram
This is the UML sequence diagram of Credit Card Approval System which shows the interaction between the objects of Document, Credit Card, Application, Cibil Reports, Consumer. The instance of class objects involved in this UML Sequence Diagram of Credit Card Approval System are as follows:
- Document Object
- Credit Card Object
- Application Object
- Cibil Reports Object
- Consumer Object
Login Sequence Diagram of Credit Card Approval System:
This is the Login Sequence Diagram of Credit Card Approval System, where admin will be able to login in their account using their credentials. After login user can manage all the operations on Application, Document, Credit Card, Consumer, Cibil Reports. All the pages such as Credit Card, Consumer, Cibil Reports are secure and user can access these page after login. The diagram below helps demonstrate how the login page works in a Credit Card Approval System. The various objects in the Consumer, Application, Document, Credit Card, and Cibil Reports page—interact over the course of the sequence, and user will not be able to access this page without verifying their identity.
This is the UML sequence diagram of Credit Card Approval System which shows the interaction between the objects of Document, Credit Card, Application, Cibil Reports, Consumer. The instance of class objects involved in this UML Sequence Diagram of Credit Card Approval System are as follows:
- Document Object
- Credit Card Object
- Application Object
- Cibil Reports Object
- Consumer Object
- Posted By: freeproject
- Comments: 0
Credit Card Approval System Use Case Diagram
This Use Case Diagram is a graphic depiction of the interactions among the elements of Credit Card Approval System. It represents the methodology used in system analysis to identify, clarify, and organize system requirements of Credit Card Approval System. The main actors of Credit Card Approval System in this Use Case Diagram are: Super Admin, System User, Bank, Customer, who perform the different type of use cases such as Manage Credit Card, Manage Application, Manage Consumer, Manage Limits, Manage Cibil Reports, Manage Document, Manage Users and Full Credit Card Approval System Operations. Major elements of the UML use case diagram of Credit Card Approval System are shown on the picture below.
The relationships between and among the actors and the use cases of Credit Card Approval System:
- Super Admin Entity : Use cases of Super Admin are Manage Credit Card, Manage Application, Manage Consumer, Manage Limits, Manage Cibil Reports, Manage Document, Manage Users and Full Credit Card Approval System Operations
- System User Entity : Use cases of System User are Manage Credit Card, Manage Application, Manage Consumer, Manage Limits, Manage Cibil Reports, Manage Document
- Bank Entity : Use cases of Bank are Check Applications, Approve Applications, Deliver Credit Card, Check Delivery Status
- Customer Entity : Use cases of Customer are Apply for Credit Card, Check Status, Add Documents
Use Case Diagram of Credit Card Approval System :
