Title: Project Management Plan Module

Project Title:Doctor Appointment System(Mobile App)

Course Code: CSE-434
Course Title: Software Engineering (Sessional)

Team Members

Md.Khairul Islam Piash

ID: 1804076

Md.Fahim Hossain Saikat

ID: 1804077

S.M.Rifatur Rana
ID: 1804098

Supervised By

Mir Md. Saki Kowsar

Associate Professor
Department Of Computer Science and Engineering
Chittagong University of Engineering and Technology

Moumita Sen Sarma

Lecturer
Department Of Computer Science and Engineering
Chittagong University of Engineering and Technology

Department Of Computer Science and Engineering

Chittagong University of Engineering and Technology
Bangladesh
january, 2024
 Team Members

Photo Name ID Email Contact Total CGPA

NO. Credit
Acquire
Passed d

Md. 1804076 rk0560005@gmail 140.75 3.85

01325166591
Khairul . com
Islam

Md.Fahim 1804077 fahim7174@gmail. 140.75 3.80

01723796196
Hossain com
Saikat

S.M. 1804098 smrifaturrana@ 140.75 3.75

01865284103
Rifatur gmail.com
Rana

1
Contents
1 Process Model Used: 4

2 Rationale for Choosing the Agile Model: 5

3 Risk Analysis for Hall Dining Management System (CUET): 5

4 Constraints to project implementation: 6

4.1 Schedule Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
4.2 Mitigation Strategies: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
4.3 Hardware Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
4.4 Mitigation Strategies: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
4.5 Budget Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
4.6 Mitigation Strategies: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

5 Hardware and Software Resource (Tools/Language) Requirements: 8

5.1 Hardware Requirements: . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
5.2 Software Requirements: . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

6 Project Timeline and Schedule 9

2
List of Figures
1 Agile Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1 Process Model Used:
During this project, we will use agile model during the software development process.

Communication:
To gather requirements for the software we will identify the stakeholders and communicate
with them. The stakeholders will be hall provost, manager, office staffs, students.

Quick Planning:
In this step, we will document all kinds of possible outline for our project that outlines
contain project features, timelines, risks etc.

Modeling Quick Design:

In this step, based on user requirements we will create a mockup software by defining the
user flow and their interactions.

Construction of Prototype:
A functional prototype will be developed with rapid development by focusing the user
requirements and that prototype will be tested based on user’s feedback.

Deployment, Delivery, and Feedback:

Build prototype will go to deployment, then user will give feedback on this and based on
their feedback necessary features will be added.

Communication(Iterative):
Regular updates to stakeholders on the project’s progress will be provided. Then proto-
type deployment plan will also be provided to the user so that they can interact with the
software development team at the right time.

4
 Figure 1: Agile Model

2 Rationale for Choosing the Agile Model:

Agile is an approach to project management that centers around incremental and iterative
steps to completing projects. Agile model is used when:
• It is difficult to predict in advance which software requirements will persist and which
will change. It is equally difficult to predict how customer priorities will change as
the project proceeds.

• Analysis, design, construction, and testing are not as predictable (from a planning
point of view) as we might like.
From the point of view of our hall dining management system, we considers agile model
as the software development approach. Because during the development of our soft-
ware, the requirements are not fixed that means requirements can vary with the needs of
users of that software. Agile method is useful when customer is always ready to conduct
meeting with the software team. As our hall provost, office staffs, managers and stu-
dents are sincere to give the feedback on the developed software that means face-to-face
communication between software development team and the stakeholders are possible,
so by considering this point we have choose agile model. Also for the small size of our
project we have choose agile model for the development of our software to reduce the
total development time.

3 Risk Analysis for Hall Dining Management System

(CUET):
Effective risk analysis is crucial for the success of any software development project, and
the Hall Dining Management System (HDMS) is no exception. By proactively identifying

5
and evaluating potential risks, we can prepare for potential challenges and minimize their
impact on the project’s success.
This risk analysis considers various factors, including:

• PS (Product Size): Complexity and scope of the HDMS features.

• BU (Business Impact): Potential disruption to dining operations and student satis-

faction.

• TE (Technology): Reliance on specific technologies and integration with existing

systems.

• DE (Development Environment): Factors influencing development process and test-

ing.

• TR (Technical Risks): Security vulnerabilities and other technical concerns.

In the table below, we analyze potential risks with the following impact rating:

• (Catastrophic): Severe disruption, potential system failure.

