Content

Topic Page No.

1. Aim of the Project 1
2. Introduction 1
3. Feasibility Study 2
4. Risk Analysis 4
5. Project size estimation 5
6. SRS Document 6
7. SRS Introduction Section 8
8. Types of Requirement 10
9. User interface design 20
10. Requirement Analysis 24
11. Software development process 25
12. SDLC 27
13. Coding 38
14. Testing 39
15. DFD 46
16. ER diagram 55
17. Data Flow Diagram 60

1|Page
 18. Snapshot of Login Page 65
19. Limitation 66
20. Conclusion 67

AIM OF THE PROJECT:-

The aim of the project is to develop an online based
teacher’s diary.

INTRODUCTION:-

PROBLEM STATEMENT:-
Develop an online teacher’s diary which can be
maintained by using internet. The data that are store in
the database can’t be hampering by any one which is
secure than maintain dairy in paper.

SCOPE: -
As every process becoming online in today’s world
so it is a step to add the teacher’s dairy system to online
system. It will easy for a teacher to maintain teacher’s

2|Page
 dairy sitting anywhere in world having internet
connection.

FEASIBILITY STUDY:-
The main of the feasibility study activity is to
determine whether it would be financially and technically to
develop the product. The feasibility study activity involves
analysis of the problem and collection of all relevant
information relating to the product.
TECHNOLOGY & SYSTEM FEASIBILITY
As in today’s world almost every work is done with
the help of computer, so why a teacher uses pen & paper
to maintain their daily diary.
In our project we are going to develop an online
system by which a teacher can maintain his/her diary
with the help of computer which is a technological
implementation to maintain teacher’s diary.
 OPERATIONAL FEASIBILITY
When teachers maintain their diary, it may be lost or
damage due to some incident. But if the system becomes
online then there is less chance of loss of data. Online

3|Page
 system is easy to use & also it is secure the data can’t be
hamper by any other user.
ECONOMICAL FEASIBILITY
Requires 20GB of web space to launch the website
which will cost very less for an organization who is going
to implement our project.

4|Page
RISK ANALYSIS:
• A risk is any anticipated unfavourable events or
circumstances that can occur while a project is
underway.
• If risk becomes true, it can hamper the successful and
timely completion of a project.
• Therefore it is necessary to anticipate and identify
different risk that a project maybe susceptible to, so that
contingency plans can be prepared to contain the effect of
each risk.
• In this context, risk management aims at reducing the
impact of all kinds of risk that might affect a project. Risk
management consists of three activities mentioned below
• Risk Identification
• Risk Assessment
• Risk Containment

• There are three different catagories of risk which can

affect a software project. These are :

o Project Risk
o Technical Risk
o Business RIsk

5|Page
PROJECT SIZE ESTIMATION :

Let the total lines of project estimated to be 250 lines.

Then total kilo lines of code(KLOC)=250/1000=0.25 KLOC
According to the basic COCOMO model:
(Assuming the team to be embedded)
 Effort=3.6(KLOC)1.20
=3.6(0.25)1.20
Effort=0.68 PM
 Time=2.5(Effort)0.32
=2.5(0.68)0.32
Time=2.21Month

 Cost=Time x (Pay/Month)
Cost=Time x (Pay/Month)

 Group Size=Time/Effort
=2.21/0.68
Group Size=3.25=4 Persons

6|Page
SOFTWARE REQUIREMENT SPECIFICATION
DOCUMENT:-

SRS document is a contract between the

development team and the customer.

Once the SRS document is approved by the

customer.

Any subsequent controversies are settled by

referring the SRS document.

PURPOSE OF SRS:-

 Communication between the Customer, Analyst,

system developers, maintainers.

Firm foundation for the design phase.

7|Page
  Support project management and control

SPECIFICATION PRINCIPLES:-

 Separate functionality from implementation.

Develop model of desired behavior of the system.

Establish the context in which s/w operates.

Define the environment in which system operates.

Specifications must be tolerant of incompleteness &

augmentable

BENEFITS OF SRS:-

Forces the users to consider their specific

requirements carefully.

Enhances communication between the Purchaser

and System developers.
8|Page
 Provides a firm foundation for the system design
phase.

Enables planning of validation, verification, and

acceptance procedures.

Enables project planning e.g. estimates of cost and

time, resource scheduling.

Usable during maintenance phase.

SRS-INTRODUCTION SECTION:-

Introduction:

The main purpose for preparing the document is to give a

