ACKNOWLEDGEMENT

Exchange of ideas generate the new object to work in a better way whenever a person is
helped and cooperated by others his heart is bound to pay gratitude and obligation to
them. To develop a project is not a one-man show. It is essentially a collective work,
where every step taken with all precautions and care. Therefore our first duty is to thanks
all persons who took pain in completing this project.

Firstly, we thank Mrs. RACHNA SETHI, who gave us inspiration to do work in this field
and gave us her precious time whenever needed. Thanks may be matter of merely
formality but with us it is expression of heartfelt gratitude to our project supervision. We
are highly indebted for her gestures, invaluable suggestions and boosting confidence to
make this successful. The success of this work is mostly due to her suitable guidance.

We also thank our class fellows and friends, who helped us a lot during our project work.
 CERTIFICATE

This is to certify that the project entitled “INTERNAL ASSESSMENT EVALUATION

SYSTEM” prepared by us, Jigyasa Kaur & Inderpreet Singh for the partial fulfilment of
the requirements of the B.Sc. (Hons.) Comp. Sc. degree, embodies the work, we all are
doing during 4th semester of our course under due supervision of the supervisor from this
college.

SIGNATURE
 INDEX

1. PROJECT INTRODUCTION
1.1 OVERVIEW
1.2 DISADVANTAGES OF THE MANUAL SYSTEM
1.3 OBJECTIVE OF THE PROJECT
1.4 SCOPE OF THE PROJECT

2. PROJECT MANAGEMENT
2.1 INTRODUCTION
2.2 PROJECT PLAN
2.2.1 SOFTWARE PROCESS MODEL
2.2.2 PROJECT TEAM STRUCTURE
2.2.3 RISK ANALYSIS & MANAGEMENT
2.2.4 TIME-LINE CHART
2.3 COMPLEXITY TABLES
2.4 FUNCTION POINT ANALYSIS

3. REQUIREMENT ANALYSIS & MANAGEMENT

3.1 INTRODUCTION
3.2 FUNCTIONAL REQUIREMENTS
3.3 DATA DICTIONARY
3.4 ENTITY RELATIONSHIP DIAGRAM
3.5 DATA FLOW DIAGRAM

4. DESIGN
4.1 INTRODUCTION
4.2 DATA DESIGN
4.3 ARCHITECTURAL DESIGN
4.4 INTERFACE DESIGN
4.5 SCREENS DESCRIPTION
 CHAPTER 1

PROJECT

INTRODUCTION
1.1 OVERVIEW

The exact talent of a student cannot be judged, however hard a student may attempt,
during the stipulated period of 3 hrs in the final exam.
Hence, Delhi University has earmarked 25% marks to be awarded to the college
students on the basis of their individual performance during their stay in the college.
The university has advised the teachers that the internal assessment should be objective
rather than subjective.
The marking scheme of the INTERNAL ASSESSMENT SYSTEM is grouped in 3 different
categories i.e.
10% for house examination marks,
5% for the attendance &
10% for assignments and project submitted by each.
The students secure only what they deserve out of the above mentioned 3 categories.
1.2 DISADVANTAGES OF THE MANUAL SYSTEM

1. Maintaining records as paperwork is a cumbersome task.

2. Too many calculations done manually leads to chances of errors which in turn can
disrupt the final outcome of the software.

3. There can be threat to the security of the records, since anyone can easily
access and modify these.
1.3 OBJECTIVE OF THE PROJECT

The objective of our project is to computerize the revised Internal Assessment

Evaluation Scheme for B.Sc(H) Computer Science, Delhi University.

This software also enhances the security features (by using passwords) that are void in
the traditional ways of implementation of the information storage.
1.4 SCOPE OF THE PROJECT

The software product INTERNAL ASSESSMENT EVALUATION SYSTEM will

be a reporting application that will be used for calculating the internal assessment
of students.

The user is allowed to access the software only if he enters the correct password.
Thereby, providing security from unauthentic users .

Each lecturer marks daily attendance and at the close of the session, marks not
amounting to more than 5% are awarded to each student depending on the
percentage of lectures attended by each to the total lectures.

Again, students submit their assignments periodically which are corrected by

teacher concerned & when the session ends, marks amounting to not more than
10% are awarded to the student keeping in view his/her performance.

