computer science final year documentation sample

7/28/2019 computer science final year documentation sample

1/140

COMPUTRIZATION OF

EXAMINATOPN CONDUCT SYSTEM

By

Ali Goher

2007-GCUF-1253-526

Haroon Riaz

2007-GCUF-1270-526

Thesis submitted in partial fulfillment ofthe requirements for the degree of

BACHOLAR OF SCIENCEIN

COMPUTER SCIENCE

COLLEGE OF COMPUTER SCIENCE & INFORMATION STUDIES

GC UNIVERSITY, FAISALABAD.

July 2011


2/140

DECLARATION

The work reported in this project was carried out by us under the supervision of SirSalman Mansoor College of Computer Science & Information Studies GC University,

Faisalabad, Pakistan.

We hereby declare that the Computerization of Examination Conduct System

and the contents of project is the product of our own research. We further declare that thiswork has not been submitted for award of any other degree / diploma. The University

may take action if the information provided is found inaccurate at any stage.

Signature of the Student:

Registration No.: 2007-GCUF-1253-526

Signature of the Student:

Registration No.: 2007-GCUF-1270-526


3/140

CERTIFICATE BY THE PROJECT SUPERVISOR

This is to certify that Ali Goher Roll No. 2086 and Haroon Riaz Roll No. 2104 havesuccessfully completed the final project named as: Computerization of ExaminationConduct System, at the Department of Computer Science, GC University, Faisalabad, to

fulfill the partial requirement of the degree ofBS (SE).

Internal Examiner

Name: Mr: Salman Mansoor

Signature: ___________

External Examiner

Name: ______________________

Signature: ____________________

PrincipalCollege of Computer Science

& Information StudiesG.C. University Faisalabad

Coordinator Projects:


4/140

STATEMENT OF SUBMISSION

This is to certify that Ali Goher Roll No. 2086 and Haroon Riaz Roll No. 2104 havesuccessfully completed the final project named as: Computerization of Examination

Conduct System , at the College of Computer Science & Information Studies, GC

University, and Faisalabad, to fulfill the partial requirement of the degree ofBS (SE).

_____________________________ ________________________

Project Supervisor, Project Examiner

Designation DesignationCollege of Computer Science & Information Studies

GC University, Faisalabad


5/140

Acknowledgement

Firstly we are thankful to ALLAH ALMIGHTY who blessed us with knowledge to complete

this project with HIS mercy. We truly acknowledge the cooperation and help make by Name of

Mr:Salman Mansoor, teacher of G.C University Faisalabad for his help and guidance

throughout this project.. He has been a constant source of guidance throughout the course of this

project. We would also like to thankMr: Umar sarwar , Project Coordinator of Department

of Computer Science who helped us in requirement gathering and specification. We are also

thankful to our friends and families specially our father Dr: Muhammad Irshad Naseem and Riaz

Ahmed whose silent support led us to complete our project.

1- Ali Goher2- Haroon Riaz

Date: July, 7th, 2011


6/140

Summary

All the modules of Examination system had developed already but the Examination

Conduct System is still working manually. We want to computerize it. The conductsystem performs two types of duties. Internal Exam conduction External Exam

conduction

There are two types of external university exams. One is for Private candidates and other

is for affiliated colleges.

To provide stationary to the internal and to the external examination and maintaining all

concerned record is also the duty of conduct system. After the paper marking merit lists

are forwarded to the degree cell and the marked sheets are manually numbered and

placed in store room. This all record is maintained manually on the registers.

Conduct system will be a complete automatic system. The purpose of making this system

is to make our system totally computerize All the record will be entering in computerize

form. The manual data is transferred to data base. With the help of this we will be able to

submit our admission form via web link and this link is available on the site of GC

University Faisalabad. The cultists are maintained automatically. After that the date sheet

is saved on Data Base and uploaded on legal site of university, all the record of

employees (supretendent,depty superintendent, liners ,guards, peons etc),stationary

