Acknowledgement

I am using this opportunity to express my gratitude to everyone who supported me throughout

the course of this OOP assignment. I am thankful for their aspiring guidance, invaluably
constructive criticism and friendly advice during the project work. I am sincerely grateful to
them for sharing their truthful and illuminating views on a number of issues related to the
project.

A.K. Mohamed Rila

Table of Contents
Acknowledgement ................................................................... Error! Bookmark not defined.

1. Pillar concepts of Object Oriented Programming .............................................................. 7

1.2. What is Object Oriented Programs.............................................................................. 7

1.1.1 Abstraction ........................................................................................................... 8

1.1.2 Encapsulation ....................................................................................................... 9

1.1.3 Inheritance.......................................................................................................... 10

1.1.4 Polymorphism .................................................................................................... 11

2. File structures of design ................................................................................................... 12

3. UML Diagrams of the software ....................................................................................... 15

3.1 Use case diagram ........................................................................................................... 15

3.2 Class Diagram ................................................................................................................ 16

3.3 Sequence Diagram ......................................................................................................... 17

3.4 ER Diagram ................................................................................................................... 20

4. Visual Studio IDE for the solution................................................................................... 21

5. Control Structure of the solution.......................................................................................... 22

4.1 IF-ELSE Statement ................................................................................................... 22

4.2 Switch Statement ....................................................................................................... 23

4.3 While Loop ................................................................................................................ 24

4.4 Do-While Loop .............................................................................................................. 24

4.4 For Loop .................................................................................................................... 25

6. Use of an Integrated Development Environment................................................................. 26

7. Test Plan of the Solution ...................................................................................................... 36

7.1.2 Developed Test Plan for University of Stafford ......................................................... 37

8. Actual and Expect result of the solution. ............................................................................. 38

9. Feedback of the solution. ..................................................................................................... 42

10. User Guidance and technical documentation. .................................................................... 45

 10.1 Installation Guide ......................................................................................................... 45

10.2 User guidance............................................................................................................... 47

Gantt chart ................................................................................................................................ 50

Future Enhancement ................................................................................................................ 51

Conclusion ............................................................................................................................... 52

Self-Criticism ........................................................................................................................... 53

References ................................................................................................................................ 54

Table 1 : File structure ............................................................................................................. 12

Table 2 : Test plan.................................................................................................................... 37
Table 3 : expect result 1 ........................................................................................................... 38
Table 4 : Expect result 2 .......................................................................................................... 39
Table 5 : Expect result 3 .......................................................................................................... 39
Table 6 : Expect Result 4 ......................................................................................................... 40
Table 7 : Expect Result 5 ......................................................................................................... 40
Table 8 : Expect Result 6 ......................................................................................................... 41
Table 9 : Expect Result 7 ......................................................................................................... 42
Table 10 : Feedback 1 .............................................................................................................. 42
Table 11 : Feedback 2 .............................................................................................................. 43
Table 12 : Self Criticism .......................................................................................................... 53

Figure 1 : Abstraction ................................................................................................................ 8

