Scribd
Upload
16 views2 pages

6.1 Conclusions

Uploaded by

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

6.1 Conclusions

Uploaded by

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

6.

1 Conclusions

As we come to end of our system development, it is time to reiterate the work previouslyhave been
done and check against our success indicators set at the beginning of the project to determine whether
the endeavor was a success. The project began by laying out the foundation that dictates the
development process. Thisinvolved defining the system development methodology, identifying resource
requirements,and setting the project schedule.We performed requirements analysis to discover the
needs of the new solution to proposed system. This phase consists of drawing out functional and non-
function requirements of thesystem. And then we performed object oriented analysis and object
oriented design.In analysis, we tried to model the new and proposed system using UML diagrams: use
casediagrams, sequence diagrams, Class diagrams, Activity diagrams. Domain modeling washandled
using Class Responsibility Collaboration (CRC) model, while we gave a sneakpreview of what
the new system might look and feel with our user interface design anddocumentation.In design
phase, we extended our work in analysis with more models. The class typearchitecture,
Class diagrams in analysis were extended in design to step closer toimplementation, while
deployment and component diagrams were also drawn. We also usedpersistence modeling to have a
feel of the database that would accompany the system.A dawn side to this project was probably the
persistence modeling we did not manage toundergo due to time constraint. Still we are limited to
persistence model was carried with realdata obtained partially, in addition from the general overview
of other institute spatiallypersonnel information providing limited source from what we are required

atot view web based hotel management system Our development team believes that we have at large
accomplished what we set out for in thebeginning of this project. We set to develop a working system
prototype that would solve theproblems in the beginning of our project. But before winding up, we
would like to give ourfinal word on how to go from here by recommending further improvement that
could bemade in the future.

6.2 Recommendations

Having seen the problem encountered in using the old system of hotel management system, we suggest
that this web based Atot Hotel Management System be adopted in Hotels and staff that will be handling
this software package be given training on computer based on how to use the new system.From the
various facts that constitute the project, the following recommendations have come tolight:

• User must have a basic knowledge of computer.

• User must have a basic first hand experience with web based systems.

• User must have a basic skill on how to use browser soft ware.

• Training user should be considering for best performance and efficiency of technology.

•Organization should have adequate computer facilities for the introduction of the newsystem.

•Behavioral change of the users of the system to adapt the new system.
References

1. (n.d.). Retrieved from www.businessdictionary.com.

2. Agile. (n.d.). http://agilemodeling.com/artifacts/uiPrototype.htm. Retrieved 02 3, 20019, from


http://agilemodeling.com/artifacts/uiPrototype.htm.

3. google.com. (n.d.). Retrieved from www.google.com.

4. hotel management study course. (n.d.). education.com.

5. https:\www.google.come. (n.d.). Retrieved from www.google.com.

6. Lausen.s. (2003). IEEE Computer Society,functional requirement.

7. louw, D. (2006 may 10). Description with UML for hotel reservation system.

8. Louw, D. (2006). UML for hotel management system.

9. http://www.liacs.nl/assets/abchelorscripties/2006-08JanneLouw.pdf.

10. http://www.itu.dk/~slauesen/Papers/IEEEtasks.pdf

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy