SINE INTERNATIONAL INSTITUTE

OF TECHNOLOGY,JAIPUR
A
PROJECT REPORT
ON
“STUDENT MARKS ANALYSIS SYSTEM”
2nd YEAR/4th SEM (CS)
SESSION (2014-15)
SUBMITTED TO: SUBMITTED BY:
MR. BINAY KUMAR 1. KAVITA SHARMA
2. NEERJA SHARMA
 ABSTRACT :
Student Marks Analysis System is software which is helpful for students as
well as the college authorities. In the current system all the activities are done
manually. It is very time consuming and costly. Our Student Marks Analysis
System deals with the various activities related to the students. During analysis,
data collected on the various files, decision points and transactions handled by the
present system. The commonly used tools in the system are Data Flow Diagram,
interviews, etc. Training, experience and common sense are required for collection
of relevant information needed to develop the system. The success of the system
depends largely on how clearly the problem is defined, thoroughly investigated and
properly carried out through the choice of solution.

INTRODUCTION:
This document aims at defining overall software requirement for STUDENT
MARKS ANALYSIS SYSTEM . Efforts have been made to define the
requirements exhaustively and accurately. The final product will be having only
features/functionalities mentioned in this document and assumptions for any
additional functionality/feature should not be made by any of the parties involved
in developing/testing/implementing /using this product .

 PURPOSE: This specification document describes the capabilities that will be provided
by the software application STUDENT RESULT MANAGEMENT SYSTEM .It also states the
various constraints by which the system will abide. The intended audience for this document are
the development team, testing team and end users of the product.

 SCOPE: The application will manage the information about various students enrolled in
this course in different years, the subjects offered during different semesters of the course, the
marks obtained by the various students in various subjects in different semesters.The application
will greatly simplify and speed up the result preparation and management process.

 Overall description: The application will have capability to maintain information about
the students enrolled in the course, the subjects offered to students during different semesters ,
the marks obtained by the students in different subjects in various semesters. The software will
also generate summary report regarding student information, semester wise marks list and
performance reports .

 USER INTERFACES: (1) Login screen for entering the username, password, type of
user(Administrator, Data entry operator, student, teacher)will be provided. Access will be based
upon the ole of user. (2) A screen showing the marks obtained by the student in each subject.

Hardware interfaces: (1) Intel p4 processor with minimum 2GHz speed. (2) RAM:
Minimum 1GB (3) Hard Disk: min 20GB

 Software interfaces: (1) Visual Studio 2010 (2) Service Pack2 for Windows XP/VISTA
(3) DB Server: SQL SERVER 2008 (4) OS: Window Vista/XP/7

.Use Case Diagram

. Software development life cycle
There are various software development approaches defined and designed which are
used/employed during development process of software, these approaches are also referred as
“Software Development Process Models” (e.g. Waterfall model, incremental model, V-model,
iterative model, etc.). Each process model follows a particular life cycle in order to ensure
success in process of software development.

Software life cycle models describe phases of the software cycle and the order in which those
phases are executed. Each phase produces deliverables required by the next phase in the life
cycle. Requirements are translated into design. Code is produced according to the design which
is called development phase. After coding and development the testing verifies the deliverable of
the implementation phase against requirements

There are following six phases in every Software development life cycle model:

1. Requirement gathering and analysis

2. Design
3. Implementation or coding
4. Testing
 5. Deployment
6. Maintenance

1) Requirement gathering and analysis: Business requirements are gathered in this phase.
This phase is the main focus of the project managers and stake holders. Meetings with managers,
stake holders and users are held in order to determine the requirements like; Who is going to use
the system? How will they use the system? What data should be input into the system? What
data should be output by the system? These are general questions that get answered during a
requirements gathering phase. After requirement gathering these requirements are analyzed for
their validity and the possibility of incorporating the requirements in the system to be
development is also studied.

Finally, a Requirement Specification document is created which serves the purpose of guideline
for the next phase of the model.

2) Design: In this phase the system and software design is prepared from the requirement
specifications which were studied in the first phase. System Design helps in specifying hardware
and system requirements and also helps in defining overall system architecture. The system
design specifications serve as input for the next phase of the model.

3) Implementation / Coding: On receiving system design documents, the work is divided in

modules/units and actual coding is started. Since, in this phase the code is produced so it is the
main focus for the developer. This is the longest phase of the software development life cycle.

4) Testing: After the code is developed it is tested against the requirements to make sure that
the product is actually solving the needs addressed and gathered during the requirements phase.
During this phase unit testing, integration testing, system testing, acceptance testing are done.

5) Deployment: After successful testing the product is delivered / deployed to the customer for
their use.

6) Maintenance: Once when the customers starts using the developed system then the actual
problems comes up and needs to be solved from time to time. This process where the care is
taken for the developed product is known as maintenance.

