System Guide

HANOI UNIVERSITY OF SCIENCE AND TECHNOLOGY, VIETNAM GENETIC SINGAPORE - HUT JOINT TRAINING PROGRAM
------------HIGHER DIPLOMA IN COMPUTER STUDIES PROJECT 2013 (TEAM PROJECT)
CANDIDATE AND MARK MANAGEMENT SYSTEM (SYSTEM GUIDE) GROUP: 22 SUPERVISOR: Msc. VU THI HAU
PARTICIPANTS: NGUYEN THU HIEN (TEAM LEADER) HOANG THU HA NGUYEN THI NGOC HOA NGUYEN NGOC HUNG
REGNO: 0701-023-0139 REGNO: 0701-021-0159 REGNO: 0701-023-0131 REGNO: 0701-023-0108
Copyright Genetic Computer School, Singapore HANOI, VIET NAM Jun 2013
Mark and candidate management system

ACKNOWLEDGEMENT
System guide
Studying in Genetic Computer School for a long time, we have been well provided and imparted for all the necessary and high valuable of professional knowledge by our lecturers. Besides, we have our faithful, careful style and creative mind in studying and working. They are very necessary characters to gain successes in the next steps of our future. Project is a very good opportunity to examine our knowledge and promote our work group ability. During executing this project, we have received a lot of helping from our guides, teachers, and study- management department. Firstly, We would like to give special thanks to Msc. Vu Thi Hau for her great moral support; guidance and feedback enable us to complete this project.
Secondly, we wish to give our thankfulness to Mr. William Goh Principle of Genetic Computer School, Mr Nguyen Trung Dung Director of Hanoi Open University, Prof. Dr. Nguyen Thi Viet Huong. Moreover, we wish to give our thankfulness to all the teachers of Genetic Computer School, who gave us the knowledge and enthusiastically helped us in studying, Because our project cannot avoid some mistakes, we wish to sympathize to professors, lecturers. To make the criticism, suggestion of our teachers is the precious experiences for our actual work in the future. In addition, we wish respectfully our teachers healthy, happiness; achieve the great results in study and career of education. Extra special thanks our parents and all of our friends in D13 for their help. We would like to thank sincerely! Group 22 HUT Genetic Singapore International Join Program- 2013
HUT-Genetic Computer School
Group 22

TABLE OF CONTENT
System guide
CHAPTER I: SYSTEM SPECIFICATION ................................................................................ 3 1.1 SCENARIO...................................................................................................................... 3 1.2 INFRASTRUCTURE ...................................................................................................... 5 1.4 SCHEDULE OF PROJECT ............................................................................................. 6 1.5 METHOD OF INVESTIGATION ................................................................................... 7 1.6 UML (THE UNIFIED MODELING LANGUAGE) .................................................................... 9 1.6.1 USER CASE ................................................................................................................ 9 1.6.2 CLASS DIAGRAM .................................................................................................... 10 1.6.3 SEQUENCE DIAGRAM ........................................................................................... 14 1.6.4 ACTIVITY DIAGRAM ............................................................................................... 21 1.6.4.1 ADD NEW CANDIDATE ACTIVITY DIAGRAM ................................................ 22 1.6.4.2 ADD NEW MARK BY HAND ACTIVITY DIAGRAM.......................................... 23 1.6.4.3 ADD NEW MARK BY FILE ACTIVITY DIAGRAM .......................................... 24 1.7 DATABASE DESIGN (INCLUDING ERD) ................................................................ 37 1.7.1 Normalized Forms ................................................................................................. 37 CHAPTER 2: INPUT AND OUTPUT SPECIFICATION ....................................................... 43 2.1 FILE SPECIFICATION ................................................................................................... 43 2.2 RECORD SPECIFICATION ......................................................................................... 43 2.3 OUTPUT SPECIFICATION............................................................................................ 45 CHAPTER 3: PROGRAM DESIGN AND TESTING ............................................................. 46 3.1 PROGRAM DESIGN ...................................................................................................... 47 3.1.1 DECISION TABLE ................................................................................................... 47 3.1.2 UML (ACTIVITY DIAGRAM) ............................................................................... 50 3.2 PROGRAM TESTING .................................................................................................. 65 3.2.1 TEST PLAN ............................................................................................................... 65 3.2.2 TEST DATA............................................................................................................... 66 Table dbo.Info_Candidate ............................................................................................. 66 Tabledbo.Candidate_Code ............................................................................................ 66 Tabledbo.Mark .............................................................................................................. 66 Tabledbo.Subject ........................................................................................................... 67 CHAPTER 4: OPERATING INSTRUCTIONS........................................................................ 68 4. OPERATING INSTRUCTIONS ........................................................................................... 68 4.1 HARDWARE ARE REQUIREMENT ............................................................................ 70 4.2 SOFTWARE ARE REQUIREMENT .............................................................................. 71 CONCLUSION .......................................................................................................................... 72
Group 22