Figure 2 : Encapsulation ............................................................................................................ 9
Figure 3 : Inheritance ............................................................................................................... 10
Figure 4 : Polymorphism ......................................................................................................... 11
Figure 5 : Use case ................................................................................................................... 15
Figure 6 : Class Diagram ......................................................................................................... 16
Figure 7 : Sequence of Student ................................................................................................ 17
Figure 8 : Sequence of Professor ............................................................................................. 18
Figure 9 : Registrar .................................................................................................................. 19
Figure 10 : ER Diagram ........................................................................................................... 20
Figure 11 : VSIDE ................................................................................................................... 21
Figure 12 : VSIDE code ........................................................................................................... 21
Figure 13 : If-else Statement .................................................................................................... 23
Figure 14 : Switch statement.................................................................................................... 23
Figure 15 : While loop ............................................................................................................. 24
Figure 16 : Do-while loop ........................................................................................................ 25
Figure 17 : For loop ................................................................................................................. 25
Figure 18 : Login page ............................................................................................................. 26
Figure 19 : Login code ............................................................................................................. 27
Figure 20 : Lecturer ................................................................................................................. 27
Figure 21 : Lecturer Code ........................................................................................................ 28
Figure 22 : Lecturer Registration ............................................................................................. 28
Figure 23 : Lecturer Registration Code ................................................................................... 29
Figure 24 : Student Registration .............................................................................................. 29
Figure 25 : Student Registration Code ..................................................................................... 30
Figure 26 : Update Lecturer ..................................................................................................... 30
Figure 27 : Update Lecturer Code ........................................................................................... 31
Figure 28 : View Lecturer ........................................................................................................ 31
Figure 29 : View Lecturer Code .............................................................................................. 32
Figure 30 : View Student ......................................................................................................... 32
Figure 31 : View Student Code ................................................................................................ 33
Figure 32 : Lecturer ................................................................................................................. 33
Figure 33 : Lecturer Code ........................................................................................................ 34
Figure 34 : Student ................................................................................................................... 34
Figure 35 : Student Code ......................................................................................................... 35
Figure 36 : Bill ......................................................................................................................... 35
Figure 37 : Bill Code................................................................................................................ 36
Figure 38 : Installation 2 .......................................................................................................... 45
Figure 39 : Installation 1 .......................................................................................................... 45
Figure 40 : Installation 4 .......................................................................................................... 46
Figure 41 : Installation 3 .......................................................................................................... 46
Figure 42 : Login ..................................................................................................................... 47
Figure 43 : Student ................................................................................................................... 47
Figure 44 : Lecturer ................................................................................................................. 48
Figure 45 : Registrar ................................................................................................................ 48
Figure 46 : Lecture registration................................................................................................ 49
Figure 47 : Gantt chart ............................................................. Error! Bookmark not defined.
 1. Pillar concepts of Object Oriented Programming
1.2.What is Object Oriented Programs
Object-oriented programming (OOP) is a programming language model organized around
objects rather than "actions" and data rather than logic. Historically, a program has been viewed
as a logical procedure that takes input data, processes it, and produces output data.

The programming challenge was seen as how to write the logic, not how to define the data.
Object-oriented programming takes the view that what we really care about are the objects we
want to manipulate rather than the logic required to manipulate them.

The first step in OOP is to identify all the objects the programmer wants to manipulate and
how they relate to each other, an exercise often known as data modelling. Once an object has
been identified, it is generalized as a class of objects (think of Plato's concept of the "ideal"
chair that stands for all chairs) which defines the kind of data it contains and any logic
sequences that can manipulate it. Each distinct logic sequence is known as a method.

Benefits of OOP (Object Oriented Programs)

 The concept of a data class makes it possible to define subclasses of data objects that
share some or all of the main class characteristics. Called inheritance, this property of
OOP forces a more thorough data analysis, reduces development time, and ensures
more accurate coding.
 Since a class defines only the data it needs to be concerned with, when an instance of
that class (an object) is run, the code will not be able to accidentally access other
program data. This characteristic of data hiding provides greater system security and
avoids unintended data corruption.
 The definition of a class is reusable not only by the program for which it is initially
created but also by other object-oriented programs (and, for this reason, can be more
easily distributed for use in networks).
 The concept of data classes allows a programmer to create any new data type that is not
already defined in the language itself.
 There are four main pillar concepts of OOP

1. Abstraction
2. Encapsulation
3. Inheritance
4. Polymorphism

1.1.1 Abstraction
This is a process of showing only the relevant data and hiding the unnecessary details of an
object from the user. In other words, abstraction refers to a base class where it can be shared
by multiple derived classes as well. As mentioned earlier abstraction is mechanism to show
only the relevant data to the user

Figure 1 : Abstraction
 Benefits of Abstraction

 This helps the programmers in different situations

 This will reduce the size of the code (vomit the unnecessary codes in the program)
 Saves time
 Solves the problem in Design Level
 Reduces the complexity of the problem

1.1.2 Encapsulation
In Object Oriented Programming, the Encapsulation is the process to prevent or protect
the codes from any sort of accidental corruptions and due to some little silly errors. In OOP
data are mainly treated as a critical element. Instead of determining the data in public form, it
can be declared in private. Here, the private data is manipulated indirectly by two ways. The
initial method that is used to manipulate is using a pair of conventional accessor. The second
manipulating method is using a named property. Finally, the main idea is using the data without
any changes or corruptions.

Figure 2 : Encapsulation
 Benefits of Encapsulation

 The main purpose is to protect important data inside the class and not to expose outside
of the class
 In other words, hiding the internal state, behaviour of an object
 Keep safe from outside interference and misuse
 Solves problems in the level of implementation

