Principles of Software Engineering: System Design Project

This assignment is a software engineering project focused on designing a digital information management system for Hastings Dental Care. It encompasses the creation of key UML diagrams, including a use case diagram illustrating the interactions of various actors (administrator, staff, patients, managers) with the system, a class diagram detailing the system's classes, attributes, and relationships, and a sequence diagram modeling the functional requirements. The project also includes a discussion of the chosen Software Development Life Cycle (SDLC) methodology, along with a critical reflection on the security, ethical, professional, legal, and social issues related to the design and development of the system. The diagrams are created based on the case study provided, demonstrating the system's functional and non-functional requirements effectively. The new digital system is designed to replace an existing manual system, automating processes like appointment booking, resource management, and patient data handling. The goal is to create a user-friendly system accessible to both patients and staff, allowing them to easily manage appointments and patient information.

PRINCIPLES OF SOFTWARE
ENGINEERING

TABLE OF CONTENTS
INTRODUCTION...........................................................................................................................1
PART A: COMPONENT 1: Software design.................................................................................1
Use case diagram.........................................................................................................................2
Class Diagram..............................................................................................................................5
Sequence diagram to model functional requirements..................................................................8
Task Reflection and Critical Evaluation..........................................................................................9
Discuss about the Software development life cycle methodology that have chosen for solution
in development with example......................................................................................................9
Critically Reflect the security and ethical issues, professional, legal and social related to the
design and development............................................................................................................12
CONCLUSION..............................................................................................................................14
REFERENCES..............................................................................................................................15

INTRODUCTION
Software engineering is one of the main core sub-branch of computer science
engineering. It is a kind of systematic application of different approaches of engineering that are
basically used in development of a software. In order to develop a good quality software without
any issues there are various principles of software engineering that are required to be adhered by
the software engineers (Tsui, Karam and Bernal, 2016). These principles help in developing an
effective system and remove any kind of issue, error or repetitive data or functionality. This
assignment will lay emphasis on various software engineering theories, demonstrate ability to
apply software engineering knowledge to complex projects such as use case diagram, use case
description, class diagram, sequence diagram. Other than this, in this assignment reflection on
professional, legal, social, security and ethical issues related to the design and development of
the software, critical discussion on Software Development Life Cycle (SDLC) methodology that
has been chosen for the developed solution. All the diagrams (use case diagram, sequence
diagram and class diagram) are made on the basis of the provided case study in such a manner
that all the functional and non-functional requirements of the system are demonstrated within the
diagram in an accurate and appropriate manner.
This assignment will also lay emphasis on a Hastings Dental Care House who has
recently built a new Central Dental Care House but now are focusing on building a New digital
information management system that would be replacing the old system in which all the data
recording, searching and updating are done mostly manually using Microsoft Word processing
package. The new system will be effective enough to record and support booking, deleting,
updating appointments, managing, and organising the use of business resources, logistics and
facilities automatically. The new system that would be build will be easy and effective enough
such that all the patients can book appointments for themselves or their family members using
new system online and the staff members will be able to update details easily. All the three
diagrams will help in explaining the main requirements and functionalities of the new system.
PART A: COMPONENT 1: Software design
Software solution development
New digital information management system for Hastings dental care house.
1

Use case diagram
Use case diagram can be defined as a simplest form of diagram that helps in representing
All the users of the system and their interaction with the system and in order to show this
relationship all the users of the system are shown in the form of an actor and functionalities are
shown in the form of use cases (Khurana, Chhillar and Chhillar, 2016). It is one of the most
important aspect or required diagram of the system which helps in capturing dynamic behaviour
of the system i.e. behaviour of the system when it is being operated or is running. Other than this
it also helps in dividing all functionalities according to the users of those functionalities. It is
important for development of the system because only static view of the diagram is not sufficient
for development of a system. So, it can be said that it is used to model the entire system and its
functionalities. Use case diagram is used for various purposes such as:
 Use to gather main requirements of the system that will be used by different users of the
system.
 Used to gather an outer view of the main system or it can also be said as dynamic view
(Sabharwal, Kaur and Sibal, 2017).
 Also helps in identification of all kinds of external and internal factors that can influence a
system.
 Lastly, it helps in showing interactions among all the user actors and the system