CHAPTER I: SYSTEM SPECIFICATION 1.1 SCENARIO
System guide
Phuong Dong University (PDU) was established since 1994. After nearly 20 years of construction and development, PDU has been continuously growing thousands of students each year. PDU has a periodic examination of Candidates who want to enter for PDU. Formerly, they managed all the information of candidates and their marks by manual. It took so much time but the effect is not good because the accuracy was low, cost high expense. Nowadays information technology has been developing dramatically and is one of the most important roles in our lives. With development of Information Technology, especially Internet, people can easily access information from anywhere, at any time they want. It also blurs boundaries, makes people closer as if they are face to face and sharing information become easiest than ever. Information technology is applied flexibly and creatively in many areas and it actually gets many amazing achievements. So Managers decide to create a system to manage candidates and marks automatically. In this project we choose PDU for our system to develop. However, it got many benefits in a short time, especially everyone can easily use. However, it has been taken place in a limited or small scale, which is impossible to meet the huge demand of customer, especially who are busy or far from the school. For these reasons, we built the project to give out the solution for solving the limitations. Our System mainly focuses on candidate and mark which help customers easily lookup scores they want just by one click on system everywhere event at home. The systems function: 1) (User)Admin must log on to use the program. Accounts of admin are stored in the database. 2) Admin can input data, edit data, delete data, view data about Candidates and Marks. 3) Admin can manage room-exam and subject. 4) Admin can search information of candidates and marks by many criteria: a. Search Candidates by Candidates code b. Search Candidates by Candidates name c. Search Marks by Candidates code d. Search Marks by Candidates name HUT-Genetic Computer School Group 22 3

e. Search Marks by Exam papers code. 5) Admin must create the following report: i. The quantity of register form(Sales/Register) ii. All Candidates marks (Print the notice about marks). The report must display the following information: 1. Candidates code. 2. Candidates full name. 3. DOB 4. Mark of each subject and sum of them. iii. Dispose candidates marks from higher to lower. iv. Report about list the Derogation examinee v. Generate candidates who pass the exam. The report must display the following information: 1. Candidates code. 2. Candidates full name. 3. Sex 4. DOB. 5. Mark of each subject and sum of them. 6. Specialty. 7. Address. vi. Ratio of candidates who pass the exam. vii. Advice note of candidates who pass the exam.
System guide
vii. Advice note of the beginning of term for candidates who pass the exam 6) Admin must manage the files of the beginning of term. 7) Admin can backup and recovery the database.
Group 22
System guide
1.2 INFRASTRUCTURE Genetic Computer School has 5 computer labs with 150 networked PCs that hook up to the school intranet. These computers also have direct Internet access. There is a server run by system administration and several computers used by school registrar staff. Meanwhile, centralized, multi-user functionalities are performed by the server. The database can be stored in a server for data safety.
Figure 1: Infrastructure for Candidate and Mark Management System
Group 22

1.4
System guide
SCHEDULE OF PROJECT Our project has been started at December 2012 and finished at 20th May 2013. Schedule
of project is represented as below:
PRELIMINARY INVESTIGATION (17 days)
SYSTEM ANALYSIS (28 days)
SYSTEM DESIGN (23 days)
CODING (27 days)
TESTING, MAINTENANCE AND DOCUMENTATION (15 days)
Group 22

1.5 METHOD OF INVESTIGATION
System guide
The using of some method for investigation is the first work before analyzing and designing programming. Although interviewing is the most commonly used, the others are also valuable and effective techniques for requirement determination. But we also use some other methods such as: Observation method: There are two kinds of observation methods o Official observation: Its not a good method to observe every single element while collecting information to develop system. The future system youre building up may be deemed to change the current way of working. Moreover, those youre looking at may be uncomfortable and may behave unusually, which will affect your surveys quality. o Unofficial observation: Researching through document is the final food method to get important. We choose unofficial observation method to collect data and develop our system. Survey methods: o The interview: An interview is a planned meeting during which you obtain information from another person. The process of interviewing consists of six steps: Determine who to interview Establish objectives for the interview Prepare for the interview Conduct the interview Document the interview Evaluate the interview o Questions: You should carefully choose the kind of question you will ask. As each kind of question serves a particular context, you will suffer if you choose it wrongly. You should take those questions which show your prediction and use the words that can help emphasize your idea. HUT-Genetic Computer School Group 22 7
System guide
Learn to know how to be quiet and listen to your interviewers. Dont present a question while he/she thinks or manage to answer a question. Dont try to ask in a way so as to lead the interviewee to your own direction, you wouldnt get much information that way. o Communications: The language you use and the way you talk about technical stuff should in some way create a close contact between you and the one youre interviewing. Questionnaire method: This method requires your clear instructions to the user. In general, this method is complicated and ineffective for inexperienced analyzers.
Group 22