Similarly, marks obtained in the house examination are taken into consideration
& on the basis of actual performance each student is awarded marks at the
close of the session which don’t exceed 10%.
Thus various records to be maintained are:

1. User information
2. Course year
3. Semester
4. Current semester
5. Subjects
6. Faculty information
7. Faculty & subjects
8. Database of the students
9. Students attendance
10. Internal assignments/project
11. House examination marks
12. Total internal assessment marks

USER INFORMATION

The security of the software will be maintained with the following inputs:

username
user id
password
COURSE YEAR

The course information is maintained as follows:

year no.
year description

SEMESTER

The semester record contains the following fields:

semester no.
course year no.

CURRENT SEMESTER

It includes the following fields:

current year

SUBJECT

This record contains following fields:

subject name
subject code
semester no.
course year no.
FACULTY INFORMATION

The faculty information includes:

faculty name
faculty code

FACULTY & SUBJECTS

This record includes:

current year semester

faculty code
subject code

DATABASE OF THE STUDENTS

The database of each student is inclusive of :

semester no.
year
enrollment no.
university roll no.
student’s name
birth date
father’s name
mother’s name
address
phone no.
STUDENTS ATTENDANCE

The attendance record will contain the following fields:

current year semester

subject code
enrollment no.
total lectures
lectures attended

ASSIGNMENTS / PROJECT

Following are the fields to be included in this record:

current year semester

subject code
enrollment no.
assignments/project submitted
max. marks
marks scored

HOUSE EXAMINATION MARKS

The house examination marks record will contain the following:

current year semester

subject code
enrollment roll no.
max. marks
marks scored
TOTAL INTERNAL ASSESSMENT MARKS

This is the final record including:

current year semester

subject code
enrollment no.
attendance marks
assignment/project marks
house exam marks
marks of each subject
total marks out of 125
 CHAPTER - 2

PROJECT

MANAGEMENT
2.1 INTRODUCTION

Project management involves the planning , monitoring and control of the people ,
process and events that occur as software evolves from a preliminary concept to an
operational implementation.
Effective software project management focuses on the 4 P’s :-

People , Product , Process , Project.

THE PEOPLE

Software engineering institute has developed a people management capability maturity

model (PM-CMM). The people management maturity model defines the key practice areas
[KPA’s] for software people like :-
recruiting , selection , performance management , training , compensation , carrier
development , organization and work design ,and team / culture development.
THE PRODUCT

Before a project can be planned, product objectives and scope should be established,
alternative solutions should be considered and technical and management constraints
should be identified.
Objectives identify the overall goal of the product from customer’s point.
Scope identifies the primary data, functions and behaviours that characterize the product.
Alternatives enable managers to select the best approach given constraints imposed by
technical interfaces , personnel availability , delivery deadlines
and budgetary restrictions.

Thus, the product factor helps to define the accurate cost estimation , effective risk
assessment and a manageable project schedule.

THE PROCESS

A software process provides the framework from which a comprehensive plan for
software development can be established
Framework activities are populated with tasks , milestones , work products and
quality assurance points. These activities characterize the software product and the project
team.
Umbrella activities i.e. software quality assurance , software configuration management
and measurement overlay the process model.
THE PROJECT

Planned and controlled software projects are conducted to manage complexity.

To avoid project failure, the project manager must
avoid a set of common warning signs ,
understand critical success factors and
develop a common sense approach for planning , monitoring and controlling the project.

2.2
2.3
2.4
2.5
2.6
 2.2 PROJECT – PLAN

2.2.1 SOFTWARE PROCESS MODEL

To solve a particular problem, the project team must incorporate a development strategy
that encompasses the process, methods and tools. This strategy is often referred to as a
process model or a “SOFTWARE ENGINEERING PARADIGM”. The use of a particular
process model or software paradigm is based on the nature of the application.

The following points state the need of a particular software paradigm for development of
a software.

 To improve the quality of software.

 To increase the productivity of software development.

 To develop software on time.

 To produce a reliable software.

 To develop the software with in cost estimates.

 The project has been made following the WATERFALL MODEL.

Waterfall Model / Linear Sequential Model

This is sometimes called the Classic Life Cycle or Linear Sequential Model.
It suggests a systematic approach to software development that begins at the system level
and progress through analysis, design, coding, testing and support.

