Cissp: Knowledge-Based Systems And The Development Models

Front 1

expert system

Back 1

is a knowledge-based system that uses AI to solve complex problems. Is based on a rule based system and inference engine.

Front 2

artificial neural network

Back 2

is a type of knowledge-based system that processes information based on the neuron structure of the human brain.
uses highly interconnected processing elements, which are capable of learning, remembering, and solving a problem from the acquired knowledge or tasks that have been already performed.

Front 3

Iterative and non-iterative

Back 3

Two types of development models

Front 4

Waterfall

Back 4

Non-iterative development model.
It consists of a set of phases that run in sequence. Each stage has to be completed before it's possible to move on to the next. Each phase consists of instructions that need to be followed and recorded.

Front 5

Structured Programming

Back 5

Non-iterative development model which is very disciplined and consists of a modular development and defined processes. Each phase is evaluated and then authorized, which means that security is strong as it is incorporated in a strict methodical approach. This model is one of the most popular software development methods. It has measured adaptability, which allows developers to consider each phase and make ongoing changes to help improve the system.

Front 6

Spiral

Back 6

Non-iterative development model that is similar to a nested version of the Waterfall model in that sequential phases are planned and designed. differs from the Waterfall model in that each phase contains four in-built steps – planning, implementing, checking, and acting. This allows for error checking and risk assessment. The four steps are from another model called Plan-Do-Check-Act, or PDCA, by Demming. So essentially, this model incorporates the PDCA model into each phase.

Front 7

Cleanroom

Back 7

Non-iterative development model that is mostly used for high-quality software development in engineering processes. The main objective is to prevent inconsistencies in the system by writing code without errors at the beginning of the process, rather than having to fix errors at a later stage.
As the intention is to prevent errors at the very beginning of the process, time spent on planning and consideration is much longer than other models allow for. As a result, this assumes that less time will be spent on testing. The security in this model can be strong, as long as it's considered in the planning stages rather than an afterthought.
The testing and checking phase of a development model can be extremely time consuming, especially if not much time has been spent on the initial planning. This model can save a lot of time at the testing phase because of the time spent on initial planning.

Front 8

Prototyping

Back 8

Iterative development model: . One of the first iterative models. A rough system is developed quickly and then tested and evaluated to check where improvements need to be made. A new model is then made with the changes in place and the testing repeated. This cycle is repeated until the system is satisfactory on all levels. Security in this model may be weak to begin with, as the first system is developed roughly. Over the development process, security will be strengthened, but still may be considered as an afterthought.

Front 9

Modified Prototype

Back 9

Iterative development model: creates and implements a system quickly and commences the maintenance phase immediately. This means the system can be constantly revised and improved, and is never static in one stage. Security can be weak in this model, as it's implemented so quickly. Risk is high in the beginning. Over time, inconsistencies will become evident and can be corrected with more security mechanisms.

Front 10

Rapid Application Development

Back 10

Iterative development model: sets a strict time limit for each phase enforcing a quick process. However, mistakes can be made under strict time pressures. As a result of the time pressure, security may not take priority and the security community believes this model to be very risky.

Front 11

Joint Application Development

Back 11

Iterative development model: was created to help developers and users work together to manage the design of a software application. Users who will be performing the job have first-hand knowledge of what is needed. combines the users, the technical experts, and the expert-system developers. By doing this, ensures the development of the best possible solution. is now used in combination with other types of development models to strengthen the suitability of the final system. However, security can be lessened as a result of the large numbers of people involved and time pressures.

Front 12

Exploratory

Back 12

Iterative development model: Bases a system on logical assumptions. As this model is slightly unpredictable, security may lose priority in favor of making rapid adjustments to improve the system.

Front 13

Computer-Aided Software Engineering

Back 13

model uses a variety of tools and approaches to cover most aspects of the software development process including design, development, methodical evaluation, implementation, and maintenance.
It was originally created in the 1970s, but has continued to evolve and is now one of the most widely used models in software development. this model makes use of visual programming tools and object-oriented programming. The this model method consists of building and maintaining the necessary software tools, and providing training for developers.
Often used on large-scale, intricate projects, this model helps the whole software development team work together with a mutual understanding of the project's status at each stage in the life cycle. It can help lower costs and enhance quality as code can be reused.

Front 14

Component-Based

Back 14

model puts a system together using sets of standardized data and standardized methods as building blocks. This can save both time and costs. The security of the this model is highly regarded as the components have all been previously tested.

Front 15

reuse

Back 15

model is put together using previously created components. This model is often used in projects that use object-oriented development because it makes use of exporting, reusing, or modifying objects. Components may be selected that have been previously security tested, again saving time and costs.

Front 16

extreme programming

Back 16

is based on simple values, clear mutual objectives, and feedback. It is a structured approach that works best with a small team. Software systems are produced and released one at a time, and in succession. This means security is implemented with each small succession allowing for strong security. As a result, new customer needs are met with new software being produced constantly.