Principles of Software Engineering

PRINCIPLES OF SOFTWARE ENGINEERING
1

Contents
INTRODUCTION...........................................................................................................................3
PART A...........................................................................................................................................3
Produce a use case diagram to model functional requirements...................................................3
Produce class diagram that model the system structure and proposed the potential solution.....5
Produce the sequence diagram to model functional needs..........................................................8
PART B.........................................................................................................................................10
Discuss about the software development life cycle methodology with example......................10
Critically reflect on professional, security, ethical and social issues related to design or
development...............................................................................................................................14
CONCLUSION..............................................................................................................................17
REFERENCES..............................................................................................................................18
2

INTRODUCTION
Software engineering is basically defined the process of analysing user requirements and
then building, designing and testing the entire application. In order to satisfy those requirements
in which help for obtain the software in reliable and work efficiently. The report is based on the
“Hasting dental care house” that will develop a new system for manging and controlling the
operational functions. The report will discuss about the use case diagram to model the functional
requirements for representing the necessary actors that perform significant operation. It will
describe about the class diagram to represent the system structure for proposed the potential
solution. Furthermore, it reflects on the professional, security, ethical and social issues related to
design or development. The documentation will describe about the software development life
cycle methodology that useful for designing system structure and its functionality.
PART A
Produce a use case diagram to model functional requirements.
A use case diagram is based on the model that capture system functionality and user
requirements with the help of actors (De Lessio, Wynn and Clarkson, 2019). It useful for
modelling the service, function and task that needs to perform effectively. Use case must contain
high level of functionalities whereas how user can handle the system activities. It is core concept
in terms of unified modelling language that consists of persons, various things invoke the
features. In this way, it will be considered as dynamic behaviour that capture behaviour of live
system. The use case model is responsible for visualising the internal or external things.
Figure 1 Use Case Diagram
3

In above diagram, it has summarized that use case diagram is representing flow of information
and also give prevail other for purpose plan of their development. In this way, it can easily
understanding the different operation performed within “Hasting Dental system”. It is considered
the high level of diagram that mainly show the system or application. It can be divided into
different element or components that mainly used on Hasting dental system such as
 Systems
 Actors
 Use cases and Relationships
Use case description
Use case Use case of hasting dental new system.
Actor  Admin
 Staff
 Patient
Description The use case is mainly representing the overall
functionality that performed before
appointment. The patient will use new system
to book appointment and check time slot. First
of all, patient login the system to enter details
and send request through SMS. Afterwards,
staff members have been confirmed the online
booking and provide time, date and
information of regular doctor. After
confirmation, it has been successfully making
payment.
Flow of event  Patient login system for track the
number of booking and select the
4

particular time slot.
 Patient update the details on the system.
 User can book appointment and staff
member give confirmation to the
patient.
 Admin has recorded the details of
patient in the system.
 Choose Payment Option and
Successfully completed in proper
manner.
Pre-condition Patient and staff members must require to exist
account on the system so that they can easily
check information.
Post-condition  The pre-booking appointment must be
created by staff members.
 Each payment also created and
associated by individual users.
Alternative exceptions The details of patient are already present in the
system. Admin staff needs only as a key
identity where system automatically display
information about particular customer.
Non-functional requirement  Reliable system
 Performance
 Dependability
 Privacy and security
5

Table:1
Produce class diagram that model the system structure and proposed the potential solution.
A class is a blueprint for particular object that mainly used for designing a new system. it
is based on the static structure representation whereas they are showing the system classes,
attributes, methods and relationship between objects (Fernandes, 2019). All classes are arranged
in the groups that easily share common characteristics among them. It also resembles a flow
chart in which classes are designed in box whereas each one having specific attributes.
Figure 2 Class Diagram
From the above figure, it can be implemented the classes HDCH management system. It also
seen the Relationships between different classes. In above figure-2, It can be described the
different classes and their attributes. Each class has established the relationship with one or more
classes. It is mainly including patient, booking, Customer, staff, administrator, doctor and
manager.
For Example- In patient class, it also represents the attributes such as id, name, gender
and age whereas operations are shown in third partition. Patient class creates relationship with
booking class whereas both are performing operations. Patient is to search the information on the
system for searching booking time, date and status. In this way, it can be developed the
relationship between patient and booking classes.
6