1.1.3 Inheritance
This is another main concept in Object Oriented Programming. This is the action of
where one class acquires the properties and the functionalities of another class is referred as
the inheritance. Inheritance provides the idea of reusability of the codes and each sub class
defines only those features that are unique. In other words, Inheritance is the process of
determining a new class based on an existing class.

Figure 3 : Inheritance
 Benefits of Inheritance

 The code which is in the base class need not to be rewritten

 This allows to modify the behaviour of an existing class
 Reusability of the existing code
 The codes which are in superclass need to be written again in the sub class

1.1.4 Polymorphism
This is another concept of Object Oriented Programming, which allows to perform a
single action in many ways. Like the ability of a function, variable or object to take on multiple
forms. This concept is used in programming world where the software entities need to show
some different behaviours while they are in the same type and sharing all the other common
features as well

Figure 4 : Polymorphism
 Benefits of Polymorphism

 The purpose of polymorphism in OOP is when having different types of objects and
can write classes that can work with all those different types
 When compared to the example which is given below, this concept is helpful when we
have multiple kinds of “Flying Machines”
 When building generic frameworks that will take the whole bunch of different objects
with the same interface
 This allows programmer to call the methods of derived class by referencing to the base
class

2. File structures of design

Table 1 : File structure

Stafford University Management System

IDENTIFICATION OF OBJECT AND DATA AND FILE STRUCTURES
No. Entity Data File Structure
01 Student Student_ID: int; Register ();
First_Name: varchar; Login ();
Last_Name: varchar; Select_Course ();
DOB: string; Register_for_Course ();
Address: varchar; Check_Course ();
Contact_No: int; View_Course_Catalog ();
Email: varchar; View_Curriculum ();
St_Account: varchar; Send_Request ();
Username: varchar; Add_Course ();
Password: varchar; Drop_Course ();
Sign_out ();
View_Print_Bill ();
02 Professor Pro.ID: int; Login ();
First_name: varchar; Select_course ();
Last _name: varchar; Register_course ();
DOB: string; Check_course_catlog ();
Contact No: int; Check _course_roster ();
Email: varchar; Signout ();
Pro_Account: varchar;
Batch_report: varchar;
Username: varchar;
Password: varchar;
03 Registrar First_name: varchar; Login ();
Last_name: varchar; Enter_Professor ();
Email: varchar; Enter_Course ();
Contact_no: int; Enter_Student ();
Username: varchar; Create_batch_report ();
Password: varchar; Update_student ();
Delete_student ();
Search_student ();
Update_professor ();
Delete_professor ();
Search_professor ();
Update_course ();
Delete_course ();
Search_course ();
View_student ();
View_professor ();
View_course ();
Generate_course_catalog
();
04 Billing Receipt_no: int; Print_Bill ();
St_name: varchar;
C_ID: int;
C_name: int;
Date: int;
Currency: varchar;
Payment_method: varchar;
05 Course C_ID: int; -
Programme: varchar;
Duration: string;
Course_outline: varchar;
Course_fee: varchar;
3. UML Diagrams of the software
3.1 Use case diagram

Figure 5 : Use case

3.2 Class Diagram

Figure 6 : Class Diagram

3.3 Sequence Diagram
Student 

Figure 7 : Sequence of Student

Professor

Figure 8 : Sequence of Professor

Registrar 

Figure 9 : Registrar
3.4 ER Diagram

Figure 10 : ER Diagram
4. Visual Studio IDE for the solution

Figure 11 : VSIDE

Figure 12 : VSIDE code

Source file has been attached in mail

5. Control Structure of the solution
In Procedural Programming Languages, control structures are the most essential entities. The
programming languages such as C/C++ are the most well-known languages. When we
critically discuss what a control structure is, this is a primary concept in most high-level
programming languages such as C, C++, COBOL, Pascal and Prolog. Control structures are
mainly used to control the flow of execution of the program. In other words, we can call this
as decision making. For an example, if we consider apply our real life as examples, we can
assume that when we are deciding to continue our field in IT or in any other fields like
accounting, management and psychology. In this example it shows that we are suppose take
make decision by analysing certain conditions such as the demand for the job opportunities,
scope, and personal interest as well. The decision which is made, everyone will alter the flow
of the life’s direction (Valid-computing, 2017).

In programming, the programmers reading or maintaining code need to be able to identify

these control structures easily. The main purpose to use control structures is to make decisions
and alter the direction of the program flow. Now let us discuss what the different types of
control structures in programming are.

4.1 IF-ELSE Statement

