MINOR PROJECT REPORT

(Minor Project Semester August-November 2010)

Topic: Digital Diary

Submitted by:

Divyansh NegiRegistration No.: 7470070046Section: A17B1Roll No.: RAI7B1A23Program: B.Tech (IT)-MBA (Integrated)

Virender KumarRegistration No.: 7070070037Section: A17B1Roll No.: RAI7B1A26Program: B.Tech (IT)-MBA (Integrated)

Under the Guidance of

Faculty Member:Mr. Sawal Tandon

LecturerLPU

Department of CSE/IT

Lovely Professional University, Phagwara

ACKNOWLEDGEMENT

1

The satisfaction that accompanies that the successful completion of any task would be incomplete without the mention of people whose ceaseless cooperation made it possible, whose constant guidance and encouragement crown all efforts with success.

We are grateful to our project guide Mr Sawal Tondon for the guidance, inspiration and constructive suggestions that helpful us in the preparation of this project.We also thank our colleagues who have helped in successful completion of the project.

Thanking you

Divyansh Negi and Virender Kumar

PREFACE

2

During the past decade, increasing attention has been focus on the Technology of Computer software. As

manual computing system becomes more numerous, complex the need for the systematic approaches

development becomes increasingly apparent.

The objective of project work-Digital Diary is designing a convenient frame work including Address Book,

Dead-Lines Note-Book and Reminder Application to the user on one platform. A primary goal of this project

is to develop good software to overcome the existing problem caused by manual systems.

This application is developed for the users who want to store contacts, want to set reminders and dead line

notes through single application. The users who have computer knowledge will get more advantage from

this application.

Although every care has been taken to check mistakes through verifications and validations, yet it is difficult

to claim absolute perfection.

EXECUTIVE SUMMARY

3

We have developed Digital Diary application to makes ease the work of users by this computerised software.

By this application a user can store contact details, retrieve contact details, set reminder for important

meetings of works and make dead line notes on single platform. Thus the user can manage his contacts and

daily working schedules through this application. This application avoids user to make manual contact

diaries to store the contact address. A user who is working on system can set reminder for the important

work while doing some another work. Reminder will remind him about that work. He can also set reminder

message which will tell him what to do at which time by stealing his attention.

Through dead line note book a user can set the start date, start date message, end date and end date message

for any project. This will remind him about a project that he had started on which date and when to submit

that project. On the whole this application will make a user punctual. The dead line note book will show

current date dead line notes through red colour as a warning.

So, this application is convenient platform for a user to manage, contacts, daily work schedules and to

enhance the punctuality of the user.

TABLE OF CONTENTS

4

PARTICULARS PAGE NO.

1. Acknowledgement 2

2. Preface 3

3. Executive Summary 4

4.Problem Statement 5

5.System Analysis 6

5.1 Existing System and Drawbacks 6

5.2 Proposed System Description 7

6. Software Requirement Specification 7

7.Feasibility Analysis 10

8.E-R Diagram 11

9.Data-Flow-Diagrams 12

10.Data Tables 16

11.Module Description 18

12.System Testing Security & Implementation 18

12.1 Coding 18

12.2 Testing 18

12.3 Security 19

12.4 Implementation 20

13.Input/output GUI Interface Screenshots 21

14.Conclusion 25

15.References 26

PROBLEM STATEMENT

5

This point describe you how to overcome the problem that arisen general for any person scheduling the

appointments, activities, daily work and managing contact details of their known’s. Previously we were

using manual systems to manage contact details of knowns. We were using separate applications for

reminder dead line note book reminder or manual methods to do that.

The task of managing daily activities future activities, contact details is time consuming and very

complex and may lead to confusion if not properly scheduled.

This is the application which provides user to maintain contact details, their present and future activities

and their start and deadlines date of accomplishing any project through one platform with one

application. A user can store contact details of any known person and side by side can set reminder and

dead line project details.

