CAPSTONE PROJECT REPORT

Report 4 – Software Design Document

Table of Contents
I. Project Report..........................................................................................................................................3
1. Status Report.......................................................................................................................................3
2. Team Involvements.............................................................................................................................3
3. Issues/Suggestions...............................................................................................................................3
II. Software Design Document.....................................................................................................................4
1. Overall Description..............................................................................................................................4
1.1 Assumptions..................................................................................................................................4
1.2 Design Constraints.........................................................................................................................4
1.3 [Technology Suggestion]................................................................................................................5
2. System Architecture Design.................................................................................................................5
2.1 Overall Architecture.......................................................................................................................5
2.2 System Architecture......................................................................................................................5
2.3 Package Diagram...........................................................................................................................5
3. System Detailed Design.......................................................................................................................6
3.1 <Feature Name1>..........................................................................................................................6
4. Data & Database Design......................................................................................................................8
4.1 Database Design............................................................................................................................8
4.2 Data File Design.............................................................................................................................9
I. Project Report
1. Status Report
# Work Item Status Notes (Work Item in Details)
 1   Pending  
 2   In Progress  
 3   Completed  

2. Team Involvements
# Task Member Notes (Task Details, tec.)
 1   KhangNN  
 2   HuyTH  
3 LongNN
4 QuangNV
 5   KhangCH  

3. Issues/Suggestions
# Issue Status Notes (Solution, Suggestion, etc.)
 1   Pending  
 2   In Progress  
 3   Completed  
II. Software Design Document
1. Overall Description
1.1 Assumptions
-Assume all the people who use this system have basic knowledge of mobile and know how to operate
the system smoothly.

1.2 Design Constraints

-The device requires full functionality to use the application

1.3 [Technology Suggestion]

2. System Architecture Design
2.1 Overall Architecture
2.2 System Architecture

2.3 Package Diagram

[Provide the package diagram for each sub-system. The content of this section include the overall
package diagram(s) and the explanation for each package. Please see the sample and description table
format below]

No Metho Description
 d
01 db Package contains the connection class for connecting to the database
dao
2 Package contains classes that connect, query the database, and return the model

3 model Package contains classes responsible for sharping the data to return to dao

3. System Detailed Design

3.1 <Feature Name1>
[Provide the detailed design for the feature <Feature Name1>. It include Class Diagram, Class
Specifications, and Sequence Diagram(s)]

a. Class Diagram
[This part presents the class diagram for the relevant feature]

b. Class Specification
[Provide the description for each class, including both Class Attributes and Class Methods information.
Those can be in the table format as below]
b1. User model
[Provide the detailed description for the class methods]
No Method Description
01 idUser The id of user

02 userName The id of user to login

03 fullName The Name of user

04 email The Email of user

05 address

06 phoneNumber

N Visibilit
Method Return Type Description
o y

1 getter public Attribute Type get attribute value

2 setter public void set attribute value

b2. Campaign model

Class Methods
[Provide the detailed description for the class methods]
No Method Description
01 idCampaign The id of Campaign

02 namCampaign The name of campaign

03 createDate The date on which the clerk create campaign in the system.
Starting: The campaign is in progress.
04 status
Not yet: The campaign hasn't taken place yet.

05 personCreate The person create campaign

06 Description Describe more about the campaign.

N Visibilit
Method Return Type Description
o y

1 getter public Attribute Type get attribute value

 2 setter public void set attribute value

b3. Task model

No Method Description
01 idTask

c. Sequence Diagram(s)
[Provide the sequence diagram(s) for the feature, see the sample below]
Guest Login
Authenticated User Logout

4. Data & Database Design

4.1 Database Design
[Provide the tables relationship like example below]
a. User
[Give some lines about the table here>>
[Table fields, in the form of table format as below]
Uniq Not
Field name Type Size PK/FK Notes
ue Null
idUser nvarchar 50 x PK The id of the user.
userName nvarchar 50 x The name of the user.
fullName nvarchar 50 x The full name of the user.
password nvarchar 50 The password of the user.
email nvarchar 50 The email of the user.
address nvarchar 50 The address of the user.
phone number 10 The phone number of the user

b. Campaign
Uniq Not
Field name Type Size PK/FK Notes
ue Null
idCampaign nvarchar 50 x PK The id of the campaign.
nameCampaign nvarchar 50 x The name of the campaign.
dateCreate nvarchar 50 x Date create of campaign
 dateStart nvarchar 50 Date start campaign
dateEnd nvarchar 50 Date finish campaign
personCreate nvarchar 50 Person create campaign
description nvarchar 100

c. Task
Uniq Not
Field name Type Size PK/FK Notes
ue Null
idTask nvarchar 50 x PK The id of the task.
nameTask nvarchar 50 x The name of the task.
idCampaign nvarchar 50 x The id Campaign of task
dateCreate nvarchar 50 Date create of task
dateStart nvarchar 50
dateEnd nvarchar 50
discription nvarchar 100

4.2 Data File Design

N/A