1.6 UML (The Unified Modeling Language) 1.6.1 USER CASE
System guide
Introduce about Use Case A use case is a description of a systems behavior as it responds to a request that originates from outside of that system. The use case technique is used in software and system engineering to capture the functional requirements of a system. USE CASE diagram contains following elements: Actor may be a person or an external system that provides or receives information from the system. Use case is the function that the system performs General Use Case diagram symbol: <<Include >> Include e <<Extend >> Extend e
Association Use case
Generalization System boundary Use case: A use case represents a declaration of an offered behavior Association: An association represents the collaboration between an actor and a use case. Include: Include is a directed relationship between two use cases, which implies that the behavior of the included use case is inserted into the behavior of the including use case. Extend: Extend is a relationship between two use cases, which specifies how and when the extended use case insert the behavior defined in the extending use case. Actor: An actor specifies a role played by human users, external hardware, or other subjects that interacts with the subject System boundary: Represents the boundary of the subject Generalization: A generalization relationship relates a more general use case and a more specific use case. Group 22 9
Actor
System guide
GENERAL USER CASE
Main
Information of candidate management View Information of candidate
Manage Candidates code
View Candidates code Manage Room Exam View Room Exam Exam_paper_code View Exam_paper_code Mark management Admin View mark Search
User
Report
Report
Manage User
File of begin term management
Figure 1.1: General Use Case Diagram
1.6.2 CLASS DIAGRAM
Group 22
10
System guide
Class is a description of an entity group that has the same attributes, meanings, behaviors and relationship with others. Therefore, class is a form to create entities. Class diagrams are the most common diagram in modeling object-oriented systems. A class diagram shows a set of classes, interfaces and collaborations and their relationships. We use class diagrams to model the static design view of a system. For the most part, this involves modeling the vocabulary of the system, modeling collaborations, or modeling schemas. General Class Diagram Symbol: Class
<<Interface>> Class
Association Class Interface
Class: A class is a classifier that has objects as its instances. A class provides the template from which objects are created (instantiated). It also defines its attributes and operations.
Interface: An interface is a kind of classifier that defines a set of related public operations and responsibilities.
Association: An association specifies a relationship that appears between two classifiers.
Group 22
11

Administrator Login () <<Interface>> Administrator Manage_Candidates() Managet_Rooms() Management_Marks() Logout()
System guide
<<Intergace>> Manage Candidates - IDCard: Nchar - Candidate_LastName: Nvarchar - Candidate_FirstName: Nvarchar - DOB: Datetime -Sex: Text -Address: Nvarchar -Phone: Nvarchar -Speciality: Text - Notice: Ntext Add_new_candidate() Edit_candidate() Delete_candidate() Search_candidate()
<<Interface>> Manage Rooms -Rooms: Nchar -Place: Nchar -Date: Nchar -Time: Nchar Add_new_room() Edit_room() Delete_room() Search_room()
<<Interface>> Manage Mark -Exam_paper_code: Nchar -Mark: Nchar -Add_mark() -Exit()
Figure 1.2: System Administration class relationship diagram
Group 22
12

User Login () <<Interface>> User Manage_Candidates() Managet_Rooms() Management_Marks() Logout()
System guide
<<Intergace>> View Candidates - IDCard: Nchar - Candidate_LastName: Nvarchar - Candidate_FirstName: Nvarchar - DOB: Datetime -Sex: Text -Address: Nvarchar -Phone: Nvarchar -Speciality: Text - Notice: Ntext - View_candidate()
<<Interface>> Manage Rooms -Rooms: Nchar -Place: Nchar -Date: Nchar -Time: Nchar - View_room()
<<Interface>> Manage Mark -Exam_paper_code: Nchar -Mark: Nchar - View_mark()
Figure 1.3: User class relationship diagram
Group 22
13
System guide
1.6.3 SEQUENCE DIAGRAM Introduce about Sequence Diagram Sequence diagrams belong to a group of UML diagrams called Interaction Diagram. Sequence diagrams show the functional flows through the use cases. They describe the interactions between the objects and concentrate on describing the order of the messages by the time. So each function in the use case diagram would produce a sequence diagram. A single sequence diagram often represents the flow of events for a single use case. Instance: An instance of a class shows a sample configuration of an object. On the sequence diagram, each instance has a lifeline box underneath it showing its existence over a period of time. Actor: An actor is anything outside the system that interacts with the system. It could be a user or another system. Message: The message indicates communication between objects. The order of messages from top to bottom on your diagram should be the order in which the messages occur. Horizontal dimension shows Objects Vertical dimension shows time sequencing of object Object is shown as a vertical dashed line, its lifeline.
Group 22
14
System guide
General Sequence Diagram Symbol:
Lifeline
Call Message
Return Message
Lifeline
Self Message Actor
Lifeline: An individual participant in the Interaction. Call Message: A type of message which represents an operation call. Return Message: A type of message which represents an execution end and return to the caller.
Self Message: A type of message which represents the execution or operation call in the same lifeline.
Actor: Actor specifies a role played by human users, external hardware, or other subjects that interacts with the subject.
Group 22
15