requirements.
Here, Use Case diagram of Hastings dental care house has been developed who are
planning to develop a new digital information management system that will be used by
administrator, staff members, patients and managers. Each of them has their own requirements.
Like, Patients of the dental care house will be using the system to book appointments, make
enquiries, request changes, request for special facilities, make payments or cancel appointments.
Managers of the system will be using it for organizing and updating logistics. Doctors will be
using the system to view patient details or history and cancel appointments. Whereas the main
use of the system will be done by the administrator staff. They will be the one who will register
new patients and update their information, Update staff members details, check slot availability,
book or cancel appointments, manage or track booking, check for special arrangements, deposit
fees for appointments etc. The main use case of this scenario is provided below:
2

Figure 1 Use case diagram of Hastings dental care house new digital information system
Use case description
Use Case name: This use case decryption is of Book Appointment as it is a primary use case.
Actors:
Main actors of this use case are
 Admin staff
 Patient
Pre-Conditions:
Conditions that are required to be true before starting the use case are:
 Both the users of the system must be signed in.
3

 Patient should be registered to the system
 Slots should be available
 Patient should provide details for booking an appointment
Post Conditions:
Conditions that are required to be true when the use case ends, no matter in which Scenario it is
executed are:
 Booking conformation message should be send to the patient
 Deposit fees should be informed and deducted from patient’s balance
 If low in balance then patient should be informed about low balance
Event path:
Basic path:
 Admin will log in to the system.
 Register details of all the new patients.
 Receive appointment bookings made on phone
 Check slot availability and then confirm booking
 Deduct appointment fees from patient’s balance
 Refund deposit if appointment is cancelled.
 Update booking
 Log out from the system.
Alternative path:
 Patient log in to the system.
 Make booking online as per availability of the slot.
 Make payment.
 If balance is running low then update balance.
 Cancel appointment if want to.
 Log out from the system.
Interface: digital information management system
Class Diagram
Class diagram is a based on the building block that useful in object oriented method for
new software development. It is mainly used the classes, interface, association, collaboration and
4

