Software Design Document for Website Re-construction Project ISY3002

This Software Design Document (SDD) outlines the architecture and design for the re-construction of the instituteofknowledge.com.au website. The document addresses the needs of stakeholders, including customers, the website owner (Dr. Sam), developers, and project managers. It details the system behavior, logical view, high-level and mid-level design, and includes diagrams such as a class diagram and sequence diagram to illustrate the website's functionality. The SDD covers design goals, system behavior, and project management aspects, ensuring a modular and scalable design that minimizes complexity. The document provides a comprehensive overview of the website's re-construction, including system architecture, use case views, and project planning to enhance user experience and data management efficiency.

Running head: SOFTWARE DESIGN DOCUMENT
Software Design Document: Website Re-construction Project
Name of Student-
Name of University-
Author’s Note-

1SOFTWARE DESIGN DOCUMENT
1. Introduction
This particular document describes the architecture as well as re-designing of the website
of www.instituteofknowledge.com.au which is owned by Dr. Sam. The application is being
developed for the customer who wants to work with institute and for Dr. Sam who can handle the
data and the website more efficiently. The application will allow the owner to synchronize the
data of the website and manage all the training more efficiently.
The main purpose for this document is describing the architecture of the website and
designing the website application is such a way that will address the concerns and the interests of
the major stakeholders. The main stakeholders who are involved with the development of this
project are:
 The customers and Dr. Sam: The customer wants assurance that architecture will help to
provide the system functionality as well as exhibit all desired non-functional requirement
of the website. The owner of the website also wants assurance that the website that will
be built will have high quality requirement that will include reliability, usability and
accountability.
 Developers: Another stakeholder associated is the developers. The developers wants to
design the architecture that will make the work of the user more efficient and will
minimize complexity and the development effort.
 Project Manager: The responsibility of the project manager is assigning the tasks as well
as coordinating with the development work in the system. The work of the project
manager is to develop the designing process in many components of equal size and
design the complexity for developing the software. There is to be well-defined interfaces

2SOFTWARE DESIGN DOCUMENT
that is to be define while designing the application. The modules need different interfaces
for designing them and the project manager has the responsibility to design it. Most of the
individuals specializes in some particular technology or skill and the design should be
done specifically.
 Maintenance Programmers: The programmers wants assurance for re-constructing the
system that will help to evolve as well as maintain the website application in future.
The design and the architecture that is developed for the software system is very complex
as well as provides individual interests of the stakeholders. There are many diagrams that can
help the developer to design the redesigning of the application and to express the architecture
and the design of the application that is to be built. There are many terms that are included for
developing the system and those are presented in multiple perspectives and views. The
architecture that is associated with reconstruction of the website includes four different
perspectives.
1. Logical View: the main concern of logical view is to include the major components, the
attributes as well as the operations that are to be included in the system. The view also
includes defining the relationships between the components and the interactions that are
included in the system. When the object oriented designs are done for the website, the
design is known to be as the logical view of the system.
2. Process View: The process view describes the threads for controlling as well as
processing the processes that are to be used for executing all operations associated with
the logical view of the application.
3. Development View: This particular view states about how the modules in the application
system are mapped for work to be done efficiently in the website.

3SOFTWARE DESIGN DOCUMENT
4. Use Case View: The view of Use case is mainly used to validate as well as motivate the
design activities that are included in the system. At the starting of the project, the
requirements is defined as functional objectives for designing. With the use case, the
developer can validate any design suggestion for the system interaction between all
components in the system.
2. Design Goals
The design goals of the project states the project to be a good project or a bad project. But
there is no actual good project or a project to be bad. The design value of the project or an
application is mainly depended on the priorities of the stakeholders. The design value mainly
depends on effective design as well as circumstances that is better compared to the present
website that is used by the company.
The presentation of the application design should be good that will state the design
priorities in the application. The design for the organization can be judged as per the satisfaction
of the priorities stated.
The priorities of the design that is developed for this application is judged accordingly
stating how the application will satisfy the need of the users according to their priorities.
The priorities of design that is included in re-constructing the website application are
stated below:
 The application design will help to minimize the complexity of the application and the