general insight into the analysis and requirements of the
existing system or situation for determining the operating
characteristics of the system.

PURPOSE:-

9|Page
  To maintain teacher’s dairy through internet.

 To make the teacher’s dairy system online.

SCOPE:-

 It is easy to maintain dairy through online

rather than in pen & paper.

 By using this simple system through online

a teacher can gain extra knowledge about
internet

Developer’s Responsibility Overview

The developer is responsible for

1. The system should have a login.

2. Submitting the required user manual, describing the

system interface to work on and also the document of the
system.

10 | P a g e
 3. Maintaining the system for a period of one year after
installation.

TYPES OF REQUIREMENTS:-

FUNCTIONAL REQUIREMENTS:-

Transformations:-

Teacher can use this online system.

It stores all the data that required for

maintaining teacher’s dairy.

11 | P a g e
 It gives higher authority to see the all
information that is present in anyone’s dairy.

Data:-

 Inputs and Outputs:-attendance, marks,

class notes, lesson plan, report, syllabus.

 Stored data: - attendance sheet, mark sheet,

syllabus, time table.

NON FUNCTIONAL REQUIREMENTS:-

Performance Requirements:-

Capacity Response time

System priorities for users and functions

12 | P a g e
 System efficiency

Availability

Fault recovery

The total work of project is not completed yet, so the

above all the requirements are not specified in details.

External interface requirements:-

 User interfaces: - Login form, registration

form, class notes upload, syllabus, attendance
sheet, mark sheet, reports, remarks.

 Hardware interfaces:-The hardware interfaces

for this system are Pentium IV processor, min
512 MB of RAM, 4 GB free space in hard disk.

 Software interfaces:-The various software

interfaces for this system are JDK 1.6, Oracle
10g, Tomcat Web Server, Dreamweaver, and
Windows XP.

Functional Requirements :

13 | P a g e
Following is a list of functionalities of the system
 The system should have appropriate login facility,
relevant options like change password and creating
new profiles etc.

 The system should allow the administrator to control

all the activities, hence identify roles and accessibility
of other users.

 The administrator should have the facility to

add/modify/delete new performance measures.

14 | P a g e
Output Design:
Outputs from the computer system are required primarily
to communicate the results of processing to the users. They
are also used to provide a permanent copy of the results for
later consolation. The various types of outputs in general are
External outputs whose destination is outside the
organization.

Internal outputs whose destination is within the

organization.

Operational outputs whose use in purely within the

computer department.

Interface outputs which involve the user in

communicating directly with the system.

15 | P a g e
Output Definition:
The outputs should be defined in terms of the following points:
 Types of the output

 Content of the output

 Format of the output

 Location of the output

 Frequency of the output

 Volume of the output

 Sequence of the outputs

It is not always desirable to print or display data as it is held
on a computer. It should be decided as to which forms of
output is most suitable.
16 | P a g e
For example:
Will decimal point need to be inserted?
Should leading zeros be suppressed?

Output Media:
In the next stage it is to be decided that which medium is the
most appropriate for the output. The main considerations
when deciding about the output media are,
 The suitability of the device to the particular application.
 The need for a hard copy.
 The response time being limited.
 The location of users.
 The software and hardware availability.
 The cost.
Keeping in view the above description, the project is to have
outputs mainly coming under the category of internal outputs.
The main outputs desired according to the requirement
specification are,

17 | P a g e
  The outputs were needed to be generated as a hard copy
and as well as queries to be viewed on screen.
 Keeping in view the outputs, the formats for the outputs is
taken from the outputs which are currently being
obtained after manual processing.
 The standard printer is to be used as output media for
hard copy.

Input Design:
Input design is a part of the overall system design. The main
objectives during the input design are as follows,
 To produce a cost effective method of inputs.

 To achieve the highest possible level of accuracy.

 To ensure that the inputs is acceptable and understood by

the user.

Input stages:
The main input stages can be listed below

18 | P a g e
  Data recording

 Data transcription

 Data conversion

 Data verification

 Data control

 Data transmission

 Data validation

 Data correction

Input Types:
It is necessary to determine the various types of input. Inputs
can be categorized as follows.
 External inputs, which are prime inputs for the system.

19 | P a g e
  Internal inputs, which are user’s communications with
the system

 Operational inputs, which are computer department

communication to the system

 Interactive inputs, which are inputs entered during

dialog.