SYSTEM/INFORMATION
ANALYSIS
ANALYSIS DESIGN CODE TEST
ENGINEERING

The following are the activities that the Linear Sequential Model applies:-

System/Information engineering and modeling

It is essential when software must interact with other elements such as hardware, people
and database. System engineering and analysis encompass requirement gathering at the
system level with a small amount of top-level design and analysis. Information engineering
encompass requirement gathering at the strategic business level and at the business area
level.

Software Requirement Analysis

It is a necessary step to understand the nature of the problem to be built. This phase
gathers the input, output, etc. Requirement for both the system and the software are
documented leading to the requirement specification report.

Design
This phase focuses on the software architecture, data structures, tables, flow diagrams,
interface representations and procedural details. The design translates requirements into
a presentation of software that can be assessed and reviewed before code generation
begins.

Code Generation
The design developed above has to be translated into a machine-readable form. The code
generation step performs this task.

Testing
After the code has been generated, program testing begins. Testing is done to uncover
errors and ensure that defined input produces the actual results as required by the user.

Support
This is a phase when software will undoubtedly undergo change after it is delivered to the
customer. Change will occur because errors have been encountered, because the
software must be adapted to accommodate changes in its external environment, or
because the customer requires functional or performance enhancements. Software
support/maintenance reapplies each of the preceding phases to an existing program
rather than a new one.

2.2.2 TEAM STRUCTURE

The “best” team structure depends on the :-

management style of the organization
the number of people who will populate the team and their skill levels and
the overall problem difficulty.

The three generic team organizations are:

Democratic decentralized (DD)

This software engineering team has no permanent leader. Task coordinators are
appointed for short duration and then replaced by others who may coordinate
different tasks. Communication among team members is horizontal.

Controlled decentralized (CD)

This software engineering team has a defined leader who coordinates specific tasks
and secondary leaders that have responsibility for subtasks. Problem solving
remains a group activity. Communication among subgroups and individuals is
horizontal.

Controlled centralized (CC)

Top- level problem solving and internal team coordination are managed by a team
leader. Communication between the leader and team members is vertical.
We use democratic decentralized [DD] team structure in our project. Our team
comprises of two members:

JIGYASA KAUR (7008718)

INDERPREET SINGH (7008742)

Advantages

 Generate better solutions

 Have greater probability of success when working on difficult problems.

 Best applied to programs with low modularity because of the higher volume of
communication needed

 Results in high morale

2.2.3 RISK ANALYSIS & MANAGEMENT

Risk always involves two characteristics:-

UNCERTAINITY
LOSS

Risk analysis and management is a series of steps that help a software team to
understand and manage uncertainty. Many problems can plague a software project. A risk
is a potential problem-it might happen, it might not. But regardless of the outcome, it’s
really a good idea to identify it, assess its probability of occurrence, estimate its impact,
and establish a contingency plan should the problem actually occur.

Types of risk

PROJECT RISK
They identify potential budgetary, schedule, personnel, resource,
custom potential and requirements problem and there impact
on software project. They threaten the project plan.

TECHNICAL RISK
They identify potential design, implementation, interface
verification, and maintenance problem. They threaten the quality
and timeliness of software to be produced.

BUSINESS RISK
 They often jeopardizes the project or the product and
includes market risk, strategic risk, management risk and budget risk.

Risk strategies

REACTIVE
A reactive strategy monitors the risk project for likely risk and set aside
resources to deal with them, should they become actual problems.
Software team does nothing about risks until something goes wrong.

PROACTIVE
A proactive strategy begins long before technical work is initiated. Potential
risks are identified, their probability impact is assessed, and they are ranked
by importance.

Risk analysis

Risk analysis is a technique to identify and assess factors that jeopardize

the success of a project or achieving a goal. This technique also helps
define preventive measures to reduce the probability of these factors from
occuring and identify counter measures to successfully deal with these
constraints when they develop to avert possible negative effects on the
competitiveness of the company.

This is achieved by:-

 Risk avoidance
 Risk monitoring
 Risk management and contingency plan

RMMM PLAN (Risk Mitigation, Monitoring and Management Plan)

It documents all work performed as a part of risk analysis and is used by

project manager as a part of overall project plan.
Once RMMM has been documented and the project has begun, risk
mitigation and monitoring steps commence.

Risk management

Following steps can be taken for resolution of the mentioned risks:

 Try to develop healthy communication with clients’ staff so as to easily gather