SYSTEM ANALYSIS

System analysis is a detailed study of various operation performed by a system and their relationships

within and outside the system. A key question is “what must be done to solve the problem?”. One

aspect of analysis is defining the boundaries of system and determining whether or not the proposed

system should consider other related systems. During analysis, data are collect from the available files,

decision points, and transactions handled by the present system.

The logical system model and tools that are used in the analysis are Data Flow Diagrams (DFDs), data

dictionaries and flow chart. The analysis part in the following pages cover:

Existing System

Proposed System

Existing System & Drawbacks

Almost each person have their known’s who are living apart from him having some contacts details. It is

a very complex task to store contact details manually at diaries and searching them page by page. A user

also want to do some specific tasks in the future for that he always makes diaries or separate applications

with limited memory size to store reminder data and large number of reminders. Side by side a user also

has to complete any work at some specific dates. A person having large number of task to be done at

different dead line dates also have to make manual entries in the separate applications or in the manual

diaries and he have to check those notes daily to know about which project’s deadline date is reached.

All these tasks are very time consuming and very complex.

Drawbacks:

6

As seen clearly a lot of time is spent and much effort is made for managing contact details of the known

future activities times and submission dates of the projects. In today’s world which is growing, these all

tasks should take minimum effort and less time. But the present system does not support this. In the

present system user install and operate on three different applications to complete about written task

which is very difficult and complex.

Proposed System

The system which we have developed makes it easy for a user to maintain, search thousand of contacts,

thousand of future activity reminder and thousand of future dead line dates for the projects through

installing and operating on single application, as it provides:

Address Book- to store add and search contacts

My Note Book- to set reminder for dead line dates of projects.

Reminders- to set reminders for the recent future activities

So, this system is very convenient a user. It saves the time of the user makes his work easy with fast

speed through operating on single application.

This is the application which provides user to maintain contact details, their present and future activities

and their start and deadlines date of accomplishing any project through one platform with one

application. A user can store contact details of any known person and side by side can set reminder and

dead line project details.

SOFTWARE REQUIREMENT SPECIFICATION

1. Introduction

1.1 Purpose The goal of the project is to develop the software for a computer-based personal Digital Diary. Only one user will use the Digital Diary at any time. There are three parts in the Digital Diary – a phone diary cum contacts list, task to do, reminder. The contacts are used to store and retrieve personal appointments.

Using the Digital Diary, a user must be able to add, delete and modify names, addresses and phone numbers. In addition, the user must be able to search and retrieve names and information associated with names (the address and phone numbers) from the Digital diary. The phone numbers can range from 7 to 21 digits, thus allowing the user to enter local, long distance and international phone numbers. Addresses use conventional 3-line format - The first line contains the house/building number followed by street name, followed by an apartment number, if any. The second line contains the city name, state abbreviation and the ZIP code. The third line contains the country name.

The appointment reminder is used to store and retrieve personal appointments throughout the year. A user must use date/time as a key when storing or retrieving reminder details. Each appointment must also

7

have a tag that can contain a name of the person in the appointment. By this way, the user can retrieve the address and phone number of the person when needed. The Dead line note book will also work as reminder but it will show dead line dates of the project by highlighting the current dead line dated projects.

1.2 Scope User who wants short and precise application can use it, without taking much time to install.

Users are allowed to delete, update any record any time. Almost every person is the user of this application because everyone has to store contact address of their known’s, to manage future activities through reminders, to get remind about the dead line dated projects. This application provides a user to manage the above written activities through single platform with one application.The features that are described in this document are used in the future phases of the software development cycle. The features described here meet the needs of all the users.

1.3 Overview This the product which can used as only for personal use. User uses it in their laptop and desktops. It is

short and precise application.

2. The Overall Description It includes general factors that affect the product design and implementation in Digital Diary requirements

and necessary features. Digital Diary requirements and specifications will be the main factor determining the design of the components since this is a single user product.