• (Critical): Significant impact on functionality, significant resource investment re-

quired.

• (Moderate): Temporary disruption, manageable effort to resolve.

• (Negligible): Minor inconvenience, minimal impact on project.

Risk Analysis
Risks Category Probability Impact
High user demand exceeding system capacity BU 40% 3
Integration issues with existing systems TE 35% 2
Data security breaches or privacy violations TR 25% 4
Insufficient training for Hall staff and users DE 30% 2
Changes in university policies regarding meal plans BU 20% 3
Software malfunctions or bugs affecting meal planning TE 30% 2

Table 1: Risk Analysis of CUET Hall Dining Management System

4 Constraints to project implementation:

4.1 Schedule Constraints
• Requirement Gathering Complexity: Understanding the diverse needs of stu-
dents, hall staff, and dining services providers necessitates thorough analysis and
potential iterations, potentially extending the development timeline.

• Integration with Existing Systems: Seamless integration with university sys-

tems (e.g., student information systems, payment gateways) may require additional
time for coordination and testing.

6
 • External Dependencies: Reliance on external vendors for hardware or software
components may introduce delays due to procurement processes or vendor availabil-
ity.

4.2 Mitigation Strategies:

• Agile Development Approach: Employ iterative development cycles to gather
feedback and refine requirements early on.

• Clear Communication Channels: Establish effective communication among

stakeholders to identify and address potential delays promptly.

• Prioritized Requirements: Focus initial development on core functionalities to

ensure a working system within essential deadlines.

• Thorough Planning and Contingency Plans: Anticipate potential delays and

create contingency plans to minimize their impact.

4.3 Hardware Constraints

• Server Capacity: Handling high user traffic during peak meal times, complex meal
planning algorithms, and data storage requirements may demand high-performance
servers with sufficient processing power and storage capacity.

• Network Infrastructure: Reliable and secure network infrastructure is crucial for

real-time data transmission, online ordering, and system updates.

• Point-of-Sale (POS) Devices: Integration with existing POS devices in dining

halls may necessitate compatibility checks and potential upgrades.

4.4 Mitigation Strategies:

• Hardware Optimization: Optimize code and database queries for efficient re-
source utilization.

• Cloud-Based Solutions: Consider cloud-based infrastructure for scalability and

flexibility, potentially reducing hardware costs and maintenance needs.

• Phased Implementation: Implement the system in phases to distribute hardware

requirements and costs over time.

4.5 Budget Constraints

• Development Costs: Software development, hardware procurement, and system
maintenance involve significant financial investments.

• Licensing Fees: Licensing fees for third-party software or services may add to the
overall cost.

• Training and Support: User training and ongoing technical support require ded-
icated resources.

7
4.6 Mitigation Strategies:
• Open-Source Solutions: Explore open-source software options to reduce licensing
costs.

• Strategic Resource Allocation: Prioritize essential features and functionalities

to optimize budget allocation.

• Partnerships and Grants: Seek funding opportunities through partnerships or

grants.

• In-House Development: Consider developing certain components in-house to re-

duce reliance on external vendors.

5 Hardware and Software Resource

(Tools/Language) Requirements:
To successfully implement our dormitory finding web app for teachers and staff, specific
hardware and software resources, as well as tools and languages, are essential. Here are
the requirements:

5.1 Hardware Requirements:

• Server Infrastructure:

– A robust server with sufficient processing power and storage to handle user
requests and database operations efficiently.
– Reliable network connectivity to ensure seamless communication between the
server and client devices

• Client Devices:

– End-user devices such as computers, laptops, tablets, and smartphones capable

of running modern web browsers.

• Development Machines:

– Developer workstations equipped with fast processors, sufficient RAM, and ad-
equate storage for coding, testing, and debugging.

5.2 Software Requirements:

• Operating System:

– Server: Linux or Windows Server for hosting the web application.

– Development Machines: Windows, macOS, or Linux for developers’ worksta-
tions.

• Web Server:

– Apache, Nginx, or another web server for hosting the web application.

8
 • Database Management System (DBMS):

– MySQL, PostgreSQL, or MongoDB for storing and retrieving data related to

dormitories and user applications.

• Programming Languages:

– Frontend: HTML, CSS, JavaScript, and a JavaScript framework/library such

as React or Vue.js for building the user interface.
– Backend: Node.js, Python (Django or Flask), or Java (Spring) for server-side
logic.

• Version Control:

– Git for version control to manage codebase changes and collaboration among
developers.