development effort of the application.
 The design should satisfy the goals of the user associated with the application.

4SOFTWARE DESIGN DOCUMENT
3. System Behavior
The system behavior is stated as per the use case view which is used for both in the
design phase as well as to validate all outputs of the design phase in the system. This section
includes the architecture design of the application that is to be reconstructed and a review of the
application is stated below in this section. There is also a description of the architecture that is to
be designed for the application of the website.
Figure 1: System Behaviour Design
(Source: Created by Author)

5SOFTWARE DESIGN DOCUMENT
Description: The above wireframe shows the details of the application that is to be
reconstructed for the undertaken website. The home page will have a sign up process tab, the
courses that are to be offered by the institute, the training that will be provided to you, the about
us tab. When clicked on the sign up button, the user is taken to the page where details for the
sign up is to be given. After the sign up page, then comes the page that shows the courses that are
to be given by the institute. The institute consist of many courses that are related with the
training courses and the system shows all the training and the user can book for the training for
the available dates that shows on the screen. By this system, the owner of the institute can view
all the data related with the system and can manage the data efficiently.
4. Logical View
The system logical view that are related with all functional components of the system.
Logical View includes modules, all the relationships that are included in the modules, and the
patterns that are associated with the system interaction.
This particular section will show the modules that are associated with the system, the
section will show an architecture design of high level of the system that is to be developed. There
is also a mid-level design process that is shown in this particular section. A detailed class
diagram for the system is also shown in this section that states the attributes as well as the
operations that are associated with the system.

6SOFTWARE DESIGN DOCUMENT
4.1 High-Level Design (Architecture Design)
Figure 1: High-Level Architectural Design
(Source: Created by author)
The application that is being designed for the website application will be built in modular
manner for enhancing the scalability. Designing the architecture of the application software is
actually considered as an art for developing the software. Designing the architecture of a
software includes blue print of the application that is going to be developed. Making an
architecture that is included in the system is very much needed to design the activity of the

7SOFTWARE DESIGN DOCUMENT
system. This is an important activity that is to be done in the SDLC method of developing the
system architecture. The architectural design is mainly done in two steps, high-level design and
mid-level design. The high level design of the application system ensures that the design is made
with good principle design and proper data flow diagram, sequence diagram and the class
diagram is done for developing the application of the institute.
The above diagram shows the architectural diagram of the application system that is to be
re-constructed for the website. The data of the application is to be stored in the database of the
system and there is to be a third party API associated with the system. The architecture diagram
also has the options to reset the API of the system. The architectural design that is stated above
states the designing of the reconstruction of the website that provides training courses to business
for developing the system.
For developing the architectural diagram, the application type should be known so that
the developer has better understanding in creating the developing the system. The project
manager should have the responsibility to develop the system. The main key scenarios and the
use cases are to be developed for the system that will state the working process of the system.
The functional and the non-functional requirements are to be implemented for re-designing the
system for the website. The developer has to choose a topology of deploying the system
architecture. Designing the application is a complicated method and the hardware included in
developing the application is very expensive.
The layer of the application that is to be designed for this website is to be chosen wisely.
There should be client server role in the system that include two roles and the client and the
server that helps to pass the information in a simple way. The client in the system makes request

8SOFTWARE DESIGN DOCUMENT
to the server and after getting the request, the server responds to the request of the client and then
provide an answer that the client wants from the server.
4.2 Mid-Level Design
Figure 2: Class Diagram of the new re-constructed website
(Source: Created by Author)
Description: The mid-level design had been presented above, this diagram includes three
classes namely customer, courses and training. These classes have numerous attributes and
methods, the attributes are used alternatively for numerous properties or data members.
Attributes are usually he data members of a particular object. The class named customer has
various attributes including customer name, address of customer, phone number of the customer,
email and company name of the customer. The methods that are included in this include