(answer sheets ,extra sheets, attendance sheets etc and others will be saved in data base

and assign to the concerned person. An automatic E-mail is sent by the system to the

concerned employee. After conduction of examination all the stationary is checked and

entered in the data base, if it is as it was in record then an automatic receipt is generated

for the concerned person & the merit lists are maintained and saved in data base, all the

result is forwarded to the degree cell and the Assigning employees for paper conduction.

All the data is save on registers marked answer sheets bundles will be sequence

numbered by software .No editing can occur after the first save.


7/140

Table of Contents

List Of figures: ................................................................................................................ i

List Of tables: ................................................................................................................. iiChapter No:1 ...................................................................................................................1

Software Requirement Specification ................................................................................1

1. The Purpose of the Project. ......................................................................................22. Client, Customer and other Stakeholders ..................................................................2

List of Stake Holders: ..............................................................................................2

Client and Customer Contact ...................................................................................2Users of the Product .................................................................................................2

4. Mandated Constraints: .............................................................................................24a. Solution design constraints .................................................................................2

4b. Implementation environment of the current system ............................................34c. Partner or collaborative applications ...................................................................3

4d. Off-the-shelf software ........................................................................................3

4e. Anticipated workplace environment ...................................................................3

4f. How long do the developers have for the project? ...............................................3 4g. What is the financial budget for the project? .......................................................3

5. Naming Conventions and Definitions .......................................................................36. Relevant Facts and Assumptions ..............................................................................3

List of Facts and Assumptions: ................................................................................37. The Scope of the Work ............................................................................................4

Existing System Scenario. ........................................................................................4Context Level Diagram ............................................................................................5

8. The Scope of the Product .........................................................................................6Reasons to develop this product. ..............................................................................6

Scope of product in market. .....................................................................................6

9. Functional Requirements .........................................................................................6List of requirements .................................................................................................69b. Description of each Requirement (Requirement Shell) .......................................7

10. Look and Feel Requirements ..................................................................................910a. The interface ....................................................................................................9

10b. The style of the product ....................................................................................9

11. Usability and Humanity Requirements ...................................................................9

11a. Ease of use. ......................................................................................................911b. Personalization and internationalization requirements ......................................9

11c. Ease of learning. ...............................................................................................911d. Understandability and Politeness requirements. .............................................. 10

11e. Accessibility requirements. ............................................................................. 1012. Performance Requirements .................................................................................. 10

12a. Reliability and Availability requirements ........................................................ 10.12b. Longevity requirements ................................................................................. 10

13. Operational Requirements .................................................................................... 1013a. Expected physical environment ...................................................................... 10

13b. Expected technological environment .............................................................. 1013c. Partner applications ........................................................................................ 10


8/140

14. Maintainability and Support Requirements ........................................................... 1114a. Maintenance requirements .............................................................................. 11

14b. Special conditions that apply to the maintenance of the Product ..................... 1114c. Adaptability requirements .............................................................................. 11

15 Security Requirements .......................................................................................... 11

15a. Access requirements ....................................................................................... 1116. Legal Requirements ............................................................................................. 1116a. Compliance requirements ............................................................................... 11

16b. Standards requirements .................................................................................. 1117. Open Issues .......................................................................................................... 12

18. Off-the-Shelf Solutions ........................................................................................ 1218a. Is there a ready-made product that could be bought? ....................................... 12

18b. Can ready-made components be used for this product? ................................... 1218c. Is there something that we could copy?........................................................... 12

19-New problems ...................................................................................................... 1219a. what new problems could the new product cause in the current environment? 12

19b. Will the new development affect any of the installed system? ........................ 1219c. Will any of our existing users be adversely affected by the new development?

.............................................................................................................................. 1219d. Will the new product create other problems? .................................................. 12

20. Tasks ................................................................................................................... 1220a. What steps have to be taken to deliver the system? ......................................... 13

21. Risks .................................................................................................................... 14Prepare Risk Management Plan. ............................................................................. 14

22. Costs .................................................................................................................... 1523.Schedule: .............................................................................................................. 16

GANT CHART: .................................................................................................... 1724 User Documentation and Training ......................................................................... 19

25 Waiting Room....................................................................................................... 1926 Ideas for Solutions ................................................................................................ 19

Chapter No:2 ................................................................................................................. 18Software Requirement Analysis ..................................................................................... 18

1. Abstract Level Use case Model .............................................................................. 192. Detailed Level Use Case Model ............................................................................. 20

Use Case: Admission Form .................................................................................... 20Use Case: Enter Data ............................................................................................. 21

Use Case: Verify Student ...................................................................................... 22Use Case: Confirmation to Sender ......................................................................... 23

Use Case: Manage Information .............................................................................. 243. Use Case Description (Detailed Level) ................................................................... 25

Use Case Name: Admission Form ....................................................................... 25Use Case Name: Enter Data ................................................................................... 27

Use Case Name: Verify Student .......................................................................... 28Use Case Name: Confirmation to sender ................................................................ 29

Use Case Name: Manage Information. ................................................................ 30System Sequence Diagram ......................................................................................... 32


9/140

Admission form ..................................................................................................... 32Enter Data .............................................................................................................. 33

Verify Student ....................................................................................................... 34Conformation to sender .......................................................................................... 35

Manage Information............................................................................................... 36

Domain Model ........................................................................................................... 37Chapter No:3 ................................................................................................................. 40Software Detail Design .................................................................................................. 40

Sequence Diagram ..................................................................................................... 41SD: Submit admission form: .................................................................................. 41

SD: main Interface: ................................................................................................ 42SD: return Resourses: ............................................................................................ 43

Class Diagram ........................................................................................................... 44Chapter No:4 ................................................................................................................. 47

Implementation.............................................................................................................. 471. Implementation ...................................................................................................... 48

1.1 Tools & Technology Used................................................................................ 481.2 Hardware Used ................................................................................................ 48

Chapter No:5 ................................................................................................................. 49Software Testing............................................................................................................ 49

Test Cases of Computerization of Examination Conduct System ............................... 50TC-1 (admission form)........................................................................................... 50

TC-2 Enter Data ..................................................................................................... 52TC-3 Verify Student .............................................................................................. 54

TC-4 Conformation to Sender ................................................................................ 56TC-5 Manage Information ..................................................................................... 58

Description: the requirement is to check all the record is manageable ............................ 58Appendix ................................ ....................................................................................... 61

How to Access (Start Using) System.......................................................................... 61Menu Available to User ............................................................................................. 62

Login ..................................................................................................................... 62Issue Roll No. slip .................................................................................................. 62

Staff Management .................................................................................................. 62Staff Allocation...................................................................................................... 62

Fee Updation ......................................................................................................... 62Manage Courses .................................................................................................... 62

Manage Datesheet .................................................................................................. 62Add Degrees .......................................................................................................... 63

Manage Exam Center ............................................................................................. 63Update Stationary .................................................................................................. 63

Cut List Generation ................................................................................................ 63How Menu Look and How to Interact/ Use System Components ............................... 64

Login: .................................................................................................................... 64Main page: ............................................................................................................. 65

Staff Management: ................................................................................................. 66Staff Allocation: .................................................................................................... 67


10/140

Fee Updation ......................................................................................................... 68Manage Courses .................................................................................................... 69

Manage Datesheet .................................................................................................. 70Report Of Date Sheet ............................................................................................. 71

Add Degrees .......................................................................................................... 72

Manage Exam Center ............................................................................................. 73Update Stationary .................................................................................................. 74Cut List Generation ................................................................................................ 75


11/140

i

List Of figures:

Figure 1: Context diagram ...............................................................................................5Figure 2: WBS(work breakdown structure) .................................................................... 13

Figure 3:Schedule .......................................................................................................... 16Figure 4:GANT chart ..................................................................................................... 18

Figure 5:Use case model ................................................................................................ 19Figure 6:Admission form(Use case model) .................................................................... 20

Figure 7:Enter Data(Use case) ....................................................................................... 21Figure 8:Verify student(Use case model) ....................................................................... 22

Figure 9:confirmation to sender(use case model) ........................................................... 23Figure 10:manage information(use case model) ............................................................. 24

Figure 11: SSD admission form ..................................................................................... 32Figure 12:SSD enter data ............................................................................................... 33

Figure 13:SSD verify student ......................................................................................... 34Figure 14:SSD confirmation to sender ........................................................................... 35

Figure 15:SSD manage information ............................................................................... 36

Figure 16: Domain Model of System ............................................................................ 37Figure 17:SD submit admission form ............................................................................. 41Figure 18:SD main interface .......................................................................................... 42

Figure 19:SD return resources ....................................................................................... 43Figure 20:Class diagram of system ................................................................................ 44

Figure 21:ERD of system............................................................................................... 46Figure 22:Login (interface) ............................................................................................ 64

Figure 23:Main page (interface) ..................................................................................... 65Figure 24:Staff management (interface) ......................................................................... 66

Figure 25:Staff allocation (interface) ............................................................................. 67Figure 26:Fee updation (interface) ................................................................................. 68

Figure 27:Manage courses (interface) ............................................................................ 69Figure 28:Manage date sheet(interface) ......................................................................... 70

Figure 29:report ............................................................................................................. 71Figure 30:add degree(interface) ..................................................................................... 72

Figure 31:Manage exam center(interface) ...................................................................... 73Figure 32:update stationary(interface) ............................................................................ 74

Figure 33:Cut List.......................................................................................................... 75


12/140

ii

List Of tables:

Table 1:Users of project ...................................................................................................2

Table 2:Naming Conventions ..........................................................................................3Table 3: req-01 ................................................................................................................7

Table 4: req-02 ................................................................................................................8Table 5: req-03 ................................................................................................................9

Table 6: ......................................................................................................................... 11Table 7:risk management plan ....................................................................................... 14

Table 8:Cost estimation ................................ ................................................................. 15Table 9: use case 1 ......................................................................................................... 26

Table 10 : Use case 2 ..................................................................................................... 27Table 11: Use case 3 ...................................................................................................... 28

Table 12:Use case 4 ....................................................................................................... 29Table 13: Use case 5 ...................................................................................................... 31

Table 14: TC 1............................................................................................................... 51

Table 15: TC 2............................................................................................................... 53Table 16: TC 3............................................................................................................... 55Table 17: TC 4............................................................................................................... 57

Table 18:TC 5 ............................................................................................................... 59


13/140

Software Requirements Specification

Chapter No:1

Software Requirement Specification


14/140

2


1. The Purpose of the Project.

All the data was on registers and its not so easy to manage the record, and to make thethings feasible and easy for the user to perform all the tasks regarding record

management.

2. Client, Customer and other Stakeholders

List of Stake Holders:

Student

Clerk

Director exam controller

Assistant exam controller

Accountant

Client and Customer Contact

041-9200000

Users of the Product

Sr. No User Roles and Responsibilities

1. Accountant Insert data

View reports

Manage Accounts

2. Director View Reports

Update data

3. Administrator To Maintain System

Table 1:Users of project

4. Mandated Constraints:

4a. Solution design constraints

core i3 2.4ghz 2gb(ddr3),320gb sata withWindows 7


15/140

3


4b. Implementation environment of the current system

The Product must be developed in C#.

4c. Partner or collaborative applications

There is no partner or collaborative application is involved.

4d. Off-the-shelf software

Application requires making the registration system online.

4e. Anticipated workplace environment

Healthy and supportive

4f. how long do the developers have for the project?

3 months

4g. what is the financial budget for the project?

Rs .24000

5. Naming Conventions and Definitions

Term used Definition

MIS Management Information System

SDLC System Development Life Cycle

Dir Director

Table 2:Naming Conventions

6. Relevant Facts and Assumptions

List of Facts and Assumptions:

1. It is assumed that all the users are familiar with tool and technology and it is forexpert users and they can easily deal with it.

2. All the network arrangements are according to the desire of application.


16/140

4


7. The Scope of the Work

Existing System Scenario.

All the modules of Examination system had developed already but the

Conduct System is still working manually. We want to computerize it. The

conduct system performs two types of duties. Internal Exam conduction

External Exam conduction

There are two types of external university exams.

For Private candidates.

For Affiliated colleges.

To provide stationary to the internal and to the external examination and

maintaining all concerned record is also the duty of conduct system. After

the paper marking merit lists are forwarded to the degree cell and the

marked sheets are manually numbered and placed in store room. This all

record is maintained manually on the registers.

Major works of conduct system are:- All the admission forms are submitted manually.

Cultists are maintained by employees.

Issuing date sheet.

Assigning employees for paper conduction.

Paper marking and merit lists.

Numbering record manually.

All the data is save on registers.


17/140

5


Context Level Diagram

Figure 1: Context diagram


18/140

6


8. The Scope of the Product

Reasons to develop this product

To make all the work computerize, to get rid from this manually fatigue working. To

make all the working easy and manageable.

Scope of product in market

As it is for govt.college university Faisalabad, all the system is confidential. Soscope of product in market does not exist here.

9. Functional Requirements

List of requirements

a.

Registration / Sign up

b. Send datac. Receive data/acknowledgementd. CRUD


19/140

7


9b. Description of each Requirement (Requirement Shell)

Req-01: Sign inRequirement # :Req-01

Requirement Type:Functional

Description Sign in

Rationale The Requirement is important because theClient/User has to sign in with the system .

Source Person Client/User

Fit Criterion The User will be signed in.

Customer Satisfaction:N/A

Customer Dissatisfaction:N/A

Dependencies N/A

Table 3: req-01


20/140

8


Req-02 Send data

Requirement # :Req-02


Description Send data

Rationale The Requirement is important because the

Client/User has to Send all his/her details.Source Person Student

Fit Criterion The details will be send.

Customer Satisfaction:N/A

Customer Dissatisfaction:N/A

Dependencies Sign Up

Table 4: req-02


21/140

9


Req-03: Receive data/info.

Requirement # :Req-03


Description Read data/infoRationale The Requirement is important because the

student will be acknowledged against his/hersending info.

Source Person user

Fit Criterion The user will read and send acknoweledgement

Customer Satisfaction:

N/ACustomer Dissatisfaction:

N/A

Dependencies Sign Up

Table 5: req-03

10. Look and Feel Requirements

10a. The interface

The look of the interface is sober. The color scheme used in it is not much stylish

as it is for exam conduct system, so the color scheme is just as it suits to the

system. All the items on the interface are visible.

10b. The style of the product

As it system is confidential so few but professional users will use it .we used

professional approach for this.

11. Usability and Humanity Requirements

11a. Ease of use.

As the users are professional, so no hurdle will come while working.

11b. Personalization and internationalization requirements

As it is confidential, and copy rights are reserve so if any to whom the exam centre team

will allow he/she can use it easily because its not difficult for the professional users.

11c. Ease of learning.

System is being used by the professional ones so nothing will be new thing for them.


22/140

10


11d. Understandability and Politeness requirements.

Interface is designed so clear that everything is visible, and the icons are designed in sucha way that by just seeing the icon the thing will be clear to the user.

11e. Accessibility requirements.

There is nothing like this available for this system as it is confidential.

12. Performance Requirements

12a. Reliability and Availability requirements

It is an online application, so thousands of users will access the Server at once sowe have to use a Strong Server and a Modem that has maximum connections limitand it is available even network is congested. It is also available at low band

width.

Browser compatibility will be handles.

System will be flexible.

Data recovery will be high.

Database will response quickly

12b. Longevity requirements

We will use SQL and C# because these are the latest development languages soour system will perform its working for minimum 20 years.

13. Operational Requirements

13a. Expected physical environment

The product will be run in highly confidential environment

13b. Expected technological environment

As it is for professional users so the technological environment is healthy

13c. Partner applications

We must be able to interface with any html browser.


23/140

11


14. Maintainability and Support Requirements

14a. Maintenance requirements

Maintenance is the most necessary part of the product; the system will be maintainableenough that if any type of modernization is required, it can be updated without disturbing

other modules.

14b. Special conditions that apply to the maintenance of the Product

The updated release will be offered to customer once in year for one without any cost.

14c. Adaptability requirements

The product is designed to run in offices. The product is expected to run under Windows

7.

15 Security Requirements

15a. Access requirementsUser Access

Administrator Authorized Access to all components of the

Product.

User Sign Up.

Send conformation to user

Enquiry to the schedule

Update Information.

Manage record

Table 6:

16. Legal Requirements

16a. Compliance requirements

Whole system shall not violate any tax policy imposed by the Government.

16b. Standards requirements

The product shall comply with College of Computer Science and Information Studies

standards.


24/140

12


17. Open Issues

There is a chance that the government college university can make change in examsystem procedure which will yield a problem in the product.

18. Off-the-Shelf Solutions

18a. Is there a ready-made product that could be bought?

No there is nothing to bought to implement this application

18b. Can ready-made components be used for this product?

This is total confidential so nothing can be add from outside and nothing is similar to theproduct is available .As it is confidential so nothing can be brought from outside

18c. Is there something that we could copy?

Nothing can be copied from anywhere because the product is unique and confidential.

19-New problems

19a. what new problems could the new product cause in the current

environment?

Problems will occur iff the user is naive or the professional user is careless and

irresponsible.

19b. Will the new development affect any of the installed system?

As I mentioned above that all the previous data managing was manual, so it is a new

product to manage all the system in computerized way.

19c. Will any of our existing users be adversely affected by the newdevelopment?

No, nothing will affect him hard well it will be easy for the user, as all working will be

done in computerize form.

19d. Will the new product create other problems?

As the product is confidential so just responsibility is require then no problem will occur.

20. Tasks


25/140

13


Figure 2: WBS(work breakdown structure)


26/140

14


21. Risks

Prepare Risk Management Plan.

Risk Probability(0-1)

Impact(1-10)

Risk factor(Probability

* Impact)

Responsibility

MitigationSteps

InexperienceStaff

0.8 3 0.8*3 = 2.4 ProjectManager

SignalProblem

0.8 7 0.8*7 = 5.6 User Check Mobileor change Area

or Location.

Signal

Problem

0.8 7 0.8*7= 5.6 Internet

ServiceProvider

Contact with

ServiceProvider.

ConnectionEstablished

0.7 6 0.7*6= 4.2 ProjectManager

CreateConnection.

Text format

not readable

0.6 5 0.6*5= 3.0 Sender Request to

change theformat.

Involvement

of newtechnology

0.5 5 0.5*5= 2.5 Project

Manager

Ensuring all

detailspertaining to the

technology isavailable and

keeping in closetouch with the

technologyvendor.

Browser

compatibility

0.7 4 0.7*4=2.8 Project

manager

Valid CSS use

for project

Internet Un

Availability

0.7 6 0.7*6+=4.2 Internet

ServiceProvider

Contact Internet

service provider

Table 7:risk management plan


27/140

15


22. Costs

Information Low Medium High Total

User inputs 1 * 3 = 3 1* 4 = 4 2 * 6 = 12 19

User outputs 0 * 4 = 0 0* 5 = 0 2 * 7= 14 14User inquiries 0 * 3 = 0 0* 4 = 0 1 * 6 = 6 6

Internal files 2 * 7 = 14 2 * 10 = 20 3 * 15 = 45 79

Externalinterfaces

0 * 5 = 0 0 * 7 = 0 2* 10 = 20 20

TOTAL UNADJUSTED FUNCTION POINTS (TUFP) 138

Sr. # General System Characteristics Degree of Influence Value

1 Data Communication 5

2 Distributed Functions 1

3 Performance 4

4 Heavily Used Configuration 3

5 Transaction Rate 4

6 On-line Date Entry 4

7 End-User Efficiency 3

8 Online-Update 4

9 Complex Processing 2

10 Reusability 3

11 Installation Ease 1

12 Operational Ease 213 Multiple Sites 0

14 Facilitates Change 2

Total GSC 38

Table 8:Cost estimation

VAF = (0.65+ [0.01 * Sum of Fi])

= (0.65+ [0.01 * 38)= (0.65+0.38)

= 1.03FP = TUFP * VAF

= 138*(1.03)= 142

Cost of 01 F.P = 200Cost of 142 F.P = 142 *200

=28400So 28400 is cost of project and including all expenses its cost will be 40000.


28/140

16


23. Schedule:

Figure 3: Schedule


29/140

17


GANT CHART:


30/140

18


Figure 4:GANT chart


31/140

19


24 User Documentation and Training

User documentation will be provided for the easiness of administrator. User

documentation will help him out about the system. There will be no training for the user.

25 Waiting Room

If any kind changes occurs in the exam system then modules can be added in it , to meet

future needs.

26 Ideas for Solutions

The product is confidential, so it should be handling with care.


32/140

Software Requirement Analysis

Chapter No:2



33/140

19


1. Abstract Level Use case Model

enter data

verify student

conformation to sender

manage information

admin

fee paymentadmission form

send documents

Figure 5:Use case model


34/140

20


2. Detailed Level Use Case Model

Use Case: Admission Form

Figure 6:Admission form(Use case model)

Degree Info

personal info

previous examination record

selection of subjects

fee paid

admin


35/140

21


Use Case: Enter Data

Figure 7:Enter Data(Use case)

exam center

staff

date sheet

chalan fee

stationary

admin

courses


36/140

22


Use Case: Verify Student

type of admission

student info

chalan fee

admin

sign up

type of admission

student info

chalan fee

admin

sign up

Figure 8:Verify student(Use case model)


37/140

23


Use Case: Confirmation to Sender

type of admission

student info

admin

sign up

type of admission

admin

sign up

student info conformation of student

Figure 9:confirmation to sender(use case model)


38/140

24


Use Case: Manage Information

Create Record

Delete Record

Update Record

Admin

View Record

Figure 10:manage information(use case model)


39/140

25


3. Use Case Description (Detailed Level)

Use Case Name: Admission Form

UC # 01 Ref: Req. # 01

UC Name Admission formLevel Detailed.

Description The User will fill admission form.

Actor (s) Student

Stakeholders Admin, Govt., Bank

Preconditions The student has

1. BrowserSuccess Guarantee The student will be Registered to our server through online

website.

Main Success

Scenario

Action Response

1. The student enters the

Address of Sign Up page.

2. The browser opens the

requested page.

3. Student entered degree

info, personal info, Previous

examination record, selection

of subject, fee paid and other

relevant info and click submit

button.

4. The Student data will be

stored in the Database and the

User will be Registered.

Extensions 3.1. If the Student entered

give any wrong record.

The System will generate an

error message invalid user

please enter correct

information.

3.2. If the Student miss some

required information.

The System will generate an

error that complete that

specific information.


40/140

26


4. If the Server is down or

crashed.

The System will show

message in browser that the

Server is down or crashed

please try after some time.

Special requirements N/A

Frequency of

Occurrence

Multiple Times in a day.

Table 9: use case 1


41/140

27


Use Case Name: Enter Data

UC # 02 Ref: Req. # 02

UC Name Enter Data

Level Detailed.

Description Admin will enter all the record after making sure that all record

is valid or nothing mismatches.

Actor (s) Admin

Stakeholders Student, Senior staff

Preconditions The Admin

1. Must Sign up.2. Has knowledge about predefined format

Success Guarantee The User will receive a message of request in progress

Main Success

Scenario

Action Response

1. When data has entered. 2. A message will come

successfully entered

Extensions 2.1. If the internet is not

working.

The System will not send any

message of conformation to

applicant.2.2. If the Server is down or

Server is crashed.

The System will not response

and does not send any

message.

Special

requirements

An internet connection is necessary

Must have an internet connection

Frequency of

Occurrence


Table 10 : Use case 2


42/140

28


Use Case Name: Verify Student

UC # 03 Ref: Req. # 03

UC Name Verify Student.

Level Detailed.

Description Details sent from Student will be matched from the database

Actor (s) Admin

Stakeholders Student, senior staff, Bank

Preconditions The Internet connection is in working state.

The Admin

1. Must Sign up.2. Has knowledge about predefined format.3. Authorized

Success Guarantee The details have been matched with the database the server

successfully.

Main Success

Scenario

Action Response

1. When the details has been

sent.

2. The Server will match the

message using database.

Extensions 2.1. If the internet is not

responding.



message.

2.2. If the Server is down or

Server is crashed.



message.

Special

requirements

Internet connection is necessary.

Frequency of

Occurrence


Table 11: Use case 3


43/140

29


Use Case Name: Confirmation to sender

UC # 04 Ref: Req. # 04

UC Name Confirmation to sender

Level Detailed

Description The confirmation of sender will be done by server.

Actor (s) Admin

Stakeholders Admin, Bank, senior staff, Student

Preconditions The Admin

1. Must Sign up.2. Authorized.

Success Guarantee Student will receive a conformation message.

Main Success

Scenario

Action Response

1. When details are being

received.

2. The Server will match the

message using database

2.1. If the internet is not

responding.

The System will not send any

message.

2.2. If the Server is down or

Server is crashed.


and does not send anymessage.

2.3. if the applicant doesnt

fall under requirements

The system will send a

message of better luck next

time

Special

requirements

An internet connection is necessary.

Frequency of

Occurrence


Table 12:Use case 4


44/140

30


Use Case Name: Manage Information.

UC # 05 Ref: Req. # 05

UC Name Manage Information.

Level Detailed.

Description Admin can manage his all record.

Actor (s) Admin.

Stakeholders Student, GOVT. , Senior staff

Preconditions The admin

1. Must Sign Up.2. An expert

Success Guarantee All record will be changed and updated, deleted and stored in

Database.

Main Success

Scenario

Action Response

1. The User Sign In. 2. The Server opens the main

page.

3. Admin clicks Update

Button.

4. The Server Open the Update

Page.

5. The Admin Update his

information and click Update

button.

6. The User information will be

updated and stored in Database.

7. Admin clicks delete

Button.

8.The Server Open the Update

Page and allow admin to delete

whatever he wants

9. Admin clicks create/add

record button

10.The Server Open the add

record Page and allow admin to

delete whatever he wants

11. admin clicks on search

button

12.The server open the search

engine to fine some record


45/140

31


Extensions

1.1 If the admin miss some or

type invalid information.

The System will generate an error.

Special requirements Text visibility must be ensured. System response time must not

exceed from 15 seconds. The system shall display all options and

messages in English language. The height of letters displayed on

the display console shall not be smaller than 0.5 inches

Frequency of

Occurrence


Table 13: Use case 5


46/140

32


System Sequence Diagram

Admission form

a message comes on the screen "data has been sent successfully"

system

: student

student fills all his/her data given onthat admission from and click submit button

verify

Figure 11: SSD admission form


47/140

33


Enter Data

a message comes on the screen "data has been enterd successfully"

system: admin

enters all the record of exam center,staff,datesheet,fee,courses,stationary

verify

Figure 12:SSD enter data


48/140

34


Verify Student

all data "successfully entered"

system: admin

clicks on the recieving messgae button

system will show all the details of the new candidate

enters all the record of new applicant in data base

Figure 13:SSD verify student


49/140

35


Conformation to sender

system: admin

sends the conformation message to applicant

message will appear "sent successfully "

Figure 14:SSD confirmation to sender


50/140

36


Manage Information

system: admin

clicks on the "update" button

message comes"record has been updated"

clicks on the delete button

message comes "record has been deleted"

clicks on the cerate /add record button

message comes "added successfully"

clicks on the search button

display the search engine

write the thing to find

display that required thing

verify

Figure 15:SSD manage information


51/140

37


Domain Model

Figure 16: Domain Model of System


52/140

Software Detail Design

Chapter No:3

Software Detail Design


53/140

41

Software Implementation

Sequence Diagram

SD: Submit admission form:

Figure 17:SD submit admission form


54/140

42


SD: main Interface:

Figure 18:SD main interface


55/140

43


SD: return Recourses:

Figure 19:SD return resources


56/140

44


Class Diagram

Figure 20:Class diagram of system


57/140

46


Figure 21:ERD of system

offer

Candidates

Name

DegreeFee

Degree code

Degree name

Examination Dept

Conduct set

Student ID

Faculty

CID

Degree code

Supervis

CID

Exams Include

Course code

Appear in

Fee amount

Exam info

Personal Info

FID Name

Addres

Rank

Has

Addr

Courses

Course nameHeld inExam Centers

Name

Seat Cap

Address

DegreeFee

Degree code

Degree name

Examination Dept

Conduct set

Student ID

Faculty

CID

Degree code

Supervis

CID

Exams Include

Course code

Appear in

Fee amount

Exam info

Personal Info

FID Name

Addres

Rank


58/140

47



59/140

Implementation

Chapter No:4

Implementation


60/140

48


1. Implementation

After the completion of Logical Design and Physical Design the implementation

phase was completed. The implementation of the software requires a sufficient timeas different resources have to be managed for implementation. When the detailed

design of the proposed system is available, the coding phase starts. In the coding

phase the design is converted into actual code. This is accomplished by usingprogramming tools.

The selection of programming tools is a critical step. Each tool has its own merits and

demerits but the selection of the tool for a particular project depends purely on thespecific requirements of the proposed system.

1.1 Tools & Technology Used

The system is developed using C#, SQL Server and Rational Rose .The

selection of these is due to following:

C# and is used to Front End. SQL Server is used for Data Base such as creation of table Rational Rose is used for Documentation

1.2 Hardware Used

The system has been designed on a machine having Corei3 2.4GHz processor with

4GB of physical memory. However a system having at least core2duo 2.0 GHz

processor with 2GB of physical memory is sufficient for optimum execution speed ofthe software.

namespace Exam_Conduct


61/140

49


{partialclassMain{

////// Required designer variable.///private System.ComponentModel.IContainer components = null;

////// Clean up any resources being used.//////true if managed resources should be

disposed; otherwise, false.protectedoverridevoid Dispose(bool disposing){

if (disposing && (components != null)){

components.Dispose();}base.Dispose(disposing);

}

#region Windows Form Designer generated code

////// Required method for Designer support - do not modify/// the contents of this method with the code editor.///privatevoid InitializeComponent(){

System.ComponentModel.ComponentResourceManager resources =new System.ComponentModel.ComponentResourceManager(typeof(Main));

this.label5 = new System.Windows.Forms.Label();this.label6 = new System.Windows.Forms.Label();this.label8 = new System.Windows.Forms.Label();this.label9 = new System.Windows.Forms.Label();this.label4 = new System.Windows.Forms.Label();this.label3 = new System.Windows.Forms.Label();this.label2 = new System.Windows.Forms.Label();this.label13 = new System.Windows.Forms.Label();this.label11 = new System.Windows.Forms.Label();this.label1 = new System.Windows.Forms.Label();this.label12 = new System.Windows.Forms.Label();this.label10 = new System.Windows.Forms.Label();this.label7 = new System.Windows.Forms.Label();this.glowingPanel2 = new Epos.GlowingPanel();this.glowingPanel1 = new Epos.GlowingPanel();

this.btn_new_Verification = new Epos.ImageButton();this.btn_new_Roll_No = new Epos.ImageButton();this.imageButton1 = new Epos.ImageButton();this.btn_new_DateSheet = new Epos.ImageButton();this.btn_new_Cources = new Epos.ImageButton();this.btn_new_Fee = new Epos.ImageButton();this.btn_new_Subject = new Epos.ImageButton();this.btn_new_Faculity = new Epos.ImageButton();this.btn_new_Alloction = new Epos.ImageButton();this.btn_new_Exam = new Epos.ImageButton();


62/140

50


this.btn_new_Cut_List = new Epos.ImageButton();this.btn_new_Stationary = new Epos.ImageButton();

((System.ComponentModel.ISupportInitialize)(this.btn_new_Verification)).BeginInit();

((System.ComponentModel.ISupportInitialize)(this.btn_new_Roll_No)).BeginInit();

((System.ComponentModel.ISupportInitialize)(this.imageButton1)).BeginInit();

((System.ComponentModel.ISupportInitialize)(this.btn_new_DateSheet)).BeginInit();

((System.ComponentModel.ISupportInitialize)(this.btn_new_Cources)).BeginInit();

((System.ComponentModel.ISupportInitialize)(this.btn_new_Fee)).BeginInit();

((System.ComponentModel.ISupportInitialize)(this.btn_new_Subject)).BeginInit();

((System.ComponentModel.ISupportInitialize)(this.btn_new_Faculity)).BeginInit();

((System.ComponentModel.ISupportInitialize)(this.btn_new_Alloction)).BeginInit();

((System.ComponentModel.ISupportInitialize)(this.btn_new_Exam)).BeginInit();

((System.ComponentModel.ISupportInitialize)(this.btn_new_Cut_List)).BeginInit();

((System.ComponentModel.ISupportInitialize)(this.btn_new_Stationary)).BeginInit();

this.SuspendLayout();//// label5//this.label5.AutoSize = true;this.label5.BackColor = System.Drawing.Color.Transparent;this.label5.Font = new System.Drawing.Font("Times New

Roman", 9F, System.Drawing.FontStyle.Bold,System.Drawing.GraphicsUnit.Point, ((byte)(0)));

this.label5.Location = new System.Drawing.Point(161, 613);this.label5.Name = "label5";this.label5.Size = new System.Drawing.Size(33, 15);this.label5.TabIndex = 3;this.label5.Text = "Staff";//// label6//this.label6.AutoSize = true;this.label6.BackColor = System.Drawing.Color.Transparent;


63/140

51


this.label6.Font = new System.Drawing.Font("Times NewRoman", 9F, System.Drawing.FontStyle.Bold,System.Drawing.GraphicsUnit.Point, ((byte)(0)));

this.label6.Location = new System.Drawing.Point(776, 613);this.label6.Name = "label6";this.label6.Size = new System.Drawing.Size(76, 15);this.label6.TabIndex = 3;this.label6.Text = "Exam Center";//// label8//this.label8.AutoSize = true;this.label8.BackColor = System.Drawing.Color.Transparent;this.label8.Font = new System.Drawing.Font("Times New


this.label8.Location = new System.Drawing.Point(871, 613);this.label8.Name = "label8";this.label8.Size = new System.Drawing.Size(63, 15);this.label8.TabIndex = 3;

this.label8.Text = "Stationary";//// label9//this.label9.AutoSize = true;this.label9.BackColor = System.Drawing.Color.Transparent;this.label9.Font = new System.Drawing.Font("Times New


this.label9.Location = new System.Drawing.Point(970, 613);this.label9.Name = "label9";this.label9.Size = new System.Drawing.Size(50, 15);this.label9.TabIndex = 3;this.label9.Text = "Cut List";//// label4//this.label4.AutoSize = true;this.label4.BackColor = System.Drawing.Color.Transparent;this.label4.Font = new System.Drawing.Font("Times New


this.label4.Location = new System.Drawing.Point(1059, 613);this.label4.Name = "label4";this.label4.Size = new System.Drawing.Size(37, 15);this.label4.TabIndex = 3;this.label4.Text = "Close";

//// label3//this.label3.AutoSize = true;this.label3.BackColor = System.Drawing.Color.Transparent;this.label3.Font = new System.Drawing.Font("Times New


this.label3.Location = new System.Drawing.Point(693, 613);this.label3.Name = "label3";


64/140

52


this.label3.Size = new System.Drawing.Size(45, 15);this.label3.TabIndex = 3;this.label3.Text = "Degree";//// label2//this.label2.AutoSize = true;this.label2.BackColor = System.Drawing.Color.Transparent;this.label2.Font = new System.Drawing.Font("Times New


this.label2.Location = new System.Drawing.Point(597, 613);this.label2.Name = "label2";this.label2.Size = new System.Drawing.Size(66, 15);this.label2.TabIndex = 3;this.label2.Text = "Date Sheet";//// label13//this.label13.AutoSize = true;

this.label13.BackColor = System.Drawing.Color.Transparent;this.label13.Font = new System.Drawing.Font("Times New


this.label13.Location = new System.Drawing.Point(346, 613);this.label13.Name = "label13";this.label13.Size = new System.Drawing.Size(26, 15);this.label13.TabIndex = 3;this.label13.Text = "Fee";//// label11//this.label11.AutoSize = true;this.label11.BackColor = System.Drawing.Color.Transparent;this.label11.Font = new System.Drawing.Font("Times New


this.label11.Location = new System.Drawing.Point(234, 613);this.label11.Name = "label11";this.label11.Size = new System.Drawing.Size(61, 30);this.label11.TabIndex = 3;this.label11.Text = " Staff \r\nAllocation";//// label1//this.label1.AutoSize = true;this.label1.BackColor = System.Drawing.Color.Transparent;

this.label1.Font = new System.Drawing.Font("Times NewRoman", 9F, System.Drawing.FontStyle.Bold,System.Drawing.GraphicsUnit.Point, ((byte)(0)));

this.label1.Location = new System.Drawing.Point(423, 613);this.label1.Name = "label1";this.label1.Size = new System.Drawing.Size(50, 15);this.label1.TabIndex = 3;this.label1.Text = "Courses";//// label12


65/140

53


//this.label12.AutoSize = true;this.label12.BackColor = System.Drawing.Color.Transparent;this.label12.Font = new System.Drawing.Font("Times New


this.label12.Location = new System.Drawing.Point(58, 613);this.label12.Name = "label12";this.label12.Size = new System.Drawing.Size(68, 30);this.label12.TabIndex = 3;this.label12.Text = "Issue Roll #\r\n Slips";//// label10//this.label10.AutoSize = true;this.label10.BackColor = System.Drawing.Color.Transparent;this.label10.Font = new System.Drawing.Font("Times New


this.label10.Location = new System.Drawing.Point(502, 613);

this.label10.Name = "label10";this.label10.Size = new System.Drawing.Size(69, 30);this.label10.TabIndex = 3;this.label10.Text = " Student\r\nVerification";//// label7//this.label7.Image =

((System.Drawing.Image)(resources.GetObject("label7.Image")));this.label7.Location = new System.Drawing.Point(423, 39);this.label7.Name = "label7";this.label7.Size = new System.Drawing.Size(418, 69);this.label7.TabIndex = 8;//// glowingPanel2//this.glowingPanel2.BackColor = System.Drawing.Color.Maroon;this.glowingPanel2.Dock =

System.Windows.Forms.DockStyle.Bottom;this.glowingPanel2.GlowColor = System.Drawing.Color.White;this.glowingPanel2.Location = new System.Drawing.Point(0,

650);this.glowingPanel2.Name = "glowingPanel2";this.glowingPanel2.ShineColor =

System.Drawing.Color.Maroon;this.glowingPanel2.Size = new System.Drawing.Size(1186,

36);

this.glowingPanel2.TabIndex = 1;//// glowingPanel1//this.glowingPanel1.BackColor = System.Drawing.Color.Maroon;this.glowingPanel1.Dock =

System.Windows.Forms.DockStyle.Top;this.glowingPanel1.GlowColor = System.Drawing.Color.White;this.glowingPanel1.Location = new System.Drawing.Point(0,

0);


66/140

54


this.glowingPanel1.Name = "glowingPanel1";this.glowingPanel1.ShineColor =

System.Drawing.Color.Maroon;this.glowingPanel1.Size = new System.Drawing.Size(1186,

36);this.glowingPanel1.TabIndex = 0;//// btn_new_Verification//this.btn_new_Verification.BackColor =

System.Drawing.Color.Transparent;this.btn_new_Verification.DialogResult =

System.Windows.Forms.DialogResult.None;this.btn_new_Verification.DownImage =

global::Exam_Conduct.Properties.Resources.exam_icon1;this.btn_new_Verification.HoverImage =

global::Exam_Conduct.Properties.Resources.exam_icon2;this.btn_new_Verification.Location = new

System.Drawing.Point(503, 538);this.btn_new_Verification.Name = "btn_new_Verification";

this.btn_new_Verification.NormalImage =global::Exam_Conduct.Properties.Resources.exam_icon;

this.btn_new_Verification.Size = newSystem.Drawing.Size(68, 68);

this.btn_new_Verification.TabIndex = 6;this.btn_new_Verification.TabStop = false;this.btn_new_Verification.Click += new

System.EventHandler(this.btn_new_Verification_Click);//// btn_new_Roll_No//this.btn_new_Roll_No.BackColor =

System.Drawing.Color.Transparent;this.btn_new_Roll_No.DialogResult =

System.Windows.Forms.DialogResult.None;this.btn_new_Roll_No.DownImage =

global::Exam_Conduct.Properties.Resources.icon_examResults2;this.btn_new_Roll_No.HoverImage =

global::Exam_Conduct.Properties.Resources.icon_examResults1;this.btn_new_Roll_No.Location = new

System.Drawing.Point(61, 532);this.btn_new_Roll_No.Name = "btn_new_Roll_No";this.btn_new_Roll_No.NormalImage =

global::Exam_Conduct.Properties.Resources.icon_examResults;this.btn_new_Roll_No.Size = new System.Drawing.Size(69,

68);this.btn_new_Roll_No.TabIndex = 8;

this.btn_new_Roll_No.TabStop = false;//// imageButton1//this.imageButton1.BackColor =

System.Drawing.Color.Transparent;this.imageButton1.DialogResult =

System.Windows.Forms.DialogResult.None;this.imageButton1.DownImage =

global::Exam_Conduct.Properties.Resources.close2;


67/140

55


this.imageButton1.HoverImage =global::Exam_Conduct.Properties.Resources.close1;

this.imageButton1.Location = new System.Drawing.Point(1035,538);

this.imageButton1.Name = "imageButton1";this.imageButton1.NormalImage =

global::Exam_Conduct.Properties.Resources.close;this.imageButton1.Size = new System.Drawing.Size(71, 68);this.imageButton1.TabIndex = 6;this.imageButton1.TabStop = false;this.imageButton1.Click += new

System.EventHandler(this.imageButton1_Click);//// btn_new_DateSheet//this.btn_new_DateSheet.BackColor =

System.Drawing.Color.Transparent;this.btn_new_DateSheet.DialogResult =

System.Windows.Forms.DialogResult.None;this.btn_new_DateSheet.DownImage =

global::Exam_Conduct.Properties.Resources.timetable2;this.btn_new_DateSheet.HoverImage =

global::Exam_Conduct.Properties.Resources.timetable1;this.btn_new_DateSheet.Location = new

System.Drawing.Point(586, 538);this.btn_new_DateSheet.Name = "btn_new_DateSheet";this.btn_new_DateSheet.NormalImage =

global::Exam_Conduct.Properties.Resources.timetable;this.btn_new_DateSheet.Size = new System.Drawing.Size(77,

68);this.btn_new_DateSheet.TabIndex = 4;this.btn_new_DateSheet.TabStop = false;this.btn_new_DateSheet.Click += new

System.EventHandler(this.btn_new_DateSheet_Click);//// btn_new_Cources//this.btn_new_Cources.BackColor =

System.Drawing.Color.Transparent;this.btn_new_Cources.DialogResult =

System.Windows.Forms.DialogResult.None;this.btn_new_Cources.DownImage =

global::Exam_Conduct.Properties.Resources.book_icon2;this.btn_new_Cources.HoverImage =

global::Exam_Conduct.Properties.Resources.book_icon1;this.btn_new_Cources.Location = new

System.Drawing.Point(411, 538);

this.btn_new_Cources.Name = "btn_new_Cources";this.btn_new_Cources.NormalImage =

global::Exam_Conduct.Properties.Resources.book_icon;this.btn_new_Cources.Size = new System.Drawing.Size(77,

68);this.btn_new_Cources.TabIndex = 2;this.btn_new_Cources.TabStop = false;this.btn_new_Cources.Click += new

System.EventHandler(this.btn_new_Cources_Click);//


68/140

56


// btn_new_Fee//this.btn_new_Fee.BackColor =

System.Drawing.Color.Transparent;this.btn_new_Fee.DialogResult =

System.Windows.Forms.DialogResult.None;this.btn_new_Fee.DownImage =

global::Exam_Conduct.Properties.Resources.Fee2;this.btn_new_Fee.HoverImage =

global::Exam_Conduct.Properties.Resources.Fee3;this.btn_new_Fee.Location = new System.Drawing.Point(321,

538);this.btn_new_Fee.Name = "btn_new_Fee";this.btn_new_Fee.NormalImage =

global::Exam_Conduct.Properties.Resources.Fee1;this.btn_new_Fee.Size = new System.Drawing.Size(75, 68);this.btn_new_Fee.TabIndex = 7;this.btn_new_Fee.TabStop = false;this.btn_new_Fee.Click += new

System.EventHandler(this.btn_new_Fee_Click);

//// btn_new_Subject//this.btn_new_Subject.BackColor =

System.Drawing.Color.Transparent;this.btn_new_Subject.DialogResult =

System.Windows.Forms.DialogResult.None;this.btn_new_Subject.DownImage =

global::Exam_Conduct.Properties.Resources.photoshop_degree_cap_logo_icon252;

this.btn_new_Subject.HoverImage =global::Exam_Conduct.Properties.Resources.photoshop_degree_cap_logo_icon251;

this.btn_new_Subject.Location = newSystem.Drawing.Point(678, 529);

this.btn_new_Subject.Name = "btn_new_Subject";this.btn_new_Subject.NormalImage =

global::Exam_Conduct.Properties.Resources.photoshop_degree_cap_logo_icon25;

this.btn_new_Subject.Size = new System.Drawing.Size(77,68);

this.btn_new_Subject.TabIndex = 5;this.btn_new_Subject.TabStop = false;this.btn_new_Subject.Click += new

System.EventHandler(this.btn_new_Subject_Click);//// btn_new_Faculity

//this.btn_new_Faculity.BackColor =

System.Drawing.Color.Transparent;this.btn_new_Faculity.DialogResult =

System.Windows.Forms.DialogResult.None;this.btn_new_Faculity.DownImage =

global::Exam_Conduct.Properties.Resources.faculty_icon_ove3r;this.btn_new_Faculity.HoverImage =

global::Exam_Conduct.Properties.Resources.faculty_icon_ove2r;


69/140

57


this.btn_new_Faculity.Location = newSystem.Drawing.Point(145, 538);

this.btn_new_Faculity.Name = "btn_new_Faculity";this.btn_new_Faculity.NormalImage =

global::Exam_Conduct.Properties.Resources.faculty_icon_ove1r;this.btn_new_Faculity.Size = new System.Drawing.Size(77,

68);this.btn_new_Faculity.TabIndex = 1;this.btn_new_Faculity.TabStop = false;this.btn_new_Faculity.Click += new

System.EventHandler(this.btn_new_Faculity_Click);//// btn_new_Alloction//this.btn_new_Alloction.BackColor =

System.Drawing.Color.Transparent;this.btn_new_Alloction.DialogResult =

System.Windows.Forms.DialogResult.None;this.btn_new_Alloction.DownImage =

global::Exam_Conduct.Properties.Resources.docs_icon2;

this.btn_new_Alloction.HoverImage =global::Exam_Conduct.Properties.Resources.docs_icon1;

this.btn_new_Alloction.Location = newSystem.Drawing.Point(237, 522);

this.btn_new_Alloction.Name = "btn_new_Alloction";this.btn_new_Alloction.NormalImage =

global::Exam_Conduct.Properties.Resources.docs_icon;this.btn_new_Alloction.Size = new System.Drawing.Size(69,

66);this.btn_new_Alloction.TabIndex = 7;this.btn_new_Alloction.TabStop = false;this.btn_new_Alloction.Click += new

System.EventHandler(this.btn_new_Alloction_Click);//// btn_new_Exam//this.btn_new_Exam.BackColor =

System.Drawing.Color.Transparent;this.btn_new_Exam.DialogResult =

System.Windows.Forms.DialogResult.None;this.btn_new_Exam.DownImage =

global::Exam_Conduct.Properties.Resources.examhall_icon_small2;this.btn_new_Exam.HoverImage =

global::Exam_Conduct.Properties.Resources.examhall_icon_small;this.btn_new_Exam.Location = new System.Drawing.Point(770,

533);this.btn_new_Exam.Name = "btn_new_Exam";

this.btn_new_Exam.NormalImage =global::Exam_Conduct.Properties.Resources.examhall_icon_smal1l;

this.btn_new_Exam.Size = new System.Drawing.Size(72, 73);this.btn_new_Exam.TabIndex = 8;this.btn_new_Exam.TabStop = false;this.btn_new_Exam.Click += new

System.EventHandler(this.btn_new_Exam_Click);//// btn_new_Cut_List//


70/140

58


this.btn_new_Cut_List.BackColor =System.Drawing.Color.Transparent;

this.btn_new_Cut_List.DialogResult =System.Windows.Forms.DialogResult.None;

this.btn_new_Cut_List.DownImage =global::Exam_Conduct.Properties.Resources.icon_coupons2;

this.btn_new_Cut_List.HoverImage =global::Exam_Conduct.Properties.Resources.icon_coupons1;

this.btn_new_Cut_List.Location = newSystem.Drawing.Point(949, 538);

this.btn_new_Cut_List.Name = "btn_new_Cut_List";this.btn_new_Cut_List.NormalImage =

global::Exam_Conduct.Properties.Resources.icon_coupons;this.btn_new_Cut_List.Size = new System.Drawing.Size(71,

73);this.btn_new_Cut_List.TabIndex = 5;this.btn_new_Cut_List.TabStop = false;//// btn_new_Stationary//

this.btn_new_Stationary.BackColor =System.Drawing.Color.Transparent;

this.btn_new_Stationary.DialogResult =System.Windows.Forms.DialogResult.None;

this.btn_new_Stationary.DownImage =global::Exam_Conduct.Properties.Resources.stockphotopro_68401390JDL_no_title1;

this.btn_new_Stationary.HoverImage =global::Exam_Conduct.Properties.Resources.stockphotopro_68401390JDL_no_title2;

this.btn_new_Stationary.Location = newSystem.Drawing.Point(857, 538);

this.btn_new_Stationary.Name = "btn_new_Stationary";this.btn_new_Stationary.NormalImage =

global::Exam_Conduct.Properties.Resources.stockphotopro_68401390JDL_no_title;

this.btn_new_Stationary.Size = new System.Drawing.Size(77,68);

this.btn_new_Stationary.TabIndex = 4;this.btn_new_Stationary.TabStop = false;this.btn_new_Stationary.Click += new

System.EventHandler(this.btn_new_Stationary_Click);//// Main//this.AutoScaleDimensions = new System.Drawing.SizeF(6F,

13F);

this.AutoScaleMode =System.Windows.Forms.AutoScaleMode.Font;

this.BackColor = System.Drawing.Color.Wheat;this.BackgroundImageLayout =

System.Windows.Forms.ImageLayout.Stretch;this.ClientSize = new System.Drawing.Size(1186, 686);this.ControlBox = false;this.Controls.Add(this.glowingPanel2);this.Controls.Add(this.label10);this.Controls.Add(this.glowingPanel1);


71/140

59


this.Controls.Add(this.btn_new_Verification);this.Controls.Add(this.label7);this.Controls.Add(this.btn_new_Roll_No);this.Controls.Add(this.label5);this.Controls.Add(this.imageButton1);this.Controls.Add(this.label12);this.Controls.Add(this.label3);this.Controls.Add(this.btn_new_DateSheet);this.Controls.Add(this.label4);this.Controls.Add(this.btn_new_Cources);this.Controls.Add(this.btn_new_Fee);this.Controls.Add(this.btn_new_Subject);this.Controls.Add(this.btn_new_Faculity);this.Controls.Add(this.btn_new_Alloction);this.Controls.Add(this.label2);this.Controls.Add(this.label6);this.Controls.Add(this.label9);this.Controls.Add(this.label1);this.Controls.Add(this.btn_new_Exam);this.Controls.Add(this.btn_new_Cut_List);

this.Controls.Add(this.btn_new_Stationary);this.Controls.Add(this.label11);this.Controls.Add(this.label13);this.Controls.Add(this.label8);this.FormBorderStyle =

System.Windows.Forms.FormBorderStyle.FixedSingle;this.Name = "Main";this.StartPosition =

System.Windows.Forms.FormStartPosition.CenterScreen;

((System.ComponentModel.ISupportInitialize)(this.btn_new_Verification)).EndInit();

((System.ComponentModel.ISupportInitialize)(this.btn_new_Roll_No)).EndInit();

((System.ComponentModel.ISupportInitialize)(this.imageButton1)).EndInit();

((System.ComponentModel.ISupportInitialize)(this.btn_new_DateSheet)).EndInit();

((System.ComponentModel.ISupportInitialize)(this.btn_new_Cources)).EndInit();

((System.ComponentModel.ISupportInitialize)(this.btn_new_Fee)).EndInit();

((System.ComponentModel.ISupportInitialize)(this.btn_new_Subject)).EndInit();

((System.ComponentModel.ISupportInitialize)(this.btn_new_Faculity)).EndInit();

((System.ComponentModel.ISupportInitialize)(this.btn_new_Alloction)).EndInit();


72/140

60


((System.ComponentModel.ISupportInitialize)(this.btn_new_Exam)).EndInit();

((System.ComponentModel.ISupportInitialize)(this.btn_new_Cut_List)).EndInit();

((System.ComponentModel.ISupportInitialize)(this.btn_new_Stationary)).EndInit();

this.ResumeLayout(false);this.PerformLayout();

}

#endregion

private System.Windows.Forms.Label label7;private Epos.GlowingPanel glowingPanel1;private Epos.GlowingPanel glowingPanel2;private System.Windows.Forms.Label label10;

private Epos.ImageButton btn_new_Verification;private Epos.ImageButton btn_new_Roll_No;private System.Windows.Forms.Label label5;private System.Windows.Forms.Label label12;private Epos.ImageButton btn_new_DateSheet;private Epos.ImageButton btn_new_Cources;private Epos.ImageButton btn_new_Subject;private Epos.ImageButton btn_new_Alloction;private System.Windows.Forms.Label label6;private System.Windows.Forms.Label label1;private Epos.ImageButton btn_new_Cut_List;private System.Windows.Forms.Label label11;private System.Windows.Forms.Label label8;private System.Windows.Forms.Label label13;private Epos.ImageButton btn_new_Stationary;private Epos.ImageButton btn_new_Exam;private System.Windows.Forms.Label label9;private System.Windows.Forms.Label label2;private Epos.ImageButton btn_new_Faculity;private Epos.ImageButton btn_new_Fee;private System.Windows.Forms.Label label4;private System.Windows.Forms.Label label3;private Epos.ImageButton imageButton1;

}}namespace Exam_Conduct{

partialclassCourse

{////// Required designer variable.///private System.ComponentModel.IContainer components = null;

////// Clean up any resources being used.///


73/140

61


///true if managed resources should bedisposed; otherwise, false.

protectedoverridevoid Dispose(bool disposing){

if (disposing && (components != null)){

components.Dispose();}base.Dispose(disposing);

}

#region Windows Form Designer generated code

////// Required method for Designer support - do not modify/// the contents of this method with the code editor.///privatevoid InitializeComponent(){

this.label2 = new System.Windows.Forms.Label();

this.dgv_Courses = new System.Windows.Forms.DataGridView();this.C_Serial = new

System.Windows.Forms.DataGridViewTextBoxColumn();this.C_tital = new

System.Windows.Forms.DataGridViewTextBoxColumn();this.C_Code = new

System.Windows.Forms.DataGridViewTextBoxColumn();this.C_Marks = new

System.Windows.Forms.DataGridViewTextBoxColumn();this.cmb_C_Discipline = new

System.Windows.Forms.ComboBox();this.label1 = new System.Windows.Forms.Label();this.cmb_S_Subject = new System.Windows.Forms.ComboBox();this.label3 = new System.Windows.Forms.Label();this.cmb_S_Type = new System.Windows.Forms.ComboBox();this.label4 = new System.Windows.Forms.Label();this.glowingPanel2 = new Epos.GlowingPanel();this.glowingPanel1 = new Epos.GlowingPanel();this.btn_new_Update = new Epos.ImageButton();this.btn_new_Close = new Epos.ImageButton();this.btn_new_Search = new Epos.ImageButton();this.btn_new_Del = new Epos.ImageButton();this.label6 = new System.Windows.Forms.Label();this.label5 = new System.Windows.Forms.Label();this.label7 = new System.Windows.Forms.Label();this.label8 = new System.Windows.Forms.Label();this.label9 = new System.Windows.Forms.Label();

this.btn_new_Add = new Epos.ImageButton();

((System.ComponentModel.ISupportInitialize)(this.dgv_Courses)).BeginInit();

((System.ComponentModel.ISupportInitialize)(this.btn_new_Update)).BeginInit();

((System.ComponentModel.ISupportInitialize)(this.btn_new_Close)).BeginInit();


74/140

62


((System.ComponentModel.ISupportInitialize)(this.btn_new_Search)).BeginInit();

((System.ComponentModel.ISupportInitialize)(this.btn_new_Del)).BeginInit();

((System.ComponentModel.ISupportInitialize)(this.btn_new_Add)).BeginInit();

this.SuspendLayout();//// label2//this.label2.AutoSize = true;this.label2.Font = new System.Drawing.Font("Times New

Roman", 15.75F, System.Drawing.FontStyle.Bold);this.label2.Location = new System.Drawing.Point(295, 39);this.label2.Name = "label2";this.label2.Size = new System.Drawing.Size(81, 24);this.label2.TabIndex = 0;

this.label2.Text = "Courses";this.label2.Click += new

System.EventHandler(this.label2_Click);//// dgv_Courses//this.dgv_Courses.BackgroundColor =

System.Drawing.Color.Wheat;this.dgv_Courses.BorderStyle =

System.Windows.Forms.BorderStyle.None;this.dgv_Courses.ColumnHeadersHeightSizeMode =

System.Windows.Forms.DataGridViewColumnHeadersHeightSizeMode.AutoSize;this.dgv_Courses.Columns.AddRange(new

System.Windows.Forms.DataGridViewColumn[] {this.C_Serial,this.C_tital,this.C_Code,this.C_Marks});this.dgv_Courses.GridColor = System.Drawing.Color.Maroon;this.dgv_Courses.Location = new System.Drawing.Point(0,

109);this.dgv_Courses.Name = "dgv_Courses";this.dgv_Courses.RowHeadersVisible = false;this.dgv_C

computer science final year documentation sample

Documents