.Feasibility study
The feasibility study is an evaluation and analysis of the potential of a proposed project. It is
based on extensive investigation and research to support the process of decision making.
Feasibility studies aim to objectively and rationally uncover the strengths and weaknesses of an
existing business or proposed venture, opportunities and threats present in the environment, the
resources required to carry through, and ultimately the prospects for success. In its simplest
terms, the two criteria to judge feasibility are cost required and value to be attained.

A well-designed feasibility study should provide a historical background of the business or

project, a description of the product or service, accounting statements, details of the operations
and management, marketing research and policies, financial data, legal requirements and tax
obligations. Generally, feasibility studies precede technical development and project
implementation.

A feasibility study evaluates the project's potential for success; therefore, perceived objectivity is
an important factor in the credibility of the study for potential investors and lending institutions.
It must therefore be conducted with an objective, unbiased approach to provide information upon
which decisions can be based.[

Feasibility study topics echo

Common factors

The acronym TELOS refers to the five areas of feasibility - Technical, Economic, Legal,
Operational, and Scheduling.

The assessment is based on an outline design of system requirements, to determine whether the
company has the technical expertise to handle completion of the project. When writing a
feasibility report, the following should be taken to consideration:

 A brief description of the business to assess more possible factors which could affect the study
 The part of the business being examined
 The human and economic factor
 The possible solutions to the problem

At this level, the concern is whether the proposal is both technically and legally feasible
(assuming moderate cost).

Legal Feasibility

Determines whether the proposed system conflicts with legal requirements, e.g. a data processing
system must comply with the local Data Protection Acts.

Operational Feasibility
Operational feasibility is a measure of how well a proposed system solves the problems, and
takes advantage of the opportunities identified during scope definition and how it satisfies the
requirements identified in the requirements analysis phase of system development.

The operational feasibility assessment focuses on the degree to which the proposed development
projects fits in with the existing business environment and objectives with regard to development
schedule, delivery date, corporate culture, and existing business processes.

To ensure success, desired operational outcomes must be imparted during design and
development. These include such design-dependent parameters such as reliability,
maintainability, supportability, usability, producibility, disposability, sustainability, affordability
and others. These parameters are required to be considered at the early stages of design if desired
operational behaviors are to be realized. A system design and development requires appropriate
and timely application of engineering and management efforts to meet the previously mentioned
parameters. A system may serve its intended purpose most effectively when its technical and
operating characteristics are engineered into the design. Therefore operational feasibility is a
critical aspect of systems engineering that needs to be an integral part of the early design phases.

Economic Feasibility

The purpose of the economic feasibility assessment is to determine the positive economic
benefits to the organization that the proposed system will provide. It includes quantification and
identification of all the benefits expected. This assessment typically involves a cost/ benefits
analysis.

Technical Feasibility

The technical feasibility assessment is focused on gaining an understanding of the present

technical resources of the organization and their applicability to the expected needs of the
proposed system. It is an evaluation of the hardware and software and how it meets the need of
the proposed system.

Schedule Feasibility

A project will fail if it takes too long to be completed before it is useful. Typically this means
estimating how long the system will take to develop, and if it can be completed in a given time
period using some methods like payback period. Schedule feasibility is a measure of how
reasonable the project timetable is. Given our technical expertise, are the project deadlines
reasonable? Some projects are initiated with specific deadlines. It is necessary to determine
whether the deadlines are mandatory or desirable.

.ERD (Entity Relationship Diagram):

Control Flow Diagram
Control diagrams are graphical notations specially designed to represent event and control
flows. Data flow is represented by solid arrow whereas control flow is represented by dashed or shaded
arrow. A process that handles only control flow is known as controlled process and is represented by
dashed bubble.

In some cases, multiple instances of the same control or data transformation occur. Ward and Mellor
notations used to represent such multiple instances simple overlays such process bubbles to indicate
multiplicity.

DATA FLOW DIAGRAM

 A graphical tool useful for communicating with users and
other personnel.

 Used to perform structured analysis to determine logical.

 Useful for analyzing existing as well as propsed system.

 Focus on movement of data between external entities and

processes, and between processes and data stores.

 A relatively simple technique to learn and use.

CONCLUSION :
It is an efficient method to store the student marks in the
smart phone rather than wasting the paper. It also
updates the students mark directly on the server
reducing the faculty’s time on logging from the
computer. In future we implement this same framework
to various online mark analysis for online test conducted
by many fields.
REFERENCES:
1. Zinged, Laird Darning, G. Blake Mike, and Masumi Nakamura,” Programming
Android”, Second Edition 2009.

2. Diego Torres Milano,” Android Application Testing Guide”, Packet Publishing,

2011

3. Wallace Jackson, “Learn Android App development”, Third Edition, 2010.

4. Don Feeler, “Android Tablet Application Development For Dummies”, john

Wiley and Sons,2012

5. Android SDK | Android Developers

http://developer.android.com/sdk/index.html

6. Kennedy,” Raising test scores for all students”, crowing press 2003.