9SOFTWARE DESIGN DOCUMENT
gertCourseDetails, this collects details regarding the course that the customer wants to go
through. The next method used is getTrainingDetails, this particular method collects data
regarding the training that the customer is undergoing or aspires to undergo. getHelp method
helps a customer to contact the customer support in case they have any query or confusion. The
class names courses include numerous attributes that hold data relevant to the courses that are
held by the website. The attributes include name of the course, ID of the course and type of
course. The methods that are used by this class include getTrainigDetails and
getCustomerDetails. The next class is training, this class includes attributes like name of training,
ID of training, and the methods include getTrainingDetails, getCustomerDetails, and
getCourseDetails. This particular class includes data regarding the training that customers can
undergo with the help of the website and the details of customers who are undergoing numerous
trainings.
Figure 3: Sequence Diagram of login process of customer

10SOFTWARE DESIGN DOCUMENT
(Source: Created by author)
Description: The sequence diagram represents the method of login that has to be
followed by the customer in order to get access to the further details of the services provided by
the website. The initial step that has to be performed by the customer includes providing the
username as well as password, this data is passed on to the management systems and is further
passed to the system, the system checks weather the constraints provided by the customer are
authentic, if not the login request is denied and the customer is provided that message that the
login had been unsuccessful and they might register or might provide with appropriate user name
and password. If the credentials provided by the customers match with the data that has been
already saved in the database, the customer is logged into the website. If login n successful, the
customer is provided with a message that the login had been carried out successfully.

11SOFTWARE DESIGN DOCUMENT
Figure 4: Sequence Diagram of searching course details
(Source: Created by author)
Description
One more sequence diagram had been presented which represents the searching course
details. The initial step in this process includes the customer searching the courses that he aspires
to undertake, this search data is sent to the management and further to the system. In case the
database consists of similar course, the customer is provided with a resalt or some results that are
relevant to the search. This search result is shown to the customer. In case the search results are
not matched, a message is sent to the customer that there are no results found. The customer then
searches for training details, the training details are searched for by the system and relevant
results are provided to the customer, in case there are no details found by the system, the
customer receives message that the search results are not found.

12SOFTWARE DESIGN DOCUMENT
4.3 Detailed Class Diagram
Figure 5: Detailed Class Diagram
(Source: Created by author)
Description: The detailed class diagram shows the internal processes that would undergo
within the website, the processes include booking, payment, training and some more. This
diagram includes numerous classes, these classes include payment, booking, customer, courses
and training. These classes contain numerous attributes and methods which describe the detailed
process undergone by the classes. The class that has been placed in the middle and is connected
to all other classes is customer, this is because customer is the key class in this process. The
attributes under the customer class include name, address, phone number, email and name of the
customers. The methods include getCourseDetails, getTrainingDetails and getHelp. The next
attribute is courses, this includes details regarding the courses that customers would aspire to
under, the next class is training which includes details regarding the raining that is provided by
the website and the customer details is collected. The class of booking deals with collecting data

13SOFTWARE DESIGN DOCUMENT
related to the booking of the training that has been selected by the customer. The payment class
deals with the transaction that would be carried out if the customer wants to continue with a
specific training.

14SOFTWARE DESIGN DOCUMENT
5. Process view
5.1 Process View Description
The view process that is associated with developing an application and designing an
application mainly understands the way to separate all the components as well as sub-
components that helps to communicate with all other applications that are included in the system.
The process description helps to understand all the paths that are necessary for establishing the
communication in between all such components and it is possible to control the flow of data and
the storage that is associated with the website development and ensure some thread safety in the
system.
4.2 Application Thread
The application thread is considered as a main thread of application that helps to create
some runtime in the program. The application thread helps to create some program thread that is
not actually a thread that is created by user. This particular thread helps to handle all such basic
flow of basic programs that controls navigation between the pages of the website and also
controls all the processing that are created in the window events that includes handling all inputs
of the user in some of the graphical forms.
4.3 Presentation Thread
This particular thread is mainly created by the user when the user using the website
application goes through the application and navigates from one page to another of the new
website that is being re-constructed for the Institute of Knowledge Management. The
presentation thread is mainly responsible to take the landmark that is near and also helps to rely
on the information that is gathered from the presentation thread. The presentation thread requests

