CERTIFICATE

This is to certify that the project entitled INTERNAL ASSESSMENT EVALUATION SYSTEM prepared by us, PRANEET TAHILRAMANI, KAMANDEEP SINGH, AJAY BATRA, AKSHAY DESHWAL, & GEETIKA MALHOTRA for the partial fulfillment of the requirements of the BBA(CAM) degree, embodies the work, we all are doing during 2nd semester of our course under due supervision of the supervisor from this college.

SIGNATURE
PRANEET TAHILRAMANI KAMANDEEP SINGH AJAY BATRA AKSHAY DESHWAL GEETIKA MALHOTRA

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 Mr HEMANT KUMAR, who gave us inspiration to do work in this field and gave us his 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.

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

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

3.
3.1
3.2 3.3 3.4 3.5

REQUIREMENT ANALYSIS & MANAGEMENT

INTRODUCTION FUNCTIONAL REQUIREMENTS DATA DICTIONARY ENTITY RELATIONSHIP DIAGRAM DATA FLOW DIAGRAM

4.
4.1
4.2 4.3 4.4

DESIGN
INTRODUCTION DATA DESIGN ARCHITECTURAL DESIGN INTERFACE DESIGN SCREENS DESCRIPTION

4.5

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. 2. Maintaining records as paperwork is a cumbersome task. 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 BBA(CAM), IP 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 dont 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. students name birth date fathers name mothers 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 process and events operational implementation. Effective software project management focuses on the 4 Ps :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 [KPAs] 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 customers 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 people , that occur as software evolves from a preliminary concept to an

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.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 Communication between the leader and team members is vertical. We use democratic decentralized [DD] team structure in our project. Our team comprises of five members: PRANEET TAHILRAMANI KAMANDEEP SINGH AJAY BATRA AKSHAY DESHWAL GEETIKA MALHOTRA leader.

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, its 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 occurring 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
REQUIREMENT GATHERING AND ANALYSIS

DATE OF START

DATE OF END

1.1 1.2 1.3 1.4 1.5 1.6 1.7 1.8

Course Faculty Students

26.12.2007 30.12.2007 2.1.2008 7.1.2008 6.1.2008 9.1.2008 20.1.2008 27.1.2008 1.2.2008 9.2.2008 17.2.2008

Internal assessment 11.1.2008 FPA Data dictionary ERD DFD 23.1.2008 28.1.2008 3.2.2008 10.2.2008

2
2.1 2.2

DESIGN Data design Architectural design 19.2.2008 24.2.2008 22.2.2008 29.2.2008

2.3 2.4

Interface design Pseudocode

1.3.2008 11.3.2008

10.3.2008 15.3.2008

2.3

COMPLEXITY TABLES

FILES COMPLEXITY FILES USER INFO. COURSE INFO FACULTY INFO DATABASE OF STUDENTS NO. OF FIELDS 3 (username, user id, password) 4 (course year, sem, subcode ,sub name) 4 (subcode, faculty name, sem, year) RECORDS COMPLEXITY

1 1 1

LOW LOW LOW LOW LOW LOW LOW LOW

ATTENDENCE ASSIGNMENT/ PROJECT RECORD EXAM 7 (sem, subcode, enrl. no., student name, 1 HOUSE RECORD total marks scored, mrks out of 10, year) INTERNAL ASSESSMENT RECORD 24 (sem, subcode, enrl.no.,uni rno,student 1 name,att. mrks (out 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) )

10 (sem,year,enr no, univ rno., student 1 name, birthdate, father name, mother's name, add., ph no.) 6 (sem, subcode, enrl. no.,attendance, 1 6 (sem, subcode, enrl. no., assign/ project 1 submitted, marks out of 10, year)

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) 1 (House exam record) NO. OF FIELDS 4 (subcode, subname, sem,course year) 14 ( subcode , faculty for each sub, sem, year) 5 ( sem ,sub code, enr no. , attend., year) 6 (sem, sub code , enr no,assig mrks, project marks, year) 6 ( sem , sub code , enr no., student name, marks out of 50, year) COMPLEXITY LOW LOW LOW LOW LOW

OUTPUT SCREEN COMPLEXITY

SCREENS SUBJECT INFO DATABASE OF STUDENTS FACULTY INFO FILES 1 [Course info] 1 [Database of students] 1 [Faculty info] NO. OF FIELDS 3 ( sem, subcode, sub name ) COMPLEXITY LOW

10 ( sem, year,enr no, univ rno., student LOW name, birthdate, father's name, mother's name, add., ph no.) 4 (sub code, faculty name, sem no., year) LOW

QUERY SCREEN COMPLEXITY

SCREENS LOGIN SCREEN ATTENDANCE RECORD ASSIGNMENT/ PROJECT RECORD HOUSE EXAM RECORD INTERNAL ASSESSMENT RECORD FILES 1 (User info) 1 (Attendance record) 1 (Assign/ project rec) 1 (House exam record) 1 (Internal assessment record) NO. OF FIELDS 2 (username,password] 6 (sem, subcode, enr no., ttendance, marks out of 5,year) COMPLEXITY LOW LOW