Input Media:
At this stage, choice has to be made about the input media. To
conclude about the input media, consideration has to be given
to,
20 | P a g e
 Types of input

 Flexibility of format

 Speed

 Accuracy

 Verification methods

 Rejection rates

 Ease of correction

 Storage and handling requirements

 Security

 Ease to use

 Portability

21 | P a g e
Keeping in view the above description of input types and input
media, it can be said that most of the inputs are of the form of
the internal and interactive inputs. As input data is to be
directly keyed in by the user, the keyboard can be considered
to be the most suitable input device.

Error Avoidance:-
At this stage care is to be taken to ensure that input data
remains accurate from that stage at which it is recorded up to
which the data is accepted by the system. This can be achieved
only be means of careful control in handling data.

Error Detection:-
Even though every effort is made to avoid the occurrence
of error, still a small proportion of error is always likely to
occur. These types of error can be discovered by using
validation to check the input data.

Data Validation:-
Validation procedures are designed to detect errors in
data at a lower level of detail. Data validations have been
included in the system in almost every area where there is a
possibility for the user to commit errors. The system will not
accept invalid data. Whenever an invalid data is keyed in, the
system immediately prompts the user and the user has to again

22 | P a g e
key in the data and the system will accept the data only if it is
correct. Validations have been included wherever necessary.
The system is designed to be a user friendly one. In other
words, the system has been designed to communicate
effectively with the user. The system has been designed with
popup menus.

User Interface Design:-

It is essential to consult the system user and discuss their
needs while designing the user interface.
User interface systems can be broadly classified as:
• User initiated interfaces:-

In this the user is in charge, controlling the progress of

the user dialogue. In the computer initiated interface,
the computer sets the next stage in the interaction.

• Computer initiated interfaces:-

In the computer initiated interfaces the computer

guides the progress of the user’s dialogue. Information
is displayed and the user response of the action takes
the action or displays further information.

23 | P a g e
User Initiated Interfaces:-
User initiated classes fall into two approximate classes,
• Command Driven Interfaces:
In this type of interface, the user inputs commands or
queries which is interpreted by the computer.

• Form Oriented Interface:-

The user calls up an image of the form to his screen
and dills in the form. The forms oriented interface is
chosen because it is the best choice.

Computer Initiated Interface:-

The following computer initiated interfaces were used:
• The menu system for the user is presented with a list of
alternatives and the user chooses one of the alternatives.

24 | P a g e
 • Question and answer dialog system were used, where the
computer asks questions and takes action based on the
basis of the user’s reply.
Right from the start, the system is going to be menu driven.
The opening menu displays the available options. Choosing
one options gives another popup menu with more options.
In this way every option leads the users to the data entry
form, where the users can key in the data.

Error Message Design:-

The design of the message is an important part of

the user interface design. As user is bound to commit some
errors therefore while designing of the system, the system
should be designed to be helpful by providing the user with
the information regarding the error he has committed. This
application must be able to produce output at different
module for different inputs.

25 | P a g e
Performance requirements:-
Performance is measure in terms of the output provided
by the application.
Requirement specification plays an important part in the
analysis of a system. Only when the requirement specification
is properly given, it is possible to design a system which will
fit into the required environment. It rests largely in the part of
the users of the existing system to give the Requirement
specification because they are the people who finally use the
system. This is because the requirements have to be known
during the initial stage so that the system can be designed
according to the requirements. It is very difficult to change the
system once it has been designed and on the other hand
designing a system, which does not cater to the requirement of
the user, is of no use.
The Requirement specification of any system can be broadly
stated as given below,

26 | P a g e
 • The system should be able to interface with the existing
system
• The system should be accurate or the system should be
better than the existing system.

The existing system is entirely dependent on the user to

perform all the duties.

REQUIREDMENT ANALYSIS:-
As every project has basically two requirements, our
project also have two requirement i.e.
 Hardware Requirement
 Software Requirement

HARDWARE REQUIREMENT
Processor-Pentium IV

4GB Free Space Hard Drive

Minimum 512MB RAM

SOFTWARE REQUIREMENT
27 | P a g e
  Operating System:- Windows XP

 Technology:-JDK 1.6

 Database:- Oracle-10g

 Designing Tool- Dreamweaver (HTML)

 Application Server:- Apache Tomcat

SOFTWARE DEVELOPMENT PROCESS:-

• Explain the important of a phased approach to software

development.
• Describe the various phases involved in software
development.
• Discuss the Entry and exit criteria from the various
phases.
• Explain the process of organizing various phases in to
processes.
• Software Engineering used to develop methods and
produced to high quality software at low cost.

