Micro Project report on

STUDENT EXAMINATION DATA CARD

Academic Year: 2021–2022 InstituteCode:056

3

Program: Computer Engineering Semester: IV

Course: Software Engineering [SEN] CourseCode:21243

Group no: 24

Maharashtra State Board of Technical Education, Mumbai

(Autonomous)(ISO-9001-2008) (ISO/IEC 27001:20013)
 Maharashtra State Board of Technical Education,
Mumbai

CERTIFICATE

This is to certify that,

Roll Student Name Seat No Enroll No

No

72  CHELIPARAMBIL JOSHUA 2005630117

BINOY

73  DHANAWADE RAJ VIJAY 2005630118

74  KAMBLE MANSI JAYWANT 2005630119

Of Fourth Semester of Diploma in Computer Engineering of Institute

Pravin Patil College of Diploma Engineering and Technology, Bhayander
(E) (Code: 0563) has completed the Micro Project satisfactorily in subject
SOFTWARE ENGINEERING (22413) for the academic year 2021–2022 as

prescribed in the curriculum.

Place: Bhayander (E)

Date:

Mrs.Harsha Zope MRS.MANJULA ATHANI Mrs. R.B. PATIL

Subject Teacher Head of Department Principal
 PART A
Micro Project Proposal

STUDENT EXAMINATION DATA CARD

 Brief Introduction:-
The “Studtent card system” will make a complete information detail about each
individual student.
It will contain all the examination results from his S.S.C. till date, which will include all
government given examinations results in it. These results will be in the form of scanned
document. And the format will be very compressed one which won’t require more storage
space.

Advantages:-
1. The System provides simple way of document verification.
2. Eliminates the need to store all documents thus saving physical
space.
3. The Student does not need to carry all documents physically.
4. A Single card for all documents.

Disadvantages:-
1. If card is lost there is no way to interact with system

Application:-
 The card can be used during exams
 It helps to save our documents in one card,can seen easily

 Aim of the Micro-Project

1. The time spent during result processing will be reduced due
to the speed of computer system.
2. A database for managing students results.
3. To develop a query, modules, for easy interaction with the
database.
4. To have a database on student result, record, were query and
validation check can be carry out.
5. To eliminate the various problem associated with the manual
method and alleviate a flexible method of processing.
 6. To improve proper documentation of result which a
computer is capable of.
7. Storing large volume of data over a long period of time.

 Action Plan
Name of
Sr. Planned Start Planned Finish
Details of Activity Responsible
No Date Date
Team Members

Discussion and finalization of

1  
topic

Preparation & submission of

2
abstract

Collection of data&Literature
3
review

Discussion on outline of
4 content & Formulation of
content

Editing and proof reading of

5
content

Compilation of report and

6
Presentation

7 Viva Voce

8 Final submission

Sr. Name of
Specifications Qty Remarks
No Resource/Material

For report
1 MS Word MS Office 2013 1
purpose
 Nirali Available in
2 Books 1
Publication college library

 Resources Required

********************

PART B
Micro Project report
SOFTWARE PIRACY PROTECTION SYSTEM
1.0Brief Introduction
The “Studtent card system” will make a complete information detail about
each individual student.
It will contain all the examination results from his S.S.C. till date, which will include all
government given examinations results in it. These results will be in the form of scanned
document. And the format will be very compressed one which won’t require more storage
space.
The existing students can apply for the same and get their regarding card , and the
one’s in the S.S.C. currently can get their cards along with their results.The admin will get a
list wise view of all the students with their UIN(unique identification number),which is
unique for all the students. And he can view it also college wise , in that too department
wise. The user of the card will get all the details of his exam results in the card,and also some
other information about the courses completed or ongoing.

Advantages:-
1. The System provides simple way of document verification.
2. Eliminates the need to store all documents thus saving physical
space.
3. The Student does not need to carry all documents physically.
4. A Single card for all documents.

Disadvantages:-
1. If card is lost there is no way to interact with system

Application:-
 The card can be used during exams
 It helps to save our documents in one card,can seen easily
 
2.0Aim of the Micro-Project
1. The time spent during result processing will be reduced due
to the speed of computer system.
2. A database for managing students results.
3. To develop a query, modules, for easy interaction with the
database.
4. To have a database on student result, record, were query and
validation check can be carry out.
5. To eliminate the various problem associated with the manual
method and alleviate a flexible method of processing.
6. To improve proper documentation of result which a computer
is capable of.
7. Storing large volume of data over a long period of time.

3.0Course Outcomes Integrated

a. Select suitable Software Process model for Software development.
b. Prepare software requirement specification.
c. Use Software modeling to create data designs.
d. Estimate size and cost of create data designs.
e. Apply project management and quality assurance principle in software
development.

4.0Actual Procedure Followed