2.1 InterfacesAll component interfaces will be GUI interfaces.

Logical Characteristics:

(1) View Status

(a) View list of contact persons at once or differently

(b) Can display all the upcoming appointments through reminders

(c) Can display all the start and end dates of the projects to be accomplished

(2) Change Status

(a) Options for changing a person’s information

(b) Interface is easy to find person in list

(c) Options to edit reminder- time, date, message and date, message for the coming projects.

2.2 Hardware Requirement

The system has following hardware requirements: Pentium 2 and higher processor 16 MB RAM minimum 64kb cache memory at least Hard Disk 50 MB space at least

8

2.3 Software requirementsThe system has following software requirements:

Operating System: Window XP/98/95/NT/ 2000/W 7 Database server -: Ms-access Data base connectivity: ODBC, Microsoft ODBD Driver Other tools and technology: Visual Studio 2008 Front End: C# Back End: Ms-Access

2.4 Product FeaturesUsers are provided with different function and each function sub-functions.Address Book is having sub function like user can see the date from 1 to 30 at time, add, delete, edit, save and close. User can make schedule for whole day in particular date, a different page is opened using my notes. Search help to find out your contacts in bulk of contacts. You can use it for saving previous record. Important alarms are there.

(1) Product will need to connect with Ms-Access database.

(2) Product will work on windows operating only

(3) Product will need to overcome search latency, when records are more then 1000.

2.5 Apportioning of RequirementsWe feel that we can accomplish all of the above stated requirements given the time that we have. We have already limited the number of components that we intend to develop, because we do feel that we have time to completely finish and test more components then the ones listed in future.

3. Specific Requirements: Specific requirements include:

3.1 Functions: Product will perform following functions:3.1.1 Functional Requirements

In this system there is lots of functioning: The user can Search and see any account information.

a) He will be able to get the record using character searching.

b) There will also be a reminder and digital diary through this he can go to know about details.

c) User can use my notes for daily purpose.

d) Main user can safe this application by giving passwords so that no other can put record into it.

3.1.2 Non-Functional Requirement: Non functional requirements are as:

3.1.2.1 Performance RequirementsSoftware must be able to support more than 2000 entries, and efficiently search them.

3.2.2.2 Safety requirementDatabase safety from viruses and operating system failure

9

3.2.2.3Software quality attributesThe quality of the database maintained in such a way so that it can be a very user friendly to all the user of the data base.

3.2.2.4 Design ConstraintsThe system must be designed in such a way that it will easy to use and user friendly.

3.2.2.5 ReliabilityWe try to make it reliable by testing it.

3.2.2.6 AvailabilitySystem will be available during all work hours.

3.2.2.7 SecurityLogins will be used to restrict use.

FEASIBILITY STUDY

Feasibility study is a high level version of the entire system and design process. The purpose of feasibility study is not to solve the problem but to determine if the problem is worth solving. It is conducted to select the best system that meets performance requirement. A system’s required the identification of specific system objectives, and a description of out puts defines performance.Three key considerations are involved in the feasibility analysis:

Economical feasibility Technical feasibility Operational feasibility

Economical feasibility: economical analysis is the most frequently used method for evaluating the effectiveness of the proposed system. This is an ongoing effort that improves inaccuracy at each phase of the system life cycle. As the necessary software and hardware is available in the system, the initial investment for the proposed system is NIL.

The proposed system minimizes the time and effort right from managing the activities. Thus, the proposed system is economically feasible.

Technical feasibility: it centres on the existing computer system (hardware, software etc) and to what extent it can support the proposed system. The necessary hardware and software tools are available in the computer system and the software recommended supports the system objectives. Thus, it is technically feasible to design and develop the proposed system.

Operational feasibility: people are inherently resistant to change and computers have been known to facilitate the change. As estimate should be made of how a strong reaction the user is likely to have towards the development of a new system. As the proposed system is a user friendly package with all the visual aids,

