Content: Hut - Genetic Singapore Joint Training Program Project 2010 - Group 73

HUT – GENETIC SINGAPORE JOINT TRAINING PROGRAM Project 2010 – Group 73
CONTENT
Part I:
Chapter I: System Introduction
1.1 Scenario.........................................................................................................4
1.2 The reason for choosing tools......................................................................6
1.3 Project schedule............................................................................................8
Chapter II: System Analysis
2.1 Function diagram (FD)................................................................................9
2.2 Data Flow Diagram (DFD)........................................................................11
2.2.1 Context diagram...................................................................................12
2.2.2 DFD level 0 for Function Diagram......................................................14
2.2.3 DFD level 1 for System........................................................................15
2.2.4 DFD level 1 for Management...............................................................16
2.2.5 DFD level 1 for Search.........................................................................17
2.2.6 DFD level 1 for View...........................................................................18
2.2.7 DFD level 2 for Report.........................................................................19
2.2.8 DFD level 2 for Account Management................................................20
2.2.9 DFD level 2 for Pupil...........................................................................21
2.2.10 DFD level 2 for Class.........................................................................22
2.2.11 DFD level 2 for Subject.....................................................................23
2.2.12 DFD level 2 for Pupil Subject............................................................24
Chapter III: System Design
3.1 Entity Relationship Diagram (ERD).........................................................25
3.2 Input Design (Record specification)..........................................................29
3.3 Output Design (List of output)..................................................................38
3.4 Program Design (Flow Chart)...................................................................40
3.4.1 Flow chart for Login............................................................................41
3.4.2 Flow chart for Add New Pupil’s information.....................................42
1 Emerald Primary School Management System

3.4.3 Flow chart for Add New Class’s information......................................43

3.4.4 Flow chart for Add New Subject’s information...................................44
3.4.5 Flow chart for Add New Pupil Subject................................................45
3.4.6 Flow chart for Delete Pupil’s information.......................................... 46
3.4.7 Flow chart for Delete Subject...............................................................47
3.4.8 Flow chart for Delete Class..................................................................48
3.4.9 Flow chart for Pupil Mark....................................................................49
3.4.10 Flow chart Edit Pupil’s information.................................................. 50
3.4.11 Flow chart for Edit Subject................................................................51
3.4.12 Flow chart for Edit Class....................................................................52
3.4.13 Flow chart for Pupil Mark..................................................................53
3.4.14 Flow chart Search Pupil’s information...............................................54
3.4.15 Flow chart for Search Pupil’s Mark...................................................55
3.4.16 Flowchart for Report..........................................................................56
3.4.17 Flow chart for View ..........................................................................57
Chapter IV: Program Testing
4.1 Test Plan......................................................................................................58
4.2 Test Data......................................................................................................59
Chapter V: Operating Introductions
5.1 Operating introduction..............................................................................60
5.2 Hardware Requirement.............................................................................60
5.3 Software Requirement...............................................................................60
5.4 How to install..............................................................................................60
Chapter VI: Conclusion
6.1 Scope and limitations.................................................................................61
6.2 Future development tendency...................................................................61
Part II:…………………………………………...……………………….. 62

Project Part I:
Emerald Primary School Management System

Chapter I: System Introduction
1.1 Scenario:
Nowadays, information technology has an important role in our
life. The more society develops, the more need of management
increase, such as when we want to develop or enlarge an organization
or a company, and we need efficient management system that helps us
to attain our desirable goal. To meet the need of management, many
computer programs is developed in many high level language that use
full for supplier to manage and customer to access. But also, we’re
student Genetic _ Ha Noi University of Technology join center with
almost different way to other Universities in Viet Nam. There’re a few
subjects buts they’re useful for our job in the future. And we can
approach to the new way in studying, the new technology of the world
Information Technology. To graduate, in the five year at the
university, we have to study and finish two projects two periods. It
will check your ability in the IT field. With the 3rd year student as us,
we have to finish the project with the following situation:
Emerald Primary School, located in the Dampening Ranges (50km
from Melbourne), Victoria, Australia. The school has offered an
unique place for the education of the children of the area for more
than 100 years, is the largest primary school and has an enrolment of
460+ pupils each year so to manage student’s mark and document is a
problem. Directors decide to develop an information system for
solving this.

