09-04-2012, 10:15 AM
Personal Diary
PERSONAL DIARYdocumentation2007.docx (Size: 1.3 MB / Downloads: 77)
ACKNOWLEDGEMENT
This project has been received tremendous assistance and good wishes from a large cross-section of people we therefore acknowledge me general indebtedness for each and every one associated with me for this project.
We esteem it a great privilege to thank Mr.D.Murali, The Principal, Sree Narayana College Cherthala for granting me permission to do the project.
We convey my sincere thanks to Mrs.Sangeetha, M.Tech (elec), MS.Anju, Msc CS and MS.BINDU, MCA for their valuable instructions and guidance to the project and their apt encouragement towards the successful completion of our project.
We thank Almighty God for allowing us to complete our project work successfully. We would like to take a minute to acknowledge those who helped me for the completion of the project.
Once again we remember with great pleasure and gratitude towards those who extended their hands for me.
SYNOPSIS
Here we are proposing utility software for Personal Diary. This software will help people to keep their personal information’s like daily notes photos etc, safe for a long period of time . The present system is manual and we are attempting to design a software which will make it more efficient. It is designed to overcome the problems that we face with the conventional diary.
We are using Microsoft Visual Studio as front end and Microsoft SQL as back end.
We hope this is the most convenient method for solving the problem of the present system.
1.2 PROJECT OVERVIEW
Personal Diary is a multi-user environment to deal with the administration of Diary writing. The system includes modules for create user, registration, diary writing, reminder setting, photo gallery, calculator, user accounts and autobiography etc.
Various users of the system are…
• Administrators (the persons who has an account)
• Users (everyone who uses the diary)
This software can be used by different persons by using different user names and passwords. The person who has an account (administrators) can add daily notes, add photos, set reminders, write autobiography, add biodata etc. There is an advantage of classifying the photos which the administrator adds as private and public. By adding the photos as private the administrator who added the photo will only have the right to delete and the photos will be visible only to the administrator.
1.3 DOMAIN INFORMATION
C Sharp (programming language)
Paradigm
multi-paradigm: structured, imperative, object-oriented, event-driven, functional, generic
Appeared in 2001
Designed by Microsoft
Developer
Microsoft
Stable release
4.0 (April 12, 2010; 14 months ago)
Typing discipline
static, dynamic,[1] strong, safe, nominative
Major implementations
.NET Framework, Mono, DotGNU
Dialects
Cω, Spec#, Polyphonic C#
Influenced by Java,[2] C++,[3] Eiffel, Modula-3, Object Pascal[4]
Influenced D, F#, Java 5,[5] Nemerle, Vala
Platform
Common Language Infrastructure
License
CLR is proprietary, Mono compiler is dual GPLv3, MIT/X11 and libraries are LGPLv2, DotGNU is dual GPL and LGPLv2
Usual file extensions
.cs
Website C# Language (MSDN)
C# (pronounced see sharp) is a multi-paradigm programming language encompassing strong typing, imperative, declarative, functional, generic, object-oriented (class-based), and component-oriented programming disciplines. It was developed by Microsoft within its .NET initiative and later approved as a standard by Ecma (ECMA-334) and ISO (ISO/IEC 23270). C# is one of the programming languages designed for the Common Language Infrastructure.
C# is intended to be a simple, modern, general-purpose, object-oriented programming language. Its development team is led by Anders Hejlsberg. The most recent version is C# 4.0, which was released on April 12, 2010.
Features
See also: C Sharp syntax
Note: The following description is based on the language standard and other documents listed in the external links section.
By design, C# is the programming language that most directly reflects the underlying Common Language Infrastructure (CLI). Most of its intrinsic types correspond to value-types implemented by the CLI framework. However, the language specification does not state the code generation requirements of the compiler: that is, it does not state that a C# compiler must target a Common Language Runtime, or generate Common Intermediate Language (CIL), or generate any other specific format. Theoretically, a C# compiler could generate machine code like traditional compilers of C++ or Fortran.
Some notable distinguishing features of C# are:
• It has no global variables or functions. All methods and members must be declared within classes. Static members of public classes can substitute for global variables and functions.
• Local variables cannot shadow variables of the enclosing block, unlike C and C++. Variable shadowing is often considered confusing by C++ texts.
• C# supports a strict Boolean data type, bool. Statements that take conditions, such as while and if, require an expression of a type that implements the true operator, such as the boolean type. While C++ also has a boolean type, it can be freely converted to and from integers, and expressions such as if(a) require only that a is convertible to bool, allowing a to be an int, or a pointer. C# disallows this "integer meaning true or false" approach, on the grounds that forcing programmers to use expressions that return exactly bool can prevent certain types of common programming mistakes in C or C++ such as if (a = b) (use of assignment = instead of equality ==).
• In C#, memory address pointers can only be used within blocks specifically marked as unsafe, and programs with unsafe code need appropriate permissions to run. Most object access is done through safe object references, which always either point to a "live" object or have the well-defined null value; it is impossible to obtain a reference to a "dead" object (one which has been garbage collected), or to a random block of memory. An unsafe pointer can point to an instance of a value-type, array, string, or a block of memory allocated on a stack. Code that is not marked as unsafe can still store and manipulate pointers through the System.IntPtr type, but it cannot dereference them.
• Managed memory cannot be explicitly freed; instead, it is automatically garbage collected. Garbage collection addresses the problem of memory leaks by freeing the programmer of responsibility for releasing memory which is no longer needed.
• In addition to the try...catch construct to handle exceptions, C# has a try...finally construct to guarantee execution of the code in the finally block.
• Multiple inheritance is not supported, although a class can implement any number of interfaces. This was a design decision by the language's lead architect to avoid complication and simplify architectural requirements throughout CLI.
• C# is more type safe than C++. The only implicit conversions by default are those which are considered safe, such as widening of integers. This is enforced at compile-time, during JIT, and, in some cases, at runtime. No implicit conversions occur between booleans and integers, nor between enumeration members and integers (except for literal 0, which can be implicitly converted to any enumerated type). Any user-defined conversion must be explicitly marked as explicit or implicit, unlike C++ copy constructors and conversion operators, which are both implicit by default. Starting with version 4.0, C# supports a "dynamic" data type that enforces type checking at runtime only.
• Enumeration members are placed in their own scope.
• C# provides properties as syntactic sugar for a common pattern in which a pair of methods, accessor (getter) and mutator (setter) encapsulate operations on a single attribute of a class.
• Full type reflection and discovery is available.
• C# currently (as of version 4.0) has 77 reserved words.
• Checked exceptions are not present in C# (in contrast to Java). This has been a conscious decision based on the issues of scalability and versionability.