5 (sem, subcode, enr no., marks out LOW of 10, year) 7 (sem, subcode, enr no., student LOW name, marks out of 50, mrks out of 10, year) 24 (sem, subcode, enr no.,uni rno, AVG student name,att. mrks (out 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

CATEGORY NO. OF INPUTS NO. OF OUTPUTS NO. OF FILES NO. OF QUERIES SIMPLE 5 X 3 = 15 3 X 4 = 12 8 X 7 = 56 5 X 3 = 15 AVERAGE COMPLEX 0X4= 0 0X5= 0 0 X 10 = 0 1X4= 1 0 X 6 = 0] 0X7= 0 0 X 15 = 0 0X6= 0 99 TOTAL 15 12 56 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

CHAPTER - 3

REQUIREMENT ANALYSIS & MANAGEMENT

3.1

INTRODUCTION

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

between system

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. 3.

It should provide facility for updating the next semester on the completion of last one. 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 It should be able to calculate assg marks out of 10 Facility should be provided to calculate house examination marks out of 10.

7. 8.

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
TYPE LENGTH

S NO. FIELD NAME DESCRIPTION 1 1.1 User Info User name

Contains all details about various users It stores the user name of the faculty and administrators

Character

30

1.2

Password

It stores the password Alphanumeric of the corresponding user id It stores the id of each user

1.3 2. 2.1 2.2

User id

Numeric

Course year Contains all details

about course years

Year No. Year description

It stores the course year nos. It stores description of the course years.

Numeric Character

1 30

Semester

Contains all details about semesters in course years It stores the no. of each semester .It stores the info. To which year no. a particular sem belongs

3.1

Semester No.

Numeric

3.2

Course year No.

Numeric

5 no. Field name Subjects S 4 5.1 4.1 5.2 Current Subject semester Name Current Subject year Code Sem no.

Contains all Description

detailsType

Length 30 4 3

about subjects in all the semesters the name of Contains all details It stores about prevailing each subject semesters It stores the code of It stores the year of current semesters each subject. It stores the semester no. to which a particular each subject belong

Character Numeric Numeric

5.3

Numeric

6 6.1 6.2

Faculty Info Faculty name Faculty code

Contains all about faculty

details

It stores the name of each lecturer It stores the code of each lecturer

Character Numeric

30 4

S no. Field name 7 Faculty& subject 7.1

Current semester faculty code

Description

Type

Length

Contains all details about the faculty assosciated with subjects. yearIt stores the prevailing semester no. It stores the code of each lecturer. It stores the subject code assosciated with that lecturer

Numeric

7.2 7.3

Numeric Numeric

4 3

subject code

S no. Field name 9 8 9.1 8.1 9.2 8.2 10 8.3 9.3 8.4 9.4 10.1 8.5 8.6 10.2 9.5 8.7 10.3 10.4 10.5

Description

Type

Length

Contains all details Student Attendance about attendance of students in each record subject Contains info of Student It stores the prevailing Current yearstudents of each course Info semester no. year. semester It stores the name of Name It stores the subject Subject code each student It stores enrollment no. Enroll. code to which the of each student. no. attendance of each Containsbelongs. details all Student student It stores the university Univ. about thethe enr no. of assignments roll no. of each student It stores ass/project Enr no. Roll no. each student record name & project submitted by It stores the mothers Mothers each student student name of each It stores the total no. of Total Current name It stores the prevailing the fathers Fathers year It stores delivered by lectures lectures semestereach student semester name of no. teacher. It stores the address of Address Subject code It stores the subject the stores the no. of It student Lectures code to attended the lectures by It stores whichphone the Ph no. attended

Numeric

1 30 3 4 7 4 30 2 2 30 30 3 2 10 4 2 2

Character Numeric Numeric

Numeric

Numeric

Character Numeric Numeric Character Character Numeric Numeric Numeric Numeric Numeric Numeric

Enroll no. Max marks

assgnstudent student each of the numbermarks of each student belong It stores the enr no. of each student It stores the max assgn marks by each student

Marks scored It stores marks scored

S no 11 11.1

Field name Description House exam marks

Current semester

Type

Length

Contains all details about the house exams conducted It stores the prevailingnumeric yearsemester no. It stores the subjectnumeric code to which total the Contains info assgn marks of each of each assessment student belong student. 2

11.2 12 12.1 11.3 12.2 11.4 12.3 11.5 12.4 12.5 12.6 12.7 12.8

Subject code

Internal assessment record It stores the prevailing Numeric Current Enroll no. yearIt stores the enr no. ofnumeric semester no. semester each student
It stores the max. Numeric Subject code It stores the subjectnumeric Total code to marks of thewhich the exam marks

42
33 34 1 2 2 2 2

Enroll no. Marks scored Attend. marks Ass/project marks House exam marks Subject marks Total marks

assgn marks of each student the enr no. of Numeric It storesbelong of thenumeric details each student marks stored by each 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

Numeric Numeric Numeric Numeric

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

3.4

ENTITY RELATIONSHIP DIAGRAM

SEM YEAR NO. YEAR DESC. NO. UNIV. ROLL NO

ENR NO. ADD . PH. NO.

NAME

COURSE YEAR

HA SS SS

SEMESTER

FATHE R NAME

STUDENT

HA S
FACULT Y CODE FACULT Y NAME

MOTHER NAME

SUB. NAME

SUB CODE

FACULTY

HA SS HA S

FACULTY SUBJECTS

ARE FRO M

SUBJECTS

HA S HA S

CURR . YEAR

LECT. ATTEN D

ASSG. SUBMTD

TOTAL MARKS

MAR K (125)

CURRENT SEMESTER

HOUSE STUDENT ATTENDENCE STUDENT ASS/PROJECT EXAM. MARKS

MARKS SCORED ASS (10)

TOTAL INTERNAL ASSESSMENT

OUT OF 25 ATTD. (10)

TOTA L LECT.

PROJECT SUBMTD

HA SS

3.5

DATA

FLOW DIAGRAM

LEVEL0

ADMIN

COURSE INFO STUDENT REC FACULTY INFO

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 activitiesdesign, 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) OR OPTIONAL(O)