The information system must have the following requirement:
Teacher must log on to use the program. Accounts of teacher are

1.
stored in the database.
The information system must have the following requirement:
Teacher can Input data, Edit data for pupil’s mark and information.
2.
Teacher can search information of pupil’s mark and ….
3.
Search pupil by pupil’s code
a)
Search pupil by pupil’s name
b)
Search pupil by pupil’s birthday
c)
Search pupil by pupil’s mark
d)
Teacher can view information of pupil:
4.
List all pupils’ information.
a)
List all pupils’ mark according to each subject.
b)
List all pupils’ information according each class.
c)
5. Teacher can generate the reports as following:
Generate report about pupil’s information. The report must

a)
display all information of pupil.
Generate subject’s report. The report must display all

b)
information of subjects and mark for each subject.
Generate report for marks of each pupil and calculate average

c)
mark.
User can backup and recovery the database.

6.
Group 73. D12 - I6
Participants: Regno:
Nguyen Duy Thanh 0701-013-0445
Nguyen Minh Thanh 0701-011-0633
Dau Thi Thanh Toan 0701-012-0396
Nguyen Thi Quynh Trang 0701-011-0648
So, with a program like this, we has to build this information system
with any programming language such as: VB.Net, C#, Visual Basic,
Java….and the database has been normalized in 3NF as the following, a
database such as: Microsoft Access, Structured Query Language (SQL
server), Oracle.…..After a long time we have made the decision the use
VB.Net as for programming language and Microsoft Access for database.
1.2 Reason for choosing the tool
Database:
There are a lot of tools manage such as: Microsoft Access, SQL
server, Oracle …. We choose Management System Access 2003 the
following reasons:
Easy to used Relation Database Management System.


It helps us to manage locate our records in a faster manner.

Data organization: involve creating and manipulating table that

contain data in conventional tabular.
Table linking and data extraction: link multiple tables by data


Relationships to create temporary tables.
Data entry and editing: require design and implementation of data


viewing, entry, and editing forms as an alternative to tabular presentation.

Data presentation: require the creation of reports that can


summarize the information in record set.
Macros: are sequences of action that automate repetitive database


operations.
Modules: are function and procedures written in the VBA


programming language.
Printing: lets us print virtually anything.


Programming language:
Besides, we use the programming language VB.Net 2005 because it’s
the programming language that widely used in Vietnam and it’s the first
GUI programming language that we study in the university. Moreover, it’s
compatible with Windows OS; it has hundreds of tools to help the
programmer easily to use it for programming, its GUI is nearly similar to
the Windows interface will make the user feel more familiar so they can
easily use it, too. And another reason that makes us choose it is because of
its features:
The “Visual” part refers to the method used to create the graphical
user interface (GUI).
The “Basic” part refers to the BASIC (Beginners All – Purpose
Symbolic Instruction Code) language, a language used by more
programmers than any other language in the history of computing. Visual
Basic has evolved from the original BASIC language and now contains

several hundred statements, functions, and keywords, many of which relate
directly to the Windows GUI.
The Visual Basic programming language is not unique to Visual Basic.
The Visual Basic programming system, Applications Edition included in
Microsoft Excel, Microsoft Access, and many other Windows applications
uses the same language.
Visual Basic developers need to get ready for the biggest transition
they have ever had to make. The next edition of VB, called Visual
Basic.Net, is designed to make web development as different languages.

1.3: Project Schedule
Figure 1.1: Table of Project Schedule
Task Time to
Planned Task Contents
# Accomplish
Complete Chapter 1(Introduction to
the system) included :
System + Scenario
February 23th -
requirements
1 February 28th + Reason for choosing tools.
analysis
(analyses user needs and user
requirements)
Complete Chapter 2(System analysis
and design part 1)included:
+ Context Diagram
System analysis March 1st - April
2
and design - Part 1 15th + Function hierarchy diagram
+ D.F.D
+ E.R.D
Complete Chapter 2(System analysis
h
System analysis April 16 - April and design part 2)included:
3 and design - Part 2 23th
+ Flow Chart
Converts the designs into the
complete information system
System includes acquiring and installing
April 24h - May 16th
4 Development system's environment; creating and
testing databases (test files, coding,
compiling....)
Demonstrates that developed system
conforms to requirements as
Integration and specified in the Functional
5 May 17th - May 22th
Test Requirements Document (includes
implementation preparation and
resolution of identified problems)
+ Complete all problems, print
Complete Project documents and Burn disks.
6 May 23th - May 26rd
and Submit
+ Prepare for presentation.