If statements are mainly used for developing conditional statements which is followed by
the logical expressions. This means, where the data is compared based on the decision made.
This is a single selection statement where it will select or ignores a single action. The main
function of if statement is, if the given condition is true, the particular statement will be
executed (block of statements will be run) and if the given condition is false the statement will
be skipped.
 Figure 13 : If-else Statement

4.2 Switch Statement

Switch Statements are mainly used when there is an instance to evaluate a variable for
multiple values. In other words, a switch statement will allow a variable to be tested for the
equality against a list of given values. In this scenario, each value or variable name can be
considered as a case. The proper syntax for the switch statement is given below including
examples.

Figure 14 : Switch statement

 4.3 While Loop
Simply, while loop is a statement that will repeatedly executes a target statement as long
as a provided condition is true. In other words, the condition may be an expression, and true is
any non-zero value. The loop will iterate while the condition is true. When the test expression
is false, the while loop is terminated.

Figure 15 : While loop

4.4 Do-While Loop

The next repetition control structure is that the do while loop. This is also considered as a
conditional loop. Which means, do while is an exit condition loop. The Do-While loop
functions much the same way the while loop functions. The difference in do-while loop is that
post-test loop. In do-while loop the statement occurs before the condition. By this we can easily
spot the difference between while loop and do-while loop. Since the statement is executed
before the condition is tested, the do while loop is guaranteed to execute at least once. The
process of a do-while loop is repeated as long as the expression evaluates to true.
 Figure 16 : Do-while loop

4.4 For Loop

For loop is also another loop structure, that is mainly used to execute a set of statements
for a specific number of times only. For loop is an extremely handy control structure for
working with lists of information, such as arrays. This is also known as the most convenient
with counting loops. The proper syntax for the For-Loop statement is given below including
examples.

Figure 17 : For loop

6. Use of an Integrated Development Environment
Visual Studio is the software development application that is mainly used to develop
the Stafford University Management System. Microsoft Visual Studio 2013 Professional is the
version of the software development application, where I had a creative launching of a work
bench for developing the University Management System (UMS) and abled to view and edit
any kind of code and debug as well.

Login page:

Figure 18 : Login page

 Figure 19 : Login code

Registrar:

Figure 20 : Lecturer
 Figure 21 : Lecturer Code

Lecturer Registration:

Figure 22 : Lecturer Registration

 Figure 23 : Lecturer Registration Code

Student Registration:

Figure 24 : Student Registration

 Figure 25 : Student Registration Code

Update Lecturer:

Figure 26 : Update Lecturer

 Figure 27 : Update Lecturer Code

View Lecturer:

Figure 28 : View Lecturer

 Figure 29 : View Lecturer Code

View Student:

Figure 30 : View Student

 Figure 31 : View Student Code

Lecturer:

Figure 32 : Lecturer
 Figure 33 : Lecturer Code

Student:

Figure 34 : Student
 Figure 35 : Student Code

Bill:

Figure 36 : Bill
 Figure 37 : Bill Code

7. Test Plan of the Solution

This is a University Management System, which is mainly developed in order to
overcome the frustration and the time-consuming experience for University of Stafford. The
system mainly consists of three users namely Student, Lecturer and Registrar. The roles and
responsibilities for each user is different in the system. The main user in the UNIVERSITY
MANAGEMENT SYSTEM is the Registrar, registrar is mainly responsible for maintaining
the entire system. The lecturer is responsible to teach students according to the catalog and the
lecturers will be able to check the student details by using the management system. The Student
is another user in the university management system.
7.1.2 Developed Test Plan for University of Stafford

Table 2 : Test plan

UNIVERSITY OF STAFFORD MANAGEMENT SYSTEM

Test Plan ID 001
Brief Introduction to the This is a University Management System which is developed
system to Stafford University. This Software application will mainly
manage all the information of the Students, Lecturers and
Courses in the University. The Registrar will handle the
system in the Stafford University.

Brief Introduction to the This documentation will mainly describe the plan for testing
Testing Objectives Stafford University Management System. The main
objectives are: Testing the main features in the system,
recommended test requirements, and Deliverables
elements of the Test activities

Test Approach Black Box Testing