LOGIN
System guide
Administrator
Login Form
Login Process
Database
1: Input Username and Password
2:Click btn_login
3: Login Process
4: Check Username and Password
5: Respond result
6: Successful and Notification
7: Error notification
8: Display login result
Figure 1.4: Login Sequence Diagram
Group 22
16

ADD NEW CANDIDATE
System guide
Administrator
Add Candidate Form
Add candidate Process
Database
1: Input candidate to Addnew
3: Check Validation 2:Click btn_add
4: Input process
5: Save to database
6: Respond result
8: Display Addnew result
Figure 1.5: Add New Candidate Sequence Diagram
Group 22
17

DELETE
System guide
Administrator
Delete Candidate Form
Delete candidate Process
Database
1: Chosse candidate to delete
3: Search candidate 2:Click btn_delete
4: Delete process
5: Save to database
6: Respond result
8: Display Delete result
Figure 1.6: Delete Sequence Diagram
Group 22
18

EDIT
System guide
Administrator
Edit Candidate Form
Edit candidate Process
Database
1: Chosse candidate to edit
2:Click btn_edit
3: Search and Check Validation
4: Edit process
5: Save to database
6: Respond result
8: Display Edit result
Figure 1.7: Edit Sequence Diagram
Group 22
19

SEARCH
System guide
Administrator
Search Candidate Form
Search candidate Process
Database
1: Input candidate to search
2:Click btn_search
3: Search process
5: Find into database
6: Respond result
8: Display search result
Figured 1.8: Search Sequence Diagram
Group 22
20

1.6.4 ACTIVITY DIAGRAM
System guide
An activity diagram which is related to program flow plans (flowcharts) is used to illustrate activities. In external view, we use activity diagrams for the description of those business processes that describe the functionality of the system. General Activity Symbol:
Initial Activity
Activity
Decision
Final Activity
Initial Activity: This shows the starting point or first activity of the flow. Denoted by a solid circle. This is similar to the notation used for Initial State.
Activity: Represented by a rectangle with rounded edges. Decision: a logic where a decision is to be made is depicted by a diamond. Final Activity: The end of the Activity diagram is shown by a bull's eye symbol,
also called as a final activity.
Group 22
21
System guide
1.6.4.1
ADD NEW CANDIDATE ACTIVITY DIAGRAM
Login Enter Username and Password Open dada connection
Error message
Invalid
Check Username and Password Valid
Enter information of candidate
Check validation
Check data exist

Yes
No Yes Continue No
Save to database
Figure 1.9: Add new candidate activity diagram
Group 22
22

1.6.4.2 ADD NEW MARK BY HAND ACTIVITY DIAGRAM
System guide
Error message
Invalid
Check Username and Password Valid Yes

No
Input mark data
Check data
Continue
Check mark correct
Mark isnt correct message
No
Yes Input new mark record
Figure 1.10: Add New Mark by Hand Activity Diagram
Group 22
23
System guide
1.6.4.3
ADD NEW MARK BY FILE ACTIVITY DIAGRAM
Error message
Invalid
Select criteria
Processing
Success message
Continue
No Yes Show mark record information action
Figure 1.11: Add new mark by file activity diagram
Group 22
24
System guide
1.6.4.3
EDITING ACTIVITY DIAGRAM
Error message
Invalid Valid
Check Username and Password
Yes Input data for editing No
Check data
Continue
Check data exist
Data doesnt exist message
No Yes Show and edit data
Continue edit
No
Yes Save record to data
Figure 1.12: Editing activity diagram
Group 22
25

1.6.4.4 DELETING ACTIVITY DIAGRAM
System guide
Error message
Invalid Valid
Yes Input data for deleting No
Check data
Continue
Check data exist
No
Yes Confirm deleting activity
No
Yes Delete record and save to database
Figure 1.13: Deleting activity diagram
Group 22
26

1.6.4.5 SEARCHIG ACTIVITY DIARAM
System guide
Error message
Invalid Valid
Yes No Select option
Input criteria to search
Continue
Check in data base
Check data exist
No
Yes
Show record inform action
Figure 1.14: Searching activity diagram
Group 22
27

1.6.4.6
System guide
DISPOSING CANDIDATES CODE AND NAME ACTIVITY DIAGRAM
Error message
Invalid Valid
Input/ select criteria
Process in database
Success message
Continue
No
Yes
Figure 1.15: Disposing Candidate Code and Name activity diagram
1.6.4.7
REGULAING ROOM-EXAM ACTIVITY DIAGRAM Group 22 28
System guide
Error message
Invalid Valid
Process in database
Success message
Continue
No
Yes
Figure 1.16: Regulating Room -exam activity diagram
1.6.4.8
REPORTING EXAMINEE LIST ATTEDING EXAMINATION ATIVITY DIAGRAM
Group 22
29
System guide
Error message
Invalid Valid
Yes Input required data No
Access/ process database
Continue
Show information
No Yes Show examinee list attending examination
View examinee list attending examination
Report examinee list attending examination
Figure 1.17: Reporting Examinee List attending examination activity diagram
Group 22
30

