Professional Documents
Culture Documents
SYSTEM
Supervisor
Mr. Munshif
03rd.02.2015
PDIE/ MP
Declaration
I hereby declare that the project work entitled by under the guidance and Supervision of,
Mr. Munshif Cassim Bsc, Member of the Research center of the Bcas Kandy
Campus.
Mr. Mohamed Nuzrath Bsc, Senior Lecture of the Bcas Kandy Campus.
.
The Started time of the project,
And these project are my own creativity and thinking, I have collected information from the
internet and some other books. I think this could be a good project according to my future
career.
This project work is submitted in the partial fulfillment of the requirements for the award of
the Advanced Diploma of Technology in Computer System. The results embodied in this
thesis have not been submitted to any other University or Institute for the award of any
degree or diploma.
Acknowledgment
First of all I would like to express our heartful thanks to God for this opportunity, which he
rendered to us and gives the physical strength and pleasant mind to complete this project
work as success.
Then of all Ill thanks to Mr. Mohamed Niwas Director of the BCAS Kandy Campus. To give
this great opportunity to complete my HND Programme without any confusion. Then my
sincere gratitude to whole Administrative and IT Department of Bcas Kandy Campus for
their constant encouragements.
I also thanks to Mr. Mohamed Nuzrath, Senior Lecture of the Bcas Kandy Campus. He is
the only person give the idea and the fact about the system. And Sincere thanks to the
individuals that participated in my research Mr. Munshif Cassim. And he was helped to
develop my system as possible.
Who all encourage and satisfy my needs to finish this project work. I am very happy to thank
our Coordinator of the Bcas Kandy Campus, and other lectures giving a well-equipped for
developing this project work. I extent my thanks and gratitude my parents, Friends those
who helped me directly and indirectly for the successful completion of this project work.
Table of Contents
1. Abstract 16
1.1. Content Summery .. 16
1.1.1. Scope .. 16
1.1.2. Schedule .. 16
1.1.3. Costs 16
2. Introduction 17 - 21
2.1. Project Background .. 17
2.1.1. Project Documentation . 17
2.1.2. Software Engineering Principles . 17
3. Literature Review . 22 - 29
3.1.1. Abstract .. 22
3.1.2. Rationale of the Research .. 22
3.1.3. Systematic Literature Review Process . 23 - 24
3.1.3.1. Formal Definition 23
3.1.3.2. Motivation & Benefits .... 23
3.1.3.3. The Process 23 - 24
4. Analysis .. 30 - 46
4.1.1. Meaning of Analysis . 30
4.1.2. Importance of Analysis . 30
4.6. Specification .. 45 - 46
4.6.1. Functional Requirements 45
4.6.1.1. Main Function of the System 45
4.6.1.2. Some Other Requirements ... 45
4.6.2. Non Functional Requirements . 46
5. Design . 47 - 62
5.1. Work Breakdown Structure and Task Allocation . 47 - 49
5.1.1. Purpose .. 47
5.1.2. Process ... 47
5.1.3. WBS Task Allocation 49
5.5. ER Diagram . 61
List of Figures
1. Figure 1.1 Systematic Literature Review Process Flowchart 24
2. Figure 4.1.1 ElDorado Management System Registration . 32
3. Figure 4.1.2 ElDorado Management System Blood Ordering 33
4. Figure 4.1.3 ElDorado Management System ER Diagram . 34
5. Figure 4.2.1 Feasibility Studies 1 37
6. Figure 4.2.2 Feasibility Studies 2 37
7. Figure 4.2.3 Feasibility Studies 3 38
8. Figure 4.4.1 GSM Network .. 43
9. Figure 5.2.1 Splash Screen of System .. 51
10. Figure 5.2.2 Login for Administrator .. 51
11. Figure 5.2.3 Main Window of System 52
12. Figure 5.2.4 Menu Strip Tool of the Main Window .. 52
13. Figure 5.2.5 Button with Icon .. 52
14. Figure 5.2.6 Blood Donor Registration Form 53
15. Figure 5.2.7 Maintaining Blood Donors . 53
16. Figure 5.2.8 Sending SMS to Donors 54
17. Figure 5.2.9 Create New Admin and User 54
18. Figure 5.2.10 Create New Events .. 55
19. Figure 5.2.11 Search Donors .. 55
20. Figure 6.1.1 Waterfall Model ... 64
21. Figure 6.1.2 Iteration Model . 66
22. Figure 6.1.3 V-Shaped Model . 67
23. Figure 6.1.4 Spiral Model . 68
24. Figure 6.1.5 Extreme XP Release Cycle ... 69
25. Figure 6.4.1 Sample User Manual . 76
26. Figure 8.4.1 Principle of Software Project Quality Factors 103
27. Figure 8.4.2 Module Testing Activity . 104
28. Figure 9.4.1 Run the Blood Donor Information System .. 117
29. Figure 9.4.2 Incorrect Username and Password . 118
30. Figure 9.4.3 Correct Username and Password 118
31. Figure 9.4.4 Donor Registration Window .. 119
32. Figure 9.4.5 Message Box of Donor Registration 119
33. Figure 9.4.6 Selecting the Donor ID .. 120
34. Figure 9.4.7 Delete the Current Blood Donor .. 120
35. Figure 9.4.8 Confirmation Message for Deleted . 120
36. Figure 9.4.9 Edit or Update Blood Donor Details 121
37. Figure 9.4.10 Edit the Blood Donor Details . 121
38. Figure 9.4.11 Create New Events . 122
List of Tables
1. Table 4.3.1 Issues for Project Management Success 42
2. Table 4.4.1 PC Specification .. 44
3. Table 4.4.2 Server Specification 44
4. Table 5.5.1 WBS Task Matrix . 49
5. Table 8.1 SDLC Compliance Matrix . 77
6. Table 8.2 SDLC Compliance Matrix .. 78
7. Table 8.1.1.1 Advantages & Disadvantages of Black Box Testing .. 79
8. Table 8.1.1.2 Advantages & Disadvantages of White Box Testing .. 80
9. Table 8.1.1.3 Advantages & Disadvantages of Grey Box Testing 81
10. Table 8.1.1.4 Deferent Between Testing Methods . 81
11. Table 8.1.2.1 Test Case for Login Validation .. 82
12. Table 8.1.2.2 Test Case for Donor Registration . 83
13. Table 8.1.2.3 Test Case for Update Donor Details . 84
14. Table 8.1.2.4 Test Case for Delete Donor Details .. 85
15. Table 8.1.2.5 Test Case for Sending SMS .. 86
16. Table 8.1.2.6 Test Case for Report View . 87
17. Table 8.1.2.7 Test Case for Create Admin & User . 88
18. Table 8.1.2.8 Test Case for Creating New Event ... 89
19. Table 8.1.2.9 Test Case for Search Blood Donors .... 90
20. Table 8.1.3.1 Test Case for Login . 91
21. Table 8.1.3.2 Test Case for Donor Registration . 92
22. Table 8.1.3.2.1 Test Case for Donor Registration Error Correction . 92
23. Table 8.1.3.3 Test Case for Donor Maintaining . 93
24. Table 8.1.3.3.1 Test Case for Donor Maintaining Error Correction . 93
25. Table 8.1.3.4 Test Case for Sending SMS . 94
26. Table 8.1.3.4.1 Test Case for Sending SMS Error Correction . 94
27. Table 8.1.3.5 Test Case for Report View 95
28. Table 8.1.3.6 Test Case for Create Admin & User 96
29. Table 8.1.3.6.1 Test Case Create Admin & User Error Correction . 96
30. Table 8.1.3.7 Test Case for Creating New Events 97
31. Table 8.1.3.7.1 Test Case for Creating New Events Error Correction 97
32. Table 8.1.3.8 Test Case for Search Blood Donors 98
33. Table 8.2.1.1 Budgeted Cost for Work Schedule .................... 99
34. Table 8.2.2.1 Budgeted Cost for Work Performed................... 100
35. Table 8.3.1.1 Change of Schedule .. 101
List of Acronyms
AC Actual Cost
ACWP Actual Cost of Work Performed
AD Activity Description
ADM Arrow Diagramming Method
ACML AMD Core Math Library
AMD Advanced Micro Devices
API Application Programming Interface
APPML AMD Accelerated Processing Math Libraries
APU Accelerated Processing Unit
BAC Budget at Completion
BCWP Budgeted Cost of Work Performed
BCWS Budgeted Cost of Work Scheduled
CentOS Community Enterprise Operating System
CVS Concurrent Versioning System / Concurrent Versions System
CVSQL Concurrent Versioning System Structured Query Language
COTS Commercial off the Shelf
CPU Central Processing Unit
COQ Cost of Quality
CPF Cost-Plus-Fee
CPFF Cost-Plus-Fixed-Fee
CPI Cost Performance Index
CPIF Cost-Plus-Incentive-Fee
CPM Critical Path Method
CPPC Cost-Plus-Percentage of Cost
CV Cost Variance
Abstract
Blood Donor Information System is to create a Computerized Information about the donor
and Hospitals that are related to donating the blood. Through this System any person who is
interested in donating the blood can register himself in the same way, if any hospitals wants
to register itself with this System that can also register. And the purpose of my System is
registering blood donors, and maintain their details. Not only had those things, using my
system easily contact the donors in a critical or emergency situation. Because this system
giving more features to the clients or the hospitals or the blood camp groups.
And I have gathered some information in the internet and some ideas given by the project
supervisors. And this Project Document will cover each Stages of the System Development
Life Cycle (SDLF), and some other important objectives, scope, and motivation of the
project.
Computerized systems as compared to Paper record Systems are time consuming,
laborious, and costly. This paper introduces the review of the main features, merits and
demerits provided by the existing Computer-Based Information System for Blood Banks.
This study shows the comparison of various existing system and providing some more idea
about the computerized system.
Introduction
Blood is universally recognized as the most precious element that sustains life. It saves
innumerable lives across the world in a variety of conditions. A blood bank is a place
designed especially for the storage of blood and blood products. The term "blood bank"
typically refers to a division of a hospital laboratory where the storage of blood product
occurs and where proper testing is performed to reduce the risk of transfusion related
events. Large coolers hold these products at a constant temperature and they are available
at a moment's notice. The blood donor information system offers functionalities to quick
access to register the donor, and collected donor details from various parts of the Provinces.
It enables monitoring of the results and performance of the blood donation activity such that
relevant and measurable objectives of the organization can be checked. In my system Im
providing the efficient search who needs the blood in their own city, name, and blood groups
as fast as possible.
Blood Bank or the Hospital accept the donated blood, only if donor satisfy all of the following
conditions.
Project Documentation
Project Documentation or the Report will give the brief idea about the system which has
been developed by the developers. In the project documentation contain many facts, such
as software development life cycle and each stages, I mean explanation of each stages or
phase and etc.
For get more details of software engineering principles, please visit to this site.
http://www.d.umn.edu/~gshute/softeng/principles.html
To computerize all details regarding blood donor details & events details.
To automate the process of sending SMS selecting via district.
To maintain records effectively.
To manage current blood group of the donors and maintaining new events.
The project has information regarding the fresh blood donors, already registered
blood donor details, events, creating new events details and sending SMS to already
registered blood donors in the system.
Creating New Admin and Users for the System, only from admin privilege.
The valuable data can be keep as secure.
Creating new events to display about when next blood camp? , and where?
Specific
Measurable
Agreed Upon
Realistic
Time Bound
2. Table of Contents
The table of contents lists the various sections of the report in logical order.
3. Introduction
The introduction presents the problem at hand. That is the purpose of analysis or
experiment.
Many times the introduction presents what others have done in the area of concern, what
has and has not worked well; references to previous work is appropriate in this section.
4. Theory/Literature Review
This section identifies the methodology upon which the analysis or experiment is based.
8. References
The references should be complete and follow Harvard formats.
9. Appendices
The appendices may contain large sets of tabular data, detailed computer output results,
detailed procedures utilized, etc.
Software Tools
Visual Studio 2010
- Introduced by Microsoft Corporation.
- Help to Develop Software and Systems according to the requirements.
Microsoft Word 2013
- Introduced by Microsoft Corporation.
- Help to create reports and documents
Edraw Max 6
- Introduced by Edraw Soft Pvt.Ltd.
- Help to draw the software related diagrams.
Microsoft SQL Server 2008
- Introduced by Microsoft Corporation.
- Used to manage the data called database management system (DBMS).
Adobe Photoshop
Literature Review
Abstract
It is observed that in recent years small and medium Software companies have emerged
very rapidly and thousands of such companies are in existence all over the globe. To cater
the needs of such companies, a new field of research was created Software Engineering,
given than Web engineering differs from traditional software engineering in numerous ways,
which include the need of agile process models, extended modelling techniques (WebML),
Navigational development techniques, different architectures and rapid application process
along with different testing techniques.
It has been observed that Software process improvement emerges as one of the biggest
challenges for such companies. A systematic literature review (SLR) has been conducted to
identify and discuss the existing models and techniques used by small and medium
companies. Important phases of our SLR included identification of the research questions to
be investigated, primary and secondary database searches to identify relevant literature,
data extraction from selected studies, data synthesis to formulate answers, and formal
discussion to identify trends and research gaps.
The Process
SR is a detailed process divided into different tasks and activities that are listed as follows:
Systematic Literature Review Study and Understanding This Phase helps in
developing and understanding of review concepts and to develop an understanding of the
overall methodology.
Formulation of Research Questions This is an iterative phase where the important
research questions to be investigated during the SR are identified.
Development of a Study Protocol This phase is very rigorous and also iterative. It covers
the overall plan for the systematic literature review
Identification of Relevant Literature This phase encompasses the identification of
primary and secondary studies and is a search phase.
Determining Inclusion & Exclusion Criteria During this phase a criteria is applied to
select the studies for to be part of the SR. If a study fulfils the inclusion criteria it is selected
otherwise it is discarded.
Think
This last Principle is probably the most overlooked. Placing clear, complete thought before
action almost always produces better results. When we think about something, we are more
likely to do it right. We also gain knowledge about how to do it right again. If we do think
about something and still do it wrong, it becomes valuable experience. A side effect of
thinking is learning to recognize when we don t know something, at which point we can
Separation of Concerns
Separation of concerns is a recognition of the need for human beings to work within a limited
context. Although human capacity for forming abstractions appears to be unlimited, it takes
time and repetitive use for an abstraction to become a useful tool. When specifying the
behavior of a data structure component, there are often two concerns that need to be dealt
with basic functionality and support for data integrity. A data structure component is often
easier to use if these two concerns are divided as much as possible into separate sets of
client functions. It is certainly helpful to clients if the client documentation treats the two
concerns separately. Further, implementation documentation and algorithm descriptions can
profit from separate treatment of basic algorithms and modifications for data integrity and
exception handling.
There is another reason for the importance of separation of concerns. Software engineers
must deal with complex values in attempting to optimize the quality of a project. From the
study of algorithmic complexity, we can learn an important lesson. There are often efficient
algorithms for optimizing a single measurable quantity, but problems requiring optimization
of a combination of quantities are almost always complete. Although it is not a proven fact,
most experts in complexity theory believe that complete problems cannot be solved by
algorithms that run in polynomial time.
Modularity
The principle of modularity is a specialization of the principle of separation of concerns.
Following the principle of modularity implies separating software into components according
to functionality and responsibility.
Anticipation of Change
Computer software is an automated solution to a problem. The problem arises in some
context, or domain that is familiar to the users of the software. The domain defines the types
of data that the users need to work with and relationships between the types of data.
Software developers, on the other hand, are familiar with a technology that deals with data in
an abstract way. They deal with structures and algorithms without regard for the meaning or
importance of the data that is involved. A software developer can think in terms of graphs
and graph algorithms without attaching concrete meaning to vertices and edges. Working
out an automated solution to a problem is thus a learning experience for both software
developers and their clients. Software developers are learning the domain that the clients
work in. They are also learning the values of the client. What form of data presentation is
most useful to the client, what kinds of data are crucial and require special protective
measures? The clients are learning to see the range of possible solutions that software
technology can provide. They are also learning to evaluate the possible solutions with regard
to their effectiveness in meeting the clients needs.
If the problem to be solved is complex then it is not reasonable to assume that the best
solution will be worked out in a short period of time. The clients do, however, want a timely
solution. In most cases, they are not willing to wait until the perfect solution is worked out.
They want a reasonable solution soon; perfection can come later. To develop a timely
solution, software developers need to know the requirements: how the software should
behave. The principle of anticipation of change recognizes the complexity of the learning
process for both software developers and their clients. Preliminary requirements need to be
worked out early, but it should be possible to make changes in the requirements as learning
progresses.
Generality
The principle of generality is closely related to the principle of anticipation of change. It is
important in designing software that is free from unnatural restrictions and limitations. One
excellent example of an unnatural restriction or limitation is the use of two digit year
numbers, which has led to the "year 2000" problem, software that will garble record keeping
at the turn of the century. Although the two-digit limitation appeared reasonable at the time,
good software frequently survives beyond its expected lifetime.
Incremental Development
Description of an incremental software development process. In this process, we build the
software in small increments, for example, adding one use case at a time.
An incremental software development process simplifies verification. If we develop software
by adding small increments of functionality then, for verification, we only need to deal with
the added portion. If there are any errors detected then they are already partly isolated so
they are much easier to correct.
A carefully planned incremental development process can also ease the handling of
changes in requirements. To do this, the planning must identify use cases that are most
likely to be changed and put them towards the end of the development process.
Consistency
The principle of consistency is a recognition of the fact that it is easier to do things in a
familiar context. For example, coding style is a consistent manner of laying out code text.
This serves two purposes. First, it makes reading the code easier. Second, it allows
programmers to automate part of the skills required in code entry, freeing the programmer's
mind to deal with more important issues
Consistency serves two purposes in designing graphical user interfaces. First, a consistent
look and feel makes it easier for users to learn to use software. Once the basic elements of
dealing with an interface are learned, they do not have to be relearned for a different
software application. Second, a consistent user interface promotes reuse of the interface
components. Graphical user interface systems have a collection of frames, panes, and other
view components that support the common look. They also have a collection of controllers
for responding to user input, supporting the common feel. Often, both look and feel are
combined, as in pop-up menus and buttons. These components can be used by any
program.
Analysis
One of important phase of Software development life cycle is Analysis. So its really
important for any kind of software project. Even Im also spend many days to analysis for my
project called blood donor information system.
Analysis part is beginning of any software project, so this is summarizing all the feasibly
studies, functional and non-function requirements.
Meaning of Analysis
In a broad sense, a general methodology (not a fixed set of techniques) that applies a
'systems' or 'holistic' perspective by taking all aspects of the situation into account, and by
concentrating on the interactions between its different elements. It provides a framework in
which judgments of the experts in different fields can be combined to determine what must
be done, and what is the best way to accomplish it in light of current and future needs.
Although closely associated with data or information processing, the practice of SA has been
in existence since long before computers were invented.
In a narrow sense, analysis of the current and future roles of proposed computer system in
an organization, the system analyst (usually a software engineer or programmer) examines
the flow of documents, information, and material to design a system that best meets the
cost, performance, and scheduling objectives.
Important of Analysis
Problem identification, definition and capture The requirement analyst should
identify the problem along with the system define it accurately. The requirement
definition should be able to provide information on -
o The problems the solution is aimed to solve
o The benefits expected from the solution
The feasibility of the requirements
High Level Description of solution The solution planned to be developed should be
described at a high level along with the system needs it caters to.
Address the needs of all the clients and the users This is a very important part of
the requirement analysis and a step which needs to be meticulously followed before
freezing the requirements. This would help in the deployment phase of the project
too, by getting the users adaptable to the new process or application.
Feature definition The applications planned features need to be captured at length.
The functional and non-functional requirements need to be captured in detail along
with the details on how the project is going to be executed etc.
Figure Source -
http://www.haemonetics.com/Products/Software/Blood%20Center/ElDorado%20Donor.aspx
Figure Source -
http://www.haemonetics.com/Products/Software/Blood%20Center/ElDorado%20Donor.aspx
Objectives
To develop and maintain an appropriate integrated blood donor tracing database
system for the efficient and effective recording and management of blood donor data
and blood donor retention
To improve the quality of recording and management of information about blood
donors. This facilitates the effective tracking of repeat blood donors and the
establishment of a reliable pool of regular repeat blood donors
To improve the accuracy, efficiency and effectiveness of tracking information on
blood donations, from Vein to Vein and ensure blood safety through accurate
labelling and identification of blood units at every stage
To ensure sustainability through capacity building, staff skills training and the
integration of the project into the plan and operations of Zambian Blood Transfusion
Services (ZBTS)
Institution
Department of Health and Family Welfare, Government of Delhi
Theme
Knowledge Management in Government, Internet Governance
Implementation Date: Oct 08, 2005
Summary
The Web-based Blood Bank Management System of the Department of Health and
Family Welfare provides the stock of blood for different groups in the various blood
banks as well as online registration to people who are willing to donate blood. The
details of blood donation camps are also available in the system.
The Blood Bank Management System software features, among other things, donor
registration and blood collection; red cell serology; an infectious marker system;
stock maintenance (whole blood/component); transfer of stock of whole blood
(unscreened location to screened location); rejection accounting; discard accounting;
record of the staff; details on blood donation camps; inventory record; and user
access control.
Impact
Through the Web-based Blood Bank Management System, the entire process of
submitting the online registration form is simple and citizens can register online from
home.
The Department of Health and Family Welfare can collect information regarding
various blood groups. Citizens receive information about the next blood donation
camp via post or e-mail after registration as a result of the listings with respect to
various blood groups.
Source
Government of Delhi
Because of the range of options and the uncertainty of which would be recommended, then
embedding a feasibility study within the delivery project would give rise to many problems.
For example, each option would require a different project plan for my blood donor
information system, and it would be difficult to create the project initiation documentation
without knowing which option would be chosen.
For this reason, current wisdom suggests that a feasibility study being conducted as a
standalone project, with the project implement as the final report itself. This would then be
used by corporate or programme management to act as a mandate to implement the project
that would implement the feasibility recommendations,
Feasibility can be viewed from multiple perspectives. Below present six categories of
feasibility tests.
Operational Feasibility is measure of how well a solution meets the identified the
system requirements to solve the problems and take advantage of the opportunities
envisioned for the system.
Cultural or Political Feasibility is a measure of how people fell about a solution and
how well it will be accepted in a given organizational climate.
Operational Feasibility
Operational feasibility is the measure of how well a proposed system solves the problems
and the task of the project advantage of the opportunities identified during the scope
definition and problem analysis phases and how well it satisfies the system requirements
identified in the requirements analysis phase. Operational feasibility also asks if, given what
is now known about the problem and the cost of the solution, the problem is still worth
solving.
Technical Feasibility
Today very little is technically impossible. Consequently, technical feasibility looks at what is
practical and reasonable. Technical feasibility addresses three major issues,
1. Is the proposed technology or solution practical?
2. Do we currently possess the necessary technology?
3. Do we possess the necessary technical expertise?
Schedule Feasibility
Given the available technical expertise, are the project deadlines reasonable that is, what is
the schedule feasibility of the project? Some projects are initiated with specific deadlines. It
is necessary to determine whether the deadlines are mandatory or desirable. For instance, a
project to develop a system to meet the customer requirements.
If the deadlines are desirable rather than mandatory, the analyst can propose alternative
schedules. It is preferable to deliver a properly functioning information system late deliver
unless information system on time.
Economic Feasibility
The bottom line in many projects is economic feasibility. During the early phases of the
project, economic feasibility analysis amount too little more than judging whether the
possible benefits of solving the problem are worthwhile. Costs are practically impossible to
estimate at that stage because the end users requirements and alternative technical
solutions have not been identified. However, as soon as specific requirements and solutions
have been identified, the analyst can weigh the costs and benefits of each alternative. This is
called a cost benefit analysis.
Legal Feasibility
Information system have a legal impact. First of all, there are copyright restrictions. For any
system that includes purchased components, one has to make sure that the license
agreements are not violated. For one things this means installing only licensed copies. But
license agreements and copy protection can also restrict how you integrate the data and
processes with other parts of the system. If you are working with contract programmers, the
ownership of the program source code and nondisclosure agreements have to be worked
out in advance.
Union contracts can add constrains to the information system on how workers are paid and
how their work is monitored. Legal requirements for financial reporting must be met. System
requirements for sharing data with partners could even run up against antitrust laws. Finally,
many information systems today are international in scope. Some countries mandate where
data on local employees and local transactions must be stored and processed. Countries
differ on the number of hours that make up a workweek or how long employees break for
lunch.
Proper planning
This is one of the keys to a successful project. Creating a project plan is the first thing to do
when undertaking any kind of project. We should need to create a proper plan to develop the
system with the customer requirements.
Implementation factor
This is caused by project scope changes, incorrect use of project methodology, major
changes in the requirements and testing, and/or inspections are poorly done.
Human factor
Project managers are not trained to acquire the necessary management skills. Also, some
managers are not able to apply and put the theory of project management into practice. Poor
communications are also one of the human factors that cause a project to fail.
Among these three factors, the major cause of project failure is inappropriate use of project
planning and scheduling methodology.
Operating System
Blood donor information system runs on Windows XP, Vista or Windows 7& 8 (also Windows
Server 2000, 2003 and 2008). It also has full support for both 32-bit and 64-bit architectures.
If we are thinking of purchasing a new computer, then we thoroughly recommend the
excellent Windows 8. My second choice would be Windows 7.
PC Specifications
This table 4.4.1 shows the recommended and minimum computer specifications for running
the blood donor information system.
4.5 Specification
A standalone application is able to function independently of other hardware. Standalone
application not like web application, only run inside the computer RAM not in the server.
Design
5.1 Work Breakdown Structure and Task Allocation
The Work Breakdown Structure (WBS) is defined by A Guide to the Project Management
Body of Knowledge.
"A deliverable-oriented hierarchical decomposition of the work to be executed by the project
team to accomplish the project objectives and create the required deliverables."
Purpose
Why do we need to create a WBS for our projects? What purpose does it serve? Why should
I waste my time writing on post-it notes and drawing charts when I could be getting my team
started on the actual work of the project? Now, I know everyone reading this is a great
project manager or team member, so I am sure none of we have ever said comments such
as these, but I am sure we have heard them from those "other" project managers who will
remain nameless.
So to answer these questions, let's take a look at what purpose the WBS serves to our
project. There are three reasons to use a WBS in my project. The first is that is helps more
accurately and specifically define and organize the scope of the total project. The most
common way this is done is by using a hierarchical tree structure. Each level of this structure
breaks the project deliverables or objectives down to more specific and measurable chunks.
The second reason for using a WBS in my project is to help with assigning responsibilities,
resource allocation, monitoring the project, and controlling the project. The WBS makes the
deliverables more precise and concrete so that the project team knows exactly what has to
be accomplished within each deliverable. This also allows for better estimating of cost, risk,
and time because you can work from the smaller tasks back up to the level of the entire
project. Finally, it allows you double check all the deliverables' specifics with the
stakeholders and make sure there is nothing missing or overlapping.
Process
Now that we have agreed that creating a WBS will be help to our project's efficiency and
effectiveness, how do we go about it? First, let's look at what all we need to get started.
There are several inputs,
The simplicity principle The design should make simple, common tasks easy,
communicating clearly and simply in the users own language, and providing good
shortcuts that are meaningfully related to longer procedures.
The visibility principle The design should make all needed options and materials
for a given task visible without distracting the user with extraneous or redundant
information. Good designs dont overwhelm users with alternatives or confuse with
unneeded information.
The feedback principle The design should keep users informed of actions or
interpretations, changes of state or condition, and errors or exceptions that are
relevant and of interest to the user through clear, concise, and unambiguous
language familiar to users.
The tolerance principle The design should be flexible and tolerant, reducing the
cost of mistakes and misuse by allowing undoing and redoing, while also preventing
errors wherever possible by tolerating varied inputs and sequences and by
interpreting all reasonable actions.
The reuse principle The design should reuse internal and external components
and behaviors, maintaining consistency with purpose rather than merely arbitrary
consistency, thus reducing the need for users to rethink and remember.
After five second the system will display a new window called login window, I mean in my
system there two privileges can access to the system. Those are administrator and users.
Administrators are the people manage whole the system, and users are just registering
donors and maintaining the donors.
Figure 5.2.2 is showing administrator login, without proper username, and password anyone
cannot access to the system. Likewise the interface for the user, they also ever need proper
username and password to access to the system.
In here figure 5.2.3 there are some icons I have use some icons to get more clear idea about
those functions. And I have used menu strip tools to rive some more function in the separate
way.
Figure 5.2.4 Menu Strip tool of the Main window in the system
Menu strip help to quick access to the function in the system. And I have used some button
tools and picture tools to make visible to the users.
Figure 5.2.5 is showing the button with one icon. I have created this icon used Adobe
Photoshop tool. This button will give more easiness to fine the solution to the users.
Figure 5.2.7 is showing the window of maintain the donors by the administrator.
Administrator only can visible or display this window to make any changes in the system.
As well as there is other interface called create new administrators and users to the system.
This figure 5.2.9 also displaying some kind of .NET framework tools.
And figure 5.2.11 is showing the search window. I mean using this window the admin and
users can easily search the donors and find out easily from the donors list.
5.5 ER Diagram
The selection of model has very high impact on the testing that is carried out. It will define
the what, where and when of our planned testing, influence regression testing and largely
determines which test techniques to use.
There are various Software development models or methodologies,
Waterfall Model
Iteration Model
V Shaped Model
Spiral Model
Extreme Model
Waterfall Model
The waterfall model is the classical model of software engineering. This model is one of the
oldest models and is widely used in government projects and in many major companies. As
this model emphasizes planning in early stages, it ensures design flaws before they develop.
In addition, its intensive document and planning make it work well for projects in which
quality control is a major concern.
The pure waterfall lifecycle consists of several no overlapping stages, as shown in the
following figure 6.1.1. The model begins with establishing system requirements and software
requirements and continues with architectural design, detailed design, coding, and testing.
The waterfall model serves as a baseline for many other lifecycle models.
The following list details the steps for using the waterfall model,
System requirements
Establishes the components for building the system, including the hardware requirements,
software tools, and other necessary components. Examples include decisions on hardware,
such as plug-in boards (number of channels, acquisition speed, and so on), and decisions
on external pieces of software, such as databases or libraries.
Software requirements
Establishes the expectations for software functionality and identifies which system
requirements the software affects. Requirements analysis includes determining interaction
needed with other applications and databases, performance requirements, user interface
requirements, and so on.
Although the waterfall model has its weaknesses, it is instructive because it emphasizes
important stages of project development. Even if one does not apply this model, we must
consider each of these stages and its relationship to our own project.
Iteration Model
The problems with the Waterfall Model created a demand for a new method of developing
systems which could provide faster results, require less up-front information, and offer
greater flexibility. With Iterative Development, the project is divided into small parts. This
allows the development team to demonstrate results earlier on in the process and obtain
valuable feedback from system users.
Often, each iteration is actually a mini-Waterfall process with the feedback from one phase
providing vital information for the design of the next phase. In a variation of this model, the
software products, which are produced at the end of each step (or series of steps), can go
into production immediately as incremental releases.
V Shaped Model
Just like the waterfall model, the V-Shaped life cycle is a sequential path of execution of
processes. Each phase must be completed before the next phase begins. Testing is
emphasized in this model more than the waterfall model. The testing procedures are
developed early in the life cycle before any coding is done, during each of the phases
preceding implementation. Requirements begin the life cycle model just like the waterfall
model. Before development is started, a system test plan is created. The test plan focuses
on meeting the functionality specified in requirements gathering.
Spiral Model
The spiral model is similar to the incremental model, with more emphases placed on risk
analysis. The spiral model has four phases: Planning, Risk Analysis, Engineering and
Evaluation. A software project repeatedly passes through these phases in iterations (called
Spirals in this model). The baseline spiral, starting in the planning phase, requirements are
gathered and risk is assessed. Each subsequent spiral builds on the baseline spiral.
Requirements are gathered during the planning phase. In the risk analysis phase, a process
is undertaken to identify risk and alternate solutions. A prototype is produced at the end of
the risk analysis phase. Software is produced in the engineering phase, along with testing at
the end of the phase. The evaluation phase allows the customer to evaluate the output of the
project to date before the project continues to the next spiral.
In the spiral model, the angular component represents progress, and the radius of the spiral
represents cost.
Extreme Model
An approach to development, based on the development and delivery of very small
increments of functionality. It relies on constant code improvement, user involvement in the
development team and pair wise programming. It can be difficult to keep the interest of
customers who are involved in process. Team members may be unsuited to the intense
involvement that characterizes agile methods.
Advantages of the XP
Lightweight methods suit small-medium size projects.
Produces good team cohesion.
Emphasizes final product.
Iterative.
Test based approach to requirements and quality assurance.
Disadvantages of the XP
Difficult to scale up to large projects where documentation is essential.
Needs experience and skill if not to degenerate into code and fix.
Programming pairs costly.
Waterfall Model
The waterfall model is a sequential design process, often used in software development
processes, in which progress is seen as flowing steadily downwards (like a waterfall) through
the phases of planning, analyzing, designing, coding, testing, implementing, and
maintaining.
The waterfall development model originates in the manufacturing and construction
industries. Highly structured physical environments in which after-the-fact changes are
prohibitively costly, if not impossible. Since no formal software development methodologies
existed at the time, this hardware-oriented model was simply adapted for software
development.
When done well the waterfall method is excellent for large projects and there are no
surprises when the application is finally delivered as all features and even the appearance of
the application has been fully specified and understood by future users of the system.
If the requirements phase is done badly the waterfall method delivers failure as the end
result will only ever be as good as the specifications.
My first step is to create the functional specification. This often begins life as a very
abstract requirements specification provided by the client.
When the application is complete a beta release is published and provided to the
business for testing. Any bugs found are rapidly repaired.
6.3 Procedures
The waterfall model proceeds from one phase to the next in a sequential manner. For
example, one first completes requirements specification, which after sign-off are considered
set in stone. When requirements are completed, one proceeds to design. The software in
question is designed and a blueprint is drawn for implementers (coders) to follow this design
should be a plan for implementing the requirements given. When the design is complete, an
implementation of that design is made by coders. Towards the later stages of this
implementation phase, separate software components produced are combined to introduce
new functionality and reduced risk through the removal of errors.
Thus the waterfall model maintains that one should move to a phase only when its
preceding phase is completed and perfected. However, there are various modified waterfall
models that may include slight or major variations upon this process.
Phases of the waterfall life cycle model.
Requirements - The first phase involves understanding what we need to design and
what is its function, purpose etc. Unless we know what we are going to design, we
cannot approach the problem. Here, the specifications of the input and output or the
final product is studied and marked.
Analysis - As per the requirements, the software and hardware needed for the
proper completion of the project is analyzed in this phase. Right from deciding which
computer language should be used for designing the software, to the database
system that can be used for the smooth functioning of the software, such features are
decided at this stage.
Design - The algorithm (pseudo-code) of the program or the software code to be
written in the next stage, is created now. This algorithm forms the backbone for the
actual coding process. Proper planning relating to the design of user interface,
flowcharts is done here.
Coding - Based on the algorithm or flowchart designed, the actual coding of the
software is carried out at this stage. The flowcharts / algorithms are converted into
instructions written in a programming language.
Testing - The software designed, needs to go through constant software testing and
error correction processes to find out if there are any flaw or errors. Testing is done
so that the client does not face any problem during the installation of the software.
Maintenance - There are some issues which come up in the client environment. To
fix those issues patches are released. Also to enhance the product some better
versions are released. Maintenance is done to deliver these changes in the customer
environment.
6.4 Implementation
Normally I have did work of each phases of the software development life cycle. Now here Ill
show the implementation or the works in each phases during the development of the blood
donor information system. These are the stages or phases of software development life
cycle.
Requirements
For the requirements, I have categorized in to two ways, such as functional and non-
function requirements. These are the important thing during the project development period
because we need requirements to collect how system it should be. These are some notes
which I have gathered from the clients and other resources.
Analysis
After collected requirements have to analyze the function or we need to study some similar
systems and develop the systems with use of requirements. And I have studied some similar
systems same as blood donor information systems. Some facts,
Design
Based on the user requirements and the detailed analysis of a new system, the new system
must be designed. This is the phase of system designing. It is the most crucial phase in the
development of a system. The logical system design arrived at as a result of system analysis
and is converted into physical system design.
The logical design produced during the analysis is turned into a physical design - a detailed
description of what is needed to solve original problem. Input, output, databases, forms,
codification schemes and processing specifications are drawn up in detail. In the design
stage, the programming language and the hardware and software platform in which the new
system will run are also decided. Data structure, control process, equipment source,
workload and limitation of the system, Interface, documentation, training, procedures of
using the system, taking backups and staffing requirement are decided at this stage.
There are several tools and techniques used for describing the system design of the system.
These tools and techniques are: Flowchart, Data flow diagram (DFD), Data dictionary.
Design is make impact to the systems. Because before develop the system, the diagrams
other resources will give brief idea how this system it should be.
Coding
The system design needs to be implemented to make it a workable system. Its demands the
coding of design into computer language, i.e., programming language. This is also called the
programming phase in which the programmer converts the program specifications into
computer instructions, which we refer to as programs. It is an important stage where the
defined procedures are transformed into control specifications by the help of a computer
language. The programs coordinate the data movements and control the entire process in a
system. A well written code reduces the testing and maintenance effort. It is generally felt
that the programs must be modular in nature. This helps in fast development, maintenance
and future changes, if required. Programming tools like compilers, interpreters and language
like c#, c++, and java etc., are used for coding .with respect to the type of application. The
right programming language should be chosen.
And I have choose C# programming language to develop the system by using codes. And
coding is important to make the functions and the programmes. I have used Microsoft Visual
Studio 2010 GUI to develop this system without any affection.
conn.Open();
}
}
These set of codes are help to connect with database. So this one method or function,
because we can use this method in anywhere, thats why we are called as object oriented
programming language.
func(Controls);
}
These set of codes are used to clear the text fields which they have called this function.
Example 1 and 2 is showing the sample codes which I have used in my system.
Implementation
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,
Systems Development Life Cycle (SDLC) puts emphasis on decision making processes that
affect system cost and usefulness. These decisions must be based on full consideration of
functional requirements, and economic and technical feasibility. The primary objectives of
any SDLC is to deliver quality system which meets or exceed customer expectations and
within cost estimates, work effectively and efficiently within the current and planned
infrastructure, and is an inexpensive to maintain. SDLC establishes a logical order of events
for conducting system development that is controlled, measured, documented, and
ultimately improved. Any software is not all complete and there are enough rooms to add
new features to existing software.
Phases dropped 0
Table 8.2 SDLC Compliance Summary
And summary show how many phases implemented for this project work, and about phases
of the software development life cycle table 8.2.
I was created test cases to identify the each step of the system, and test for to identify the
working condition of the whole system. Below I have created the test cases for each and
each methods of the system, which is clearly testing the each methods and function witch
are run inside the system.
Most of actual testing is giving good comment, and I have got some errors and warning
messages during testing period, I have corrected those errors and warning with the system,
and I have fixed those problems.
This system could be more useful for any kind of patients in the hospitals. Whoever
immediately need blood, using this this they contact the already registered donors by using
this system.
The scope and objective of this system is giving a more secure to data and the information
of the donors, in the critical or emergency situation the admin or user can easily contact the
blood donors, and administrator can create new events to get know when next blood
donation camp will start and the time of it.
So I make one decision the computerized system is better than other paper base or other
systems. So its more secured purpose. I really experienced on developing computer based
and standalone application.
Advantages Disadvantages
Advantages Disadvantages
As the tester has knowledge of the Due to the fact that a skilled tester is
source code, it becomes very easy needed to perform white box testing,
to find out which type of data can the costs are increased.
help in testing the application
effectively. Sometimes it is impossible to look
into every nook and corner to find
It helps in optimizing the code. out hidden errors that may create
problems as many paths will go
Extra lines of code can be removed untested.
which can bring in hidden defects.
It is difficult to maintain white box
Due to the tester's knowledge about testing as the use of specialized
the code, maximum coverage is tools like code analyzers and
attained during test scenario writing. debugging tools are required.
Table 8.1.1.2 Advantages and Disadvantages of White box testing
Advantages Disadvantages
Offers combined benefits of black
box and white box testing wherever
possible. Since the access to source code is
not available, the ability to go over
Grey box testers don't rely on the the code and test coverage is
source code; instead they rely on limited.
interface definition and functional
specifications. The tests can be redundant if the
software designer has already run a
Based on the limited information test case.
available, a grey box tester can
design excellent test scenarios Testing every possible input stream
especially around communication is unrealistic because it would take
protocols and data type handling. an unreasonable amount of time;
therefore, many program paths will
The test is done from the point of go untested.
view of the user and not the
designer.
Table 8.1.1.3 Advantages and Disadvantages of Grey box testing
Table 8.1.1.4 display the different and compere of those testing methods.
S.N. Black Box Testing Grey Box Testing White Box Testing
1 The Internal Workings of Somewhat knowledge of the Tester has full knowledge of
an application are not internal workings are known the Internal workings of the
required to be known application
2 Also known as closed box Another term for grey box Also known as clear box
testing, data driven testing testing is translucent testing as testing, structural testing or
and functional testing the tester has limited code based testing
knowledge of the insides of the
application
3 Performed by end users Performed by end users and Normally done by testers and
and also by testers and also by testers and developers developers
developers
4 Testing is based on Testing is done on the basis of Internal workings are fully
external expectations - high level database diagrams known and the tester can
Internal behavior of the and data flow diagrams design test data accordingly
application is unknown
5 This is the least time Partly time consuming and The most exhaustive and time
consuming and exhaustive exhaustive consuming type of testing
6 Not suited to algorithm Not suited to algorithm testing Suited for algorithm testing
testing
7 This can only be done by Data domains and Internal Data domains and Internal
trial and error method boundaries can be tested, if boundaries can be better
known tested
Table 8.1.1.4 Different between testing methods
Pre- Conditions
System have 2 kind privileges to access, those are admin and the user. They must access to
the system with proper username and password. If the admin or user type their correct
username and password, then the programme will be check the valid username and
password to access to the system.
Pass/
Step Action Expected System Response Comment
Fail
Change the user type to admin or
1 Click the user type button Pass Good
user in the system
Without Filling the text box Display error message with
2 Pass Good
and click login button information to login
Post- Conditions
There are two User type, Administrator and User.
If the Username and Password is correct, access to the main function in the system.
If the Username and Password is incorrect, then error massage will be display.
Check the valid username and password from the database.
Make Sure the username and password of those two users in the system.
Pre- Conditions
After given correct username and password, then the user can view this page by using main
window of the system. All the text fields can be fill by administrator or user.
Pass/
Step Action Expected System Response
Fail
Comment
Click the donor id text field Filling with using any kind numbers
1 Pass Too Slow to select
and fill or text
Without filling the donor id Display error message with
2 Pass Good
field and click save button information
Post- Conditions
All the Donor details can be store in the database.
Donor id is the primary key, cant duplicate the value.
Admin and users can view this window to register new donors to the system.
Pre- Conditions
After completing the registration of donor, then if they have any wrong details the admin can
only update or edit their details with correct details. Using donor id and they can select to
update their details.
Pass/
Step Action Expected System Response Comment
Fail
Using donor id and select the
1 Changing with details Pass Very Quick
donor
Type the donor id in the
2 Changing with details Fail Not Fix
combo box field
Without Changing any details
Not display any error message and
3 of the donors and click Pass Good
save in the database
update button
Post- Conditions
Only Administrator can update or edit the donor details.
Using Donor id and select the donors to make changes.
Donor Details can be make complete changes.
After change all the details and clicking save button will change all the details of the
current donor.
Pre- Conditions
If the blood camp, no need one donor they can just delete the donor by clicking one button.
In the donor maintaining window there is combo box to change the donor list, I mean using
that combo box and select the donor current donor and delete.
Pass/
Step Action Expected System Response
Fail
Comment
Changing the donor id using All the details must change with the
1 Pass Fix
combo box donor id
After delete the donor then Delete the donors and get refresh
3 Pass Fix
get refresh to make the list of the donor id
Post- Conditions
Only Administrator can delete the donor details.
Selecting donor id and delete the donors.
Easily can delete the donors from the list.
Pre- Conditions
Sending SMS to donors is the most important function of the Blood donor information
system. There is two function sending SMS by the phone number and sending SMS by
selecting blood group, and area of the donor.
Pass/
Step Action Expected System Response
Fail
Comment
Click send button without fix Sending the SMS to all registered
5 Pass Quick
the district and blood group donors
6 After click the send button The message box will display Pass Quick
Post- Conditions
Admin and User can send the SMS to Donors, or others using mobile number.
The already registered donors will receive a SMS from the system.
Quick contact with the blood donors.
Easily send the SMS to anyone.
Pre- Conditions
Report view is one of important for any kind of system. So report will give the brief idea
about all the blood donors details at one time. Not only that admin or user can print the
donors list with details.
Pass/
Step Action Expected System Response
Fail
Comment
Click the donor registered list Preview the donor registered list
1 Pass Too Slow
report report with details
Click the donor contact Preview the donor contact details
2 Pass Tool Slow
details report report with the details
3 Click the event details report Preview the event details report Pass Too Slow
Post- Conditions
Reports can view by administrator and users.
Using report they can easily print those details.
Report is given brief idea and clear for the users.
Test Case: 1.7 Test Case Name: Create Admin and User
System: Blood Donor Information System Design Date: 22nd December 2014
Pre- Conditions
Administrator only can create the new administrator and user for the system. To create new
admin or user they must log into one of admin account. Admin can create new account,
update the account, and delete the account.
Pass/
Step Action Expected System Response
Fail
Comment
Post- Conditions
Admin only can use this system.
Easily create new administrator and users to the system.
Update the username and password of current users, or administrators.
Delete unwanted users from the database.
Clear the text field just clicking a button.
Pre- Conditions
Event management will give a brief idea about the next blood camp event. Here the
administrator only create new events. Administrator only can update the events, and delete
unwanted events.
Pass/
Step Action Expected System Response
Fail
Comment
Change the event id from Changing all the details about the
1 Pass Quick
combo box events
Display error message with
2 Re-type the event id Pass Good
information
Click save button without Display error message with
3 Pass Good
filling any text field information
Post- Conditions
Administrator only can access to the event management window.
New events can create by using this function.
Update the current events.
If there is any unwanted event they can delete.
Pre- Conditions
Search event is most important for any kind of system, because it will be make easy to
identify the details by using id. Here search donors is needed to identify donors immediately.
Pass/
Step Action Expected System Response
Fail
Comment
Enter value in the search text Display search result in the grid
7 Pass Quick
field view
Table 8.1.2.9 Test Case for Search Blood Donors
Post- Conditions
Administrator and user can search the blood donors.
There 4 type to search the donors
o Search by Donor ID
o Search by Donor Name
o Search by Donor Address
o Search by Donor Blood Group
Quickly view the search result to grid view.
Expected
Test No Test Data Purpose Actual Result
Result
Click the Save button to
Not Saved in the
Record the details in the Store the details in Popup an error
01 database, there is an
database without filling any the database message
error message
fields
Need to be
Click the Save button to
Store the details in store all the Successfully Saved in
02 Record the details in the
the database details in the the database
database with filling fields
database fields
Successfully save the
Type already registered id Avoid the Show an error
03 donor details to the
of the donor registration message
registered donor details
Changing with
Check the Valid blood Easily can select
04 using mouse Successfully changing
groups in the combo box the blood group
scroll
Table 8.1.3.2 Test Case for Donor Registration
Type already registered id Avoid the Show an error Not Saved, Popup an
03
of the donor registration message error message
Table 8.1.3.2.1 Test Case for Donor Registration Error Correction
Expected
Test No Test Data Purpose Actual Result
Result
Give a warning
message called
Click update button without Update the details
01 Please select Update successfully
selecting the donor id of current donor
an id of the
donor
Give message
Click the update button with Update the details
02 called Updated Updated successfully
selecting the current donor of current donor
successfully
Delete the donor by Delete from the
03 Delete the donors Deleted successfully
selecting the donor id database
Hide the main
Without hiding the main
window and
04 Logout process Logout the system window and display login
display the login
window
window
Table 8.1.3.3 Test Case for Donor Maintaining
Give a warning
message called
Click update button without Update the details
01 Please select Update successfully
selecting the donor id of current donor
an id of the
donor
Hide the main
Hide the main window
window and
04 Logout process Logout the system and display login
display the login
window
window
Table 8.1.3.3.1 Test Case for Donor Maintaining Error Correction
Expected
Test No Test Data Purpose Actual Result
Result
Successfully
01 Change the COM Port Connect with GSM connected with Show an error message
the GSM
Without selecting any field Popup an error Display error Display send message
02
and click send button message message successfully
Display Popup the message
Selecting the field and click
03 Sending the SMS Successfully called Successfully
send button
Send message send the message
Send to current city
Selecting donor by using Send the SMS
04 or blood group Successfully sent
city, and blood group to donor
donor
Table 8.1.3.4 Test Case for Sending SMS
Successfully Successfully
01 Change the COM Port Connect with GSM connected with connected with GSM
the GSM network
Expected
Test No Test Data Purpose Actual Result
Result
Display the
Access to the report of the View the all the donor details in Display the result in the
01
donors details donor details the crystal crystal report
report
Display the
View the all the
Access to the report of the donor contact Display the result in the
02 donor contact
donors contact details details in the crystal report
details
crystal report
Display the
Access to the report of the View the all the event details in Display the result in the
03
event details event details the crystal crystal report
report
Print the reports via using Can printed any
04 Printing the reports Printed the reports
printer kind of reports
Display the
View the current donor View the current donor
05 View the donor current donor
details details
details
Display the
06 Search donor by id Searching Display the search result
search result
Table 8.1.3.5 Test Case for Reports view
Error Correction
Here I havent got any errors, reports are very important to check the current donors details
and the all the donors details at one time, and of course, we can find the donors contact
details without any other details. Not only the donors details, events details also can be see
using these kind of function.
Again I prefer to tell I havent got any error during testing the reports view function.
Expected
Test No Test Data Purpose Actual Result
Result
Update the
Change the user id and Update Display updated
01 username and
click update button successfully successfully
password
Delete the
Click delete button to delete Delete current user current user or
04 Deleted successfully
current user or admin or admin admin from the
database
Change user or admin id View the username
View each user Changing with user or
05 and view the user name and password of
and admin admin id
and password of each each user & admin
Table 8.1.3.6.1 Test Case for Create Admin and User Error Correction
Expected
Test No Test Data Purpose Actual Result
Result
Click the create button Popup error Display an error Save successfully in the
01
without filling any details message message database
Display
Click the create button after Save the event Save in the database
02 message save
filling details details with successful message
successfully
Display
Update the event details Update event message Update event details in
03
buy using event id details updated the database
successfully
Display
Click delete button to delete Delete event by message Delete the event detail
04
current event using event id deleted from the database
successfully
View the event
View the event
details by Not change according to
05 Changing the event id details by changing
changing the the event id
event id
event id
Table 8.1.3.7 Test Case for Creating New Events
Click the create button Popup error Display an error Show an error
01
without filling any details message message message
Expected
Test No Test Data Purpose Actual Result
Result
Display the
Select search by donor id Select donor id and Display the donor id
02 donor id
and click next search window
window
Display the
Select search by donor Select donor Display the donor
03 donor address
address and click next address and search address window
window
Display the
Select search by donor Select donor blood Display the donor blood
04 donor blood
blood group and click next group and search group window
group window
Display the
Select search by donor Select donor name Display the donor name
05 donor name
name and click next and search window
window
Type id of the current blood Searching current Display the Displayed the search
06
donor and search blood donor search result result
Close the
07 Click close button Close the window Closed the window
window
Documentation To create the Project Book 1 Book = Rs. 2, 000 , 3 Book Rs. 6, 000
SIM Card To Send the SMS to the Donors SIM Card = Rs. 200 Rs. 200
Table 8.2.1.1 is showing the cost for work schedule of the blood donor information system.
The total cost is 12, 200 rupees to develop this system successfully. The more cost to print
the documentation, I mean to bind the Project report. And low cost for to buy a SIM Card and
A4 Papers. This my estimation of the cost schedule.
SIM Card To Send the SMS to the Donors SIM Card = Rs. 200 Rs. 200 Rs. 200
Total Cost for the Project Rs. 12, 350 Rs. 5, 540
Table 8.2.2.1 Budgeted Cost of Work Performed
As I told, I have changed some schedule of the project and add some more extra days. Then
within these days I have finalized my project as much possible.
For large software projects with average capabilities, the development process
determines project quality.
For small software projects, the capabilities of the developers is the main
determinant.
The development technology is particularly significant for small software projects.
In all cases, if an unrealistic schedule is imposed then software quality will suffer.
Module testing is the testing of complete code objects as produced by the compiler when
built from source.
A library may be composed of a single compiled object or several compiled objects. There is
only a slight difference between unit testing and module testing. Modules are fully formed
chunks of coherent source code that can typically be tested by driving a few function
signatures with various stimuli. On the other hand, unit testing (which is considered as part
of the implementation phase for this software development process) may involve testing one
small part of a function that will never formally implement any function interface.
Centralization Database
Make the database into centralization by using a database server. Because if all the data of
the donors are in a one database mean thats very useful to contact or communicate the
donors easily and quickly.
So we can make the database of blood donor information system into the centralization
database server. So its safe because in a one place of all the data. Easily can make security
purpose for the database server.
(name) (email)
(phone number)
Project Description
This project is about Blood Donor Information System. Purpose
of this system registering the blood donors, and critical situation
easily can communicate with registered blood donors via SMS.
Issues Normally I havent got any issues. But I have spent lots time to
develop this system.
PREPARED BY
Project Manager(Client)
APPROVALS
Sponsor
Project
Supervisor(Academic)
(name) (signature) (date)
Blood Donor
Project Title: Information System Project category : Softwares &
Databases
B. Project Deliverables
List all Project Deliverables and the date each was accepted by the user. Identify any contingencies
or conditions related to the acceptance.
Deliverable Date Accepted Contingencies or Conditions
C. Performance Baseline
The above stated project business objectives and servicers alongside the performance goal and their
respective results were all achieved. A look on the below cost base line would allow to see how the
project had been successful and hence cost effective as well.
State the Planned Cost and Funding for the project, as approved in the Initial Cost Baseline and the
Project Charter. State the Actual Cost and Funding at completion. Document and explain all cost
and funding variances, including approved changes to the cost baseline.
Expenditures (Rs.000)
Materials and
Supplies - - - No special materials
Non-General Fund - - - -
Federal - - - -
Other Rs. 5000 Rs. 5000 Rs. 000 Cash from parents
E. Schedule Baseline
Compare the initial approved schedule baseline against the actual completion dates. Enter the
planned start and finish dates from the initial schedule baseline. Document all actual start, finish
dates, and explain any schedule variances, including approved changes to the schedule baseline
Document any changes to the Project Scope and their impact on Performance, Cost, or Schedule
Baselines.
Describe the plan for operation and maintenance of the product, well, or service delivered by the
project. State the projected annual cost to operate and maintain the product, good, or service.
Identify where and why this projection of cost differs (if it differs) from the Project Proposal. If the
operation and maintenance plan is not in place, what is the target date for the plan and what is the
impact of not having operations and maintenance for the product, well, or services in place.
This project has to be handled with proper care. The system codes very longer than others,
and the user have computer based knowledge to operate the system.
Failing to that, the following problem is likely to occur:
Therefore its very important that this program is maintained by a learned person. If for e.g. the
client wills to increase the capturing frame number or even wishes to change the saving directory a
backup of the original program must be taken first before any changes shall be considered to take
effect.
Expenditures ($000)
Services - - - -
No much software
Software Tools - - - tools used
Hardware - - - -
Decrease in electricity
Facilities Rs.1, 000 Rs. 800 -200 charges
Contingency (Risk) - - - -
Non-General Fund - - - -
Federal - - - -
H. Project Resources
List the Resources specified in the Resource Plan and used by the project. Identify to whom each
resource was transferred and when it was transferred. Account for all project resources utilized by the
project.
Person or
Resource
Organization Who Turnover Date
(Describe or name the resource used)
Received Resource
Project Team
Mr. Munshif Help to develop 11th November 2014
Mr. Nuzrath Giving a plan 15th August 2014
Customer Support
Facilities
Equipment
Dongle (Modem) Parents 12th June 2014
Software Tools
Visual Studio 2010 BCAS Kandy Campus 14th July 2014
Crystal Report BCAS Kandy Campus 14th July 2014
SQL Server 2008 BCAS Kandy Campus 14th July 2014
Other
Identify all project documentation materials stored in the project library or other repository. Identify the
type of media used and the disposition of the project documentation (see Communications Plan).
Storage
Report(s) and Document(s) Media Used Location Disposition
Feasibility Studies Report Doc, PDF DVD Feasibility Study of System
Specification Report Doc, PDF DVD Functional and Non-Functional
User Interfaces Report Doc, PDF, MP4 DVD Images of Interfaces
System Diagram Report Doc, PDF DVD Sample Diagrams
SDLC Report Doc, PDF DVD Introduction to SDLC
System Testing Report Doc, PDF DVD Testing Methods, Actual Test
User Manual Documentation Doc, PDF DVD User Manual
J. Lessons Learned
Identify Lessons Learned for feedback to the Commonwealth Project Management process. Lessons
Learned should be stated in terms of Problems (or issues) and Corrective Actions taken. Provide a
brief discussion of the problem that identifies its nature, source, and impact. Site any references that
provide additional detail. References may include project reports, plans, issue logs, change
management documents, and general literature or guidance used that comes from another source.
Identify the date for completing the post implementation report and the person responsible for this
action.
Action Date Responsible Person
L. Approvals
Project Sponsor
Project coordinator
After double click the icon, then there is one splash screen will pop up in the display, and
after 3 to 6 second the progress will be load, then the logging window will display in the
computer or leptop monitor.
If the password is not matching with the username, then this kind of error message will be
display. If the administrator given correct username and password in the correct text fields in
the login window figure 9.4.3 is showing,
After fill all the text fields with the correct username and password, then the user need to
click the login button to access or display the main admin window.
If we miss some important text fields then it wont save in the database. So we should know
what thing need to be complete are.
Donor ID Donor id must be type in that field, it is a unique, cant be repeated same
numbers.
Name Name also need to be fill then only system allow to record the data.
Blood Group We cannot leave this stage, because this is one of important for the
system.
After complete those fields then the data or blood donor details recorded in the database.
And display a message box figure 9.4.5 is shown.
Select a current donor by using donor id, and if that donor is not important or no need for the
future works then just click the delete button to delete that donor with details completely.
After delete the current donor form the list then there is one confirmation message will be
display in the screen figure 9.4.8 is showing.
After clicking the edit button there is window called edit the donors will be display figure
9.4.10 showing.
Just select the donors via using donor id. So then we can make any kind of changes about
the selected donors in the list box. Sometimes the donor might be change their mobile
numbers and other email addresses according to their situation. So we should need
connection with the donors to contact them in a critical or emergency situation.
The Administrator can select one donor and make the changes according to that donors
prefer.
First of all we should fill those empty text boxes like figure 9.4.11. Then press the save to
create new events. After few second new event has been created in the database figure
9.4.12 is showing that function in clearly.
Here its showing the events details in clearly. Even we can search the events by using
events id. So you can just type the wanted event by using event id in the search field.
To delete the old or unwanted event just click the delete button with selected events id. Then
there is one message will display in the window about to confirm the delete via using two
button Yes, and No. If we want delete that event press Yes, to keep that even as well it
is press No.
There is one button called clear, this is for to clean the text fields, and make it empty. In the
figure 9.4.13 showing that button clearly.
There is a one default message in that particular message field, so if we want right
something new just click the clear button to clean that message box and whatever we want
we can type the message and clicking the send to send to the donors. Make sure the
confirmation message.
Using the selecting search option and easily do a search with different search option and
figure 9.4.18 is showing that window.
Select one search option and click next button then particular search window will be display
in the monitor as figure 9.4.19 showing.
Make sure first of all we should select the particular user by using the ID. Then just click the
delete button to delete that particular account from the list figure 9.4.22. Confirmation of the
deleted will be display figure 9.4.23.
Likewise we can delete the administrator account and user account clicking just one button,
but this function is only allow for administrator to make changes. Any other account cannot
access to this maintain function without authorized permission.
There are three types of reports can view with details. If we Donor registered list. After few
second it will be display figure 9.4.25 is showing that particular report.
And easily view the report and make good understanding of the details of each and each
donors.
After click the print button the print properties window will be display figure 9.4.27 is showing
that properties of printing.
Here just select the printer and setup the pages then click the print button to print the details
of the current details of donors.
References
System Development Principle
James, 1996. tifr. [Online]
Available at: http://www.smartdraw.com/resources/tutorials/jackson-system-
development-diagrams/#/resources/tutorials/Introduction-to-Yourdon-and-Coad
[Accessed 09 11 2014]
South Carolina Department of Education. Program for Assisting, Developing and Evaluating
Principal Performance (PADEPP). n.d. Retrieved December 1, 2010,from
http://www.scteachers.org/leadership/principalperformance.cfm
Testing Methods
Guide to the Software Engineering Body of Knowledge, Swebok A project of the IEEE
Computer Society Professional Practices Committee, 2004.
Software Engineering: A Practitioners Approach, 6/e; Chapter 14: Software Testing
Techniques, R.S. Pressman & Associates, Inc., 2005.
Myers, Glenford J., IBM Systems Research Institute, Lecturer in Computer Science,
Polytechnic Institute of New York, The Art of Software Guide to the Software Engineering
Body of Knowledge, Swebok A project of the IEEE Computer Society Professional Practices
Committee, 2004.
Software Engineering: A Practitioners Approach, 6/e; Chapter 14: Software Testing
Techniques, R.S. Pressman & Associates, Inc., 2005.
Myers, Glenford J., IBM Systems Research Institute, Lecturer in Computer Science,
Polytechnic Institute of New York, The Art of Software 2004.
Index
Acronyms 14
Abstract 16, 20, 22, and 27
Admin 18, 40, 51, 62, 70, 71, and 72
Application 22, and 117
Analysis 30, and 104
Business 16, and 23
Blood Donor 16, 17, 33, 36, 51, 52, 53, 54, 66, 77, 99, and 107 120
Computerized 16, 43
Coding 17, 20, 25, and 73
Documentation 17, 18, 20, 40, 70, 92, and 108
Developers 17, 68, and 69
Diagram 56- 62
Database 33, 66, 34, 74, and 105
Data 23, 24, and 48
Development 25, and 29
Design 25, and 73
Engineering 21, 27, and 46
Functional 31, 45, 46, 49, and 64
Feasibility 37, 38, 39, and 40
Factor 42, 50, and 77
Gathered 16, 41, and 42
Generality 29, 42, and 50
Goal 17, and 26
Graphical 34, and 75
Hospital 16, 17, and 33
Information 32, 45, 78, 112, and 115
Implement 25, and 35
Interface 50, and 70
Modularity 17, 27, and 28