Assumptions According to this Stafford University Management System,
following are some assumptions used to develop the system,
• The system consists 03 courses namely HND, BIT
and BCS
• The system consists 05 lecturers such as (Shivaraam,
Maheema, Suseendran and Saranki) to teach students
• Each semester consists more than two subjects
• The system consists 15 students including 03 batches
• According to the system there are separate payments
for different courses
Test Items (Modules) Main functions in the System
Features to be tested 1. User Login
2. Search Student
3. View Course
4. Course Registration
5. Create Catalog
6. Insert Lecturer
7. Delete Lecturer
Test Environment At College (Esoft Metro Campus), Home
Test Deliverables Test Plan, Test Environment, Test Summary, Test Result,
Test Evaluation Report
Testing Schedule 31st January 2018, 1.30 PM to 5.30 PM

8. Actual and Expect result of the solution.

Table 3 : expect result 1

PROJECT NAME SU STUDENT TEST ENGINEER Suhail

REGISTRATION
TESTING DATE 2018/01/31
SYSTEM
Test Case ID 001
Product Module User Login Status: Pass
Purpose Ensuring the user can access to their respective page
Pre-Condition Welcome Page
Steps Initially insert the correct USERNAME = admin and PASSWORD
= admin123 in the respective text boxes, then click on “Sign In”
button
Expected Outcome After inserting the correct username and password of a particular
user, the user logged page will be displayed.

Actual Outcome Successfully Logged into the user’s account

Post Condition Able to View, Add and Drop courses
 Table 4 : Expect result 2

PROJECT NAME SU STUDENT TEST ENGINEER Suhail

REGISTRATION
SYSTEM TESTING DATE 2018/01/31
Test Case ID 002
Product Module Search Student Status: Pass
Purpose To ensure that the student will be able to view the details
Pre-Condition The Student ID must be entered
Steps Inserting the student ID in and then click on “View”, then it will
display the name of the course that was assigned for that student ID

Expected Outcome After inserting the student ID, should be able to view the name of
the student and course in the text boxes

Actual Outcome Successfully displayed the student name of the course

Post Condition Display the particular user’s login page

Table 5 : Expect result 3

PROJECT NAME SU STUDENT TEST ENGINEER Suhail

REGISTRATION
SYSTEM TESTING DATE 2018/01/31
Test Case ID 003
Product Module View Course Status: Pass
Purpose To ensure that the lecturer will be able to view the duration of
courses

Pre-Condition Should select the relevant course from the combo box
Steps The lecturer should select the respective course and then click on
“View” to get the output of the process
Expected Outcome After inserting the selecting the course, the lecturer will be able to
view the duration of the selected course

Actual Outcome Successfully displayed the duration in the text box

Post Condition -
 Table 6 : Expect Result 4

PROJECT NAME SU STUDENT TEST ENGINEER Suhail

REGISTRATION
SYSTEM TESTING DATE 2018/01/31
Test Case ID 004
Product Module Course Registration Status: Pass
Purpose Adding Courses to the System
Pre-Condition Registrar should login using correct credentials and select course
maintenance

Steps Insert USERNAME and PASSWORD, then click the “Sign In”
Button. Then it will direct to the registrar’s portal and then click on
“Course Maintenance”. Then it will direct to the “Course
Maintenance” option, by inserting the course records the registrar will
be able to register for courses

Expected Outcome After inserting the course records the records should be successfully
inserted to the system

Actual Outcome Successfully message displayed in detail (“RECORDS INSERTED

SUCCESSFULLY”)
Post Condition -

Table 7 : Expect Result 5

PROJECT NAME SU STUDENT TEST ENGINEER Suhail

REGISTRATION
SYSTEM

TESTING DATE 2018/01/31

Test Case ID 005

Product Module Create Catalog Status: Pass

Purpose Generation of the course catalog for a semester

Pre-Condition Registrar should login using correct credentials and select create
catalog
Steps Insert USERNAME and PASSWORD, then click the “Sign In”
button. Then it will direct to the registrar’s portal and then click on
“Create Catalog”. Then it will direct to the “Create Catalog”
option, by inserting the course name, semester and the subjects the
registrar will be able to generate the course catalog for the semester

Expected Outcome After inserting the records, it should successfully have inserted to
the system

Actual Outcome “RECORDS INSERTED SUCCESSFULLY”

Post Condition -

Table 8 : Expect Result 6

PROJECT NAME SU STUDENT TEST ENGINEER Suhail

REGISTRATION
SYSTEM TESTING DATE 2018/01/31
Test Case ID 006
Product Module Insert Lecturer Status: Pass
Details
Purpose Inserting lecturer records to the system
Pre-Condition Registrar should login using correct credentials and select lecturer
maintenance