10

Address Book Reminder System

ID

Name

Address

Phone

Other Details

Father’s Name

Nationality

Mail ID

Designation

DOB

Qualification

My Notes

ID

Start Date

Notes

Dead Line Date

Dead Line Notes

ID

Date

Time

Message

User

do

User Name

Password

Login

Digital Diary

Select

the effort that goes into the educating and training the user staff is almost negligible. Therefore, resistance to the proposed system is NIL.

Based on the above analysis, the recommended system is feasible.

ENTITY RELATIONSHIP DIAGRAM

DFD (DATA FLOW DIAGRAMS)

11

Level-0

Level-1

12

Level-2

13

Level-3

14

DATA TABLES

15

Table under AddressBook.mdb Database:1. AddressData Table2. login Table

AddressData Table:

login Table:

Table under MyNotes.mdb Database: tb1_notes Table:

16

Reminder uses the XML file for creating the Data Table as given:

MODULE DESCRIPTION

17

The main objective of the Digital Diary is to Display, Store, Edit, Searching Contacts, setting reminders and

setting dead line project dates. We have divided it into three sub-modules as given under:

1. Address-Book: for inserting, editing, searching the contacts of the known.

2. My-Note Book: for inserting the start date with message and end date of the project with specific

message.

3. Reminder: to set reminder for accomplishing specific activities at time.

All the above three modules are integrating within the Digital Diary to give an ease to the user. A single user

can operate on it at a time in one system. Total control on the application is provided to the authorized user.

First sub-module is the Address Book that a user can use to store contacts of their known. He can store

thousands of the records in it. A user can edit any contact easily and he can also search the contact by the

initial character searching of the contact name.

Second sub-module is My Note Book that a user can use to manage the starting and deadline dates of the

projects that he has to complete. He simply can add, edit and delete any entry made in it. The starting and

end date of the projects with the specific messages can be stored in this Note Book. The current deadline

dated projects will be highlighted with the red colour as a warning.

Third sub-module is Reminder that a user can use to remind him about the activities planned by him to

complete at some specific times in future. He can add any reminder with specific message at specific date

and time to be shown. A user can also edit and delete any entry at any time.

SYSTEM TESTING SECURITY & IMPLEMENTATION Coding

Coding is the process that transforms design into a programming language, which can be understood by the

computer. Coding is viewed as natural source code which is based on internal documentation, methods for

data declaration procedures for statement constructions and input output techniques. Source Code is

Intelligible if it is simple and clear.

Testing:

Testing the newly developed or modified systems is one of the most important activities in the system

development methodology the goal of the testing is to verify the logical and physical operation of the design

blocks to determine that they operates as intended.

18

During testing the program to be tested is executed with a set of the test cases, and the output of the program

for the test cases is evaluated to determine if the program is performing as it is expected to do so. There are a

number of rules that can serve well as testing objectives.

Testing is a process of executing a program with the intent of finding errors. Good test case is alone that has

a high Probability of finding as yet undiscovered errors. A successful test is one that uncovers as yet

undiscovered errors. The basic levels are unit testing, Integration testing and Acceptance testing. The

different levels of the testing attempt to detect different types of the faults as discussed below:

Unit Testing

During the implementation of the system each module of the system was tested separately to uncover errors

with all its boundaries. User inter-faces was used as a guide in this process.

Integration Testing

The objective of the integration testing is to take the unit tested modules and build a program structure that

has been defined in the design. We have down a top down integration, which is an incremental approach,

which is constructing and testing small segments where errors are easier to isolate and corrected. The

Integration process was performed in three steps is:

1. The main control was used as a test driver.

2. Tests were conducted as each module was integrated.

3. Regression Testing (Conducting all or some of the previous tests) to ensure that new errors not been

introduced.

System Testing

Here the entire software system was tested. The references document for this process is the requirements