28 | P a g e
 • The development process controls
Quality
Scalability
Consistency
Productivity
• Software development done in phases done ensures
consistency

PHASED APPROACH

Development Phased Activity

REQUIREMENT ANALYSIS:-
It translates informal inputs from users in to formally
specified requirements.

Problem Analysis
• Obtaining clear understanding of the requirement
,involves interviewing the clients

29 | P a g e
Basic Approach Involves
• Informal Approach :Communication through interviews

• Conceptual Modeling :Partitioning the Problem

• Prototyping :Analysis through feedbacks

Structured Requirement Analysis:-

FOCUSES ON
Functions performed in the problem domain
Data consumed and produced by these function.

SYSTEM ANALYSIS:-

It is an important activity that takes place when we are

building new information or changing existing ones.

The investigation in to system operation and possible

changes to the system is called system analysis.

30 | P a g e
 Once system analysis is completed system design
commences.

It is the process of studying and understanding the

existing system and its problems to design and build a
better system.

For system study and analysis we have to know the SDLC

process.

SDLC (SYSTEM DEVELOPMENT LIFE CYCLE):-

It is the over all process of developing information systems

through a multi step process from investigation of initial
requirements through analysis, design , implementation and
maintenance.

31 | P a g e
 Compare how software development companies
organize their development process.
Explain the essentials of any process model.
Discuss the advantages and disadvantages of various
process models.
Describe the criteria for choosing the appropriate
process models.
Describe the process model for the web and the process
technology.

ESSENTIAL OF PROCESS MODE:

SDLC consists of
 Preliminary investigation
Determination of system requirements
Design of the system
Development of software
System testing
Implementation and evaluation

PRELIMINARI INVESTIGATION:-

The basic for a candidate system is reorganizations of a

need for an improving an information system. This need leads
32 | P a g e
to preliminary investigation or initial survey to determine
whether an alternate system can solve the existing problem
.The purpose of preliminary investigation is to evaluate project
request .It refers to collection of information that permits the
management people in the system department to evaluate the
merit of the project request and make an inform judgment
about the feasibility of the purpose system.
The preliminary investigation accomplishes following
objectives
Clarifies and understand the project requirement

Determine the size of the project

Access cost and benefit of alternate approaches

Determine the technical and operational feasibility of

alternate approaches.

The various aspects of preliminary investigation are as

follows-
Request Clarification:-

33 | P a g e
 Initially all the activities by the executive and its
employee were done manually to communicate with each
other, which was a difficult task to the management realized
that they need a system , which will meet their requirements.

FEASIBILITY STUDY:-
Preliminary investigation examine project feasibility
,the like hood, the system is useful to the organization
.feasibility study is the test is a test of a system proposal
according to its workability, impact on organization ,ability
to meet user requirements and effective use of resources
.There are 3 aspects in feasibility study ..
TECHNICAL FEASIBILITY:-
The main purpose of technical feasibility is to test
whether with the existing h/w and s/w that the project can
plan. In case of hardware, we consider about the processor,
hard disk and size of RAM i.e. the configuration of the
development system we need to have. as our requirement is to
have a Clint server architecture system, the requirement for
both the Clint and server is 20 GB hard disc drive,pentiun 4
processor and 512MB RAM.

ECONOMICAL FEASIBILITY:-
A system that can be develop technically and will be
use if it is install must be a good investment for the
34 | P a g e
organization. This package is develop e as project work and a
foundation work for inventory control system of e-hotel
management and also learning each more valuable than any
other benefit, which comes in term of money .So it is
economically feasible.

OPERATIONAL FEASIBILITY:-
Any object can be beneficial only if it can meet
organizations operating requirements. The operational
feasibility is very much important in order to find out whether
the system will work after it is developed and installed. Also
this project is operational feasible.

REQUEST APPROVAL:-
The system was found to be technically,
economically, operationally feasible. Beside that the system
has the support of both the user and the management. Hence
the project was approved.
The data that analyst collect during preliminary
investigation are gather through following method.

INTERVIEW OF THE USER:-

35 | P a g e
 Analyst use interview to collect information from