Steps Insert USERNAME and PASSWORD, then click the “Sign In”
button. Then it will direct to the registrar’s portal and then click on
“Lecturer Maintenance”. Then it will direct to the “lecturer
maintenance” option, by inserting the lecturer ID, lecturer name and
the contact no. the registrar will be able to insert the lecturer details to
the system

Expected Outcome After inserting the lecturer records, it should successfully have inserted
to the system

Actual Outcome “RECORDS INSERTED SUCCESSFULLY”

Post Condition -
 Table 9 : Expect Result 7

PROJECT NAME SU STUDENT TEST ENGINEER Suhail

REGISTRATION
SYSTEM TESTING DATE 2018/01/26
Test Case ID 007
Product Module Delete Lecturer Status: Pass
Details
Purpose Deleting lecturer records to the system
Pre-Condition Should insert the lecturer ID
Steps Insert USERNAME and PASSWORD, then click the “Sign In”
button. Then it will direct to the registrar’s portal and then click on
“Lecturer Maintenance”. Then it will direct to the “lecturer
maintenance” option, by inserting the lecturer ID and click on
“Delete” the registrar will be able to delete the lecturer details from
the system

Expected Outcome After inserting the lecturer ID for deletion, the records should have
successfully deleted from the system

Actual Outcome “RECORDS INSERTED SUCCESSFULLY”

Post Condition -

9. Feedback of the solution.

User name: - Ravi Kumar (Software Developer)
Table 10 : Feedback 1

No Question User feedback

01 Is the user interface easy to understand? Yes is the user interface is very easy to
understand

02 What about the onscreen assist during using Onscreen assist is best for understand the
the library management System? system.

03 How user friendly is this User friendly is best ok good try.

Library management System?
 04 How well do Library Management System This system help to finish our needs
meet your needs? quickly.

05 If any problem encountered during using Sometime admin login system loading.
Library Management System?

06 What about the security features of Library Increase your security features.
Management System?

07 What do you like best feature of the Library Borrow Books is the best feature
Management System?

08 Would you like to recommend our system Yes

someone else?

09 Any special Comments? No

User name: - Ushan Mohamed (Software Engineer)

Table 11 : Feedback 2

No Question User feedback

01 Is the user interface easy to understand? Yes is the user interface is good for
understand

02 What about the onscreen assist during using Onscreen assist is very important for this
the Library Management System? system good.
 03 How user friendly is this User friendly75% best.
Library Management System?

04 How well do Library Management System This system complete our needs very
meet your needs? well.

05 If any problem encountered during using I want more Details in Add member form
Library Management System?

06 What about the security features of Library Security features ok good.

Management System?

07 What do you like best feature of the Library Form alignment is good try.
Management System?

08 Would you like to recommend our system No

someone else?

09 Any special Comments? Add some details in Add Members form

Conclusion

Based on the evaluation, the developed application has provided an appropriate solution
for the frustrating problem at the Stafford University. All the user requirements were addressed
within the developed system and there is an elimination of paper-based processes. Some users
required the system to be more attractive and user-friendly and this will help to enhance the
development of the system. Based on the requirements, the system provides a clear
understanding and the system structure serves as reliable unit in the University Management
System.
10. User Guidance and technical documentation.
10.1 Installation Guide
Follow the Picture number order to install the software successfully.

Figure 39 : Installation 1

Figure 38 : Installation 2
Figure 41 : Installation 3

Figure 40 : Installation 4
10.2 User guidance

Figure 42 : Login

Registrar and Lecturer want to give the username and password of their account to login but
if the user is student he/she can use the software without password but the student can’t give
the vote for module without gave their ID of their account. Registrar and Lecturer can access
the software by clicking the “Log In” button after giving their password and username.

Figure 43 : Student

If the user click the “No I’m Student” button they can visit this page to provide vote for their
module which Lecturer should teach. Before the users giving vote they must give their ID to
check user information and validation. If the user already gave the vote they can able to see
their billing information of their modules by clicking “Confirm Bill” button.
 Figure 44 : Lecturer

This page for lecturers. If the lecturers enter correct username and password of their account
like figure 42. They can able visit lecturer’s page to provide their vote which they are going
to teach next semester not only they can vote but also they can able to see student votes also
by clicking “See students vote”.

Figure 45 : Registrar