Chapter II: System Analysis
2.1 Function diagram (FD)

A functional diagram is used to show system’s functions that will be
constructed and the implementation process of data diagram. Function diagram will
also be used to determine the appearance frequency of smaller processes in the data
flow chart. A functional diagram only shows what to do know how to do. In a
functional diagram, a function is divided into many smaller functions and each
smaller function contains even smaller ones. Constructing diagram is a process of
division, from a higher function to appropriate smaller functions. Diagrams need to
be presented clearly, simply, exactly, fully and well-balanced. Function of the same
level has the same level of difficulty need to be on the same page.

10
1. System 2. Management 3. Search 4. View 5. Report
1.1 Account
Management
2.1 Pupil 3.1 Pupil’s 4.1 Pupil’s 5.1 Pupil’s
Mark Information Information
Add
Add 3.2 Pupil by 4.2 Pupil’s 5.2 Subject &
Edit Pupil’s code Mark Mark
Edit
Delete 4.3 Pupil’s 5.3 Marks of
3.3 Pupil by
Delete Info according each pupil &
Pupil’s name average mark
2.2 Class to each class
3.4 Pupil by
1.2 Backup
Add Pupil’s b-day
1.3 Recovery Edit 3.5 Pupil by

Pupil’s mark
Delete
2.3 Subject
Add
Edit
Delete
2.4 Pupil
Subject
Add
Edit
Delete
Figure 2.1: Function Diagram

11
2.2 Data flow diagram: (DFD)

DFD is one of the most important tools in a structured system
analysis. It presents method of establishing relationship between functions or
processes of the system with information it use.DFD is a key component of the
system requirement specification, because it determines what information is needed
for the process before it is implemented.
DFD is used to provide special description of requirement and system design.

It provides an overview of key functional components of the system but it does
not provide any detail on these components
There are 4 main components of data flow diagram. These include:
Process
Data Flow
Data Store
External Factor
Figure 2.2: Main components of Data Flow Diagram

12
Introduction about tool to draw diagram:
The process: The process shows a part of the system that


transforms inputs into outputs; that shows how one or more inputs are
changed into outputs.
The data flow: The flow is used to describe the movement of


information from one part of the system to another.
The data store: the store is used to model a collection of data


packets at rest
External factors: External factor can be a person, a group of


persons or an organization that are not under the studying field of the
system.
2.2.1 Context Diagram
A context diagram is a data flow diagram that shows the boundaries of the
information system. The context diagram is a top-level view of the information
system.
The first step in constructing a set of data flow diagrams for an
information system is to draw a DFD (Data Flow Diagram) called the
context diagram. A context diagram is a data flow diagram that shows the
boundaries of the information system. The context diagram is a top level
view of the information system.

13
Admin
Require
Emerald Primary Feedback

School Management
Require
System
Feedback
User
Fig
ure2.2: Context Diagram for “Emerald Primary School Management
System”.
Figure2.2: Is context diagram for “Emerald Primary School
Management System” (PSMS). The “PSMS” process and an external
entity is “Management”.
The data interactions between the information system and the external
entity occur through two deferent data flows. The “ Admin” external entity
supplies data through the “Requirement Info” data flow (which requires
information about: User, information of Pupils, Class, Subject) and
receives data through the “Feedback “

14
2.2.2 DFD level 0 for function diagram
tblPupil
tblClass
tblSubject
tblPupilSubject
tblUser
Feedback Require
System
User Feedback User
Require Feedback Require Feedback Require
Require Require Require

Require
Management Admin Report
Feedback
Feedback Feedback
Feedback
tblPupilSubject
tblPupil
tblSubject
tblPupil
tblClass
tblSubject
Feedback Feedback
tblPupilSubject
Require Require Require

Require
Search View
Feedback
Feedback
Require
Require
tblPupilSubject
tblPupilSubject
tblSubject
tblClass
tblClass
tblPupil
tblPupil
Feedback Feedback
User
Figure 2.3: DFD level 0 for function diagram
2.2.3 DFD level 1 for function System

