Artefact 1

Plan driven approach

It contains 2 part:  Project Plan and Requirement specifications.

Project Plan

Introduction

It is a plan-driven approach which consists of the following: Project scope, schedule, risks, requirement, mappings and specifications. It’s an attempt to create and develop all the needs of the project and how best the features can be built. (Imani et al.,2017)

It is an online booking system for clients who wish to book an appointment of a counsellor for 7 -day psychology. The current scenario is they are taking appointments on call, so they want to make an online system through which counsellor can book their time for appointment availability, any customer can log in and book an appointment on that provided slot.  The counsellor can edit the slot of availability and customer can cancel the appointment. (McEvoy et al.,2016)

The main objective of this project is to save the time of the customer which waits in a long queue at the clinic for their turn and counsellor can manage their time by editing the availability time so that they can look after their clients in the specific time slot. The system reduces human work and more focused on the proper functioning of daily checkups of the clients. Save time for both client and counsellor. The primary constraint of this project are –

• To make the system user – friendly so that booking and cancellation of the appointment can be made accessible so older people can easily use it.
• The system should be available 24/7.
• Easily update and cancellation of the appointment.

At the first stage in the development of the system, these points should be considered in priority:

• Site designing and wireframe of the system.
• Language – JavaScript, html5, CSS.
• Login accounts for both counsellor and client.
• Booking for the appointment on the given slot and receiving the message for confirmation.
• The counsellor does time slot option.
• Testing and debugging for making the system public.

At the second stage:

• Cancellation of the appointment.
• Use of different languages for making the system more user-friendly.
• A reminder which reminds about the appointment to the client.
• Cost control of the system.
• Addition of the new functionalities which will help counsellor and clients.

Requirements

Hardware

1. Processor: At least i5 processor is required.
2. Ethernet connection (LAN) or any wireless connection (WIFI)
3. Hard Drive: Minimum 32 GB requires
4. Memory (RAM): Minimum 1 GB
5. Operating System: Windows 10.

Software:

1. Apache server.
2. Any text editor like Sublime for Coding of Html, JavaScript, CSS.
3. Database: MySQL

Team members and responsibilities

In our team there are four members:

Gantt chart

(Mohammad et al.,2016)

Work Breakdown Structure (Zecheru et al.,2016)

Risk Associated with the system.

The risk associated with the system is booking a fake appointment and then not going to the counsellor. The other risk is related to the server; if the server is not working, then no one will be able to use the system. In the project, there are four types of risk:

1. Scope risk: If change in any hardware or software required during the development of the system.
2. Scheduling risk: This will occur if the booking of appointment shows different time to client and different time to a counsellor
3. Resource issues: If any of the members of the project doesn’t support and leaves in between, then it will impact on the development of the system.
4. Technology risks: This occurs if there is any failure in the hardware or software or any update is required.

By brainstorming or Swot analysis, we can identify the risk associated with the project system. In brainstorming, all the team members come along and identify the risks. In SWOT analysis, we can identify the weakness, opportunities and threats related to the system.

Quality Assurance

Develop an organisational structure and strategies plans according to which work is carried out and we ensure a high quality of work will be done by monitoring the system and control over the development of the system.

Our quality assurance plan includes:

1. The proper definition of all the process carried out during the development of the system
2. Proper monitoring will be done on all the process to ensure that all the standards are correctly followed

.

3. The report will be made for the full system so that if any changes need to be done can be processed quickly.

Requirements

Functional requirements

1. The system should support customer booking and cancellation of the appointment.
2. The system should support counsellor appointment time and cancel an appointment.
3. The system should be able to create accounts of both counsellor and customer.
4. Customer can search for the counsellor he wants.
5. The system must send a customer confirmation message of a booked appointment.
6. Customer should be able to check the booking status from his account.
7. Customer should be able to send feedback
8. Customer can see the latest offerings of the counsellor.

Non-functional requirements

1. All the bookings are made in the secured connection.
2. The system should handle multiple logins at the same time.
3. The system must provide 24/7 hours of online service.
4. The system should support all the browsers, e.g. google chrome, internet explorer, Firefox.
5. Customer should cancel a booking before 24 hours otherwise it will be chargeable.
6. Proper data of counsellor shown to the customer.

(Holtmann et al.,2016)

Use – Case Diagram (Jacobson et al.,2016)

Customer / Client

Counsellor

Description:

Requirement Mapping

Login as Client Login as Counsellor

References

Holtmann, J., Bernijazov, R., Meyer, M., Schmelter, D., & Tschirner, C. (2016). Integrated and iterative systems engineering and software requirements engineering for technical systems. Journal of Software: Evolution and Process, 28(9), 722-743.

Imani, T., Nakano, M., & Anantatmula, V. (2017). Does a Hybrid Approach to Agile and Plan-Driven Methods Work Better for IT System Development Projects?. Development, 1(2), 3.

Jacobson, I., Spence, I., & Kerr, B. (2016). Use-Case 2.0. Queue, 14(1), 94-123.

McEvoy, D. (2016). U.S. Patent No. 9,324,083. Washington, DC: U.S. Patent and Trademark Office.

Mohammad, I., van den Broek, H., Boots, M. L., & Wong, R. (2016). U.S. Patent No. 9,336,502. Washington, DC: U.S. Patent and Trademark Office.

Zecheru, V., & Olaru, B. G. (2016). Work Breakdown Structure (WBS) in Project Management. Review of International Comparative Management/Revista de Management Comparat International, 17(1).