This is registrar page he/she can add, edit and view of the student, lecturer and Modules of
the Stafford University. If he/she want to add something new he/she can use Registration
button it contain Student, Lecturer and Modules they can add by using the button. If he/she
want to edit information button which also contain like Registration button. Not only view
button different but also like other buttons. If the user want to log out the account he/she can
use the log out button by clicking that.

Figure 46 : Lecture registration

In here, lecturer registration can be held by Registrar by using this page if the registrar made
some typing mistakes he/she can use the reset button to clear all text box. After filling correct
information she/he can click the ADD button to add new lecturer and student registration also
like this.
Gantt chart
Appendix

OOPtry.zip
Future Enhancement

The main effort to create this system more user-friendly and creating the system with
more features like advanced graphical user interfaces that will make the user to attract to
interact and helpful to use the system efficiently and effectively. There might be a great
advantage if there is a new feature to add any new fields and details to the management system.
This will reduce in time consumption. An improvement should be done in the way of inserting,
updating and deleting the records in the University Management System. The user
documentation will give a brief knowledge to the user to interact and should improve the
graphical interfaces in user documentation. If I can make the system more attractive and
userfriendly, it will be more points in development. The Administrator in the university
management system should be given more options and increase the security.

Finally, by considering the security in a database. There should be a critical improvement in

order to protect the database form various kinds of threats using different kinds of control
mechanisms.

Conclusion

This document is all about Object Oriented Programming, based on a database that
is developed for the Stafford University Management System. The main requirement of SU is
to maintain the university records efficiently and effectively using a proper management
system.

I have provided my best and developed this application which includes all the features.
In the first task I have briefly discussed the pillar concepts of Object Oriented Programming
by including its characteristics, purposes and with the examples which I have used in my
application. In the second task, I have identified the objects and data structures which is
required to implement the given design. In the third task, I have designed the use case
(including use case narratives), class, sequence and entity relationship diagrams for the given
scenario. In the fourth task, I have implemented the objected oriented solution using C#.net.
In the fifth task, I have provided the evidences of implementation of the object behaviors using
control structures. In the sixth task, I have evaluated the effective use of an IDE, including
important code snippets and screenshots of important UI’s. In the seventh task, I have
prepared the test plan that covers the important functionality of the system. In the eighth task,
I have analysed the actual test results using the test cases in order to overcome the discrepancies
occurred. In the ninth task, I obtained the independent feedback for the proposed solution
using questionnaires. And I had provided the recommendations and suggestions for the
improvements and the conclusion. In the tenth task, I have prepared the onscreen help and the
technical documentation for the developed system and the maintenance of the system.

Self-Criticism

I should specially convey my deepest gratitude to our lecturer Miss. Ishani Jayasuriya, who
helped me a lot to obtain the required information.

I guess that I have tried my best to deliver a best answer to the question based on the case
study. I hope the question were answered properly that satisfies the examiner. I had plenty of
time to complete this assignment before the deadline.

I tried and gave my best to produce this assignment and I have delivered the best answers to
the questions. I hope all the questions were answered properly, which satisfies the examiner.
When doing this assignment, I felt comfortable doing the assignments due to the liking and
willingness towards the subject, I was able to complete this assignment with my level best in
the given time period. This assignment made me strong and realizes many things about object-
oriented programming modules. Especially now I am well familiar with this module.

During this assignment my strengths and weaknesses are as follows:

Table 12 : Self Criticism

Strengths Weaknesses
Confidence in completing the assignment Difficulties in when explaining to others
before the deadline

Interest throughout the module and The time spent on a single task was quite
developing the system long

A big support from my family members Difficulties in arranging the tasks from
within the given time single documents

Was able to understand how to develop a

system using Visual Studio
All the required information gathered easily

Self-satisfied with my time management

Finally, I used to find useful articles, books

and websites which I gained very useful
information

References

Adobe.com. (2017). Object-oriented programming concepts: Objects and classes | Adobe

Developer Connection. [online] Available at:

http://www.adobe.com/devnet/actionscript/learning/oop-concepts/objects-and-classes.html

Azad, C. (2017). C# Inheritance. [online] Available at:

http://www.csharpcorner.com/UploadFile/azadc/C-Sharp-inheritance/

Chegg.com. (2017). Basic Control Structures. [online] Available at:

https://www.chegg.com/homework-help/definitions/basic-control-structures-3

Ching, P. (2017). Control Structures. [Blog] SMK Lundu ICT Class. Available at:

http://smklunduictclass.blogspot.com/2012/07/5154-differentiate-between-sequence.html

Completecsharptutorial.com. (2017). Concepts of Encapsulation and Abstraction (C#)C#

Tutorial | C# Tutorial. [online] Available at:
http://www.completecsharptutorial.com/basic/understanding-concepts

Cook, R. (2016). What is the sequence control structure?. [online] Quora. Available at:
https://www.quora.com/What-is-the-sequence-control-structure

Creatively, (2017). Ultimate Guide to ER Diagrams ( Entity Relationship Diagrams ). [Blog]

creately. Available at: http://creately.com/blog/diagrams/er-diagrams-tutorial

Docs.microsoft.com. (2017). Visual Studio IDE overview. [online] Available at:

https://docs.microsoft.com/en-us/visualstudio/ide/visual-studio-ide
Docs.oracle.com. (2017). Lesson: Object-Oriented Programming Concepts (The Java™
Tutorials > Learning the Java Language). [online] Available
at: https://docs.oracle.com/javase/tutorial/java/concepts/

Fowler, M. (2004). When to Use Sequence Diagrams | UML Sequence Diagrams | InformIT.
[online] Informit.com. Available at:
http://www.informit.com/articles/article.aspx?p=169507&seqNum=4

Loganathan, G. (2017). OOP: Polymorphism. [online] Java Helps. Available at:

http://www.javahelps.com/2015/02/oop-polymorphism.html

Lucidchart. (2017). What is Unified Modeling Language. [online] Available at:

https://www.lucidchart.com/pages/what-is-UML-unified-modeling-language

Make Selenium Easy. (2017). OOPs. [online] Available at:

https://sasiqa.wordpress.com/oops/

Margaret, R. (2017). What is class? - Definition from WhatIs.com. [online] Available at:
http://whatis.techtarget.com/definition/class

O'Dell, J. (2010). A Beginner's Guide to Integrated Development Environments. [online]

Puran, M. (2009). Polymorphism in C#. [online] Available at:

http://www.csharpcorner.com/UploadFile/puranindia/polymorphism-in-C-Sharp/

Quadri, A. (2018). Fact Finding Techniques | Intelligence Analysis | Communication. [online]

Scribd. Available at: https://www.scribd.com/doc/6902721/Fact-Finding-Techniques

Ritzhaupt, A. (2005). Repetition Control Structures. 4th ed. p.4.

Smartdraw.com. (2017). Use Case Diagrams - Use Case Diagrams Online, Examples, and
Tools. [online] Available at: https://www.smartdraw.com/use-case-diagram

Stackify. (2017). What Are OOPs Concepts in Java? The Four Main OOPs Concepts in Java,
How They Work, Examples, and More. [online] Available at:
https://stackify.com/oopsconcepts-in-c#/

Techterms.com. (2017). OOP (Object-Oriented Programming) Definition. [online] Available

at: https://techterms.com/definition/oop
Thomas, D. (2017). What is UML? The Unified Modelling Language Explained. [online]
Available at: http://dthomas-software.co.uk/resources/frequently-asked-questions/what-
isuml-2/

Timothy, B. (2004), An Introduction to Object-Oriented Programming, 2nd edition.

Singapore: Pearson Education.

Tutorialspoint. (2017). UML - Class Diagram. [online] Available at:

https://www.tutorialspoint.com/uml/uml_class_diagram.htm

UKEssays. (2015). Definition Of Fact Finding Techniques Information Technology Essay.

[online] Available at: https://www.ukessays.com/essays/information-technology/definitionof-
fact-finding-techniques-information-technology-essay.php

Valid-computing.com. (2017). Control Structures. [online] Available at:

http://www.validcomputing.com/control-structures.html

Visual-paradigm.com. (2017). What is Unified Modeling Language (UML)?. [online]

Available at: https://www.visual-paradigm.com/guide/uml-unified-modeling-
language/whatis-uml/

Wideskills.com. (2017). C# Control Statements | C# tutorial by Wideskills. [online] Available

at: http://www.wideskills.com/csharp/control-statements
Gantt chart

November
N Task 01 December 01 December 15 December 28 January 20
o
W T F S W T F S W T F S W T F S W T

Selecting
1 and
studying
about the
Organizatio
n

2 Collected
informatio
n

starting
3 do the
Assignmen
t

4 Finishing

5 Finalizing

6 Submission