15
Require
1.1
Account Tbl User
Management
Feedback
Feedback
Require
Feedback Feedback
Admin
1.3
1.2 Require Require
Recovery
Backup
tblUser
tblPupil
Require Require
tblClass
tblSubject
Feedback Feedback
tblSubject
Figure 2.4: DFD level 1 for function System
2.2.4 DFD level 1 for Management

16
Require Require
2.1 2.2
tblPupil tblClass
Pupil Require Require Class
Feedback Feedback
Feedback Feedback
Admin
Feedback Feedback
Require
tblPupil
Require
2.4 tblPupilSubject
tblSubject 2.3 Require Require
Pupil_ tblSubject
Subject Subject
Feedback Feedback
2.5: DFD level 1 for Management
2.2.5 DFD level 1 for Search

17
Require Require
Feedback
3.4
tblPupil
User Search pupil
Feedback by birthday
Feedback
Require
Require
Feedback
Require
Feedback
Feedback Require
3.3
3.2 Search
pupil by code
Admin Search pupil
Require Feedback
by name
Feedback
Require
Feedback
Require
tblPupil
Feedback
Require
User
Require Require
3.1 3.5
Search Pupil’s Search pupil
Feedback mark by mark Feedback
Require
Feedback
tblPupilSubject
tblPupilSubject
tblSubject
tblSubject
tblPupil
Require Feedback
User
Figure 2.6: DFD level 1 for Search

18
2.2.6 DFD level 1 for View
Feedback Feedback
User
Require Require
Require Require
4.1 4.2
View pupil’s Admin View pupil’s
Information Feedback Feedback mark
Feedback
Require
Feedback
Feedback
Require
Require
tblPupil
Feedback 4.3
View pupil
tblPupil
tblClass info according
to class
tblPupil tblSubject
Feedback
Require
tblPupilSubject
User
2.7: DFD level 1 for View
2.2.7 DFD level 1 for Report:

19
Feedback
5.1
Feedback
tblPupil
Generate
User report pupil’s
Require information Require
Feedback
Order
Feedback Feedback
Admin
Require
Require
tblPupil
5.2 Require Require 5.3
Generate report tblSubject Generate report
subject and pupil’s Mark and
mark
Feedback tblPupil_Subject Feedback
average Mark
Feedback Feedback
User
Require Require
2.8: DFD level 1 for Report
2.2.8 DFD level 2 for Account Management

20
Require
1.1.1
Create new tblUser
account
Feedback
Feedback
Require
Require Require
Admin
1.1.2 Feedback Feedback 1.1.3

Edit Account Delete Account
Feedback Feedback
tblUser
Order Order
2.9: DFD level 2 for Account Management
2.2.9 DFD level 2 for Pupil

21
Require
2.1.1
tblPupil
Add new Pupil
Feedback
Feedback
Require
Require Require
Admin
Feedback Feedback
Feedback Feedback
2.1.2 2.1.3
tblPupil Delete Pupil
Edit Pupil
Require Require
2.10: DFD level 2 for Pupil
2.2.10 DFD level 2 for Class

22
Require
2.2.1
Add new Class tblClass
Feedback
Require
Feedback Require
Require
Admin
Feedback Feedback
Feedback Feedback
2.2.2 2.2.3
tblClass Delete Class
Edit Class
Require Require
Figure 2.11: DFD level 2 for Class
2.2.11 DFD level 2 for Subject:

23
Require
2.3.1
Add new tblSubject
subject
Feedback
Feedback
Require
Require Require
Admin
Feedback Feedback
Feedback Feedback
2.3.2 2.3.3
tblSubject Delete Subject
Edit Subject
Require Require
Figure 2.12: DFD level 2 for Subject

24
2.2.12 DFD level 2 for Pupil_Subject
Order
2.4.1
Add new tblPupil_Subject
Pupil_Subject
Feedback Feedback
Order
Order Order
Admin
Feedback Feedback
2.4.2 Feedback Feedback 2.4.3

Edit tblPupil_Subject Delete
Pupil_Subject Order Order
Pupil_Subject
Figure 2.12: DFD level 2 for Pupil_Subject

25
Chapter III: System Design
3.1 ERD (Entity Relationship Diagram)