• Integrated Development Environment (IDE):

– Visual Studio Code, IntelliJ IDEA, or another suitable IDE for coding and
development.

• Frameworks and Libraries:

– Utilize relevant frameworks and libraries for backend and frontend development,
such as Express.js, Django, or Flask, and React or Vue.js.

• Security Tools:

– Implement security tools and practices to safeguard user data and the web
application from potential threats.

These hardware and software resources, along with the specified tools and languages,
are crucial for the development, deployment, and maintenance of an effective dormitory-
finding web app.

6 Project Timeline and Schedule

• Specifying requirements: 3 days

• Planning: 5 days

• Modeling: 7 days

• Code generation and testing: 15 days

9
Estimated Budget for Hall Dining Management Sys-
tem:
Estimating the budget for our Hall Dining Management Syetem involves considering
several key factors.

• Type of Software Project:

– Our Hall Dining Management Syetem constitutes a new software development

project, given its unique requirements and functionality tailored for Token Man-
agement ,meal updation and taking student feedback

• Size of Software Project:

– Categorized as a medium-sized project, Hall Dining Management Syetem in-

volves substantial functionality beyond minor tweaks. It encompasses a well-
defined scope with features such as order and cancel tokens, meal updation,
and admin evaluation. The project’s complexity lies in its ability to integrate
multiple systems, incorporate a database component, and address security con-
siderations.

• Development Team Size:

– The team size for the Hall Dining Management Syetem is crucial in budget
estimation. Typically, a project of this scale requires at least three essential
roles: a Project Manager, a Developer, and a QA Tester. However, considering
the multifaceted nature of these roles, some team members may fulfill more
than one responsibility, optimizing resource allocation.

With these factors in mind, the estimated budget for the Hall Dining Management
Syetem encompasses costs associated with development, testing, project management,
and any additional resources necessary for a successful implementation. The budgeting
process will involve a detailed breakdown of expenses, ensuring adequate coverage for
each phase of the project lifecycle.

Project Details
Type of project
The Hall Dining Management System (HDMS) project involves the development of a new,
standalone software system specifically designed to streamline and enhance dining opera-
tions within student halls. Its unique features and functionalities cater to meal planning,
ordering, payment processing, and inventory management, tailored to the specific needs
of the university’s dining services.

Size of project
The HDMS is classified as a medium-sized project due to its well-defined scope and
comprehensive set of functionalities. It encompasses features such as:

10
• Meal planning and scheduling

• Online ordering and payment processing

• Inventory tracking and management

• Dietary preference management

• Reporting and analytics

• Integration with existing systems (e.g., student information system, payment gateways)

The project’s complexity arises from its integration with multiple systems, database
management, security considerations, and the need to cater to a large and diverse user
base.

Development Team Size

The estimated development team size for the HDMS project includes the following es-
sential roles:

• Backend Developer

• Frontend Developer

• User Experience (UX) Designer

With these factors in mind, the estimated budget for the Hall Dining Management
System encompasses costs associated with development, testing, project management,
and any additional resources necessary for a successful implementation. The budgeting
process will involve a detailed breakdown of expenses, ensuring adequate coverage for
each phase of the project lifecycle.

Area Specification Area

Laptop x 2 2,40,000/=
Resource cost Other Software 3,000/=
Server 8,000/==
UI/UX Designer 10,000/=
Developer X 2 20,000/=
Developer cost
Total 30000/=

Table 2: Estimated Cost for Hall Dining Management System

Social/Cultural/Environmental impact of the project:

The development and implementation of a dormitory reservation system for teachers and
staff within a university campus can have significant social, cultural, and environmental
impacts:

11
• Social Impact

– The HDMS offers a user-friendly and efficient way for students to order meals,
reducing queues and waiting times. This ultimately leads to a more positive
and convenient dining experience for everyone.
– The system caters to diverse dietary needs and preferences through clear menu
descriptions, filtering options, and allergy notifications. This promotes inclu-
sivity and ensures everyone feels comfortable using the system. .

• Cultural Impact

– The HDMS facilitates offering healthy meal options and providing nutritional
information, potentially influencing students’ eating habits and promoting a
healthier campus lifestyle.
– Detailed information about meals, ingredients, and nutritional values provided
by the HDMS increases transparency and builds trust in the dining services.

• Environmental Impact Replacing paper-based systems with a digital platform

reduces paper waste and contributes to a more environmentally conscious operation.

12