requirements and to train and guide them about the software.

 Divide the work among team members properly to meet the deadlines.

 Try to finish the work at least 10 days before the deadline, as many changes have
to be incorporated after that.

 Timely check the space availability and size of the software.

 Take client approvals after each step of project development.

 Keep a check on the costs and resources so that they do not exceed the estimates.
2.2.4 TIME - LINE CHART

S.NO. TASK DATE OF DATE OF

START END
1 REQUIREMENT
GATHERING
AND ANALYSIS
1.1 Course 26.12.2007 30.12.2007

1.2 Faculty 2.1.2008 6.1.2008

1.3 Students 7.1.2008 9.1.2008

1.4 Internal 11.1.2008 20.1.2008

assessment
1.5 FPA 23.1.2008 27.1.2008

1.6 Data dictionary 28.1.2008 1.2.2008

1.7 ERD 3.2.2008 9.2.2008

1.8 DFD 10.2.2008 17.2.2008

2 DESIGN

2.1 Data design 19.2.2008 22.2.2008

2.2 Architectural design 24.2.2008 29.2.2008

2.3 Interface design 1.3.2008 10.3.2008

2.4 Pseudocode 11.3.2008 15.3.2008

2.3 COMPLEXITY TABLES

Files complexity

FILES NO. OF FIELDS RECORDS COMPLEXITY

