Member Avatar for ukey.nilesh

Hi folks i am pursuing my Dual Degree(Bachelor + Masters) from Indian Institute of Technology Roorkee(India). I am quite interested in web services and planning to do a project which states as: web service enabled appointment scheduler for universities/colleges.

This scheduler may have many different functions like: given our free time slot, ask persons/professors for an appointment (main function), and many other can be included.

Now, since i am a novice in the field of web services, I don't know how to start the implementation phase. The main problem is to decide which tool to use( websphere-IBM, eclipse, netbeans)

Can someone help me with this and tell me the step wise procedure to start this project.

Thanks and Regards

  • 3 Contributors
  • 4 Replies
  • 137 Views
  • 1 Month Discussion Span
  • Latest Post Latest Post by khaleekcool

Dani AI

Generated

A concise, practical roadmap for that builds on ’s suggestion to start from requirements and existing work.

Start by choosing REST for a campus appointment scheduler unless you need SOAP for an enterprise integration requirement. For Java, Spring Boot gives the fastest path to a REST API (easy embedded server, starters and testing support) while JAX-RS (Jersey) is the standard alternative if you prefer the Java EE style. Use Maven or Gradle for dependency management and Eclipse/NetBeans/IntelliJ for development. If the university requires IBM WebSphere in production, develop locally on Tomcat/GlassFish and validate on WebSphere later. (Spring Boot: https://spring.io/projects/spring-boot)

A working step-by-step plan:

  1. Capture requirements and actors (student, faculty, admin). Define core flows: propose time, accept/decline, bulk booking, office-hours, notifications, and privacy constraints.
  2. Design API contract first (OpenAPI/Swagger). Sketch endpoints: /users, /availability, /appointments, /proposals, /notifications.
  3. Model data (Appointment: id, organizer, participants, startUtc, endUtc, status, recurrenceId, createdAt). Keep timestamps in UTC.
  4. Build a minimal backend prototype (CRUD + conflict detection). Use in-memory DB (H2) for fast iterations.
  5. Add a simple client (HTML/JS or small SPA) and a manual booking UI. Test API with Postman.
  6. Add notifications (SMTP/JavaMail) and calendar export (ICS). For calendar format reference RFC 5545.
  7. Add authentication/authorization (start with token-based, add OAuth2 when integrating with campus SSO).
  8. Write unit/integration tests, then deploy to an app server and stress-test concurrency paths.

Common pitfalls and tips: handle time zones and DST consistently (store UTC), design conflict resolution and locking for simultaneous bookings, treat recurring events as a separate complexity, and protect private data. Start with a small MVP and iterate — that delivers learning and keeps integration scope manageable. (RFC 5545: https://datatracker.ietf.org/doc/html/rfc5545)

Recommended Answers

All 4 Replies

Member Avatar for peter_budo

You should look first into available web technologies PHP/ASP/JSP find what are advantages and disadvantages for each of them plus clearly state why the "chosen one" is the right for you and after that should think about which IDE/tool you may want to use.
So do you know what you want to use and why?

Member Avatar for ukey.nilesh

Thanks Peter for replying,

I know that these technologies can help me in a much better way....
but my motive is to expertise in web services and i want to do a simple project on web services to get hands on experience in this technology,,,,if the idea dosn't seems that great to you to be implemented as web service please suggest me some other to start with,
also my main aim for staring this thread is to get an overview how to start any project using web service technology.

i think i am much clearer this time

Member Avatar for peter_budo
  1. Get pre-requirements written down, you can say this will your draft
  2. Do research on already existing projects of same or similar topic. Try to find out what are the mistakes, what was good and in total how it can be improved and why.
  3. In doing your research you want to keep an eye on which technology been used and think about it if it does satisfies the needs of the project and if it was used appropriately
  4. From collected notes draw your requirement, this may little change over the period of time while developing

It is just raw description of you should do.

Member Avatar for khaleekcool

thank you

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.