MCAproject Marking Scheme

8/10/2019 MCAproject Marking Scheme

1/5

Annexure - I

Assessment pattern for MCA Project (CS-17) / MCSP - 060

Project Report 150

Software Process Marks

Analysis 40

Project planning: Cost & efforts estimation is to be done with thehelp of functional point analysis.

5

Project scheduling:

(i) Pert chart: Proper decomposition of stages -----3 marks(ii) Gantt chart: time line structure and validity of chart---- 2 marks

5

Software requirement specification documents (SRS)

If a student use IEEE standards or any other international standardgive him/her 10 marks

If a student makes SRS with proper structure based on software

engineering Concepts give him/her 5 marks If a student makes SRS in running text, no structuring, give 2

marks

10

Entity Relationship diagram (ER Diagram)

Indicators:

Proper symbol of attributes, entities and relationship 2 marks

Relationship of ER diagram to SRS with strong association 3

marks OR

Class diagrams for projects which does not use any DBMS but

developed in an Object Oriented Programming Language

Indicators:

Class diagrams indicating hierarchies

5


2/5

OR

For projects which neither use any DBMS nor any object oriented

programming language but used a procedural languageIndicators:

System should be modular

Each module should control the functions of appropriate number of

subordinate modules at the next level

Modules should be independent

Each module should perform one function

Each module should be of reasonable size

OR

Modeling diagrams consist of data models

Data Flow Diagram (DFD)

Requirements

All Data flow should be leveled and should have proper input and

output.

Relationship of data flow to data dictionaryContext Diagram --- 2 marks

Level 1 ---- 4 marksLevel 2 -------- - 4 marks

OR

Any other Behavior Model and /or State Transition Diagram

10

Data DictionaryRequirements: It should explain each entity and relationship in ER

diagram and data flow in DFD.

Data element definitions----2

Database schema with reference keys----3

OR

Projects which does not use any DBMS but developed in an Object

Oriented Programming Language

Data objects definition and description---2

Relation ship between data objects--------3OR

Details on various Data Structures Used

5

Design 30

Program structure:

Requirements:

It should have the proper modularizations of software and specification ofeach module.

5


3/5

Schema Design and Normalized tables:

Requirements:Normalize the table to minimum 3NF. If any demand of Demoralizations

explain clearly the reasons.

OR

Program architecture and Explanation on suitability of Data

Structure used

5

Data Integrity & Constraints:

Requirements:

Explain the referential diagram. Define entity integritywitch should include keys, alternate keys and other keys

OR

Value constraints and ranges

5

Procedural Design:Requirements:

Explain using Flowchart / Pseudo code / PDL

5

User Interface design:

Requirements:Coherence with dataflow and processor; Consistency of interface and

naming convention.

10

Coding 30

Comments and descriptionRequirements:

Should have comments with functional description

input, output, totalfunction calls to/from other functions, function parameters, description of

main variables, Data type, logic description, etc

10

Standardization of coding

Naming convention of variable and functions---2 marks

Nested depth---3 marks

Naming constant---2 marks

Use of data structure and style---3 marks

10

Error Handling

Requirements:

Explain the exceptions handling---3

Explain the conditional checking----2

5

Parameter passing and calling

Requirements:Check the technique used for this purpose, how it optimize the coding

5


4/5

Security 10

Database or Data security

Requirements: (for database security)

Use of Views

Use of Revoke and grant

Requirements: (for data security)

Proper encapsulation leading to secure data

5

User and Access rights 3

Steps taken against hacking of system 2

Testing 30

Test case Design

Unit Testing ---5 marks

Integration testing ---5 marks System testing ---5 marks

15

Test reports

Unit Testing ---4 marks

Integration testing ---3 marks

System testing ---3 marks

10

Debugging and code improvement 5

Organization of report 10

Proper Binding of project report 2

Content page and page numbering 2

Organization of content, proper printout of text and images 6


5/5

VIVA 50

Presentation 40

Analysis:

Project Objectives--2

ER Diagrams/ Data Model/ class diagram / Reasons for using the

particular software to develop project---------2 marks

Context Diagram---2 marks

Level-1 DFD/ Functional or behavioural diagram---------2 marks

Hardware and software used and why? -----2 marks

10

Design:

Project architecture: How Modules are linked?---3 marks

Data design or Tables and there referential linkage-----------------3marks

Algorithms/procedure details-------------------------4 marks

10

Coding:

Implementation details of software--------2 marks

Input output screens of functions----------- 2 marks

Details of Standards used---------------------1 marks

5

Coding Demonstrations:

Student should be asked to write code for problem during viva todemonstrate his coding capabilities and s/he should be asked to write anysegment of coding given in project report.

5

Testing

Test cases--------5 marks Test Reports-----5 marks

10

Explanations of subjects areas related to the project 10

Documents

MCAproject Marking Scheme