dido:public:s_cli:05_contents:01_prt:00_intro:01_problem
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
dido:public:s_cli:05_contents:01_prt:00_intro:01_problem [2021/04/30 11:47] nick ↷ Page moved from dido:public:s_cli:02_contents:00_intro:01_problem to dido:public:s_cli:05_contents:00_intro:01_problem |
dido:public:s_cli:05_contents:01_prt:00_intro:01_problem [2022/01/15 14:48] (current) 50.19.247.197 ↷ Links adapted because of a move operation |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== 1.1 Problem ====== | ====== 1.1 Problem ====== | ||
| - | [[dido:public:s_cli:02_contents:00_intro| Return to Introduction]] | + | [[dido:public:s_cli:05_contents:01_prt:00_intro:start| Return to Introduction]] |
| + | A major problem confronting the users of [[dido:public:ra:xapend:xapend.a_glossary:d:dido_platform | DIDO Platforms]] are getting products that support the end-users [[dido:public:ra:1.4_req:2_nonfunc | Non-Functional]] requirements. The two most noteworthy Non-Functional requirements are [[dido:public:ra:1.4_req:2_nonfunc:05_interoperability | Interoperability ]] and [[dido:public:ra:1.4_req:2_nonfunc:10_portability | Portability]] of products built upon the existing DIDO platforms. However, other Non-Functional requirements such as [[dido:public:ra:1.4_req:2_nonfunc:20_maintainability | Maintainability]] are of concern. Maintainability covers a broad spectrum of areas: | ||
| + | * //**[[dido:public:ra:1.4_req:2_nonfunc:20_maintainability:modularity| Modularity]]** - Degree to which a system or computer program is composed of discrete components such that a change to one component has minimal impact on other components.// | ||
| + | * //**[[dido:public:ra:1.4_req:2_nonfunc:20_maintainability:reuseability| Reusability]]** - Degree to which an asset can be used in more than one system, or in building other assets.// | ||
| + | * //**[[dido:public:ra:1.4_req:2_nonfunc:20_maintainability:analysability| Analysability]]** - Degree of effectiveness and efficiency with which it is possible to assess the impact on a product or system of an intended change to one or more of its parts, or to diagnose a product for deficiencies or causes of failures, or to identify parts to be modified.// | ||
| + | * //**[[dido:public:ra:1.4_req:2_nonfunc:20_maintainability:modifiability| Modifiability]]** - Degree to which a product or system can be effectively and efficiently modified without introducing defects or degrading existing product quality.// | ||
| + | * //**[[dido:public:ra:1.4_req:2_nonfunc:20_maintainability:testability| Testability]]** - Degree of effectiveness and efficiency with which test criteria can be established for a system, product or component and tests can be performed to determine whether those criteria have been met.// | ||
| + | Often, the DIDO Platforms use proprietary languages, libraries, and interfaces which ultimately affect the Interoperability, Portability and maintainability of end user solutions built upon the proprietary solutions causing [[dido:public:ra:xapend:xapend.a_glossary:v:vendorlockin]]. The response from the DIDO Platforms is often //"our product is [[dido:public:ra:xapend:xapend.a_glossary:o:oss]]"// therefore it is a standard or our specification is a [[dido:public:ra:xapend:xapend.a_glossary:d:defactostd]]. While there is some legitimacy in these responses, it is not adequate for long term (30+ year) lifecycles or for [[dido:public:ra:xapend:xapend.a_glossary:m:missioncritical | Mission Critical Systems]]. | ||
| + | |||
| + | Additionally, the use of //"languages, libraries, and interfaces"// require a labor force that is highly trained and skilled in specialized general computing rather than the trained and skilled in the business domain. In other words, the end-user must find people who are educated and trained in their specific domain (i.e., finance, accounting, taxes, supply chain, environment, public records, etc.) as well as having the computing skills to use the languages, libraries and interfaces for each DIDO Platform. | ||
| + | |||
| + | This is not unlike the problems that have confronted other domains. For example, the [[dido:public:ra:xapend:xapend.a_glossary:d:dbms]] and [[dido:public:ra:1.4_req:1_func:platform:os_arch | Operating System (OS) Platform]] domains. Both of these domains have solved many of their problems by relying on formal, well defined and standardized [[dido:public:ra:xapend:xapend.a_glossary:c:cli | Command line Interfaces]] developed in [[dido:public:ra:xapend:xapend.b_stds:tech]]. See [[dido:public:ra:xapend:xapend.b_stds:tech:ieee:1003.1]] and [[dido:public:ra:xapend:xapend.b_stds:tech:iso:dblang-sql-part1]]. | ||
| /**=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- | /**=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- | ||
dido/public/s_cli/05_contents/01_prt/00_intro/01_problem.1619797663.txt.gz · Last modified: 2021/04/30 11:47 by nick