1. Selection of topic.
2. Information collected from books.
 3. Information collected from web resources.
4. Designing algorithm for project.
5. Developing code for project
6. Solving error and testing of project.
7. Preparation of report.

5.0Outputs of the Micro-Project

 WATERFALL MODEL

Waterfall Model:-
The Waterfall Model was the first Process Model to be introduced. It is also
referred to as a linear-sequential life cycle model. It is very simple to
understand and use. In a waterfall model, each phase must be completed
before the next phase can begin and there is no overlapping in the phases.
Phases:-
 Requirement Gathering and analysis − All possible requirements of the system to be
developed are captured in this phase and documented in a requirement specification
document.
 System Design − The requirement specifications from first phase are studied in this
phase and the system design is prepared. This system design helps in specifying
hardware and system requirements and helps in defining the overall system
architecture.
 Implementation − With inputs from the system design, the system is first
developed in small programs called units, which are integrated in the next phase.
Each unit is developed and tested for its functionality, which is referred to as Unit
Testing.
 Integration and Testing − All the units developed in the implementation phase are
integrated into a system after testing of each unit. Post integration the entire
system is tested for any faults and failures.
 Deployment of system − Once the functional and non-functional testing is done;
the product is deployed in the customer environment or released into the market.
 Maintenance − There are some issues which come up in the client environment. To
fix those issues, patches are released. Also to enhance the product some better
versions are released. Maintenance is done to deliver these changes in the
customer environment.

 Advantages of Waterfall Model:

1. Simple and easy to understand and use
2. Easy to manage due to the rigidity of the model. Each
phase has specific deliverables and a review
process.
3. Phases are processed and completed one at a time.
4. Works well for smaller projects where requirements
are very well understood.
5. Clearly defined stages.
6. Well understood milestones.
7. Easy to arrange tasks.
8. Process and results are well documented.
 Disadvantages of Waterfall Model: 
1. No working software is produced until late during the
life cycle.
2. High amounts of risk and uncertainty.
3. Not a good model for complex and object-oriented
projects.
4. Poor model for long and ongoing projects.
5. Not suitable for the projects where requirements are
at a moderate to high risk of changing. So, risk and
uncertainty is high with this process model.
6. It is difficult to measure progress within stages.
7. Cannot accommodate changing requirements.

 Functional and Nonfunctional Requirement of Project:

1. Functional Requirement:
 Functional requirement describe the interaction of software with its environment
and specify the input, output, external interfaces and function that’s should be
included in the software.

1. There should be a function for the customer or client online register.

2. There should be a function for downloading the software after buying.

3. There should a function for downloading for one device software (client can’t
download more than software at the same time device.)

4. There should be a facility for key generation (password). Password should be 6

digits (contains only numbers.)

5. Its accept only three times wrong password.

6. It should be function for matching data to developer.

2. Non-Functional Requirement:-
 1. Performance requirement: -If there are performance requirements for the product
under various circumstance state them here and explain their rational, to help the
developers understand the intent and make suitable design choices.

2. Safety requirement: - Specify those requirement that are concerned with possible
loss damage, or harm that could result from the use of product. Define any
safeguard or action that must be taken, as well as action that must be prevented.

3. Security requirement: - Specify any requirement regarding security and privacy

issues surrounding use of the product or protection of the data used to create by the
product. Define any user identity authentication requirements.

 USE – CASE DIAGRAM

 ACTIVITY DIAGRAM
  Size Estimation:-

Information
Weighting factor
Domain value
Count

Simple Average Complex

No. of user input

3 6 18
No. of user output
4 * 7 28

No. of user inquires

1 7 7

No. of logical files

1 15 15

No. of external
files 1 10 10

Count total 78

Functional Point = Count Total *(0.65 +0.01 * sum [fi])

= 78 * (0.65+0.01*70)
= 94.5
 Cost estimation:-
Software project ab bb cb db
Organic 2.4 1.05 2.5 0.38
Semi-detached 3.0 1.12 2.5 0.35
Embedded 3.6 1.20 2.5 0.32
1. Effort estimation:-
E = ab (KLDC) bb
= 2.4(24)1.05
E = 67.52
2. Durationestimation:-
D = cb(E)db
=2.5(67.52)0.38
D = 12.39 months

3. Person estimation
P = E/D
= 67.52/12.39
P = 2 person
 Time line chart:-
7.0 Skill Developed/Learning out of this Micro-Project
✓We developed the skillof working ingroup.

✓To implement informations into diagrams.

Teacher Evaluation Sheet

Name of Student:  CHELIPARAMBIL JOSHUA BINOY Enrollment No: 2005630117

