i
w
u
@
n
ua
y
x
(
0
2
2
4
P
o
s
nd
1. Right click the name of the database that has been created in the project
1. Right click the original project name LoginPage
2. Click Delete to remove the database
2. Choose to Rename it to BookStoreGUI
M
O
C
* Always make changes/modifications within Visual Studio as changes
directly in the solution folder corrupt the solution
)
a
r.c
Note: Apply the same refactoring procedure to rename the project of
UnitTestLoginPage to BookStoreLIB
1
2
1. Double click Properties
2. Click Application
M
O
C
3. Type in the new name
4. Type in the new name again
5. Right click BookStoreGUI
i
w
u
@
n
ua
y
x
(
0
2
2
4
P
)
a
r.c
o
s
nd
1. Right click LoginPage in the file of MainWindow.xaml.cs
2. Choose to Rename
3. Change LoginPage to BookStoreGUI
4. Check-mark the boxes
5. Choose to Apply the change of namespace
6. Choose to “Save Selected Iterms”
3
4
1. Right click MainWindow.xaml
2. Choose to Rename
M
O
C
i
w
u
@
n
ua
y
x
(
0
2
2
4
P
3. Type the new name, i.e., LoginDialog
)
a
r.c
o
s
nd
1. Right click the class name
2. Choose to Rename
3. Type the new class name, i.e., LoginDialog
4. Click Apply after check-marking the two boxes
5
6
@
n
ua
y
x
(
0
2
2
4
P
* Modify the content of the class in preparation of extensions for the
application
M
O
C
i
w
u
)
a
r.c
o
s
nd
1. Right click on BookStoreGUI
2. Choose to Add
3. Select Window (WPF)
4. Highlight Window (WPF) with C#
5. Type “MainWindow”
6. Click Add
7
8
@
n
ua
y
x
(
0
2
2
4
P
* Use the Designer Window to lay out the main window and specify the
values in the XAML file
M
O
C
i
w
u
9
)
a
r.c
o
s
nd
* Code the new class with desired functionality with “using BookStoreLIB”
being added to use classes in the other project
10
2. Click the icon in the cell under the Value column
M
O
C
3. Click Browse
4. Locate the provided database
5. Click Open
@
n
ua
y
x
(
0
2
2
4
P
1. Click Settings.settings under BookStoreLIB
i
w
u
)
a
r.c
o
s
nd
1. Click Start to run the application
2. Click Login
3. Try out the application by providing user information
4. Clicking OK should change the message according to the valid user
6. Click OK to connect to the database, which has more build-in tables as
illustrated in (7)
11
12
@
n
ua
y
x
(
0
2
2
4
P
* This activity diagram shows the sequence of activities for several of the
functionalities of the software under development
M
O
C
i
w
u
13
)
a
r.c
o
s
nd
* The path coverage of white-box testing can be applied to test the
interface of the software. Rather than coding a test method, this test
requires the software tester to interact with the software with specific inputs
so that the flow of control goes through the activities along an independent
path in the activity diagram
14