1. ARMY PUBLIC COLLEGE OF
MANAGEMENT AND SCIENCES
STUDENT EXAMINATION SYSTEM
Group members:
Maryam Saifullah
Aqsa Rafique

2. SYSTEM
DEVELOPMENT
LIFECYCLE (SDLC)

3. ANALYSIS PHASE
Feasibility analysis
Requirement analysis

4. FEASIBILITY ANALYSIS
 The feasibility study of any system is mainly
intended to study and analyze the proposed
system and to decide whether the system under
consideration or not.
 “Calculation of risk involved in the system is
called feasibility analysis”
 Risk in the examination system is approximately
equal to zero so this system is said to be
feasible.

5. FEASIBILITY ANALYSIS
Economic feasibility
Technical feasibility
Operational feasibility
Legal feasibility

6. ECONOMIC FEASIBILITY
Economic analysis is most frequently
used for evaluation of the system.
Most commonly knows as cost/benefit
analysis.
The procedure is to determine the
benefit and savings that are expected
from a system.

7. S.NO ITEMS QUANTITY COST BENEFITS
1 furniture 102 50,000 On rent, made it
easy to get chairs
and tables.
2 Roll slips 102 20,000 Easy to recognize
our students.
3 rooms 8 10,000 Rooms were
distempered in
less cost to give a
clean look to the
rooms.
4 supervisors 16 15,000 Each supervisor
was paid a
reasonable amount
of money to keep a
strict eye on
students.

8. TECHNICAL FEASIBILITY
 According to feasibility analysis procedure
the technical feasibility of the
system is analyzed and the technical
requirements such as software facilities,
procedure, inputs are identified.
 In our case IT experts were required for
keeping the record of the exams held and
an analyst to analyze the report of students.

9. OPERATIONAL FEASIBILITY
 This system is running properly till now with
no issue by the students or anyone else.
The teachers and students both are
satisfied.
 Nor our exams delayed nor they are
cancelled, everything is done on time. Even
the result is also displayed on the
mentioned date given to the student at the
last day of the examination.

10. LEGAL FEASIBILITY
The orders are also not against
the system and there is no law
violation in the examination
system of APCOMS.

11. REQUIREMENT ANALYSIS
To provide the functionality to students to appear
for the exam.
 This system should handle multiple exams at the
same time.
To enable Exam Controller to define criteria and
create Admin and Experts.
To enable Exam Dept Admin to declare schedule
and Results.
To enable Expert to send set of Questions.

12. SYSTEM ANALYSIS TOOLS
Organizational materials:
Through university’s magazines,
prospectus and website we got all
the information without any
trouble.

13. DESIGN PHASE
System design
 It tells how sub systems are linked
together
 It’s the outlook
Detailed design
Each and every minute detail of the
system

15. Many students can M
give many exams
Student Course
M
M
Faculty Department
One faculty can
teach many
courses
1
1
One department
can have many
faculty
1
1
Exam
M
One faculty can
teach many
students
Result
M
M
1
M
1
M

16. DESIGN PHASE
Convert ER_Diagram into tables
Department: (Department no, Name,
Location)
Student: (Roll no, Name, Address, Contact
no, Registration no, Deptno)
Faculty: (Faculty ID, Name, Hiredate,
Contact no, Deptno)

17. CONVERT ER-DIAGRAM INTO TABLES
Exam: (Exam ID, type, Date, Exam
fee, Roll no)
 Course: (Course ID, Title, Credit
hours)
 Result: ( Date, Grade, Rollno)

18. NORMALIZATION
 Student:
Student(Rollno , Name , Registration no , Deptno)
 Student Add:
Student add (rollno, address)
 Studentcontact:
Studentcontact(rollno, contactno)
 Faculty:
Faculty(Name, Hiredate , Deptno)
 Facultycontact:
Facultycontact(facultyID, contactno)

19. CODING
SQL commands
DDL
DML
DD
TCC

20. CODING
SQL commands:
Composite key:
SQL> Create table STUDENTADD
(Rollno Number(6), Address
VARCHAR2(16), PRIMARY
KEY(Rollno, Address));

21. SQL COMMANDS
 Foreign key:
 SQL> Create table EXAM( ExamID Number(7)
PRIMARY KEY, Type VARCHAR2(9), ExamDate
DATE, Examfee Number(4) NOT NULL), rollno
number(6) reference student(rollno));

22. SQL COMMANDS
 DEFAULT:
 SQL> create table Course (CourseID Number(8)
PRIMARY KEY, Title VARCHAR2(19), Crhrs
Number(2) DEFAULT 3);

