Professional Documents
Culture Documents
The present software application is related to maintain the records of the donors
who donated generously towards the great cause of our non-profit organization.
All these are to be automated and an application is required to relate all of them
relatively and logically so that the current system can be replaced and accepted
OBJECTIVE
The main objective of the application is to automate the existing system of manually
maintained records of the contributors of the non-profit organization along with other
valuable information like listing of pledged and unpledged donors.
Some major objectives are
SYSTEM SPECIFICATION
Hardware and Software requirements
Hardware Requirements
Processor
RAM
2GB RAM
Monitor
15 Color Monitor
Operating System
Windows XP/7/8
Developing Tool
MS Access
Software Requirements
the activity is defined somewhat differently. According to Taylor (2004) The life of the
project, he focuses all activities of the project life cycle including systems, product
development needs to create. Stage of development The Systems Development Life
Cycle (SDLC) in accordance with the main sections, which are necessary for the
developers, such as planning, analysis, design and implementation, and be in the next
section. Some existing systems development life-cycle model. The oldest model, which
was originally a system development life cycle, the Cascade model: a sequence of steps
of each phase output, the entry for next year. Steps generally follow the same basic
procedure, but different methods give different names and Kaskadenstufen like to change
the number of steps 4 to 7 is certainly a good example of the system development life
cycle, but the procedure can be characterized and in several different stages:
The different phases of the implementation of the project here is Business Process &
Requirements analysis Software Requirements Specifications
Design and Development Testing & Debugging Maintenance.
System Study
Preliminary system study is the first stage of system development life cycle. This is a
brief investigation of the system under consideration and gives a clear picture of what
actually the physical system is? In practice, the initial system study involves the
preparation of a System proposal which lists the Problem Definition, Objectives of the
Study, Terms of reference for Study, Constraints, Expected benefits of the new system,
etc. in the light of the user requirements. The system proposal is prepared by the System
Analyst (who studies the system) and places it before the user management.
The management may accept the proposal and the cycle proceeds to the next stage. The
management may also reject the proposal or request some modifications in the proposal.
In summary, we would say that system study phase passes through the following steps:
10
Feasibility Study
In case the system proposal is acceptable to the management, the next phase is to
examine the feasibility of the system. The feasibility study is basically the test of the
proposed system in the light of its workability, meeting users requirements, effective use
of resources and of course, the cost effectiveness. These are categorized as technical,
operational, economic, schedule and social feasibility. The main goal of feasibility study
is not to solve the problem but to achieve the scope. In the process of feasibility study, the
cost and benefits are estimated with greater accuracy to find the Return on Investment
(ROI). This also defines the resources needed to complete the detailed investigation. The
result is a feasibility report submitted to the management. This may be accepted or
accepted with modifications or rejected.
In short, following decision are taken in different feasibility study:
Economic feasibility - The likely benefits outweigh the cost of solving the
Detailed System
Study The detailed investigation of the system is carried out in accordance with the
objectives of the proposed system. This involves detailed study of various operations
performed by a system and their relationships within and outside the system. During this
11
process, data are collected on the available files, decision points and transactions handled
by the present system. Interviews, on-site observation and questionnaire are the tools
used for detailed system study. Using the following steps it becomes easy to draw the
exact boundary of the new system under consideration:
All the data and the findings must be documented in the form of detailed data flow
diagrams (DFDs), data dictionary, logical data structures and miniature specifications. It
includes planning for the new system, analysis of requirement, system constraints,
functions and proposed system architecture, prototype of the proposed system and its
analysis.
Errors removed, then system test is done. At this stage the test is done on
actual data. The complete system is executed on the actual data. At each stage of
the execution, the results or output of the system is analyzed. During the result
analysis, it may be found that the outputs are not matching the expected output of
the system. In such case, the errors in the particular programs are identified and
are fixed and further tested for the expected output. All independent modules be
brought together and all the interfaces to be tested between multiple modules, the
whole set of software is tested to establish that all modules work together
correctly as an application or system or package. When it is ensured that the
system is running error-free, the users are called with their own actual data so that
the system could be shown running as per their requirements.
12
2.2.5 Implementation
The project enters the implementation phase when the product is ready to be
Implemented/ piloted on the production environment and after thorough training to all the
end users the product is implemented after having the user acceptance of the new system
developed, the implementation phase begins. Implementation is the stage of a project
during which theory is turned into practice. The major steps involved in this phase are:
The hardware and the relevant software required for running the system must be made
fully operational before implementation. The conversion is also one of the most critical
and expensive activities in the system development life cycle. The data from the old
system needs to be converted to operate in the new format of the new system. The
database needs to be setup with security and recovery procedures fully defined. During
this phase, all the programs of the system are loaded onto the users computer. After
loading the system, training of the user starts. Main topics of such type of training are:
13
After the users are trained about the computerized system, working has to shift from
manual to computerized working. The process is called Changeover. The following
strategies are followed for changeover of the system.
1.
Failure of the computerized system at the early stage does not affect the
working of the organization, because the manual system continues to work, as it
used to do.
3.
Pilot run: In this type of run, the new system is run with the data from
one or more of the previous periods for the whole or part of the system. The
results are compared with the old system results. It is less expensive and risky
than parallel run approach. This strategy builds the confidence and the errors are
traced easily without affecting the operations. The documentation of the system is
also one of the most important activity in the system development life cycle. This
ensures the continuity of the system. Generally following two types of
documentations are prepared for any system. User or Operator Documentation
System Documentation
User Documentation: The user documentation is a complete description of the
system from the users point of view detailing how to use or operate the system. It
also includes the major error messages likely to be encountered by the user.
System Documentation: The system documentation contains the details of
system design, programs, their coding, system flow, data dictionary, process
14
description, etc. This helps to understand the system and permit changes to be
made in the existing system to satisfy new user needs.
15
Project Estimates:
The estimated time lines for completing the implementation of the application identified
and its approach is enumerated as below
Phase
Duration
in weeks
3
5 Implementation
16
2.5
18
Software developers and data architects can use Microsoft Access to develop application
software, and "power users" can use it to build software applications. Like other Office
applications, Access is supported by Visual Basic for Applications, an object-oriented
programming language that can reference a variety of objects including DAO (Data
Access Objects), ActiveX Data Objects, and many other ActiveX components. Visual
objects used in forms and reports expose their methods and properties in the VBA
programming environment, and VBA code modules may declare and call Windows
operating-system functions.
19
Uses
In addition to using its own database storage file, Microsoft Access also may be used as
the 'front-end' of a program while other products act as the 'back-end' tables, such as
Microsoft SQL Server and non-Microsoft products such as Oracle and Sybase. Multiple
backend sources can be used by a Microsoft Access Jet Database (accdb and mdb
formats). Similarly, some applications such as Visual Basic, ASP.NET, or Visual
Studio .NET will use the Microsoft Access database format for its tables and queries.
Microsoft Access may also be part of a more complex solution, where it may be
integrated with other technologies such as Microsoft Excel, Microsoft Outlook, Microsoft
Word, Microsoft PowerPoint and ActiveX Controls.
Access tables support a variety of standard field types, indices, and referential integrity
including cascading updates and deletes. Access also includes a query interface, forms to
display and enter data, and reports for printing. The underlying Jet database, which
contains these objects, is multiuser-aware and handles record-locking.
Repetitive tasks can be automated through macros with point-and-click options. It is also
easy to place a database on a network and have multiple users share and update data
without overwriting each other's work. Data is locked at the record level which is
significantly different from Excel which locks the entire spreadsheet.
There are template databases within the program and for download from their website.
These options are available upon starting Access and allow users to enhance a database
with predefined tables, queries, forms, reports, and macros. Database templates support
VBA code but Microsoft's templates do not include VBA code.
Programmers can create solutions using the programming language Visual Basic for
Applications (VBA), which is similar to Visual Basic 6.0 (VB6) and used throughout the
Microsoft Office programs such as Excel, Word, Outlook and PowerPoint. Most VB6
code, including the use of Windows API calls, can be used in VBA. Power users and
developers can extend basic end-user solutions to a professional solution with advanced
automation, data validation, error trapping, and multi-user support.
The number of simultaneous users that can be supported depends on the amount of data,
the tasks being performed, level of use, and application design. Generally accepted limits
are solutions with 1 GB or less of data (Access supports up to 2 GB) and performs quite
20
well with 100 or fewer simultaneous connections (255 concurrent users are supported).
This capability is often a good fit for department solutions. If using an Access database
solution in a multi-user scenario, the application should be "split". This means that the
tables are in one file called the back end (typically stored on a shared network folder) and
the application components (forms, reports, queries, code, macros, linked tables) are in
another file called the front end. The linked tables in the front end point to the back end
file. Each user of the Access application would then receive his or her own copy of the
front end file.
Applications that run complex queries or analysis across large datasets would naturally
require greater bandwidth and memory. Microsoft Access is designed to scale to support
more data and users by linking to multiple Access databases or using a back-end database
like Microsoft SQL Server. With the latter design, the amount of data and users can scale
to enterprise-level solutions.
Microsoft Access's role in web development prior to version 2010 is limited. User
interface features of Access, such as forms and reports, only work in Windows. In
versions 2000 through 2003 an Access object type called Data Access Pages created
publishable web pages. Data Access Pages are no longer supported. The Microsoft Jet
Database Engine, core to Access, can be accessed through technologies such as ODBC or
OLE DB. The data (i.e., tables and queries) can be accessed by web-based applications
developed in ASP.NET, PHP, or Java. With the use of Microsoft's Terminal Services and
Remote Desktop Application in Windows Server 2008 R2, organizations can host Access
applications so they can be run over the web. This technique does not scale the way a
web application would but is appropriate for a limited number of users depending on the
configuration of the host.
Access 2010 allows databases to be published to SharePoint 2010 web sites running
Access Services. These web-based forms and reports run in any modern web browser.
The resulting web forms and reports, when accessed via a web browser, don't require any
add-ins or extensions (e.g. ActiveX, Silver light).
Access 2013 can create web applications directly in SharePoint 2013 sites running Access
Services. Access 2013 web solutions store its data in an underlying SQL Server database
21
which is much more scalable and robust than the Access 2010 version which used
SharePoint lists to store its data.
A compiled version of an Access database (File extensions: .MDE /ACCDE or .ADE;
ACCDE only works with Access 2007 or later) can be created to prevent user from
accessing the design surfaces to modify module code, forms, and reports. An
MDE/ACCDE file is a Microsoft Access database file with all modules compiled and all
editable source code removed. An ADE file is an Access project file with all modules
compiled and all editable source code removed. Both the .MDE/ACCDE and .ADE
versions of an Access database are used when end-user modifications are not allowed or
when the applications source code should be kept confidential.
Microsoft also offers developer extensions for download to help distribute Access 2007
applications, create database templates, and integrate source code control with Microsoft
Visual SourceSafe.
Features
Users can create tables, queries, forms and reports, and connect them together with
macros. Advanced users can use VBA to write rich solutions with advanced data
manipulation and user control. Access also has report creation features that can work with
any data source that Access can access.
The original concept of Access was for end users to be able to access data from any
source. Other features include: the import and export of data to many formats including
Excel, Outlook, ASCII, dBase, Paradox, FoxPro, SQL Server, Oracle, ODBC, etc. It also
has the ability to link to data in its existing location and use it for viewing, querying,
editing, and reporting. This allows the existing data to change while ensuring that Access
uses the latest data. It can perform heterogeneous joins between data sets stored across
different platforms. Access is often used by people downloading data from enterprise
level databases for manipulation, analysis, and reporting locally.
There is also the Jet Database format (MDB or ACCDB in Access 2007) which can
contain the application and data in one file. This makes it very convenient to distribute
the entire application to another user, who can run it in disconnected environments.
22
23
Microsoft Access
Excel
SharePoint lists
Plain text
XML
Outlook
HTML
Lotus 1-2-3
Development
Access stores all database tables, queries, forms, reports, macros, and modules in the
Access Jet database as a single file.
For query development, Access offers a "Query Designer", a graphical user interface that
allows users to build queries without knowledge of structured query language. In the
Query Designer, users can "show" the data sources of the query (which can be tables or
queries) and select the fields they want returned by clicking and dragging them into the
grid. One can set up joins by clicking and dragging fields in tables to fields in other
tables. Access allows users to view and manipulate the SQL code if desired. Any Access
table, including linked tables from different data sources, can be used in a query.
25
Access also supports the creation of "pass-through queries". These snippets of SQL code
can address external data sources through the use of ODBC connections on the local
machine. This enables users to interact with data stored outside the Access program
without using linked tables or Jet. Users construct the pass-through queries using the SQL
syntax supported by the external data source.
When developing reports (in "Design View") additions or changes to controls cause any
linked queries to execute in the background and the designer is forced to wait for records
to be returned before being able to make another change. This feature cannot be turned
off.
Non-programmers can use the macro feature to automate simple tasks through a series of
drop-down selections. Macros allow users to easily chain commands together such as
running queries, importing or exporting data, opening and closing forms, previewing and
printing reports, etc. Macros support basic logic (IF-conditions) and the ability to call
other macros. Macros can also contain sub-macros which are similar to subroutines. In
Access 2007, enhanced macros included error-handling and support for temporary
variables. Access 2007 also introduced embedded macros that are essentially properties
of an object's event. This eliminated the need to store macros as individual objects.
However, macros were limited in their functionality by a lack of programming loops and
advanced coding logic until Access 2013. With significant further enhancements
introduced in Access 2013, the capabilities of macros became fully comparable to VBA.
They made feature rich web-based application deployments practical, via a greatly
enhanced Microsoft SharePoint interface and tools, as well as on traditional Windows
desktops.
In common with other products in the Microsoft Office suite, the other programming
language used in Access is Microsoft VBA Visual Basic for Applications. VBA is similar
to Visual Basic 6.0 (VB6) and code can be stored in modules, classes, and code behind
forms and reports. To create a richer, more efficient and maintainable finished product
with good error handling, most professional Access applications are developed using the
VBA programming language rather than macros, except where web deployment is a
business requirement.
26
27
To manipulate data in tables and queries in VBA or macros, Microsoft provides two
database access libraries of COM components:
1
Data Access Objects (DAO) (32-bit only), which is included in Access and
Windows and evolved to ACE in Microsoft Access 2007 for the ACCDE database
format
ActiveX Data Objects ActiveX Data Objects (ADO) (both 32-bit and 64-bit
versions)
As well as DAO and ADO, developers can also use OLE DB and ODBC for developing
native C/C++ programs for Access. For ADPs and the direct manipulation of SQL Server
data, ADO is required. DAO is most appropriate for managing data in Access/Jet
databases, and the only way to manipulate the complex field types in ACCDB tables.
In the database container or navigation pane in Access 2007 and later versions, the
system automatically categorizes each object by type (e.g., table, query, macro). Many
Access developers use the Leszynski naming convention, though this is not universal; it
is a programming convention, not a DBMS-enforced rule. It is particularly helpful in
VBA where references to object names may not indicate its data type (e.g. tbl for tables,
qry for queries).
Developers deploy Microsoft Access most often for individual and workgroup projects
(the Access 97 speed characterization was done for 32 users). Since Access 97, and with
Access 2003 and 2007, Microsoft Access and hardware have evolved significantly.
Databases under 1 GB in size (which can now fit entirely in RAM) and 50 simultaneous
users are well within the capabilities of Microsoft Access. Of course, performance
depends on the database design and tasks. Disk-intensive work such as complex
searching and querying take the most time.
28
As data from a Microsoft Access database can be cached in RAM, processing speed may
substantially improve when there is only a single user or if the data are not changing. In
the past, the effect of packet latency on the record-locking system caused Access
databases to run slowly on a Virtual Private Network (VPN) or a Wide Area Network
(WAN) against a Jet database. As of 2010 broadband connections have mitigated this
issue. Performance can also be enhanced if a continuous connection is maintained to the
back-end database throughout the session rather than opening and closing it for each table
access. If Access database performance over VPN or WAN suffers, then a client using
Remote Desktop Protocol (such as Microsoft Terminal Services) can provide an effective
solution. Access databases linked to SQL Server or to Access Data Projects work well
over VPNs and WANs.
In July 2011, Microsoft acknowledged an intermittent query performance problem with
all versions of Access and Windows 7 and Windows Server 2008 R2 due to the nature of
resource management being vastly different in newer operating systems. This issue
severely affects query performance on both Access 2003 and earlier with the Jet Database
Engine code, as well as Access 2007 and later with the Access Database Engine (ACE).
Microsoft has issued hotfixes KB2553029 for Access 2007 and KB2553116 for Access
2010, but will not fix the issue with Jet 4.0 as it is out of mainstream support.
In previous versions of Microsoft Access the ability to distribute applications required the
purchase of the Developer Toolkit; in Access 2010 and Access 2013 the "Runtime Only"
version is offered as a free download, making the distribution of royalty-free applications
possible on Windows 7 and Windows 8.x.
copy of Microsoft Access (or the runtime version) installed on their machine along with
their application database. This reduces network traffic since the application is not
retrieved for each use. The "front-end" database can still contain local tables for storing a
user's settings or temporary data. This split-database design also allows development of
the application independent of the data. One disadvantage is that users may make various
changes to their own local copy of the application and this makes it hard to manage
version control. When a new version is ready, the front-end database is replaced without
impacting the data database. Microsoft Access has two built-in utilities, Database Splitter
and Linked Table Manager, to facilitate this architecture.
Linked tables in Access use absolute paths rather than relative paths, so the development
environment either has to have the same path as the production environment or a
"dynamic-linker" routine can be written in VBA.
For very large Access databases, this may have performance issues and a SQL backend
should be considered in these circumstances. This is less of an issue if the entire database
can fit in the PC's RAM since Access caches data and indexes.
Yes/True (-1). The corresponding SQL Server data type is binary, with only two states,
permissible values, zero and 1. Regardless, SQL Server is still the easiest migration, and
most appropriate especially if the user does not have rights to create objects such as
stored procedures on SQL Server. Retrieving data from linked tables is optimized to just
the records needed, but this scenario may operate less efficiently than what would
otherwise be optimal for SQL Server. For example, in instances where multi-table joins
still require copying the whole table across the network. In previous versions of Access,
including Access 2010, databases can also be converted to Access Data Projects (ADP)
which are tied directly to one SQL Server database. This feature was removed from
Access 2013. ADP's support the ability to directly create and modify SQL Server objects
such as tables, views, stored procedures, and SQL Server constraints. The views and
stored procedures can significantly reduce the network traffic for multi-table joins.
Fortunately, SQL Server supports temporary tables and links to other data sources beyond
the single SQL Server database. Finally, some Access databases are completely replaced
by another technology such as ASP.NET or Java once the data is converted. However any
migration may dictate major effort since the Access SQL language is a more powerful
superset of standard SQL. Further, Access application procedures, whether VBA and
macros, are written at a relatively higher level versus the currently available alternatives
that are both robust and comprehensive. Note that the Access macro language, allowing
an even higher level of abstraction than VBA, was significantly enhanced in Access 2010
and again in Access 2013.In many cases, developers build direct web-to-data interfaces
using ASP.NET, while keeping major business automation processes, administrative and
reporting functions that don't need to be distributed to everyone in Access for information
workers to maintain. While all Access data can migrate to SQL Server directly, some
queries cannot migrate successfully. In some situations, you may need to translate VBA
functions and user defined functions into TSQL or .NET functions / procedures.
Crosstab queries can be migrated to SQL Server using the PIVOT command.
31
Protection
Microsoft Access offers several ways to secure the application while allowing users to
remain productive. The most basic is a database password. Once entered, the user has full
control of all the database objects. This is a relatively weak form of protection which can
be easily cracked. A higher level of protection is the use of workgroup security requiring
a user name and password. Users and groups can be specified along with their rights at
the object type or individual object level. This can be used to specify people with readonly or data entry rights but may be challenging to specify. A separate workgroup
security file contains the settings which can be used to manage multiple databases.
Workgroup security is not supported in the Access 2007 and Access 2010 ACCDB
database format, although Access 2007 and Access 2010 still support it for MDB
databases. Databases can also be encrypted. The ACCDB format offers significantly
advanced encryption from previous versions. Additionally, if the database design needs to
be secured to prevent changes, Access databases can be locked/protected (and the source
code compiled) by converting the database to a .MDE file. All changes to the VBA
project (modules, forms, or reports) need to be made to the original MDB and then
reconverted to MDE. In Access 2007 and Access 2010, the ACCDB database is converted
to an ACCDE file. Some tools are available for unlocking and "decompiling", although
certain elements including original VBA comments and formatting are normally
irretrievable.
32
File extensions
Microsoft Access saves information under the following file formats:
File format
Extensio
n
.ade
.adp
.adn
.accdb
.accdr
.accdt
.accda
.mdb
.cdb
.mda
workgroups (2).
Access Blank Database Template (2003 and earlier)
Access Add-in Data (2003 and earlier)
Access Workgroup, database for user-level security.
Access (SQL Server) detached database (2000)
Protected Access Database, with compiled VBA and/or macros (2003 and
.mdn
.mdt
.mdw
.mdf
.mde
earlier)
Protected Access Database, with compiled VBA and/or macros (2007)
Windows Shortcut: Access Macro
Windows Shortcut: Access Query
Windows Shortcut: Access Report
Windows Shortcut: Access Table
Windows Shortcut: Access Form
Access lock files (associated with .mdb)
Access lock files (associated with .accdb)
.accde
.mam
.maq
.mar
.mat
.maf
.ldb
.laccdb
Versions
Version
Version
Release
Jet
numbe
Date
version
Supported OS
Office suite
version
r
33
Access 1.1
Access 2.0
Access for
1.0
2.0
7.0
1992
1993
Aug.
Windows
24,
95
Access 97
1995
Jan. 16,
8.0
1.1
2.0
3.0
9.0
2000
Access
3.5
10.0
11.0
2007
Nov. 27,
Jan. 27,
2007
Windows NT 3.51
Professional and
SP5, Windows NT
Developer
12
Office 2000
Windows NT 4.0,
Professional,
Windows 98,
Premium and
Developer
Office XP
Professional and
Windows 2000,
Developer
Windows Me
4.0 SP1 Windows 2000
2003
12.0
Office 97
Windows 2000
4.0 SP1 Windows NT 4.0
2001
2003
Access
May 31,
Windows 95,
4.0 SP2
4.0 SP1 Windows 95,
1999
2002
Access
June 7,
1997
Access
Windows 3.0
Windows 3.1x
Windows 95
Office 2003
SP3 or later,
Professional and
Windows XP,
Professional
Windows Vista,
Enterprise
Windows 7
Windows XP SP2,
Office 2007
Windows Server
Professional,
2003 SP1, or
Professional Plus,
newer operating
Ultimate and
system
Enterprise
34
Notes
There are no Access versions between 2.0 and 7.0 because the Office 95 version
was launched with Word 7. All of the Office 95 products have OLE 2 capabilities,
and Access 7 shows that it was compatible with Word 7.
Version number 13 was skipped.
Microsoft Access has been around for some time, yet people often still ask me what is
Microsoft Access and what does it do? Microsoft Access is a part of the Microsoft Office
Suite. It does not come with all versions of Microsoft Office, so if you specifically want
Microsoft Access make sure the office suite you are purchasing has it. Microsoft Access
has the look and feel of other Microsoft Office products, including its layout and
navigational aspects. That is where the similarity ends. Microsoft Access is a database
and, more specifically, a relational database. This will be explained in more detail later.
Access has an .mdb extension by default, whereas Microsoft Word has the .doc
extension. Although this has changed in Access 2007 where the extension is now an
accdb extension. Early versions of Access cannot read accdb extensions but Microsoft
Access 2007 can read and change earlier versions of Access. The above is a bried
overview of what is Microsoft Access. Now lets look at it in a bit more detail. What is
Microsoft Access made up of?
The Microsoft Access Database is made up of 7 major components:
Tables;
Relationships;
Queries;
Forms;
Reports;
Macros;
Modules.
35
2.5.2Tables
The tables are the backbone and the storage container of the data entered into the
database. If the tables are not set up correctly, with the correct relationships, then the
database may be slow, give you the wrong results or not react the way you expect. So,
take a bit of time when setting up your tables. Queries, forms, etc. are usually based on a
table. The tables that contain data look a bit like a table in Microsoft Word or a
Microsoft Excel Spreadsheet, when opened. They have columns and rows as does a
table in Microsoft Word and an Excel worksheet. Each of the columns will have a field
name at the top and each of the rows will represent a record.
As an example:
36
2.5.3 Forms
Forms are the primary interface through which the users of the database enter data. The
person who enters the data will interact with forms regularly. The programmer can set the
forms to show only the data required. By using queries, properties, macros and VBA
(Visual Basic for Applications), the ability to add, edit and delete data can also be set.
Forms can be set up and developed to reflect the use they will be required for.
2.5.4Reports
Reports are the results of the manipulation of the data you have entered into the database.
Unlike forms, they cannot be edited. Reports are intended to be used to output data to
another device or application, i.e. printer, fax, Microsoft Word or Microsoft Excel.
2.5.5 Relationships
Relationships are the bonds you build between the tables. They join tables that have
associated elements. To do this there is a field in each table, which is linked to each other,
and have the same values.
2.5.6Queries
Queries are the means of manipulating the data to display in a form or a report. Queries
can sort, calculate, group, filter, join tables, update data, delete data, etc. Their power is
immense. The Microsoft Access database query language is SQL (Structured Query
Language). The need to know SQL is not required in the early stages of learning Access.
Microsoft Access writes the SQL for you, after you tell it what you want, in the Design
view of the queries window.
2.5.7Macros
Macros are an automatic way for Access to carry out a series of actions for the database.
Access gives you a selection of actions that are carried out in the order you enter. Macros
can open forms; run queries, change values of a field, run other Macros, etc. the list is
almost endless.
37
2.5.8Modules : Modules are the basis of the programming language that supports
Microsoft Access, The module window is where you can write and store Visual Basic
for Applications (VBA). Advanced users of Microsoft Access tend to use VBA instead
of Macros.
38
39
40
Pledges Table
41
42
Contributors Form
43
44
45
46
ER-DIAGRAM
48
49
50
Typed of Testing
Regression Testing.
Re-Testing.
Static Testing.
Dynamic Testing.
Alpha Testing
Regression Testing: It is one of the best and important testing. Regression testing is
the process in which the functionality, which is already tested before, is once again tested
whenever some new change is added in order to check whether the existing functionality
remains same.
Re-Testing: It is the process in which testing is performed on some functionality
which is already tested before to make sure that the defects are reproducible and to rule
out the environments issues if at all any defects are there.
51
Normal data
This is the correct and valid data that was input into the database. The system accepted
the data and updated the tables appropriately. The following is an example of normal data
entered without any error.
52
53
Exceptional data
The system analyst used invalid data to test whether the system obeyed the syntax of the
program.
The following is an example of exceptional data used by the analyst:
Exceptional data from accommodation form. When an data that is not part of the
list in the record is entered, the system displays the following error message:
GENERAL INFORMATION
Test Stage:
Unit
Functionality
System
Integration
Interface
Performance
Regression
Acceptance
Pilot
Specify the testing stage for this test case.
Test Date:
01/11/2014
System Date, if
01/11/2014
applicable:
Tester:
Test Case
TD_COD_CL02
Number:
Test Case
Description:
Results:
Pass
Fail
Incident Number, NA
if applicable:
INTRODUCTION
Requirement(s)
Want to check whether the project accept suitable value or not like
to be tested:
Roles and
Divya Sharma and Mr. Manpreet Singh responsible for this test.
Responsibilities
:
Here Divya Sharma enters the value and Mr. Manpreet Singh check
the output of such value.
ENVIRONMENTAL NEEDS
Hardware:
Software:
Ms access 2007
TEST
All ms access forms have been tested under this test case regarding
Features:
Input
All mentioned things were required that appear on the screen like to
55
Specifications:
Expected
Results of
happens too.
Case:
ACTUAL RESULTS
Output
Specifications:
validating the input it works and indicates that we are trying to give
wrong input and it ask for right input as we amend our mistake and
give right input and according our hoped output was accurate.
56
GENERAL INFORMATION
Test Stage:
Unit
Functionality
System
Integration
Interface
Performance
Regression
Acceptance
Pilot
Specify the testing stage for this test case.
Test Date:
03/11/2014
System Date, if
03/11/2014
applicable:
Tester:
Test Case
TD_COD_CL01
Number:
Test Case
Description:
Results:
Pass
Fail
Incident Number, NA
if applicable:
INTRODUCTION
Requirement(s)
Want to check whether the all ms access forms provides better and
to be tested:
Roles and
Mr. Manpreet Singh and Vishal Shrimal responsible for this test.
Responsibilities
:
Here Vishal Shrimal runs all forms and Mr. Manpreet Singh check
the output of that form.
ENVIRONMENTAL NEEDS
Hardware:
Software:
MS ACCESS 2007
TEST
57
All MS ACCESS forms has been tested under this test case
Features:
Input
Specifications:
Expected
Results of
happens too.
Case:
ACTUAL RESULTS
Output
Specifications:
not. And also to check all linking that done in the project will work
correctly or not.
58
Unit
Functionality
System
Integration
Interface
Performance
Regression
Acceptance
Pilot
Specify the testing stage for this test case.
Test Date:
27/10/2014
System Date, if
27/10/2014
applicable:
Tester:
Riddhima Babbar
Test Case
TD_COD_CL03
Number:
Test Case
Check all connectivity and data base validity and existence and
Description:
Results:
Pass
Fail
Incident Number, NA
if applicable:
INTRODUCTION
Requirement(s)
Want to check whether the database and table used in the project are
to be tested:
Roles and
Responsibilities
this test.
Hardware:
Software:
MS ACCESS 2007.
TEST
59
All database connectivity code will be test under this test case.
Features:
Input
Give all details that appear on the screen and check that the data
Specifications:
Expected
Results of
happens too.
Case:
ACTUAL RESULTS
Output
We check that all data flows rightly between our system and
Specifications:
5.1 Conclusion:
60
61
5.2 Limitations:
1. Database systems are complex, difficult, and time-consuming to design.
2. Damage to database affects virtually all applications programs.
3. Substantial hardware and software start-up costs.
4. Initial training required for all programmers and users.
5. Minimum hardware and software required.
6. As we have included many features and too much user handling, the expected
code could be complex and not easy to improve by another programmer.
7. The system will undergo system entropy hence an extra cost of updating will be
incurred to keep the system competitive in the ICT and BUSINESS world.
8. The customer service management system will incur an extra cost on the
electricity and internet bills due to computerization of the Donations Management
System.
9. The company will be required to train its employees on how to manage the system
hence the output capacity will reduce a bit during this period.
62
63
5.4 Bibliography:
1. Davinder Singh Minhas, Drag and Drop MS access 2007, Sterling publishers pvt.
Ltd, 2007
2. Advanced database projects in Access 2007,Julian Mott, Hodder education, 2009
3. The complete reference, Microsoft office access 2007 Virginia Anderson
4. Pressman, R.S., Software Engineering: A Practitioners Approach, McGraw Hill
Int. S Student Ed., 6th Ed., 2005
5. Sommerville, I., Software Engineering, Pearson Education, 6th ed., 2001
6. Jalote, P., An Integrated Approach to Software Engineering, 2nd ed., Narosa, 1998
7. Behforooz, A. and F. Hudson, Fundamentals of Software Engineering, Oxford
University Press, 1996
Websites:
http://en.wikipedia.org/wiki/Microsoft_Access
https://www.housing.wisc.edu/docs/tlc_quicktip_access.pdf
www.simply-access.com/What-Is-Microsoft-Access.html
64
A-1
SCREEN SHOTS
Campaign Summary Report
65
66
2. Unpaid Pledges
67
Switchboard Manager
68
Forms output
1. Contributors
69
70