USER INFO. 3 (username,user
1 LOW
id,password)
COURSE 4 (course year, sem, 1
LOW
INFO subcode,sub name)
FACULTY 4 (subcode, faculty 1
LOW
INFO name, sem, year)
10 (sem,year,enr no,
DATABASE univ rno., student name,
1
OF birthdate, father name, LOW
STUDENTS mother's name, add.,
ph no.)
ATTENDENCE 6 (sem, subcode, enr
RECORD no.,attendance, marks 1 LOW
out of 5, year)
ASSIGNMENT/ 6 (sem, subcode, enr
PROJECT no., assign/ project
1 LOW
RECORD submitted, marks out of
10, year)
7 (sem, subcode, enr
HOUSE EXAM
no., student name, total 1
RECORD LOW
marks scored, mrks out
of 10, year)
 24(sem,subcode,enr
no.,uni rno,student
INTERNAL
name,att. mrks (out
ASSESSMENT 1
of 5), assign mrks LOW
RECORD
(out of 10), house
exam marks (out
of 10), mrks of each

Input screen complexity

SCREENS FILES NO. OF FIELDS COMPLEXITY

COURSE 4 (subcode, subname,

1 (Course info) LOW
INFO sem,course year)

FACULTY 14 ( subcode , faculty

1 (Faculty info) LOW
INFO for each sub, sem, year)

5 ( sem ,sub code,

ATTENDANCE 1 (Attendance
enr no. , attend., LOW
RECORD record)
year)

ASSIGNMENT/ 6 ( sem , sub code ,

1 (Assign/
PROJECT enr no,assig mrks , LOW
project rec)
RECORD project mks,year)

6 ( sem , sub code ,

HOUSE
1 (House exam enr no., student
EXAMS LOW
record) name, marks out
RECORD
of 50, year)
Output screen complexity

SCREENS FILES NO. OF FIELDS COMPLEXITY

SUBJECT 3 ( sem, subcode,

1 [Course info] LOW
INFO sub name )

10 ( sem, year,enr no, univ

DATABASE rno., student name,
1 [Database of
OF birthdate, father's LOW
students]
STUDENTS name, mother's
name, add., ph no.)

FACULTY 4 ( sub code, faculty

1 [Faculty info] LOW
INFO name, sem no., year)
Query screen complexity
SCREENS FILES NO. OF FIELDS COMPLEXITY

LOGIN SCREEN 1 (User info) 2 (username,password] LOW

6 (sem, subcode, enr no.,

ATTENDANCE 1 (Attendance
attendance, LOW
RECORD record)
marks out of 5,year)

ASSIGNMENT/ 1 (Assign/ 5 (sem, subcode, enr no.,

LOW
PROJECT project rec) marks out of 10, year)
RECORD
7 (sem, subcode, enr no.,
HOUSE EXAM 1 (House exam student name, marks out
LOW
RECORD record) of 50, mrks out of 10,
year)

24(sem,subcode,enr
no.,uni rno,student
name,att. mrks (out
INTERNAL of 5), assign mrks
1 (Internal
ASSESSMENT (out of 10), house AVG
assessment
RECORD exam marks (out
record)
of 10), mrks of each
sub(out of 25), total
mrks (out of 125) )

2.4 FUNCTION POINT ANALYSIS

 CATE TOTA
GORY SIMPLE AVERAGE COMPLEX L

NO. OF
INPUTS 5 X 3 = 15 0X4= 0 0X6= 0 15

NO. OF
OUTPUTS 3 X 4 = 12 0X5= 0 0X7= 0 12

NO. OF
FILES 8 X 7 = 56 0 X 10 = 0 0 X 15 = 0 56

NO. OF
QUERIES 5 X 3 = 15 1X4= 1 0X6= 0 16

UNADJUSTED FUNCTION POINT(UFP) = 99

FP = UFP x [0.65 + 0.01 x Σfi]

= 99 x [0.65 + 0.01 x 42]
FPs = 105.93
 CHAPTER - 3

REQUIREMENT

ANALYSIS

&

MANAGEMENT
3.1 INTRODUCTION

Requirement analysis is a software engineering task that bridges the gap between
system level requirements engineering and software design.

System
level
engineering
Requirement
analysis

Software
design

The software requirements analysis may be divided into five areas of efforts:-

Problem recognition
Recognition of basic problem elements as perceived by the users.

Evaluation and synthesis

Define all data objects, evaluate the flow and content of information, define and
elaborate all functions, understand software behavior and establish interface
characteristics
 Modeling
Functional models represent the information that software transforms, functions enabling
the transformation, and behavior of the system during transformation.

Specification
States the goals and objectives of the software, describing it in context of the
computer based system.

Review
Changes to the specification may be recommended.

Analysis Principles

 The information domain of a problem must be represented and understood.

 The functions to be performed by software must be defined.

 The behaviour of the software must be represented.

 The models that depict information , function and behaviour must be

partitioned in a manner that uncovers detail in a layered fashion.

 The analysis process should move from essential information towards

implementation detail
 3.2 FUNCTIONAL REQUIREMENTS

1. System should incorporate security services.

2. It should provide facility for updating the next semester on the completion of last
one.

3. It should be able to update the faculty information at the commencement of every

semester.

4. The system should update the course information.

5. It should be able to maintain records for attendance, assg, house examination for
each semester.

6. There should be a provision to calculate attendance marks out of 5

7. It should be able to calculate assg marks out of 10

8. Facility should be provided to calculate house examination marks out of 10.

9. At the end system should be able to sum up all the above mentioned marks out of
25 for each subject and finally out of 125.
Analysis model

The analysis model achieves three primary objectives:-

 To describe what the customer requires

To establish a basis for the creation of software design.

To define set of requirements that can be validated.

It uses a combination of text and diagrammatic form to depict requirements for

data ,function and behaviour in a way that is relatively easy to understand and review.
3.3 DATA DICTIONARY

S NO. FIELD NAME DESCRIPTION TYPE LENGTH

1 User Info Contains all details

about various users

1.1 User name It stores the user name Character 30

of the faculty
and administrators

1.2 Password It stores the password Alphanumeric 6

of the corresponding
user id

1.3 User id It stores the id of each Numeric 4

user

2. Course year Contains all details

about course years
2.1 Year No. It stores the course year Numeric 1
nos.
2.2 Year It stores description Character 30
description of the course years.
3 Semester Contains all details
about semesters in
course years
3.1 Semester It stores the no. of Numeric 1
No. each semester

3.2 Course year .It stores the info. To Numeric 1

No. which year no. a
particular sem belongs
S no. Field name Description Type Length

4 Current Contains all details

semester about prevailing
semesters
4.1 Current It stores the year of Numeric 4
year current semesters

5 Subjects Contains all details

about subjects in all the

5.1 Subject semesters

It stores the name of Character 30
Name each subject
5.2 Subject It stores the code of Numeric 3
Code each subject.

5.3 Sem no. It stores the semester Numeric 1

no. to which a particular
each subject belong

6 Faculty Contains all details

Info about faculty

6.1 Faculty It stores the name of Character 30

name each lecturer

6.2 Faculty It stores the code of Numeric 4

code each lecturer
S no. Field name Description Type Length

7 Faculty& Contains all details

about the faculty
subject assosciated with
subjects.
7.1 Current yearIt stores the prevailing Numeric 1
semester semester no.

7.2 faculty code It stores the code of Numeric 4

each lecturer.

7.3 subject code It stores the subject Numeric 3

code assosciated with
that lecturer
8 Student Contains info of
Info students of each course
year.
8.1 Name It stores the name of Character 30
each student
8.2 Enroll. It stores enrollment no. Numeric 4
no. of each student.
8.3 Univ. It stores the university Numeric 7
Roll no. roll no. of each student
8.4 Mother’s name It stores the mother’s Character 30
name of each student
8.5 Father’s name It stores the father’s Character 30
name of each student
8.6 Address It stores the address of Character 30
the student
8.7 Ph no. It stores the phone Numeric 10
number of the student
S no. Field name Description Type Length

9 Student Contains all details

Attendance about attendance of
record students in each
subject
9.1 Current yearIt stores the prevailing Numeric 1
semester semester no.

9.2 Subject code It stores the subject Numeric 3

code to which the
attendance of each
student belongs.
9.3 Enr no. It stores the enr no. of Numeric 4
each student
9.4 Total It stores the total no. of Numeric 2
lectures lectures delivered by
teacher.

9.5 Lectures It stores the no. of Numeric 2

attended lectures attended by
each student
10 Student Contains all details
ass/project about the assignments
record & project submitted by
each student
10.1 Current yearIt stores the prevailing Numeric 2
semester semester no.

10.2 Subject code It stores the subject Numeric 3

code to which the
assgn marks of each
student belong
10.3 Enroll no. It stores the enr no. of Numeric 4
each student

10.4 Max marks It stores the max assgn Numeric 2

marks

10.5 Marks scored It stores marks scored Numeric 2

by each student
S no Field name Description Type Length

11 House Contains all details

exam about the house exams
marks conducted
11.1 It stores the prevailingnumeric 2
Current yearsemester no.
semester

11.2 Subject code It stores the subjectnumeric 3

code to which the
assgn marks of each
student belong

11.3 Enroll no. It stores the enr no. ofnumeric 4

each student

11.4 Total It stores the max.numeric 3

marks marks of the exam

11.5 Marks It stores details of thenumeric 3

scored marks stored by each
12 Internal Contains info total
assessment assessment of each
record student.
12.1 Current yearIt stores the prevailing Numeric 2
semester semester no.

12.2 Subject code It stores the subject Numeric 3

code to which the
assgn marks of each
12.3 Enroll no. student
It storesbelong
the enr no. of Numeric 4
each student

12.4 Attend. It stores marks out of 5 Numeric 1

marks in attendance
12.5 Ass/project It stores the marks out Numeric 2
marks of 10 in assigns
12.6 House exam It stores the marks out Numeric 2
marks of 10 in house exams
12.7 Subject It stores the marks out Numeric 2
marks of 25 of each subject

12.8 Total marks It stores the sum of Numeric 2

marks of each subject
out of 125
 3.4 ENTITY RELATIONSHIP DIAGRAM

ENR
NO.
SEM
UNIV. PH.
YEAR ADD
NO. ROLL NO NO.
YEAR DESC. .
NO.

NAME
HA
COURSE SS SEMESTER FATHE
STUDENT
YEAR SS R
NAME

MOTHER
NAME
HA
S
FACULT
Y FACULT
CODE Y
SUB. SUB
NAME
NAME CODE

HA FACULTY ARE
FACULTY SS FRO SUBJECTS
SUBJECTS M
HA
S
HA
S

HA
S

LECT.
ATTEN
ASSG. TOTAL
CURR D MAR
SUBMTD MARKS
. K
YEAR (125)

HOUSE
CURRENT TOTAL
STUDENT STUDENT
INTERNAL
SEMESTER ATTENDENCE ASS/PROJECT EXAM.
ASSESSMENT
MARKS

TOTA OUT
L MARKS ASS OF 25
PROJECT
LECT. SCORED (10)
SUBMTD
ATTD.
HA (10)
SS
3.5 DATA FLOW DIAGRAM

LEVEL0

COURSE INFO
ADMIN STUDENT RE
FACULTY INF
LEVEL1

STUDENT
DETAILS
CHAPTER - 4

DESIGN
4.1 INTRODUCTION

Design phase of the software development deals with transforming the requirements of
the client into a form implement able using a programming language.
Software design is applied regardless of the software process model that is used.
Beginning once software requirements have been analyzed and specifies, software
design is the first of three technical activities—design, code generation, tests that are
required to build and verify the software.
A good software design is a series of step-by-step procedures to do the desired act.

Design task comprises of:--

Data Design
It transforms the information domain model created during analysis into the data
structures that will be required to implement the software.

Architectural Design
It defines the relationship between major structural elements of the software.

Interface Design
It describes how the software communicates within itself, with systems that
interoperate with it, and with the users who use it.

Component Level Design

It transforms structural elements of software architecture into a procedural
description of software components.
DESIGN MODEL

D
M

COMPONENT

LEVEL

DESIGN

INTERFACE
DESIGN

ARCHITECTURAL
DESIGN

DATA
DESIGN
4.2 DATA DESIGN

USER INFO

S NO. FIELD TYPE LENGTH MANDATORY(M) PRIMARY

OR KEY
OPTIONAL(O)

1. USER CHAR 30 M --
NAME

USER NUMERIC 4 M YES

2.
ID

PASSWORD NUMERIC 6 M --
3.
COURSE YEAR

S NO. FIELD TYPE LENGTH MANDATORY(M) PRIMARY

OR KEY
OPTIONAL(O)

1. YEAR NUMERIC 1 M YES

NO.

2. YEAR CHAR 30 O ---

DESC.

SEMESTER

S NO. FIELD TYPE LENGTH MANDATORY(M) PRIMARY

OR KEY
OPTIONAL(O)

1. SEM NO. NUMERIC 1 M YES

SUBJECTS

S NO. FIELD TYPE LENGTH MANDATORY(M) PRIMARY

OR KEY
OPTIONAL(O)

1. SUBJECT CHAR 30 O ----

NAME

2. SUBJECT NUMERIC 1 M YES

CODE

CURRENT SEMESTER

S NO. FIELD TYPE LENGTH MANDATORY(M) PRIMARY

OR KEY
OPTIONAL (O)

1. CURRENT NUMERIC 4 M YES

YEAR

FACULTY
S NO. FIELD TYPE LENGTH MANDATORY(M) PRIMARY
OR KEY
OPTIONAL(O)

1. FACULTY CHAR 30 O ---

NAME

FACULTY NUMERIC 4 M YES

2.
CODE

FACULTY & SUBJECTS

S NO. FIELD TYPE LENGTH MANDATORY(M) PRIMARY

OR KEY
OPTIONAL(O)

1. CURRENT CHAR 30 M YES

YEAR
SEMESTER

FACULTY NUMERIC 4 M YES

2.
CODE

SUBJECT NUMERIC 3 M YES

3. CODE
STUDENT

S NO. FIELD TYPE LENGTH MANDATORY(M) PRIMARY

OR KEY
OPTIONAL(O)

1. NAME CHAR 30 M ---

2. FATHER CHAR 30 O ---

NAME

3. MOTHER CHAR 30 O ---

NAME

4. ENR NO. NUMERIC 5 M YES

5. UNIV NO. NUMERIC 6 M ---

6. ADDRESS ALPHANUMERIC 30 O ---

7. PHONE NUMERIC 8 O ---

NO.
STUDENT’S ATTENDENCE

S NO. FIELD TYPE LENGTH MANDATORY(M) PRIMARY

OR KET
OPTIONAL(O)

1. CURRENT NUMERIC 2 M YES

YEAR
SEMESTER

2. SUBJECT NUMERIC 3 M YES

CODE

3. ENR NO. NUMERIC 4 M YES

4 TOTAL NUMERIC 2 M --
LECTURES

5 LECTURES NUMERIC 2 M --
ATTENDED
STUDENT’S ASSIGNMENTS / PROJECT MARKS

S NO. FIELD TYPE LENGTH MANDATORY(M) PRIMARY

OR KEY
OPTIONAL(O)

CURRENT NUMERIC 2 M YES

1. YEAR
SEMESTER

NUMERIC 3 M YES
2. SUBJECT
CODE
NUMERIC 4 M YES
3. ENR NO.
NUMERIC 2 M --
4 MAX MARKS

NUMERIC 2 M --
5 MARKS
SCORED
STUDENT’S HOUSE EXAMINATION MARKS

S NO. FIELD TYPE LENGTH MANDATORY(M) PRIMARY

OR KEY
OPTIONAL(O)

M
1. CURRENT NUMERIC 2 YES
YEAR
SEMESTER
M
2. NUMERIC 3 YES
SUBJECT
CODE M
3. NUMERIC 4 YES
ENR NO. M
4 NUMERIC 2 --
TOTAL
MRKS M
5 NUMERIC 2 --
MARKS
SCORED
 STUDENT INTERNAL ASSESSMENT RECORD

S NO. FIELD TYPE LENGTH MANDATORY(M) PRIMARY

OR KEY
OPTIONAL(O)

1. CURRENT YEAR NUMERIC 2 M YES

SEMESTER

2. SUBJECT CODE NUMERIC 3 M YES

3. ENR NO. NUMERIC 4 M YES

4 ASSIGNMENT MARKS NUMERIC 2 M --

(OUT OF 10)

5 HOUSE EXAM MARKS NUMERIC 2 M --

(OUT OF 10)

6 ATTENDENCE MARKS NUMERIC 1 M --

(OUT OF 5)

7 MARKS OUT OF 25 NUMERIC 2 M --

8 MARKS OUT OF 125 NUMERIC 3 M --

4.3 ARCHITECTURAL DESIGN

FACULTY &
SUBJECTS
4.4 INTERFACE DESIGN
4.5 SCREENS DESCRIPTION

LOGIN SCREEN
The access of the system is given to the faculty & the administrator.

When the faculty logs in, the following screens appear

SEMESTER ALLOTED
This screen lists the current semester allotted to the teacher who has logged in.
The teacher selects a particular semester

SUBJECTS ALLOTED
This screen gives details of the subjects allotted to that teacher in that particular
semester.
When the teacher selects a particular subject, the foll. menu screen is displayed

SUBJECTS INFORMATION
This is a subject menu screen. It has the following options.
ATTENDANCE RECORD
ASSIGNMENT / PROJECT RECORD
HOUSE EXAM RECORD
The teacher selects one of these options.
ATTENDANCE RECORD
It lists the total lectures delivered by the teacher & lectures attended by each
student in that particular subject.

ASSIGNMENT/PROJECT RECORD
This screen gives the details of the assignment & project work submitted by each
student in that subject.

HOUSE EXAMINATION RECORD

It shows the marks scored by each student in that subject.

When an administrator logs in the following screen appears

ADMINISTARTIVE USE
This is a menu screen having the following options
FULL COURSE INFORMATION
CURRENT SEMESTER

Selecting the full course information option gives

FULL COURSE INFORMATION

This menu screen has following options
SUBJECTS
FACULTY
SUBJECT INFORMATION
This screen shows the details of the subjects ie subject name ,subject code of
every semester.

FACULTY INFORMATION
This screen gives the details of the faculty displaying their name and code.

At the selection of current semester option ,following screen is displayed.

CURRENT SEMESTER
This is a menu screen listing the prevailing semesters
When the administrator selects one of these semester, the following menu
screen appears

SEMESTER INFORMATION
It has following options
FACULTY & SUBJECTS
DATABASE OF STUDENTS
INTERNAL ASSESSMENT

FACULTY & SUBJECT INFORMATION

This screen gives the details of the subjects assigned to the faculty of that
semester

DATABASE OF STUDENTS
This screen shows the database of all the students of that semester.
INTERNAL ASSESSMENT CALCULATION
This screen lists the option for the calculation of internal assessment
ATTENDANCE MARKS
ASSIGNMENT/PROJECT MARKS
HOUSE EXAMINATION MARKS
TOTAL INTERNAL ASSESSMENT

ATTENDANCE MARKS
Here the attendance marks out of 5 of each student for each subject in that
semester are calculated & shown.

ASSIGNMENT/PROJECT MARKS
It shows the assignment marks calculated of each student out of 10 for each
subject in that semester.

HOUSE EXAMINATION MARKS

Here the House Examination marks calculated out of 10 for every subject of each
student in that semester are displayed.

TOTAL INTERNAL ASSESSMENT

Lastly, the marks out of 25 for each subject and finally out of 125 for all the
subjects of each student calculated and shown