When developing a new information system, analyst often has
discussion with users, especially database manager, on the current system.
It’s they who have the responsibilities to collect necessary information
about the system required by system analyst. ERD is one of the most useful
models forming tools to organize this discussion. ERD is network model
that describes stored data of a system at a high level of abstraction.
The main components of an ERD include: Entity, Attribute and
Relationship
Entity is a subject, a duty, or an event that has a significant


meaning to the future system and displayed by a rectangle with round
corners. Each entity has its own name. In some case, entities of the same
port can be merged into one entity type. Entity type of a system is defined
base on the outcome of system function analysis.
Attributes are the characteristic of the entity displayed by fields or


columns of a table.
Relationship shows connections among the system’s entities.


Triangle head arrows display these connections. There are 3 major types of
relationship used in ERDs:
One - one relationship.


One - many relationship.

Many - many relationship.


26
. Introduce the function and Relationship of the fields in the database:
In our database, there’re 5 tables that include the entire field for the
information that used for the program. They are: tblPupil, tblClass,
tblSbject, tblPupil_Subject, and tblUser.
a. Table Pupil:
Table tblPupil contains the fields: with each Class ID define one class
name.
PupilID (primary key): define that the student is unique, and avoid
mistake with other students.
PupilName: describe the student name used to search, list, and sort the
result after processed.
ClassID: define the code of the Class.


PupilBirthday: Other detailed information of student.

PupilPhone: Other detailed information of student.

PupilEmail: Other detailed information of student.

PupilAddress: Other detailed information of student


27
Figure 3.1: Table Pupil Information
b. Table Class:
Table tblClass contains the fields: with each Class ID define one class
name.
ClassID (primary key): define the code of the class.


ClassName: define the class name.

Figure
3.2: Table Class
c. Table Subject:
Table tblSubject contains the fields:
SubjectID (primary key): define the code of the subject.


SubjectName: define the name of the subject.

SubjectHourNum: define the number of hour of subject.

Figure
3.3: Table Subject

28
d. Table Pupil and Subject Mark:
Table tblPupil_Subject (Mark) contains the fields: With couple key are
Subject ID and Pupil ID that define link relationship with table Pupil and
table Subject.
SubjectID: define the code of the subject.


PupilID: define the pupil’s code.

SubjectMark: define the mark of subjects of students.

Figure
3.4: Table Pupil_Subject
e.Table User:
Table tblUser contains fields: Username and Password. Define
authority that signs into system.
Figure 3.5: Table User

29
Relationship Diagram for PSMS:
Figure 3.6: Relationship Diagram for PSMS
3.2 Input Design

3.2.1 Record Specification
1. Table Pupil
Field name Data type Length Allow null Note
PupilID * Text 20 Primary Key
PupilName Text 50 Require
PupilBirthday Date/Time Require
PupilPhone Text 15 Require
PupilEmail Text 50 Require
PupilAdd Text 50 Require
MotherName Text 50 Require
MotherBirthday Date/Time Require
MotherPhone Text 15 Require
FatherName Text 50 Require
FatherBirthday Date/Time Require
FatherPhone Text 15 Require

30
ClassID Text 15 Require
2. Table Class
ClassID * Text 15 Primary Key
ClassName Text 50 Require
3. Table Subject
SubjectID * Text 15 Primary Key
SubjectName Text 50 Require
SubjectHourNum Number Require
4. Table Pupil_Subject
SubjectID * Text 15 Primary Key
PupilID * Text 15 Primary Key
SubjectMark Number Require
5. Table User
UserName * Text 10 Primary Key
Password Text 10 Require
Role Text 15 Require
3.2.2 Input Form Design

Login

31
Figure 3.7: Login form
Main

32
Figure 3.8: Main form
Account Management

33
Figure 3.9: Account Management form
Pupil Management

34
Figure 3.10: Pupil Management form
Class Management

35
Figure 3.11: Class Management form
Subject Management

36
Figure 3.12: Subject Management form
Mark Management

37
Figure 3.13: Mark Management form
3.3 Output Design

3.3.1: Report Pupil’s Information

38
3.3.2: Report Subject
3.3.3: Report Mark

39
3.4 Program Design (Flow Chart)

40
A Flow Chart is defined as a pictorial representation describing a process