1.6.4.9
System guide
REPORTING ALL CANDIDATES MARK ACTIVITY DIAGRAM
Error message
Invalid Valid
Continue
Show information
No Yes
Show all candidates marks
View all candidates marks
Report all candidates marks
Figure 1.18: Reporting All candidate's mark activity diagram REPORTING DIAPOSE CANDIDATES MARK ACTIVITY DIAGRAM Group 22 31
1.6.4.10
System guide
Error message
Invalid Valid
Continue
Show information
No Yes
Show disposed marks
View disposed marks
Report disposed marks
Figure 1.19: Reporting Dispose candidate's mark activity diagram
1.6.4.11
REPORTING GENERATE CANDIDATE WHO PASS THE EXAM ACTIVITY DIAGRAM
Group 22
32
System guide
Error message
Invalid Valid
Search mark for candidate
Continue
Find mark for candidate
Error message
No Yes Show mark and candidate who pass the exam
View mark and candidate who pass the exam
Report mark and candidate who pass the exam
Figure 1.20: Reporting Generate candidate who pass the exam activity diagram
1.6.4.12
REPORTING LIST THE DEROGATION EXAMINEE ACTIVITY DIAGRAM
Group 22
33
System guide
Error message
Invalid Valid
Continue
Error message
No Yes Show candidates who derogate examinee
View candidates who derogate examinee
Report candidates who derogate examinee
Figure 1.21: Reporting List the Derogation examinee activity diagram
Group 22
34

1.6.4.13
System guide
REPORTING RATIO OF CANDIDATE WHO PASSES THE EXAM ACTIVITY DIAGRAM
Error message
Invalid Valid
Continue
Error message
No Yes
Show mark and average mark
View ratio of candidates who pass the exam
Report ratio of candidates who pass the exam
Figure 1.22: Reporting Ratio of candidate who passes the exam activity diagram
Group 22
35

1.6.4.14
System guide
REPORTING ADVICEOF CANDIDATES AND THE BEGINNING OF THE TERM OF CANDIDATES WHO PASS THE EXAM ACTIVITY DIAGRAM
Error message
Invalid Valid
Yes Input data No
Access to database
Continue
Insert data
Error message
No Yes
Insert
View all report
Report
Figure 1.23: Reporting Advice of candidates and the beginning of the term of candidates who pass the exam activity diagram
Group 22
36

1.7 DATABASE DESIGN (INCLUDING ERD) 1.7.1 Normalized Forms
System guide
Normalization is a process by which we identify and correct inherent problems and complexities in our record design. The Normalization is the process of normalizing entity tables through 1NF, 2NF, 3NF, and further. An entity table is in 1NF if, and only if, it contains no repeating groups. An entity table is in 2NF if, and only if, all of its must depend on the entire identifier of its entity or its value. In other words it is in 1NF and every non-key attribute is dependent on all parts of the primary key. An entity table is in 3NF if, and only if: it is in 2NF, and no non-key attribute is functionally dependent on another non-key attribute. This means that, every attribute must not depend on anything except the unique identifier of its entity for a value. Un-Normalization IDCard Candidate_LastName Candidate_FirstName DOB Sex Address Phone Speciality Candidate_Code Room Place Date Time Subject_code
Group 22
37

Subject_name Exam_paper_code Mark
System guide
1NF
IDCard Candidate_LastName Candidate_FirstName DOB Sex Address Phone Speciality Candidate_Code Room Place Date Time Exam_paper_code Subject_code Subject_name Mark
Group 22
38

2NF
System guide
IDCard Candidate_LastName Candidate_FirstName DOB Sex Address Phone Speciality
IDCard Candidate_Code Room Place Date Time
Exam_paper_code Subject_code Subject_name Candidate_Code Mark
Group 22
39

3NF Candidates Information Table in 3NF
System guide
IDCard * (PK) Candidate_LastName Candidate_FirstName DOB Sex Address Phone Speciality
Candidate Code Table in 3NF
IDCard * (PK) Candidate_Code (unique) Room
Group 22
40

Room exam Table in 3NF
System guide
Room * ( PK) Place Date Time Exam paper code Table in 3NF
Exam_paper_code * (PK) Candidate_Code Subject_code
Subject Table in 3NF
Subject_code * (PK) Subject_name
Mark Table in 3NF Exam_paper_code * (PK) Mark
Group 22
41