individual or from groups. The person interview includes the
current user of the existing system and the potential users of
the propose system along the manager who is directly affected
by the system.
DESIGN OF THE SYSTEM:-
The most creative and challenging phase o the
system life cycle is system design. The term design describes a
final system and describe by which it is developed. It refers to
the technical specification that can be applied in implementing
the candidate system. It also includes the construction of the
program and program testing. The major steps in design are:
1. To determine how the output is produced and in what
format.
2. Input data and master files have designed to meet the
requirement of proposed output. The operational
phases are handled through program construction
and testing, including a list of program needed to
meet the system’s objective and complete
documentation.
3. Details related to the justification of the system on the
management as step toward implementation.

SYSTEM TESTING:-

36 | P a g e
 System testing is the process in which the system is
used experimentally to ensure that the S/W does not fail. In
system testing we are ensuring the quality of S/W. Quality
assurance is the review of S/W products and related
documentation for completeness, correctness, reliability and
maintainability. Testing verification and clarification are the
four level of quality assurance. Thus it is essential to ensure
the reliability of the S/W, this is done through various testing
technique.

IMPLIMENTATION AND EVALUATION:-

The implementation phase is less creative than
system design. It is primarily concerned with user training,
site preparation and file conversion. When the candidate
system is linked to terminals or remote sites, the
telecommunication network and the tests of the network along
with the system are also included under implementation.

SYSTEM DESIGN:-
Overview of design:

37 | P a g e
 Designing is the most important part of software
development. It requires a careful planning and logical
thinking on the part of the system designer. Designing the s/w
means to plan how the various parts of s/w are going to meet
the desired goals. It should be done with the utmost care
because if the phase contains error then it is going to effect the
performance of the system as a result it may take more
processing, more of coding time extra work load. System
design involves first logical design and physical design of the
system. When an analyst formulates a logical design write the
details specification for the outputs, and the inputs, files,
databases & procedures. Design specification instructs
programmers about what the system done. The programmers
in turn write the program those accept data from users,
process data produce the report and store data.
System design involves following three phases .
Design of output

Design of input

Design of database

38 | P a g e
DESIGN OF OUTPUT:-

Output is the most important and direct source of

information the user. Efficient, intelligent output design should
improve the user and help indecision making. A form of output
is a hard copy from the printer .The output will be shown in
the web page.

39 | P a g e
DESIGN OF INPUT:-
Inaccurate input data are the most common cause
of errors in data processing. Errors are entered by data entry
operator can be processing of converting user oriented inputs
to a comp based format. The input generated through forms is
stored in appropriate tables for processing. The following
forms are used for capturing input data.
1. Login Form : Captures user id along with his/her
password.
2. Main Form : Used for going into different forms used
in a system.
3. Tank Master Form : it holds the tank No ,the product
stored in the tank and the capacity of the tank.
4. Pump Master Form : It stores the information about
the pump ,the tank no that is connected to that pump.
5. Supply details Form : It keeps the details of the
supplier.
6. Purchase Form : It stores all product name ,rate of
item quantity of item ,bill no. of purchase bill ,the
amount , the net amount , tax amount , supply code of
from which the item purchased and the date of the
purchase.
7. Customer form : it keeps the details of customer
including his name , address etc.

40 | P a g e
DATABASE DESIGN:-
The database is designed after the analyst provides the
database administrator with following descriptions:
• Data needed from the databases.
• Actions that will affect the databases.
Then the role database administrator includes the following
responsibilities:
• Evaluate the appropriateness of the analyst’s
request.
• Describes methods for interactions with the
database.
• Ensure that the application cannot damage the
database or adversely affect the needs of other
information system applications in any way.

41 | P a g e
DATA DICTIONARY:-
Data dictionary is a catalogue-a repository –of the
elements in the system. Data dictionary are an integral
component of structured analysis, since data flow diagrams by
themselves do not describe the subject of the investigation. The
data dictionary provides additional information about the
system.
Every DFD model of a system must be accompanied
by a data dictionary. A data dictionary lists all data items
appearing in the DFD model of a system. The data item listed
include all data flows and the contents of all data stores
appearing on all DFDs in the DFD model of a system.
It may be recalled that the DFD model of a system
typically consists of several DFDs, namely level 0 DFDs, level
1 DFD, level 2 DFDs,etc. However a single data dictionary
should capture all the data appear in all the DFDs
constituting the DFD model of a system.
A data dictionary lists the purpose of all data items
& the definition of all composite data items in terms of their
component data items.

42 | P a g e
CODING:-
 Translates the design of the system to code in the given
programming language.
 Coding affects both the testing and maintenance process.
 Coding could be Top Down or Bottom Up.
