BIC 3349

GUI & RAD

SCHOOL MANAGEMENT SYSTEM

MR. ZULFAHMI RASHID

FACULTY OF COMPUTER SCIENCE AND MULTIMEDIA

REPORT BY:Noradlirazman Bin Othman810910-03-5961BACHELOR IN COMPUTER SCIENCE

TABLE OF CONTENTS

INTERFACE PAGE

1. MAIN FORM…………………………………………………………………………………………………………………………………………………………………………..31.1 File………………………………………………………………………………………

……………………………………………………………………………………………………………3

1.2 Transaction………………………………………………………………………………………………………………………………………………………………………………………3

1.3 View………………………………………………………………………………………………………………………………………………………………………………………………….3

1.4 Reports…………………………………………………………………………………………………………………………………………………………………………………………….3

1.5 Utilities…………………………………………………………………………………………………………………………………………………………………………………………..…3

1.6 Help…………………………………………………………………………………………………………………………………………………………………………………………………..3

2. SIGN IN…………………………………………………………………………………………………………………………………………………………………………………4

3. ADMINISTRATIVE AND ACCESS OPTIONS…………..…………………………………………………………………………………………………………………43.1 Creating New

Users…………………………………………………………………………………………………………………………………………………………………………4

3.2 Resetting Password…………………………………………………………………………………………………………………………………………………………………………4

3.3 Deleting account……………………………………………………………………………………………………………………………………………………………………………...4

2

4. STUDENT REGISTRATION ……………………………………………………………………………………………………………………………………………………54.1 Important student data

………………………………………………………………………………………………………………………………………………………………….5

4.2

Interface…………………………………………………………………………………………………………………………………………………………………………………………..5

4.3

Validations………………………………………………………………………………………………………………………………………………………………………………………..5

4.4 Submit to data base……………………………………………………………………………………………………………………………………………………………………..…5

5. FEE REGISTRATION SYSTEM ……………………………………………………………………………………………………………………………………………..…65.1 Check student

registration……………………………………………………………………………………………………………………………………………………………6

5.2 Calculations………………………………………..……………………………………………………………………………………………………………………………………………6

5.3 Interface…………………………….....…………………………………………………………………………………………………………………………………………………………6

5.4

Validation……………………………………………………………………………………………………………………………………………………………………………………….…6

5.5 Submit to database……………………………………………………………………………………………………………………………………………………………………….…6

6. Course Registration ……………………………………………………………………………………………………………………………………………..…………….76.1 Check student

registration……………………………………………………………………………………………………………………………………………………………..7

3

6.2 Possibility of Course registration…………………………………………………………………………………………………………………………………………………..7

6.3 Submit to data base……………….………………………………………………………………………………………………………………………………………………………..7

7. MARKS ENTRY …………………………………………………………………………………………………………………………………………………..…..…………….87.1 Check Course Registration

……………………………………………………………………………………………………………………..…………………..…..…………….8

7.2 Extract course from course registration module..………………………………………………………………………………..…………………..…..…………….8

7.3 Enter Marks…………………………………………………………………………………….………………………………………………………..…………………..…..…………….8

7.4

Validation…………………………………………………………………………………………………………………………………………………..…………………..…..…………….8

7.5

Interface……………………………………………………………………………………………………………………..………………………………….……………..…..…………….8

7.6 Submitting to database……………………………………………………………………………………………………………………..………………….……..…..…………….8

8. REPORTING …………………………………………………………………………………………………………………………………………………..…..…………………98.1 Reporting for each module

……………………………………………………………………………………………………………………………………..…..…………………9

8.2 Overall report of student data……………………………………………………………………………………………………………………………………..…..……………9

8.3 Exam report of each student ……………………………………………………………………………………………………………………………………..…..……………..9

4

9. UPDATING AND EDITING …………………………………………………………………………….………………………………………………..…..…………………109.1 Updating of student

data……………………………………………………………………………………………………………………………………..…..……………………10

9.2 Updating of Fee Registration Data……………………………………………………………………………………………………………………………………..…..…….10

9.3 Updating Course Registration……………………………………………………………………………………………………………………………………..…..……………10

9.4 Updating Marks……………………………………………………………………………………………………………………………………..…..……………………………………10

