Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Table of Contents
Chapter and Topic
Page
No.
A.
Page 2 of 146
Types of Functions to be carried by the program:o Calculations-To find the quarters to be paid by the
owner for a year i.e. Quarters 1 and 2=25,000 paid,
remaining Quarter 3 and 4=15,000 to be paid
Page 3 of 146
Page 5 of 146
B. Design:
Designing a solution:
The implemented solution should be a comprehensive system
consisted at multiple levels and of varied importance. In order to
understand the working and the principles of the proposed
solution, the flow of data must be constantly observed.
Page 6 of 146
Key
Data Field
Data
Type
Size
(Bytes
)
Sample Data
Constraints
Primar
y Key
Apt No
Short
Text
Short
50
P3A2B
Alphanumeric
255
R.V.Venkatesh
Sq_Ft
Email ID
Integer
Long
Text
8
4
1633
Alternative
Contact
Long
Text
30
9789950512
Letters, Full
stops and
spaces
Numeric only
Alphanumeric,
Special
characters
Numeric only
Name_Of_Owner
venkat@netvigator.c
om
Page 8 of 146
List of Objectives
Page 9 of 146
Input Design
The Inputs needed from the user for the program to complete a
task are of two types:
o Pre-Entered Inputs-This type of input is where the
Administrator stores the payment details in a database and
links it to the main program. The data of the payment detail
will be fetched from the database by the program and is laid
on the report along with the maintenance due details.
o Live Input-In the case of searching contact details when
email service is unavailable. Edition of any contact details of
any of the apartments will also need live input from the user.
Page 11 of 146
Signature
_______________________________
Mockup1 shows the basic input design from the user which is
planned to be implemented in the main program package. This
mockup consists of features such as navigation control,
Modification and updating option, and Searching.
These features are included for easy management of controls,
efficient process of data fetching and sending which help the
Page 12 of 146
Page 13 of 146
Mockup 2:
Title
Header
Payment
Details for
Flat
Generate overall
reports
Search
details for
flat
Filter Paid
Owners
Combo
Boxes
Display
Sheets for
fetched
data.
Edit
Save
Exit
Dispatch via
Mail
Page 14 of 146
Command
Buttons for
edition and
Open MS Outlook
and keep Compose
Mockup 2: The image shows the layout in
which the design of the form will
mail ready for the
be generated.
Payment Details: The above image shows the form where data is inputted
in thePAY and GO TO of the form in order to fetch data from the database.
Page 15 of 146
Output Design
Page 16 of 146
Design Draft:-The above diagram depicts the layout in which the original
receipt must be produced by the program on behalf of LCM.
Page 17 of 146
In the layout provided above, the details present will include the
debit amount that is to be paid and the credit amount that is paid
by the owner. The owner will receive a receipt that will contain the
amount that is to be paid/received by either of the parties.
In order to reduce the complexity of the calculations and display
the necessary information that the owner requires, the draft was
designed, keeping in mind, to produce an Easy to Understand
Fetched data laid out
layout.
on report
Named Labels
Header Title
Mockup 3:
Apt
No:
Name of
Owner
Sq. Ft
Contact
Mockup 3: The image shows the draft of the layout for the creation of a
report which contains the contact information of all flats.
Page 18 of 146
Header Title
Time and
Date labels.
Named Labels
Fetched data
laid out
Mockup 4:
La Celeste Overall Maintenance Report
Date of
Generati
Apt
No.
10/09/2014
Time of
Generation
10:10 AM
Amount
Paid
Page Number
Page X of Y
Mockup 4: The image shows the draft of the layout of the data of owners
payment details of all flats
Page 19 of 146
The mockup draft was created primarily for the forms which were
of high importance. With the mockups drawn above, I will be
following those designs to produce the original forms in the new
system.
Menu/Module Design
1
2
3
4
5
6
User Login
Password Alteration
Apartment Information
Payment Details
Report Generation
Email Dispatch
Page 20 of 146
Page 21 of 146
Page 22 of 146
-------------------------------------------------------------------------------------------------USER LOGIN
MENU DESIGN
VIEW
GENERAL APARTMENT INFORMATION
MAINTENANCE DUE OF APARTMENTS
ACCOUNT SETTINGS
CHANGE PASSWORD
LOGOUT
EMERGENCY SHUTDOWN
ABOUT
VERSION NO.
HELP
USER GUIDE
EXIT SYSTEM
--------------------------------------------------------------------------------------------------
Page 23 of 146
C.
Schematics:
System Flowchart: The above diagram shows the primary concept of the
proposed systems workings.
Page 24 of 146
When a user enters the login credentials, the data inputted will
travel to the Login Module which will act as an intermediate
between the User and the Login Verification. The Login Module
will send an instruction to the Password Module and fetches them.
Unlike the Password Module, The Login Module sends the
Username to the Username Module for verification. The only data
Page 25 of 146
sent from the Username Module to the Login Module will be only a
simple instruction of Valid/Invalid. The reason behind this is due to
the existence of only one username.
But in the case of the Password Module, The Administrator has an
option to modify the password inside the program that is inputted
in the login screen. So, the password must be fetched and then
cross-checked with the user input.
After the Verification of the Username and Password from their
respective modules, an output to the user will be displayed
according to their input.
If the User credentials are valid, then an appropriate output
displaying that the credentials were valid will be outputted. After
this process, the user is taken to the Menu screen. But if the User
credentials are invalid, then the user will be alerted and will not
be allowed access.
After the User has inputted valid credentials, the user can proceed
with the generation of bill receipts according to the payment
details. This process consists of a great amount of data transfer in
and around the main program.
Page 26 of 146
Data Flow in the program: The diagram depicts the data that is
transmitted in and around the software during the process of production of
receipts and dispatch.
In the above data flow diagram, the depiction of the flow of data
in order to produce a notification when an entity pays the
maintenance due is shown.
The Entities refers to the payees who pay their maintenance
dues. After the entities pay their dues to LCM, They will have to
produce a receipt which notifies the Owner that the payment has
been received, mentioning the quarters details that are paid and
the amount to be paid in the future quarters.
Page 27 of 146
Page 28 of 146
MasterDB Table
Apt ID
Corresponds to
Payment details
PAYMENT Table
Output methods:
All outputs e.g. invoice receipt, Payment details etc which were
previously handwritten will now be in the form of criteria based
reports produced by the system in the form of *.html files which
can later be dispatched to the respective email ID. This makes the
output neat, accurate, and fast.
Storage:
All the records which were previously maintained using registers,
will now be replaced by Database filling system stored on hard
disk. A backup copy will be made daily to ensure 100% security of
data. Furthermore records that are not used over a period of time
will now be archived and stored on separate disks to allow excess
free storage space on the hard disk.
Limitations of The Scope of Solution:Even though the program contains a large number of merits, it
also contains some disadvantages that may prove to be a limiting
factor during the users operation.
The limitations of the scope of the solution are as follows: If large amount of data are to be processed (More than
100,000 records), The Computerized solution, along with the
Page 31 of 146
File Size Estimation:Total Number of bytes for one record in Table1= 50+255+8+4+30
347
Total Number of bytes for one record in
Table2=50+255+8+4+8+4(255)+ 4(8)=>1377
Total Number of records in 1 table of the database (fixed) => 425
Total Number of bytes in Table1 => 347*425=147,475
Total Number of bytes in Table2 => 585,225
Total Number of bytes in both Table1 and Table2=732,700
10% Space for Memory Allocation= (10/100)*732,700 =>73,270
Total Number of bytes => 73,270+732,700=805,970
Page 32 of 146
D.
Code Listing:
SUBMIT BUTTON:
A = Text1.Text
b = Text2.Text
Page 33 of 146
If A = "laceleste" Then
Open "C:\Users\Rajesh\AppData\Roaming\VBProj\pwd.dat" For
Input As #1
Input #1, variable1
//Opens the pwd.dat file and cross checks password
Close #1
End If
If b = variable1 Then
MsgBox "User Login Successful!",vbInformation, "Access Granted"
MDIForm1.Show
Unload Me
Else
MsgBox "Unsuccessful Login-Please try again!",vbExclamation,
"Access Denied"
Exit Sub
End If
Page 34 of 146
End Sub
CLEAR BUTTON:
SUBMIT BUTTON:
Private Sub Command1_Click()
Dim pdch, rtpdch, pass As String
If Text1.Text = "" Then
MsgBox "No,you need to type your old password before clicking
'Submit'", vbInformation, "Try Again"
End If
pdch = Text2.Text
If Len(pdch) >= 20 Then
MsgBox ("Hey,You've exceeded your limit on the characters of the
password"), vbExclamation
Text2.Text = ""
Exit Sub
End If
Page 36 of 146
rtpdch = Text3.Text
If pdch<>rtpdch Then
MsgBox ("Error Retyping Password.Please Try Again"),
vbExclamation
Exit Sub
End If
Open "C:\Users\Rajesh\AppData\Roaming\VBProj\pwd.dat" For
Input As #1
Input #1, variable1
// If the old password is correct, Then proceed to replace the
password
Close #1
xy = Text1.Text
If xy = variable1 Then
Open "C:\Users\Rajesh\AppData\Roaming\VBProj\pwd.dat" For
Output As #1
pass = Text2.Text
Print #1, pass
Close #1
MsgBox ("Password Successfully Changed"), vbInformation,
"Successful"
Exit Sub
End If
MsgBox "Your Old Password is Wrong", vbInformation, "Access
Denied-Password Change Unsuccessful"
Page 37 of 146
End Sub
CLEAR BUTTON:
EXIT BUTTON:
Private Sub Command3_Click()
Unload Me
End Sub
EXIT BUTTON:
Private Sub Command3_Click()
Unload Me
End Sub
Unload Me
End Sub
UPDATE DB BUTTON:
Combo1.AddItem DataEnvironment1.rsCommand1("APT_NO")
DataEnvironment1.rsCommand1.MoveNext
Wend
End Sub
CHANGE PASSWORD
Private Sub chngpwd_Click()
Form2.Show
End Sub
FORCE SHUTDOWN
Private Sub emshut_Click()
MsgBox ("Are you sure you want to exit?"), vbYesNo
If vbYes Then
Unload Form1
Page 42 of 146
Unload Form2
Unload Form3
Unload Form4
Unload Form5
Unload Form6
Unload Me
Else
End If
End Sub
ABOUT Option:
Private Sub liagmnt_Click()
MsgBox ("This is an Open-Source Project and is developed using
Microsoft Visual Basic 6.0 by Hayagrish.Any Illegal or Commercial
use of this Project by anyone other than the authorized Client
cannot be accepted")
End Sub
LOGOUT OPTION
Private Sub logout_Click()
Unload Me
Form1.Show
End Sub
Page 43 of 146
f = UCase(bank)
branch = InputBox("Enter Branch of the Bank")
If Asc(branch) <= 65 Then
MsgBox ("Please Enter alphabets Only"), vbCritical
Exit Sub
Else
End If
g = UCase(branch)
cheque = InputBox("Enter the Cheque Number")
If Len(cheque) <= 8 And
Len(cheque) >= 6 Then
Page 46 of 146
Page 48 of 146
DataEnvironment1.rsPAYMENT("TOTAL") =
(DataEnvironment1.rsPAYMENT("AMOUNT") +
DataEnvironment1.rsPAYMENT("OTHERS"))
End If
DataEnvironment1.rsPAYMENT("BALANCE") =
(DataEnvironment1.rsPAYMENT("AMOUNT") +
DataEnvironment1.rsPAYMENT("OTHERS")) DataEnvironment1.rsPAYMENT("AMTPAID")
DataEnvironment1.rsPAYMENT.Update
Exit Sub
Else
DataEnvironment1.rsPAYMENT.MoveNext
End If
Wend
Frame3.Visible = False
Set DataGrid1.DataSource = DataEnvironment1
DataGrid1.Enabled = True
Else
MsgBox ("Hey,You've entered an incorrect length of Cheque
Number"), vbExclamation
End If
DataEnvironment1.rsPAYMENT.Close
DataEnvironment1.rsPAYMENT.Open
End Sub
Page 49 of 146
DataEnvironment1.rsCommand1.MoveFirst
While Not DataEnvironment1.rsCommand1.EOF
DataEnvironment1.rsPAYMENT.AddNew
DataEnvironment1.rsPAYMENT("APT_NO") =
DataEnvironment1.rsCommand1("APT_NO")
DataEnvironment1.rsPAYMENT("SQR_FEET") =
DataEnvironment1.rsCommand1("sq_ft")
DataEnvironment1.rsPAYMENT("AMOUNT") =
DataEnvironment1.rsCommand1("sq_ft") * 2.60 * 12
'DataEnvironment1.rsPAYMENT("OTHERS") = 7000
DataEnvironment1.rsPAYMENT("AMTPAID") = 0
DataEnvironment1.rsPAYMENT("STATUS") = "P"
DataEnvironment1.rsCommand1.MoveNext
DataEnvironment1.rsPAYMENT.Update
Wend
DataEnvironment1.rsCommand1.Close
DataEnvironment1.rsPAYMENT.Close
Set DataGrid1.DataSource = DataEnvironment1
Else
MsgBox ("Invalid Credentials"), vbCritical
End If
End If
End Sub
Page 51 of 146
DataReport3.Show
End Sub
RESET PAYMENTS OF PAID MEMBERS button:
Private Sub Command13_Click()
MsgBox ("This will delete every data in fields")
DataEnvironment1.rsPAYMENT("BRANCH") = ""
DataEnvironment1.rsPAYMENT("CHEQUENO") = ""
DataEnvironment1.rsPAYMENT("BANK") = ""
DataEnvironment1.rsPAYMENT("QTR") = ""
DataEnvironment1.rsPAYMENT("STATUS") = "P"
DataEnvironment1.rsPAYMENT.Update
End Sub
Page 53 of 146
Page 54 of 146
GO TO Button:
Private Sub Command4_Click()
If Combo2.Text = "" Then
MsgBox "Please Enter the Flat Number", vbOKOnly
Exit Sub
Else
// Validating if the first letter as P
If Left(Combo2.Text, 1) <> "P" Then
Page 55 of 146
DEVELOPMENT OF DATABASE:-
Page 58 of 146
TABLE1: MasterDB
Layout View:
Page 59 of 146
Design View:
Page 60 of 146
TABLE2: OnlinePay
Page 61 of 146
Layout View:
Design View:
Page 62 of 146
TABLE3: Credits
Layout View:
Page 63 of 146
Design View:
Page 64 of 146
TABLE4:PAYMENTS
Layout View:
Page 65 of 146
Design View:
Page 66 of 146
Design View:
Page 67 of 146
In the program package, there is a need for manual input from the
users end in order for the program to operate according to the
users desired function. Some manual input functions include
security login, modification of data in the database, searching for
record from the database, password replacement and other
miscellaneous functions like navigation and basic input-mouse
clicks.
Since this program package was made using Microsoft Visual
Basic 6.0 and Microsoft Access as its primary developmental tools,
the program made using Visual Basic was then linked to the
Access database using a DataEnvironment Connection which is an
Page 68 of 146
Page 69 of 146
Clear button:In the case of wrong input into the text boxes,
this buttonclears out the existing input present in the text boxes
Exit button:Upon clicking this button, the program will
terminate.
MENU SCREEN:
Account Settings:
o Change Password-executes the form which allows the
authorized user to change his/her password
o Logout-closes all forms and menu and returns to the
login form
o Force Close: executes force closing of all processes by
closing all forms and menu of the program.It does not
display the login form and the user has to start the
program again
About:
o Version No.-outputs the information of how many
times this program was perfected to suit the clients
requirement
Help:
o User Guide-executes a word file which displays the
basic instructions needed to execute operations in the
program.
Page 71 of 146
Page 72 of 146
TEXT BOXES: Area of space where the old password and new
password strings are to be entered.
Submit button: executes the function of cross checking the old
password with the external password file. After verification
succeeds, the newly typed passwords are checked if both are the
same. After passing that, the data is appended to the password
file.
Clear button: clears the text boxes in the case of wrong input.
Exit button: Closes the password replacement form completely.
Page 73 of 146
Page 75 of 146
Page 76 of 146
Page 77 of 146
Page 78 of 146
Page 79 of 146
Page 80 of 146
Page 81 of 146
Page 82 of 146
Page 83 of 146
Page 84 of 146
Page 85 of 146
Menu-Force Close
Page 86 of 146
Page 87 of 146
Type
Size
Short
Text
Short
Text
50
Sq_ft
Email ID
Numbe
r
Long
Text
Alternative
Contact
Long
Text
30
255
Descripti
on
Flat ID No.
Example
Flat
Owners
Name
Sq.Ft of
flat
Email ID
of the
owner
Contact
Number
Jawahar.S
P1A1A
1985
Jawahars29@ashokleyland
.com
+919894276092
Page 88 of 146
Design View:
Layout View:
Page 90 of 146
Design View:
One to many
relationship between
MasterDB and
PAYMENT
Page 91 of 146
Page 92 of 146
Page 93 of 146
Menu form:
2
1
Password form:
Page 95 of 146
Payment Form:
Page 96 of 146
Page 97 of 146
Page 98 of 146
Page 99 of 146
Data Dictionary:
Field Name
Data Type
Description
APT_NO
Short Text
Flat ID No.
Name_of_Owne
r
Short Text
Sq_ft
Number
Sq.Ft of flat
Email ID
Long Text
Alternative
Contact
Long Text
Contact Number
APT_NO
Short Text
Flat ID No.
QTR
Short Text
DATE_of_Collect
ion
Date/Time
SQR_FEET
Number
AMOUNT
Currency
STATUS
Short Text
BANK
Short Text
CHEQUENO
Short Text
BRANCH
Short Text
AMTPAID
Currency
BALANCE
Currency
OTHERS
Currency
TOTAL
Currency
Navigational Paths:
E. TESTING
TEST STRATEGY:-
II
TEST PLAN:-
The table provided in the next page shows the data that will be
used for testing, its expected results, the actual results and the
actions that were taken if the actual results didnt match the
expected results:
Test
Type
Test
Data
Expecte
d
Results
Actual
Action
Results
Evidenc
e
Amount
Paid
Amount
Paid
Valid
50,000
50000
50,000
Pg.111
Extrem
e
100,000,0
00
100,000,00
0
1000000
00
Amount
Paid
Invalid
Cheque
Invalid
Input
Message
Please
Input
Numbers
Only as
Output
Message
Successful
Input
Successful
Input and
Size
allocation.
Comma
signs
removed
during
input.
success in
acceptanc
e of data
Successful
. Program
accepts
integers
only.
Terminate
s the
function
Pg.112
Pg.113,11
4
Bank
Name
Valid
Best Bank
BEST BANK
BEST
BANK
Bank
Name
Extrem
e
Best
BaNk.L.l.C,
CHeNnAi,i
NDia
Best
BaNk.L.l.C,
CHeNnAi,iN
Dia
Bank
Name
Invalid
9Best
B@nk.L.l.c
Invalid
Output
Message
Best
BaNk.L.l.
C,
CHeNnAi,i
NDia
Please
Enter
Alphabets
Only
Message
output.
Cheque
Number
Valid
A123456
A123456
A123456
Cheque
Number
Extrem
e
AW1234
AW1234
Cheque
Number
Invalid
AW123
Invalid
Cheque
length
Output
message
when
string
entered.
Successful
. lower
case
converted
to upper
caseautomatically
Successful
Input.
Pg.115,11
6
Pg.117,11
8
Successful
. Program
uses ascii
values to
filter
integers
and
strings.
Terminate
s after
output
message.
Successful
Input.
Pg.119,12
0
AW1234
Successful
input.
Pg.123,12
4
Incorrect
Length of
cheque
number
Output
message
Successful
. Program
verifies if
the length
of cheque
number is
>6 and
<8.
Pg.125,12
6
Pg.121,12
2
Terminate
s if
condition
false.
10
Quarter
Term
Valid
Q1
Q1
Q1
Successful
Input
Pg.127,12
8
11
Quarter
Term
Extrem
e
q1
Q1
Quarter
Term
Invalid
X1
Invalid
Input
Message
output
13
Searchin
g for Flat
Details
Valid
P1A1A
14
Searchin
g for Flat
Details
Extrem
e
p1C3B
Flat record
to be
pointed in
the
datagrid of
the form
Flat record
to be
pointer in
the
datagrid of
the form
Failed. I
Modified
the
program
to accept
q as Q
Successful
Input.
Verifies
the
starting
character
of string
to be Q
or q
Successful
Search.
Pg.129,13
0
12
Please
Input first
letter as
Q
Message
output.
Please
Input first
letter as
Q
Message
output
Success. I
changed
the
program
to convert
p to
upper
case and
continue
Pg.135
Pointer
Points
that
particular
record.
Pointer
did not
point at
the
record
Pg.131,13
2
Pg.133,13
4
search
15
Searchin
g for Flat
Details
Invalid
O2A14
Invalid
input
message as
output.
(Since first
letter
should be
P)
16
Searchin
g for Flat
Details
Valid
P4C3E
Pointer
must be
pointing to
that
particular
record
17
Searchin
g for the
Flat
Details
Extrem
e
P4c3E
Pointer
Must point
to that
particular
record
18
Searchin
g for the
Flat
Details
Invalid
P4F4G
Pointer
Must Not
Point at any
record(Sinc
e the 3rd
must be
Pointer
did not
point at
any of
the
record.
Remains
where it
was
pointed
before.
Pointer
Points to
that
record in
the
datagrid
of the
form.
Pointer
does not
point to
that
record
Pointer
did not
point at
record.
Successful
.
Pg.136,13
7
Successful
.
Pg.138,13
9
Failed.I
changed
the coding
to convert
3rd and 5th
letter to
upper
case and
continue
search.
Successful
. Since it
cross
checks
with the
database
Pg.138,13
9
Pg.140
below D
and 5th
letters
must be
below E)
and no
records
found,It
completes
search
function
Snapshots of Testing:-
Fig1.1: The above image shows the input of a valid data in the
PAYMENT Table.
Fig1.3: The above image shows the input of an extreme data into
the Payment Table
Fig1.4: The above image displays the input of the extreme data
stored in the PAYMENT Table
Fig1.5: The above Image shows the input of an invalid data into the
AMTPAID Field in the PAYMENT Table
Page 114 of 146
Fig1.6- The above image shows the invalid output message when a
string is entered into the AMTPAID Field of the PAYMENT Table
Page 115 of 146
Fig 2.1: The above image shows the input of a string into the BANK
Field of the PAYMENT Table
Fig2.2: The above image shows the valid input stored in the
PAYMENT Table
Fig2.3: The above image shows the input of an extreme data in the
Fig2.3: The above Image shows the stored input of an extreme data
in the PAYMENT Table. Note that the Extreme data is converted into
valid input by conversion into upper case letters.
Fig2.5: The above image shows the input of an invalid data into the
BANK Field of the PAYMENT Table.
Fig2.6: The above image shows the denial to store the invalid data
Fig3.1: The above image shows the input of valid cheque number in
the CHEQUENO Field of the PAYMENT Table
Fig3.2: The above image shows the stored valid input in the
PAYMENT Table in the database.
Fig 3.3: The input of an extreme data into the PAYMENT Table is
shown above.
Fig 3.4: The input of extreme data is stored in the PAYMENT Table.
Fig 3.5: An input of invalid data is entered into the PAYMENT Table
Fig3.6: The denial of invalid data due to short length into the
database is shown.
Fig 4.3:The above image shows the input of an extreme data which
is considered to be invalid data. The input of q1 lead to error.
Fig 4.4: The Above image shows the output when an extreme data
was considered to be invalid in nature. This error was corrected.
Fig 4.5: The above image shows the input of an invalid data in the
form to the database.
Page 132 of 146
Fig 5.1: The above image shows the movement of the pointer to a
particular record when a valid data is entered.
Fig 5.2: The above data shows no movement of the pointer when an
invalid data is entered. It remains at the previous record.
Before Correction:
Page 137 of 146
Fig 6.2: The above image shows the failure to show the record when
an extreme data was entered into the combo box of GO TO Field.
After Correction:
Page 138 of 146
Fig 6.2: The input of extreme data into the combo box of the GO TO
Field moves the record to that particular record when SHOW ME is
clicked.
Configuration Action
Processor-Core
i3,1.53 Ghz
RAM-2GB
OS-Windows 7
Professional
Processor-Core
i5,2.65 Ghz
RAM-3GB
GPU-2GB
OS-Windows
8.1 Pro
ProcessorRAM-1GB
OS-Windows 7
Home Premium
3.
Performance Testing:
Test table:
Page 142 of 146
Test
#
Configurati
on
Memory Usage
Action
ProcessorCore i3,1.53
Ghz
RAM-2GB
OS-Windows
7
Professional
6,796-27,944 KB
Maximum Memory
Used=27.289 MB
Minimum Memory
Used= 6.636 MB
Successful.
The Program
displayed no
signs of lags
or crashes
during runtime.
Processor-Core
i5,2.65 Ghz
RAM-3GB
GPU-2GB
OS-Windows
8.1 Pro
4710.4-16,327
Maximum Memory
Used=15.944 MB
Minimum Memory
Used=4.681 MB
3.
ProcessorCentrino 2
RAM-1GB
OS-Windows 7
Home
Premium
6,520-27,660 KB
Maximum Memory
Used=27.011 MB
Minimum Memory
Used=6.367 MB
Successful. The
Program ran
smoothly and
displayed a
small lag at the
start of the
program since
it was
searching for
the database
linked to the
program.
Successful. The
Program
displayed lags
but the
program
restored itself
back to normal
and carried out
the functions
perfectly
This is the third type of testing I will use to test my program. This
Testing is used to evaluate how the program behaves under
unfavorable conditions or beyond limits of specifications.
In this type of testing, I will take the highest memory used by the
program (Test 1 from performance table) and run the program
under harsh conditions. The Program will be made to use the
memory greater than the maximum memory used. The behavior
and the functionality of the program in this situation will be
tested. This is to ensure that the program does not crash during
my clients operation. This is to also check if the program
functions in any situation that is unfavorable.
Test Table
Test #
Size of
RAM
Load provided
on program
Progra
ms
Memory
Usage
Action
3GB
1540.61MB
30.06
MB
Under
input of
huge
amount of
data and
high load
on the
program,T
he
program
showed a
sign of
lagging at
first but
then
carried out
its
functions
Evidenc
e
properly.
From all the testing strategies used above. I conclude that the
program package is tested to be error-free and is ready to be
installed and run on the new system