relationships (Agrawal, 2019). This type of method is considered as a standardized in class
diagram where each class represents building block of application. It is based on object oriented
that must design an appropriate structure in terms of relationships, inheritances and classes.
A class is mainly describe the group of objects with similar role in system of Hastings
Dental care house which consists of structural features, behavioural features, notation, class
operation, attributes etc. Each and every class are established relationship between one and more.
The primary purpose of class diagram is proposed new solution in terms of software archicture
that will show static structure through different classifiers (Arzumanov and Orlova, 2019). Class
diagram is representing the basic notation for entire structure diagram by using UML. It is
useful for developer and other members to understand overall functionality of new system and
also identifies attributes of each classes.
3cU2Fsd6GVkX1F%2FBgpNDgA94wO8NNe3EvNz9Nu%2FFietxc0TXJtQJ4%3DR8QXOKs5U2FsdGVkX1%2B4bCoBhhOkwcK%2Bml43JJHqsmDT%2B%2F6blmo3FxAZfZu0CUIeyT3kkBaLtK%2FRYbXOFtzvfLGUD5SQg6d8gavozHux5VLTMNGVRAGzDxLaTPwiAk3x9Z0UZQIVuvHlgniMYhUmsxhE7i4ut3vmoX4xBaBaE%2FMkloN5ZSzHANtA49w66vKNv4atl%2FBF9LKoNq6DrgOvDrzipjYE64oWH869KknaKPemSwlq%2Fa%2BDtYd2TgLCImph%2FLc2iFcvTo%2FzjTJyoKkUc1hsiQsGGZARiOX62a39bECAK3n7SzbcABcyudUcqjIIu%2FzeQx0W%2B%2FOk8kKj8zAQ3rYBBOeNCe%2FXZr1pYFQqiX2vloHRTjPe4Dzp3L7sgLXe8Zjvf1ZgiwyOmySiaDOaV5z6FU99jJdmIIFXX%2BExoS6o03UITPjy%2BdX3HE99jIwBhVVaA3DAQPLy16aVD5LPQvgmkmxxZ9JTJu7ea3r7f64%2Bi%2BFcuYmEanGVLmg993bH3R2cszuNwQ82qS9uwye9nHA9zZsdISBO5z6Ojprsh1%2BsSfzXjczHzhpy91ZRQBV%2FA2S71KhsucnaY3Ymsz8FnzRYs2UzW
%2B4qvIyAhGFRJSGzCfU04p6zgPIHOUrCOz2fodqQibXKPVNSp5KcMKOhlVUyeopBE1op3%2BYzq2ahY0fXEzofVOC36x8gLWEBvPhXlhTVbYsXOmxrmpQQKeWLpzWgRwZlCsPVrLJzVqRC1BI1eMA42lOp0nS44At5xP51b84sJQbhWwwsZhXxobwk5D1Z7TTUYZwAVWorNWFBx0pbeGeVrEXrqeLRXVx4eHYVIkcQkyIlyoH%2BrLCcw1KMTSi0Ni775C5ldsbXWMS%2FCWkOtwWO7pqiD3P760Q8BUZ9fqMQS7PiYCNhENFUS%2Bxki7Zz2Q%2BvK7dydD7lEux3fHHQPMEcy6uWHS91XGQTGzzB%2BFUXHQL7HBh8X%2FHJBGnleTYPgyZK8bQmWDXnjvqt3vmMwxT%2BmgophtJO9jp5P%2FrNNOuuZ7QA5j5udbdqKmyso0WcMnwXLBfY0XFeCotwlXsuJlCrn3sEQionEDHCb%2FdKdiFKtbXh8qEoki%2Fytz0tqSPn0%2BzeN6ijY9Nni8N%2Fr%2FswTsjfC3Gf1uZhZLGynbQpGsjYG8tcz4OK7isM5CR6tQ2w7ZxYMI3%2Fm9Arwv%2BJjwDezmAfpiybWHBTP3mkHwv6MbnwaHkmBJfnGvLMJ0uKORl8A2daFiUzVdPhgZe
%2BIH5aXkwcfdZcT6EoeDxc3Wles1cyt0BcjU9UQc4vFyPqafKnprUxWDsxqW4BsFgxBgWj7AOYlCZhqEV3%2Fg22EkxbUOuPCL1nDuzTB5gMQcC%2FP3pM5FwhLtrklCiv55jasKmrtCrLiqg%2FhzlM2%2BmRvqasvT7DZp%2F2%2FLIxlgy20JL6TVyFF4Z5bMaLaHm%2BeNwZd7uWDY62M9IYcvF7BuJuc3Rr3ptHfBG1Rj7ymyC6b6Q4cK8z4Dp46TTAdo0p6kOpnpZSDyyCE2JstGOkEhvwTxfY8ehwNV1bFtpef%2BdtnUaEcf75Cm6hJBWVbINWR3q0cKjLZ2aLxCORJZnBdkJWzDoe9IQYI%2F1XHYZp1rfv%2F8vC2nmV93V8jrIXqGSB5yZUsJm2ylg%3D1cvohi39
Figure 2 Class Diagram
The class diagram is mainly representing the attributes of each classes and also consists of
relationship between them. In above diagram, it mainly consisting of different classes and their
specific attributes.
Classes Attributes
5

Payment Date: date
Time: time
Customer Name: Character
Address: varchar
PhoneNo: integer
Staff Id : integer
Name: char
PhoneNo: integer
Address: Varchar
Email: Varchar
Patient Name: Char
Gender: text
Age: integer
Email: Varchar
Doctor Name : char
Address: Varchar
Specialist: char
PhoneNo: integer
Appointment Date :date
Time: time
Status: text
Table: 1
6

In this table, it contains different classes which has specified attribute that shows different role
and responsibilities for maintaining communication between one and two classes.
For Example-
In customer class, it contain mainly three attributes such as name, address and phoneNo,
2 operations such as login (), access (). These are different action performed in the new system
where customer easily search information about dental care services. New system will provide
facilities for giving proper details. In customer class, it also used the different parameters like
char, integer.
In staff class, it can be used four different attributes in staff such as id, name, email and
address while it also used two different operations: Record(), calculateTotal().These are different
action performed in the new system where customer easily search information about dental care
services. New system will provide facilities for giving proper details. In staff class, it also used
the different parameters like char, integer, Varchar and so on.
In booking class, it is mainly consists of three attributes such as id, date and time, 2
operations such as update (), record (). These are different action performed in the new system
where customer easily search information about dental care services. New system will provide
facilities for giving proper details. In booking class, it also used the different parameters such as
integer, date and time.
In Payment class, it is mainly consists of three attributes such as id, date and time, 1
operations such as update status (). These are different action performed in the new system where
customer easily search information about dental care services. New system will provide facilities
for giving proper details. In payment class, it also used the different parameters such as integer,
date and time.
Class diagram processes: while dealing with the complex system which may include
single as well as multiple attributes included. It always supports for handle entire process and
modelling system for business purpose. A dental care house mainly used new system to remove
all type of threats and limitation that generated during processing. It directly affects on the
customer experience during booking appointment and also increases chances of data loss. That’s
why, it has designed the unique structure for representing whole procedure functionality
effectively and efficiently.
7