1.7.2 Entity Relationship Diagram
System guide
Figure 1.24: Entity Relationship Diagram
Group 22
42
System guide
CHAPTER 2: INPUT AND OUTPUT SPECIFICATION
2.1 FILE SPECIFICATION In this program, the Mark_Candidate_managementSystem file would be used when the user enter data into this file. The information is stored in Mark_Candidate_managementSystem file. So the input file is described as follow: Mark_Candidate_managementSystem File: FILE NAME FILE ID FILE ORGANISATION SQL MODE Mark_Candidate_managementSystem file Mark_Candidate_managementSystem.MDF SERIAL SERIAL
2.2 RECORD SPECIFICATION In this system, we have used SQL Server 2005 to store all data the user posted via internet to the system or updated, edit, temporary data do by this system members. The information are stored in tables on Mark_Candidate_managementSystem database file, this file would be used. So this file is the input files. Table Candidate
Group 22
43

Table Candidate_Code
System guide
Table Exam_paper_code
Table Mark
Table Room_Exam
Group 22
44

Table Subject
System guide
Table Users
2.3 OUTPUT SPECIFICATION Some main forms of program are shown:
Group 22
45
System guide
Group 22
46

CHAPTER 3: PROGRAM DESIGN AND TESTING
System guide
3.1 PROGRAM DESIGN 3.1.1 DECISION TABLE Decision table for LOGIN procedure Condition Stub 1. Valid username 2. Valid password 3. Continue Action Stub 1. Error message 2. Input data again 3. Access System X X X X Y Y Y Y Y N Y N Y Condition Entry Y N N N Y Y N Y N N N Y N N N
Action Entry X X X X X X X
Decision table for ADD NEW procedure
Condition Stub 1. Existing Data 2. Continue Action Stub 1. Error message 2. Input data again 3. Insert Database X X Y Y
Condition Entry Y N N Y N N
Action Entry X
Group 22
47

Decision table for EDIT procedure
System guide
Condition Stub 1. Data existing in record table 2. Continue 3. Edit data Action Stub 1. Error message 2. Input data again 3. Save data to database X X Y Y Y Y Y N Y N Y
Condition Entry Y N N N Y Y N Y N N N Y N N N
Action Entry X X X X X X
Decision table for DELETE procedure
Condition Stub 1. Data existing in record table 2. Continue 3. Delete confirmation Action Stub 1. Error message 2. Input data again 3. Delete data and save to database X X Y Y Y Y Y N Y N Y
Condition Entry Y N N N Y Y N Y N N N Y N N N
Action Entry X X X X X X
Group 22
48
System guide
Decision table for REPORT procedure
Condition Stub 1. find or show data 2. continue Action Stub 1. Error message 2. Input data again 3. Show, view and report data X Y Y
Action Entry X X X X
Decision table for SEARCH procedure
Condition Stub 1. Data existing in record table 2. Continue Action Stub 1. Error message 2. Input data again 3. Show, view and report data X Y Y
Action Entry X X X X
Group 22
49

3.1.2 3.1.2.1 UML (ACTIVITY DIAGRAM) ADD NEW CANDIDATE ACTIVITY DIAGRAM
System guide
Error message
Invalid
Enter information of candidate
Check validation
Check data exist

Yes
No Yes Continue No
Save to database
Figure 3.1: Add new candidate activity diagram
Group 22
50

3.1.2.2 ADD NEW MARK BY HAND ACTIVITY DIAGRAM
System guide
Error message
Invalid
Check Username and Password Valid Yes

No
Input mark data
Check data
Continue
Check mark correct
Mark isnt correct message
No
Yes Input new mark record
Figure 3.2: Add New Mark by Hand Activity Diagram
Group 22
51
System guide
3.1.2.3
ADD NEW MARK BY FILE ACTIVITY DIAGRAM
Error message
Invalid
Select criteria
Processing
Success message
Continue
No Yes Show mark record information action
Figure 3.3 Add new mark by file activity diagram
Group 22
52

3.1.2.4 EDITING ACTIVITY DIAGRAM
System guide
Error message
Invalid Valid
Yes Input data for editing No
Check data
Continue
Check data exist
No Yes Show and edit data
Continue edit
No
Yes Save record to data
Figure 3.4: Editing activity diagram
Group 22
53

3.1.2.5 DELETING ACTIVITY DIAGRAM
System guide
Error message
Invalid Valid
Yes Input data for deleting No
Check data
Continue
Check data exist
No
Yes Confirm deleting activity
No
Yes Delete record and save to database
Figure 3.5: Deleting activity diagram
Group 22
54

3.1.2.6 SEARCHIG ACTIVITY DIARAM
System guide
Error message
Invalid Valid
Yes No Select option
Input criteria to search
Continue
Check in data base
Check data exist
No
Yes
Figure 3.6: Searching activity diagram
Group 22
55
System guide
3.1.2.7 DISPOSING CANDIDATES CODE AND NAME ACTIVITY DIAGRAM
Error message
Invalid Valid
Process in database
Success message
Continue
No
Yes
Figure 3.7: Disposing Candidate Code and Name activity diagram
Group 22
56