document and the goal is to see if the system meets its requirements.

Boundary Conditions Test

Boundary conditions as in case of the generating sequences were tested to ensure that the module operates

properly at boundaries established to limit or restrict processing.

Acceptance Testing

This is normally performed with the realistic data of the client to demonstrate that the software is working

satisfactorily. Testing here focus on external behaviour of the system.

Security

Security is the main concepts we have to provide in the project, so that unauthorized users can not access or

violate valuable information. In the present system we provided a logon screen which monitors the users.

Which helps the only authorized users can access the data.

Implementation

19

The implementation phase is the period during which the system is used. The major activities of this are:

1. Complete conversion2. Operate system3. Evaluate system performance4. Maintain system and manage charges

The implementation phase follows the development phase. Usually it is the longest of all life cycle phases

and is characterized by four distinct stages. Initially the new system must be introduced into business activity

mainstream. This state is called changeover. The changeover transaction period may take weeks or even

months. After it is completed the system enters the operation and routine maintenance state. Early in this

stage an evaluation should be made based on performance measurement that determine whether the specific

benefits claimed for the system have been achieved. Finally the new system has all operational systems must

be able to accommodate change. Change is perhaps the most important state in the life of a computer based

application. Whether or not change can be managed is the final measure of the success or failure of the entire

system effort.

The principal activities and documents that characterize the stages of the implementation phase are:

System Changes Over

Normally a period of transition is required to change from an old system to new one. If all the development

phase implementation activities have been performed adequately the necessary manuals and documentation

for the new system are available. There is a nucleus of trained personnel to assume responsibility for the new

system. However it is critically important for the project team to remain heavily involved and in control

during changeover. Changeover usually is one way process it must result in a planned, numerous unforeseen

incidents and problems will arise. System changeover is the most critical period in the entire life cycle of the

computer-based system. Positive support by all user organization is essential.

Routine Operation

At the conclusion of the changeover process the system has been operational for a reasonable period; its

performance is formally evaluated. The result of the evaluation is documented in an evaluation report, which

should be presented to a user management review board. The principle user of the system should head the

board.

System change

The modern system environment is dynamic subject to many internal and external influences. The business

environment may trigger a change request, which is then reviewed by the user management. This process

may form a brief analysis of the requested change to an extensive investigation. This investigation could

cause a return to the study phase, in which case the resulting new design and development activities might

yield a great modified system.

20

INPUT/OUTPUT GUI INTERFACE SCREENSHOTS Login Form:

Main Form:

Address Book Form:

21

My Notes Form: This form is showing two states:

1. Starting My Notes Form:

2. My-Notes form showing Deadline Date of project with red colour:

22

Reminders Form: Three states of this form are shown:

1. Starting form:

2. Form after reminder details insertion:

23

3. Reminder showing pop-up:

CONCLUSION

24

This report gives an overview of all that one needs to get acquainted with in order to work with software

project documentation specifically in the field of software development.

It was a diverse and enriching experience to learn from developing a software and documentation in a team

on our own.

This project helped us to enhance our skills in programming field of the software development. We learnt

how to develop software, how to make requirement analysis, how to make feasibility analysis and how to

document the same.

On a whole, this project helped us to enhance our technical skills, teamwork, documenting skills.

REFERENCES

25

Books:

1. C# Black Book, Wiley

2. C# Unleashed, Pearson Education

Websites:

1. http://www.edrawsoft.com/Data-Flow-Diagrams.php

2. http://www.freetutes.com/systemanalysis/sa5-dfd-ordering-system.html

3. http://www.umsl.edu/~sauterv/analysis/dfd/dfd.htm

4. http://www.agilemodeling.com/artifacts/dataFlowDiagram.htm

5. http://www.csharphelp.com/archives/archive172.html

6. http://www.datadirect.com/developer/net/index.ssp

7. http://www.codeproject.com

8. http://www.msdn.com

26