15SOFTWARE DESIGN DOCUMENT
Image Viewer as well as the sub-components of Audio Player to update the updated presentation
of the website where ever it is necessary.
4.4 Connection Thread
This particular thread is created by the user. The connection thread has the charge to
check the connection that is included in the GPS device of the application that is to be built. This
thread checks whether the thread is working perfectly or not and whether the GPS is valid or not.
Before switching between the pages of the re-constructed website, the connection thread that is
included in this application ensures the user that the connection is valid or not and check the
authentication of the connection before proceeding with the website. The connection thread also
helps to track the time in which the connection was not valid and shows time to the user. If the
connection related with the application website is not valid for certain period of time, the system
will notify that particular user about the re-connection to re-connect with the system. If the
connection is invalid for more time, the system will proceed with the flow of the program
without providing any notification to the user about the failed connection while attempting re-
establishment of the connection.
4.5 GPS Thread
The GPS thread is also user created. This particular thread will read the latitude as well as
the longitude of the GPS device and will keep a track on the location of the user. The GPS thread
will help to provide the program with all the information that are necessary about the position of
the user and the location of the user will get updated each time the user travels from one position
to another. The GPS connection thread will check constantly with the thread for establishing
valid connection.

16SOFTWARE DESIGN DOCUMENT
4.6 Device Thread
Device thread is created by the user. The device thread will help to read the present state
of the particular device and will help to track all the state of the device and of the device of
accessing the application is changed by the user, the device thread will generate an event that
will notify the device changing state of using the application. This will also track the GPS of the
system thread that will help to update the present position of the user. The device thread does not
have any connection with the connection thread.
Figure 6: Process View Diagram
(Source: Created by author)
Description: The below diagram shows the threads that are related with the application
website. There is audio thread, the GPS thread, the database thread and the mapping thread that
are included with the website application. The website application has audio mode that will help

17SOFTWARE DESIGN DOCUMENT
the user to track the audio that is associated with the system. There is GPS system that will help
the application system to track the user who is using the system. The database system will help
the user to store the data or the information that is related with the system. The mapping thread
will help the application to map the system. The database thread associated with the system will
help the user to store the data that are related with the system. The device thread will help the
user to track the device that is being used for accessing the system. The application system will
ensure the system to track all the devices that are being used to access the website application of
the Management system.

18SOFTWARE DESIGN DOCUMENT
6. Physical View
Figure 7: Website Planning Process
(Source: Created by author)
Description: The website planning process of the application that is to be re-constructed
for the application website. The sponsor of the website Dr. Syed Ahmed wants to reconstruct the
website that will help the working of the application more efficiently and effectively. Website

19SOFTWARE DESIGN DOCUMENT
planning is needed for developing the application website and will help in re-constructing the
knowledge management website that will be developed. The website system planning process is
explained in the above diagram.
For planning the website, the developer has to develop the system by making a goal of
the website along with the metrics that are to be included in the system. The developer also has
to decide the name of the website for the new re-constructed website that is being developed for
the system. For re-constructing this particular website of the management system, the developer
does not need any particular website name as because a name is already present for the
application. If the developer wants, he has the accessibility to change the name of the
application. The developer also notifies all the technologies that will be needed to re-construct
the system which consists of web- hosting, the platform that is needed, the web developer, the
web designer, and the technical maintenance. The developer also has to define the target
audience for the system. The developer also need application demographic, the need of re-
constructing the website, and the problems that are faced to re-construct the application website.
The need of planning process helps the developer to develop the system efficiently and
effectively. The re-construction of the process will involve user side that will help the
organization to login for the system.
The application of the website view that is to be include in the system are the images, the
video, and the audio that are related to the training course of the system. The system needs to be
re-constructed so that the owner of the website can track all the application data more efficiently.
The data will help in better system controlling. The website will include the short video and
audio clips of the training that will be provided by the institute. The video clips will help the user
to get an idea of the how training is provided related to different courses and details of the