3.1.2.8 REGULAING ROOM-EXAM ACTIVITY DIAGRAM
System guide
Error message
Invalid Valid
Process in database
Success message
Continue
No
Yes
Figure 3.8: Regulating Room -exam activity diagram 3.1.2.9 REPORTING EXAMINEE LIST ATTEDING EXAMINATION ATIVITY DIAGRAM HUT-Genetic Computer School Group 22 57
System guide
Error message
Invalid Valid
Continue
Show information
No Yes Show examinee list attending examination
View examinee list attending examination
Report examinee list attending examination
Figure 3.9: Reporting Examinee List attending examination activity diagram
Group 22
58

3.1.2.10
System guide
REPORTING ALL CANDIDATES MARK ACTIVITY DIAGRAM
Error message
Invalid Valid
Continue
Show information
No Yes
Show all candidates marks
View all candidates marks
Report all candidates marks
Figure 3.10: Reporting All candidate's mark activity diagram REPORTING DIAPOSE CANDIDATES MARK ACTIVITY DIAGRAM Group 22 59
3.1.2.11
System guide
Error message
Invalid Valid
Continue
Show information
No Yes
Show disposed marks
View disposed marks
Report disposed marks
Figure 3.11: Reporting Dispose candidate's mark activity diagram
3.1.2.12
REPORTING GENERATE CANDIDATE WHO PASS THE EXAM
ACTIVITY DIAGRAM HUT-Genetic Computer School Group 22 60
System guide
Error message
Invalid Valid
Continue
Error message
No Yes Show mark and candidate who pass the exam
View mark and candidate who pass the exam
Report mark and candidate who pass the exam
Figure 3.12: Reporting Generate candidate who pass the exam activity diagram
Group 22
61

3.1.2.13
System guide
REPORTING LIST THE DEROGATION EXAMINEE ACTIVITY
DIAGRAM
Error message
Invalid Valid
Continue
Error message
No Yes Show candidates who derogate examinee
View candidates who derogate examinee
Report candidates who derogate examinee
Figure 3.13: Reporting List the Derogation examinee activity diagram
Group 22
62

3.1.2.14
System guide
REPORTING RATIO OF CANDIDATE WHO PASSES THE EXAM
ACTIVITY DIAGRAM
Error message
Invalid Valid
Continue
Error message
No Yes
Show mark and average mark
View ratio of candidates who pass the exam
Report ratio of candidates who pass the exam
Figure 3.14: Reporting Ratio of candidate who passes the exam activity diagram
Group 22
63

3.1.2.15
System guide
REPORTING ADVICEOF CANDIDATES AND THE BEGINNING OF
THE TERM OF CANDIDATES WHO PASS THE EXAM ACTIVITY DIAGRAM
Error message
Invalid Valid
Yes Input data No
Access to database
Continue
Insert data
Error message
No Yes
Insert
View all report
Report
Figure 3.15: Reporting Advice of candidates and the beginning of the term of candidates who pass the exam activity diagram
Group 22
64

3.2 PROGRAM TESTING
System guide
3.2.1 TEST PLAN Testing accomplishes a variety of things, but most importantly it measures the quality of the project. The requirements section of the project specification does more than set benchmarks and list features. It also provides the basis for all testing on the product. After all, testing generally identifies defects that create, cause, or allow behavior not expected in the project based on descriptions in the specification. Specification writers should maintain the following standards when presenting requirements:

All requirements should be unambiguous and interpretable only one way. All requirements must be testable in a way that ensures the program complies. All requirements should be binding because customers demand them. Analyze each specification from the viewpoint of how well it supports the development
of test cases.
Purpose of test 1. Test for open all input and output file 2. Test for adding into the data.mdb file 3. Test for delete record
Test data
Expected Result All input and output file are opened All input are written to the specific files Particular record is deleted and refresh in data.mdb file Particular record is updated and refresh in data.mdb file File is read carefully and display the data that the file contained All process are performed successfully Whole program run successfully with test data
4. Test for update record
5. Test for read the file for output
6. Test for processing internal file 7. Test for whole program
Group 22
65

3.2.2 TEST DATA
System guide
Test data is a valid checking system of data, so we used some data for the program and have found what data is valid or invalid. Table dbo.Info_Candidate
Valid test data IDCard Candidate_ LastName 07010230145 Dang Tra Candidate_ FirstName My 6/10/1984 Female Bac Giang 0988303339 B DOB Sex Address Phone Speciality
Invalid data IDCard Candidate_ LastName 07010230145 Tabledbo.Candidate_Code Valid test data IDCard 0701-023-0145 Candidate_Code A101 Room 12 134 Candidate_ FirstName 568 6/10/1984 Female 232 098303339 B DOB Sex Address Phone Speciality
Invalid data IDCard 0701-023-0145 Tabledbo.Mark Valid test data HUT-Genetic Computer School Group 22 66 Candidate_Code A101 Room xyz