being studied of even used to plan stages of a project. Flow Chart tends to provide
people with a common language or reference point when dealing with a project or
process.
The basic Flow Chart symbols:
Decision or
Process
Condition
Terminator
Input/Ouput
Data Flow
Figure 3.14: The Basic Flow Chart symbols
The Terminator: It represents the process to start and end Program.
The Process: Check and process data.
The Data: Store data that entered in program.
The Decision: It represents what users want to do by giving requirement

system.
The Data Flow: It is used to describe the movement information from one
part of system to another.
3.4.1 Flow chart for Login

41
Begin
Input
username
and
password
Check Account False Error

message
True
Check admin False

permission
True
Access system with Access system with

Full Control Limit Control
End
Figure 3.15: Flowchart for Login
3.4.2 Flow chart for Add New Pupil’s information

42
Begin
Input
Pupil’s data
Check pupil’s No Error

information message
Yes
No
Confirm Add ?
Yes
Stored Pupil’s
Information record
in database
Successful
End
Figure 3.16: Flowchart for add new pupil’s information
3.4.3 Flow chart for Add New Class’s information

43
Begin
Input
Class’s
data
Check class’s No Error

information message
Yes
No Confirm Add ?
Yes
Stored Class’s
Information record
in database
Successful
End
Figure 3.17: Flowchart for add new class’s information
3.4.4 Flow chart for Add New Subject’s information

44
Begin
Input
Subject’s
data
Check Subject’s No Error

Information message
Yes
No
Confirm Add ?
Yes
Stored Subject’s
Information record
in database
Successful
End
Figure 3.18: Flowchart for add new subject’s information
3.4.5 Flow chart for Add New Pupil_Subject

45
Begin
Input Pupil_
Subject
data
Check Pupil_
No Error
Subject’s
message
Information
Yes
No Confirm Add ?
Yes
Stored new Pupil_

Subject Information
record in database
Successful
End
Figure 3.19: Flowchart for add new subject’s information
3.4.6 Flow chart for Delete Pupil’s information

46
Begin
Input Pupil
ID
Check exist of No Error

Pupil ID message
Yes
Confirm Delete ?
No
Yes
Update Pupil’s
Information record
Successful
End
Figure 3.20: Flowchart for delete pupil’s information
3.4.7 Flow chart for Delete Subject

47
Begin
Input
Subject ID

Subject ID message
Yes
Confirm Delete ?
No
Yes
Update Subject’s
Information record
Successful
End
Figure 3.21: Flowchart for delete subject
3.4.8 Flow chart for Delete Class

48
Begin
Input Class
ID

Class ID message
Yes
No
Confirm Delete ?
Yes
Update Class’s
Information record
Successful
End
Figure 3.22: Flowchart for delete class
3.4.9 Flow chart for delete Pupil_Subject

49
Begin
Input Pupil
ID &
Subject ID
Check exist of Error

No
Pupil ID & Subject ID
message
Yes
Confirm Delete ?
No
Yes
Update Pupil_Subject’s
Information record
Successful
End
Figure 3.23: Flowchart for delete pupil mark
3.4.10 Flow chart Edit Pupil’s information

50
Begin
Input Pupil
ID
Check exist False Error

of Pupil ID message
True
Show
Pupil’s
information
No Confirm Edit ?
Yes
Update Pupil’s
information record
Successful
End
Figure 3.24: Flowchart for edit pupil’s information
3.4.11 Flow chart for Edit Subject

51
Begin
Input
Subject ID

of Subject ID message
True
Show
Subject’s
information
No Confirm Edit ?
Yes
Update Subject record
Successful
End
Figure 3.25: Flowchart for edit subject
3.4.12 Flow chart for Edit Class

52
Begin
Input Class
ID

of Class ID message
True
Show
Class’s
information
No Confirm Edit ?
Yes
Update Class record
Successful
End
Figure 3.26: Flowchart for edit Class
3.4.13 Flow chart for Edit Pupil_Subject

53
Begin
Input Pupil
ID and
Subject ID
Check exist
of Pupil ID and False Error
Subject ID message
True
Show
Pupil_
Subject’s
information
No Confirm Edit ?
Yes
Update Pupil’s mark

record
Successful
End
Figure 3.27: Flowchart for edit pupil’s mark
3.4.14 Flow chart Search Pupil’s information:

54
Begin
Input
keyword to
Search
Search Pupil’s
Information
Check exist of Pupil’s False Error

