Internal Assessment Project

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 ENGINEERING

CODE

TEST

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

1

REQUIREMENT

DATE OF

DATE OF

START

END

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

1.5

assessment 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 USER INFO.

NO. OF FIELDS 3 (username,user id,password)

COURSE

4

(course year, sem,

INFO

subcode,sub name)

FACULTY

4

INFO

name, sem, year) 10 (sem,year,enr no,

DATABASE

univ rno., student name,

OF

birthdate,

STUDENTS

mother's name, add.,

(subcode,

RECORDS

COMPLEXITY

1

LOW

1

faculty 1

father name,

1

LOW LOW

LOW

ph no.) ATTENDENCE

6

(sem, subcode, enr

RECORD

no.,attendance,

marks 1

LOW

out of 5, year) ASSIGNMENT/ 6

(sem, subcode, enr

PROJECT

no.,

RECORD

submitted, marks out of

HOUSE EXAM RECORD

assign/

project

1

LOW

10, year) 7 (sem, subcode, enr no., student name, total 1 marks scored, mrks out of 10, year)

LOW

24(sem,subcode,enr INTERNAL ASSESSMENT RECORD

no.,uni rno,student name,att. mrks (out

1

of 5), assign mrks

LOW

(out of 10), house exam marks (out of 10), mrks of each

Input screen complexity

SCREENS COURSE INFO FACULTY INFO

ATTENDANCE RECORD

ASSIGNMENT/ PROJECT RECORD

HOUSE EXAMS RECORD

FILES

1 (Course info)

1 (Faculty info)

1 (Attendance record)

1 (Assign/ project rec)

NO. OF FIELDS 4 (subcode, subname, sem,course year) 14 ( subcode , faculty for each sub, sem, year)

COMPLEXITY

LOW

LOW

5 ( sem ,sub code, enr no. , attend.,

LOW

year) 6 ( sem , sub code , enr no,assig mrks ,

LOW

project mks,year) 6 ( sem , sub code ,

1 (House exam record)

enr no., student name, marks out of 50, year)

LOW

Output screen complexity

SCREENS SUBJECT INFO

FILES

1 [Course info]

NO. OF FIELDS 3 ( sem, subcode, sub name )

COMPLEXITY

LOW

10 ( sem, year,enr no, univ DATABASE OF STUDENTS

1 [Database of students]

rno., student name, birthdate, father's

LOW

name, mother's name, add., ph no.)

FACULTY INFO

1 [Faculty info]

4

( sub code, faculty

name, sem no., year)

LOW

Query screen complexity

SCREENS

FILES

NO. OF FIELDS

LOGIN SCREEN

1 (User info)

2 (username,password]

ATTENDANCE

1 (Attendance

RECORD

ASSIGNMENT/ PROJECT

record)

1 (Assign/ project rec)

COMPLEXITY LOW

6 (sem, subcode, enr no., attendance,

LOW

marks out of 5,year) 5 (sem, subcode, enr no., marks out of 10, year)

LOW

RECORD 7 (sem, subcode, enr no., HOUSE EXAM RECORD

1 (House exam record)

student name, marks out of 50, mrks out of 10,

LOW

year) 24(sem,subcode,enr no.,uni rno,student name,att. mrks (out INTERNAL ASSESSMENT RECORD

1 (Internal assessment record)

of 5), assign mrks (out of 10), house exam marks (out of 10), mrks of each sub(out of 25), total mrks (out of 125) )

2.4 FUNCTION POINT ANALYSIS

AVG

CATE GORY

SIMPLE

AVERAGE

COMPLEX

TOTA

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) =

FP

= UFP x [0.65 + 0.01 x Σfi] = 99 x [0.65 + 0.01 x 42]

FPs = 105.93

L

99

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

1.

FUNCTIONAL REQUIREMENTS

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 of the faculty and administrators

1.2

Password

It stores the password Alphanumeric of the corresponding user id

6

1.3

User id

It stores the id of each user

Numeric

4

2.

Course year Contains all details Numeric

1

Character

30

30

about course years

2.1

Year No.

It stores the course year nos.

2.2

Year

It stores description

description

of the course years.

3

Semester

Contains all details about

3.1

Semester No.

3.2

Course year No.

semesters

in

course years It stores the no. of

Numeric

1

Numeric

1

each semester .It stores the info. To which

year

no.

particular sem belongs

a

S no. Field name

Description

4

Current semester

4.1

Current year

Contains all details about prevailing semesters It stores the year of current semesters

5

Subjects

Contains

all

Type

Length

Numeric

4

Character

30

Numeric

3

Numeric

1

details

about subjects in all the

5.1 5.2

5.3

Subject

semesters It stores the name of

Name

each subject

Subject

It stores the code of

Code

each subject.

Sem no.

It stores the semester no. to which a particular each subject belong

6

Faculty Info

Contains all about faculty

details

6.1

Faculty name

It stores the name of each lecturer

Character

30

6.2

Faculty code

It stores the code of each lecturer

Numeric

4

S no. Field name 7

Faculty& subject

Description

Contains all details about the faculty assosciated with subjects. yearIt stores the prevailing semester no.

7.1

Current semester

7.2

faculty code

7.3

subject code

Type

Length

Numeric

1

It stores the code of each lecturer.

Numeric

4

It stores the subject code assosciated with that lecturer

Numeric

3

8 8.1 8.2 8.3 8.4 8.5 8.6 8.7

Student Info

Contains info of students of each course year. It stores the name of Name each student It stores enrollment no. Enroll. of each student. no. It stores the university Univ. roll no. of each student Roll no. Mother’s name It stores the mother’s name of each student Father’s name It stores the father’s name of each student It stores the address of Address the student It stores the phone Ph no. number of the student

Character

30

Numeric

4

Numeric

7

Character

30

Character

30

Character

30

Numeric

10

S no. Field name 9

9.1

Description

Type

Contains all details about attendance of students in each subject Current yearIt stores the prevailing semester no. semester

Length

Student Attendance record

Numeric

1

It stores the subject code to which the attendance of each student belongs. It stores the enr no. of each student

Numeric

3

Numeric

4

9.2

Subject code

9.3

Enr no.

9.4

Total lectures

It stores the total no. of lectures delivered by teacher.

Numeric

2

9.5

Lectures attended

It stores the no. of lectures attended by each student

Numeric

2

10

10.1

Student ass/project record

Contains all details about the assignments & project submitted by each student Current yearIt stores the prevailing semester no. semester

Numeric

2

10.2

Subject code It stores the subject

Numeric

3

10.3

Enroll no.

Numeric

4

10.4

Max marks

It stores the max assgn marks

Numeric

2

10.5

Marks scored It stores marks scored

Numeric

2

code to which the assgn marks of each student belong It stores the enr no. of each student

by each student

S no 11

Field name Description

Current semester

Length

Contains all details about the house exams conducted

House exam marks

11.1

Type

It stores the prevailingnumeric yearsemester no.

2

11.2

Subject code

It stores the subjectnumeric code to which the assgn marks of each student belong

3

11.3

Enroll no.

It stores the enr no. ofnumeric each student

4

11.4

Total marks

It stores the max.numeric marks of the exam

3

11.5

Marks scored

It stores details of thenumeric marks stored by each

3

12 12.1

Contains info total Internal assessment assessment of each student. record Current yearIt stores the prevailing Numeric semester no. semester

2

12.2

Subject code It stores the subject Numeric

3

12.3

Enroll no.

4

12.4

Attend. marks Ass/project marks House exam marks Subject marks

It stores marks out of 5 in attendance It stores the marks out of 10 in assigns It stores the marks out of 10 in house exams It stores the marks out of 25 of each subject

Total marks

12.5 12.6 12.7 12.8

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

Numeric

1

Numeric

2

Numeric

2

Numeric

2

It stores the sum of Numeric marks of each subject out of 125

2

3.4

ENTITY RELATIONSHIP DIAGRAM

ENR NO.

SEM YEAR DESC.

YEAR NO.

UNIV. ROLL NO

NO.

PH. NO.

ADD .

NAME

HA SS SS

COURSE YEAR

SEMESTER

MOTHER NAME

HA S FACULT Y CODE

FACULT Y NAME

SUB. NAME

HA SS

FACULTY

STUDENT

FATHE R NAME

FACULTY SUBJECTS

ARE FRO M

HA S

SUB CODE

SUBJECTS

HA S HA S

CURR . YEAR

LECT. ATTEN D

ASSG. SUBMTD

TOTAL MARKS

MAR K (125)

HOUSE

CURRENT SEMESTER

STUDENT ATTENDENCE

TOTA L LECT.

HA SS

STUDENT ASS/PROJECT

PROJECT SUBMTD

TOTAL INTERNAL ASSESSMENT

EXAM. MARKS MARKS SCORED

OUT OF 25

ASS (10) ATTD. (10)

3.5

DATA

FLOW DIAGRAM

LEVEL0

ADMIN

COURSE INFO 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

1.

USER NAME

CHAR

30

M

--

2.

USER ID

NUMERIC

4

M

YES

PASSWORD

NUMERIC

6

M

--

3.

TYPE

LENGTH

MANDATORY(M) OR OPTIONAL(O)

PRIMARY KEY

COURSE YEAR

S NO.

FIELD

TYPE

LENGTH MANDATORY(M) OR OPTIONAL(O)

PRIMARY KEY

1.

YEAR NO.

NUMERIC

1

M

YES

2.

YEAR DESC.

CHAR

30

O

---

SEMESTER

S NO.

1.

FIELD

SEM NO.

TYPE

NUMERIC

LENGTH

1

MANDATORY(M) OR OPTIONAL(O)

PRIMARY KEY

M

YES

SUBJECTS

S NO.

FIELD

TYPE

LENGTH

MANDATORY(M) OR OPTIONAL(O)

PRIMARY KEY

1.

SUBJECT NAME

CHAR

30

O

----

2.

SUBJECT CODE

NUMERIC

1

M

YES

CURRENT SEMESTER

S NO.

1.

FIELD

CURRENT YEAR

FACULTY

TYPE

NUMERIC

LENGTH

4

MANDATORY(M) OR OPTIONAL (O) M

PRIMARY KEY YES

S NO.

FIELD

TYPE

LENGTH

MANDATORY(M) OR OPTIONAL(O)

PRIMARY KEY

1.

FACULTY NAME

CHAR

30

O

---

2.

FACULTY CODE

NUMERIC

4

M

YES

FACULTY & SUBJECTS

S NO.

FIELD

TYPE

LENGTH

MANDATORY(M) OR OPTIONAL(O)

PRIMARY KEY

CHAR

30

M

YES

FACULTY CODE

NUMERIC

4

M

YES

SUBJECT CODE

NUMERIC

3

M

YES

1.

CURRENT YEAR SEMESTER

2.

3.

STUDENT

S NO.

FIELD

TYPE

LENGTH

MANDATORY(M) OR OPTIONAL(O)

PRIMARY KEY

1.

NAME

CHAR

30

M

---

2.

FATHER NAME

CHAR

30

O

---

3.

MOTHER NAME

CHAR

30

O

---

4.

ENR NO.

NUMERIC

5

M

YES

5.

UNIV NO.

NUMERIC

6

M

---

6.

ADDRESS

ALPHANUMERIC

30

O

---

7.

PHONE NO.

NUMERIC

8

O

---

STUDENT’S ATTENDENCE

S NO.

FIELD

TYPE

LENGTH

MANDATORY(M) OR OPTIONAL(O)

PRIMARY KET

1.

CURRENT YEAR SEMESTER

NUMERIC

2

M

YES

2.

SUBJECT CODE

NUMERIC

3

M

YES

3.

ENR NO.

NUMERIC

4

M

YES

4

TOTAL LECTURES

NUMERIC

2

M

--

5

LECTURES ATTENDED

NUMERIC

2

M

--

STUDENT’S ASSIGNMENTS / PROJECT MARKS

S NO.

1.

2.

FIELD

TYPE

LENGTH

MANDATORY(M) OR OPTIONAL(O)

PRIMARY KEY

CURRENT YEAR SEMESTER

NUMERIC

2

M

YES

NUMERIC

3

M

YES

NUMERIC

4

M

YES

NUMERIC

2

M

--

NUMERIC

2

M

--

SUBJECT CODE

3.

ENR NO.

4

MAX MARKS

5

MARKS SCORED

STUDENT’S HOUSE EXAMINATION MARKS

S NO.

FIELD

TYPE

LENGTH

MANDATORY(M) OR OPTIONAL(O)

PRIMARY KEY

M 1.

CURRENT YEAR SEMESTER

NUMERIC

2

NUMERIC

3

NUMERIC

4

NUMERIC

2

NUMERIC

2

YES M

2. SUBJECT CODE 3.

M

ENR NO. 4

MARKS SCORED

YES M

TOTAL MRKS 5

YES

-M --

STUDENT INTERNAL ASSESSMENT RECORD

S NO.

FIELD

TYPE

LENGTH

MANDATORY(M) OR OPTIONAL(O)

PRIMARY KEY

1.

CURRENT YEAR SEMESTER

NUMERIC

2

M

YES

2.

SUBJECT CODE

NUMERIC

3

M

YES

3.

ENR NO.

NUMERIC

4

M

YES

4

ASSIGNMENT MARKS (OUT OF 10)

NUMERIC

2

M

--

5

HOUSE EXAM MARKS (OUT OF 10)

NUMERIC

2

M

--

6

ATTENDENCE MARKS (OUT OF 5)

NUMERIC

1

M

--

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