Exam_paper_code A1234 Mark 91
System guide
Invalid data Exam_paper_code A1234 Tabledbo.Subject Valid test data Subject_code Gs0011 Subject_name English Description Dsfshdlf232 Mark XT1
Invalid test data Subject_code Gs0011 Subject_name 34343 Description Dsfshdlf232
Group 22
67
System guide
CHAPTER 4: OPERATING INSTRUCTIONS
4. OPERATING INSTRUCTIONS
Firstly, your system must be installed .Net framework and SQL server 2005.Run setup to install program, window for setup will display and choose folder for new install program, and then click close to finish setup.
Group 22
68
System guide
Group 22
69
System guide
4.1 HARDWARE ARE REQUIREMENT 70
Group 22

Recommended Processor XEON Processor 1.8Ghz, 512KB-L2 cache (x1) or faster 512 MB (or higher) PC133 ECC SDRAM up to 4GB Seagate Cheetah 36.4Gb Ultra 160 SCSI 10.000rpm (x1) Minimum
System guide
Intel Pentium III 1.2Ghz (x1)
RAM
128 MB PC133 SDRAM
Hard-disk
40GB, 7200rmp, ATA100
4.2 SOFTWARE ARE REQUIREMENT Software is the program instructions that tell a computer what to do. It plays the main role of the information handling. As the software is written in C#, to execute and modify the program we need the following software installed: Windows 2000 or higher version SQL Server 2005(Database) Microsoft Visio 2003 or higher Microsoft Word 2007 or higher (Text Editor) At least 500 Mb free disk space .NET Framework
Group 22
71
System guide
CONCLUSION
EFFICIENCIES Professional management. Help officers manage information easy and limiting errors. LIMITATION In each project, developing is implemented through many specified phases before to be completed program. But beside positive aspects, its also existing negative aspects. These are shortcoming of designing, analysis, and initialize the program. Our project is not an exception: This system only use for an admin. It does not allow many people use. -This is a small program, so it can only be used for small or medium Offices. Small program, little function May have error when enter to many data. This program is only applied for single computer, so it does not support sharing data through Network or Local Area Network. If you want to use this program, you have to administrators account to manage. FUTURE DEVELOPMENT In future, we will development this system with larger scale, more functions, such as the average, memory are higher than.and user more than one admin
Group 22
72

System Guide

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

System Guide

Uploaded by

Copyright:

Available Formats

HANOI UNIVERSITY OF SCIENCE AND TECHNOLOGY, VIETNAM GENETIC SINGAPORE - HUT JOINT TRAINING PROGRAM

------------HIGHER DIPLOMA IN COMPUTER STUDIES PROJECT 2013 (TEAM PROJECT)

REGNO: 0701-023-0139 REGNO: 0701-021-0159 REGNO: 0701-023-0131 REGNO: 0701-023-0108

Mark and candidate management system

HUT-Genetic Computer School

Mark and candidate management system

HUT-Genetic Computer School

Mark and candidate management system

Mark and candidate management system

HUT-Genetic Computer School

Mark and candidate management system

Figure 1: Infrastructure for Candidate and Mark Management System

HUT-Genetic Computer School

Mark and candidate management system

of project is represented as below:

PRELIMINARY INVESTIGATION (17 days)

SYSTEM ANALYSIS (28 days)

SYSTEM DESIGN (23 days)

CODING (27 days)

TESTING, MAINTENANCE AND DOCUMENTATION (15 days)

HUT-Genetic Computer School

Mark and candidate management system

Mark and candidate management system

HUT-Genetic Computer School

Mark and candidate management system

Association Use case

HUT-Genetic Computer School

Mark and candidate management system

GENERAL USER CASE

Information of candidate management View Information of candidate

Manage Candidates code

File of begin term management

Figure 1.1: General Use Case Diagram

1.6.2 CLASS DIAGRAM

HUT-Genetic Computer School

Mark and candidate management system

Association Class Interface

Association: An association specifies a relationship that appears between two classifiers.

HUT-Genetic Computer School

Mark and candidate management system

<<Interface>> Manage Mark -Exam_paper_code: Nchar -Mark: Nchar -Add_mark() -Exit()

Figure 1.2: System Administration class relationship diagram

HUT-Genetic Computer School

Mark and candidate management system

<<Interface>> Manage Mark -Exam_paper_code: Nchar -Mark: Nchar - View_mark()

Figure 1.3: User class relationship diagram

HUT-Genetic Computer School

Mark and candidate management system

HUT-Genetic Computer School

Mark and candidate management system

General Sequence Diagram Symbol:

Self Message Actor

HUT-Genetic Computer School

Mark and candidate management system

1: Input Username and Password

4: Check Username and Password

6: Successful and Notification

8: Display login result

Figure 1.4: Login Sequence Diagram

HUT-Genetic Computer School

Mark and candidate management system

Add Candidate Form

Add candidate Process