Information message
True
Show Pupil record
End
Figure 3.29: Flowchart for search pupil’s information
3.4.15 Flow chart for Search Pupil’s Mark

:

55
Begin
Input
keyword to
Search
Search Pupil’s Mark
Check exist of Pupil’s False Error

Mark message
True
Show Pupil’s Mark

record
End
Figure 3.30: Flowchart for search pupil’s mark
3.4.16 Flow chart for Report:

56
Begin
Select type
of Report
Generate Report
Display
Report
End
Figure 3.31: Flowchart for report
3.4.17 Flow chart for View:

57
Begin
Select type
of View
View information in
database
Display
Result
End
Figure 3.32: Flowchart for View
Chapter IV: Program Testing
4.1 Test Plan

58
Purpose of Test Test Data Expected Result
Test for open all input and All input and output records are
Valid/Invalid Data
output the records opened
All the records are read and

Test for read the record Valid/Invalid Data displayed the data that the record
contained
Test for adding the record
All new records are saved into
into table in Microsoft Access Valid/Invalid Data
tables in Microsoft Access 2003
2003
All input are written and saved to
Test for modifying the record Valid/Invalid Data
the specific records
Particular record is deleted and

Test for deleting the records Valid/Invalid Data
refresh the table
Test for the limitation of data Valid/Invalid Data To find out the limitation of data
Module Testing Run correctly
Integrate Testing Cooperate correctly
Whole program runs completely

Whole program testing Valid/Invalid Data
with all tested data

59
4.2 Test Data
1. tblPupil
Field name Valid data Invalid data
PupilID * 001 Over 15 characters
2. tblClass:
Field name Valid data Valid data
ClassID * 001 15
3. tblSubject:
SubjectID * 001 Over 15 characters
4. tblPupil_Subject:
SubjectID * 004 Over 15 characters
PupilID * 001 Over 15 characters
5. tblUser
UserName * Admin Over 10 characters
Password admin Over 10 characters
Chapter V: Operating Instructions

60
5.1 Operating Instructions

To run program, we firstly need to install the following package:
 Windows XP, Windows 2003, Windows Vista, Windows 7 (Choose one of
these).
 Microsoft .Net Framework 2.0
 Microsoft Jet Data Engine 4.0
5.2 Hardware Requirement

Components Minimum Recommend
Pentium Dual-Core or
CPU Pentium IV 1.8 GHz
higher
Disk Capacity 2 GB 4 GB
RAM 512 MB 1 GB or higher
Resolution 1024 x 768 1024 x 768
VGA 8 MB 8 MB or higher
Keyboard Yes Yes
Mouse Yes Yes
CDROM Yes Yes
5.3 Software Requirement

 Microsoft Access 2003
 Visual Studio 2005
CHAPTER VI: Conclusion

61
6.1 Scope and Limitations

6.1.1 Scope
 Interface is simple and easy to understand and use.
 Because we use Access to make database that provide family interface
to design database, it’s easy to change the information of database.
 Be easy to use.
 Have all the function required.
6.1.2: Limitations
 Not support online program.
 Only run on Windows 32bit
 We have not enough experience to design system, design database, so
our system design and database design can not sufficient.
 Our program does not run as smoothly as we expected.
6.2 Future Development Tendency
This program may be supported and upgraded for some new

programs which use for managing and accessing information,
so it can manage a large database and help people to access at
the same time.
Users or programmers can modify some feature of program to


make good some disadvantages as description above and
adding for shortcoming of the system.
This program can be expanded better to meet fully needs of


management along with information technology and human
knowledge or business so on…

62
Diploma Project - Part II:

Number 2
1.Link List
1.1 Introduction

63
Linked lists are among the simplest are most common data structures, they
provide an easy implemetation for several important abstract data structures,
including stacks, queues, hash tables, symbolic expressions , and skip lists.
The principal benefit of a linked list over a conventional array is that the order of
the linked items may be different from the order that the data items are stored in
memory or on disk. For that reason, linked list allow insertion and removal of node
at any poin in the list, with a constant number of operations.
On the other hand, linked list by themselves do not allow random access to the
data, or any form of efficient indexing. Thus, many basic operations --- such as
obtaining the last node of the list, or finding a node that contains a given datum, or
locating the place where a new node should be inserted--- many require scanning
most of the list elements.
Linked list can be implemented in most languages. Languages such as Lisp and
Scheme have the data structure built in, along with operations to acces the linked
list. Procedural languages, such as Java, typically reply on mutable references to
create linked lists.
1.2 Flow Chart for Link List
Adding Flow Chart
When you input element into link list,program will question that do you want
to add more elements.If you choose “ Yes”,you can add many othere elements.If
you choose “ No”,program will display all elements which you added into link list.
Begin
Input element for adding