10. SCOPE …………………………………………………………………………….………………………………………………..…..…………………………………………….1110.1 Performance ………………………………………………………….………………………………………………..…..…………………………………………………………………1110.2 Hardware ………………………….…………………………………….………………………………………………..…..…………………………………………………………………1110.3 Platform ………………………………………………………………….………………………………………………..…..…………………………………………………………………1110.4 Deliverable Form …………………………………………………….………………………………………………..…..…………………………………………………………………1110.5 Conclusion ………………………………………………………….………..…………………………………………..…..…………………………………………………………………11

11. APPENDIX : SEQUENCE DIAGRAM OF SCHOOL MANAGEMENT SYSTEM ………………………………………………………………………………………12

5

INTERFACE

1. MAIN FORMForms are the interface via which user interact with system so it is more important to design a user friendly interface. To achieve this target we tried to use suitable controls for getting input data from user. Also form will get all the important details from users.

Main FormIn main form there are links to access all the modules of systems like registration updating and deletion. This form will be the MDi container, entire application will be close on closing this form and all the form will open over this form. The main form is divided in to five major menus. · File · Transaction · View· Reports. Utilities · Help

1.1 File

6

Figure 1 Main form

For the security reasons, administration field will only access by administrator of head on institute. File menu contains the data about resetting passwords of users, deleting or creating account of a particular user etc.1.2 Transaction

The transaction menu contains the basic registration options of the students including registration in student registration, fee registration and course registration.

1.3 ViewThe view menu contains the updating and editing option of student together with employee. In case user enter the wrong value for example a user enter wrong name such as enter Ail instead of Ali, it can be changed and updated by system.

1.4 ReportsThis menu is concern with outputs and view the data in different prospective. Such as if a user wants to see the student registration data, overall report, mark sheet etc then it can be viewed. All reports can be printed.

1.5 UtilitiesThe school management system comes with a Windows calculator utility program that emulates the appearance and functionality of a calculator, using the graphical user interface to portray a calculator.

1.6 HelpIn case a user wants to know how to operate or deal with a specific control, a

complete help will be provided by system.

2. SIGN IN To access the main form it is important to enter the username and password. This is important so only valid user can enter the system. If user forget the password, the link is given on form by which user can rest its password. For resetting password user has to enter the security phase which will be provided by administrator.

3. ADMINISTRATIVE AND ACCESS OPTIONS

7

Figure 2 Login form

Only administrator can access the task like resting user password, creating new account etc. And each type of user there are proper rights. Administrative Rights include following tasks

3.1 Creating New UsersOnly administrator will able to create new users so the menu should be in placed in administration so it can only b access by administrator.

3.2 Resetting PasswordIn cases user forget password it can be reset by administrator,

3.3 Deleting accountAdministrator can delete the account if user leaves the institute of any other case for example the designation of the user changes.

4. STUDENT REGISTRATION One of the key modules in School Management System. For each student it is important to register in this module only then it is possible for user to access other modules. This module will have following steps

4.1 Important student data The basic info of student will be provided by user to register student. This module will extract student name, father name, date of birth, education background etc. This data will be use in reporting and other module will use this data for different verifications such as class in which student is enrolled etc.

8

Figure 3 User Information form

Figure 4 Student Registration

4.2 InterfaceInterface is important because the user interact with application via interface. An interface must be easy to understand and use. A control will use according to type of input for example a calendar will use for date of birth and textbox for entering name etc.

4.3 ValidationsIt will make ensure that user must enter write type of data for particular entity. Both form level and control level validation will be applied. Validation will also be ensured by using advance controls.

4.5 Submit to data baseAt the time of submitting application will perform exception handling, and will access database to submit data and form will automatically close.

5. FEE REGISTRATION SYSTEMThe next module is about fee management of all students. All records will be store in such a fashion so that it will easy to perform joints, Abstraction and cohesions.

9

Figure 5 Fees payment

5.1 Check student registrationThe application will check the registration in student registration first and will only allow user to perform fee registration if and only if student is register in student registration system. It is important to manage the proper hierarchy for each student.

5.2 CalculationsIt will make ensure to keep application apart from human errors as much as it is possible. Most of calculation like dues will automatically calculated. There will no mechanism for instalments but if any one can’t pay entire fee, he can pay some it will manage by application by itself.