Name of Program: COMPUTER ENGINEERING Semester: FOURTH
Course Title: SOFTWARE ENGINEERING Code: 22413
Title of the Micro Project: STUDENT EXAMINATION DATACARD
Course Outcomes Achieved:
a. Select suitable Software Process model for Software development.
b. Prepare software requirement specification.
c. Use Software modeling to create data designs.
d. Estimate size and cost of create data designs.
e. Apply project management and quality assurance principle in software development.
Evaluation as per Suggested Rubric for Assessment of Micro-Project

Sr Characteristic to be Assessed Poor Average Good Excellent Sub

. (Marks 1- (Marks 4-5) (Marks 6- (Marks 9- Tota
No 3) 8) 10) l
(A) Process and Product Assessment (Covert above total marks out of 6 Marks)
1 Relevance to the course
Literature Survey / Information
2
Collection
Completion of the Target as per
3
project proposal
4 Analysis of Data and
 Representation
5 Quality of Prototype/Model
6 Report Preparation
(B) Individual Presentation / Viva (Convert above total marks out of 4 Marks)
7 Presentation
8 Defense

Micro-Project Evaluation Sheet

(A) Process and Product Assessment (B) Individual Presentation / Viva Total Marks
(6 Marks) (4 marks) (10 Marks)

Comments / Suggestions about team work / leadership / inter-personal communication:

……………………………………………………………………………………………………………………
……………………………………………………………………………………………………………………
……………………………………………………………………………………………………………………

Name & Designation of the Teacher: MRS.Harsha Zope

Dated Signature: ………………………………………..

Teacher Evaluation Sheet

Name of Student: DHANAWADE RAJ VIJAY Enrollment No: 20056118
Name of Program: COMPUTER ENGINEERING Semester: FOURTH
Course Title: SOFTWARE ENGINEERING Code: 22413
Title of the Micro Project : STUDENT EXAMINATION DATACARD
Course Outcomes Achieved:
a. Select suitable Software Process model for Software development.
b. Prepare software requirement specification.
c. Use Software modeling to create data designs.
d. Estimate size and cost of create data designs.
e. Apply project management and quality assurance principle in software development.
Evaluation as per Suggested Rubric for Assessment of Micro-Project

Sr Characteristic to be Assessed Poor Average Good Excellent Sub

. (Marks 1- (Marks 4-5) (Marks 6- (Marks 9- Tota
No 3) 8) 10) l
(A) Process and Product Assessment (Covert above total marks out of 6 Marks)
1 Relevance to the course
Literature Survey / Information
2
Collection
3 Completion of the Target as per
project proposal
 Analysis of Data and
4
Representation
5 Quality of Prototype/Model
6 Report Preparation
(B) Individual Presentation / Viva (Convert above total marks out of 4 Marks)
7 Presentation
8 Defense

Micro-Project Evaluation Sheet

(A) Process and Product Assessment (B) Individual Presentation / Viva Total Marks
(6 Marks) (4 marks) (10 Marks)

Comments / Suggestions about team work / leadership / inter-personal communication:

……………………………………………………………………………………………………………………
……………………………………………………………………………………………………………………
……………………………………………………………………………………………………………………
Name & Designation of the Teacher: Mrs.Harsha Zope

Dated Signature: ………………………………………..

Teacher Evaluation Sheet

Name of Student:  KAMBLE MANSI JAYWANT Enrollment No: 2005630119
Name of Program: COMPUUTER ENGINEERING Semester: FOURTH
Course Title: SOFTWARE ENGINEERING Code: 22413
Title of the Micro Project : STUDENT EXAMINATION DATACARD
Course Outcomes Achieved:
a. Select suitable Software Process model for Software development.
b. Prepare software requirement specification.
c. Use Software modeling to create data designs.
d. Estimate size and cost of create data designs.
e. Apply project management and quality assurance principle in software development.
Evaluation as per Suggested Rubric for Assessment of Micro-Project

Sr Characteristic to be Assessed Poor Average Good Excellent Sub

. (Marks 1- (Marks 4-5) (Marks 6- (Marks 9- Tota
No 3) 8) 10) l
(A) Process and Product Assessment (Covert above total marks out of 6 Marks)
1 Relevance to the course
Literature Survey / Information
2
Collection
3 Completion of the Target as per
project proposal
 Analysis of Data and
4
Representation
5 Quality of Prototype/Model
6 Report Preparation
(B) Individual Presentation / Viva (Convert above total marks out of 4 Marks)
7 Presentation
8 Defense

Micro-Project Evaluation Sheet

(A) Process and Product Assessment (B) Individual Presentation / Viva Total Marks
(6 Marks) (4 marks) (10 Marks)

Comments / Suggestions about team work / leadership / inter-personal communication:

……………………………………………………………………………………………………………………
……………………………………………………………………………………………………………………
……………………………………………………………………………………………………………………
Name & Designation of the Teacher: Mrs.Harsha Zope

Dated Signature: ………………………………………..