into link list
64
Do you want to add more ?

No Show input line for adding
Yes
Add those elements into

link list
No
Display those elements on

screen
End
Adding – Link List
Deleting Flow Chart
When program displayed all elements, program will show function menu.You
can choose delete function.If you choose delete function, program will display line
that you must input elements to delete element.When program delete that
elemment,program will display remain elements after deleting.
Begin

65
Input element for deleting

into link list
Do you want to delete more ?

No
Show input line for deleting
Yes
Yes
Delete inputted
No
element
on screen
Display remain elements

on screen
End
Deleting – Link list

66

Content: Hut - Genetic Singapore Joint Training Program Project 2010 - Group 73

Enviado por

Dados do documento

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

Content: Hut - Genetic Singapore Joint Training Program Project 2010 - Group 73

Enviado por

Direitos autorais:

Formatos disponíveis

HUT – GENETIC SINGAPORE JOINT TRAINING PROGRAM Project 2010 – Group 73

1 Emerald Primary School Management System

3.4.3 Flow chart for Add New Class’s information......................................43

2 Emerald Primary School Management System

3 Emerald Primary School Management System

Chapter I: System Introduction

life. The more society develops, the more need of management

increase, such as when we want to develop or enlarge an organization

or a company, and we need efficient management system that helps us

to attain our desirable goal. To meet the need of management, many

computer programs is developed in many high level language that use

student Genetic _ Ha Noi University of Technology join center with

almost different way to other Universities in Viet Nam. There’re a few

Information Technology. To graduate, in the five year at the

university, we have to study and finish two projects two periods. It

we have to finish the project with the following situation:

Emerald Primary School, located in the Dampening Ranges (50km

from Melbourne), Victoria, Australia. The school has offered an

460+ pupils each year so to manage student’s mark and document is a

problem. Directors decide to develop an information system for

4 Emerald Primary School Management System

The information system must have the following requirement:

Teacher must log on to use the program. Accounts of teacher are

The information system must have the following requirement:

Generate report about pupil’s information. The report must

Generate subject’s report. The report must display all

Generate report for marks of each pupil and calculate average

User can backup and recovery the database.

Group 73. D12 - I6

Nguyen Duy Thanh 0701-013-0445

Nguyen Minh Thanh 0701-011-0633

Dau Thi Thanh Toan 0701-012-0396

Nguyen Thi Quynh Trang 0701-011-0648

Java….and the database has been normalized in 3NF as the following, a

database such as: Microsoft Access, Structured Query Language (SQL

VB.Net as for programming language and Microsoft Access for database.

1.2 Reason for choosing the tool

server, Oracle …. We choose Management System Access 2003 the

Easy to used Relation Database Management System.

Table linking and data extraction: link multiple tables by data

Data entry and editing: require design and implementation of data

6 Emerald Primary School Management System

Data presentation: require the creation of reports that can

Macros: are sequences of action that automate repetitive database

Modules: are function and procedures written in the VBA

Printing: lets us print virtually anything.

Besides, we use the programming language VB.Net 2005 because it’s

GUI programming language that we study in the university. Moreover, it’s

compatible with Windows OS; it has hundreds of tools to help the

programmer easily to use it for programming, its GUI is nearly similar to

user interface (GUI).

The “Basic” part refers to the BASIC (Beginners All – Purpose

Symbolic Instruction Code) language, a language used by more

programmers than any other language in the history of computing. Visual

7 Emerald Primary School Management System

several hundred statements, functions, and keywords, many of which relate

directly to the Windows GUI.

The Visual Basic programming language is not unique to Visual Basic.

The Visual Basic programming system, Applications Edition included in

Microsoft Excel, Microsoft Access, and many other Windows applications

uses the same language.

Basic.Net, is designed to make web development as different languages.

8 Emerald Primary School Management System