Hotel management system

Index

1. Introduction:

– About the system /project

– Is it a web based (on a desktop).

– need for the System

– Functionalities only write briefly (Login register a customer)

2. USE-Case Diagram

-Prepare a use-case diagram for the topic chosen, which shows the interactions between the actor(s) and the system. Use–case diagram should have minimum 5 cases. Identify include and extend relationship between the use cases.

3. USE-Case Specification

– Use case specification defines information that pertains to a particular use case which is important in understanding the purpose behind the use case. Use case specification is written for every use case. A use case specification has one or more flow of events or pathways association with it.

Use case Specification should contain the following

3.1. Use-case:

-Use case name:

-Text description (a few sentences)

-Actors:

-Preconditions (if applicable)

-Flow of Events:

-Basic path:

o First step

o Second step

-Alternative Paths:

o Name and short description (in words) of first alternative path/scenario.

o Name and short description (in words) of 2nd alternative path/scenario.

-Post conditions (if applicable)

3.2. Use-case:

-Use case name:

-Text description (a few sentences)

-Actors:

-Preconditions (if applicable)

-Flow of Events:

-Basic path:

o First step

o Second step

-Alternative Paths:

o Name and short description (in words) of first alternative path/scenario.

o Name and short description (in words) of 2nd alternative path/scenario.

-Post conditions (if applicable)

3.3. Use-case:

-Use case name:

-Text description (a few sentences)

-Actors:

-Preconditions (if applicable)

-Flow of Events:

-Basic path:

o First step

o Second step

-Alternative Paths:

o Name and short description (in words) of first alternative path/scenario.

o Name and short description (in words) of 2nd alternative path/scenario.

-Post conditions (if applicable)

3.4. Use-case

-Use case name:

-Text description (a few sentences)

-Actors:

-Preconditions (if applicable)

-Flow of Events:

-Basic path:

o First step

o Second step

-Alternative Paths:

o Name and short description (in words) of first alternative path/scenario.

o Name and short description (in words) of 2nd alternative path/scenario.

-Post conditions (if applicable)

3.5. Use-case:

-Use case name:

-Text description (a few sentences)

-Actors:

-Preconditions (if applicable)

-Flow of Events:

-Basic path:

o First step

o Second step

-Alternative Paths:

o Name and short description (in words) of first alternative path/scenario.

o Name and short description (in words) of 2nd alternative path/scenario.

-Post conditions (if applicable)

3.6. Use-case:

-Use case name:

-Text description (a few sentences)

-Actors:

-Preconditions (if applicable)

-Flow of Events:

-Basic path:

o First step

o Second step

-Alternative Paths:

o Name and short description (in words) of first alternative path/scenario.

o Name and short description (in words) of 2nd alternative path/scenario.

-Post conditions (if applicable)

3.7. Use-case:

-Use case name:

-Text description (a few sentences)

-Actors:

-Preconditions (if applicable)

-Flow of Events:

-Basic path:

o First step

o Second step

-Alternative Paths:

o Name and short description (in words) of first alternative path/scenario.

o Name and short description (in words) of 2nd alternative path/scenario.

-Post conditions (if applicable)

3.8. Use-case:

-Use case name:

-Text description (a few sentences)

-Actors:

-Preconditions (if applicable)

-Flow of Events:

-Basic path:

o First step

o Second step

-Alternative Paths:

o Name and short description (in words) of first alternative path/scenario.

o Name and short description (in words) of 2nd alternative path/scenario.

-Post conditions (if applicable)

4. Class-diagram

  • The class diagram should consist of 7 to 8 classes.
  • Identify attributes and methods for each of the classes.
  • Visibilities such as private, default, protected and public should be added.
  • Identify the following relationships between the classes:
  • o Plain association with multiplicities with respective role name and association name

    o Self-association with multiplicities with respective role name and association name

    o Aggregation with multiplicities with respective role name and association name

    o Composition with multiplicities with respective role name and association name

    o Generalization

    o Dependency

    5. Glossary

    Following are the keys words used in the whole report:-

    6. Conclusion

    Detailed write-up on self-learning from the study undertaken.

    7. Reference (I need 7 or 8)

    “Order a similar paper and get 15% discount on your first order with us
    Use the following coupon
    “FIRST15”

    Order Now