5.3 InterfaceAn interface must be easy to understand and use. A control will use according to type of input for example a time and date of submitting of fee will automatically be entered in textbox same as system time and textbox for entering fee paid or dues etc.

5.4 ValidationIn case of fee dues will be automatically be calculated and user will unable to alter them. Also user can enter numeric data in fee paid, total fee text boxes. It will make ensure that user must enter write type of data for particular entity. Both form level and control level validation will be applied. Validation will also be ensured by using advance controls.

5.5 Submit to databaseData will be submitted in database using registration number as primary key so

it will easy to extract data.

6 COURSE REGISTRATIONAs the course registration is an important part of student registration system. Also for each class in school there are distinct courses or subjects which remain same

10

often but there is possibility in changing the criteria, in that case there should be some way to add and remove course. So it will be the part of course registration module. The following steps will be fallow for course registration.

6.1 Check student registrationFirst the student registration will be checked so make ensure that student is valid on domain of school. If student is register in student registration only then this module is available for student

6.2 Possibility of Course registrationA user can alter the course of entire classes and can add and remove the courses. After managing the courses for each class, for the user the course plan will automatically generated by application according to class of a particular student.

6.3 Submit to data base

Data will add to database and will be use for marks entering. Primary key will be class which will unique with in school.

11

Figure 6 Class entry form

7 MARKS ENTRYUser will enter the marks for each student and application will be able to manage record in way to use data efficiently when needed.

7.1 Check Course Registration Application will check the student registration in registration module and if student is register only then he will enable to use marks entry module

7.2 Extract course from course registration moduleThe application will extract data from course module automatically according to class given in registration module. On enter the registration courses will automatically be provided by application.

7.3 Enter MarksIn front of each course a textbox will be available to enter the obtain marks because total marks will be there in course module.

7.4 ValidationOnly valid data will be allowed by application in control.

7.5 InterfaceUser will have to enter the registration number of the student and application will provide the course detail and total marks. This data will extract from course registration

12

Figure 7 Result entry

7.6 Submitting to databaseData will store in data base, exception will be handled.

8 REPORTINGReporting is the way to show output of particular search or show relevant data with respect to different needs and teams. Microsoft Access Reports is a powerful technique to achieve this. Reporting will be done as follows

8.1 Reporting for each module For each module report is classified in two classes· The report of particular student · The report containing the data of all students of a particular module.

8.2 A overall report of student data

Overall reporting will contain the brief description of particular student from all modules. It will sort of introduction from student registration, fee status from fee module and overall position and percentage from marks module.

8.3 A Exam report of each student

It will have all description as there in report cards.

13

Figure 8.1 Student data report

Figure 8.2 Fees data report

Figure 8.3 Result data report

9 UPDATING AND EDITINGUpdating and editing are requiring correcting the input in case of human error. It is also important for flexibility of program. For updating user need to enter the registration number all data will be shown to user and user can edit the data. Our application allow updating as follow

14

Figure 9.1 Student data update formFigure 9.2 Fee Registration data update

Figure 9.3 Course Registration updateFigure 9.4 Marks update form

10SCOPEThis application will facilitate Sekolah Menengah Kebangsaan Kepong Baru in all domains which was described before. This application can be run over a standalone personal computer or can be share on LAN if it is available in the respective school.

10.1 PerformanceIn creating this design it is kept one first priority that system must work efficiently on the hardware and software which is specified and suggested.

10.2 HardwareOur application is generic and it will be for Sekolah Menengah Kebangsaan Kepong Baru so we will try to make it compatible to as low as hardware requirements. Our target is to run this application at Pentium 2 with minimum 600MHz processor and 128MB RAM. We want to run application on this specification because it is available in Sekolah Menengah Kebangsaan Kepong Baru.

10.3 PLATEFORMThis application will run over Windows 2000/NT/vista. We choose windows as plate form for our application because it is the widely using operating system in Malaysia.

10.4 Deliverable formWe will deliver the executable form of application and the source code will not

be provided to stake holder.

10.5 ConclusionThe designs are design keeping in view the all needs of user and are done according to requirements elaborated in this document.

15

11APPENDIX: THE SEQUENCE DIAGRAM OF SCHOOL MANAGEMENT SYSTEM

16