A Document Management System in Defense Industry Case Study

1. a Document Management System
in defense industry case study
Seval Çapraz
BIL/CMP 781 – Software Quality Management, Fall 2018
Importance of software quality
assurance to prevent and reduce
software failures:

2. Content
› The Problem
› What is DMS?
› Research goal & Questions
› Initial Findings
› Result

3. The Problem
› Computer software products can contain various defects which
affect the software quality very much.
› These defects may cause not only financial damage but also many
life losts especially in defence sector.
› Therefore software quality assurance has importance in order to
reduce defects and improve the quality.
› DMS; is an electronic document management system that is in
compliance with internal guidelines and regulations to produce
digital documents which is mainly used in Turkish defence industry.

4. The Problem (cont.)
› In this study, we discuss how lack of proper software
quality management(SQM) resulted in incidents based on
DMS project.
› We also recommend SQM as a proper solution in various
stage of the software development process especially for
document management systems such as DMS.

5. What is DMS?
Modules of DMS Line of Code People / Month
Document Management
Module
~2.000.000 600
Archive Module ~16.000 60
DMS is the product of one of the pioneer companies in Turkey
which develops many tools and software solutions for Turkish
defence sector.
DMS manages all processes for digital documents from creation
phase to disposal phase.

6. Document Management Module
› In compliance with TS13298 (Turkish Standards Institution – 13298),
› In compliance with the e-signature Regulation,
› In compliance with the Regulation on Procedures and Principles,
› Supports power of act attorney procedures,
› Supports E-mail integration,
› Has ability to keep different metadatas for each document type,
› Has ability to view the differences in versions of the documents,
› Supports dynamic workflow process.

7. Archive Module
› This module allows the documents that expired their life time to be
archived in the system.
› In addition to that, it allows physical archive by letting the users
enter the metadatas for physical documents.

8. Research goal
& Questions
●
This study aims to discuss the incidents
when the lack of software quality
management and the proposed solutions
based on the document management
systems such as DMS.
What are the incidents and solutions of the
main cause of defects?
Which problems arise when the actual
practice comes into play?
Why software quality management is
important for DMS?
How to find a way to develop high-quality
software at a reasonable price for DMS?

9. Research goal
& Questions
How to ensure the observation of every
objective, responsibilities and the
guideline?
How to make DMS more compact, cheaper,
and user friendly for the users in defence
industry?
How to make DMS more fault tolerant and
robust?
How to make DMS more secure?
How can we decrease bugs?
How can we decrease new product delivery
time?
How can we protect the system from failure?

10. Initial Findings

11. We have to reduce bugs because...
› Software quality is more important in defence industry because
very bad incidents may occur when the lack of software quality
management.
› For example, the system had a bug with transparency of the
watermarks on pdf documents in old releases. When the
watermark on the secret documents is not half-transparent, the
soldiers can not read the document clearly.
› It caused that a soldier bombed wrong destination because the
nontransparent watermark was published on top of the coordinates
of the correct location on the document.

12. ●
In another example, the secret documents should
not be read by non-authorized people.
●
Permission and authorization failures can not be
tolerated in defence industry because enemies can
use any information against the government.
●
A lot of bugs occur in the DMS about permission
and authorization system however they can be
avoided before the disasters by using proper
software quality management.

13. ●
The software development is done by iterative development.
●
The sprints are done in one week.
●
23 people works in the project. 12 of them are software
developers. 4 of them are looking after deployment while
other 4 for team lead. 3 of them are testers.
●
There are no deployment automation tool.
●
The product delivery is done when the system is ready, not
based on a calendar. So it always delays.

14. ●
Bugs are not analyzed and categorized before. We do not
now the root cause of bugs.
●
There are no review meetings with customers.
●
There is a tool (TFS) to track the bugs and tasks.
●
The product tests are done by testers. There is no test
automation tool.
●
The products are not measured for quality.

15. ●
A lot of bugs may occur in the DMS about
usage, permission and authorization system
however they can be avoided before the
disasters by using proper software quality
management.
●
We can diminish the software delivery time
by using software quality management.
●
There are other case studies in literature in
other domains. [1]
Results
[1] Madadipouya, Kasra. "Importance of software quality assurance to
prevent and reduce software failures in medical devices: Therac-25 case study."