30 M M M

PRIMARY KEY

1. 2. 3.

USER NAME USER ID

CHAR

-YES --

NUMERIC 4

PASSWORD NUMERIC 6

COURSE YEAR

S NO.

FIELD

TYPE

LENGTH MANDATORY(M) OR OPTIONAL(O)

1 30 M O

PRIMARY KEY
YES ---

1. 2.

YEAR NO. YEAR DESC.

NUMERIC CHAR

SEMESTER S NO. FIELD TYPE LENGTH MANDATORY(M) OR OPTIONAL(O)

M

PRIMARY KEY
YES

1.

SEM NO.

NUMERIC

SUBJECTS S NO. FIELD TYPE LENGTH MANDATORY(M) OR OPTIONAL(O)

O M

PRIMARY KEY

1. 2.

SUBJECT NAME SUBJECT CODE

CHAR NUMERIC

30 1

---YES

CURRENT SEMESTER S NO. FIELD TYPE LENGTH MANDATORY(M) OR OPTIONAL (O)

M

PRIMARY KEY
YES

1.

CURRENT YEAR

NUMERIC

FACULTY

S NO.

FIELD

TYPE

LENGTH

MANDATORY(M) OR OPTIONAL(O)
O M

PRIMARY KEY

1. 2.

FACULTY NAME FACULTY CODE

CHAR NUMERIC

30 4

--YES

FACULTY & SUBJECTS S NO. FIELD TYPE LENGTH MANDATORY(M) OR OPTIONAL(O)

M

PRIMARY KEY

1.

CURRENT YEAR SEMESTER FACULTY CODE

CHAR

30

YES

2.

NUMERIC 4

YES

3.

SUBJECT CODE

NUMERIC 3

YES

STUDENT

S NO.

FIELD

TYPE

LENGTH

MANDATORY(M) OR OPTIONAL(O)
M O O M M O O

PRIMARY KEY
------YES -------

1. 2. 3. 4. 5. 6. 7.

NAME FATHER NAME MOTHER NAME ENR NO. UNIV NO. ADDRESS PHONE NO.

CHAR CHAR CHAR NUMERIC NUMERIC ALPHANUMERIC NUMERIC

30 30 30 5 6 30 8

STUDENTS ATTENDENCE S NO. FIELD TYPE LENGTH MANDATORY(M) OR OPTIONAL(O)

M

PRIMARY KET
YES

1.

CURRENT YEAR SEMESTER SUBJECT CODE ENR NO. TOTAL LECTURES LECTURES ATTENDED

NUMERIC

2. 3. 4 5

NUMERIC NUMERIC NUMERIC NUMERIC

3 4 2 2

M M M M

YES YES ---

STUDENTS ASSIGNMENTS / PROJECT MARKS

STUDENTS HOUSE EXAMINATION MARKS S NO. FIELD TYPE LENGTH MANDATORY(M) OR OPTIONAL(O)
M 1. CURRENT YEAR SEMESTER SUBJECT CODE 3. ENR NO. 4 TOTAL MRKS 5 MARKS SCORED NUMERIC 2 NUMERIC 2 M -NUMERIC 4 M -NUMERIC 2 M 2. NUMERIC 3 M YES YES YES

PRIMARY KEY

STUDENT INTERNAL ASSESSMENT RECORD S NO. FIELD TYPE LENGTH MANDATORY(M) OR OPTIONAL(O)
M

PRIMARY KEY

1.

CURRENT YEAR SEMESTER SUBJECT CODE ENR NO. ASSIGNMENT MARKS (OUT OF 10) HOUSE EXAM MARKS (OUT OF 10) ATTENDENCE MARKS (OUT OF 5) MARKS OUT OF 25 MARKS OUT OF 125

NUMERIC

YES

2. 3. 4 5 6 7 8

NUMERIC NUMERIC NUMERIC NUMERIC NUMERIC NUMERIC NUMERIC

3 4 2 2 1 2 3

M M M M M M M

YES YES ------

4.3

ARCHITECTURAL DESIGN

FACULTY & SUBJECTS

FACULTY

SUBJECT

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 100 for all the subjects of each student calculated and shown