Effective Beauty and Health Remedies
Design Document
Version 1.0
Group ID
S20028B638 (BC160401708,BC160401709)
Supervisor Name:
Imtiaz Bibi
Revision History
Date Version Description Author
(dd/mm/yyyy
)
Current date 1.0 Introduction of the project Write student(s) id
(BC160401708,BC160401709)
04-07-2020
The Design Document Includes
Entity Relationship Diagram
(ERD), Sequence Diagrams,
Architecture Design Diagram,
Class Diagram, Database Design,
Interface Design, and various Test
Cases.
It is final year Project in the
Faculty of Virtual University of
Pakistan in the year 2020-21
Table of Contents
1. Introduction of Design Document
2. Entity Relationship Diagram (ERD)
3. Sequence Diagrams
4. Architecture Design Diagram
5. Class Diagram
6. Database Design
7. Interface Design
8. Test Cases
1. Introduction of Design Document
In Design document we have included the following diagrams and Design in this document.
Entity Relationship Diagram (ERD)
Sequence Diagrams
Architecture Design Diagram
Class Diagram
Database Design
Interface Design
Test Cases
Benefits and Purpose of this phase in software development project.
Software Documentation is a critical activity in software engineering. Documentation improves on
the quality of a software product. It also plays significant roles in software development environment
and system maintenance. Several software development best practices are ignored. This paper
Looks at the importance of software documentation, creation, applications, tools and standards.
The role of documentation in a software engineering environment is to communicate information to
its audience.
Documentation is used as a communication medium between members of the development team and
probably the clients.
Provide information for management to help them plan, budget and schedule the software
development process.
The documents also act as evidence of all the procedures and activities involved in software
development therefore, documents need to be up-to date, complete, consistent and usable. To
achieve consistency, systematic ways of document creation should be employed.
Documentation can also be used for learning a software system, testing a software system, working
with a new software system, solving problems when other developers are unavailable to answer
Questions, looking for big-picture information about a software system, maintaining a software
system, answering questions about a system for management or customers, looking for in-depth
information about a software system, working with an established software system.
Poor documentation is the cause of many errors and reduces efficiency in every phase of a software
product’s development and use. Documentation is an activity that needs to commence early in
development and continue throughout the development lifecycle. It acts as a tool for planning and
decision making.
2. Entity Relationship Diagram (ERD)
3. Sequence Diagrams
remedy
Architecture Design Diagram
It is a three-way interaction in client/Server environment Three-tier architecture is a software
design pattern and a well-established software architecture. The programming for a tier can
be changed or relocated without affecting the other tiers, the 3-tier model makes it easier for
an enterprise or software packager to continually evolve an application as new needs and
opportunities arise.
Detail of three tier is as follow:
1. Presentation Tier: User interface is stored in a client. This layer occupies the top level and
displays information related to services available on a website. This tier communicates with
other tiers by sending results to the browser and other tiers in the network.
1. Business Tier: Also called the middle tier, logic tier, application logic or logic tier, this tier is
pulled from the presentation tier. It controls application functionality by performing detailed
processing. It is stored in one or more servers.
2. Data Tier: Houses database servers where information is stored and retrieved. Data in this
tier is kept independent of application servers or business logic.
Its advantages are scalability, reusability, data integrity, security, availability and less complexity.
5. Class Diagram
Introduction:
Class diagram is a static diagram. It represents the static view of an application. Class diagram is
not only used for visualizing, describing, and documenting different aspects of a system but also for
constructing executable code of the software application.
Class diagram describes the attributes and operations of a class and also the constraints imposed on
the system. The class diagrams are widely used in the modeling of object-oriented systems because
they are the only UML diagrams, which can be mapped directly with object-oriented languages.
Class diagram shows a collection of classes, interfaces, associations, collaborations, and constraints.
It is also known as a structural diagram.
6. Database Design
<Provide Database Design Diagram of the system>
A database is usually a fundamental component of the information system, especially in business
oriented systems. Thus database design is part of system development. The following picture shows
how database design is involved in the system development lifecycle.
The phases in the middle of the picture (Database Design, Database Implementation) are the phases
that you concentrate on in the Database Design course. The other phases are briefly described. They
are part of the contents of the Systems Analysis and Design courses, for example.
7. Interface Design
8. Test Cases
Use Case Template
Test case REGISTRATION
Test case 5
Id
Description
Person can register by giving his details like Username, full Name,
Address
Pre Must load website in web browser
condition
steps
Load website in his web browser Enter his details ( Full name, ,
address and email ), Choose User Name and password for login
Expected Details are entered in system and present to administrator for
result authorization.
Actual Person is added successfully
result
Usecase LOGIN
Usecase Id 6
Description
Enter their valid user name and password to Sign in system.
Pre Web site should be loaded. And responding
condition
steps
Enter their valid Username and password. Submit this page by clicking
on Login button.
Actual Successfully Login system.
result
Expected System should allow user to enter in the system
result
Test case Logout
Test case 7
Id
Description
This test case explains about logout
Pre Must login first.
condition
steps
Click on Sign out.
Actual Successfully Sign out system.
result
Expected User must be logout after clicking on logout button
result
Test case Add Feedback/Query
Test case 7
Id
Descriptio
n
This test case explains about insert function of feedback/query
Pre Must login first with visitor account.
condition
steps
Click on add feedback/query tab for visitor .now fill the form and enter
ok
Actual Successfully added feedback/query in the system.
result
Expected Feedback must be added
result
Test case Add reply/answer
Test case 8
Id
Descriptio
n
This test case explains about insert function of reply/answer
Pre Must login first with visitor account.
condition
steps
Click on queries/feedbacks tab for admin. .now fill the form and enter
ok
Actual Successfully added reply/answer in the system.
result
Expected Reply/answer must be added
result