Thus, when we are using class diagram in different phase of software development life
cycle that typically modelled classes in structure format and also considered three perspectives.
 Conceptual Perspectives: The class diagram is interpreted for describing whole things as
per real world but it should take conceptual perspectives for drawing diagram that
represents concept in new system design (Kobashi, Washizaki and Fukazawa, 2019).
 Specification perspective: this type of perspective is describing the software abstraction
and different components with proper specifications as well as interface. In this way,
there is no such commitment to the process of implementation.
 Implementation Perspective: It can be interpreted as describe overall implementation
process of software as per used modern technology and other suitable programming
language.
These are most common perspectives that useful in new system software design and
development because. It help for understanding overall functionality and according to them by
implementing task in proper manner. In most of cases, It should be increased the level of threats
which directly affecting on the entire process of designing so as needed to handle the process
through design approach.
Sequence diagram to model functional requirements
Sequence diagram is a kind of interaction diagram which is required to show all kinds of
interaction between objects in time sequence (Zhou, Reniers and Khakzad, 2016). This diagram
helps in explaining the sequence of messages that are exchanged between all the objects that are
required by the system to carry out all of its functionalities in a proper sequential manner. It can
also be said that this diagram helps in explaining the order in which objects of the system are
present and messages that are exchanged between them that too in a sequential manner.
Sequential diagram also consists of an actor who interacts with the system directly and the order
in which they interact with the system. it also consists of a lifeline that helps in depicting all
individual participants present in the diagram. Other than this all kinds of messages that are
exchanged with the actors or objects are explained in a better manner. This sequence diagram has
helped in explaining messages that are exchanged between all the system actors and the system.
It also helps in explaining the sequence in which messages are exchanged between objects or are
exchanged between objects in a sequential and timely manner. The main actors of this sequence
diagram are patient and staff members of the dental care home.
8

Figure 3 Sequence diagram of Hastings dental care house new digital information system
Task Reflection and Critical Evaluation
Discuss about the Software development life cycle methodology that have chosen for solution in
development with example.
Software development life cycle is a type of process that must ensure the correctness and
quality of software built. The primary aim is to produce the best quality of software which meet
customer expectations. For design new dental care system that should records all information
9

about customer, patient, staff, booking and appointment (Kumar and Emfinger, 2019). In this
way, Software development life cycle play important role for providing the pre-defined time
frame and cost. It would be completing the task in proper manner. SDLC mainly consists of
detailed plan which easily describe the procedures for building, maintaining software through
different phases. Every stage of software development has performed significant task which
delivered that feed into another one. There are common stages of software development life
cycle.
Planning and requirement analysis: It is initial step for planning the need and requirement for
software development. In this process. Stakeholders are discussed about the needs of final
products and primary goal is to define detail working process of entire software system. Besides,
it needed to make sure that all participants may have clearly understand about each task
according to requirement and implemented.
Designing project: it is second phase of software development life cycle where developer play
important role for designing the overall architecture of new Hashing dental care system. It may
use the modern technologies that applicable in project where team members understand entire
loads, budgets, time frames and limitations. This will help for making decision to fulfil all type
of requirements (Machiraju and Gaurav, 2019).
Programming and development: After approved the needs and requirement, it goes further to
develop the software by using programming language. Developer may use source code for
writing while keeping to define previous requirements. It also added more features and
functionality in new system for easily recording, updating and maintaining information in proper
manner. The system admin will adjust the software environment and programmer may interface
of programs while perform different logics for purpose of interaction with different server.
Testing: It is very important phase for software development because after successfully design
new system that needed to perform testing phase (Oshana and Kraeling, 2019). It will help for
debugging any threats and defects. Sometimes, it happens that code flaws missed at the time of
development. In this way, testing phase will easily identify issues and problem, removed and
maintain software workflow.
Deployment: when the program has to be finalized that has no critical issues. It may launch in
market for end users. It is the best way to release new version where every team join and
supports for software. It also taking feedback from users and consult at the time of exploitation.
10