Scribd
Upload
20 views31 pages

SE Record 2

The document outlines various diagrams and system requirements for a hostel management system, including class diagrams, activity diagrams, and use case diagrams. It highlights the problems with the existing manual system and proposes a digital solution to manage hostel records, room allocations, and student dues. Functional and non-functional requirements for the proposed system are specified to ensure reliability and performance.

Uploaded by

gpravalika2002
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
20 views31 pages

SE Record 2

The document outlines various diagrams and system requirements for a hostel management system, including class diagrams, activity diagrams, and use case diagrams. It highlights the problems with the existing manual system and proposes a digital solution to manage hostel records, room allocations, and student dues. Functional and non-functional requirements for the proposed system are specified to ensure reliability and performance.

Uploaded by

gpravalika2002
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 31

1.

Draw a class diagram for checking “ Account” class and the “ Savings accounts” class
both inherit from the more general class “Account”.

Classes in the system


Bank, Branch, Account, Savings Account, Current Account, Loan, and Customer.
Relationships
• A Bank “has–a” number of Branches − composition, one–to–many
• A Branch with role Zonal Head Office supervises other Branches − unary association,
one–to-many
• A Branch “has–a” number of accounts − aggregation, one–to–many
From the class Account, two classes have inherited, namely, Savings Account and Current
Account.
• A Customer can have one Current Account − association, one–to–one
• A Customer can have one Savings Account − association, one–to–one
• A Branch “has–a” number of Loans − aggregation, one–to–many
• A Customer can take many loans − association, one–to–many
2. Draw an Activity diagram for withdrawal of money from ATM.
3. Draw a State chart diagram for an online grading system.
4. Draw a sequence diagram for library management system.
5. Specify the problem domain, requirements for the hostel management system.

PROBLEM DEFINITION
There are a lot of drawbacks in keeping and maintaining a hostel. Especially with a
manual system. Since most hostels are being run by only one hostel manager, the number of
students in a room are sometimes not known by the officer. He has to go room by room to ensure
that a room is occupied or not. Sometimes people may be owing in the hostel and they are saved
on papers or huge notebooks, and sometimes receipts. If the books should go missing or stolen,
one would never be able to know if a student is owing or not. Room allocation also becomes a
problem as the officer might not know which rooms are available or not. And some hostels have
a lot of rooms or have many floors and it would be very tedious to go through all floors in search
of a free room for an applicant. Also the officer might not know the number of students in a
room or know if a room is full or not.

A. Existing System

The existing system is manual based and need lot of efforts and consume enough time. In
the existing system we can apply for the hostels online but the allotment processes are done
manually. It may lead to corruptions in the allocation process as well as hostel fee calculation.
The existing system does not deals with mess calculation and complaint registration.

B. Proposed System

This project is aimed at developing a system for keeping records and showing
information about or in a hostel. This system will help the hostel officer to be able to manage the
affairs of the hostel. This system will provide full information about a student in the hostel. It
will show rooms available or not and number of people in a particular room. This will also
provide information on students who have paid in full or are still owing. This system will also
provide a report on the summary detail regarding fees and bills students are owing. Also included
is a user module for employees or the hostel officer. There will also be an administrator module
which will accessed by the administrator and has the ability to delete, add and edit employee
records.
REQUIREMENT ANALYSIS

A. Functional Requirements

1. user generate account number.

2. user allow the hostel staff members or guardians to scan’s the student’s id and access its
profile.

3. user have permission of renewing the student’s registration every year.

4. user shall generate the users profile containing the following information users account
no, full name ,address, phone no & room no.

5. user will change dues status in database according to dues paid or not.

6. user will allocate rooms to students according to the session or class.

7. user must have the details of a mess of a student and stored in a database.

8. user must allow the warden to add new users to the system’s database.

9. user must allow to put hold on a room if any room is not available at the moment.

10. user must allow the guardian to cancel the registration from the system’s database who
will leave room.

B. Non-Functional Requirements

1. The system should be reliable. It should always bep and running.


2. The system should have high performance.
6. Draw a Sequence diagram for the student result computation process.
7. Draw a Class diagram for mobile app design model.
8. Give a Data flow diagram of automatic exam model.
9. Draw a Use case diagram for user online learning system.
10. Draw an Activity diagram for course registration system.
11. Draw a Use case diagram for inventory management system.
12. Draw an Object diagram for blood bank system.

13. Draw a Deployment diagram for a web application that include


NODES (application server and database server).
ARTIFACTS (application client and database schema)
14. Draw a Class diagram for railway management system.
15. Draw an Activity diagram for event management system.
16. Draw a Sequence diagram for electricity billing system.
17. Draw a Collaboration diagram for health care appointment system.
18. Draw a Component diagram for air line booking system.
19. Draw an object diagram for online teaching system.
20. Draw a Use case diagram for online line shopping.
21. Give a Data flow diagram for traffic monitoring system.
22. Explain the phases in SDLC model and give an example of Data flow diagram.
23. Draw an Interaction diagram for passport verification.
24. Draw an Activity diagram for online payment system.
25. Give a Data flow diagram for issuing a bonafide from the college.
26. Draw a Use case diagram for route planning system.
27. Draw a State chart diagram for hospital management system.
28. Draw an Object diagram for online food ordering system.
29. Draw a Class diagram for service oriented product lines implementation.
30. Draw a Sequence diagram for court case management system.

You might also like