23. SQL COMMANDS
UNIQUE:
 SQL> Create table STUDENT (Rollno
Number(6) PRIMARY KEY, Name
VARCHAR2(15) NOT NULL, Registrationno
Number(6) NOT NULL UNIQUE), deptno
number(2) reference
DEPARTMENT(departmentno));

24. DESC COMMANDS
SQL> Desc student;
SQL> Desc studentadd;
SQL> Desc exam;
SQL> Desc result;
SQL> Desc faculty;
SQL> Desc facultycontact;
SQL> Desc department;

25. INSERT COMMANDS
SQL> Insert Into STUDENT values
(123456,’Alina’, 54102,10);
ROLLNO NAME REGISTRATIONNO
---------- --------------- --------------
123456 ALINA 54102

26. SELECT COMMANDS
SQL> Select * from exam;
EXAMID TYPE EXAMDATE EXAMFEE
---------- --------- --------- ----------
7235 Midterm 16-MAY-14 560

27. Distinct clause:
SQL> Select distinct deptno from
department;
o Where clause:
SQL> Select name from student
where name=’ALI’;

28. ANDOR CLAUSE
SQL> Select examfee from exam
where examfee<4900 OR
examfee>4910;
• SQL> Select title from course
where title=’BBA’ AND
Title=‘BSC’;

29. IN clause:
SQL> Select * from student where
departmentno IN(10,30);
BETWEEN clause:
SQL> Select * from exam where examfee
BETWEEN 4000 AND 5000;

30.  LIKE clause:
 SQL> Select * from student where name
LIKE(‘%ALI%’);
ORDER BY:
 SQL> select * from student ORDER BY name;
DELETE command:
 SQL> DELETE from Student where deptno=10;

31. CHARACTER FUNCTION
 Case conversion Function:
 LOWER:
SQL> Select Lower (name) from
STUDENT;
 UPPER:
SQL> Select UPPER(Title) from course;
 INITCAP:
SQL> Select INITCAP(name) from
department;

32. Character Manipulation Function:
 CONCAT:
SQL> select concat(name, 'WELCOME')
student from student;
 SUBSTRING:
SQL> select Substr(name,1,3) STUDENT from
student;
 LENGTH:
SQL> select LENGTH(name) STUDENT from
student;

33. INSTRING:
SQL> Select Instr(name,'F') Result from
student;
LEFTPADDING:
SQL> select LPAD(examfee,5,'*') Fee
from exam;

34. NUMBER FUNCTIONS:
ROUND:
SQL> Select ROUND ((Sysdate-
Hiredate),1) from faculty;
TRUNCATE:
SQL> Select Trunc ((Sysdate-hiredate),2)
from faculty;
MODE:
SQL> Select omarks,tmarks,mod
(Omarks,tmarks) from result;

35. ARTHEMATIC FUNCTIONS:
 SQL> select name,
sysdate,hiredate,ROUND((sysdate-hiredate)/7,2)
WEEKS from faculty;
 SQL> Select name,(Sysdate-hiredate) Days from
faculty;
 SQL> Select name,hiredate,
sysdate,ROUND(MONTHS_BETWEEN(Sysdate-
Hiredate),0) MONTHS from faculty;

36. EXPILICIT DATATYPE CONVERSION
TO_CHAR:
SQL> select to_char (examfee,'99,999') FEE
from exam;
TO_DATE:
SQL> to_date(‘01-JAN-2009’) from faculty;
TO_number:
SQL> to_number(‘1210.73’,9999.99’) from
exam;

37. GROUP FUNCTIONS
 COUNT:
SQL> select count(*) from student;
 AVERAGE:
SQL>select avg(examfee) AVERAGE from exam;
 MAXIMUM:
SQL> select max(examfee) from exam;
 MINIMUM:
SQL> select min(examfee) EXAMFEE from faculty;

38. NULL VALUE FUNCTION(NVL)
SQL> select name, NVL(examfee,0)
EXAMFEE from student;

39. TESTING
the goal of testing is to find defects
through the execution of the system or
software package.
Our system is tested and approved by
the faculty and other workers.

40. IMPLEMENTATION
As our project is passed to quality
team and approved as well, our
database can be deployed on
APCOMS examination system.
The project is checked twice by the
implementer.

41. DOCUMENTATION
Documents are provided for each of
the phase but the one issued to the
public will be a different one.
It will help us use the database
accordingly to the specifications.