20SOFTWARE DESIGN DOCUMENT
training sessions that are to be provided with the system. While confirming the needs of
reconstructing the system, all the needs of designing a new system are to be defined while
planning with the system. The website planning also need proper target audience that are to be
specified by the users. This website planning of development process will help the user to
provide a clear idea about how the website is to be developed in the system.
There are many problems that are associated with the system. The problem are to be
specified for the system. The developer while planning the physical view of the system, the
developer needs to specify the problems that are included in the system and all the exceptions
that are to be included in the system. The exceptions of handling the process are also to be
included in the system that will be needed to handle by the developer of the system.
7. Use Case View

21SOFTWARE DESIGN DOCUMENT
Figure 8: Use case View
(Source: Created by author)
Description: The above diagrams shows the use case view of the website application that
is to be re-constructed in the system. The diagram above shows different authentication process
of the system. The actors that are involved in the system are the customers, the management
system and the trainer who will provide training to the organizations. The customer will first
need to sign up in the system of knowledge management to view the courses and book the
courses. The customer can view the courses and the then view the training schedule that is
provide by the company. The customer will get the payment option to pay advance for the
training course that are taken by them.

22SOFTWARE DESIGN DOCUMENT
The management has the responsibility to approve the registration and then provide them
with the course details and the training details. The course details and the training details are the
responsibility of the management system. The management system looks after the need of the
users who will be handling the system efficiently.
There is trainer for this system who can view the schedule of training for the system and
the trainer will also provide training to the system. The trainer needs to get the details of the
training details that is fixed by the management system and the user. Trainers are allocated to all
the training that are provided in a particular course in the institute. The trainer will reach the
allocated place for providing training to the organizations.

23SOFTWARE DESIGN DOCUMENT
Bibliography
Danielson, C.K., McCauley, J.L., Gros, K.S., Jones, A.M., Barr, S.C., Borkman, A.L., Bryant,
B.G. and Ruggiero, K.J., 2016. SiHLE Web. com: Development and usability testing of an
evidence-based HIV prevention website for female African-American adolescents. Health
informatics journal, 22(2), pp.194-208.
Henry, S.S. and Singh, A., 2015. Website development for Course Management of an Academic
Institution. International Journal of Computer Science Issues (IJCSI), 12(1), p.157.
Higgins, B., 2017. Regional development theories and their application. Routledge.
Hoehle, H. and Venkatesh, V., 2015. Mobile application usability: Conceptualization and
instrument development. Mis Quarterly, 39(2).
Jamieson, K.G., Jain, L., Fernandez, C., Glattard, N.J. and Nowak, R., 2015. Next: A system for
real-world development, evaluation, and application of active learning. In Advances in Neural
Information Processing Systems (pp. 2656-2664).
Meng, R., Zhao, Z., Chi, Y. and He, D., 2017. Automatic Course Website Discovery from
Search Engine Results. iConference 2017 Proceedings Vol. 2.
Qing, L., Wu, P., Bing, Z., Yu, F., Pang, X., Ding, P., Lei, Z., Xiao, Y., Fu, J. and Tang, J., 2019.
The concept of the special form perforator flap and its role in the evolution of
reconstruction. Journal of Xiangya Medicine, 4.
Rosas, S.R. and Ridings, J.W., 2017. The use of concept mapping in measurement development
and evaluation: application and future directions. Evaluation and program planning, 60, pp.265-
276.

24SOFTWARE DESIGN DOCUMENT
Zhou, Q., Xu, Z. and Yen, N.Y., 2018. User sentiment analysis based on social network
information and its application in consumer reconstruction intention. Computers in Human
Behavior.