Good Practices In Coding:
 Names

 Control Constructs

 Go To

 Information Hiding

 User-defined types

 Nesting

 Module size

43 | P a g e
  Module interface

 Program layout

 Side effects

 Robustness

 Internal documentations

TESTING:-

 Software testing

 Process of executing software in controlled manner.

 Validation :Are we doing the right job?

 Verification : Are we doing job right?

44 | P a g e
  Static analysis : Investigates source code of software.

 Dynamic analysis : looks at behavior of software while

executing.

 Debugging: Supports testing but cannot replace testing.

Testing Techniques:-
White box testing:-
White box testing is nothing but structural testing. In
structural approach test cases are generated based on the ram
called glass box testing. It is a test case design method that
uses the control using white box testing method the cases
derive are:
1. Guarantee that independent path within a module
have been exercised at least once.

45 | P a g e
 2. Exercise all logical decision on their true and false
side.
3. Execute all loops at their boundaries and within
their operational boundary.
4. Exercise all internal data structure to assure their
validity.
BLACK BOX TESTING:-
Black box testing also called as functional testing.
Here test case are solely on the basis of requirement or
specification of the program module, and the internals of the
modules or the programs are not considered. Black box testing
finds the error in the following categories.
1. Incorrect or missing functions.
2. Interface errors.
3. Performance errors.
4. Initialization and termination of errors.
White box testing is performed following by black box testing
during the design of “Inventory control system.

TESTING STRATIGES:-
THE UNIT TESTING:

The testing focus on the modules independently of one

another to locate error agents specification produced during
the design of the module. In other words this testing technique
is used to test the reliability of individual module. Since the
inventory control system is developed in modular way all the
46 | P a g e
modules are tested separately to ensure the reliability of the
project.

ADVANTAGE OF UNIT TESTING :-

1. Since the modules are developed separately and
resultant combine testing becomes difficult, hence
the unit testing is obvious choice.

2. The error detection , isolation and correction is

easy.

3. The compilation time required to compile a

module is less, hence the progress is first.

INTIGRATED TESTING:-
After the different modules are separated ,it is
necessary to test their behavior after they are integrated into a
single system. The testing of different module is fed to the

47 | P a g e
integrated system. The movement of data between the modules
is noted down at each step.
The benefits of integrated testing is obtained during the
project work:-
As the individual models are error free, one has to look
for the errors in their integration only.
The testing easily reflect the shortcoming of individual
module if exist. Hence modules are separately modified to suit
the integrated requirement.

VALIDATION TESTING:-

Validation is the process of evaluation of the S/W

at the end of the S/W development to ensure compilation with
S/W requirement. To ensure the reliability of the developed
S/W Alpha testing is one of the most rigorous testing. Our
project was gone through this testing successfully.

SYSTEM TESTING:-
The system which is developed, is testing module-
by-module taking both text as well as live data. Inconsistent
data deliberately is fed to each module to see if it could detect
the error in data. After all the modules were found to be
functioning properly the system is tested by taking sample data

48 | P a g e
from the other database. This system which is developed, can
again go for modifying by providing feed back to the system.

The system was tested for following aspects:

1) H/W and S/W would function to establish a true
performance level.
2) User: Acceptance (Stress Testing): Unlike volume testing,
where time is not a factor the system to high volume of
data over a short time period and the system did not
malfunction under high loads.
3) Recovery and Security: A forced system follower was
induced to test a back up recovery Volume: In the test we
create as would normally be produced to verify that the
procedure for the file integrity.In accurate data was
entered to see how the system in term of error detection
and protection. Also it is checked for security from un
authorized access.
4) Usability Documentation and Procedure: The system was
found to checked to find out whether it was user friendly
and was possible to prepare accurate and complete
documentation.
Apart from these the programs were also tested
for any errors and to whether it confirms to related programs
in the system.
Beside those testing, we have done two types of testing they
are:
 Alpha Testing
 Beta Testing

ALPHA TESTING:-

49 | P a g e
 When commercial system are developed with the explicit
intention of distributing them to dealers for marketing them
through company owned field officers, they first go through
verification called alpha testing. The feed back from the
validation phase generally produces changes on the software
to deal with error and failures that are uncovered.

BETA TESTING:-

This type of testing is done by the client’s site without

the presence of developer and if any error will discovered
later on, the developer will be noticed and rectifies it. After all
these the system was cleared off all its error to get a correct,
reliable, usable, efficient, accurate, error tolerant,
expandable, access control level and communicative systems.
Many codes have been written in the forms designer in
order to make the system error tolerant.

GOOD TESTING PRACTICE:-

 Testing against a specification

 Document the testing process

50 | P a g e
  Have aright attitude

 Test hierarchically

 Plane verification and validation

 Complement testing with other techniques

 Always test positively

DATA FLOW DIAGRAM(DFD):-

• Used for under standing and analyse the system

51 | P a g e
 • Based on analyzing the flow of data on the system

• Do not show decision or timing of event

• Represent a network of path

• A graphical representation that despicts information flow

and trans forms that are applied as data move from input
to out put.
The basic form of dataflow diagram is also known as data
flow graph or a bubble chart.
The DFD servers are two purposes:-
1. To provide an indication of how data are transformed as
they move through the system.
2. To depict the functions that transform the dataflow.
DFD are of two types:-
1. Physical DFD
2. LOGICAL DFD

52 | P a g e
PHYSICAL DFDS:-
It is implementation dependent view of current system.
It shows the movement of data between people, departments
etc.

LOGICAL DFDS:-
It is implementation development view of the system.
It shows the flow of data between processes DFDs.
The dataflow diagram may be used to represent a system at
any level of abstraction. In fact, DFD may be partitioned into
level that represent increasing information flow and functional
details. Therefore, the DFD provides a mechanism for
functional modeling as well as information flow modeling.

A LEVEL 0 DFD:-
Also called a functional system model or a context model,
represents the entire s/w elements as a single bubble with
input and out put data indicated by incoming and outgoing
arrows respectively.
At level 1 the level 0 DFD is expanded. The
information flow between process has been derived from the
parse. Here DFD might contain more than one no of bubbles
with interconnecting arrows.
A level 2 is the refined version of level 1DFD and
information flow continuity has been maintained between
levels.

53 | P a g e
DRAWING A DFD:-

• Identify major input and output

• Starts from inputs, work to outputs

• Identify transformation happening on the way

• Never show control logic

• Label each arrow with proper data element

PROCESS MODEL:-

• Linear process model

1. Waterfall model

2. Prototype model
• Evolutionary model s/w process model

54 | P a g e
 1. Incremental model
l 2.Spiral model
3. Component assembly model

WATERFALL MODEL:-

• Suggests a systematic, sequential approach to s/w

development

• It is otherwise called as linear sequential model.

PHASES
• System information engineering and modeling
• Software Requirement Analysis
• Software Design
• Detailed Design
• Coding
• Testing
• Integration
• Operations and Maintenance

55 | P a g e
Waterfall model-short falls:-
• Real projects rarely follows the sequential flow that the
proposes
• Often difficult for the customer to state all requirements
explicitly
• Customer must have patience

PROTOTYPING MODEL:-
• Allows for reduced functionality or limited
performance version of the eventual software

• Delivered in the early stage of project life cycle

• Helps to make the user requirement more concrete

DRAWBACKS OF LINEAR MODEL:-

• Late discovery of design defects results in cost over runs
and sometimes project cancellation

• The acceptance test also failed to cover many off nominal

problem encountered in beta testing

56 | P a g e
VOLUNTARY SOFTWARE PROCESS MODELS:-
• Linear sequential model is designed for straight line
development

• Prototyping Model designed to assist the customer

or developer in understanding requirements

• Evolutionary model is iterative ,develops more

complete versions of

INCREMENTAL MODEL:-
• Iterative in nature
• Combines
• Elements of the linear sequential model
• Iterative philosophy of prototyping
• Focus on the delivery of an operational product with
each increment
Incremental model Benefits:-
• Tolerances changing requirements
• Elements are integrated progressively
• Risks are mitigated earlier
• Allows the organization to learn and improve

57 | P a g e
 • Facilitates reuse
• Results in a more robust product
• Tolerates tacticial changes in the product
• Learning
• Higher quality
• Results in a more thoroughly tested product

Incremental model Problem:-

• Inflexible point solutions-Not suitable for
transition to large scale use
• High risk downstream capabilities-Risk in
extending the initially released architecture to
support desired features
• Off target initial release-Lack of initial user
activity analysis leading to off track initial
release

SPIRAL MODEL:-
• Couples the iterative nature of prototyping with
controlled aspects of linear sequential model

• Takes in to account the results of risk assessment

activities

58 | P a g e
 • Views software development as a spiral process

CHOOSING A PROCESS MODEL CRITERIA:-

• Time frame available

• Execution of project

• Type of product/project being developed

• Detail in which specifications are available

• Having previous experience with similar project

WHAT IS DBMS:-
59 | P a g e
 • A database management system is a collection of
interrelated data stored and a set of programs to
access this data.
• Supports single /multi user enviorment using time
sharing method
• Centralized to distributed datadase
• Powerful database structure
• Use of 4GL
DBMS OFFERS FOLLOWING SERVICES:-
• Data definition(create,storage)
• Data maintenance(checks each record has all fields
containing all the information about one particular item)
• Data manipulation(insert,update,delet,sort)
• Data display(viewing the data)
• Data integrity(ensure accuracy of data)
Benefits of DBMS:-
• The amount of redundancy in the stored data can be
reduced
• No more inconsistencies in data
• The stored data can be shared
• Standards can be set and followed
• Data integrity can be maintained
60 | P a g e
• Security of data can be implemented

61 | P a g e
DATA MODELING:-

Describes the relationship between data objects

First Level Entity Relation Diagram
Second level Normalization

ER DIAGRAM:-

 ENTITY RELATIONSHIP DIAGRAM: The entity

relationship diagram shows the relationships between the
various entities. This is a design tools that accomplish the
developing methods for the data storage and retrieval.

 ENTITY: An entity is a person, place, thing or event of

interest to the organization and about which data are
captured, stored or processed.

 ENTITY RELATIONSHIP: This defines dependencies

and extent to which entities are related.

62 | P a g e
SYMBOLS USED IN THE ER DIAGRAM:

 -Represent the entity sets

RECTANGLE

ELLIPSE -Represent the Attribute

DIAMO
ND -Represents relationship sets

-It links attributes to entity sets

E-R diagram can express the over all logical structure of a

database graphically.
• Entity relationship modeling is a technique for analysis
and logical modeling of a system’s data requirements.
• Its uses three basic concepts ENTITY, their ATTRIBUTES
and the RELATIONSHIP that exist between the entity.

63 | P a g e
ENTITY:-
• Objects, place,person or item about which information is
stored
• Each entity has certain properties or attributes
associated with it and operations applicable to it.

Condition
Represented by RECTANGLE.
Entity
Material
Employee
Book
Student
ATTRIBUTE:-
All the data elements that describe an entity.
It is represented by ELLIPSE.
Examples
ENTITY ATTRIBUTE
Customer Name

64 | P a g e
RELATIONSHIP:-
It represent the relationship between entities.
Relationship are classified in to following types
• One-To-One
• One-To-Many
• Many-To-Many
• It is represented by DIAMOND.
Other major components used in E-R diagram.
LINES-which links attributes to entity sets and entity sets to
relationship sets
DOUBLE ELLIPSES-which represents multivalued attributes
DASHED ELLIPSES-which denoted derived attributes
DOUBLE LINES-which indicate total participation of an
entity in a relationship set
DOUBLE RECTANGLES- which represent weak entity sets

65 | P a g e
NORMALIZATION:-

• Process of refining the data’s improves database design.

• Ensures minimum redundancy of data.
• Reduces need to recognize data when design is modified
• Storage space may also be conserved, resulting in a more
efficient database
• Allows us to insert, update delete and retrieve data’s
easily and efficiently.
• This process is made for a good database design
Achieved through a technique called ‘normalisation’

66 | P a g e
DFD :-
A data flow diagram is a graphical tool used to describe and
analyse movements of the data through a system. These are
the central tool and the basic from which the other
components are developed.
Symbols used in DFD:

-Represent External Entity

-Represent Process

-Represent Data store

-Represent Data flow

-Represent output

67 | P a g e
DATA FLOW DIAGRAM (DFD):-

68 | P a g e
69 | P a g e
70 | P a g e
71 | P a g e
72 | P a g e
SNAPSHOT OF LOGIN PAGE:-

73 | P a g e
LIMITATION:-

1. If the password of any user is hacked by anyone then the

system can be used by that hacker.

2. The user should have basic knowledge about internet &

computer to access the online teacher’s diary system.

74 | P a g e
CONCLUSION:-

The fundamental problem in managing & maintain

the dairy bye teacher is hence overcome. By developing this
web-based application the faculty can enjoy task, by doing it
easy and also by saving the valuable time. The amount of time
consumption is reduced and also the manual calculation are
omitted the reports can be obtained regularly and also when
ever demand by the higher authority.

75 | P a g e